Forum Discussion
"Activate Windows" Watermark has Appeared on Windows 10 Enterprise for Virtual Desktops SessionHost
Hi Mark,
I raised a call with Microsoft Support on the 28th September for the same issue. Following a troubleshooting session, the engineer advised that there is an ongoing investigation into this issue but currently no ETA on the fix.
Details are below from the engineer:
"I have found that your behavior matches with an ongoing investigation:
• Windows 10 AVD
• Platform image: Windows 10 Enterprise for Virtual Desktops-10.0.19044.2006
• Showing intermittent watermark: Activate Windows
• Slmgr shows that the VM is licensed with Partial product key: GVLK
• Issue seems to be happening with users with lower permissions, not been able to be detected with users that are part of the Local Admins group
At this moment, there is no ETA about providing results of the ongoing investigation nor a fix.
Once the fix is released, the same will be shipped as part of an update. This can be either a preview update or as well in a cumulative one after patch tuesday."
Hope this helps,
Phil
I've been working with Microsoft, been playing with applying keys, enabling and disabling test signing. They keep feeding back to the AVD product group but doesn't look like they can find a solution to this issue. These users are pretty restricted so your thought on a permission issue somewhere could be correct.
Thanks.
Kevin
KevHalWe have the same issue with a Nerdio Scale set. We have observed this issue for 2 weeks now and the common theme is only for the 1st user of the AVD will have this watermark, for some of the AVD. The subsequent 4 users (as we have total of 5 users per AVD) do not have any water mark. We have checked and also have each user activated. I look forward to an update for this from MS.
USNOOZEYULOOSEY KevHal Hi chaps, I work for Nerdio and I worked with a few customers who were having this issue. What we did to get around the issue is just to force the re-activation. We just used the Nerdio scripted actions to run Slmgr.vbs /ato against the host pool and that fixed it.
However, that's a workaround, not a fix. But it stops the problem until Microsoft can fix the issue.
- Well its been about a week. Whilst the scripted action works (thankfully), it has a side effect. We have a scale set, and we have the action applied daily (as I cant see a way to do it upon logon), it will turn on VM's, run the scripted action, then turn it off again. Our scale set launches 8/70 VM's by 0510hrs but scales out to have 40 available sessions at all times. For some reason users can logon during the scripted actions timing which is unfortunate as users log on for 2 minutes, then get kicked off once the scripted action completes and it shuts down that VM again. We dont want to change from the scale set and how its setup.
Is there a way for it run the action upon a AVD's logon rather than run it daily?
