Config Manager Fun with Exindas!

Good morning everyone! I've recently been having an issue in my multi-site environment with clients at some of my remote sites unable to register.

As a quick background on my configuration, I'm running Config Manager 2012 R2. I have a single Primary Site (PRI) located at my data center. We have 6 remote facilities, some of which have their own site servers underneath my PRI primary.

To give you a quick overview of my environment, I have a Primary Site (PRI) with multiple other site servers associated with it. I have two secondary sites, each with a local MP and DP. The sites that aren't blessed with their own Secondary Site - are simply pointing back to PRI for management and content.

All sites are connected over the WAN with VPN links. At some locations (Namely the sites with Secondary Sites), we have Exinda appliances in place. These are used for traffic shaping and prioritization. They also have a handy little thing that they like to call Edge Cache - effectively caching common content in the hopes of saving duplicated traffic.

However, there are common issues with Edge Cache and System Center is no exception!


As for my original issue; Some of my remote sites have been very low in their client counts. For instance, according to AD, I should have approximately 60 clients from site X. However, in my admin console, I'm only showing 10 clients from site X. After manually checking the C:\Windows\CCMSetup\Logs\CCMSetup.log and finding a whole slew of Exit Code 0 -- I began to scratch my head. From every machine that I was looking at, the client was installed correctly and reported success. But why was I still getting such low client counts in SCCM?

Time to investigate some log files!


CcmMessaging.log would show the following five events over and over.
[CCMHTTP] ERROR: URL=http://PRI-SCCM.contoso.local/ccm_system_windowsauth/request, Port=80, Options=192, Code=0, Text=CCM_E_BAD_HTTP_STATUS_CODE CcmMessaging 1/27/2015 7:40:19 AM 1568 (0x0620)
Raising event:
instance of CCM_CcmHttp_Status
{
DateTime = "20150127154019.560000+000";
HostName = "PRI-SCCM.contoso.local";
HRESULT = "0x87d0027e";
ProcessID = 5284;
StatusCode = 400;
ThreadID = 1568;
};
CcmMessaging 1/27/2015 7:40:19 AM 1568 (0x0620)
Request to http://PRI-SCCM.contoso.local/ccm_system_windowsauth/request failed with 400 CcmMessaging 1/27/2015 7:40:19 AM 1568 (0x0620)
Successfully sent location services HTTP failure message. CcmMessaging 1/27/2015 7:40:19 AM 1568 (0x0620)
Post to http://PRI-SCCM.contoso.local/ccm_system_windowsauth/request failed with 0x87d00231. CcmMessaging 1/27/2015 7:40:19 AM 1568 (0x0620)


ClientIDManagerStartup.log would show the following
RegTask: Failed to send registration request message. Error: 0x87d00231 ClientIDManagerStartup 1/27/2015 8:18:55 AM 1228 (0x04CC)
RegTask: Failed to send registration request. Error: 0x87d00231 ClientIDManagerStartup 1/27/2015 8:18:55 AM 1228 (0x04CC)
[RegTask] - Sleeping for 960 seconds ... ClientIDManagerStartup 1/27/2015 8:18:55 AM 1228 (0x04CC)


At this point, I began to think about the difference between Site X and some of my other locations. Ah, Site X has an Exinda with Edge Cache enabled!

I logged into my Exinda and created a new Network Object called 'SCCM Servers' and targeted it to my Site Server's IP. The subnet for this network object can be set to /32 as we only care to define this specific IP as part of this network object.  I also added the IPs to my other SCCM servers at different sites, just to play it safe.



Now, I need to define an optimizer policy to NOT enable Edge Cache acceleration.




Upon saving and applying my changes on my Exinda, things begin to look at lot better!




ClientIDManagerStartup.log finally showed some progress!
[RegTask] - Client is not registered. Sending registration request for GUID:55786A75-B8A0-400E-A033-8CB94A468287 ... ClientIDManagerStartup 1/27/2015 8:09:20 AM 1568 (0x0620)
[RegTask] - Client registration is pending. Server assigned ClientID is GUID:55786A75-B8A0-400E-A033-8CB94A468287 ClientIDManagerStartup 1/27/2015 8:09:21 AM 1568 (0x0620)
[RegTask] - Sleeping for 960 seconds ... ClientIDManagerStartup 1/27/2015 8:09:21 AM 1568 (0x0620)
[RegTask] - Client registration is pending. Sending confirmation request for GUID:55786A75-B8A0-400E-A033-8CB94A468287 ... ClientIDManagerStartup 1/27/2015 8:25:21 AM 1568 (0x0620)
[RegTask] - Client is registered. Server assigned ClientID is GUID:55786A75-B8A0-400E-A033-8CB94A468287. Approval status 1 ClientIDManagerStartup 1/27/2015 8:25:21 AM 1568 (0x0620)

After this change was made, and the clients were given a little bit of time to 'get to know' the SCCM server, clients began popping into my Admin Console.

Comments

Popular Posts