During the installation of Microsoft SQL Server, you have two choices regarding the account used to start the “SQL Server” service:
- Local System of the computer.
- Service account, user account, created in Active Directory.
Microsoft recommends to use the service account instead of local system. However, when using service account, you can have this error in SQL Logs:
The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos
When Microsoft release a new Cumulative Update for ConfigMgr 2012, the SCCM Agent is updated too with a new version. To fix some bugs and improvements, you need to deploy it on all your clients.
To do this, you can choose two solutions:
- Use the CAB file in the folder [SCCMInstall]\hotfix\KB\SCUP and deploy it with SCUP, that means you are using Software Updates.
- Deploy the new version with two packages, one for x86 and one for x64, included in the Cumulative Update. With this solution, you can easily update your client with no technical requisite.
We will see how to update clients with the second solution, using package.
During the migration phase of SCCM 2007 clients to SCCM 2012 infrastructure, I had an issue with the Software Update Point: a lot of computers not reported their Software Update compliance and didn’t evaluated any new software updates.
After a troubleshooting, in the WUAhandler.log on client side, there was this error:
OnSearchComplete - Failed to end search job. Error = 0x80244022.
Scan failed with error = 0x80244022.
Welcome on the new version of my personal blog!
I will write some posts about System technologies. Almost all on Microsoft solutions but maybe, sometimes, another editor. Don’t be closed, we always need storage and network to work. 🙂
Main topics are System Center products, Exchange and all built-in services with Windows Server. I hope that installation guides, troubleshooting and more will help you.
See you soon. 😉
Alexandre Continue reading