Profile sizes/logon times with Windows 10

[tango]

Hi folks,

 

We've been getting complaints/comments about slow login times in our student labs.

Labs contain quite a bit of software (Adobe CC , Office 2016 , Autodesk , Visual Studio etc etc).

 

In general we create a local account , log on and run/configure all the programs before capturing that profile as the "default" mandatory one which works well but is large and slow.

 

I've seen many posts with amazing logon times , can anyone share their secrets and give me advice on how they create profiles for labs , keeping them small and with quick logons please ?

 

Thanks in advance.

 

Tango

[disk]

Is this the method you are following?

 

https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/customize-the-default-user-profile-by-using-copyprofile

 

We currently use USMT. I deploy one of our images via SCCM which includes all the software for a particular area. I then launch the software and make any customizations before capturing the profile. I then create a task in SCCM that will deploy this profile along with the image and software. USMT does a great job of capturing Windows and Microsoft software settings, and some popular third party software. For the more esoteric software, you will need to modify the XML file that tells USMT where that software captures the settings. Our logon times are fantastic in labs that have SSDs, and acceptable in labs that don't. Hope this helps.

[tango]

Hi disk,

 

Thanks for the great reply.

 

Currently we use MDT to build the image using a suspend task to pause it. At that point we run all of the software , entering any license details , save locations etc.

 

We then resume the task sequence and let MDT capture it to WIM. We then import the WIM into SCCM and deploy the images that way.

 

We then create a local user (lets say called "profile") with admin rights on a PC in the lab , log on to that and run any software that was added to SCCM task sequence on top of WIM.

 

We then log on with a domain admin account and run a script that copies the "profile" to a shared folder on a server. After that we change permissions on registry by mounting the ntuser.dat on the server and then rename to ntuser.man

 

We then configure a group policy to "set roaming profile path for all users logging onto this computer" to point to the share on the server.

 

We've also tried copying the profile from the server to default on each machine.

 

Can you give me a bit more info on how you are capturing the profile and the USMT steps please ?

 

Thanks in advance.

 

Tango