Failed to get Web DAV settings on the machine (0x80070003) Error in MPController.log

Hi Floks ,

I was working on my lab environment one day and though to upgrade my sccm 2007 to R2. I was running sccm on windows 2008 OS. I start my upgrade task and everything went as per the plan. I was very happy to test some stuff on R2 , but when i opened my console i was shocked to see that MY MP was floating with all red errors.. :( . To check what was wrong with my MP i opened the MPController.log.

Below lines gave the answer.... and the issue was "WEBDEV Settings" :(:( 

Installing the SMSMP
Passed OS version check.
IIS Service is installed.
 checking WebDAV configuraitons
Failed to get WebDAV settings on the machine (0x80070003)

I was quite confused, i was sure i configured correctly and even it was right. But the issue was "WebDAV Authoring Rules" that i missed to enable it.

You will get this error only in stages.

1.  If WebDav is not installed or it is not configured correctly.

2.  RDC feature is not installed or got corrupted.

====================================================================

 

Resolution

1. To support management point and BITS-enabled distribution point site system computers we must install and configure WebDAV for IIS 7.0 properly.

1. Depending on your server operating system platform, download either the x86 or x64 version of WebDAV    
2. Downlaod link :  http://go.microsoft.com/fwlink/?LinkId=108052.
3. Depending on which version was downloaded, run either thewebdav_x86_rtw.msi or the webdav_x64_rtw.msi file to install WebDAV IIS 7.0 extensions.
4. Enable WebDAV and create an Authoring Rule, as follows:
   
   1. Navigate to Start / All Programs / Administrative Tools /Internet Information Services (IIS) Manager to start Internet Information Services 7 Application Server Manager. In Server Manager, select the Features node, and click Add Features to start the Add Features Wizard.
   2. In the Connections pane, expand the Sites node in the navigation tree, and then click Default Web Site if you are using the default Web site for the site system or SMSWEB if you are using a custom Web site for the site system.
   3. In the Features View, double-click WebDAV Authoring Rules. 
   4. When the WebDAV Authoring Rules page is displayed, in theActions pane, click Enable WebDAV.
   5. After WebDAV has been enabled, in the Actions pane, click Add Authoring Rule.
   6. In the Add Authoring Rule dialog box, under Allow access to, click All content. 
   7. Under Allow access to this content to, click All users. 
   8. Under Permissions, click Read, and then click OK. 
5. Change the property behavior as follows:
   
   1. In the WebDAV Authoring Rules page, in the Actions pane, click WebDAV Settings. 
   2. In the WebDAV Settings page, under Property Behavior, setAllow anonymous property queries to True. 
   3. Set Allow Custom Properties to False. 
   4. Set Allow property queries with infinite depth to True. 
   5. If this is a BITS-enabled distribution point, under WebDAV Behavior, set Allow hidden files to be listed to True.
   6. In the Action pane, click Apply. 
6. Close Internet Information Services (IIS) Manager.

2. Make sure that Remote Differential Compression feature for site server and branch distribution point computers should be added!!!!!

In Server Manager, on the Features node, click Add Features to start the Add Features Wizard.

1. On the Select Features page, select Remote Differential Compression, and then click Next.
2. Complete the rest of the wizard.
3. Close Server Manager

Finally The last step that fixed everything.

As i was not ready to wait for default 60 min time to auto configure MP component. so i restarted the se SMS_SITE_COMPONENT_MANAGER service on sccm server and the log shows: "SMS Site Component Manager successfully installed MP component on this site system."

Hope This Will Help!!!!

Amarpal Singh

Crash.log that help you to know the reason for Configuration Manager 2012/2007 and SMS 2003 unhandled exceptions

What is an unhandled exception?

In almost every Configuration Manger crash there is an exception involved. An exception occurs when an instruction is attempted but fails for some reason (e.g. an Access Violation), so when an exception occurs we need information about that exception or what was in memory when the exception occurred.

Most applications have their own exception handling code and Configuration Manager is no different. Configuration Manager has its own exception handler that is designed to collect certain predefined data such as thread stack information and other data when the exception has occurred. Note that it is also sometimes necessary to do live debugging or post mortem debugging when an application/OS crashes using the Windows debugging tools.

Components that could cause unhandled exception

SMS Executive: SMSEXEC.EXE is the main service that calls many threads. Any running thread will terminate SMS_EXECUTIVE service if an exception occurs in the thread, and the Configuration Manager site server exception handler will collect the required data.

Data collected when Configuration Manger site server encounters an exception

- A log file (CRASH.LOG) that details the thread stacks and very basic information.

- All current .LOG files from the \LOGS folder. These are saved in the \LOGS\CRASHDUMPS\YYYYMMDD_000XX folder where YYYYMMDD is the date when the crash occurred and XX represents the number of crashes in that day.

- An individual thread log for every component at the time of the failure. These files have no extension but can be viewed in any text editor or SMS Trace or CM Trace.

Depending on the nature of crash and current memory conditions, not all of the above information will be captured. Here’s an example:

With this in mind, here are some steps you can do if you experience one of these crashes:

1. Check the LOGS\CRASHDUMPS\CRASH.LOG file and make a note of the failing component and thread ID.

2. Locate the <component>_thread_<thread number> in \Logs and open in a text editor such as Notepad.

3. Look at the bottom of the log to identify the last thing the component was doing when the crash occurred.

4. Take corrective action based on what was occurring. Often there will be a reference in the log to a specific file or object that is causing the crash.

NOTE If nothing useful is found in the log file, a memory dump could be used to analyze the issue deeper.

In our example, examining the CRASH.LOG shows the following:

EXCEPTION INFORMATION
Time = 08/29/2012 17:28:47.406
Service name = SMS_EXECUTIVE
Thread name = SMS_AD_SYSTEM_DISCOVERY_AGENT
Executable = D: \Microsoft Configuration Manager\bin\i386\smsexec.exe
Process ID = 11789 (0x2E0D)
Thread ID = 13565 (0x33FD)
Instruction address = 77bd8efa
Exception = c0000005 (EXCEPTION_ACCESS_VIOLATION)
Description = "The thread tried to read from the virtual address 00000000 for which it does not have the appropriate access."
Raised inside CService mutex = No

Examining the corresponding <component>_thread_<thread number> we can see the following:

Starting the data discovery. SMS_AD_SYSTEM_DISCOVERY_AGENT
INFO: Processing search path: 'LDAP://OU=xxx ,OU=xx,DC=GLOBAL,DC=xx,DC=xx'. SMS_AD_SYSTEM_DISCOVERY_AGENT
INFO: Full synchronization requested SMS_AD_SYSTEM_DISCOVERY_AGENT
INFO: DC DNS name = 'FQDN' SMS_AD_SYSTEM_DISCOVERY_AGENT

So by looking at this it becomes apparent that the Active Directory System Discovery method is causing the exception to occur. From this point you could continue troubleshooting the cause of the issue with Active Directory System Discovery, or perhaps if this is a secondary site you could disable the Active Directory System Discovery if you do not need it.

Hopefully you’ll never encounter one of the exceptions but at least now you might be able to get a head start on determining the cause of your crash.

 Hope this will help you.

Amarpal Singh Sandhu

Old system still exist in SCCM console..

Solution to get Rid fo them .

1. Enable maintanance task to delete the system and check the log files smsdbmon.log to monitor the activity.

OR

2.  I suggest you create collection of computers you haven't heard from in x number of days, and use delete special to get rid of all the objects. below query will return all objects that haven't reported any hw inventory for a month.
Servers that haven’t scanned for hw inventory in 7 days or more:
select * from SMS_R_System inner join SMS_G_System_WORKSTATION_STATUS on SMS_G_System_WORKSTATION_STATUS.ResourceId = SMS_R_System.ResourceId where SMS_R_System.OperatingSystemNameandVersion like "%server%" and (DateDiff(day, SMS_G_System_WORKSTATION_STATUS.LastHardwareScan, GetDate()) >=30)

Any above option can be used to rid of old system that dosn,t exist anymore.

Cheers!!!!!

Move all your default collection using script!!!

Thanks to Richard for this excelent script for moving the collection.

Have you always been annoyed by the default collections cluttering up the view in your ConfigMgr console, well there’s a way that you can store them away under a separate collection. I found this blog post (http://verbalprocessor.com/2009/03/20/how-to-move-collections-in-configmgr) a while ago solving the problem. But hey I’m a lazy guy and after all, I’m installing lots of ConfigMgr servers out at customer sites, so automation is the key that drives lazy admins, right? So in this post I will walk you through using a script that can move collections based on either the name or comment of the collection/collections you want to move.

First up, you need to know some stuff from your environment, like the name of your server and site code. Also you need to know the Collection ID where you want to save the collection to. Start out by going to your ConfigMgr console and locate the site code, you will find it here:

 

Then create a new collection and localize the Collection ID, like this: 

 

Next up download the script (from the bottom of this post) and save it to an appropriate location on your site server, in this case I saved it to the location F:\UTV\Scripts. Then edit the section with site server (I run it on the ConfigMgr server so the name is set to ".") and site code plus the Collection ID of your newly created collection in the script. Also, in this case I will move the collection based on the name they have, so in the script I enter “All%”, which basically means all collections that starts with All… something.  
 
Start an elevated CMD prompt and run the script like below: 



Your output should look similar to this:



Finally refresh you console and your should end up like this:



Hope this help, you can also move collection based on comments just edit the beginning of the script something like this (based on the fact that you have collections with comment like Move).  




The script is here:

just rename it after putting it in notepad.

'
' Script created by: Richard Ulfvin
' http://www.filemilk.se/
'
' Disclaimer:
' This script is provided "AS IS" without express
' or implied warranty of any kind.
'
' Version 1.0
'
Option Explicit
Dim sConfigMgrServer : sConfigMgrServer   = "."
Dim sConfigMgrSiteCode : sConfigMgrSiteCode  = "C01"
Dim sCollectionName : sCollectionName    = ""
Dim sCollectionDesc : sCollectionDesc   = ""
Dim sParentCollectionID : sParentCollectionID  = ""
Dim oConfigMgr, sResult
ConnectToConfigMgr oConfigMgr
MoveCollection oConfigMgr, sCollectionName, sCollectionDesc, sParentCollectionID
Function ConnectToConfigMgr (oConfigMgr)
 'Attempts to use the provided information to connect to the ConfigMgr environment.
 Dim oWMILocator

 On Error Resume Next

 Set oWMILocator = CreateObject("WbemScripting.SWbemLocator")
 Set oConfigMgr = oWMILocator.ConnectServer(sConfigMgrServer, "root\sms\site_" & sConfigMgrSiteCode)
 If Err <> 0 Then
  sResult = "Error: " & Err.description
  Wscript.echo sResult
  Err.Clear
  Wscript.Quit(0)
 Else
  sResult = "Successfully connected to ConfigMgr"
  Wscript.echo sResult
 End If

 On Error Goto 0

End Function
Function MoveCollection(oConfigMgr, sCollectionName, sCollectionDesc, sParentCollectionID)
 Dim cCollections, oCollection, oCollectionRelation, sCollectionID, oCollectionLink, cCollectionLinks
 ' Obtain the collection ID of the collection.
 If sCollectionName <> "" Then
  Set cCollections = oConfigMgr.ExecQuery ("SELECT * FROM SMS_Collection where Name LIKE '" & sCollectionName & "'")
  Wscript.echo "Using Collection Name for parameter: " & sCollectionName
 ElseIf sCollectionDesc <> "" Then
  Set cCollections = oConfigMgr.ExecQuery ("SELECT * FROM SMS_Collection where Comment LIKE '" & sCollectionDesc & "'") 
  Wscript.echo "Using Collection Comment for parameter: " & sCollectionDesc 
 End If

 For each oCollection in cCollections
 
  sCollectionID=oCollection.CollectionID
  Wscript.echo "Found collection with name: " & oCollection.Name & " and CollectionID: " & oCollection.CollectionID
 
  ' Attempts to move the collection into the desired parent collection.
  Set oCollectionRelation = oConfigMgr.Get("SMS_CollectToSubCollect").SpawnInstance_()
  oCollectionRelation.parentCollectionID = sParentCollectionID
  oCollectionRelation.subCollectionID = sCollectionID
  oCollectionRelation.Put_
  Wscript.echo "Moving: " & oCollection.Name & " to rootcollectionID: " & sParentCollectionID
 
  'Delete any prior collectionlink.
  Set cCollectionLinks = oConfigMgr.ExecQuery ("SELECT * FROM SMS_CollectToSubCollect WHERE subCollectionID = '" & sCollectionID & "' AND NOT parentCollectionID = '" & sParentCollectionID & "'" ) 
  For each oCollectionLink in cCollectionLinks
   Wscript.echo "Found collection link for ID: " & oCollectionLink.subCollectionID & " with parrent collectionID: " & oCollectionLink.parentCollectionID & " to delete!"
   oCollectionLink.Delete_
  Next
 
 Next

End Function

Cheers!!!!!!

Remote Tools continues to become disabled even if after setting is to enable it on SCCM server.

Senario :

On some ofmy clients remote control was disable where as on site wise base it is kept to be enabled. When i tryied to take remote of one of my client machine . it gave me error remote control is disabled. Even after reinstalling the client the problem was same. it was getting disabled automatically.

Solution :

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Client\Client Components\Remote Control]
"Enabled"=dword:00000001

All my affected machines were still set to 0. This edit is done on the client machines.

Hope this will help!!

Cheers!!!!!

Collection take long time to refresh???

Cause :

A long delay occurs when you click "Refresh" to view the latest membership in a dynamic collection on a System Center Configuration Manager 2007 SP2 site server !!

Reason :

This issue occurs because Collection Evaluator maintains a first-in, first-out (FIFO) queue to handle the collection evaluation requests.

When you click Refresh to view the latest membership of a collection, this request is put at the end of a FIFO queue. If the number of previous requests is very large, Collection Evaluator requires a long time to complete the previous requests. Therefore, a long delay occurs before you view the updated results in the Configuration Manager console.

Solution :

Install SCCM2007-SP2-KB982400-ENU.msi KB.

Pre-Req :

To apply this hotfix, you must have System Center Configuration Manager 2007 Service Pack 2 (SP2) installed.

Cheers!!!! 

HTTP 500 Error at Secondary Site Management Point

Most commonly when I have seen HTTP 500 errors on a management point it’s been a SQL permissions issue. Today I ran across another problem that resulted in HTTP 500 errors when testing a management point on a child secondary site. in an effort to resolve the issue I removed the MP using the console on the central site then I noticed that the change was never reflected at the child primary to which to secondary site reports. I opened the sitectrl.ct0 file at the secondary site and I saw there was a delta change reflecting the removal of the MP however that change was not being sent up to the parent site for some reason. To test I made a copy of the sitectrl.ct0, renamed it to sitectrl.ct2 and copied it to the parent sites hman box. The hman.log showed that the site control file serial number was wrong and the file was rejected.

Editing the site control file manually is very unsupported. This is where you should really call CSS.

Of course I figured it was broken already so I may as well take a chance on it before calling support. I took note of the expected serial number version in the HMAN.log at the primary site. I then stopped the sms executive and site component manager services at the secondary site. Open the site control file in notepad, changed the serial number to the number expected by the primary site and saved the file. Next copy the file and rename the extension to ct2. Copy the renamed file to the hman inbox at the primary site and watch the hman.log. You should see the file process successfully this time.

Wait a few minutes then reinstall the management point from the console at the central site. After you see it’s been installed successfully by viewing the mpsetup.log test again using MPList and MPCert.

Cheers!!!!!!! 

ConfigMgr (SCCM) – New Site to Site data replication flow in SMS 2003 and ConfigMgr 2007 explained

Thanks for Excellent write up on replication process of ConfigMgr in details from Terry McKinney and to Anoop for sharing this  :)

New deep-dive document: Component details and data flow for site-to-site replication in SMS 2003 and Configuration Manager 2007

=====

NOTE: Question marks (???) in the text below indicate random character generation by SMSExcec thread processing.

SMSExec thread component on source site initiates replication request

SMSExecutive thread component that is requesting data replication places the data to be replicated in replmgr.box\outbound\low OR replmgr.box\outbound\normal OR replmgr.box\outbound\ high folder. Low (3), normal (2), and high (1) specify replication priority requested by the SMSExec thread that requests replication.

Replmgr:

Replication Manager (ReplMgr) scans the three folders listed above for incoming data. Replmgr prepares the job source files by combining data files destined for replication to a given site in the \replmgr.box\process\<destinationsitecode>_<priority> folder (i.e., XYZ_2). If there are no pending replication requests to a given site that have the same replication priority, Replmgr implements steps A and B listed below. It there are pending replication requests to that site that have the same replication priority that are already scheduled for replication, data for new request(s) is held in the Replmgr.box\process\<destinationsitecode>_<priority> folder. Data for the new request(s) will remain in the Replmgr.box\process\<destinationsitecode>_<priority> folder until the pending same-priority request completes data replication OR the new replication request(s) reaches 6 hours in age. At this time, Replmgr will implement steps A and B listed below. If a replication job of the same priority and destination site is still pending, ReplMgr implements steps A and B below to create an additional same-priority replication request for that site.

A. Data to be replicated is moved to \replmgr.box\ready\<priority>_??????.<destinationsitecode> (i.e., 2_SKEJFS.XYZ).  This folder is referenced in log files as the "transfer root".

B. ReplMgr then creates a .JOB file in the \Schedule.box folder.

Scheduler:

At the top of the Scheduler process loop (except on service startup) Scheduler activates any pending jobs by completing the following steps:

A. Compresses all files in the transfer root (i.e., \replmgr.box\ready\2_SKEJFS.XYZ) into a single package file and writes this file to \schedule.box\tosend\<job id>.P??.

B. Creates a destination site despooler instruction file in \schedule.box\tosend\<job id>.I?? to be transmitted immediately after the package file created in step A is transmitted.

C. Creates a send request in the \schedule.box\requests folder (<priority>_???<originatingsite>.SRQ) (i.e., 2_5ZKABC.SRQ).

D. Determines if the package and instruction file needs to be routed through an intermediate child site. If so, a routing instruction file is created (RT??????.INS) for the send request.

E. Schedules the send request by moving it into an appropriate sender outbox. Each installed sender type creates its own folder under schedule.box\outboxes. The most common sender outbox is schedule.box\outboxes\LAN.

Sender:

1. Sender transmits the package file and then the instruction file to the remote site by completing the following steps:

A. Renames the send request (<priority>_???<originatingsite>.SRQ) to (<priority>_???<originatingsite>.SRS (changes the filename extension to .SRS)

B. Transmits the package (\schedule.box\tosend\<jobid>.P??) file to the remote site Despoolr.box\receive folder (the SMS_SITE share) and renames it to <sendrequestid>.PCK

C. Transmits the accompanying instruction file (\schedule.box\tosend\<job id>.I??) to the same location and renames it to <sendrequestid>.INS

D. Flags the <priority>_???<originatingsite>.SRS file with a "sending complete" flag.

E. Creates a \schedule.box\<sendrequestid>.DWS (done with sending) file.

Replication component processing at the destination site Despoolr.box\receive folder)

Despoolr:

The Despooler process first checks the signature on the replicated files. If signed correctly, despoolr decompresses the instruction file and implements the instructions contained within that file – to decompress the package into the \replmgr.box\incoming folder in this case.

ReplMgr:

Replication Manager analyzes incoming files and replicates the objects to appropriate inbox folders. The appropriate inbox folder is specified by the component on the source site server that began the replication process. Inbound replication jobs that use transactions must bear a transaction ID that is greater than the existing number for that object type that is contained in the sitecode.trs present on the destination site. If this condition is met, the transaction is considered valid and the inbound replication objects are passed to the destination component/inbox. If this condition is not met, the transaction is considered invalid and the replication objects are discarded by Replication Manager.

Post - replication cleanup on originating site:

Scheduler:

A. Updates the corresponding job status to "complete" when it finds the \<sendrequestid>.DWS during its

processing cycle.

B. Performs cleanup - deletes the related package and instruction files in the \schedule.box\tosend folder

C. Deletes the transfer root folder (i.e., replmgr\ready\2_SKEJFS.XYZ)

D. Marks the send request for deletion

ReplMgr:

After the transfer root has been deleted, pending replication requests with the same priority and destination site that are less than 6 hours in age can be created. Note that if there are existing jobs of the same priority and with the same destination site that are older than 6 hours, ReplMgr will request scheduling an additional replication job of the same priority for replication to that site.

Scheduler:

A. Deletes completed send requests when it finds the associated <job_id>.dws file for that job during its processing cycle.

B. Deletes the completed job files (minimum cycle: once per hour, maximum cycle: once per process loop).

Daily Best Practice for Healthy SCCM server

In order to make sure that you sccm environment should run smoothly always follow the below best practice

Ø  Administrative Checklist for Configuration Manager 2007

1.       Go to the site component and check SMS _SITE_BACKUP Component and last date when it was run and was it successful. I my experience I have seen that even if backup fail the SMS _Site_ Backup will not show it as fail. To be on safer side I recommend checking smsbkg.log on server.

2.       Expand the Site Status and look for error or warning in the site by check Component Status or Site System Status.

3.    Check the Processor :

The processor point status check is a check on the relevant servers Task Management status and the current status of the Processor on that server. If for some reason the processor is running high on utilization then this should be addressed to ensure that the issue is not a serious one.

To do this check the status of that sites Components and Site System Status information as above.

If the process is running ok (hovering between 30 and 60% generally) then a simple green box entry should be added to the Daily Checks spreadsheet as before,

However if there are failings on the processor checks (utilization is running very high into the 90 to 100% and steady) then these should be added into the spreadsheet as red boxes again as before which should also include an inserted comment explaining the issue and what you are doing to resolve the issue.

Important: If the processor is maxing out at around 90 to 100% on Primary site servers, check the following to ensure that is no excessive traffic to and fro the server cross the LAN / WAN

It’s also worth noting that a check on the Primary Site Servers SQL instance will be worth a look; as if SQL itself is struggling to process data quickly enough into the SQL Site database then this will cause the server to on occasions max out on the CPU.

4.       Check the size of SMS folder Structure to make sure that it is not flooding with any error or files.

         SMS inbox size andAlso\AUTH\DDM.BOX

5.       Check the IIS log Files :

Check the properties of the c:\windows\system32\logfiles\W3SVC1 folder

If the size of the folder (contents) exceeds 200Mb, then simply select all but the last 2 log entries (filter the display list by Date modified) and delete the log files. Keep the log files since last week and delete the rest

6.    SCCM Server Disk Space Check : Make sure that server should have 20% minimum disk space if you find that the space is less then just clean up the space to make sure that SCCM should not face any space issue.

7.    SCCM MP Check: To make sure that MP is working fine check the mpcontrol.log and also you can use the MP troubleshooter tool to check the health of MP.

8.    Removing the obsolete Systems: Create the collection with the query to collect all the obsolete systems in the environment.

Note: Always use delete special option while deleting the systems

Inaccurate software metering reports are generated on a primary System Center Configuration Manager 2007 SP2 site server

Q. Inaccurate data returned for software meeting ?

Solution :

The software metering processor on a primary Microsoft Systems Center Configuration Manager 2007 Service Pack 2 (SP2) site server may return an invalid file size when it handles the software metering summarization data (.sum file) from a child site server.

The issue causes duplicate file entries in the SoftwareFile table. Additionally, one entry has an invalid file size (most likely 0). Inaccurate software metering reports are generated because of this issue.

This issue occurs because the software metering processor on the primary site server does not correctly handle the file size data from a child site server.

For all the details and a download link please see the following KB article:

KB2534671: Inaccurate software metering reports are generated on a primary System Center Configuration Manager 2007 SP2 site server 

Deletion of Orphaned Distribution Points

 Q. The servers hosting the DP shares were decommissioned without us knowing. Once we found out, we deleted the DPs from all associated Packages and then deleted them from Site Systems on their appropriate Primary Site. However, because the servers were no longer around, things weren't totally cleaned up. Every day I would see entries in my Central Primary Site server's distmgr.log where SMS was not able to delete specific packages from these orphaned DPs.

Solutions :

Delete action for previously deleted package server '["Display=\\servername01\sms2003dp\"]MSWNET:["SMS_SITE=ABC"]\\servername01\sms2003dp\' for package 'ABC00002' will be ignored.
Delete action for previously deleted package server '["Display=\\servername02\sms2003dp\"]MSWNET:["SMS_SITE=ABC"]\\servername02\sms2003dp\' for package 'ABC00002' will be ignored.

 Using SQL Server Management Studio, the Microsoft technician and I used the following queries to find if the DPs were still in our databases:

SELECT * FROM PkgServers WHERE NALPath like '%servername01%'
SELECT * FROM PkgStatus WHERE PkgServer like '%servername01%'

Once we confirmed these queries returned entries for the orphaned DPs (and ONLY the orphaned DPs) we checked to make sure we had a valid SMS backup. Once that was confirmed, we ran a delete query to clean things up:

DELETE FROM PkgServers WHERE NALPath like '%servername01%'
DELETE FROM PkgStatus WHERE PkgServer like '%servername01%'

And like that, I no longer have activity from non-existant DPs.


Cheers!!!!!!!!!!

Configuration Manager 2007 Client Status Reporting Stoped.

Q. I installed the Configuration Manager 2007 Client Status Reporting (CSR) on my central site server but when i started the service via CSR console i get in UIconfig.log the message below :
Failed to start the service due to "The dependency service does not exist or has been marked for deletion"
My set up is  SCCM R3 SP2 ,Windows 2008 R2 . In info tab i get this :

The ConfigMgr Client Status Reporting Service is stopped. This service needs to be running in order to perform monitoring operations.

Possible reasons:
1. The service is not installed properly.  If the service is not installed, initiate a repair from the Add Remove Programs control panel applet.
2. The service credentials are invalid. Enter valid credentials for the service in the "Site Settings" tab and click the "Apply" or "OK" button to start the service.
3. The service cannot start using the specified credentials. Ensure that the Client Status Reporting Service has local administrative rights and has the "Log on as a service" local security setting rights.

Final Solution :

I made a bad configuration on SQL instance ! due to which it was not working  So I solve the problem and it started working

Cheers!!!!!!!

Management Point Installation Failure + Missing MP Log Files

Q. I have tried to install the MP on these sites via Site Management -> [Site] -> Site Settings -> Site Systems -> [Site Server] -> New Roles; this wizard runs through without errors, but once its complete nothing more happens. No MP appears on that site, and no entry for SMS_MP_CONTROL_MANAGER appears under 'Site Status' for the secondary site also unable to install the manully on secondary server.

Solution :

The problem was being caused by an incorrect sender address from the primary site to these secondary sites; (caused by setting up secondary sites in these locations in the past, but installing SCCM on a different server).
So it seems that if youre having problems with installing a management point on a secondary site, and the symptoms include missing mp log files, and missing entries for the management point under Site Status, it's worth checking that your sender addresses are correct.
Site Management > [Primary Site] > Site Settings > Addresses > Right-click the address > properties
in my case the Site server name was set to the wrong server, so to fix i deleted this address and created a new one. once the new address was in place, i was able to add the management point site role and it installed correctly.

Cheers!!!!!!!!

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, ...)

Microsoft Article: http://support.microsoft.com/kb/871234

How to verify Management Point is working fine in SCCM 2007

Verify Management Point Installation Logs
1. Verify MPsetup.log. Make sure MP is install successfully, if not resolve the problem. If you find any problem in MPSetup.log, then verify MPMSI.log for more information on the issue.

MPSetup.log:

<12-16-2008 17:12:09> Installing the SMSMP
<12-16-2008 17:12:09> Passed OS version check.
<12-16-2008 17:12:09> IIS Service is installed.
<12-16-2008 17:12:09> SMSMP already installed (Product Code: {3945C886-9779-4280-B537-AB8E62A0878E}). Upgrading/Reinstalling SMSMP
<12-16-2008 17:12:09> New SMSMP is a new product code {{7AF53388-F428-4A8B-8F20-DBB4851E3424}}. This is a major upgrade.
<12-16-2008 17:12:09> Enabling MSI logging. mp.msi will log to D:\SMS\logs\mpMSI.log
<12-16-2008 17:12:09> Installing D:\SMS\bin\i386\mp.msi REINSTALLMODE=vmaus CCMINSTALLDIR=”D:\SMS_CCM” CCMSERVERDATAROOT=”D:\SMS” USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
<12-16-2008 17:15:59> mp.msi exited with return code: 0
<12-16-2008 17:15:59> Verifying CCM_CLIENT virtual directory.
<12-16-2008 17:15:59> Website path is IIS://LocalHost/W3SVC/1.
<12-16-2008 17:15:59> Connecting to IIS.
<12-16-2008 17:15:59> CCM_CLIENT is currently D:\SMS\Client
<12-16-2008 17:15:59> Installation was successful.

2. Check IIS and make sure that you have virtual directory named SMS_MP under default website.
3.Check mpcontrol.log and find if you have below sucesses status message (Status Code 200). ( I use tracert32 to read log files)

Call to httpsendrequestsync succeeded for port 80 with status code 200,text ok
http test request succeeded

successfully performed Management Point avaialbility check against local computer

4. Fianlly for testing run this on IE from any client and from the server itself and you sould get the results mentioned.

  a) Run http://<MP Name>/sms_mp/.sms_aut?mplist

   This returns a list of MP's installed on this site including the secondary site MP's.

  b) Run http://<MP Name>/sms_mp/.sms_aut?mpcert

   This returns a long list of numbers and letters.

Output of Step a

- <MPList>
- <MP Name="smsserver1" FQDN="smsserver1.example.abc.com">
<Version>6487</Version>
<Capabilities SchemaVersion="1.0" />
</MP>
- <MP Name="smsserver18" FQDN="smsserver18.example.abc.com">
<Version>6487</Version>
<Capabilities SchemaVersion="1.0" />
</MP>
- <MP Name="smsserver2" FQDN="smsserver2.example.abc.com">
<Version>6487</Version>
<Capabilities SchemaVersion="1.0" />
</MP>
- <MP Name="secondary1" FQDN="secondary1.example.abc.com">
<Version>6487</Version>
<Capabilities SchemaVersion="1.0" />
</MP>
</MPList>

More Info on MP and resolving issues:

http://technet.microsoft.com/en-us/library/cc180197.aspx
http://technet.microsoft.com/en-us/library/cc180195.aspx 

System Center Configuration Manager 2007 backups fail with Win32 Error = 145

Microsoft System Center Configuration Manager 2007 backups may fail if other VSS-aware backup software is scheduled to run concurrently. In this scenario, the Smsbkup.log will show entries similar to the following:

Deleting E:\SMSbackup\SiteServer\SMSServer\inboxes\auth\statesys.box\incoming, FAILED, Win32 Error = 145
Deleting E:\SMSBackup\SiteServer\SMSServer\inboxes\auth\ddm.box, FAILED, Win32 Error = 145
Deleting E:\SCCMBackup\Backup, FAILED, Win32 Error = 145
Failed to delete the contents of the backup folder. Error Code = 0x0 SMS_SITE_BACKUP
Error: Deleting the existing files in the backup location failed... SMS_SITE_BACKUP
SMS site backup failed. Please see previous errors. SMS_SITE_BACKUP
SMS site backup service is stopping. SMS_SITE_BACKUP

