Jump to content

Recommended Posts

Posted

Has anybody started testing Windows 10 1703 for deployment yet?

 

We use SCCM to deploy, however are having some issues with mandatory profiles (v6 from 1607) etc.

Posted
Yup, we're using it as our only version of 10 now (though we have no deployment widespread), and I'm happy with the overall function. Not having any issues with mandatory profiles, though I did copy my .v6 profile to a .v7 in case MS followed the pattern from 1511 to 1607 (does it follow the build number maybe, so v5 for 1507 and 1511, v6 for 1607, v7 for 1703?). No info yet on https://docs.microsoft.com/en-us/windows/client-management/mandatory-user-profile
Posted
Do the issues include no start menu? If so, join the club.

 

We seem to have cured this one!

 

- - - Updated - - -

 

Yup, we're using it as our only version of 10 now (though we have no deployment widespread), and I'm happy with the overall function. Not having any issues with mandatory profiles, though I did copy my .v6 profile to a .v7 in case MS followed the pattern from 1511 to 1607 (does it follow the build number maybe, so v5 for 1507 and 1511, v6 for 1607, v7 for 1703?). No info yet on https://docs.microsoft.com/en-us/windows/client-management/mandatory-user-profile

Profile version in 1703 is still V6 as far as I am aware.

Posted
We are seeing a strange issue. We have Impero on site, when deploying 1703 with Impero and login with a mandatory profile, Explorer has no text (eg. no 'This PC' just the icon)! If we deploy without Impero, the issue goes away. Just wondering if anyone else has experienced this.
Posted
Was really a case of playing around (literally hit and miss) with the profile and permission to certain registry keys in order to make it all work. - There are some good guides online, however none seem to provide everything you need.
Posted
from my testing the start menu issue is if you disable cortana via applocker(assuming its the one i had where it looked ok but greyed out and you couldnt use it) i stopped that rebuilt the pc (as ive found applocker policies dont remove well and it was 1 test laptop) and the start menu seemed happy again but not tried mandatory profiles i canned then with windows 7. I did find with mdt you had to make sure you updated the adk and mdt before you imported the image or it had issues deploying it to a real pc (worked fine on a vm for some reason laptops i tried it on just sat there after installing drivers on a black screen for ever)
  • 4 weeks later...
Posted
I managed to get the start menu working on 1703 by making sure the "Authenticated Users", and "All App Packages" groups had full permissions over the mandatory profile hive.
  • 1 year later...
Posted
Not having any issues with mandatory profiles, though I did copy my .v6 profile to a .v7 in case MS followed the pattern from 1511 to 1607 (does it follow the build number maybe, so v5 for 1507 and 1511, v6 for 1607, v7 for 1703?). No info yet on https://docs.microsoft.com/en-us/windows/client-management/mandatory-user-profile

IIRC, the profile extension version only increments when Microsoft make changes to the profile that would cause incompatibilities with previous versions of Windows (inc. between W10 versions).

 

There isn't a .v7 profile version yet. With Microsoft essentially phasing out roaming and mandatory profiles maybe there never will be? :)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...