SQL Server – WMI Provider Error

Was changing the SQL Server Service Account on an SCCM SQL Server 2012 to a dedicated Service Account instead of Local System (recommended best practices).

Went to the SQL Server Error Log text file to get some more context on the error as SQL Server hadn’t started because of the error.

Here what I found:

Solution:

Full Control on the following objects to the service account:

C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\
C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys
HKLM\System\CurrentControlSet\Services\WinSock2\Parameters

Installing SCCM Client in a Untrusted Domain

Background:

SCCM Server in my datacenter is corrupt.

Migrating my clients to a new SCCM Management Server.

These servers are in a WORKGROUP domain. There is no trust between this WORKGROUP domain and the SCCM server/domain.

Pre-Reqs:

Firewall Ports open between clients and Management Point.

Protocol	Port
TCP	80, 443, 3268, 10123, 8530, 8531, 2701, 3389
UDP	67, 68, 69, 4011

1. Copy the SCCM Client package from the Management Point to each server.
2. Open a Command Prompt as an Administrator and run the following command:

ccmsetup.exe /mp:<management FQDN> /SMSSITECODE:<SiteCode> SMSMP:<ManagementPoint> DNSSUFFIX:<FQDN>

Eg:

ccmsetup.exe /mp:sccmmp.dev.1giantnerd /SMSSITECODE:DEV SMSMP:sccmmp.dev.1giantnerd DNSSUFFIX:dev.1giantnerd

June 2020 – Patching Issues – Print Spooler Errors

Update 18-Jun-20:
Microsoft have an Out of Cycle hotfix for the below Print Spooler issues. See link below for more details.

NP – this update is not available through WSUS Catalog. Need to download manually.

https://support.microsoft.com/en-us/help/4567512/windows-10-update-kb4567512

———————————

The June 2020 patches came out last week, and with that a fresh issue.

Below is the excerpt from the Microsoft known issues page:

Print spooler might error or close unexpectedly when attempting to print

After installing KB4560960, certain printers may be unable to print. Print Spooler may error or close unexpectedly when attempting to print and no output will come from affected printer. You might also encounter issues with the apps you are attempting to print from. You might receive an error from the app or the app may close unexpectedly. Note This issue might also affect software-based printers, for example printing to PDF.

Affected platforms:

• Client: Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1607; Windows 10 Enterprise LTSC 2015; Windows 8.1
• Server: Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2012 R2; Windows Server 2012

The current fix is to uninstall KB4560960. Microsoft are currently working on a solution.

Reference – https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-2004#436msgdesc

SCCM – SQL Server Collation PreRequisites

Installing System Center Configuration Manger (SCCM) into my HomeLab environment to ensure that my Windows Servers are patched up to date.

During the SCCM installation, the prerequisite failed due to the wrong SQL Server Collation.

Screenshot #1 shows the failure. Because the prerequisite failed, you will noticed that the Begin Install button is greyed out.

Screenshot #1 – SCCM SQL Collation Issue

SQL Collation needs to be SQL_Latin1_General_CP1_CI_AS.

Mine was set to Latin1_General_CI_AS_KS as seen in Screenshot #2.

Screenshot #2 – SCCM SQL Collation Issue

Solution:

Change the SQL Server Collation via a rebuild.

Prerequsities:

1. The sa account within SQL Server is enabled and password is known;
2. Member of SysAdmins group within SQL Server.

Screenshot #3 – SCCM SQL Collation Issue

1. Open Command Prompt as an Administrator;
2. Navigate to setup.exe where your binaries are installed;
3. Run the following command:
   .\Setup.exe /q /action=rebuilddatabase /instancename=MSSQLServer /sapwd=Password1 /SQLCollation=SQL_Latin1_General_CP1_CI_AS /SQLSYSADMINACCOUNTS=DEV\user1
4. This will change the collation to SQL_Latin1_General_CP1_CI_AS.

Screenshot #4 – SCCM SQL Collation Issue