Cache a domain account as part of build
A generic domain account is used for all laptop builds - lets call it laptoplogon. Trying to automate the caching of the account to avoid the Service Desk being asked to logon after the build process to "cache" the logon. Therefore if the user takes the laptop away and attempts to logon offline the account is there and in cache so they are ok Appreciate you could hack reg keys to auto- logon as this account as part of the build but I'd prefer to simply copy in the cache if that's possible ?Ian Burnell, London (UK)
May 15th, 2012 6:24am

Hi Ian Burnell, Are you using SCCM OSD to deploy operating system? If so, when you join the computer to domain during OSD whith specifid domain join account this account will be cached in the client. So your help desk can use this account. Thanks
Free Windows Admin Tool Kit Click here and download it now
May 17th, 2012 5:25am

Yes SCCM OSD. The account used to join the domain is not the same (and can't be the same) as this generic accountIan Burnell, London (UK)
May 21st, 2012 10:53am

Your talking about having the profile already cached on the local system so it doesn't have to be built upon first login, right? You're not going to be able to do this through the install task sequence unless you're using the USMT for a replace/refresh scenario. The only way to do this on a new system would be to capture the OS after you've logged in with the laptoplogon account. To do this you could use sccm task sequence to build the image. Then stop it before it does a capture. Logon with your account. Then insert the capture media and then save the wim. The image will include your cached profile.
Free Windows Admin Tool Kit Click here and download it now
June 21st, 2012 6:09pm

He's not refering to the profile, he's refering to the logon so that a DC does not have to be explicity contacted for the user to logon. This is completely different from their profile. Ian, your best bet is to post this on a Windows or AD forum.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
June 21st, 2012 6:41pm

Easy - Create a run command line in the task sequence to run something during the build and select the option to use a specified account. Maybe run gpupdate or something simple like that. This should cache the profile and achieve what you need. http://technet.microsoft.com/en-us/library/cc431425.aspx
Free Windows Admin Tool Kit Click here and download it now
June 22nd, 2012 10:12am

Easy - Create a run command line in the task sequence to run something during the build and select the option to use a specified account. Maybe run gpupdate or something simple like that. This should cache the profile and achieve what you need. http://technet.microsoft.com/en-us/library/cc431425.aspx Hmmm, that actually may work. Worth a try.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
June 22nd, 2012 1:51pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics