Sysprep

  • Thread starter Thread starter Joe
  • Start date Start date
J

Joe

Hi All,

We created a Master Image joined it to our exisiting AD
Domain, applied all SP's and HFX's then sysprep'd it. I
created a Sysprep.inf file that performs a completely
unattended install and to join our new domain.

It will not see the new domain, IP, DNS etc are set in the
sysprep.inf as are the domain details, all data is
applied, you run the Network ID Wizard specifying the same
data and it joins no problem, why will it not join during
the setup, is it due to thew order in which switched are
applied in the file, I ask this as the keys detailed in
thwe Unattend.doc are in a different order to those of a
file created by setupmgr.exe.


We are adding them manually as we speak so any help will
be appreciated on this ever so starnge one.

Regards.

Joe
 
I'm not sure of the exact reason but I have seen
something similar. When I build my images for sysprep I
keep them as vanilla as possible. I don't join the master
image PC to a domain or specify a local admin password. I
found that by not doing this in the build and then
specifying these items in the sysprep.inf it works
faultlessly.

Hope this helps.

Damien
 
I suspected as much!!
Thanks for the reply, I have resorted to using the
GuiRunOnce key to fire a NetDom command to se if this will
assist..

Thanks again

Joe
 
Hi All,

We created a Master Image joined it to our exisiting AD
Domain, applied all SP's and HFX's then sysprep'd it. I
created a Sysprep.inf file that performs a completely
unattended install and to join our new domain.

It will not see the new domain, IP, DNS etc are set in the
sysprep.inf as are the domain details, all data is
applied, you run the Network ID Wizard specifying the same
data and it joins no problem, why will it not join during
the setup, is it due to thew order in which switched are
applied in the file, I ask this as the keys detailed in
thwe Unattend.doc are in a different order to those of a
file created by setupmgr.exe.
Click to expand...

Same problem here. We just have it join a workgroup automatically and
then we manually join the domain afterwards.

Adam
 
Back
Top