S
Sheree
We've been using sysprep for over a year now with no
problems. However, we've just started getting this error
even when we set the system administrator password to
blank prior to sysprepping the machine. We've also tried
leaving the password in and not specifying any password
values in the sysprep file and we still get the error.
We've also tried using a clean system install instead of
an image with the same result.
FROM MS DEPLOY.CHM
[If you specify a password in the Administrator account,
you cannot use AdminPassword in the Sysprep.inf file to
change it. The Administrator password remains the same.
However, if the Administrator password was initially
blank (either manually or through an unattended Setup),
you can use AdminPassword to change it to a nonblank
password.]
We are using Windows XP SP1 and version 2.0 of sysprep.
We've also tried creating a custom file and an inf file
from setupmgr--same result. Initially we thought we had a
corrupted sysprep file or an invalid entry, but we've
tried it using the setupmgr generated file as well as
three different sysprep files all with the same result.
Frankly, we are baffled and we have a lot of machines to
roll out.
Any help offered would be most appreciated.
Thank you,
Sheree
problems. However, we've just started getting this error
even when we set the system administrator password to
blank prior to sysprepping the machine. We've also tried
leaving the password in and not specifying any password
values in the sysprep file and we still get the error.
We've also tried using a clean system install instead of
an image with the same result.
FROM MS DEPLOY.CHM
[If you specify a password in the Administrator account,
you cannot use AdminPassword in the Sysprep.inf file to
change it. The Administrator password remains the same.
However, if the Administrator password was initially
blank (either manually or through an unattended Setup),
you can use AdminPassword to change it to a nonblank
password.]
We are using Windows XP SP1 and version 2.0 of sysprep.
We've also tried creating a custom file and an inf file
from setupmgr--same result. Initially we thought we had a
corrupted sysprep file or an invalid entry, but we've
tried it using the setupmgr generated file as well as
three different sysprep files all with the same result.
Frankly, we are baffled and we have a lot of machines to
roll out.
Any help offered would be most appreciated.
Thank you,
Sheree