Simplified, User-centric Application Management across Devices with System Center 2012 R2 Configuration Manager and Windows Intune
User Experience with Unified Device Management using System Center 2012 R2 Configuration Manager and Windows Intune
New Hotfix: A task sequence cannot download content from a Configuration Manager 2007 shared distribution point in ConfigMgr 2012 SP1
Assume that you perform one of the following deployments:
- - A task sequence by using the Download content if needed option
- - A task sequence to a System Center Configuration Manager 2012 Service Pack 1 (SP1) client or a destination computer
In this situation, the task sequence cannot download content from a Microsoft System Center Configuration Manager 2007 shared distribution point.
There is a new downloadable hotfix available for this issue and you can get all the details here:
KB2841592 - FIX: A task sequence cannot download content from a Configuration Manager 2007 shared distribution point in System Center 2012 Configuration Manager SP1 (http://support.microsoft.com/kb/2841592)
J.C. Hornbeck| Knowledge 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/
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/
New Hotfix: Errors when you try to install or recover a secondary site in System Center 2012 Configuration Manager
Consider the following scenario:
- You install Microsoft System Center 2012 Configuration Manager Service Pack 1.
- You apply Cumulative Update 2 (http://support.microsoft.com/kb/2854009) for System Center 2012 Configuration Manager Service Pack 1 in the hierarchy.
- You try to install a new secondary site or to recover an old secondary site by using the Copy installation source files over the network from the parent site server Installation Source Files option.
In this scenario, errors that resemble the following are logged in the ConfigMgrSetup.log file:INFO: SQL Server Script: Creating object spupdatemessageactivity~
INFO: Configuring database replication tables.
*** [42000][50000][Microsoft][SQL Server Native Client 11.0][SQL Server]Object 'PullDPResponse' does not exist : spConfigureReplication
ERROR: Failed to execute dbo.spConfigureReplication.
ERROR: Failed to configure SQL Server replication tables.
There is a new downloadable hotfix available for this issue and you can get all the details here:
KB2867422 - FIX: Errors when you try to install or recover a secondary site in System Center 2012 Configuration Manager (http://support.microsoft.com/kb/2867422)
J.C. Hornbeck| Knowledge 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/
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/
Customizing Offline Servicing of Operating System Images
HOTFIX: "Install Application" task sequence fails with Error code 80004005 in System Center 2012 Configuration Manager SP1
Consider the following scenario:
- You install a Microsoft System Center 2012 Configuration Manager Service Pack 1 (SP1) primary site server.
- You use the Install Application task sequence step to install two applications by using the Install applications according to dynamic variable list setting.
- You create a deployment for the sequence and then deploy the sequence to the target collection.
In this scenario, the task sequence fails. Additionally, the following error is logged in the Smsts.log file:Error code: 0x80004005
There is a new downloadable hotfix available for this issue and you can get all the details here:
KB2837395 - "Install Application" task sequence fails with Error code 80004005 in System Center 2012 Configuration Manager SP1 (http://support.microsoft.com/kb/2837395)
J.C. Hornbeck| Knowledge 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/
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/
Customizing the Temporary Location for Operating System Deployment Media Creation
Supporting iOS devices in the workplace
Issues Reported with MS13-052 (KB2840628) and Configuration Manager
KB: MBAM 2.0 Setup fails with "Error retrieving Configuration Manager Server role settings for 'Reporting Services Point' role"
If you run Microsoft BitLocker Administration and Monitoring (MBAM) 2.0 Setup on a System Center 2012 Configuration Manager (ConfigMgr) server, the MBAM prerequisite checker fails with the following error message:
Error retrieving Configuration Manager server role settings for 'Reporting Services Point' role
If you are experiencing this issue please see the KB article below for more information:
KB2870847 - MBAM 2.0 Setup fails with "Error retrieving Configuration Manager Server role settings for 'Reporting Services Point' role" (http://support.microsoft.com/kb/2870847)
J.C. Hornbeck| Knowledge 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/
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/
Extending Inventory on Linux and UNIX computers using Open Management Infrastructure (OMI)
HOTFIX: A task sequence stops responding when multiple task sequences are started in System Center 2012 Configuration Manager
Consider the following scenario:
- You create 10 packages from an .msi file on a Microsoft System Center 2012 Configuration Manager site server.
- You create 10 task sequences that contain "Install Package" steps that reference one of the packages.
- You assign the task sequence to a collection.
- You update the policy on the client in the collection, and run all 10 task sequences at the same time through Software Center.
In this scenario, one of the task sequences may stop responding in the "Installing" state while other task sequences remain in the "Waiting to install" state. Additionally, some task sequences may remain in the "Available" state on the Available Software tab even though you had selected to install them.There is a new downloadable hotfix available for this issue and you can get all the details here:
KB2869380 - "Install Application" task sequence fails with Error code 80004005 in System Center 2012 Configuration Manager SP1 (http://support.microsoft.com/kb/2869380)
J.C. Hornbeck| Knowledge 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/
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/
Announcement: Configuration Manager Documentation Library Update for July 2013
Support Tip: The data in statusreportingctrl.ct0 may be reset if recovering only the site database in ConfigMgr 2012
~ Winds Wu | Support Engineer
We recently came across an issue related to restoring the site database in System Center 2012 Configuration Manager Service Pack 1 (ConfigMgr 2012 SP1) and we wanted to make you aware of it in case you happened to see it. There is no functional impact that we’ve been able to determine but it may raise some questions if you see the errors.
Issue: If you only recover the site database in ConfigMgr 2012, the data in statusreportingctrl.ct0 will be reset back to its original version.
Repro Steps
1. On a ConfigMgr Primary Site Server, backup the site sever & database.
2. Remove the database from the site server.
3. Run the recovery wizard from the SP1 RTM CD to only recover the database.
4. Finish the recovery.
Expected Result:
The data in <SMS installation folder>\scripts\statusreportingctrl.ct0 would be the same as the file before the recovery.
Actual Result:
The <SMS installation folder>\scripts\statusreportingctrl.ct0 is replaced with the file from SP1RTMCD (1KB). The original data in the file is lost.
The result is that you will see errors in SMSEXEC.log similar to the following:
CServerStatusReporter::RefreshFilter(): ERROR: The control file does not contain a configuration item named "Server Component Status Reporting".
This is currently scheduled to be addressed in a future version of the product but in the meantime, be sure to backup the statusreportingctrl.ct0 before performing a site database recovery, then copy it back after the recovery is complete.
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/
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/
Known Issue: Update to MCS.msi fails to upgrade the Multicast Configuration on Distribution Points
HOTFIX: An Alternate Content Provider does not work in a task sequence for a System Center 2012 Configuration Manager SP1 site
Consider the following scenario:
- You configure an application that takes advantage of the Alternate Content Provider (ACP) to distribute packages in a Microsoft System Center 2012 Configuration Manager Service Pack 1 (SP1) site.
- You create a task sequence that includes an "Install Application" step.
- You include a single application in the step.
- You specify the following options, and then you deploy the task sequence:
- Download all content locally before starting task sequence
- When no local distribution point is available, use a remote distribution point
- Allow clients to use a fallback source location for content
- A client receives the policy for deployment, and then begins to process the task sequence according to schedule. Or, you click Install for the task sequence deployment in Software Center on the client.
In this scenario, the ACP is not invoked in the ContentTransferManger.log file when you download the content.
There is a new downloadable hotfix available for this issue and you can get all the details here:
KB2870742 - FIX: An Alternate Content Provider does not work in a task sequence for a System Center 2012 Configuration Manager SP1 site (http://support.microsoft.com/kb/2870742)
J.C. Hornbeck| Knowledge 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/
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/
Support Tip: A ConfigMgr 2012 Management Point enabled for SSL fails with 403 forbidden
~ Vinayak Sharma| Technical Lead
Here’s a quick tip on an interesting issue I saw the other day in case you happen to run across it.
The core issue is that an HTTPS enabled System Center 2012 Configuration Manager (ConfigMgr 2012) Management Point (MP) installed on Windows Server 2012 may not work as expected, and in the IIS logs you see a 403.16 status code which resolves to ‘Client certificate is untrusted or invalid.’ The Mpcontrol.log will also show the following:
Call to HttpSendRequestSync failed for port 443 with status code 403, text: Forbidden
Http test request failed, status code is 403, 'Forbidden'.
This can occur if IIS is not configured to use a Certificate Control List (CTL). Without a CTL, SSL client certificate authentication will fail with the 403.16 error mentioned above because SChannel.dll wrongly considers the client certificate to be untrusted.
NOTE: Having no CTL in use is the default configuration of IIS 8.0. This is configured by having no SendTrustedIssuerList present or by setting SendTrustedIssuerList=0.
This can also occur there is a non self-signed certificate in the 'Trusted Root Certification Authorities' certificate store.
Solution
To resolve this issue we need to have these two registries created on the MP server.
HKLM/system/currentcontrolset/control/securityproviders/schannel/sendtrustedissuerlist=0
HKLM/system/currentcontrolset/control/securityproviders/schannel/ClientauthTrustmode=2
Also make sure that there is no self-signed certificate in the 'Trusted Root Certification Authorities' certificate store. To verify this, open MMC and add the certificate snap-in. Navigate to 'Trusted Root Certification Authorities'. There should not be any certificate where 'Issued to' and 'Issued by' is not matching. If there is one, it is safe to delete that certificate.
Vinayak Sharma| Technical Lead | 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/
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/
Support Tip: ConfigMgr 2012 App catalog error "network communication or configuration problem"
~ Gagan Mehra | Support Escalation Engineer
Here’s an interesting issue I saw the other day that I thought was worth mentioning here on the blog just in case anyone else runs across it. I was talking to a customer and whenever he would go under My Devices in the System Center 2012 Configuration Manager Application Catalog he would see the following error:
This settings cannot be configured because of network communication or configuration problem
Additionally, under the Silverlight log for the Application Catalog we found this:
[1][00/25/2010 16:54:44] :ApplicationDetailViewModel.ShowNetworkWarning-Error:User is not allowed or supported to install on the current machine
…
[1][00/25/2010 16:54:46] :ApplicationDetailViewModel.InstallAppProgression-Error:User is not allowed or supported to install on the current machine
[1][00/25/2010 16:54:46] :ApplicationDetailViewModel.UpdatePageView:PageViewMode changed to:FastInstallError
[1][00/25/2010 16:54:47] :FastInstallPageView:Create Page View FastInstallError
This issue can occur if there is a time skew (time difference) between the client and the domain controller. Fortunately for us that’s a relatively easy fix:
1. Open a CMD prompt with ADMIN rights.
2. Run Net time /set.
3. When it prompts to sync then type yes or y.
4. Close the Application Catalog and Software Center and open it again.
5. Check under My Devices in the Application Catalog and the error should be gone.
Gagan Mehra | Support Escalation 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/
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/