[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1088
  • Last Modified:

Odd behavior after SCCM server setup

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.  
0
NBquery
Asked:
NBquery
  • 3
1 Solution
 
Abduljalil Abou AlzahabCommented:
Kindly note that secondary sites cannot have sites beneath them in the hierarchy.

Secondary Sites

A secondary site has no Configuration Manager 2007 site database. It is attached to and reports to a primary site. The secondary site is managed by a Configuration Manager 2007 administrator running a Configuration Manager 2007 console that is connected to the primary site.

The secondary site forwards the information it gathers from Configuration Manager 2007 clients, such as computer inventory data and Configuration Manager 2007 system status information, to its parent site. The primary site then stores the data of both the primary and secondary sites in the Configuration Manager 2007 site database.

The advantages of using secondary sites are that they do not require any additional Configuration Manager 2007 server license and do not incur the overhead of maintaining an additional database. Secondary sites are managed from the primary site they are connected to, so they are frequently used in sites with no local administrator present. The disadvantage of secondary sites is that they must be attached to a primary site and cannot be moved to a different primary site without deleting and re-creating the site. Also, secondary sites cannot have sites beneath them in the hierarchy.
0
 
NBqueryAuthor Commented:
Our secondary site XYZ, sits under the primary site.  There are no sites under XYZ as his is not possible with SCCM.
0
 
NBqueryAuthor Commented:
The DP was setup incorrectly.  We just had to wipe it out and reinstall it fresh and we are all set.
0
 
NBqueryAuthor Commented:
We found the solution on our own.
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now