AD Profiles - Local and Mandatory

[synaesthesia]

Moving over to Windows 10 this summer and we're all but ready to rock and roll. I'd *love* to get a few machines built over to it, perhaps the staffroom machines. However, a shift from mandatory to local profiles isn't going to make that easy and I wonder if it's at all possible?

So for instance currently we have windows 7 machines using mandatory profiles; thus, there's a profile location in AD for each user. Win10 will use local profiles with UE-V, so that profile location will be empty.

The only option we can think of currently is just to knock up a couple of test accounts for people to muck around in, but in an ideal world I'd like people to use their own accounts. Can anyone think of a way to make that possible? As it integrates so tightly with Office 365 that would be *so* nice, especially after recently banning USB devices entirely to show how the new setup will make life easier for staff!

[dogeye]

Enabling "Computers Configuration\Policies\Administrative Templates\System\User Profiles\Only allow local user profiles" and "Computers Configuration\Policies\Administrative Templates\System\User Profiles\Prevent Roaming Profile changes from propagating to the server" with Group Policy should allow you to run local profiles on your Windows 10 machines

 

I believe that you should be able to leave the profile path unchanged in AD as the path you specify gets a suffix appended to it based on the version of Windows. So, Windows 7 will get ".V2", Windows 8 gets ".V3", Windows 8.1 gets ".V4" and Windows 10 gets either ".V5" or ".V6" depending on which release you are using. If you don't create a V6 mandatory profile Windows should fall back to creating a local profile instead

 

https://support.microsoft.com/en-us/help/3056198/roaming-user-profiles-versioning-in-windows-10-and-windows-server

[3s-gtech]

That's a hell of a first post. I think you're bang on.

[synaesthesia]

Oooh, that's something to give a go! Many thanks And indeed, welcome!

[synaesthesia]

Just to confirm, this works perfectly

[dogeye]

Thanks for the welcome guys! I'm glad it worked

[PotNoodleTech]

Thanks for the welcome guys! I'm glad it worked

 

Welcome! Do you work for Microsoft?

[computer_expert]

Anyone having issues on the 2nd logon where the machine tries to grab the profile defined in the ADUC user profile tab instead of using the local profile?

 

First logon is fine, it creates the local profile but on the second logon it uses the profile defined in AD (which won't work as it is a Win7 mandatory profile). GP is using the options as per post #2. Have the same issue on LTSB2016 & v1703 CBB.

 

The profile versioning reg key is set to 1 on the LTSB box, and no v6 profile exists alongside the Win7 V2 profile so can't understand why it's using that one instead