lansti
Hot Shot
Hot Shot

Windows 10 - UEM 9.x - Mandatory profile logs automatically off during logon..?

I've set up a Windows 10 Build 1607, and created a desktop pool. For these and I'll have a mandatroy profile, but when I log on client software, it will automatically be logged out again.

For testing, I set up a Windows 7 client, following the same procedure to create a mandatory profile for this, and this works as it should.

Anybody else have experience with mandatory profile on Windows 10?

Best regards
Lansti
Reply
0 Kudos
Pieter_S
Enthusiast
Enthusiast

Hi Lansti,

It can be possible that in your windows 10 environment the configuration or the profile archive directory is not available at logon. Default client behavior of UEM will be logging of then.

What you can try is to set the policy "Paths unavailable at logon" to "Skip import". In this case you can check if the paths are unavailable at logon.

If the user can logon at that point you can troubleshoot why the network shares are not available.

Let me know!

Reply
0 Kudos
lansti
Hot Shot
Hot Shot

Hi Pieter. Thanks for your reply.

Your suggestion did not work, but this setting is located in a policy named: "Horizon Agent All Users"

When i Link policy "Horizon Agent Computer Setting" i get this issue.

If I Enable "Set roamin profile path for all users logging onto this computer" \ "Users logging onto this computer should use this roaming profile path: \\server\roaminprofile\%username%" it works great, but if i change it to "\\server\UEM-Config\mandatory" it stops working and logging off.

I have followed Carl Stalhood guidelines: Horizon Group Policy and Profiles – Carl Stalhood

Best regards
Lansti
Reply
0 Kudos
larsonm
VMware Employee
VMware Employee

I've seen this occur when the user logging in does not have the necessary permissions to access the network location where the mandatory profile resides.  For example, I have the mandatory profile on a network share secured with permissions on a specific AD group, and then I try to log in with the local administrator account.  In that case, the system logs off the local account because said account does not have permission to access the file share and folders that contain the mandatory profile.

Reply
0 Kudos
Pim_van_de_Vis
VMware Employee
VMware Employee

Make sure that UEM is configured correct and the configuration share and profile share are available and users have correct permissions.

See this guide for all information needed:

http://pubs.vmware.com/uem-91/topic/com.vmware.ICbase/PDF/user-environment-manager91-install-config....

Also make sure to follow this guide to create the mandatory profile for Windows 10, it's the only supported way:

https://technet.microsoft.com/en-us/itpro/windows/manage/mandatory-user-profile

If the UEM fileshare is not available at logon, the user will be logged off by default.

You can configure this behavior: what should happen if the fileshare is not available.

See this chapter in the installation guide for the available options and how to configure:

VMware User Environment Manager 9.1 Documentation Center

View solution in original post

Reply
0 Kudos
lansti
Hot Shot
Hot Shot

Thanks, it works, but now everytime i logs on to windows i takes like 20 sec before i am logged in. I find this a little slow, and assume that the sysprep has something to do with this delay, since i get "prepering windows" on every logon.

some suggestions?

Best regards
Lansti
Reply
0 Kudos
Pim_van_de_Vis
VMware Employee
VMware Employee

Windows 10 first logon is always longer then Windows 7, because the profile is bigger. That's how Microsoft designed the user profile in Windows 10.

Did you remove the Modern / Universal apps that you don't need? The OS Optimization Tool can help you with that.

Also check out these blog posts that can online this week:

VMware User Environment Manager, Part 1: Easier, Faster Windows Logins with Mandatory Profiles - VMw...

VMware User Environment Manager, Part 2: Complementing Mandatory Profiles with VMware User Environme...

Reply
0 Kudos