CMG - HTTP1.1 500 CMGConnector_InternalServerError, check SPN

-

Picking up from my last post that covered the issue involving CMG Azure cloud resources and Tags, my battle was half won in the implementation project of CMG that I was carrying out for one of my customers.


After the cloud service was created and the service reported the status as ‘Connected’, the next logical step was to test and verify the connection. This is where things started to go south. On running the ‘CMG Connection Analyzer’ against the Client Authentication Certificate, I received the following error.




SMS Cloud Proxy Connector log indicated the same.



In my experience, that looked like a communication issue between the connection point and the HTTPS server configured to accept CMG requests.


The ConfigMgr environment has a Standalone Primary (Co-located SQL) configured to cater to HTTP requests. Cloud management gateway connection point was also configured on the same server.

Another server was stood up to cater to HTTPS requests. This server would also manage CMG traffic.


I started checking the health of the server in question (the one setup to respond to HTTPS request). The MP component was reporting all kind of HTTP errors indicating a possible issue with IIS. While I checked the IIS, I couldn’t find a reason for it to be not operational.


Next thing I did was to check the MPcontrol.log and this is where things started to make a little sense. There were entries pointing to SPN not being reachable.



I checked the SPN entries and Voila, they were clearly missing. As a matter of fact, the SPNs were created on the wrong Domain Service Account. If you are running the SQL Service (MSSQLSvc) with local computer system account, the SPNs are registered automatically and you should not see these types of errors. But, if you are running the SQL Service (MSSQLSvc) account with a domain account, then you
must manually register the SPN to ensure SQL clients and other site system can perform Kerberos authentication. Without Kerberos authentication, communication to the database might fail.


In order to fix, the following commands were executed. (Please note that you will need Domain Administrator rights to register the SPN manually)


To delete existing SPNs from wrong service account:

  • setspn -D MSSQLSvc/{SQL Server FQDN}:1433 {Domain\Account}
  • setspn -D MSSQLSvc/{SQL Server FQDN} {Domain\Account}

 To add new SPNs to the correct service account:

  • setspn -A MSSQLSvc/{SQL Server FQDN}:1433 {Local Computer Account}
  • setspn -A MSSQLSvc/{SQL Server FQDN} {Local Computer Account}

Allowed an hour for the replication to go through across all other Domain Controllers in the environment and then restarted the SMS Executive on server in question (Catering to HTTPS) and the errors cleared up in MPcontrol.log.



Also, the Connection Analyzer went through all the way this time.





Hope this helps. Until next time..

Reference - https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/register-a-service-principal-name-for-kerberos-connections?view=sql-server-ver15


Comments

Post a Comment

Popular posts from this blog

How to force escrowing of BitLocker recovery keys using Intune

-
Image
Every now and then it so happens that BitLocker recovery keys do not escrow in AAD. The usual culprits are incorrect BitLocker policies and\or the device hardware configuration failing to meet the minimum requirements. The other scenario and something I recently experienced is when everything is setup right and still the recovery key doesn’t escrow in AAD. As I understand, this can happen if the escrow process got interrupted the first time due to network or local devices related issues and the process could not resume. To circumvent this issue, one can simply push a PowerShell script to the devices to force the escrow of the recovery keys to AAD. Here is a script to do so. try{ $BitlockerVol = Get-BitLockerVolume -MountPoint $env:SystemDrive         $KPID=""         foreach($KP in $BitlockerVol.KeyProtector){             if($KP.KeyProtectorType -eq "RecoveryPassword"){              ...
Read more

Prevent users from running certain programs or applications on Windows endpoints using Intune

-
Image
  When it comes to blocking or preventing users from running an application on Windows devices, one normally uses App locker policy, Windows Defender Application Control and not so new but pretty useful method called Defender Vulnerability management within Microsoft 365 Defender Portal. A recent question on the Tech Community Microsoft forum prompted me to look for all possible alternatives. I started reminiscing over the legacy GPO policies and that is when I stumbled upon the policy  Don’t run specified Windows applications  located under User Administrative Templates - The policy setting does come with its own caveat - " This policy setting only prevents users from running programs that are started by the File Explorer process. It does not prevent users from running programs, such as Task Manager, which are started by the system process or by other processes. Also, if users have access to the command prompt (Cmd.exe), this policy setting does not prevent them from st...
Read more

Intune: Configure Printers for Non-Administrative Users

-
Image
Configuring printers for end users or giving them the ability to do it themselves is a normal requirement for organizations. Now if your users are Administrators, then the configuration can be straight forward, but in case of Non-Administrators there are additional steps required as Non-Administrators will not be able to add a driver in the driver store despite being able to install a printer. In this blog, I will cover the steps that I took to address this requirement using Intune. The setup involves 2 steps -  1. Setup registries. 2. Install the driver and configure the printer Setting up registries – The registries that need to be configured are actually part of a GPO setting – Allow non-administrators to install drivers for these device setup classes It can be found under: Computer Configuration -> Policies -> Administrative Templates -> System -> Driver Installation I used a Powershell script to set the values and wrapped it in a Win32 application. $P...
Read more