This post is more than 5 years old
1 Rookie
•
5 Posts
0
1274
January 14th, 2017 22:00
Issues with Temp environment after Imaging
I would like to know if anyone else is having issue with the temp environment after imaging. I chosen to copy the admin profile on the unattended xml creator as the default profile. That was working in Windows 7 but in Win10 the following registry stays as the name of the admin user which causes issues whenever a new profile is created.
HKEY_CURRENT_USER \Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
C:\Users\(copied admin profile name)\AppData\Local\Microsoft\Windows\INetCache
C:\Users\(copied admin profile name)\AppData\Local\Microsoft\Windows\INetCookies
I'm using latest DIA and Windows 10 (Anniversary update).
Thanks and regards,
Robert
No Events found!
Roboteknix
1 Rookie
•
5 Posts
0
January 18th, 2017 22:00
Hi Tyler,
Thanks for the reply.
On the same day I posted the query, I crossed check the same registry entries on my base image and found that for some reason the entries for the cache and cookies points to the admin account so I just renamed it to the generic %userprofile% then take the image again and it worked.
It was a clean OEM install, then upraded to Win10 Anniversary update. Did rename the admin account prior to IA.
Regards,
Robert
DELL-Tyler M
Moderator
•
342 Posts
0
January 17th, 2017 13:00
Hi Robert -
What are your build steps? Was this a clean install of the OS; did you rename the local admin account prior to running ImageAssist, policy changes, etc.?
Thank you,
Tyler