Wednesday, November 28, 2012

WMI Namespace Errors In CCMSetup Log file

 In your SMS client systems CcmSetup.Log file in the CcmSetup directory you may see any one of the following errors or warnings:

• MSI: Setup was unable to create the WMI namespace CCM
• The error code is 80041001 or 80070003

• MSI: Warning 25101. Setup was unable to delete WMI namespace CIMV2\SMS
• the error code is 80041001 or 80070003

• Client installation has failed too many times. Ccmsetup will now abort.

• Installation failed with error code 1603

what this is basically telling you is that WMI is out to lunch and has been reported as AWOL. To resolve these log file issues you must delete or rename the machines WMI Repository and allow it to recreate itself.

Follow the steps below to accomplish this:

1. Stop the "Windows Management Instrumentation" service.

2. Rename the Windows\System32\Wbem\Repository folder to ”Oldrepository”.

3. Restart the “Windows Management Instrumentation service”.

4. Verify that the Windows \System32\Wbem\Repository folder has been recreated.

5. Reinstall the SMS client software.

Tuesday, November 27, 2012

Troubleshooting Software Updates Client Issues SCCM

1-Client Scan Fails with Error 0x80040693

In the Microsoft System Center Configuration Manager 2007 console, view any reports in the category Software Updates - 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 on MSDN and deploy it using Configuration Manager 2007 software distribution.

2-Software Update Installation Fails with Error 0x80091007

Before a Configuration Manager 2007 client can install software updates, it verifies the hash on the content containing the software update. If the hash does not match, the client fails to install the software update and logs error 0x80091007 to the updatesdeployment.log on the client. The error is also sent to the management point and is visible in the reports under the category Software Updates 
This issue is often caused by having the wrong version of the package on the distribution point. Frequently this issue occurs when content has not been replicated to a child site or when the package version has changed but the client has not received new policy yet.

Possible Solution

In the Configuration Manager 2007 console, navigate to System Center Configuration Manager ,Site Database, Computer Management,  Software Updates, Deployment Packages, Package Status, Package Status, and look at the source version for the package. Verify that all distribution points are using the same source version, including any distribution points at the child site. You can also look at distmgr.log for any errors that reference the package ID.

3-Software Update Installation Fails with Error = 0x80004002

A client computer fails to install a software update with the 0x80004002 error message reported in the client log files, such as the following sample log entries:
WSUS update installation result = 0x80004002, Reboot State = NoReboot
Update execution failed.
Failed to get final installation result of updates. Error = 0x80004002.
Update 1 () finished installing (0x80004002).
Update 2 () finished installing (0x80004002).
Installation of updates completed.
WARNING: client failed installing updates with error 0x80004002
The UpdatesHandler.log and WUAHandler.log files are located in Logs, and the Windows Update.log is located in windir.
Possible Solution
The WUA installation on the client might be missing files or be corrupt. Reinstall WUA 3.0 on the client computer. For more information about installing WUA 3.0, 

Saturday, October 27, 2012

Package is showing "Waiting to install" Even package is installed on DP

A-Source version of package is missed on DP

While Package distribution on distribution point you’re facing a problem, Distmgr.log is showing following error
1-      While replication distmgr.log is showing for DP
Package CEN002E5 requires a newer version (4) of source files and the new compressed files haven't arrived yet, current version is 3, skip E:\SMS\inboxes\\INCOMING\E4D9HVCY.PKG
This error occurs if status massages have not reached to CEN server, that’s why packages are showing “Waiting to Install”

I have solution of this issue, but this is not recommended by Microsoft, but I have already tested on a DP, and that is working for me,

                “Status massages have been reached to CEN server and packages are showing Package is installed on DP”

Step1- First delete E4D9HVCY.PKG from SMS\inboxes\\INCOMING

Step2- Execute following command on CEN server,

UPDATE PkgStatus SET Status=2, SourceVersion=0 WHERE TYPE=1 AND PkgServer='DP Name' AND ID='PKGID'

After that just refresh the DP for package, it will take some time but Status massage will update to CEN server,

B-Package is showing waiting to install even package is installed on DP

Some times we are facing a error package is showing waiting to installed even package is install on DP,
This error comes when status massage has not updated on CEN server,

For this error I have a solution but this is not recommended by Microsoft but that is worked for me,

Stpe1- Delete entries from CEN server database,

Execute following commands on CEN to delete, NAL path, ContentMap and Status massage

“Delete from pkgservers where NALpath like '%\\DP Name%' and pkgID=’PkgID’ ”
 “ delete from pkgstatus where pkgserver like '%\\DP Name%' and ID='PkgID' “

“ delete from contentdpmap where serverpath like '%\\DP Name%' and contentID='PkgID' “

Step2- After execution of above commands remove package from DP,

Step3- Wait for some time then again add packages to DP

You will see the packages are installed on DP and status massages are reached to CEN server,

Thursday, October 25, 2012

Microsoft Launches Windows 8 After 1.24B Hours Of Public Testing

During Microsoft’s official launch event for Windows 8 in New York City today, Steven Sinofsky, the president of the company’s Windows and Windows Live division, said that the company’s new operating system went through 1,240,000,000 hours of testing in public in 190 countries. “No product anywhere receives this kind of testing anywhere in the world,” he said.
For Microsoft, today is obviously a big day, as users can now download and buy Windows 8 for their PCs and start buying numerous new devices. According to Microsoft, there are now over 1,000 certified Windows 8 PCs. The focus today, of course, was on devices with touchscreens, including tablets and convertibles. “These are the best PCs ever made,” Sinofsky said

Sinofsky referenced the days when we were basically "living in caves," the time of Windows 95. He used memories of that era to emphasize just how far Microsoft's operating system has come. Now, more than 1,000 PCs have been certified for Windows 8, bringing on what the folks at Microsoft describe as a new era of computing (and of Windows).
Sinofsky did at one point acknowledge that some folks might call out Microsoft's newly launched app store for having a small selection of apps, in comparison to what is available on other platforms, such as Apple and Google.
"We see today as a grand opening, and a very strong one," he said. And he says that there are more apps in the Windows app store than there were in any competitor's at launch.

Sunday, October 14, 2012

“Out Of Memory-GetRows” or SMS report is showing only 10,000 Rows,

Error massage when you try to run SMS/SCCM web Report
“Out Of Memory-GetRows” or SMS report is showing only 10,000 Rows,
No need to worry about this error, this error is known and this hits comes by default value which is
Configured in SMS Registry.
Resolution-1 Increase the row count of SMS Report from 10,000 to unlimited

Report Viewer in Configuration Manager 2007 limits the result set returned by a report query to 10,000 rows. The maximum number of rows that are returned when running a report query can be modified by creating a registry key and setting a value on site system computers that have the reporting point role

To change the number of rows returned by a report query
  1. Open the Registry Editor on the reporting point computer.
  2. Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Reporting.
  3. Create a DWORD value named Rowcount, and then set its value to the number of rows that you want returned in the report query. If you want to return all rows, set the value to 0xffffffff, which is the hexadecimal equivalent of –1.
The configured number of rows is returned by any report query that is run from this reporting point.

Note: If you have given the wrong value then SMS Report will show only 10,000 Rows,

Resolution-2 Out of Memory- GetRows error while accessing the SMS Report,

Then you have to check the AspBufferingLimit value which will you could find in C:\Windows\system32\inetsrv\MetaBase.xml  search the “AspBufferingLimit “ and you see the value is 4194304 which is about 4 MB,
Now you have to change the value from 4 MB to according your limit,

After that jus restart the SMS Reporting service and you can see your SMS Report is back on track,

Tuesday, July 31, 2012

Today Microsoft introduced, a new personal email service that reimagines the way that people use email – from a cleaner look, to fewer and less obtrusive ads, to new connections to social media sites like Facebook and Twitter. Visit to sign up for your account!

Wednesday, June 13, 2012

Microsoft System Center 2012 Configuration Manager Overview (including SP1 info

Are you ready for System Center 2012 Configuration Manager? It's just around the corner and is the most important release for client administrators! Configuration Manager 2012 will manage heterogeneous devices and introduces a new way to deploy applications—capabilities that will allow client administrators to enable Consumerization of IT. But, there is more: NEW interface, improved setting management, role based administration, and infrastructure reduction. Come to this overview session to get up to speed on all the new capabilities of Configuration Manager 2012. #TEMGT309

Some of the System Center 2012 Configuration Manager session from presented at TechEd Orlando is now available online at TechEd online.

Microsoft System Center 2012 Configuration Manager Overview (including SP1 info)
Patch and Settings Management in Microsoft System Center 2012 Configuration Manager
Microsoft System Center 2012 Endpoint Protection Overview

Configuration Manager Run Scripts feature

SCCM CB 1706 has very good new feature that is called script. script is very good feature to collect some certain data from some a comput...