These errors can occur if the Volume Shadow Copy Service (VSS) provider is in use by another process. Configuration Manager Backup expects to have exclusive access to these resources when performing a backup.

To prevent these errors, configure Configuration Manager Backup to start at a time outside the window for other backup jobs on the server. The schedule for this can be found in the Configuration Manager Console under Site Management -> Site Code -> Site Settings -> Site Maintenance -> Tasks -> Backup ConfigMgr Site Server.

For all the details and the latest version of this document please see the following new Knowledge Base article:

KB2387913 - System Center Configuration Manager 2007 backups fail with Win32 Error = 145

Rebuilding and reinstalling the WMI Repository

If you experience behavior when using WMI, such as application errors or scripts that used to work are no longer working, you may have a corrupted WMI repository. To fix a corrupted WMI repository, use these steps:

Windows XP and Windows Vista

Click Start -> Run and type CMD.EXE
Note: In Windows Vista, you need to open an elevated Command Prompt window. To do so, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.

Type this command and press Enter:

net stop winmgmt

Using Windows Explorer, rename the folder %windir%\System32\Wbem\Repository. (For example, %windir%\System32\Wbem\Repository_bad). %windir% represents the path to the Windows directory, which is typically C:\Windows.

Switch to Command Prompt window, and type the following and press ENTER after each line:

