Recently encountered a SQL issue when trying to open the SQL Server Configuration Manager on my ConfigMgr Database server. This KB was the resolution for me: http://support.microsoft.com/kb/956013
I received the following error when attempting to open the tool.
Cannot connect to WMI provider. You do not have permission or the server is unreachable. Note that you can only manage SQL Server 2005 and later servers with SQL Server Configuration Manager.
Invalid namespace [0x8004100e]
My SQL Server install was SQL Server 2012 SP1.
Running the mofcomp of sqlmgmproviderxpsp2up.mof resolved the issue for me after a restart of the WMI service.
If you are working with Windows 8.1 and ConfigMgr/MDT, you may run into the Windows Wireless screen prompting you to connect to a wireless network in the middle of your deployment.
It’s a relatively easy fix, you need to modify your unattend.xml and add the following 3 sections.
Add the following section to the Unattend:
Enable the following sections for True:
Lee Berg is a good friend of mine and has been developing quite an impressive YouTube channel lately. I did an interview with him this week and you can find that linked below. We talk about ConfigMgr, Wisconsin weather (we both live in WI) and other things.
Windows 8.1 is an interesting thing. It’s kind of a love/hate relationship most days
One thing that was really bugging me was the internet search results when searching in the Metro interface. Here’s how to disable that "feature".
Bring up the charms menu (Windows Key + C) or swipe in from the right.
Click on Change PC Settings.
Select Search and Apps
Turn Use Bing to Search Online off.
Recently had an issue at a client site where we wanted to query for all user accounts with "_a" at the end of the account. Attempting to query for this didn’t work as we were getting back accounts that just ended with "a". The Like statement was "%_a".
Turns out you need to put brackets around the underscore as it’s a special character. So the proper query was "%[_]a".
Recently had an issue at a client site where we suddenly couldn’t import drivers, manually or via a PowerShell script.
When importing manually, we were seeing the following error:
"An error occurred while importing the selected driver"
When importing via the script, we were seeing:
"Unexpected error, skipping INF : CSspConfigurationItem: SQL_ERROR 3242722562"
After some creative searching, I can across this KB article:
After moving the System Center 2012 Configuration Manager SQL Site Database to another drive, creating a new Software Update package or a new application fails.
Well as it turns out, I had just moved around the DB and Log files for this client to new drives.
I used the following commands to alter the DB, verify the Isolation level, and then finally change the DB owner back to SA.
CM_XXX = ConfigMgr DB Name
ALTER DATABASE CM_XXX SET TRUSTWORTHY ON
Verify that Isolation level is "READ COMMITTED SNAPSHOT"
Exec sp_changedbowner ‘SA’
After completing those steps, I was able to import drivers again.
Free e-book from Microsoft Press, download at the link below and description below as well.
As the authors of this book, we have tried provide you with insights and tips on troubleshooting System Center 2012 Configuration Manager drawn from our insider knowledge and real-world field experience. While most of you who are Configuration Manager administrators are fairly comfortable with the product and can perform common management tasks, many of you still have pain points when it comes to certain aspects of how the product works. Based on our observations and interactions with customers, the biggest knowledge gaps tend to be in the following areas:
- Troubleshooting common Configuration Manager tasks such as software distribution, software updates, and deployment.
- Understanding how the various components of Configuration Manager on both the server and client side work together when such tasks are performed.
- Dealing with the enormous number of log files that are generated on both the server and client side of Configuration Manager.
This book is our attempt to address some of these gaps and pain points. Chapter 1 provides insights into the Configuration Manager architecture and deployment principles. Chapter 2 familiarizes you with some of the key components of Configuration Manager and how they interact with each other when performing common tasks by using verbose logging for tracing the actions of various components. And Chapter 3 examines how to troubleshoot various Configuration Manager functionality including software and application deployment, site-to-site replication, software update and patching, operating system deployment, and Mac client issues.
An update is available for the "Operating System Deployment" feature of System Center 2012 R2 Configuration Manager
This update resolves the following issues in Microsoft System Center 2012 R2 Configuration Manager.
After you enable the PXE Service Point role on an instance of a specific distribution point, or you select the Deploy this boot image from the PXE-enabled distribution point property of a boot image, the Windows Deployment Service (WDS) stops running. Additionally, entries that resemble the following are logged in the Windows Application log:
When operating system image files are downloaded to Configuration Manager 2012 R2 clients, you may find that the download takes longer than it did in previous versions of Configuration Manager 2012 clients. You may see this behavior when the target client is running Windows PE or a full Windows operating system.
This update applies to Central Administration sites, primary sites, administrator consoles, and clients. Applying this update to a site server will let you create client update packages.
After the update is installed on site servers, any operating system boot images should be updated. To update boot images after the hotfix is applied, follow these steps:
- In the Configuration Manager console, click Software Library.
- In the Software Library workspace, expand Operating Systems, and then click Boot Images.
- Select the boot image that you want to update.
- Right-click and then select the Update Distribution Points action.
Note This action updates all distribution points and may have an adverse effect on an environment that contains many distribution points.
- Repeat steps 3 and 4 for all boot images that have previously been distributed.
- All existing media (such as stand-alone, boot, or prestaged) that use existing boot images (default or custom) will have to be re-created.
- To fully fix the problem in Issue 2, the client side .msp file has to be installed during the "Setup Windows and ConfigMgr task by using the PATCH= command.
- For more information about how to update boot images, see the How to Manage Boot Images in Configuration Manager topic on the Microsoft TechNet website.