Program command line for VBScript in sccm

create package same steps as software distribution

1) run package from DP

2) program command line is : cscript "filename.vbs"

After database migration from sql 2005 to sql 2008 Cluster server, we are getting following error.

ERROR :
	2012-02-21 19:46:00.110 Logon        Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: 172.16.28.114]
	2012-02-21 19:46:01.780 Logon        Error: 18456, Severity: 14, State: 11.
ERROR 2 :
	CTriggerManager::Init - unable to get SQL connection
	*** [28000][18456][Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
	*** Failed to connect to the SQL Server.
Solution :
	CMD -> run -> odbcad32 -> go to System DSN -> configure new database server here -> configuration -> client configuration -> Network libraries -> set to Named Pipes

Daily,Weekly & Montly maintenence tasks in sccm server.

Daily Maintenance Tasks

Applies To: System Center Configuration Manager 2007, System Center Configuration Manager 2007 R2, System Center Configuration Manager 2007 R3, System Center Configuration Manager 2007 SP1, System Center Configuration Manager 2007 SP2 Performing daily maintenance is important to ensure proper site operations.  A daily maintenance log should be maintained to document dates that maintenance was conducted,  by whom, and any maintenance-related comments about the task conducted. Common Daily Maintenance Tasks Some common daily maintenance tasks are listed below. Add any other maintenance tasks as needed to your daily maintenance log: Verify that predefined maintenance tasks scheduled to run daily are running successfully. Check Configuration Manager 2007 site database status. Check site server status. Check Configuration Manager 2007 site system inboxes for backlogs. Check site systems status. Check client status. Check the operating system event logs on site systems. Check the SQL Server error log. Check system performance.

Weekly Maintenance Tasks

Applies To: System Center Configuration Manager 2007, System Center Configuration Manager 2007 R2, System Center Configuration Manager 2007 R3, System Center Configuration Manager 2007 SP1, System Center Configuration Manager 2007 SP2 Performing weekly maintenance is important to ensure proper site operations. A weekly maintenance log should be maintained to document dates that maintenance was conducted, by whom, and any maintenance related comments about the task conducted. Common Weekly Maintenance Tasks Some common weekly maintenance tasks are listed below. Add any other maintenance tasks as needed to your weekly maintenance log: Verify that predefined maintenance tasks scheduled to run weekly are running successfully. Delete unnecessary files from site systems. Produce and distribute end-user reports if required. Back up application, security, and system event logs and clear them. Check the site database size and verify that there is enough available disk space on the site database server to allow the site database to grow. Perform SQL Server database maintenance on the site database according to your SQL Server maintenance plan. Check available disk space on all site systems. Run disk defragmentation tools on all site systems.

Periodic Maintenance Tasks

Applies To: System Center Configuration Manager 2007, System Center Configuration Manager 2007 R2, System Center Configuration Manager 2007 R3, System Center Configuration Manager 2007 SP1, System Center Configuration Manager 2007 SP2 Performing periodic maintenance is important to ensure proper site operations. Some tasks do not need to be performed during daily or weekly maintenance, but are important to ensure overall site health and security and disaster recovery plans are up to date. A periodic maintenance log should be maintained to document dates that maintenance was conducted, by whom, and any maintenance related comments about the task conducted. Common Periodic Maintenance Tasks Some common periodic maintenance tasks are listed below. Add any other maintenance tasks as needed to your periodic maintenance log: Review the security plan for any needed changes. Change accounts and passwords if necessary according to your security plan. Review the maintenance plan to verify that scheduled maintenance tasks are scheduled properly and effectively depending on configured site settings. Review the Configuration Manager 2007 hierarchy design for any needed changes. Check network performance to ensure changes have not been made that affect site operations. Verify Active Directory settings affecting site operations have not changed. For example, you should ensure that subnets assigned to Active Directory sites used as boundaries for a Configuration Manager 2007 site have not changed. Review the disaster recovery plan for any needed changes. Perform a site recovery according to the disaster recovery plan in a test lab using a backup copy of the most recent backup snapshot created by the Backup ConfigMgr Site Server maintenance task. Check hardware for any errors or hardware updates available. Check overall health of site. REF : http://technet.microsoft.com/en-us/library/bb632564.aspx

SCCM 2007 Site System roles

• Site Server - The server on which you install the SCCM software.
• Site Database Server - The server running SQL and hosting the SCCM Site Database (only required for Primary Sites)
• Configuration Manager Console - The interface for administering SCCM. Installed by default on Primary Site Servers this role can also be installed on workstations to allow remote administration.
• SMS Provider - The intermediate Windows Management Instrumentation (WMI), layer that sits between the Configuration Manager Console and the Site Database (the Configuration Manager Console accesses the Site Database via the SMS Provider). Only required for Primary Sites.
• Component Server - All SCCM Site System roles (except for the Distribution Point (DP)), requires SCCM-specific software to be installed in order for the Site System role to function.  When such software is installed on a computer that computer becomes a Component Server.
• Distribution Point (DP) - Stores SCCM Packages from where Clients can access them to install them.  Only required for the Software Distribution, Software Updates, and Advertised Task Sequences functions of SCCM.
• [NEW] Fallback Status Point - A “catch all” Site System for Clients that cannot be installed because of various issues such as assignment, or their inability to communicate with their Management Point (MP).  Not required by default, but recommended to help with Client installation issues.
• Management Point (MP) - SCCM Clients do not communicate directly with the SCCM Site Server and vice versa.  Instead all communication is facilitated via the Management Point.  A Default Management Point needs to be defined in every Site that has Intranet Clients.
• [NEW] Pre-boot Execution Environment (PXE) Service Point - The Site System that responds to any computers requesting deployment of their Operating System (OS), via a PXE request.  Only required if Operating System Deployments (OSD), are going to take place using PXE boot requests.
• Reporting Point (RP) - Hosts the Report Viewer component that provides the web-based reporting functionality of SCCM. Only required if Reports need to be run on a particular Primary Site.
• Server Locator Point (SLP) -  Responsible for informing SCCM Clients which MP they should access in order to install the SCCM Client software. Only required in some Client Deployment scenarios.
• [NEW] Software Update Point (SUP) - Assigned to the computer running Windows Server Update Services (WSUS).  Only required if the Software Updates feature is going to be used.
• [NEW] State Migration Point (SMP) - Stores the user’s state migration data when a computer’s OS is migrated.  Only required if the OSD feature is going to be used.
• [NEW] System Health Validator Point (SHVP) - This role is assigned to the computer running the Network Policy Service.  Only required if the Network Access Protection (NAP) feature is going to be used.

How to check Management point status in sccm

HTTP://<sccm server name>:80/SMS_MP/.SMS_AUT?MPCERT
HTTP://<sccm server name>:80/SMS_MP/.SMS_AUT?MPLIST