If you ever work with Operating System Deployment (OSD) in Microsoft’s System Center Configuration Manager (SCCM / ConfigMgr) 2007, you might build a task sequence that only performs an OS image capture (as opposed to an OS build & capture). You might think — logically — that you only need a single task sequence step to perform this action: a “Capture Operating System Image” step. Unfortunately, this isn’t the case. If you attempt to run a task sequence like this, you’ll probably receive a 0x80070490 error code, which means “element not found.”
In the interest of security, some organizations provide administrative IT users with separate user accounts for administrative tasks. While this improves security, it often complicates day-to-day administrative tasks by requiring additional logins to various programs or remote systems. If you are a Microsoft System Center Configuration Manager administrator who is running the console on your … Read moreConfigMgr: Start the Console as a Different User
When you upgrade your boot images in Microsoft’s System Center Configuration Manager (SCCM / ConfigMgr) 2007 from WinPE 3.0 to WinPE 3.1, you must run the ExportDefaultBootImage() WMI method on the SMS_BootImagePackage WMI class for each boot image architecture. Typically this would simply include x86 (32-bit) and x64 (64-bit) boot images (Windows Image Format (WIM) … Read morePowerShell: Update your ConfigMgr OSD Boot Images to WinPE 3.1
Recently, someone posted a PowerShell script, which is intended as a replacement for the SendSched.vbs included in the Microsoft System Center Configuration Manager 2007 Toolkit v2. I took the liberty of cleaning the code up a little bit, and simplifying it to be more PowerShell friendly. Enjoy. # # Script Name: SendSched_PowerShell_Version.ps1 # Purpose: Serves … Read morePowerShell / ConfigMgr: Sendsched.vbs Replacement
If you’re using System Center Configuration Manager (SCCM / ConfigMgr) 2007, you may want to discover how many SCCM sites you have from Active Directory. Of course, this assumes that you have Active Directory publishing enabled on your primary sites. When enabled, SCCM automatically places site information underneath the CN=System Management,CN=System,DN=mydomain,DC=com container.
Recently, I was working with Desired Configuration Management (DCM) in System Center Configuration Manager (SCCM / ConfigMgr) 2007 SP2 R3. During the development of configuration items (CIs) and baselines, it’s common to have to trigger baseline evaluations to ensure that the validation rules you’re writing are correct.
I needed to get a report of server systems that are missing the VMware Tools installation. This is pretty easy to do with a subselect query in Microsoft’s System Center Configuration Manager (SCCM / ConfigMgr). Here is the query I put together for this purpose: select [sys].[AD_Site_Name0] , [sys].[Name0] , [cs].[Manufacturer0] from … Read moreConfigMgr: Report of VMware Guests Missing VMTools
In this situation, I’m working with a System Center Configuration Manager 2007 Service Pack 2 R3 central + child primary site configuration. Both sites have local databases, and all SCCM components (eg. management point, provider, distribution point, etc.) are local. SCCM clients are a combination of Windows Server 2003, 2008, and 2008 R2.
Recently on the child primary site, I started getting a bunch of MIF processing errors in the INVENTORY_DATA_LOADER component on a primary site. I had recently made some very minor edits to sms_def.mof, by enabling a few additional properties for reporting – I didn’t add anything new or custom to my sms_def.mof or configuration.mof, so I was a bit surprised to be running into issues.
Recently, I had the need to remove software updates from Windows servers in order to test out patching functionality in System Center Configuration Manager (SCCM / ConfigMgr). Since we’re currently deploying full patched operating system (OS) images, we didn’t really have any machines to test deploying software updates with. We’re currently working with non-production servers, so removing software updates for a few minutes and reinstalling them isn’t a big deal. I figured the easiest thing to do would be to simply remove any and all updates that could be removed (some can’t be uninstalled), so naturally, I wrote a script to handle this.
I was getting the following messages in my ccmsetup.log files when trying to do a client push installation to about 50 servers. The servers were a combination of Windows Server 2003, 2008, and 2008 R2.
The HTTP 500 error message seen in the second line indicates an “internal server error” within IIS on the ConfigMgr management point. Based on that, I knew that there must have been some sort of misconfiguration on the IIS server.