MDT 2013 UDI Wizard Domain join not working

[Atomic12]

Hi,

 

after exhausting all of my options once again I need help.

My test VM wont join a domain, and I don't know why.

 

Environment:

SCCM 2012 R2

MDT 2013

Wmware Workstation VM

OSDJoinAccount and OSDJoinPassword variables set in all Unknown Computers collection and they prepopulate in UDI wizard.

Account for adding to domain is Domain Admin/Enterprise Admin.

 

Customsettings.ini

[settings]
Priority=Default
Properties=MyCustomProperty

[Default]
OSInstall=Y
SkipCapture=YES
SkipAdminPassword=NO
SkipProductKey=YES

 

 

Is Customsettings.ini missing some values?

 

Lot of unnecessary steps disabled on purpose to fast up the process.

 

Sales OU created by "Search by domain OUs" not manually(!)

 

Drivers maybe not applying?

 

What I have tried:

1. Disable step in TS Apply Network settings and remove check marks in UDI Wizard for checking AD credential check on both section (User and password) - no go.

2. Tried adding without and OU, so OU blank, and only domain - no go.

3. Tried leaving default computer name, yes I get the famous MININT predefined name (maybe leftovers from some script?, need help with that also)

4. Many other things that I cannot remember right now.

 

Please help,

Thank you,

UDIWizard_Config.xml

smsts-20140918-010624.log

[anyweb]

what does your netsetup.log file say (c:\windows\debug) ?

 

you need to reenable the apply network settings step, it's used for joining the domain...

 

"<![LOG[The action (Apply Network Settings) has been skipped because it is disabled]

[Atomic12]

Hi,

 

thanks for answering at this hour! Really appreciate it!

 

But the specified name is CLIENT05 not 02 so it must be some old value somewhere.

 

P.S. It did not work even when the step (apply network settings) was enabled. Do I have to specify Domain OU? Or leave it empty?

 

Wuh, so many edits from my side, I apologize, why is the date 31/8?? I will delete the whole VM, and create a completely new one.

[Atomic12]

Hi,

 

this is a netsetup.log from another VM machine that has been all the time in suspend/pause mode.

But my concern is that this VM was not created by the MDT TS but the ordinary one. But it still joined after wrong first part again CLIENT 02.

I am shutting down all client VMs and will test again.

 

Edit: 16:20

Found solution, will post whole procedure and description today!

NetSetup.LOG

[Atomic12]

Hi,

 

soooooo, the problem was in my test environment which consists of 2 DC's, 1 DB Server, 1 SCCM 2012 Server and 3 clients on a test laptop.

Test laptop was without battery at that time and I pulled the power cord out in order to move it to another desk and boom, none of the machines had a proper shutdown so my two DC's DID NOT REPLICATE because of connectivity issues, and therefore could not handout proper info to the test clients. That is why I kept having the CLIENT02 name in the netsetup.log. Once i reestablished the connection it worked like a charm!

Who would have thought that could be the problem, oh well, at least it is solved.

 

Edit: 21.09. I kept having the same issues again, I mean the replication worked, but i kept getting the same old name so i thought it must be the DNS settings so I changed the following:

 

Reverse lookup zones settings.

1. Added a reverse lookup zone for my test domain.

2. Set dynamic updates to Nonsecure and secure.

3. Put a checkmark on Scavange stale resource record, and set it to one day.

4. Changed the default TTL to 1 hour.

 

Forward lookup zone my domain settings.

1. Dynamic updates to Nonsecure and secure

2. Put a checkmark on Scavange stale resource record, and set it to one day.

3. Changed the default TTL to 1 hour.

 

I deleted the CLIENT02 record in both forward lookup zone and revers lookup zone, and I think that solved the problem. I still get the entry in netsetup.log but at least it adds the computer to the domain. Must be a lab setup issue.

 

Thanks anyweb, you pointed me in the right direction!

[anyweb]

glad to hear that you figured it out !

[Kinross]

Good Morning,

I'm experiencing the exact same issues.

 

Environment:

SCCM 2012 R2

MDT 2013

Windows Server 2008 R2

 

Customsettings.ini

[settings]
Priority=Default
Properties=MyCustomProperty

[Default]
OSInstall=Y
SkipCapture=YES
SkipAdminPassword=NO
SkipProductKey=YES

NetSetup.log

05/21/2015 09:21:51:344 -----------------------------------------------------------------

05/21/2015 09:21:51:344 NetpDoDomainJoin

05/21/2015 09:21:51:344 NetpDoDomainJoin: using new computer names

05/21/2015 09:21:51:359 NetpDoDomainJoin: NetpGetNewMachineName returned 0x0

05/21/2015 09:21:51:359 NetpMachineValidToJoin: 'MININT-JRA7BL9'

05/21/2015 09:21:51:359 OS Version: 6.3

05/21/2015 09:21:51:359 Build number: 9600 (9600.winblue_rtm.130821-1623)

05/21/2015 09:21:51:359 SKU:

05/21/2015 09:21:51:359 Architecture: 64-bit (AMD64)

05/21/2015 09:21:51:359 NetpGetLsaPrimaryDomain: status: 0x0

05/21/2015 09:21:51:359 NetpMachineValidToJoin: status: 0x0

05/21/2015 09:21:51:359 NetpJoinWorkgroup: joining computer 'MININT-JRA7BL9' to workgroup 'WORKGROUP'

05/21/2015 09:21:51:359 NetpValidateName: checking to see if 'WORKGROUP' is valid as type 2 name

05/21/2015 09:21:51:359 NetpCheckNetBiosNameNotInUse: for 'WORKGROUP' returned: 0x858

05/21/2015 09:21:51:359 NetpCheckNetBiosNameNotInUse for 'WORKGROUP' [ Workgroup as MACHINE] returned 0x858

05/21/2015 09:21:51:359 NetpValidateName: name 'WORKGROUP' is valid for type 2

05/21/2015 09:21:51:359 NetpSetLsaPrimaryDomain: for 'WORKGROUP' status: 0x0

05/21/2015 09:21:51:359 NetpJoinWorkgroup: status: 0x0

05/21/2015 09:21:51:359 NetpDoDomainJoin: status: 0x0

I followed your labs 16 -18 but I'm unfortunately I just can't get this going. Could it be a permissions issue? I've reviewed all the logs from x:\windows\temp\smstslog and x:\smstslog. Is there a particular log file I should be looking at?

Your help would be greatly appreciated.

[Atomic12]

Hi,

 

are the issues in for example in VMware Workstation, Hyper-V, Oracle VirtualBox?

Here are my notes:

Check netsetup.log in c:\windows\debug

TS Apply network settings page should be applied not disabled.

If netsetup.log is showing you old values like old client name or old dates check DC’s replication and ping them and other servers (DB, SCCM).

Ping ip address with –a (reverse lookup in WinPE environment)

Ping FQDN with –a

[Kinross]

Thanks for the quick response.

 

I'm experiencing these issues on all our Dell Latitude laptops.

 

I'll try your suggestions and let you know.

 

Again, much appreciated.