I Am ReSpOnSiBlE fOr .........WhAt I aM...........wHaT i Do.....WhAt I hAvE

I've been looking for short notes that facilitate quick understanding knowledge on SCCM 2007. I finally put my efforts to bring a short notes on SCCM 2007 to help those who are already familiar with Systems Management Server (SMS) 2003 and who wish to quickly develop understanding knowledge on 'Microsoft System Center Configuration Manager 2007'. Microsoft SCCM -2007 (ConfigMgr) provides a comprehensive solution for change and configuration management for the Microsoft platform, enabling organizations to provide relevant software and updates to users quickly and cost-effectively, Allows IT staff to monitor and manage the hardware & software in a modern distributed environment. SCCM 2007 Features HW/SW Inventory Software Distribution Software Update Software Metering Operating System Deployment (Image capture/deployment, User State Migration, Task sequence) Manage site accounts tool (MSAC) Asset Intelligence Remote tools NAP Works with Windows Server...

Issue:    Some Clients (specifically Windows 7 and Server 2003 ) stuck at downloading state. Error Message:   I noticed in client machine DataTransferService.log this Error retrieving manifest (0x80070003).  Will attempt retry 2 in 60 seconds. With each retry the wait time was increasing Note : Whenever any issues occurs related to windows updates check the logs first in Windows Update Agent Log File C:\Windows\WindowsUpdate.log Here is what the WindowsUpdate.log has: 2011-08-30 08:53:50:805 1424 1591c PT +++++++++++  PT: Synchronizing server updates  +++++++++++ 2011-08-30 08:53:50:805 1424 1591c PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://SMSWIWSUS.ohsnet.ad.oakhealth.net:8530/ClientWebService/client.asmx 2011-08-30 08:53:50:899 1424 1591c PT WARNING: Cached cookie has expired or new PID is available 2011-08-30 08:53:50:899 1424 1591c PT Initializing simple...

Please find the list of activities which an Administrator needs to check on SCCM site servers to ascertain the performance of SCCM servers. I have categorized it in different task categories: Daily Tasks Weekly Tasks Monthly Tasks Quarterly Tasks Half Yearly Tasks Yearly Tasks Daily Tasks include administrative activities as below: Monitoring Alerts on SCOM web console Ensuring availability of SCCM site servers Monitoring & Controlling SCCM site health status Monitoring & Controlling client health status Ensuring successful backup on all primary servers Monitoring site system’s inbox folder(s) Ensuring ongoing production packages are copied to DPs Monitoring long running queries Monitoring Audit messages Weekly Tasks include administrative activities as below: Delete unnecessary objects Delete unnecessary files from site systems Check disk space on all site systems Check advertisement status Review Package status Review sync between SCCM...

HTTP 500 Internal Server Error when accessing SCCM Reports If you are receiving HTTP 500 Internal Server Error when accessing SCCM Reports via web browser, check the following settings: 1. Make sure that you are not hitting the limit of maximum rows returned by a report query. By default, report viewer in SCCM 2007 is configured to limit the results returned by a report query to 10 000 rows. To change the number of rows returned by a report query, create the Rowcount DWORD value under the HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Reporting registry key. 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. For more information, refer to the following TechNet article: How to Configure the Maximum Rows Returned by a Report Query   2. Increase the ASP response buffer limit size ( aspbufferinglimit ). In IIS 6.0 change ...

Sometimes the most challenging part of the Configuration Manager 2007 can be ensuring that the client successfully reports to the site server. This document will describe step by step instructions to troubleshoot Non-Client Machines.  There are various reasons why a client may not be able to report to even if the SCCM agent is installed on a machine. A few of these reasons with troubleshooting are discussed below: 1. The first thing to check is whether the client is on the network, and if it’s not on the network, does the system even exist?  It’s possible that represents a stale record from AD. 2. Systems NOT on the network:   If the system is not actually on the network, check if it is shutdown, and if so if it’s been shut down for long time.  If yes then first restart the system and then initiate the discovery cycle from the control panel agent properties action TAB . 3. Stale Entries:  When you use AD discovery, the DDRs (Data Discovery Records)...