Thanks for your reply Eswar.
One of the SMS_SiteToSiteConnection_<SiteCode>
groups on two of my Secondary Site servers I believe are configured correctly and they both have my Primary Site Server as a member, but the
SMS_SiteSystemToSiteServerConnection_<SiteCode> group is empty. Is the
SMS_SiteSystemToSiteServerConnection_<SiteCode> group supposed to contain my Primary Site server as well? Both the SMS_SiteSystemToSiteServerConnection_<SiteCode>
SMS_SiteToSiteConnection_<SiteCode> groups on my Primary Site Server have my Secondary Site Servers as members.
Is this correct?
I'm wondering now if the strange groups with the odd site codes that don't even exist were created when the secondary sites were initially being created a while back. From the documentation, it looks like the former admin initially configured the secondary
sites using a PowerShell script created by Kaido Jarvemets. According to some of the notes I have read, the admin kept uninstalling and re-installing the sites when they were not showing up in the SCCM 2007 Admin console, but apparently they simply forgot
to configure a Sender and an Address, if that makes any sense to you.
So, perhaps these groups ending with an odd Secondary Site code may have been a typo during one of the installation attempts? If this is the case, can these groups be deleted?
One thing I forgot to mention was that the Secondary Site servers belong to a Global Security AD group and that group is used to add them to both the SMS_SiteSystemToSiteServerConnection_<SiteCode
and the SMS_SiteToSiteConnection_<SiteCode>
groups on the Primary Site server.
Is this allowed?
- Edited by
Wednesday, February 12, 2014 9:06 AM