I'm having an issue where an admin account created during deployment is having major permission issues. One example is the inability to install applications as it doesn't have correct permissions to Program File (x86)
The account is created in unnatended.xml with the following to commands;
cmd /c net user /add newadmin password
cmd /c net localgroup administrators newadmin /add
Those commands are done during the Specialize>Microsoft-Windows-Deployment phase and are two separate run synchronous commands. The commands succed at least partially since the account is created and when checking it through the local users mmc snap-in I see that the account belongs to the administrators group.
To further troubleshoot, I created another admin account through the standard GUI. The end result was;
- Built in administrator account has correct permissions and can install applications and carry out all expected actions
- Admin account created through standard GUI has correct permissons
- Admin account created in unatended seem to have bad permissions and cant carry out expected actions
I just noticed that the permissions issue only occurs when manually launching the program as a different user using the run-as option. If I just double click the program and have it spawn the windows dialog to run as a different user, then it completes. So it looks like the program only manifests in instances where I need to use the runas option.