Student profiles

[IdiotTech]

Hi All,

 

Has anyone created student profiles for windows 10?

Could anyone send me a "step by step How to do"?

 

Ive worked in It for a few years but never had to create profiles.

 

Any help would be awesome. Thanks all

[Javik]

Don't know what you are asking exactly. User profiles are typically a combination of group policy user settings plus enabling a network share for roaming or mandatory profile storage. But otherwise the process used with Windows 7 / 8 is exactly the same as before.

 

It would be pretty hard for anyone to give you a step by step do how when so much of it can be customized.

[3s-gtech]

Have a look here (for mandatory profiles):

 

http://www.edugeek.net/forums/windows-10/163160-w10-mandatory-profile-issues.html#post1397548

[Guest obsidianpillar]

Hi,

What we've got in our environment is we'd export the "Default Profile" for Windows 10 (systempropertiescomputername.exe, Advanced, User Profiles, Default Profile, Export to network share giving EVERYONE full control.) Then we'd setup an account in Active Directory, in our environment we'd give it a username of something along the lines of "Win10-March16". We'd set the account to have full control of the profile share we'd setup to allow it to write to it and set the profile path to \\servername\sharename\win10-march16\%username%. This would create the profile that we'd then distribute to users.

 

We'd then logon as that user on a workstation that you're going to use the profiles on (i.e. all apps installed that you'd like to configure settings for). We'd then make all necessary customisations that are specific to the network/client and then logoff. At this point (unless you've got a policy in place preventing this) it will copy and propagate the profile back to the server. We'd then ensure that it's copied over and then we'd deploy it, changing the extension to .man on the NTUSER file.

 

In our environment we don't assign profiles based on individual users (inside of AD), we use the "Set Romaing profile path for all users logging onto this computer" Group Policy to assign different profiles based on workstations in different OU's. This works well with us to allow us to customise profiles based on different system images etc.

 

Not saying it's the best, or equally right way. I know methods that involve using Sysprep etc to achieve the same method. This is what works for us and allows us to make customisations without having to recreate the profile again.

 

Working in a Server 2012 R2 Environment with Windows 7/8.1 and 10 Clients.

 

Best Wishes,

Tom.

 

EDIT: One thing to note, use this as an opportunity to remove all of the unnecessary MS Apps that may write to AppData. We did this by removing unnecessary programs and our profile sits at around 2mb.

 

 

Edited March 9, 2016 by obsidianpillar