Posted March 23, 201212 yr Using a newly installed OS, I've customized a default profile using the Administrator account and used the in sysprep to successfully move it over to the Default user account. I then moved forward and added the machine to the domain to log on as a domain admin account used to create images - our "Image" account. From there, I connected to the network resources to add what needed to be added and then removed the machine from the domain and logged into the Administrator account.... here is where I think I am running into an issue. When the machine is joined to the domain, the default domain policy changes the Administrator account to another name. This is done for security and uniformity throughout the organization for desktops and servers alike and cannot be changed. I believe that it is this step that is throwing me the curve ball. When I run my unattend.xml that copies the profile, I now get an error during the specialized pass (as per the error). I'm using the same xml as the first time around with rearm value set to 1. The only thing that is different that I can think of is the following: 1. The "Image" account has been deleted from the Users folder. 2. It was joined and disjoined from the domain. 3. The Administrator account name was changed, but the account folder in Users is still "Administrator" as well as other registry entries. 1 net user administrator /active:yes c:\corpsoft\pra.bmp pra false true Central Standard Time true * TgAwAHQANgA0AGIAMQB0ACEAUABhAHMAcwB3AG8AcgBkAA== false true 1 Administrator true true Work 3 TgAwAHQANgA0AGIAMQB0ACEAQQBkAG0AaQBuAGkAcwB0AHIAYQB0AG8AcgBQAGEAcwBzAHcAbwByAGQA false TgAwAHQANgA0AGIAMQB0ACEAUABhAHMAcwB3AG8AcgBkAA== false placeholder admin account sysprep users sysprep false true en-us en-us en-us en-us en-us 1 Continue reading...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.