Another user is signed in. If you continue, they'll be disconnected. Windows 10 Multi Session

Copper Contributor

We have successfully rolled out our WVD Tenant after many hurdles.  We are now faced with "Another user is signed in.  If you continue, they'll be disconnected.  Do you want to sign in anyway?"  

Background info on the Image.  The original build came from Market place using "Windows 10 Enterprise for Virtual Desktops Preview, Version 1809".  We installed and configured our apps, joined domain to enable security group etc.  Installed FSLogix and made appropriate reg keys.  After all was configured as we wished we did a Sysprep, Generalize Shutdown.  Of course it had the standard gamet of errors regarding Applications assigned to another user.  Anyway it eventually generalized and shutdown.  We went to the managed disk and Captured to Azure Images.  After doing all prepwork in Powershell we moved on to the Azure GUI and Deployed.  We have done several restarts, shutdowns etc.  Deployed and Redeployed several times.  When we do a winver we are noticing license states Windows 10 Pro, screenshot attached.  We have seen other screenshots around here and other places showing "Windows 10 Enterprise Multi Session" as the License.  Does something happen with licensing after the Machine is generalized that is removing the Enterprise Multi Session License?


I believe Documentation will need some help before this goes GA.  Specifically the ordering of steps.  Our biggest hurdle was likely our own fault but we were having random issues that made no sense.  Specifically the same one that most have been seeing, user not authorized to query management service.  We turns out we were creating all of these items in a Visual Studio Subscription that was tied to our main subscription.  Once we did "set-azcontext -Name "Subscription Name" -SubscriptionId xxxx-xxx-x-xx things begin to start falling in place.  You can check the context you are running under by running a "get-azcontext:.

4 Replies
Winver should say "Windows 10 Enterprise for Virtual Desktops", if it states Pro - you do not have multi-session. We have tested sysprepping Windows 10 Enterprise for Virtual Desktops and it came back up as such. I can try to see if we can repro this scenario, could you send me a private message with more details on the region and resource ID?
Hello Pieter and thank you for replying to my post. I have DM'd you the requested information. After reading your response I went and double checked our Deployment operation details and found we deployed this image MicrosoftWindowsDesktop.Windows-10-rs5-e-20190405081326 I then Deployed another Enterprise Multisession host and looked at its details and noticed it is nearly the same just a bit later build MicrosoftWindowsDesktop.Windows-10-rs5-e-20190411011556. Please let me know if you see anything that is off or have any suggestions.

@ccbrownkc I'm unable to repro the issue, this is what I did: 

  • Opened Azure portal -> Create Resource, search for "Windows 10" 
  • Selected "Microsoft Windows 10" and made sure "Windows 10 Enterprise for Virtual Desktops, preview version 1809" was selected
  • Deployed in US East 
  • Logged on, validated it's EVD via WINVER, rebooted, logged on, sysprep /generalize
  • Capture image
  • Create VM from image, already have a Windows license -> Windows Client

The VM comes up as Windows 10 Enterprise for Virtual Desktops. 


Did you follow the same steps? 

@ccbrownkc I've reached out to one of the Azure specialists to look into this. I'll report back when I know more (this will take a couple of days)