Installing Client via GPO on Subnet with 2 Domains -SCCM 2012 SP1

[TheDoctor]

OK, so this is an odd one. We have 51 forests that we are currently consolidating. This summer we will be replacing computers at 24 schools with no time to do onsite imaging (400-500 machines per school and only 1.5 days per site to get it done).

• We are connected on a Metro-E and all Forests have Trusts built back to our "consolidated" domain.
• All DC's are running in our datacenter as well as DHCP for ALL sites (sites=forests)
• DC's are on different subnet that DHCP

I built an MDT 2013 server and a set of MDT Task Sequences that Auto-name the machine based on schoolname (the TS uses the TS Name for schoolcode. so I have 24 Task Sequences, all identical other than name), type and service tag (ex. = LHS-L-123XYZQ) and supplied the server to the vendor to do the imaging into workgroup offsite so they would have time to get them imaged before bringing onsite.

 

I created a profile in the image and added a shortcut to a batch file on their desktop that joins them to the consolidated domain and drops them into a particular OU.

I created a Device Collection based on the OU and it populates properly.

 

The issue I'm facing is that when I test the process in my office, which is on the consolidated domain, everything works fine.

 

When we take machines to a school and test, it's hit-or-miss, but mostly miss.

 

I have worked on changing from MSI/GPO deployment to startup script, logon script and even manual install, but most of the time it fails with various errors, but the most common are here, from the CCMSetup.Log:

GetDPLocations failed with error 0x80072ee7 (ccmsetup)

Unable to retrieve AD forest + domain membership

 

However, if I push the client thru SCCM it works every time.

 

DHCP DNS settings point to our consolidated domain and we just add a suffix search order thru GPO on the "old" domains for them to access both.

 

I realize that 2 domains on the same subnet can be an issue, and we are working through that (consolidating 24 domains-user accounts, groups, etc is also happening this summer but not before the machines will arrive), so unless I want to spend my summer "Updating Membership" and pushing the client, I need to find a way to get this going.

 

 

[Peter van der Woude]

It looks like you didn't configure ConfigMgr to write it the different forests. I would start by supplying an initial management point during the client installation. This should tell the client were to assign and the management point will help the client with locating polices, distribution points, etc. For more client installation properties, see: http://technet.microsoft.com/en-us/library/gg699356.aspx

[TheDoctor]

It would seem so, but we are using the ADM template with the following settings for the MSI:
/MP:SCCM.FQDN SMSMP=SCCM.FQDN SMSSITECODE=HCS

 

Thanks for the reply!