Odd behavior after SCCM server setup
Posted on 2011-02-16
We just setup a fresh SCCM infrastructure. Right now we have one central site, and a secondary site that will act as just a DP. Two oddities have arisen
1a. Our Active directory has two Active Directory sites used by SCCM that are combined into one logical AD site for our e-mail system. So where the central site ABC is physically separate from the secondary site XYZ, they appear as one entity in AD sites and services. We are using subnets to set boundaries on our sites. On the central site ABC, I am using the local LAN subnet where all the workstations are. I put this subnet in the ABC boundaries. I'm a bit lost on where to put the secondary site LAN subnet as a boundary. Should it be under the central site boundary, or on the secondary sites boundary? Both subnets are now defined under the central site boundaries, but not sure if this is correct.
1b. While the only primary site with a MP is our central site ABC, can we have clients at the secondary site have their own site-code of XYZ, or will it only use the central site code ABC, as it is the only MP? I'd like to have those clients on the local lan @ site XYZ to have XYZ be their SCCM Site code.
2. When I'm trying to add new packages to a DP, the central site is listed twice along with the secondary site?? The sites I have available to add packages to show up like this in the 'Add Distribution Points' wizard:
ABCSCCM1 Site ABC -SCCM Central Site Type Server
XYZSCCM1 Site XYZ - SCCM Secondary Site Type Server
ABCSCCM1 Site XYZ - SCCM Secondary Site Type Server
Why would the central site server, be listed as part of the secondary site?? Is this normal?
Hoping one of you guys might have an idea.