Auto join domain using sysprep - Windows 7

Fixed for you.

Code:

---

Brilliant, Thanks :)

---

Thanks for posting that!

I have a script that pulls the asset tag from the machine which is what we use for PC naming.

Dumb question : how does that script get deleted after the final boot?

When the script runs, it does not join the Domain. I entered our information here with what JaTyler said change what was in RED.

Quote:

---

Originally Posted by ronnoco

Hi all,

We are quite new to using Windows and Sysprep is a different kettle of fish to the XP version I am use to.

I have followed Brian Lee Jacksons Sysprep guide and all works well apart from I am not sure how to get a machine to automatically join the domain?

Is there a setting in the unattend.xml file or do a need an additional xml file or a vbs script?

We are using FOG to capture and deploy the image.

Thanks very much in advance for any help/advice.

Gary

---

I don't know what version of FOG your up to but I've been using version 0.29. It has a client you install in the image before your run sysprep. It handles the domain join, computer naming, and a host of other things. I believe all you need to do is put your active directory information into the FOG server (you need to encrypt your AD password first. instructions) and install the agent in the image before you sysprep it (get the agent from <fog_ip/hostname>/fog/client).

Justin

Can you possibly provide the exact syntax of the entries we need to change? In other words is the user in the domain\user format or just the user name, is the domain the netbios name or domain.local and does the computer account need to be created in AD before this script runs?

I've experienced the same occurrence as windstar above, that the rename of the PC is successful, but when it tries to join the domain, it gives you the same join domain failed, error code 0. I also see even following the instructions on placing the files in the c:\windows\setup\scripts folder that they don't automatically run upon completion of the unattended setup. I can run the scripts physically by browsing to them, and it won't join the domain.

i used mysysprep version 2

it pops up asking for computer name and then asks you what domain you want. i have it auto populated with the 1 domain i have , so we just have to click ok.

Alright, we're somewhat there. This particular utility will join the PC automatically to the domain, but I can't get it to prompt us for a computer name. I've left the <ComputerName></ComputerName> blank which is supposed to prompt, also I've deleted the line completely according to another site that should prompt it as well. Any more suggestions?

not sure if its been posted before but this site here enables you to create the xml file that joins a domain without having to jumo through hoops the MS way.


Windows 7 unattend.xml Generator

Do You have to change anything in your unattend xml file

Thanks to JaTaylor for the vbs script useful addition to the arsenal.

I tried to create the XML file using Ben O'Sullivan's XML generator, and that crashed my image with error "Windows could not parse or process unattend answer file c:\windows\panther\unattend.xml for pass specialize. The answer file is invalid. My IT director shot down any thought of using a third party tool such as mysysprep since it is not being authorized by Microsoft. Any suggestions?

How can i delete the autojoindomain.vbs after its ran?
I dont want it left on the computer since it contains password

Quote:

---

Originally Posted by ihaveaproblem

How can i delete the autojoindomain.vbs after its ran?
I dont want it left on the computer since it contains password

---

You should be able to just add:

Code:

---

Dim objFSO
Set objFSO = CreateObject("Scripting.FileSystemObject")
objFSO.DeleteFile WScript.ScriptFullName
Set objFSO = Nothing

---

at the end. So it'll delete itself, might want to test it, but should work.

Steve