Here’s some info on a hotfix we just released. The issue you might see is that at primary site servers in a site hierarchy, Discovery Data Manager (DDM) spends significant time rebuilding network configuration data files (.ncf files) for other primary sites and their child sites when ConfigMgr 2012 starts. The rebuilding of the .ncf files occurs even when there are no boundary changes that were made since the last time DDM built the .ncf files. This blocks other DDM processing. In most hierarchies, the NCF rebuild operation is quick enough that the work is insignificant. However, when there are many boundaries that are configured for one or more sites, DDM throughput can be affected.

For additional details and a link to a hotfix that resolves this issue please see the following:

KB2931044 - Discovery Data Manager slows when it rebuilds .ncf files on startup in System Center 2012 Configuration Manager Service Pack 1 (http://support.microsoft.com/kb/2931044)

J.C. Hornbeck| Solution Asset PM | Microsoft GBS Management and Security Division

Get the latest System Center news onFacebookandTwitter:

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

The Forefront Endpoint Protection 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/

~ Winds Wu

Here’s an FYI on an issue we ran into recently that you might want to be aware of. When using Microsoft Deployment Toolkit (MDT) 2013 integrated with System Center 2012 R2 Configuration Manager (ConfigMgr R2) and deploying Windows 7, the Task Sequence may continuously fail to download the MDT tools during the post install/state restore phase.

You will also see the following in the smsts.log at the time:

WinHttpSendRequest (hRequest, pszAdditionalHeader != NULL ? pszAdditionalHeader : WINHTTP_NO_ADDITIONAL_HEADERS, (DWORD)-1, NULL, 0, 0, NULL), HRESULT=80072ee2 (e:\nts_sccm_release\sms\framework\tscore\downloadcontent.cpp,1193) InstallSoftware 10/02/2014 05:15:53 2332 (0x091C)
WinHttpSendRequest failed. InstallSoftware 10/02/2014 05:15:53 2332 (0x091C)
SendWinHttpRequest failed. 80072ee2. InstallSoftware 10/02/2014 05:15:53 2332 (0x091C)
SendWinHttpRequest (hSession, hConnect, hRequest, pszSourcePath, sWinHttpRangeHeader.c_str(), bUseSSL, ullContentLength, LastGoodCredentialsType), HRESULT=80072ee2 (e:\nts_sccm_release\sms\framework\tscore\downloadcontent.cpp,1406) InstallSoftware 10/02/2014 05:15:53 2332 (0x091C)
DownloadFileWithRanges() failed. 80072ee2. InstallSoftware 10/02/2014 05:15:53 2332 (0x091C)
Error downloading file from http://ConfigMgrR2.SC.LOCAL:80/SMS_DP_SMSPKG$/RR200021/sccm?/Scripts/DeployWiz_Definition_ENU.xml to C:\_SMSTaskSequence\Packages\RR200021\Scripts/DeployWiz_Definition_ENU.xml InstallSoftware 10/02/2014 05:15:53 2332 (0x091C)
DownloadFiles() failed. 80072ee2. InstallSoftware 10/02/2014 05:15:53 2332 (0x091C)
Download() failed. 80072ee2. InstallSoftware 10/02/2014 05:15:53 2332 (0x091C)
DownloadContentAndVerifyHash() failed. 80070002. InstallSoftware 10/02/2014 05:15:53 2332 (0x091C)
Failed to resolve the source for SMS PKGID=RR200021, hr=0x80070002 InstallSoftware 10/02/2014 05:15:53 2332 (0x091C)
Install Software failed to run command line, hr=0x80070002 InstallSoftware 10/02/2014 05:15:53 2332 (0x091C)
Failed to run the action: Use Toolkit Package.
The system cannot find the file specified. (Error: 80070002; Source: Windows) TSManager 10/02/2014 05:15:53 1812 (0x0714)

Cause

When using MDT 2013 integrated with ConfigMgr R2 and deploying Windows 7, the Task Sequence will continuously fail to download the MDT tools during the post install/state restore phase *IF* the Set Variable for Drive Letter TS variable is configured to True. This does not occur if it is configured to False.

Workaround

To work around this issue, create the following two Task Sequence variables at the very top of the Task Sequence, immediately below "Execute Task Sequence"

SMSTSDownloadRetryCount = 5
SMSTSDownloadRetryDelay = 15

Winds Wu | Support Engineer | Microsoft GBS Management and Security Division

Get the latest System Center news onFacebookandTwitter:

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection 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/

Here’s a quick note about a hotfix for System Center 2012 Configuration Manager Service Pack 1 (SP1) that we recently released:

When you try to install an application by a using stand-alone media Task Sequence in Microsoft System Center 2012 Configuration Manager Service Pack 1 the installation fails and entries similar to the following are logged in the Smsts.log file:

Created temp document: C:\Windows\TEMP\\b90-0\0000000a.xml
Created temp document: C:\Windows\TEMP\\b90-0\0000000b.xml
Created temp document: C:\Windows\TEMP\\b90-0\0000000c.xml
Created temp document: C:\Windows\TEMP\\b90-0\0000000d.xml
spCIStore->StoreCIFromDisk(pInfo), HRESULT=80004005

This problem occurs because the XML files that are created on the client when you run the Task Sequence are formatted incorrectly. This is a UTF-8 issue with extended characters that causes an XML parsing error. For additional details and a link to a hotfix that resolves this issue please see the following:

KB2952686 - You cannot install an application by using stand-alone media in System Center 2012 Configuration Manager Service Pack 1 (http://support.microsoft.com/kb/2952686)

J.C. Hornbeck| Solution Asset PM | Microsoft GBS Management and Security Division

Get the latest System Center news onFacebookandTwitter:

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

The Forefront Endpoint Protection 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/

Here’s a tip on a new ConfigMgr 2012 hotfix we just released. The issue addressed is that when you use the Start-CMDistributionPointUpgrade cmdlet to upgrade a shared distribution point to a Microsoft System Center 2012 R2 Configuration Manager distribution point, the cmdlet fails. This problem occurs if a secondary site is referenced in the -sitecode parameter. Additionally, you receive the following exception message:

Initiation of upgrade of BDP: server1.contoso.internal, failed.
Exception Type: System.Collections.Generic.KeyNotFoundException,Microsoft.ConfigurationManagement.Cmdlets.HS.Commands.StartDistributionPointUpgradeCommand :: Exception Message: System.Collect
ions.Generic.KeyNotFoundException: The given key was not present in the dictionary.
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
at Microsoft.ConfigurationManagement.Cmdlets.HS.Commands.StartDistributionPointUpgradeCommand.SetObjectProperties(IResultObject siteSystemObject, IResultObject distributionPointObject)
at Microsoft.ConfigurationManagement.Cmdlets.HS.Commands.StartDistributionPointUpgradeCommand.ProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord().

For additional details and a link to a hotfix that resolves this issue please see the following:

KB2948224 - The Start-CMDistributionPointUpgrade cmdlet fails in System Center 2012 R2 Configuration Manager (http://support.microsoft.com/kb/2948224)

J.C. Hornbeck| Solution Asset PM | Microsoft GBS Management and Security Division

Get the latest System Center news onFacebookandTwitter:

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

The Forefront Endpoint Protection 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/

Here’s some info on a new hotfix we recently published. The issue is that a Task Sequence (TS) doesn't start as expected in System Center 2012 Configuration Manager (ConfigMgr 2012). This issue occurs if the Run Command Line Action sequence step has a link to a package, and the deployment for the task sequence has the Download all contents locally before starting task sequence configuration applied to it. This problem occurs only if multiple task sequences include the same package and the package has a larger source size.

For all the details as well as a download link, please see the following:

KB2961924 - A command-line action that has a linked package doesn't start in System Center 2012 Configuration Manager (http://support.microsoft.com/kb/2961924)

J.C. Hornbeck| Solution Asset PM | Microsoft GBS Management and Security Division

Get the latest System Center news onFacebookandTwitter:

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

The Forefront Endpoint Protection 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/

Most support issues with Operating System Deployment (OSD) in System Center 2012 Configuration Manager stem from product misconfigurations. While there are no simple guides to implement something as powerful and complex as OSD, this article describes the step-by-step process for configuring System Center 2012 Configuration Manager (ConfigMgr 2012) to capture an existing Windows image, then walks you through creating a Client Package and Task Sequence to deploy and install that image.

This article assumes you have an existing environment that has a Configuration Manager 2012 site installed as well as a primary site that is running Configuration Manager 2012. These steps can also be used with a standalone primary site running Configuration Manager 2012. Further, this article requires that the Network Access Account and Boundaries are properly configured, and that ConfigMgr client agents are installed on the clients.

You can find the complete article here:

KB2969096 - e2e: Configuring and Troubleshooting Operating System Deployment in System Center 2012 Configuration Manager (http://support.microsoft.com/kb/2969096)

J.C. Hornbeck| Solution Asset PM | Microsoft GBS Management and Security Division

Get the latest System Center news onFacebookandTwitter:

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

The Forefront Endpoint Protection 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/

Consider the following scenario:

- You run a computer that is a member of a domain (such as Domain A).

- The first common name (CN) of the domain fully qualified domain name (FQDN) is different from the domain NetBIOS name.

- The computer is a member of a group in a different domain (such as Domain B).

- Active Directory discovery is run in Domain B in Microsoft System Center 2012 Configuration Manager. In this case, the computer that is a member of Domain A is a foreign security principal.

A supported hotfix is available from Microsoft that addresses this issue. For additional details and download instructions please see the following:

KB2962909 - Active Directory discovery creates computer names that use the domain NetBios name in System Center 2012 Configuration Manager (http://support.microsoft.com/kb/2962909)

J.C. Hornbeck| Solution Asset PM | Microsoft GBS Management and Security Division

Get the latest System Center news onFacebookandTwitter:

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

The Forefront Endpoint Protection 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/

~ Bindusar Kushwaha

Hi everyone, here in product support we regularly see issues relating to how the Content Library in System Center 2012 Configuration Manager uses and managed disk space so I thought I would take a minute and walk through a couple scenarios.

Hopefully you already have good working knowledge of each subdirectory in the Content Library and its role, but if not please refer to following articles:

• http://blogs.technet.com/b/configmgrteam/archive/2013/10/29/understanding-the-configuration-manager-content-library.aspx
• http://technet.microsoft.com/en-us/library/gg682083.aspx#BKMK_ManagingContent
• http://blogs.technet.com/b/hhoy/archive/2012/05/31/an-adventure-in-the-sccmcontentlib-single-instance-store.aspx

Also, if you need information on what to do if the drive where the Content Library is located becomes full. You can find that at the link here:

http://blogs.technet.com/b/neilp/archive/2013/01/08/configuration-manager-2012-sp1-content-library-transfer.aspx

So with all that said, what happens if the drive gets full before we realize it and we attempt to distribute packages and/or applications?

Answer is simple:

1. ConfigMgr will locate the next drive that has the maximum amount of space and “no_sms_on_drive” file (which makes that drive off limits). In our example, SCCMContentLib is on the C: drive however now it is full, and the E: drive is the next available drive for ConfigMgr.

2. ConfigMgr will then create SCCMContentLib\FileLib on the E: drive (yes, only FileLib). The Registry value for ContentLibraryPath (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\DP\ContentLibraryPath) will still be pointing to C: since the rest of the files are still located there. Only SCCMContentLib\FileLib will move because it contains the actual file.

This is by design to make sure that the package and application creation and/or distribution does not fail.

However, this raises a few more questions. Since we realized after the fact that the C: drive was full, and now SCCMContentLib is spread over both C: and E:, what if I want to move all content to the E: drive or any other drive? Or what if I want to go back and free disk space on C: so that I can keep all my content there? If I do that will SCCMContentLib from C: merge with SCCMContentLib\FileLib on E: drive? If yes, will ConfigMgr be able to utilize all of the files inside? The answer is yes, but here’s how I tested this in my lab environment before implementing it in production.

STEPS:

1. SCCMContentLib was on C: and the drive became full, however we didn’t realize this until it was too late.

2. SCCMContentLib\FileLib got created automatically on E:

3. After some additional time, let’s say that E: also got full and SCCMContentLib\FileLib got created on K: (just to make the situation more complex ;)

4. To consolidate things, we move SCCMContentLib from C: to K: using ContentLibraryTransfer.exe which merges SCCMContentLib\FileLib from K: into SCCMContentLib, and we also change the registry key “ContentLibraryPath” from C: to K:

5. Next we moved SCCMContentLib\FileLib from E: to K: using the same ContentLibraryTransfer.exe which merges SCCMContentLib\FileLib from E: to SCCMContentLib on K:

6. When complete we test the applications to see if they are still working and yes, they are!

Here is a deeper look at the steps involved and what takes place.

STEP 1:

Registry is pointing to C: for ContentLibraryPath.

The C: drive is full and we have an E: drive with plenty of space. 

As of now, SCCMContentLib is on C: and the E: drive doesn’t have any files in it.

STEP 2:

We create a new Application for the ConfigMgr 2012 Toolkit R2. Note that no failure is observed even though the disk is full.

In the background, the E: drive sees SCCMContentLib created with only SCCMContentLib\FileLib in it.

The screen shot below simply shows that FileLib contains the actual file and DataLib and PackageLib only have pointers to it.

STEP 3:

Now we shrink the E: drive and copy some random files to it to make it full.

Next we created another drive K: and verify that it is empty.

Now we’ll create another application for ReportBuilder.

SCCMContentLib gets created in K: with only SCCMContentLib\FileLib as expected. We can track the SCCMContentLib\DataLib in C: to verified that it’s created there.

This clearly shows that the SCCMContentLib\FileLib is on other drives as the drive is full, however SCCMContentLib\DataLib and SCCMContentLib\PkgLib are still at the location specified in registry (C:\SCCMContentLib in our case).

STEP 4:

Next we run the following command to move the SCCMContentLib from the C: drive to the K: drive where we already have SCCMContentLib\FileLib.

As per logs:

CLT:04/30/2014 11:25:13 ***************************************************************************************************
CLT:04/30/2014 11:25:13 Content Library Transfer                                                                          
…
CLT:04/30/2014 11:25:13 Run this tool when the server hosting the content library is offline. If you run this tool when   
CLT:04/30/2014 11:25:13 data is being written to or removed from the content library, you may introduce errors.           
…
CLT:04/30/2014 11:25:13 Read Input Arguments                                                                              
CLT:04/30/2014 11:25:13 CurrDir C NewDir K
…
CLT:04/30/2014 11:25:13 Loaded Configuration                                                                              
CLT:04/30/2014 11:25:13 Folder Source:                                                                                    
CLT:04/30/2014 11:25:13 C:\SMSSIG$                                                                                        
CLT:04/30/2014 11:25:13 C:\SMSPKGC$                                                                                       
CLT:04/30/2014 11:25:13 C:\SMSPKGSIG                                                                                      
CLT:04/30/2014 11:25:13 C:\SMSPKG                                                                                         
CLT:04/30/2014 11:25:13 C:\SCCMContentLib                                                                                 
CLT:04/30/2014 11:25:13                                                                                                   
CLT:04/30/2014 11:25:13 Folder Destination:                                                                               
CLT:04/30/2014 11:25:13 K:\SMSSIG$                                                                                        
CLT:04/30/2014 11:25:13 K:\SMSPKGK$                                                                                       
CLT:04/30/2014 11:25:13 K:\SMSPKGSIG                                                                                      
CLT:04/30/2014 11:25:13 K:\SMSPKG                                                                                         
CLT:04/30/2014 11:25:13 K:\SCCMContentLib                                                                                 
CLT:04/30/2014 11:25:13                                                                                                   
CLT:04/30/2014 11:25:13 Share Source:                                                                                     
CLT:04/30/2014 11:25:13 SMSSIG$,C:\SMSSIG$                                                                                
CLT:04/30/2014 11:25:13 SMSPKGC$,C:\SMSPKGC$                                                                              
CLT:04/30/2014 11:25:13 SMS_CPSC$,C:\SMSPKG                                                                               
CLT:04/30/2014 11:25:13 SCCMContentLib$,C:\SCCMContentLib

The changes observed in the drives explain everything:

The tool transferred the following directories from C: to K:

Also, in the Registry the location is changed to K:

Now we’ll look for the ReportBuilder application which was previously in K: to verify if it’s still there or overwritten, and if still there, is it really working or not.

We can see that it is still there and the date modified stamp tells the complete story.

In order to check whether this application still works we’ll distribute it:

Distribution was successful so I decided to deploy it to a test machine:

We are able to see that the application is downloaded by the client and saved in CCMcache on the client machine.

This clearly means the application is working, thus moving SCCMContentLib from the source drive to the target drive will merge the content and NOT overwrite it.

STEP 5:

So now we have E: with only SCCMContentLib\FileLib and the Resource ToolKit application in it. SCCMContentLib with all other information is currently moved to K: so we need to see if SCCMContentLib\FileLib from E: can also be merged to K:

We run the following command again

And check the log for verification:

CLT:04/30/2014 12:22:40 ***************************************************************************************************
…                                                                               
CLT:04/30/2014 12:22:40 Read Input Arguments                                                                              
CLT:04/30/2014 12:22:40 CurrDir E NewDir K
CLT:04/30/2014 12:22:40 Read Input Arguments: Completed Successfully                                                      
…
CLT:04/30/2014 12:22:40 Folder Source:                                                                                    
CLT:04/30/2014 12:22:40 E:\SMSSIG$                                                                                        
CLT:04/30/2014 12:22:40 E:\SMSPKGE$                                                                                       
CLT:04/30/2014 12:22:40 E:\SMSPKGSIG                                                                                      
CLT:04/30/2014 12:22:40 E:\SMSPKG                                                                                         
CLT:04/30/2014 12:22:40 E:\SCCMContentLib
CLT:04/30/2014 12:22:40                                                                                                   
CLT:04/30/2014 12:22:40 Folder Destination:                                                                               
CLT:04/30/2014 12:22:40 K:\SMSSIG$                                                                                        
CLT:04/30/2014 12:22:40 K:\SMSPKGK$                                                                                       
CLT:04/30/2014 12:22:40 K:\SMSPKGSIG                                                                                      
CLT:04/30/2014 12:22:40 K:\SMSPKG                                                                                         
CLT:04/30/2014 12:22:40 K:\SCCMContentLib
CLT:04/30/2014 12:22:40                                                                                                   
CLT:04/30/2014 12:22:40 Share Source:                                                                                     
CLT:04/30/2014 12:22:40 SMSSIG$,E:\SMSSIG$                                                                                
CLT:04/30/2014 12:22:40 SMSPKGE$,E:\SMSPKGE$                                                                              
CLT:04/30/2014 12:22:40 SMS_CPSE$,E:\SMSPKG                                                                               
CLT:04/30/2014 12:22:40 SCCMContentLib$,E:\SCCMContentLib                                                                 
CLT:04/30/2014 12:22:40                                                                                                   
Share Destination:CLT:04/30/2014 12:22:40 SMSSIG$,K:\SMSSIG$                                                                                
CLT:04/30/2014 12:22:40 SMSPKGK$,K:\SMSPKGK$                                                                              
CLT:04/30/2014 12:22:40 SMS_CPSK$,K:\SMSPKG                                                                               
CLT:04/30/2014 12:22:40 SCCMContentLib$,K:\SCCMContentLib                                                                 
…
CLT:04/30/2014 12:22:40 Verify Drives: Validating drives specified for the transfer exist                                 
CLT:04/30/2014 12:22:40 Verify Drives: Completed Successfully                                                             
CLT:04/30/2014 12:22:40 Verify Destination: Check if target drive has enough space for the transfer
…
CLT:04/30/2014 12:22:40 Executing Transfer: Begin Content Library Transfer                                                
CLT:04/30/2014 12:22:40 Mark Source: Mark source drive for Do Not Use                                                     
CLT:04/30/2014 12:22:40 Dropping No SMS.
CLT:04/30/2014 12:22:40 Successfully created NO_SMS file!                                                                 
CLT:04/30/2014 12:22:40 Mark Source: Completed                                                                            
…
CLT:04/30/2014 12:22:40 Copying Folder E:\SCCMContentLib                                                                  
CLT:04/30/2014 12:22:40 Moving E:\SCCMContentLib to K:\SCCMContentLib
CLT:04/30/2014 12:22:40 Moving E:\SCCMContentLib\FileLib to K:\SCCMContentLib\FileLib
CLT:04/30/2014 12:22:40 Moving E:\SCCMContentLib\FileLib\9CC8 to K:\SCCMContentLib\FileLib\9CC8            
CLT:04/30/2014 12:22:40 Creating directory K:\SCCMContentLib\FileLib\9CC8                                                 
LT:04/30/2014 12:22:40 Copying file E:\SCCMContentLib\FileLib\9CC8\9CC8085253117D1B938EFB87DB73F175F1B2D657083ADC963904DAD5B8008E1C to K:\SCCMContentLib\FileLib\9CC8\9CC8085253117D1B938EFB87DB73F175F1B2D657083ADC963904DAD5B8008E1C
CLT:04/30/2014 12:22:40 Copying file E:\SCCMContentLib\FileLib\9CC8\9CC8085253117D1B938EFB87DB73F175F1B2D657083ADC963904DAD5B8008E1C.INI to K:\SCCMContentLib\FileLib\9CC8\9CC8085253117D1B938EFB87DB73F175F1B2D657083ADC963904DAD5B8008E1C.INI
CLT:04/30/2014 12:22:40 Copying file E:\SCCMContentLib\FileLib\9CC8\9CC8085253117D1B938EFB87DB73F175F1B2D657083ADC963904DAD5B8008E1C.SIG to K:\SCCMContentLib\FileLib\9CC8\9CC8085253117D1B938EFB87DB73F175F1B2D657083ADC963904DAD5B8008E1C.SIG
CLT:04/30/2014 12:22:40 Copy Content: Completed                                                                           
CLT:04/30/2014 12:22:40 Stop Services                                                                                     
…
CLT:04/30/2014 12:23:11 Deleting E:\SMSSIG$                                                                               
CLT:04/30/2014 12:23:11 Deleting E:\SMSPKGE$                                                                              
CLT:04/30/2014 12:23:11 Deleting E:\SMSPKGSIG                                                                             
CLT:04/30/2014 12:23:11 Deleting E:\SMSPKG                                                                                
CLT:04/30/2014 12:23:11 Deleting E:\SCCMContentLib
CLT:04/30/2014 12:23:11 Deleting Old Content Complete                                                                     
CLT:04/30/2014 12:23:11                                                                                                   
CLT:04/30/2014 12:23:11 Updating Virtual Directories
CLT:04/30/2014 12:23:13 Virtual Directories Update Complete                                                               
…
CLT:04/30/2014 12:23:13 Content Library Transfer is now complete !!

Now we are able to see 9CC8* on the K: drive:

Also, in E:\SCCMcontentLib it is deleted:

The E: drive is removed from the usable drives list:

To make sure the application is still healthy I distributed and deployed it.

While deploying this application to a machine, we are able to see that the application is installed on the client machine:

Hopefully this will clarify how SCCMContentLib works when using disk space and helps provide a little insight on how you can manage the same.

Bindusar Kushwaha | Support Engineer | Microsoft GBS Management and Security Division

Get the latest System Center news onFacebookandTwitter:

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

The Forefront Endpoint Protection 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/

When you try to distribute a driver package to a package share on a pull-distribution point in System Center 2012 R2 Configuration Manager, the driver package is not distributed and error messages that resemble the following are logged in the Smsdpprov.log file:

CreateFolder failed; 0x8007007b
CContentDefinition::ExpandContentDefinitionItems failed; 0x8007007b
CContentDefinition::Expand failed; 0x8007007b

Note that this problem occurs even though you can distribute the driver package to a regular distribution point.

For all the details regarding why this happens and download instructions for a hotfix that addresses the issue, please see the following:

KB2962927 - You cannot distribute a driver package to a package share on a pull-distribution point (http://support.microsoft.com/kb/2962927)

J.C. Hornbeck| Solution Asset PM | Microsoft GBS Management and Security Division

Get the latest System Center news onFacebookandTwitter:

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

The Forefront Endpoint Protection 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/

~ Bindusar Kushwaha

Hi everyone, Bindusar here again. Are you planning to install the System Center 2012 Configuration Manager (ConfigMgr 2012) client using a Software Update Point but running into issues? Below are the things you may want to check.

- The computer should be joined to the domain.
- Group Policy should be working properly.
- The Software Update Point should be installed and working properly.
- Configuration Manager should be published in Active Directory (AD).
- The Windows Update agent on client machines should be working properly.
- Client Push installation should not be configured.

When installing the client using a Software Update Point, we need to make sure a few things are configured:

- Configure the WSUS server location using Group Policy so that client machines can get ccmsetup as an update patch.
- From the Configuration Manager console, client installation should be configured using the Software Update Point.

That’s it!

You can find more information on this in the following articles:

How to Install Configuration Manager Clients Using Software Update Point Based Installation: http://technet.microsoft.com/en-us/library/bb633194.aspx

Top 3 ConfigMgr 2012 Client Installation Methods: http://blogs.technet.com/b/smartinez/archive/2013/09/27/top-3-configmgr-2012-client-installation-methods.aspx

Putting it all together

Configure Group Policy to locate the WSUS server by configuring the policy item named “Specify intranet Microsoft Update service location” and provide the WSUS server name (e.g. http://WsusServerName>:Port).

Then just run Gpupdate /force on the client and make sure it’s getting that policy (this can be checked using RSOP.msc).

At this point the client computer is now ready to get all the updates needed from WSUS server location.

Now it’s time to configure Configuration Manager to distribute the Client Installer package.

NOTE The “Published version” will be blank if it was NOT configured (published) earlier.

In WCM.log we can see the following lines:

Attempting connection to WSUS server: BinPri1.Contoso.com, port: 8530, useSSL: False       SMS_WSUS_CONFIGURATION_MANAGER                   5/28/2014 4:07:24 AM    4404 (0x1134)

As we can see, the update is not only published but it’s approved with a deadline automatically! Once we are able to see this line in WCM.log we are done from the server side.

Connect to SUSDB and you should be able to see the following now available:

If you are connecting to WSUS on Server 2008 R2 use \\.\pipe\mssql$microsoft##ssee\sql\query
If you are connecting to WSUS on Server 2012, use \\.\pipe\MICROSOFT##WID\tsql\query

Now we need to wait and watch on the client machine for it to start the update scan cycle. Alternatively, you can manually trigger it from Control Panel with the Check for Updates option.

Now let’s take a look at CCMsetup.log on the client computer:

Launch from folder C:\Windows\SoftwareDistribution\Download\Install\         ccmsetup      6/2/2014 3:00:54 AM      3060 (0x0BF4)

As we can clearly see, CCMSetup is not calling any additional parameters with it. This simply means that all of the default parameters will be passed. Site and MP information will be fetched from Active Directory.

Bindusar Kushwaha | Support Engineer | Microsoft GBS Management and Security Division

Get the latest System Center news onFacebookandTwitter:

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

The Forefront Endpoint Protection 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/

After using System Center 2012 Configuration Manager or System Center 2012 R2 Configuration Manager to deploy a Windows 8 or Windows 8.1 image, when a user starts the system that has the image (physical or virtual) and tries to log on for the first time they receive the following error message:

The Group Policy Client service failed the sign-in.
The universal unique identifier (UUID) type is not supported.

This error message appears at first user logon after initial deployment of the image, however in some scenarios later user logons also result in the error.

After the message is displayed and the user clicks OK, the logon screen is displayed again.

For all the details including the cause and the steps to resolve the issue, please see the following:

KB2976660 - First logon fails with "The universal unique identifier (UUID) type is not supported" (http://support.microsoft.com/kb/2976660)

J.C. Hornbeck| Solution Asset PM | Microsoft GBS Management and Security Division

Get the latest System Center news onFacebookandTwitter:

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

The Forefront Endpoint Protection 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/

ConfigMgr 2012 R2 CU2 is now available for download and the article below describes the issues that are fixed and functionality that is updated.

For all the details and a download link, please see the following:

KB2970177 - Description of Cumulative Update 2 for System Center 2012 R2 Configuration Manager (http://support.microsoft.com/kb/2970177)

J.C. Hornbeck| Solution Asset PM | Microsoft GBS Management and Security Division

Get the latest System Center news onFacebookandTwitter:

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

The Forefront Endpoint Protection 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/

The article below describes the Windows PowerShell issues that are fixed in Cumulative Update 2 (CU2) for Microsoft System Center 2012 R2 Configuration Manager. Other ConfigMgr 2012 R2 CU2 fixes are described in Cumulative Update 2 for System Center 2012 R2 Configuration Manager.

For all the details please see the following:

KB2962855 - Description of Windows PowerShell changes in Cumulative Update 2 for System Center 2012 R2 Configuration Manager (http://support.microsoft.com/kb/2962855)

J.C. Hornbeck| Solution Asset PM | Microsoft GBS Management and Security Division

Get the latest System Center news onFacebookandTwitter:

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

The Forefront Endpoint Protection 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/

The article below describes the issues that are fixed and the functionality that is updated in Cumulative Update 2 (CU2) for Microsoft System Center 2012 R2 Configuration Manager Client for UNIX and Linux. The System Center 2012 R2 CU2 clients for UNIX and Linux can be used with both System Center 2012 Configuration Manager SP1 and System Center 2012 R2 Configuration Manager.

For all the details as well as download instructions, please see the following:

KB2976481 - Description of Cumulative Update 2 for the System Center 2012 R2 Configuration Manager Clients for Linux and Unix (http://support.microsoft.com/kb/2976481)

J.C. Hornbeck| Solution Asset PM | Microsoft GBS Management and Security Division

Get the latest System Center news onFacebookandTwitter:

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

The Forefront Endpoint Protection 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/