Client installation in another domain
Hi, I am in the middle of rolling out SCCM clients and have got everything installed for clients in the same domain as the SCCM server without any issues. We also have another completely separate company to roll out clients to from the same SCCM server. I have managed to push the client successfully but it won't report back in to the SCCM server. On my original setup I had to extend the AD schema and configure the appropriate permissions for the System container. Can someone point me to a resource or give me a gentle nudge in the right direction as to how to get the machines in the other domain to report in to the SCCM server (I can browse to it and ping it from the other domain but just missing that last bit of the puzzle.) Many thanks, Brian.
June 1st, 2011 11:02am

Same forest or not the same forest? John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|
Free Windows Admin Tool Kit Click here and download it now
June 1st, 2011 11:07am

(I'm assuming separate forest here, as John's question rightly suggests, yes it makes a difference -- mainly in service location, not managability though.) How are installing the client? Are you adding any properties to the client installation? Do you have an SLP set up? Do have it published in WINS? Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
June 1st, 2011 1:27pm

Hi Rodders, Did you have your boundary correctly configured for those clients? If yes, since these clients are not in the same domain as your SCCM server, check the ClientLocation.log on the client to verify the client assignment. If error occured in client assignment, you can: check whether SCCM server data was published to DNS. Technet reference of MP DNS publishing: http://technet.microsoft.com/en-us/library/bb633030.aspx manully publish SCCM server data to WINS server (less security, because data was stored in clear text). If SLP was correctly installed, and assigned to client. Technet reference: http://technet.microsoft.com/en-us/library/bb694195.aspx Thanks
Free Windows Admin Tool Kit Click here and download it now
June 2nd, 2011 3:31am

Hi Brian, 1. You can try to add Server Locator Point role in you SCCM server. 2. Go to Client Push Method|Client Push Installation|Accounts tab add the another domain admin account 3. Click the Client tab and enter SMSSITECODE=XXX SMSSLP=SCCMSERVER.DOMAIN.COM in the installation properties 4. Now try to do the push the client again Alternatively, you can manual install the client using command prompt 1. Open you command prompt and locate the sccm client folder 2. run ccmsetup.exe /mp:SCCMSERVER SMSSLP=sccmserver.domain.com SMSSITECODE=SVR For more information regarding the setup properties, please refer to http://technet.microsoft.com/en-us/library/bb680980.aspx Regards, Hau
June 2nd, 2011 3:57am

Hi, Many thanks for all your replies. I didn't know about SLPs but once I had configured this it all worked fine. I still have some issues remote controlling these clients but I'll raise another thread if I can't figure it out. Brian.
Free Windows Admin Tool Kit Click here and download it now
June 3rd, 2011 7:20am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics