Image may be NSFW.
Clik here to view.Operating System Deployment (OSD) in System Center Configuration Manager 2007 offers several options for deploying images to target systems. One option includes support for imaging systems that are completely disconnected from the network using stand-alone media. You will also see this referred to as using offline media.

Using stand-alone media doesn’t require access to the ConfigMgr infrastructure during imaging because all components needed during the imaging process are copied to the stand-alone media and available locally. This includes the task sequence and any packages or other items referenced by the task sequence. For this reason, stand-alone media can be quite large – often exceeding the space available on a DVD. To avoid swapping DVD’s during imaging with larger stand-alone media based images, it is convenient to use a USB thumb drive. Because of smaller size, easier portability and convenience, USB media is often preferred over DVD’s even when image sizes don’t require DVD spanning. But there are a few requirements for using USB stand-alone media successfully. Let’s walk through the process of creating USB stand-alone media and then go through a few requirements that need to be in place to avoid problems.

To start, ensure the USB flash drive is connected then launch the wizard by selecting task sequences under the OSD node, right-click and choose ‘create task sequence media’.
Image may be NSFW.
Clik here to view.

In the wizard that launches select to create ‘stand-alone media’

Image may be NSFW.
Clik here to view.

On the next screen you have a choice of whether to create a CD/DVD set or a USB flash drive.

NOTE: That the text states USB flash drive. A common question is whether it’s supported to use a USB hard drive rather than a USB flash drive. At present USB hard drives are NOT supported.

Image may be NSFW.
Clik here to view.

Click next and you will get a warning that the USB device will be formatted. Select yes to continue.

Note: The max size for a USB flash drive is 32 GB. If you attempt to use a flash drive larger than this you may see errors. To avoid, create a 32 GB partition on the flash drive and choose that partition in the wizard. More on this later.

The next screen displays a screen allowing a password to be entered for the USB disk.
Image may be NSFW.
Clik here to view.

Next, select the task sequence that is to be deployed with this offline media.

Image may be NSFW.
Clik here to view.

The next screen shows available distribution points. Choose the one that has the content you want to deploy. The bottom window will detail how many of the task sequence packages (but not which ones) are available on the selected distribution point. Note that if the distribution point selected does not have the content you will not complete creation of the offline media successfully.

Image may be NSFW.
Clik here to view.

The next window will allow adding any task sequence variables to the offline media. This is an option selection. For this example I just click next.

Image may be NSFW.
Clik here to view.

The summary screen is displayed, select next and the offline media creation begins. Depending on the size of the image and associated content the offline image creation can take several minutes.

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

The media creation process can be tracked in CreateTSMedia log which is in the AdminUI\AdminUILog folder. A successful media creation will show the following near the end of the log.

Image may be NSFW.
Clik here to view.

If you look at the USB flash drive you will see all of the items that have been loaded. Note that the flash drive is by default formatted as a FAT32 partition.

Image may be NSFW.
Clik here to view.

That is the process when all goes well – but there are times when things don’t work so easy. The following is a list of some known issues and ways to deal with errors encountered.

Problem: Cannot create offline media from an SCCM 2007 Admin console running on a Windows 7 workstation.
Resolution: This is a known issue with three potential workarounds documented at

• http://support.microsoft.com/kb/2471018
• http://blogs.msdn.com/b/steverac/archive/2010/10/11/problems-creating-usb-media-with-windows-7.aspx

Problem: >32 GB USB disk won't work to create TS media.
Resolution: You can create a 32 GB partition on a larger USB drive by using diskpart and the following script. The resulting partition will be formatted with an NTFS partition using the script below. Note: The value # in the script should be replaced with the drive number.

Problem: You see an error in the CreateTSMedia log stating ‘directory name is invalid’.
Resolution: The offline media was being created from content located on a branch distribution point. The problem was due to the users account (in this case an admin on the system) not having permissions to the SMSPXEImages$ share. Adding permissions resolved the problem. This problem can happen with any distribution point if appropriate permissions are not in place.

Problem: An error was noted that the USB disk being used was too small but in reality had plenty of space.
Resolution: The error resulted because not all packages had replicated successfully to the distribution points being used for media creation.

Problem: You run out of disk space while trying to create the offline media.
Resolution: Sufficient disk space is required to stage all the content in the current logged on users %TEMP% directory. If the offline media wizard is run on a server where the C:\ is a small partition to host just the OS, you may run out of space during the media creation without a clear error. Workaround this by changing the %TEMP% variable path to another drive with sufficient space, or leverage a remote console on a workstation with sufficient C: drive space to stage the content.

Problem: The formatted USB flash drive may not have enough space to hold the image.
Resolution: If the USB flash drive is formatted using a FAT32 partition then no file can exceed 4 GB in size (which is common with the WIM). Format the USB Flash stick as NTFS first.

Problem: When running the offline media wizard the attached USB flash drive is not detected.
Resolution: The USB flash drive must be connected prior to launching the wizard.

For more information on using OSD through System Center Configuration Manager 2007 see the following:

http://blogs.technet.com/b/configurationmgr/archive/2009/07/27/a-step-by-step-for-using-osd-through-system-center-configuration-manager-2007.aspx

Steve Rachui | Senior Premier Field Engineer

The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The SCOM 2007 Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis
The Service Manager Team blog: http: http://blogs.technet.com/b/servicemanager
The AVIcode Team blog: http: http://blogs.technet.com/b/avicode
The System Center Essentials Team blog: http: http://blogs.technet.com/b/systemcenteressentials
The Server App-V Team blog: http: http://blogs.technet.com/b/serverappv

Image may be NSFW.
Clik here to view.Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.I recently encountered a question from a customer who wanted to be able to set the computer name, and also be able to have their Desktop Technicians select software to be installed during an Operating System Deployment for their upcoming Windows 7 refresh over Windows XP.  I walk you through the basics step by step to do this with a UDI Task Sequence over on the TechNet Wiki:

http://social.technet.microsoft.com/wiki/contents/articles/configmgr-2007-basic-user-driven-installation-task-sequence-step-by-step.aspx

Clifton Hughes | Support Escalation Engineer

The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The SCOM 2007 Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis
The Service Manager Team blog: http: http://blogs.technet.com/b/servicemanager
The AVIcode Team blog: http: http://blogs.technet.com/b/avicode
The System Center Essentials Team blog: http: http://blogs.technet.com/b/systemcenteressentials
The Server App-V Team blog: http: http://blogs.technet.com/b/serverappv

Image may be NSFW.
Clik here to view.Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

After creating the article ConfigMgr 2007 Basic User Driven Installation Task Sequence Step by Step, I wanted to follow up with another article covering the Application Discovery and Mapping features in a UDI Task Sequence. This cool feature allows you to discover the applications installed on your Windows Clients during deployment of Windows 7, and based on mappings you configure, installs Windows 7 with the new versions, or other applications, that you specified in the UDI Wizard Designer. I walk you through how to implement this here on the TechNet Wiki:

http://social.technet.microsoft.com/wiki/contents/articles/configmgr-2007-application-mapping-with-a-user-driven-installation-task-sequence.aspx

Clifton Hughes | Support Escalation Engineer

The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The SCOM 2007 Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis
The Service Manager Team blog: http: http://blogs.technet.com/b/servicemanager
The AVIcode Team blog: http: http://blogs.technet.com/b/avicode
The System Center Essentials Team blog: http: http://blogs.technet.com/b/systemcenteressentials
The Server App-V Team blog: http: http://blogs.technet.com/b/serverappv

Image may be NSFW.
Clik here to view.Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.Here’s another new KB article we published today.  This one involves the locale setting in Windows 7 when deployed with ConfigMgr 2007:

=====

Symptoms

When deploying a Windows 7 image using System Center Configuration Manager 2007 (ConfigMgr 2007)/ Microsoft Deployment Toolkit 2010 (MDT 2010), if the default system Locale setting is changed, the localename (e.g. sv-SE) is set correctly but the locale code in the Registry remains set to 00000409 (en-US). As a result, some applications will display incorrect characters or languages. For example, the Page Setup in MSPaint is still set to U.S. (inches) instead of Metric (millimeters).

Cause

In Windows 7, in RUNAS/Impersonation scenarios such as an OS Deployment (OSD) by System Center Configuration Manager 2007 where one runs as local system, the LocaleName and Locale registry values are not in sync.

Resolution

To resolve this issue, add an extra step to the System Center Configuration Manager Task Sequence to change the Locale value of the Default User profile (ntuser.dat). This value is located in the following key:

HKEY_USERS\ntuser.dat\Control Panel\International

Example:
======
reg load HKU\ntuser.dat c:\users\default\ntuser.dat
reg import locale.reg
reg unload HKU\ntuser.dat

locale.reg
=======
Windows Registry Editor Version 5.00

[HKEY_USERS\ntuser.dat\Control Panel\International]
“Locale”=”0000041D”

=====

For the most current version of this article please see the following:

2625165: An incorrect Windows 7 Locale setting is configured after OS Deployment with Configuration Manager 2007

J.C. Hornbeck| System Center Knowledge Engineer

App-V Team blog: http://blogs.technet.com/appv/
AVIcode Team blog: http://blogs.technet.com/b/avicode
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
OOB Support Team blog: http://blogs.technet.com/oob/
Opalis Team blog: http://blogs.technet.com/opalis
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/
SCMDM Support Team blog: http://blogs.technet.com/mdm/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

Image may be NSFW.
Clik here to view.Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.Hi everyone, David Smith here.  I’m a Senior Support Engineer here on the ConfigMgr team and I recently came across an interesting issue that I thought might be worth a mention here on our blog.  In this case, an Operating System Deployment (OSD) using System Center Configuration Manager 2007 SP2 would fail and in the loadstate.log file we would see the following:

2011-12-13 13:40:19, Error [0x080000] There was an error while calling CreateProfile. Error: 0x800700B7
2011-12-13 13:40:19, Error [0x000000] Error 0 creating profile for user domain\user1 (source user domain\user1)
2011-12-13 13:40:19, Info [0x000000] Failed.[gle=0x00000006]
2011-12-13 13:40:19, Info [0x000000] A Windows Win32 API error occurred
Windows error 0 description: The operation completed successfully.[gle=0x00000006]
2011-12-13 13:40:19, Info [0x000000] USMT Completed at 2011/12/13:13:40:19.782[gle=0x00000057]

NOTE In your log you will see an actual User ID. 

The issue would happen in a refresh scenario where, for example, you might be migrating from Windows XP to Windows 7 and repurposing the old hardware.  It should also happen in all version of ConfigMgr 2007, not just SP2.

After doing a little troubleshooting we found that the WIM image contained a partial user profile named domain\user1, meaning that the reference computer had been joined to the domain and user1 had logged onto the machine.  In this situation, when we refreshed the computer of domain\user1 it would fail with the above error but when we refreshed the computer of domain\user2 it would succeed.

To fix this issue, we rebuilt the reference computer ensuring that no partial user profiles existed, and then captured it again creating a new WIM image.  Once we did this everything worked as expected.

To ensure that no profiles exist you should clean out all profiles through the control panel and then remove whatever is left in the registry key below:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

Hope this helps!

David Smith | Senior Support Engineer

Get the latest System Center news onFacebookandTwitter:

Image may be NSFW.
Clik here to view.Image may be NSFW.
Clik here to view.

App-V Team blog: http://blogs.technet.com/appv/
AVIcode Team blog: http://blogs.technet.com/b/avicode
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
OOB Support Team blog: http://blogs.technet.com/oob/
Opalis Team blog: http://blogs.technet.com/opalis
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/
SCMDM Support Team blog: http://blogs.technet.com/mdm/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.Here’s a new Knowledge Base article we published this morning. This one discusses an issue where the partition name is set to the ID of the user who created it when using prestaged media in System Center Configuration Manager 2007.

=====

Symptoms

When creating and deploying prestaged media using System Center Configuration Manager 2007, when the WIM comes back from the OEM on a new target machine the label of the C: drive on the target machine is set to the ID of the user that created the media.

NOTE See the following for more information about prestaged media: http://blogs.technet.com/b/configurationmgr/archive/2011/01/11/how-to-stage-task-sequence-prestaged-media-on-a-hard-drive-in-configuration-manager-2007.aspx

Cause

This occurs because the media creation process manipulates the label of the C: drive by editing the label attribute in AutoRun.INF.

Resolution

Follow these steps to modify AutoRun.INF (which is inside the WIM) and remove the label attribute:

1. Run imagex.exe to mount the WIM (for example: WIM is e:\osd2\image3.wim):

C:
Cd\
Md mount
Cd\program files\windows aik\tools\x86
Imagex.exe /mountrw 1 e:\osd2\image3.wim c:\mount

2. Edit AutoRun.INF removing the lines containing Label= and Icon=:

Notepad c:\mount\autorun.inf

3. Run imagex.exe to unmount the WIM (make sure to exit out of c:\mount or a File in Use error may occur):

Imagex.exe /unmount /commit c:\mount

4. Update the WIM image on all Distribution Points with a new package source version.

5. Continue following the standard steps to create and deploy prestaged media per the article listed below in the More Information section.

More Information

How to stage Task Sequence Prestaged Media on a hard drive in Configuration Manager 2007 : http://blogs.technet.com/b/configurationmgr/archive/2011/01/11/how-to-stage-task-sequence-prestaged-media-on-a-hard-drive-in-configuration-manager-2007.aspx.

=====

For the most current version of this article please see the following:

2702735 - When using prestaged media in Configuration Manager 2007, the partition name is set to the ID of the user who created it

J.C. Hornbeck| System Center & Security Knowledge Engineer

Get the latest System Center news onFacebookandTwitter:

Image may be NSFW.
Clik here to view.Image may be NSFW.
Clik here to view.

App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Image may be NSFW.
Clik here to view.

When the Configuration Manager client is installed on, or uninstalled from, a server that’s running a multicast distribution point (DP), the IUSR account permission is removed from CCM/SMS_CCM folder. This causes multicast to stop working. Additionally, you may receive the following error message:

Call to HttpSendRequestSync failed for port 80 with status code 401, text: Unauthorized” in mcsmgr.log

Note that this issue affects Configuration Manager 2012, Configuration Manager 2012 R2 and Configuration Manager Current Branch. For complete details please see the following:

3205795 – No IUSR account access after you install the Configuration Manager client on a server that’s running a multicast DP (https://support.microsoft.com/en-us/kb/3205795)

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

ConfigMgr 2012 R2

When you try to create a configuration item for a mobile device in Microsoft System Center Configuration Manager current branch, you may encounter a System.InvalidOperationException error. This issue can occur if the user who is assigned a custom security role does not have the proper permissions for the Custom Configuration Setting role.

We published a new KB article that discusses this issue and you can get all the details as well as a resolution here:

3205796 – “System.InvalidOperationException” error when you create a configuration item for a mobile device (https://support.microsoft.com/en-us/kb/3205796)

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

A new update is available for the Asset Intelligence (AI) authentication certificate in Microsoft System Center Configuration Manager 2007 Service Pack 2, System Center 2012 Configuration Manager Service Pack 2, System Center 2012 R2 Configuration Manager Service Pack 1, and the current branch of System Center Configuration Manager versions 1606 and earlier. Note that System Center Configuration Manager current branch version 1610 and later versions are pre-provisioned with this version of the Asset Intelligence (AI) authentication certificate so you do not have to apply this update to those versions.

For all the details please see the following:

3207852 – Update for authentication certificate in System Center Configuration Manager Asset Intelligence is available (https://support.microsoft.com/en-us/kb/3207852)

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

ConfigMgr 2007 SP2 ConfigMgr 2012 R2 SP2 ConfigMgr 1511 ConfigMgr 1602 ConfigMgr CB

As you’re probably already aware, in October we announced a new simplified servicing model, where on the 2ndTuesday of each month you will see a new Security Monthly Quality Rollup as well as a new Security Only Quality Update. Because the Security Monthly Quality Rollup contains the same security fixes as the Security Only Quality Update, as well as all fixes from previous monthly rollups and Security Only Quality Updates, there is a supersedence relationship between these updates, and this relationship was described in this post.

However, please note that for December, the Monthly Rollup will not supersede the Security Only update of the same month, nor will it supersede the Security Only update of previous months. Customers using Configuration Manager 2007 will see both updates available to them for deployment (as seen in October), and can deploy the update of their choice using the Software Update Management functionality. In the absence of supersedence, the December Security Only update has installation applicability logic to not install if the Monthly Rollup is installed. This alleviates the impact Monthly Rollup customers observed in October, when the Security Only update would still be installable and show as missing or required in certain compliance tools. Now, customers of the December Monthly Rollup will not see the December Security Only update as missing or required.

Also, with the release of the December updates on Patch Tuesday (12/13), we also revised the following updates:

• The November Security Only Quality Update
• The November Security Monthly Quality Rollup
• The October Security Only Quality Update.

These updates have been rereleased to leverage the same new logic as in the December updates, without supersedence between the Monthly Rollups and the Security Only updates. With this rerelease, customers who have yet to deploy an earlier Security Only update will gain the benefit of it not being superseded.  Additionally, customers of the Monthly Rollups will continue to benefit from the Security Only updates not being installable or flagged as missing.

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

Administrators who opted in to the early wave deployment for System Center Configuration Manager current branch, version 1610, have an update available in the Updates and Servicing node of the Configuration Manager console. This update, made available on December 12, 2016, addresses important late-breaking issues that were discovered during the final release process for version 1610. This update does not apply to sites that update or install a copy of version 1610 that was downloaded before December 1, 2016.

For more information, including the issues fixed, please see the following:

3211925 – Update 2 for System Center Configuration Manager version 1610, early wave (https://support.microsoft.com/en-us/kb/3211925)

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

ConfigMgr 1610

Consider the following scenario:

• You’re running Configuration Manager current branch, version 1511 through 1606, or version 1610 LTSB.
• Your old primary site was being used for client piloting.
• You perform site expansion.

In this scenario, the Configuration Manager Client Piloting Package fails. When this occurs, you receive a status message stating that Distribution Manager failed to access the source directory for Configuration Manager Client Piloting Package content. Additionally, the Distmgr.log file contains errors indicating that Distribution Manager cannot locate the source for PilotUpgrade and cannot process the snapshot of the package.

We have a new KB article that describes this issue as well as how to work around it. For more information please see the following:

3205797 – Client piloting package fails after site expansion in Configuration Manager (https://support.microsoft.com/en-us/kb/3205797)

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

We are happy to announce that that update 1612 for the Technical Preview Branch of Microsoft System Center Configuration Manager has been released. Technical Preview Branch releases give you an opportunity to try out new Configuration Manager features in a test environment before they are made generally available. For information on this month’s new preview features, please see the following:

Update 1612 for Configuration Manager Technical Preview Branch – Available Now!

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

Version 1610 of System Center Configuration Manager Current Branch (ConfigMgr 1610) contains many changes that are intended to prevent issues and improve features. A list of these changes and fixes is available in the KB article below, Keep in mind that this list is not comprehensive, however it does include the items that the product development team believes are the most relevant to most customers. Many of these changes are in response to customer feedback about product issues and ideas for product improvement. For more information regarding what’s been fixed and/or updated, please see the following:

3213269 – Summary of changes in System Center Configuration Manager current branch, version 1610 (https://support.microsoft.com/en-us/kb/3213269)

Please note that version 1610 is available as an in-console update to be installed at the top-most site in a hierarchy. For more information on installing the 1610 update, see Checklist for installing update 1610 for System Center Configuration Manager.

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

After you install the Convenience rollup update for Windows 7 SP1 and Windows Server 2008 R2 SP1 (3125574) and the System Center Configuration Manager client, the Software Metering Agent fails, and the following error message is recorded in the mtrmgr.log file:

Software Metering failed to start PrepDriver

This error can occur if you install rollup 3125574 before you install the System Center Configuration Manager client software. In that scenario, PrepDrv is not installed during the System Center Configuration Manager client setup process.

For a couple options on how to resolve this issue, please see the following:

3213242 – Software Metering Agent fails with “Software Metering failed to start PrepDriver” in mtrmgr.log (https://support.microsoft.com/en-us/kb/3213242)

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group