Secondary Site Installation Successful, but Not Working

[BzowK]

Hey Guys / Niall - 

I'm wrapping up the build of a brand new environment on a new domain we are migrating to and installing the last Secondary Site of 7.  The destination servers of all the Secondary sites are all new 2012 R2 installations where I manually installed all pre-reqs, deployed the Secondary site from the console, and once complete added SUP & SMP.  All 6 installed prior to this one went great with no issues.  However, this last one is a pain even though I installed it the exact same way.  It shows it completed successfully, but that's not the case.  Below is a list of characteristics of the issue , what I've tried so far, and finally log info.  I'm referring to the Secondary with issues as "TEX" and primary site as "ABC"

Characteristics of Secondary Site Issues (As it appears 24 hours after installation / deployment)

• Installation completes successfully and under Sites its listed as "Active."  All results within Installation Results pass except for 2 pre-req warnings
  • BITS & IIS6 WMI compatibility component for IIS7 are not installed or cannot be verified
  • Setup unable to establish a remote connection to WMI on secondary site
• Site Status & Component Status lists do not contain and entries from "TEX" yet lists ones from the 6 other Secondaries
• AD Forests / Publishing Status lists all 6 Secondaries + 1 Primary including TEX - however - the "Last Publishing Time" & "Last Publishing Status" are empty only for TEX
• There are no entries for "TEX" within System Management container
• In Monitoring / Database Replication, it states "Link is being configured" & "Initializing data between the parent site and child site". 
• Replication Analyzer
  • Inconsistent public keys - asks me to initiate public key transfer for target site TEX on source site ABC
  • File replication route is required for site-to-site communication and file replication route is missing for site ABC on site TEX
  • Replication initialization is aborted in site ABC for the replication groups: Secondary_Site_Replication_Configuration. RLA recommends reinitializing the above mentioned groups on site TEX.  This may take several hours
• A boundary group with ~200 IP Ranges is associated with the Secondary Site
• Groups for local admins on TEX are the same as all other secondaries
• Distribution is not working / processing anything to TEX although should be

What I've Tried to Resolve Issue

• Uninstall Secondary Site then reinstall
• Delete Secondary Site from console then manually uninstall all SCCM & SQL components, delete related files, registry entries, and even uninstalled roles / features; rebooted; then reinstalled all from scratch - same issue persists
• Manually added server's hostname to System Management container delegating full access to it
• Chosen to run all suggested actions in Replication Link Analyzer.  After doing each, same issue appeared so had to skip rule to get it to continue
• Used the commands "preinst.exe /keyforchild" and "preinst.exe /keyforparent" then copied the resulting files into the hman.inbox where they belonged.  They were processed and disappeared but nothing changed
• Considering uninstall / reinstall again but using a different site code.  Only thing is that if that worked I feel I'd have some crap left over in database from old site code and don't want to jeopardize stability or performance

Log FIles

Below are individual log files as well as ZIPs of multiple ones taken from when I worked on it this afternoon. 

• TEX_to_ABC Diagnostics.csv
• ReplicationAnalysis.htm
• rcmctrl_(Primary ABC).log
• rcmctrl_(Secondary_TEX).log
• AllReplicationLogs.zip
• SecondaryLogFiles.zip
• SecondaryInstallLogs.zip
• replmgr_(Primary ABC).log
• replmgr_(Secondary_TEX).log

The site is 2012 R2 SP1 CU4 with all site servers running 2012 R2 OS.  Any help or suggestions you could provide would be fantastic - Thank You!!

[BzowK]

Anyone able to assist?  Thanks!

[anyweb]

hi Ben

if you fix the " BITS & IIS6 WMI compatibility component for IIS7 are not installed or cannot be verified " does it make any difference ?

[Eswar Koneti]

Have you checked the SQL ports 1433 and 4022 (bi-directional) between SCCM Primary to Secondary Site ? I suspect you had firewall port issues that cause this issue.

[BzowK]

Hey Guys - 

Sorry for the late reply.  Found out that there were some routing issues with the server which I think caused the issue.  Actually tried a site recovery a couple of days ago.  Checked the status today and it said it completed successfully, but the site was still in the "Recovering" status.  In addition to the initial warnings, it now also had the warning: Setup is unable to establish a remote connection to WMI on the secondary site.

I still think there are routing issues, honestly; but in the meantime am trying a full install again to make sure by performing the below steps - I just finished the below steps and am waiting on results.

1. Deleted secondary site from Primary choosing to Uninstall the site - verified that it uninstalled from Add/Remove programs on server
2. Ran PS script on server to install pre-reqs.  They should already be installed, but thought I'd run it too to be sure.(Details below)
3. Ran "winmgmt /verifyrepository" but came back consistent so not going to attempt to salvage or reset
4. Restarting server
5. Install Secondary site again using same settings (below) from Primary server

Wish me luck!  By the way, below are the Secondary settings selected, the script I ran for pre-reqs, plus it's output:

Secondary Settings For Install

•  Site code: BSA
•  Site server name: SECPMSCCM01.mycompany.net
•  Site name: Texas Secondary Site Server
•  Installation folder: C:\Program Files\Microsoft Configuration Manager\
• Accounts
•  Site server communication account:
• •    Primary site connection: Secondary computer account
• •    Secondary site connection: Primary computer account
• (Yes - Primary's hostname is a local admin and hostname of secondary has full rights to System Management container & objects within)
• Site System Roles
•  Management point: MDCPMSCCM01.ardenthealth.net
•  Distribution point: MDCPMSCCM01.ardenthealth.net
• Installation Status
•  Copy installation source from parent: Yes
• SQL Server Settings
•  Install and configure SQL Server Express: Yes
•  SQL Server service port: Yes
•  SQL Server Service Broker port: 4022
• Boundary Groups
•   Success: Boundary Settings
• •    Fallback source location for content: Allow fallback source location for content: No
•   Success: Boundary Groups
   

SCCM Pre-Reqs Install Script
Import-Module servermanager
Add-WindowsFeature WAS-Process-Model
Add-WindowsFeature WAS-Config-APIs
Add-WindowsFeature WAS-Net-Environment
Add-WindowsFeature Web-Server
Add-WindowsFeature Web-ISAPI-Ext
Add-WindowsFeature Web-ISAPI-Filter
Add-WindowsFeature Web-Net-Ext
Add-WindowsFeature Web-ASP-Net
Add-WindowsFeature Web-ASP
Add-WindowsFeature Web-Windows-Auth
Add-WindowsFeature Web-Basic-Auth
Add-WindowsFeature Web-URL-Auth
Add-WindowsFeature Web-IP-Security
Add-WindowsFeature Web-Scripting-Tools
Add-WindowsFeature Web-Mgmt-Service
Add-WindowsFeature Web-Lgcy-Scripting
Add-WindowsFeature Web-Lgcy-Mgmt-Console
Add-WindowsFeature Web-Stat-Compression
Add-WindowsFeature Web-Metabase
Add-WindowsFeature Web-WMI
Add-WindowsFeature Web-HTTP-Redirect
Add-WindowsFeature Web-Log-Libraries
Add-WindowsFeature Web-HTTP-Tracing
Add-WindowsFeature BITS-IIS-Ext
Add-WindowsFeature Net-Framework-Core
Add-WindowsFeature RDC

Script Output

Success Restart Needed Exit Code      Feature Result                               
------- -------------- ---------      --------------                               
True    No             Success        {Process Model}                              
True    No             NoChangeNeeded {}                                           
True    No             Success        {.NET Environment 3.5}                       
True    No             NoChangeNeeded {}                                           
True    No             NoChangeNeeded {}                                           
True    No             NoChangeNeeded {}                                           
True    No             Success        {.NET Extensibility 3.5}                     
True    No             Success        {ASP.NET 3.5}                                
True    No             Success        {ASP}                                        
True    No             NoChangeNeeded {}                                           
True    No             Success        {Basic Authentication}                       
True    No             Success        {URL Authorization}                          
True    No             Success        {IP and Domain Restrictions}                 
True    No             NoChangeNeeded {}                                           
True    No             Success        {Management Service}                         
True    No             Success        {IIS 6 Scripting Tools}                      
True    No             Success        {IIS 6 Management Console}                   
True    No             NoChangeNeeded {}                                           
True    No             NoChangeNeeded {}                                           
True    No             NoChangeNeeded {}                                           
True    No             NoChangeNeeded {}                                           
True    No             NoChangeNeeded {}                                           
True    No             NoChangeNeeded {}                                           
True    No             NoChangeNeeded {}                                           
True    No             NoChangeNeeded {}                                           
True    No             NoChangeNeeded {}  

Thanks again...

[SNB12148]

BzowK, did you ever get to the bottom of your issues? Ever get it up and running? I have a Secondary Site with the very same issues. I'd be grateful to hear if you figured it out. Thanks in advance!