Microsoft System Center & Windows Blogs

“sccm installation failed with error code 1603” Getting error for SCCM 2007 Client installation Below are the SCCM Client installation options for CCMSETUP.exe “sccm installation failed with error code 1603” 1. Navigate to the following folder and run the following commands: C:\Windows\System32\Wbem for /f %s in ('dir /b *.mof *.mfl') do mofcomp %s for /f %s in ('dir /b /s *.dll') do regsvr32 /s %s First command will recompile all the mof fils under the WBEM folder Second command will register all the .dlls under the WBEM folder 2. Verified the WMI permission under DCOMCNFG Default WMI DCOM Settings: Modifying the default WMI DCOM Settings can also cause a wide range of problems. Once again, you can use DCOMCNFG to view these settings. Windows XP a. Start -> Run -> Open: DCOMCNFG b. Expand Component Services node c. Expand Computers node d. Expand My Computer node e. Expand DCOM Config nod

Client Push Installation In order to successfully use client push to install the Configuration Manager 2007 client, you must add the following as exceptions to the Windows Firewall: • File and Printer Sharing  • Windows Management Instrumentation (WMI)  Client Installation using Group Policy In order to successfully use Group Policy to install the Configuration Manager 2007 client, you must add File and Printer Sharing as an exception to the Windows Firewall. Client Requests In order for client computers to communicate with Configuration Manager 2007 site systems, you must add the following as exceptions to the Windows Firewall: TCP Port 80 (for HTTP communication) TCP Port 443 (for HTTPS communication) Network Access Protection In order for client computers to successfully communicate with the system health validator point, you need to allow the following ports: •UDP 67 and UDP 68 for DHCP •TCP 80/443 for IPsec Remote Control   In order to use the remote

System Center Configuration Manager Services  Active services running in SCCM primary server SMS_Executive Service  SMS_Site_Component_Manager SMS_Site_SQL_Backup SCCM Active Server Services Secondary Site