net start winmgmt

EXIT

For Windows XP Service Pack 2 and Service Pack 3

Click Start, Run and type the following command:

rundll32 wbemupgd, UpgradeRepository

This command is used to detect and repair a corrupted WMI Repository. The results are stored in the setup.log (%windir%\system32\wbem\logs\setup.log) file.

For Windows Vista

Open an elevated Command Prompt window. To do so, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
Type the following command:

winmgmt /salvagerepository

The above command Performs a consistency check on the WMI repository, and if an inconsistency is detected, rebuilds the repository. The content of the inconsistent repository is merged into the rebuilt repository, if it can be read.

For Windows Server 2003

Use the following command to detect and repair a corrupted WMI Repository:

rundll32 wbemupgd, RepairWMISetup

Re-registering the WMI components

The .DLL and .EXE files used by WMI are located in %windir%\system32\wbem. You might need to re-register all the .DLL and .EXE files in this directory. If you are running a 64-bit system you might also need to check for .DLLs and .EXE files in %windir%\sysWOW64\wbem.

To re-register the WMI components, run the following commands at the command prompt:

• CD %windir%\system32\wbem
• for /f %s in ('dir /b /s *.dll') do regsvr32 /s %s
• for /f %s in ('dir /b *.mof') do mofcomp %s 

