OSD domain join in a non trusted / cross forest domain

[Stian M.]

Hi!

I've recently set up a MP/DP in a non trusted / cross forest domain. Everything is going smooth, except that the computer object is not moved (or created) to the correct OU, but instead it's created in the root Computers OU.

I've made sure that the domain join account has all the necessary permissions in the OUs. The "Apply network settings" task in the Task Sequence is configured with the djoin account only. The "Domain OU" setting is blank.

Here's a snippet from my customsettings.ini:

[DefaultGateway]

32.10.195.1=GD

[GD]

MachineObjectOU=OU=Computers,OU=GUDA,OU=Medier,DC=GD,DC=local

Here's a snippet from smsts.log:

Determining the INI file to use. InstallSoftware 29.10.2015 13.08.37 1824 (0x0720)

Using COMMAND LINE ARG: Ini file = CustomSettings.ini InstallSoftware 29.10.2015 13.08.37 1824 (0x0720)

Finished determining the INI file to use. InstallSoftware 29.10.2015 13.08.37 1824 (0x0720)

Added new custom property MYCUSTOMPROPERTY InstallSoftware 29.10.2015 13.08.37 1824 (0x0720)

Using from [settings]: Rule Priority = DEFAULT, DEFAULTGATEWAY InstallSoftware 29.10.2015 13.08.37 1824 (0x0720)

------ Processing the [DEFAULT] section ------ InstallSoftware 29.10.2015 13.08.37 1824 (0x0720)

------ Processing the [DEFAULTGATEWAY] section ------ InstallSoftware 29.10.2015 13.08.37 1824 (0x0720)

Match found for default gateway 32.10.195.1, retrieving settings. InstallSoftware 29.10.2015 13.08.37 1824 (0x0720)

------ Processing the [GD] section ------ InstallSoftware 29.10.2015 13.08.37 1824 (0x0720)

------ Done processing CustomSettings.ini ------ InstallSoftware 29.10.2015 13.08.38 1824 (0x0720)

Process completed with exit code 0 InstallSoftware 29.10.2015 13.08.38 1824 (0x0720)

SetupErr.log is clean - no errors SetupAct.log is also clean, the only thing I can see is that DJOIN.EXE MachineObjectOU = [NULL].

Has anyone been working with a similar issue? I'm quite stuck here, and google doesn't say much about the subject.

Regarding the blank field in Domain OU; it doesn't really matter if the field is blank or not - I've tried both.

Just to clarify - the customsettings.ini works like a charm when deploying OS to machines in my "primary" domain. The computers are assigned to their respecive OUs specified in customsettings.ini.

Anyone here with a clue?

[jay]

Check C:\Windows\debug\NetSetup.log

 

Also OSD won't move an existing object, you will need to provide a script to do that.

[Stian M.]

SOLVED!

 

"Apply network settings" -> Domain OU -> %MachineObjectOU%