Tag Archives: Microsoft

Windows XP CSA Updates in System Center Configuration Manager 2012 R2

This guide describes how to use System Center Configuration Manager 2012 R2 to import the Windows XP CSA updates.

 Logon to the System Center configuration Manager Management point and start the Windows Explorer goto C:\CSA  
 Remove the ‘old’ files from the Payload directory. Put them in the _Archive folder  
 Remove the ‘old’ cab file from the ScanCab directory. Put them in the _Archive folder  
 Download the ‘new’ Microsoft CSA Update Payload Packages to: C:\CSA\Payload And the CAB file to: C:\CSA\ScanCab. Use a Microsoft Account to get access to the Microsoft connect site.  
 Open a CMD (as an administrator) and change directory to C:\CSA  
 Excecute the command line: Wsusimporttool.exe c:\CSA\ScanCab\CSA-WindowsXPSP3.CAB c:\CSA\Payload\ c:\CSA\WorkingDir  
Reminder: if the wsusimporttool is giving an Error “No instance of WSUS found on this server. WSUSImportTool can only be run locally on a WSUS server” use the WsusUtil from C:\Program Files\Update Services\Tools\ WsusUtil.exe csaimport c:\CSA\ScanCab\CSA-WindowsXPSP3.CAB c:\CSA\Payload
Check if the updates are presented in the database. Start WSUS admin tool and check if the Custom Support updates are added.
Start the SCCM console and goto Administration | Site Configuration | Sites en selecteer de Site kies voor Configure site components | Software Update Point.
Change the settings to do not synchronize from Microsoft Update or upstream data source. Reminder: change these settings back at the end of this procedure
Go to the tab Sync Schedule and choose a date and time which will take place in a couple of minutes.
A new product group, with the name “Windows XP SP3 custom support” will appear. Check this product group. And sync again from the tab sync schedule
Open the wsyncmgr.log to see if the sync is started and when it will be finished.
Wait till it’s finished.
Change the settings back in the Sync Settings Synchronize from Microsoft update
Start the SCCM console and goto Software Library | Software Updates | All Software Updates Click on synchronize Software Updates. Watch the wsyncmgr.log
See if the updates are visible in the SCCM console
Deploy the updates to the XP collection
Click Run Now
Advertisements

#Microsoft #Surface RT and Surface Pro registry tweaks to change the start screen Tiles to 3, 4 or 5 rows.

Microsoft Surface registry tweaks you can use to change the Surface RT and Surface Pro start screen Tiles to 3, 4 or 5 rows.

Three Rows of Start Screen Tiles for Surface RT and Surface Pro
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\ExplorerScaling
“MonitorSize”=”10.6″

Four Rows of Start Screen Tiles for Surface RT and Surface Pro
Surface RT
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\ExplorerScaling
“MonitorSize”=”12.1″

Surface Pro
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Scaling
“MonitorSize”=”13.1″

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\ImmersiveShell\Grid “Layout_MaximumRowCount”=dword:00000004

Five Rows of Start Screen Tiles for Surface RT and Surface Pro
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\ExplorerScaling
“MonitorSize”=”13.1″

Reminder:
HKLM keys will need a system reboot/restart.
HKCU keys needs to be set for every users account.

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

 

Solution

  • 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.