Logo
programming4us
programming4us
programming4us
programming4us
Home
programming4us
XP
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server
programming4us
Windows Phone
 
Windows Server

System Center Configuration Manager 2007 : Site Maintenance (part 1) - Site Maintenance Tasks

- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019
6/25/2012 4:47:50 PM
In addition to having a solid backup and recovery procedure in place, you also want to maintain the data in your site and site database. There are a variety of concepts to consider when performing site maintenance, including site maintenance tasks, DDR retention, and dealing with obsolete database records.

Site Maintenance Tasks

Site maintenance tasks are a vital part of maintaining your site. After installation and performing other initial configurations, it is imperative you understand and configure these tasks to best suit your particular ConfigMgr hierarchy.

Before making any changes to site maintenance tasks, there are several points about the tasks in general:

  • Site maintenance tasks are set at each individual site and not automatically transferred to any other sites in your ConfigMgr hierarchy.

  • The Transfer Site Settings Wizard, has the capability to copy site maintenance task settings from one ConfigMgr site (or an exported copy of those settings) to any other ConfigMgr site.

  • Some of the site maintenance tasks can cause unnecessary and conflicting processing on the ConfigMgr site. These pitfalls are noted with each task.

  • Several of the tasks perform maintenance on the database, such as deleting old data or summarizing current data. Balance the amount of data manipulated at one time by scheduling the tasks to run more frequently.

Table 1 lists the site maintenance tasks in ConfigMgr 2007. Additional information is also available at http://technet.microsoft.com/en-us/library/bb632595.aspx.

Table 1. Site Maintenance Tasks in ConfigMgr
TaskEnabled by DefaultConfiguration DefaultsDescription
Backup ConfigMgr Site ServerNoNo default scheduleBacking up the ConfigMgr site server is easily one of the most important tasks. After installation, determine the appropriate schedule and configure this task. 
Rebuild IndexesYesEvery Sunday between 12:00 AM and 5:00 AM.Database indexes speed the execution of searches in the SQL database, and most tables in the ConfigMgr database have at least one index. This task evaluates those indexes, and rebuilds them if more than 50% of the data is unique to keep your ConfigMgr site running at peak efficiency. The task drops indexes if the data in the table drops to less than 50% uniqueness. 
Monitor KeysYesEvery Sunday between 12:00 AM and 5:00 AM.Primary keys in the ConfigMgr database maintain relationships between the various SQL tables. This site maintenance task checks the keys to ensure that the associations are valid. 
Delete Aged Inventory HistoryYesDelete data older than 90 days, Saturday after 12:00 AM until 5:00 AM.The Delete Aged inventory History task removes data from the ConfigMgr database after the specified number of days. After a client inventory agent is enabled, clients perform the specified actions and report it back to the ConfigMgr database. This task examines that data and determines if it is older than the number of days specified in the days. Data removed by this task includes data from the Hardware and Software Inventory client agents.
Delete Aged Status MessagesYesEvery day after 12:00 AM until 5:00 AM.This is potentially one of the largest tasks the site server runs. The number of status messages generated by the myriad of site and client components can be high; this task is designed to keep that number in check. This task might run for a long time due to the number of status messages that can be deleted. It is recommended you run this task more frequently to reduce the number of status messages deleted in each pass, and shorten the length of each individual run. 
Delete Aged Discovery DataYesDelete data older than 90 days, Saturday after 12:00 AM until 5:00 AM.When discovery data has reached a specified age, this task removes it from the ConfigMgr database. The task deletes any system that has not been discovered in the specified threshold. A common thought on this is that it refers to a system that has not been discovered by heartbeat discovery; however, that is incorrect. If any discovery method (network, active directory) has discovered the system within the threshold, the system will not be deleted. For example, you can have a system that has been gone from the site for a while but still remains in the collections because Active Directory discovery found it in AD. This can happen in environments where Active Directory is not well maintained.
Delete Aged Collected FilesYesDelete data older than 90 days, Saturday after 12:00 AM until 5:00 AM.The Software Inventory client agent has the capability to collect specific files and store them on the ConfigMgr site server. This task deletes files over a certain age, saving disk space. It also removes data about the collected files from the ConfigMgr database. Collected files are stored in the FileCol subfolder of the sinv.box inbox. If you do not collect files during software inventory, this task is irrelevant.
Delete Aged Software Metering DataYesDelete data older than 5 days, every day after 12:00 AM until 5:00 AM.When both the Software Metering client agent and a Software Metering rule are enabled on a ConfigMgr site server, clients begin to gather and report that data on the specified schedule. This task removes the data from the site server when it reaches a certain age.
Delete Aged Software Metering Summary DataYesDelete data older than 270 days, Sunday after 12:00 AM until 5:00 AM.The Summarize tasks take software metering data and summarize it in the ConfigMgr database. This task removes summarized data over a certain age, keeping only the most current dataset.
Summarize Software Metering File Usage DataYesEvery day after 12:00 AM until 5:00 AM.When this task runs, it combines multiple entries in the ConfigMgr database down to a single record. This saves space in the ConfigMgr database and ultimately helps performance.
Summarize Software Metering Monthly Usage DataYesEvery day after 12:00 AM until 5:00 AM.When this task runs, it combines multiple entries in the ConfigMgr database down to a single record. This saves space in the ConfigMgr database and ultimately helps performance.
Clear Install FlagNoClear client install flag for clients not discovered by heartbeat discovery within past 21 days, every Sunday between 12:00 AM and 5:00 AM.The Clear Install Flag is designed to help clear out stale records from the ConfigMgr database. When a client is installed, a flag is set in the database—marking the computer as installed and current.

The task clears that flag if a Heartbeat DDR is not received in the configured amount of time. As this task is closely tied to Heartbeat discovery, enable the task only if Heartbeat discovery is also enabled.

