ConfigMgr makes a rather reasonable assumption that you're not going to have two systems with the exact same name. With the Client Push, by design it's going to attempt to connect to the NETBIOS name first, and then attempt with the FQDN if that fails. If you have machines with the exact same name in both domains, it's always going to connect to the one in the same domain as the ConfigMgr server, just as you're seeing.
Your best bet for those duplicate machines in the other domain is to use something other than Client Push for the installation. -Phil _________________________________________________________________ Phil Schwan | Technical Architect, Enterprise Windows Services Microsoft VTSP ([email protected]<mailto:[email protected]>) Project Leadership Associates | 2000 Town Center, Suite 1900, Southfield, MI 48075 Lync: 312.756.1626 Mobile: 419.262.5133 www.projectleadership.net<http://www.projectleadership.net/> [linkedin_logo-19x20] <http://www.linkedin.com/in/philschwan> [Twitter-Logo1-20x20] <https://twitter.com/philschwan> [wordpress-logo3] <http://myitforum.com/myitforumwp/author/philschwan> [Description: Description: Description: Arrow email]Lead with Strategy. Leverage Technology. Deliver Results. From: [email protected] [mailto:[email protected]] On Behalf Of Mario Van Uytsel Sent: Friday, January 8, 2016 3:28 AM To: [email protected] Subject: [mssms] Client Push to server on other domain Hello all, We have upgraded our SCCM 2012 R2 to Sccm 2012 R2 SP1 CU2. It manages 2 domains, domain1 and domain2 with no problem. SCCM servers are in domain1, domain2 has been setup to allow the sccm from domain1 to manage all clients. In every domain we have a RDS server called RDSserver1. (rdsserver1.domain1.be and rdsserver1.domain2.be) When I do a manual client install (right click computer and select install client) to the RDSserver1 in domain2 the installer runs on the RDSserver1 in domain1. For some reason it does no use the domain name for client push, it connects to \\rdsserver<file:///\\rdsserver> 1\admin$ and not to \\rdsserver<file:///\\rdsserver> 1.domain2.be\admin$ as I should be. The client push account is configured correctly. When installing the client on a system in domain2 that does not exist in domain1 ex. SQLserver5 it first tries to connect to \\SQLserver5\admin$<file:///\\SQLserver5\admin$> what fails, then it tries \\sqlserver5.domain2.be\admin$<file:///\\sqlserver5.domain2.be\admin$> what is the correct path and the client gets installed. Is anyone else getting this? Mario Mario Van Uytsel Systeembeheer Windows Server Infrastructuur [cid:[email protected]] KU Leuven ICTS | www.kuleuven.be/icts<http://www.kuleuven.be/icts> [email protected]<mailto:[email protected]> | t. +32 16 3 22166