Registering WMI Service itself

Open the command console, type "net stop winmgmt". When you get the warning that other services need to be stopped type 'Y' and continue.

Open 'My Computer' and then go to the folder '%SystemRoot%\System32\WBEM\Repository' and delete that folder.

Reboot your system.

After you login, open the command console, and type the following commands in order: 

winmgmt /clearadap
winmgmt /kill
winmgmt /unregserver
winmgmt /regserver
winmgmt /resyncperf

Note: If this doesn't fix the problem, you need to try reinstalling Comprehensive rebuild method.

Comprehensive rebuild method

Important note: If you've installed a Service Pack, you need to insert your Windows XP CD with Service Pack integration (called as the Slipstreamed Windows XP CD). If you don't have one, you may point to the %Windir%\ServicePackFiles\i386 folder for a recent version of the system files required during WMI repair. Or you may create a slipstreamed Windows XP CD and insert it when prompted.

Click Start, Run and type the following command, and press ENTER:

rundll32.exe setupapi,InstallHinfSection WBEM 132 %windir%\inf\wbemoc.inf

Insert your Windows XP CD into the drive when prompted. Repair process should take few minutes to complete. Then restart Windows for the changes to take effect.

Note that none of the above two methods restore the missing files related to Windows Management Instrumentation (WMI). So, below is a comprehensive repair procedure that restores all the missing WMI modules. In case of missing WMI modules, you may use the following method.

Repair WMI using BAT File:

Most of the WMI problems can be solved by rebuilding the WMI Repository, re-registering the WMI components. To automate this, you could create a BAT file. Copy the following lines to a text file and save it with .BAT extension and run it to fix common WMI issues.

net stop winmgmt /y
%SYSTEMDRIVE%
CD %windir%\system32\wbem
rd /S /Q repository
net start winmgmt
for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s
for /f %%s in ('dir /b *.mof') do mofcomp %%s