If the Client Rediscovery period is set lower than the Heartbeat discovery cycle, you can cause clients to reinstall if the Client push installation method is also set. This can lead to unnecessary churn on the clients (as they reinstall over a presumably healthy client) and the site server (DDRs, MIFs, and so on).
Delete Inactive Client Discovery DataNoDelete data older than 90 days, Saturday after 12:00 AM until 5:00 AM.Clients can be marked inactive when the Client Health Tool marks it as such or when a client is marked obsolete. This task removes the discovery data associated with clients marked inactive; this commonly happens when a client does not heartbeat within the required time frame.

This is a discovery method that acts specifically on heartbeat data. If heartbeat data hasn’t been received, then the system is marked as inactive and is a candidate for deletion.

Similar to the Clear Install Flag task, this task is closely tied to Heartbeat discovery. It is recommended that the Delete data older than (days) option be set higher than your ConfigMgr Heartbeat Discovery cycle.

Because clients are marked inactive via other mechanisms, this particular task can be set to a fairly low number of days without risking data loss. If a client is marked inactive, it was already marked as such by the Client Health Tool, or via normal obsolete client processing.
Delete Obsolete Client Discovery DataNoDelete data older than 7 days, Saturday after 12:00 AM until 5:00 AM.When a client is marked obsolete, this task removes that client’s discovery data from the ConfigMgr database. A client is marked obsolete if superseded in the ConfigMgr database by another record. See the “Obsolete Clients” section for details. Obsolete records are not deleted until this task runs but there is no impact on software deployment, and so on.
Delete Aged Configuration Management DataYesDelete data older than 90 days, Saturday after 12:00 AM until 5:00 AM.The ConfigMgr database stores metadata about configuration items from Software Updates, Desired Configuration Management, and Operating System Deployments. If part of that data changes, ConfigMgr marks the previous version as old when all clients are using the new data.
Delete Aged Client Access License DataNoDelete CAL data older than 180 days. Runs on Saturday between 12:00 AM and 5:00 A.M.Client Access License (CAL) data is stored in the ConfigMgr database when Asset Intelligence is enabled. This task cleans out the old CAL data, ensuring that the ConfigMgr license information is accurate and timely.

Set the Delete data older than days option sufficiently high to avoid deleting data that is still accurate. As an example, setting it below Hardware Inventory cycle causes CAL license data to be deleted before new data has arrived from the client.

Data deleted by this task has no effect on data at other sites in the ConfigMgr hierarchy.

The 180-day setting is sufficient for most sites.
Summarize Client Access License Weekly Usage DataNoSaturday after 12:00 AM until 5:00 AM.Along with the other summarize tasks, this task is used to keep historical data points in the ConfigMgr database for reporting after the raw data is purged. This task gathers user and device CAL data and creates a weekly summary. The task does not remove information from the database, just summarizes it.
Delete Aged Computer Association DataYesDelete data older than 30 days, Saturday after 12:00 AM until 5:00 AM.ConfigMgr creates a computer association during operating system deployments that transfer user data. These associations are marked as ready for deletion after the user state restore has completed. This task removes those old associations.
Delete Aged Delete Detection DataYesDelete data older than 30 days, Saturday after 12:00 AM until 5:00 AM.New with Service Pack (SP) 1, for future integration with System Center Server Manager.
Reset AMT Computer PasswordsYesPassword reset interval (days) is set to 2.New with SP 1. This task resets the remote password used by ConfigMgr to manage AMT-based computers. For security purposes, computer account passwords are regularly changed every 30 days, unless the Windows functionality is disabled (say by using group policy).

If the computer account password is reset and the AMT remote password is not reset, ConfigMgr will be unable to connect to the AMT-based computer by using out of band communication.

Do not disable this task without disabling the Windows functionality of automatic password changes for computer accounts.
Evaluate Provisioned AMT Computer CertificatesYesSaturdays between 12 AM and 5 AM. Pending days to expiration: 42.New with SP 1. The task checks the validity period of the certificate issued to AMT-based computers and automatically requests a new certificate before it expires. Requesting a certificate renewal 42 days (default) before it expires allows plenty of time if there are issues, such as the issuing certification authority is not available, or there are connectivity issues.

Other -----------------
- Backing Up the Exchange Server 2007 Environment : Using and Understanding the Windows Backup Utility
- Backing Up the Exchange Server 2007 Environment : Leveraging Local Continuous Replication
- Windows Server 2008 Server Core : Monitoring the File System with the FSUtil Command (part 4) - Transaction, USN & Volume
- Windows Server 2008 Server Core : Monitoring the File System with the FSUtil Command (part 3) - Reparse-Point, Resource & Sparse
- Windows Server 2008 Server Core : Monitoring the File System with the FSUtil Command (part 2) - FSInfo, Hardlink, ObjectID, Quota & Repair
- Windows Server 2008 Server Core : Monitoring the File System with the FSUtil Command (part 1) - Behavior, Dirty & File
- Windows Server 2008 Server Core : Managing Disk Performance with the DiskPerf Utility, Managing RAID Setups Using the DiskRAID Utility & Managing the File System with the FltMC Utility
- Microsoft Dynamics CRM 4.0 : SQL Server Reporting Services Integration (part 3) - Install the Reporting Server on a Standalone Server
- Microsoft Dynamics CRM 4.0 : SQL Server Reporting Services Integration (part 2) - Install the Reporting Server on the Same Server as the Microsoft SQL Server
- Microsoft Dynamics CRM 4.0 : SQL Server Reporting Services Integration (part 1) - Install the Reporting Server on the Same Server as the Microsoft Dynamics CRM Server
 
 
Top 10
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
 
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server