Error when trying to create a new collection Getting below error when creating a New collection. Form that is already visible cannot be displayed as a modal dialog box Error Code Below ConfigMgr Error Object: instance of SMS_ExtendedStatus { CauseInfo = "11"; Description = "Unable to update parent collection due to SQL error."; ErrorCode = 3242722566; File = "e:\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\sspcollection.cpp"; Line = 766; ObjectInfo = "Adobe ; Operation = "PutInstance"; ParameterInfo = ""; ProviderName = "ExtnProv"; SQLMessage = "[HYT00][0][Microsoft][ODBC SQL Server Driver]Timeout expired"; SQLSeverity = 0; SQLStatus = 0; StatusCode = 2147749889; Suggested Steps To check 1.  Restart the console, log out and log back in, 2. Check in the  Smsprov.log file  for SQL related Errors  3. Reboot the SCCM Server 4. Try I ncreasing the tempdb size

  Install not allowed as another job is still in progress Security updates deployments to Servers Having an issue with a ConfigMgr client not installing updates No errors just showing  “ Install not allow as another job is still in progress”      or  “Security updates preparing for installation” Even after the reboot, machine policy reset, no resolution  There are no errors in the log files  UpdateDeployment.log  except showing the messages saying   "Install not allow as another job is still in progress" Steps to be followed  Kindly use SCCM Client Center to Repair WMI its more effective  SCCM Client Center to "Delete root\ccm" (button under Repair WMI) to delete the CCM Namespace from WMI. These steps worked and the SCCM service (SMS Agent Host) came back online, software updates scan took place and assignments started to apply. Updates began to download and apply as normal. 

If you find errors in the WUAHandler.log as below "OnSearchComplete - Failed to end Search job. Error = 0x80072efd Scan failed with error = 0x80072efd" Error 0x80072efd means: 'The attempt to connect to the server failed. Can you check the following logs for more information "%Windir%\WindowsUpdate.log and ScanAgent.log Server not being able to talk to the WSUS server because port 8530 might be blocked lack of  communication  between the client and the SCCM sup if you are working with custom WSUS ports. Do not forget to open the used ports in the Windows Firewall Create a rule for inbound TCP (WSUS ports). In my case it was for 8530 and 8531. 

WMI Error messages in execmgr.log file on SCCM clients   ·          Failed to open to WMI namespace '\.rootccmPolicyMachine' (8007045b) ·          Failed to ConnectSettings for ICcmPolicyAgent in CSoftDistPolicyNamespace::ConnectToNamespace ·          Failed to ConnectToNamespace in CSoftDistPolicyNamespace::GetMachinePolicy ·          Failed to connect to machine policy name space. 0x8007045b ·          Failed to connect to user policy name space ·          CSoftwareDistPolicyMgr::GetSWDistSiteSettings failed to connect to machine namespace ·          Failed to instantiate UI Server {C2F23AE4-82D8-456F-A4AF-A2655D8CA726} with error 8000401a ·          Failed to instantiate UI Server 2 {E8425D59-451B-4978-A2AB-641470EB7C02} with error 8000401a ·          Failed to instantiate Updates UI Server {2D023958-73D0-4542-8AD6-9A507364F70E} with error 8000401a ·          Failed to instantiate VApp UI Server {00AAB372-0D6D-4976-B5F5-9BC7605E30BB} with error 0x8000401A

·          11700 101 Failed Scan Tool for this update is not available ·          11701 101 Failed Scan Tool for this update failed ·          11702 101 Failed The contents hash for this update provided in policy does not match with the contents downloaded ·          11703 101 Failed The contents for this update could not be located ·          11704 101 Failed Contents size for this update exceed free cache size available ·          11705 101 Failed Contents size for this update exceed total cache size available ·          11706 101 Failed Failed to download contents for this update ·          11707 101 Failed This Update cannot be attempted due to invalid commandline ·          11708 101 Failed This Update application failed ·          11709 101 Failed This Update did not finish in allocated time ·          11710 101 Failed Creation of process failed for this update ·          11711 101 Failed Failed to get installer path for this upd

Operating system     Version number Windows 7 6.1 Windows Server 2008 R2 6.1 Windows Server 2008 6.0 Windows Vista 6.0 Windows Server 2003 R2 5.2 Windows Server 2003 5.2 Windows XP 64-Bit Edition 5.2 Windows XP 5.1 Windows 2000 5.0 Version Windows Revision Windows 7 Version 6.1 Windows 7 (Name of Vista, e.g. Windows 7 Home Premium) Windows Vista Version 6.0 Windows Vista (Name of Vista, e.g. Windows Vista Home Basic) Windows XP 5.1.2600 Windows XP (Name of XP, e.g. Home Edition, Professional, Media Center Edition) Windows 2000 5.00.2195 Windows 2000 Workstation Windows ME 4.90.3000 Original release of Windows ME. Windows CE 3.0 Windows CE 3.0 Windows 98 4.10.2222A Windows 98 Second e

To find out which version you are running just go to Site Management under your site database. RTM is 4.00.5931.0000 and SP1 is 4.00.6221.1000.   Update 1: SP2 eval is 4.00.6468.2001 Update 2: SP2 retail is 4.00.6487.2000 To see if R2 is installed right-click and choose properties on the site, in this case 007 – System Center. On the general tab it will state if R2 is installed or not.

Error Code Error message when you try to install updates from the Windows Update or Microsoft Update Web site: "0x8024000B" Cause When you try to install updates by using the Windows Update or Microsoft Update Web site, you may receive the following error message: 0x8024000B This problem may occur if Windows Update or Microsoft Update cannot read the update manifest. Soluion To resolve this problem, rename the Spupdsvc.exe file, and then try to install the updates again. To do this, follow these steps: Click Start, and then click Run. Copy the following text, paste it into the Run box, and then click OK or press ENTER: Cmd /c ren %WinDir%\System32\Spupdsvc.exe Spupdsvc.old Try to install the updates again. If you still cannot install the updates, see the "References" section for information about how to contact Windows Update support or Microsoft Update support.

Client side Log file ::: WUAHandler.log - Provides information about when the Windows Update Agent on the client searches for software updates. ScanAgent.log - Provides information about the scan requests for software updates, what tool is requested for the scan, the WSUS location, and so on. UpdatesStore.log - Provides information about the compliance status for the software updates that were assessed during the compliance scan cycle.  UpdatesHandler.log - Provides information about software update compliance scanning and about the download and installation of software updates on the client. WindowsUpdate.log (located in C:\windows directory) - Provides information about when the Windows Update Agent connects to the WSUS server and retrieves the software updates for compliance assessment and whether there are updates to the agent components. WindowsDeployment.log - Provides information about the deployment on the client, including software update activation, evalua

Troubleshooting Software Updates Client Issues Client Scan Fails with Error 0x80040693 In the Microsoft System Center Configuration Manager 2007 console, view any reports in the category Software Updates - E. Troubleshooting. If a Configuration Manager 2007 client reports the error code 0x80040693 , it means the client is running the wrong version of Windows Update Agent (WUA). Configuration Manager 2007 clients require version 7.0.6000.374 or higher.  Possible Solution If client computers are configured for Automatic Update, they should automatically update their Windows Update Agent from their Automatic Update source. If clients are not configured for Automatic Update, you can locate the WUA redistributable file wuredist.cab on MSDN and deploy it using Configuration Manager 2007 software distribution. Software Update Installation Fails with Error 0x80091007 Before a Configuration Manager 2007 client can install software updates, it verifies the hash on the content containi