Need Help Figuring Out Domain Join

KnightStorm99

How do I get the domain join/computer rename to work using WIE via PXEBoot during the imaging process. I have everything else working correctly for the most part but I'm struggling getting it to join using a service account with sufficient permissions.

Greg_E

What priority do you have that policy set to? Is it the lowest number of all other policies (like -100)? Do you have a cleanup policy after it (-50)? And reboots after each? And then finally do you have a policy to get the inventory so the client reports correctly?

KnightStorm99

I will look into all this again. I don't have a cleanup policy or an inventory policy set at the moment.

KnightStorm99

I was able to figure out the domain join and I have the cleanup policy set. One thing I can't figure out is renaming the computer during the imaging process. I put the name in but once it finishes imaging it goes with a generic name.

Greg_E

KnightStorm99

Part of the policy is failing, if the name is in your AD, the computer should get that name when the policy finishes. Watch the video carefully, the details are in there. Its been about 3 months since I was firing with similar issues, and finally got it working. But that lab system got torn down and I'm not sure I have screen shot of the process. There was a small detail that I kept missing, and once I noticed it, that part was working fine.

Part of this might have been persisting the drivers before sysprep, trying to load the drivers was really giving me trouble.

KnightStorm99

Greg_E I'm not entirely sure what policy you are referring to. Currently I'm utilizing WIE for imaging because I don't want to have to disable secure boot. As of right now I have the imaging working and I have it inject the drivers as the last part of the imaging process. Then it boots up to the logon screen and does the domain join then restart and finally the cleanup and a final restart. At what point does it actually rename the computer? I enter the name at the start of the registration when it boots into PXE. Does the computer have to be an existing object in AD for the naming to work correctly?

Greg_E

I'm not positive, but I think it might need to be in the AD and Toems needs to be synced to know it is there. I won't be back to testing for a few weeks, I have design work that's needed for our TV studio that has a ticking clock on it.

Tarrantx

I'm currently renaming my systems with the Autounattend.xml, rather than asking TOEM to do it. I think this creates issues with Image Only systems showing up in TOEMS but, it does work.

From my perspective, the computer name should be set before it is domain joined, so renaming via sysprep ensures this happens. There is a great autounattend generator here: https://schneegans.de/windows/unattend-generator/

They also have useful example scripts you can use with the generator here: https://schneegans.de/windows/unattend-generator/samples/

As we name all of our systems according to MAC address, I'm using the "derive computer name from MAC address" script. I am thinking of instead using this script as a TEOM script module that applies before the domain join policy. That would probably make more sense.