RonDel Posted April 14, 2014 Report post Posted April 14, 2014 Hello.... I've got a bit of a situation, and I'm hoping that someone might have a possible solution for me. I work for a company that has about 100 sites, and each site as two networks - an admin network and a lab network. the lab network is a subdomain of the admin network: adminnetwork.local lab.adminnetwork.local Each domain is setup on a different subnet, and for the most part, the lab network cannot access the admin network. Ports have been opened so that the lab machines can access the "primary" SCCM server at our datacenter. We are setting up an SCCM 2012 infrastructure to replace our existing SCCM 2007 infrastructure. With SCCM 2007, we have one server at each site with two NICs that service both networks. With SCCM 2007, server is joined to adminnetwork.local - but has a second NIC for our lab network - lab.adminnetwork.local domain. This 2nd NIC only has IP and subnet - no gateway or DNS information. This has worked without issue for for nearly 4 years in our environment. Our issue is with imaging in SCCM 2012. when we PXE boot machines on the adminnetwork.local, everything goes through fine, without issue. However, when we attempt to image on the lab newtork, the clients boot, but they are still looking for the admin NIC to service them. Once we start the imaging process on the LAB network, on the client, it PXE boots, gets an IP/subnet mask, and prompts us to select the TS to run. Once selected, on the Installation Progress box, the server that client is looking for is http://SCCM.adminnetwork.local (this would be the local SCCM server but the NIC on the admin network) - not http://sccm.lab.adminnetwork.com (which would be the same server, but the NIC that is on the lab network). Does anynoe have any suggestions on how to get the machines on the lab network to look for http://sccm.lab.adminnewtork.local when we try to image? We do have a way around this - and personally, I don't like it. It's to register the 2nd NIC (for the lab network) in DNS with the adminnetwork.local domain - I'm afraid of the potential issues this might cause. I'm looking for a way for the systems (and SCCM) to recognize that it's the on the LAB domain, and that it should use the proper URL for the LAB NIC in the server - http://sccm.lab.adminnetwork.com. Quote Share this post Link to post Share on other sites More sharing options...