Tag Archives: configuration manager

RES Workspace manager integration in System Center Configuration Manager

you can combine the two products Microsoft System Center Configuration Manager and RES Workspace Manager with eachother.

In this example i will distribute an ConfigMgr Application (*.msi) to an Windows client and refresh the workspace when the installation is done. Users will see the icon after the refresh.

RES Workspace Manager

In RES you need to have imported an Application with a location to it’s executable and to the icon.

When you go to the settings tab check the box “hide application if executable was not found”.

System Center Configuration Manager
In our case the Application Adobe Reader X is imported using the information from the AcroRead.msi. Afterwards I change the installation to a <install>.cmd files.

Within Configuration Manager you need to create a *.cmd file for the application with the following content.
@echo off
msiexec /i “%~dp0AcroRead.msi” TRANSFORMS=”%~dp0AdobeAcrobat_Reader_10.1.3.01.mst” /qb REBOOT=REALLYSUPPRESS
msiexec /p “%~dp0AdbeRdrUpd1013.msp” /qb /lv %temp%\AdbeRdrUpd1013.msp.log

%RESPFDIR%\pwrgate.exe -2

With the pwrgate.exe -2 command line, RES Workspace Manager will refresh the workspace.

In the Deployment Type, as mentioned, I changed the properties of the installation program to the *.cmd.

Deploy the application as an Available or Required application.
Available means the user can install it from the Application Catalog. Required means the application will be installed without user intervention.

End User
The End User can start the Application Catalog and start the installation of the application.

RES Workspace Manager will refresh the workspace automatically and the icon will be shown in the Start Menu.


System Center configuration Manager 2012 SP1; How to change the Automatic Client Upgrade checkbox from greyed out to editable?

In Configuration Manager 2012 SP1 you could run into an Automatic Client Upgrade property being greyed out even if the user is a full administrator.

 Sites Hierarchy Settings         Site Settings Properties - automatic Client Upgrade - grayed out

In this example the user is a member of an Active Directory group called ADSBehWPBSCCMLG that has Full Administrator rights within the Configuration Manager site but is not able to use the Automatic Client Upgrade settings.

administrative users



  • log in with the account which was used when the site server was installed.
  • Go to Administration | Security | Administrative Users. Continue reading

System Center Configuration Manager 2012 SP1 Error door te veel ConfigMgr policies: reply message body length is too long

System Center Configuration Manager 2012 SP1 Error

We zien onderstaande error wanneer we met System Center Configuration Manager 2012 SP1 een machine via een Task Sequence willen inspoelen:

dwBodyLength <= m_nMaxReplySize, HRESULT=80004005, reply message body length is too long

De situatie simpel beschreven:

  1. ConfigMgr 2012 SP1
  2. Windows 7 task sequence
  3. FAT client

Wat doen we op de ConfigMgr Server:

  1. Uitrollen van een Windows 7 Task Sequence (TS) naar een FAT client.
  2. De TS loopt goed door.
  3. En allles zie er goed uit.

We gebruiken bootable media (een usb stick) om de Task Sequence nogmaals te verspreiden. wanneer we dit doen zien we in de smsts.log op de client deze melding:

<![LOG[dwBodyLength <= m_nMaxReplySize, HRESULT=80004005 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,2102)]LOG]!><time=”08:31:45.146-60″ date=”03-06-2013″ component=”TSMBootstrap” context=”” type=”0″ thread=”1392″ file=”libsmsmessaging.cpp:2102″> < ![LOG[reply message body length is too long (40780108, 16777216)]LOG]!><time=”08:31:45.146-60″ type=”3″ date=”03-06-2013″ file=”libsmsmessaging.cpp:2102″ thread=”1392″ context=”” component=”TSMBootstrap”> < ![LOG[DoRequest (sReply, true), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,2817)]LOG]!><time=”08:31:45.146-60″ type=”0″ date=”03-06-2013″ file=”libsmsmessaging.cpp:2817″ thread=”1392″ context=”” component=”TSMBootstrap”> < ![LOG[oPolicyAssignments.RequestAssignments(), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\tspolicy.cpp,968)]LOG]!><time=”08:31:45.146-60″ type=”0″ date=”03-06-2013″ file=”tspolicy.cpp:968″ thread=”1392″ context=”” component=”TSMBootstrap”> < ![LOG[Failed to request policy assignments (Code 0x80004005)]LOG]!><time=”08:31:45.162-60″ type=”3″ date=”03-06-2013″ file=”tspolicy.cpp:968″ thread=”1392″ context=”” component=”TSMBootstrap”> < ![LOG[m_pPolicyManager->init( sMP, nHttpPort, nHttpsPort, sSiteCode, bUseCRL, L””, sMediaPfx, sMediaGuid, sEnterpriseCert, sServerCerts, sSiteSigningCert, sAuthenticator), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,1198)]LOG]!><time=”08:31:45.162-60″ type=”0″ date=”03-06-2013″ file=”tsmediawizardcontrol.cpp:1198″ thread=”1392″ context=”” component=”TSMBootstrap”> < ![LOG[Exiting TSMediaWizardControl::GetPolicy.]LOG]!><time=”08:31:45.162-60″ type=”0″ date=”03-06-2013″ file=”tsmediawizardcontrol.cpp:1378″ thread=”1392″ context=”” component=”TSMBootstrap”> < ![LOG[pWelcomePage->m_pTSMediaWizardControl->GetPolicy(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawelcomepage.cpp,303)]LOG]!><time=”08:31:45.162-60″ type=”0″ date=”03-06-2013″ file=”tsmediawelcomepage.cpp:303″ thread=”1392″ context=”” component=”TSMBootstrap”> < ![LOG[Setting wizard error: An error occurred while retrieving policy for this computer  (0x80004005). For more information, contact your system administrator or helpdesk operator.]LOG]!><time=”08:31:45.162-60″ date=”03-06-2013″ component=”TSMBootstrap” context=”” type=”0″ thread=”1356″ file=”tsmediawizardcontrol.cpp:1547″> <

Wanneer we onderstaande uitvoeren is het probleem verholpen:

  1. De computer entry verwijderen uit de collectie m.b.v. het administrator console.
  2. De computer herstarten.
  3. Hierna kunnen we de usb stick (boot media) weer gebruiken en werkt het.

We willen eigelijk deze workaround niet gebruiken, we willen de computer entry, die al in de collectie bekend is, hergebruiken.

Bovenstaande kan opgelost worden door minder ConfigMgr policies aan de machine aan te bieden?

In ons geval was het het hebben van teveel Compliance policies. We hadden een baseline aangemaakt met een check of alle updates wel aanwezig zijn op een machine.

Meer informatie kan gevonden worden bij Microsoft Technet, klik HIER. LET OP, hier moet je wel aanloggen met een Microsoft account.