Last week I implemented one of the new features of SCCM 2012 SP1. With SCCM 2012 SP1 it’s possible to use an existing WSUS upstream server for the local Software Update Point(SUP) in your environment. The SUP do not have any connection with the Internet. Based on my research I expected that it would work differently than it did.
SCCM 2012
SCCM 2012: Task Sequence fails to install Software Updates and Applications
StandardToday I ran into an issue that software updates and applications failed to install during a task sequence (TS). This only was applicable to ‘known’ agents. Unknown agents or agents which are receiving the task sequence for the first time doesn’t have the problems.
SCCM 2012: Hardware Inventory errors on VDI Environment
StandardLast couple of weeks I investigated an issue with hardware inventory errors on a Stateless pooled VDI environment. After deploying the Master to a number of desktops everything looks OK in the SCCM console. No conflicting records and all the desktops shows an active client. But after some time we noticed that the BADMIFS folder was growing. Looking into the dataldr.log log file we saw the following warnings:
Continue reading
SCCM 2012 and SCOM 2012: Patching and Maintenance Mode
StandardWhen System Center Configuration Manager is used for patching and System Center Operations Manager is used for monitoring you may have some difficulties with alerts during a patch window. The standard option ‘Disable Operations Manager Alerts while software updates run’ in SCCM does not solve all your alerting problems. This option is improved from 2007 to 2012, but you will receive alerts from the reboots after installing the updates. Continue reading
SCCM 2012: Add FQDN of host as TS variable
StandardYesterday I created a small powershell script which adds the FQDN of a host as a Task Sequence variable to a SCCM task sequence. See below the script: Continue reading
Hiding the task sequence progress dialog box
StandardLast week I had a script which generated popup during my task sequence. This popup was visible behind the task sequence progress window. I searched for a solution to hide the task sequence progress window and found a post from Michael Niehaus on the TechNet blogs. The link to the original post is:
Upgraded ConfigMgr 2012 SP1 Beta to ConfigMgr 2012 SP1 RTM
StandardYesterday it toke me 30 minutes to upgrade my current Configmgr 2012 lab environment from SP1 beta to SP1 RTM. From Microsoft perspective it’s a unsupported way of upgrading but in my case the upgrade process was very easy and completed without any problems.
The Beta version number was 5.0.7782.1000:
System Center SP1 RTM available for download
StandardToday Microsoft made System Center SP1 available on the Technet and MSDN websites. If you have a login for one of those websites you can download the SP1 RTM bits. SP1 give all System Center products support for Windows Server 2012 and Windows 8. For more information about what’s new please follow the links below:
Caution: KB2506143 and KB2506146 possible issues with ConfigMgr 2012
StandardLast week Microsoft released the updates KB2506143 and KB2506146 through Windows Update. Caution with installing these updates when using Configuration Manager 2012. After installing this update you could end up with broken clients and/or servers. The client health check on clients will show the following error in the console:
Cumulative Update 2 now available for System Center 2012 Configuration Manager
StandardYesterday Microsoft released cumulative update 2 for ConfigMgr 2012. Cumulative Update 2 includes the updates from CU1 and some new updates. One important bug where I recently blogged about ‘When dynamic media is used to deploy an operating system to a computer that was imported into the database together with a computer name, the correct name is not applied. Instead, the computer is named “MININT-xxxxx.”‘ is fixed through CU2.