Instead of using a post-install batch job to rename the Administator account, could this be added as a post-provision script within the system package? The post-provision script will execute on the targee before any BSA jobs execute to avoid the situation.
Did Newton's response help solve the problem?
Can you share any more information with the community?
Thanks & Regards,
Jim (Forum Manager/Facilitator)
1 of 1 people found this helpful
We use a GPO to automatically rename our Administrator account. Since it is possible that the timing of the rename from the GPO is not always the same, I wrote a simple script that runs during provissioning to make sure that the agent is mapped to a valid account.
Ours looks like this:
net user svcBMCBSAadmin randompassword /add
net localgroup Administrators svcBMCBSAadmin /add
echo BLAdmins:BLAdmin rw,map=svcBMCBSAadmin>>%WINDIR%\rsc\users.local
So you could just do that echo into users.local for map=Administrator and then let your rename script do the echo back to your xxxyyyzzz account. Then do acl push to make sure your files are all clean.
I know that isn't a pretty solution, but it is really just adding to "echo"s to your existing process.