With the XP sysprep I could make an answer file with all the info in except computername, I could put in the domainname to join for a site and name/password to join it, and then I could reseal the PC and image it out. When they bootup they only ask you for the PCname and then join the domain and reboot leaving you at a login screen to login to the domain and all is ready.
However with win7 I'm crying at the obstructions with just doing the same thing. I've reading lots everywhere that you need multiple reboots to rename a machine then reboot, then join to a domain and reboot, etc - be and that's using powershell scripts.
Using unattend.xml with the unattendedjoin component joins it BEFORE it asks for a pcname - so that's useless. I've tried a trick where as you sysprep you make a regentry to run a vbscript before OOBE which asks you for the pcname and writes it into the unattend.xml before the oobe uses the xml to join the domain using that pcname. But for some reason while the pcname part works the domainjoin doesn't.
So why is it XP is capable of a miniswetupwizard that asks just for a pcname and then joins a domain and then reboots and it all works - yet I can't find a way to do it with win7? I managed to write off my whole master image yesterday into a reboot cycle after a sysprep attempt failed in shell-setup during specialise pass -__-
I'm really sick of this contrived nonsense when I had everything working just fine with xp and a simple sysprep.inf and I only want to do the same for win7 Clearly the result I'm after should be the minimal amount of work to do AFTER imaging - hence minisetup should only ask for pcname (to be unique but not random) and take the rest from an answerfile and that's that. Right now I can't get it to enter the key or activate itself or join the domain or anything
Does ANYONE know how to run a simple sysprep that will generalise the system then bootup and only ask for a pcname and then join the domain with that name and reboot? D:
_________________________________
Leozack
However with win7 I'm crying at the obstructions with just doing the same thing. I've reading lots everywhere that you need multiple reboots to rename a machine then reboot, then join to a domain and reboot, etc - be and that's using powershell scripts.
Using unattend.xml with the unattendedjoin component joins it BEFORE it asks for a pcname - so that's useless. I've tried a trick where as you sysprep you make a regentry to run a vbscript before OOBE which asks you for the pcname and writes it into the unattend.xml before the oobe uses the xml to join the domain using that pcname. But for some reason while the pcname part works the domainjoin doesn't.
So why is it XP is capable of a miniswetupwizard that asks just for a pcname and then joins a domain and then reboots and it all works - yet I can't find a way to do it with win7? I managed to write off my whole master image yesterday into a reboot cycle after a sysprep attempt failed in shell-setup during specialise pass -__-
I'm really sick of this contrived nonsense when I had everything working just fine with xp and a simple sysprep.inf and I only want to do the same for win7 Clearly the result I'm after should be the minimal amount of work to do AFTER imaging - hence minisetup should only ask for pcname (to be unique but not random) and take the rest from an answerfile and that's that. Right now I can't get it to enter the key or activate itself or join the domain or anything
Does ANYONE know how to run a simple sysprep that will generalise the system then bootup and only ask for a pcname and then join the domain with that name and reboot? D:
_________________________________
Leozack
Code:
MakeUniverse($infinity,1,42);