Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

DeployAnywhere leaves local administrator account disabled

Created: 08 May 2013 • Updated: 09 May 2013 | 2 comments
This issue has been solved. See solution.

If I simply check the Include DeployAnywhere option when in the deploy image task, minisetup runs as expected, GhostUser logs in, reboots, and I'm sitting at the login screen ready to roll with all drivers installed. HOWEVER, the local administrator account is disabled.  Granted, I have a backup LA account which is properly added and not disabled, so I know oobeSetup pass is running.  If I enable the account after logging in with other credentials, the password is also set properly.

If I uncheck the Include DeployAnywhere option, the LA account is properly enabled.

I am using the latest version of DA, as found here:  http://www.symantec.com/docs/TECH186664

Thoughts?

Thanks!

Operating Systems:

Comments 2 CommentsJump to latest comment

David Zell's picture

I don't use deploy anywhere, but I have had a similar issue and resolved it by having sysprep login as the local admin account the first time.  I think, by default the local admin account is disabled unless you do this.

SaintFrag's picture

I got it figured out.  I moved my net user administrator /active:yes command from the specialize pass to the oobeSystem pass.

SOLUTION