SETUP WAS UNABLE TO CREATE THE WMI NAMESPACE CCM

Error : SETUP WAS UNABLE TO CREATE THE WMI NAMESPACE CCM
           Installation Failed with Error code 1603

You can resolve this issue by deleting the WMI repository. Perform the following steps to accompish this.

1. Stop the “Windows Management Instrumentation” service.
2. Rename the C:\Windows\System32\Wbem\Repository folder to repository_old or delete it.
3. Restart the “Windows Management Instrumentation service”.
4. Reinstall the SMS client.

THE PROCESS IS NOT IN BACKGROUND PROCESSING MODE SCCM 2007 + PATCH DOWNLOADING ISSUE

1) patchdownloader.log in sccm gives following error :

HttpSendRequest failed HTTP_STATUS_FORBIDDEN or HTTP_STATUS_DENIED
ERROR: DownloadContentFiles() failed with hr=0x80070193

Solution :

1) Login to sccm server.
2) Open Internet Explorer
3) if Proxy is enabled, provide your credentials, and check any website that is connecting to internet,

that's it, you are done.

Start downloading patch now,

SITE MAINTENANCE TASK PREDEFINED - SCCM

Predefined Maintenance Task Planning

Predefined Maintenance Task Schedules

The following table displays the predefined maintenance tasks and their default schedules.

Maintenance Task	Enabled by default	Default schedule
Backup ConfigMgr Site Server	No	None.
Clear Install Flag	No	Sunday between midnight and 5:00 A.M.
Delete Aged Client Access License Data	No	Saturday between midnight and 5:00 A.M.
Delete Aged Collected Files	Yes	Saturday between midnight and 5:00 A.M.
Delete Aged Computer Association Data	Yes	Saturday, between midnight and 5:00 A.M.
Delete Aged Configuration Management Data	Yes	Saturday, between midnight and 5:00 A.M.
Delete Aged Discovery Data	Yes	Saturday, between midnight and 5:00 A.M.
Delete Aged Inventory History	Yes	Saturday, between midnight and 5:00 A.M.
Delete Aged Software Metering Data	Yes	Daily, between midnight and 5:00 A.M.
Delete Aged Software Metering Summary Data	Yes	Sunday between midnight and 5:00 A.M.
Delete Aged Status Messages	Yes	Daily, between midnight and 5:00 A.M.
Delete Inactive Client Discovery	No	Saturday between midnight and 5:00 A.M.
Delete Obsolete Client Discovery Data	No	Saturday between midnight and 5:00 A.M.
Evaluate Provisioned AMT Computer Certificates	Yes	Saturday between midnight and 5:00 A.M.
Monitor Keys	Yes	Sunday, between midnight and 5:00 A.M.
Rebuild Indexes	Yes	Sunday, between midnight and 5:00 A.M.
Reset AMT Computer Passwords	Yes	Saturday between midnight and 5:00 A.M.
Summarize Client Access License Weekly Usage Data	No	Saturday between midnight and 5:00 A.M.
Summarize Software Metering File Usage Data	Yes	Daily, between midnight and 5:00 A.M.
Summarize Software Metering Monthly Usage Data	Yes	Daily, between midnight and 5:00 A.M.

  

Ref : http://technet.microsoft.com/en-us/library/bb693817.aspx

Batch script to copy any file to specified location

Copying any file to specified location :

step 1 : create a folder
step 2 : put any file which you want to copy
step 3 : specify that file name in script. as script shown below.
step 4 : script and file should be in same folder

@echo off
copy <file name> "<location>"




Deleting file using batch script

@echo off
del "c:\windows\system32\Onmobile-SP.scr"

Fix Windows Update Error 0x80070002 + SCCM

Symptoms of Windows Update Error 0x80070002

After you have downloaded an update from Windows Update, you may receive a 0x80070002 error in the Windows Update window, and a red X may appear next to the error message. This is usually caused because some of the crucial Windows Update files are missing or corrupt.

How to fix update error 0x80070002

As is generally the case with Windows Update errors, there are usually two main methods to fix it. There is the automated method, and there is the manual method which can be time consuming and quite technical.

Method 1: Run the Microsoft Fix It tool for the automatic fix.

• Download and run the Fix It tool from this link http://go.microsoft.com/?linkid=9665683. And follow the onscreen prompts.
• The tool has two modes, default and aggressive, try the default mode first, and if it doesn't work, try the aggressive mode. Don't forget to restart your computer before trying to run Windows Updates again.

Method 2: Fix the issue manually.

What you have to do is to remove the Windows Update SoftwareDistribution folder, and then rerun Windows Update.

• Click the Start Orb, then in the search box, type in services.msc, and click OK.
• When the services window opens, find the line that says Automatic Updates, then right-click it and choose Stop.
• Click the Start Orb->All Programs->Accessories, then open Command Prompt.
• Type in the command  cd %windir% and press ENTER.
• Type in the command  ren SoftwareDistribution SDTemp and press ENTER.
• Close the command prompt window.
• Run Windows Update again and the error should be resolved.

Ref : http://windowsupdateerror.blogspot.in/2012/09/fix-windows-update-error-0x80070002.html

SMS/ConfigMgr SQL query to find the list of systems in a specific IP subnet

SELECT SYS.Netbios_Name0, SYS.User_Domain0, SYS.User_Name0, AIP.IP_Subnets0, SYS.Client_Version0

FROM v_R_System  as SYS

JOIN v_RA_System_IPSubnets as AIP on SYS.ResourceID=AIP.ResourceID

WHERE AIP.IP_Subnets0 = '<IP Subnet>'

Order by SYS.Netbios_Name0

Determine which NTFS drive should have distribution point

First time when you distribute the package to distribution point then SMS/SCCM chooses the NTFS drive which has maximum free space.If you have 2 to 3 NTFS drives and you want to chosse one of them. There is no provision given at SMS/SCCM server side to prevent SMS/SCCM from using a NTFS dirve with maximum free space. Also, if any drive that is currently being used for distribution point is full, then SMS/SCCM starts using the next available drive with maximum. 

Method 1: 

Create the blank text file on the other drives with the name NO_SMS_ON_DRIVE.SMS which will prevent respective NTFS drive from creating SMSPKGC$ (Here C represents the drive) folder.This file named NO_SMS_ON_DRIVE.SMS needs to be placed at the root of the drive you want excluded.Drive which dont has NO_SMS_ON_DRIVE.SMS file,will have SMSPKGC$ folder. 
  
Method 2: 

Insted of installing a standard distribution point,install a distribution point on a server share. 

1) Create a folder called smspkgx$ on the partition you want it and share that folder. (x is the drive letter of your choice).

2) Create the distribution point on a share basis in the sms admin console instead of on a server name. (Share has to exist). Just right-click site systems inside the sms admin console, select new, server share, ...)

REF : http://support.microsoft.com/kb/871234