jpboyce Posted July 4, 2011 Report post Posted July 4, 2011 Hi all, I'm currently trying to setup a secondary site SCCM server for a new office. The server is running Windows 2008 R2. I've added all the prerequisites as per the documentation and when the installer runs, it doesn't find any problems. However, after installation is complete, it's like the server hasn't communicated back to the primary server. Symptons of this include: * The new server/site doesn't appear in the sites list in the SCCM console on the primary * I'm seeing almost zero traffic flow between the new secondary and the primary server * No activity in the Inbox folders Is there any sort of known issues that might cause this? I've tried turning Failure auditing on for the new secondary server in case it was a permissions issue but I'm not seeing anything coming up in relation to SCCM. Any ideas, suggestions, etc? Thanks. Quote Share this post Link to post Share on other sites More sharing options...
Trevor Sullivan Posted July 5, 2011 Report post Posted July 5, 2011 Hello jpboyce, I'd start out by checking your IIS logs on both the secondary site and the primary site. That may give you some indication as to what's failing. Are you using the FQDN or NetBIOS name of the secondary site in the sender address? http://technet.microsoft.com/en-us/library/bb680457.aspx FWIW, I haven't had any issues running a central & child primary site both on Windows Server 2008 R2 systems. I realize this is a bit different from your setup, but it's actually more complicated since there's two primary sites in play. Just thought I'd throw that experience out there. Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86 Quote Share this post Link to post Share on other sites More sharing options...
jpboyce Posted July 6, 2011 Report post Posted July 6, 2011 Hello jpboyce, I'd start out by checking your IIS logs on both the secondary site and the primary site. That may give you some indication as to what's failing. Are you using the FQDN or NetBIOS name of the secondary site in the sender address? http://technet.microsoft.com/en-us/library/bb680457.aspx FWIW, I haven't had any issues running a central & child primary site both on Windows Server 2008 R2 systems. I realize this is a bit different from your setup, but it's actually more complicated since there's two primary sites in play. Just thought I'd throw that experience out there. Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86 Hi Trevor, There's nothing at all in the IIS logs for the secondary site server. I can't see any references to the new server in the IIS logs on the primary server. The sender address is using the NetBIOS name (as is all the other secondary) I"ve managed to progress is now though so that the new site is appearing. However, I"ve run into a new issue relating to server shares. There's two server shares setup on the secondary site servers. I've set these up on the new server, but when I try to copy a package, it only lists the "root" server (ie. servername), it doesn't list server\sharename in the list of distribution points. Quote Share this post Link to post Share on other sites More sharing options...