Apr 10 2019 08:39 AM
Bonjour,
Je souhaite mettre en place WVD pour un client dès qu'il sort de la preview, mais je n'arrive pas à déjà le mettre en place sur un de mes tenant pour un problème qui j'imagine est simple. J'ai lu les erreurs rencontrées qui sont toutes après l'étape ou je bloque.
Je m'appuie sur https://docs.microsoft.com/en-us/azure/virtual-desktop/tenant-setup-azure-active-directory
Je bloque sur Add-RdsAccount -DeploymentUrl "https://rdbroker.wvd.microsoft.com" qui me renvoie une erreur (module installé version 1.0.1.11)
PS C:\WINDOWS\system32> Install-Module -Name Microsoft.RDInfra.RDPowerShell
PS C:\WINDOWS\system32> Import-Module -Name Microsoft.RDInfra.RDPowerShell
PS C:\WINDOWS\system32> Add-RdsAccount -DeploymentUrl "https://rdbroker.wvd.microsoft.com"
Add-RdsAccount : Une ou plusieurs erreurs se sont produites.
Au caractère Ligne:1 : 1
+ Add-RdsAccount -DeploymentUrl "https://rdbroker.wvd.microsoft.com"
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Add-RdsAccount], AggregateException
+ FullyQualifiedErrorId : System.AggregateException,Microsoft.RDInfra.RDPowershell.Context.AddRdsAccount
Je résouds bien le nom du site, les "consent" ne m'ont pas posé soucis sur le tenant ou je souhaite déployer le WVD, et je suis bien "TenantCreator".
Le support premier Azure m'a répondu qu'il ne faisaient pas de support sur les preview et m'ont envoyé ici.
Tenant ID 25f527cb-a837-40a2-b467-7bd2ab69f27c Application ID 5a0aa725-4958-4b0c-80a9-34562e23f3b7
Merci de votre retour
Apr 10 2019 02:52 PM
@Voxan : When going through the consent flow it takes some time to register. Please try to follow this steps again and you should be successfull.
Apr 11 2019 07:45 AM
Hi @Eva Seydl
Thanks for your answer.
I made again consent page for server app ( Thank You! AAD Application has been successfully registered) and i'm still getting the error message in PS
I made another more consent this time for both server & client app, and i'm still getting the error message in PS
I then checked if i was always a Tenantcreator. My account appeared 2 times, one default, and one Tenantcreator. I tried to update default to Tenantcreator and it failed wich was expected. I deleted the Tenantcreator account and then updated the default account to Tenantcreator with success.
But i'm still getting the same error message in PS....
Thanks
Apr 17 2019 02:15 PM
@Voxan : Two questions:
- Are you logging in with a user or service principal?
- Is it sourced from that Azure AD tenant? Or is it a guest (B2B user)?
Apr 17 2019 02:48 PM
I'm logging with a user interactively
The user is not sourced from the tenant i'm trying to configure WVD.
The user is at first attached to my local company AD and the AAD tenant linked is not used.
We are using a development tenant for our NAV/BC developers, wich is the one where i'm trying to configure WVD.
Since the last answer i made i also tried this : create a new tenant, consent apps, tenantowner role, and ran the commands from a new win2k19 azure VM. Still without success and same error message.
Thanks
Apr 25 2019 12:08 PM
@Voxan : Thanks for your patience. Can you try performing the same operations but with a user who is sourced from the Azured AD that you're trying to create a Windows Virtual Desktop tenant for?