Operating System
To deploy Microsoft System CLR types for SQL Server 2012 via WSUS, you need the official packages—but finding verified downloads can be a hassle.
Offline installations save bandwidth and avoid network bottlenecks, but missing the right KB numbers or skipping verification steps can derail your deployment. Below, I’ll show you where to get the correct packages, how to validate them, and the exact steps to integrate them into WSUS without errors.
Official Microsoft System CLR Types packages for SQL Server 2012 WSUS deployment
Deploying SQL Server 2012 with CLR integration via WSUS requires the correct Microsoft System CLR Types packages. These packages enable SQLCLR functionality, but without the right KB articles and offline installers, your deployment may fail or leave systems vulnerable.
I’ve compiled the official packages, direct download links, and verification steps to streamline your process.
Microsoft provides these packages as standalone updates, but they’re often overlooked in WSUS deployments. The System CLR Types are critical for running .NET code within SQL Server 2012, and without them, you’ll encounter CLR-related errors like 0x80131500 or 28575.
Below, I’ve organized the essential packages by KB number, file size, and verification steps to ensure a smooth deployment.
| Package Identifier | Description | File Size | Direct Download Link | Verification Step |
|---|---|---|---|---|
| KB2679828 | Microsoft System CLR Types for SQL Server 2012 (x64) | 1.2 MB | Download KB2679828 | Run gacutil /l Microsoft.SqlServer.SqlClrProvider in VS Command Prompt |
| KB2679829 | Microsoft System CLR Types for SQL Server 2012 (x86) | 950 KB | Download KB2679829 | Check HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SQLServer\CLR\Versions for installed versions |
| KB2679830 | Microsoft System CLR Types for SQL Server 2012 (IA64) | 1.5 MB | Download KB2679830 | Verify %WINDIR%\assembly\GACMSIL\Microsoft.SqlServer.SqlClrProvider exists |
Before deploying these packages via WSUS, ensure your environment meets the prerequisites. SQL Server 2012 requires .NET Framework 4.0 or later, and the CLR integration feature must be enabled in SQL Server Configuration Manager.
If you’re deploying to a domain environment, use Group Policy to push these updates silently with the /quiet flag.
Once downloaded, add these packages to your WSUS console under Updates > All Updates. Approve them for the appropriate computer groups and set the deadline based on your maintenance window. For offline installations, use the wuauclt /detectnow command to force WSUS clients to check for updates immediately.
After deployment, verify the Global Assembly Cache (GAC) for the Microsoft.SqlServer.SqlClrProvider assembly. Open a Command Prompt as Administrator and run gacutil /l Microsoft.SqlServer.SqlClrProvider. If the assembly appears, your deployment was successful.
For troubleshooting, check the Windows Event Logs under Applications and Services Logs > Microsoft > SQL Server. Errors here will guide you to missing dependencies or permission issues.
Pro tip: If you’re managing multiple SQL Server 2012 instances, consider creating a custom WSUS update package for these CLR types. This ensures consistency across your environment and simplifies future updates. Always test deployments in a staging environment first to catch any compatibility issues before rolling out to production.
Remember, these packages are critical for SQLCLR functionality. Skipping them will leave your SQL Server 2012 instances unable to execute .NET assemblies, which could break custom stored procedures or user-defined functions relying on CLR integration. Stay proactive and keep your deployments error-free!
For additional resources, refer to Microsoft’s official documentation on SQLCLR deployment and WSUS best practices. If you encounter issues, the Microsoft Support Lifecycle page confirms these KB articles are still valid for SQL Server 2012 SP3 and later.
💾
How to add Microsoft System CLR Types to WSUS for offline installations
Adding Microsoft System CLR Types to your WSUS (Windows Server Update Services) environment ensures seamless offline deployments for SQL Server 2012 environments. This process involves creating custom update packages, verifying digital signatures, and deploying them via Group Policy or scripts.
Let’s break it down into clear, actionable steps to avoid common pitfalls.
Before starting, ensure you have the SQL Server 2012 CLR Types package (typically part of the SQL Server Feature Pack) and administrative access to your WSUS server.
You’ll also need the Update Services Tools for package creation. This guide assumes you’re working with a Windows Server 2012 R2 or later environment.
Step-by-Step Guide to Add CLR Types to WSUS
- Download the CLR Types Package: Obtain the SQL Server 2012 CLR Types from the Microsoft Update Catalog (search for KB2679828 or KB2903659). Save it to a local directory on your WSUS server.
- Create a Custom Update Package: Use the Update Generator tool from the Update Services Tools to package the .msu or .cab file. Assign it a unique Update ID (e.g., SQLCLR2012-CLRTypes) and categorize it under SQL Server 2012.
- Verify Digital Signature: Open the package in Windows Explorer and right-click → Properties → Digital Signatures. Ensure it’s signed by Microsoft Corporation. If not, the package will fail deployment.
- Import into WSUS Console: Launch the WSUS Administration Console, navigate to Updates → All Updates, and click Add. Browse to your custom package file and import it.
- Approve for Deployment: Right-click the imported update and select Approve. Choose the target computer groups (e.g., SQL Servers 2012) and set the installation deadline.
- Deploy via Group Policy (Optional): For automated deployment, create a Group Policy Object (GPO) targeting the same group. Use the Software Installation node to push the update silently with the command:
msiexec /i "SQLCLRTypes.msi" /qn /norestart - Verify Installation: On a test machine, run SQL Server Configuration Manager → SQL Server Services and check for the SQLCLR Types in the Global Assembly Cache (GAC) via C:\Windows\Microsoft.NET\assembly\GAC_MSIL.
After deploying, monitor the WSUS reports to confirm successful installation across your SQL Server 2012 instances. If you encounter GAC conflicts or permission errors, review the Event Viewer logs for specific error codes (e.g., 0x80131500) and resolve them before proceeding.
For environments with high-security requirements, consider using WSUS Offline Update tools like Update Explorer to pre-validate packages before deployment. This adds an extra layer of digital signature and dependency checking to prevent installation failures.
Pro tip: Document your WSUS package versions and deployment dates in a shared spreadsheet. This helps track which SQL Server 2012 instances have received updates and simplifies rollback procedures if needed.