Use Full SQL Tables / Views

UseFull SQL Tables/ Views	Description / Use
v_Add_Remove_Programs
v_Advertisement
v_AdvertisementInfo
v_ClientCollectionMembers
v_Collection
v_Collection
v_ConfigurationItems
v_DistributionPoint
v_DistributionPointGroup
v_GS_ADD_REMOVE_PROGRAMS
v_GS_ADD_REMOVE_PROGRAMS_64
v_GS_COMPUTER_SYSTEM
v_GS_DISK
v_GS_Memory_Details0
v_GS_OPERATING_SYSTEM
v_GS_PATCHSTATE
v_GS_SERVICE
v_GS_SoftwareProduct
v_GS_SYSTEM
v_GS_WORKSTATION_STATUS
v_GS_X86_PC_MEMORY
v_OS_Details
v_Package
v_PackageStatus
v_Program
v_Query
v_R_System
v_R_User
v_R_UserGroup
v_RA_System_IPAddresses
v_RA_System_IPSubnets
v_RA_System_IPXAddresses
v_RA_System_MACAddresses
v_RA_System_SMSAssignedSites
v_RA_System_SMSInstalledSites
v_RA_System_SystemContainerName
v_RA_System_SystemGroupName
v_RA_System_SystemOUName
v_RA_System_SystemRoles
v_Report
v_Site
v_SiteBoundary_ADSite
v_SiteBoundary_IPSubnet
v_StateNames
v_UpdateBundles
v_UpdateListStatus_Live
v_UpdatePrograms

Windows 2008 IIS Common Issue on MP : Make sure you need to meet this settings on your windows 2008 server

 

Windows 2008 IIS Common Issue on MP : Make sure you need to meet this settings on your windows 2008 server

Popular and useful tools for ConfigMgr 2007

• SCCM Right Click Tools
• SCCM Client Center
• OSD++
• SMSMap
• SCCMAutoDoc
• SCCM 2007 SDK
• SCCM-Tools.com
• BitsAdmin
• WMI Administrative Tools
• WMI Diagnosis Utility

 

 

http://www.petervanderwoude.nl/post/The-best-(free)-tools-for-ConfigMgr-2007!.aspx

Discovery Mystery

Discovery Methods

Six methods of discovery are available in Configuration Manager 2007:

• Network Discovery
• Heartbeat Discovery----------------------------------------------------this must enabled in all sites
• Active Directory System Group Discovery
• Active Directory Security Group Discovery
• Active Directory System Discovery
• Active Directory User Discovery

 

As Configuration Manager 2007 discovers resources, it creates records in the Configuration Manager database. This record is called a data discovery record (DDR) and the file generated has a .DDR extension. The specific information contained in each record varies depending on the resource "discovered," but it can include data such as the NetBIOS name of a computer, IP address and IP subnet of a computer or device, operating system, MAC address, and so on.

Depending on the discovery method used, resource DDRs are periodically regenerated to keep the discovery data up to date in the database and to verify that the resource is still a valid resource within the Configuration Manager 2007 site.

 

Now these methods what will discover?.. below are the discover use of each

Active Directory System Group Discovery

Organizational unit

Global groups

Universal groups

Nested groups

Nonsecurity groups

Active Directory System Discovery

• Computer name
• Operating system
• Object class
• DNS Host name
• Domain

Active Directory User Discovery

• User name
• DNS host name
• Object class
• Active Directory domain
• Active Directory container name

Network Discovery

• NetBIOS name
• IP addresses
• Resource domain
• System roles
• SNMP community name
• MAC addresses

Heartbeat Discovery :- Heartbeat Discovery is active only on computers that have already been installed as Configuration Manager clients.

It is important to ensure that any schedule you create causes the DDRs to be updated frequently enough so that the original DDR isn't viewed by Configuration Manager as obsolete or deleted from the database.Heartbeat Discovery updates existing DDRs rather than creating new ones. By default, it generates an updated DDR for each client every seven days, although this timing is configurable.

Heartbeat Discovery runs on installed Configuration Manager clients according to the schedule you specify. With this method enabled, the Client Component Installation Manager (CCIM) on the client causes the Cliex32.dll to generate a DDR, which is then written to the management point. This file is the same size as a normal DDR (approximately 1 KB per client), and so it will generate approximately the same network traffic.

 

Active Directory Security Group Discovery

he Configuration Manager 2007 Active Directory Security Group Discovery method searches for security groups by polling the closest Active Directory domain controller. The Active Directory domain can be in mixed mode or native mode.

 

Discovery Troubleshooting Flowcharts http://technet.microsoft.com/en-us/library/bb735871.aspx

 

Log files related to discovery

Adsysdis.log Active Directory System Discovery log file showing when the discovery method runs, and its results. Look for the number of DDRs created and any "bogus" entries.

Adsysgrp.log Active Directory System Group Discovery log file showing when the discovery method runs, and its results. Look for the number of DDRs created.

Adusrdis.log Active Directory User Discovery log file showing when the discovery method runs, and its results. Look for the number of DDRs created.

 

DISCOVERY HAS A DEPENDENCE OF CLEINT PUSH, IF DISCOVERY IS NOT ENABLED OR NOT DISCOVERED ANY SYSTEMS THEN CLIENT PUSH WILL NOT PUSH ON ANY SYSTEM’S

Scripts:- http://technet.microsoft.com/en-us/library/cc180843.aspx

If you deleted any system from SCCM / SMS console you can initiate the client discovery data cycle then client can be reappear in the console

 

Third party Discovery Tools :- enhanced discovery tool

 

The major discovery drop backs in SCCM is it will not do a delta discovery it will do from scratch.. that means it will not discover specific to the changes that has changed from last cycle.. to accomplish this you need to depend on Enhanced discovery tool http://www.systemcentertools.com/esd.html 

now with SCCM R3 you can do delta discovery

SCCM Client Services and applets

If SMS/SCCM Client is installed we will get SMS Agent host (ccmexec.exe ) service will be installed all the related information log file is ccmexec.log file

if client installed it will come in Control Panel

 

if the client OS version is 32 bit then you can find the applets in the control panel directly, if it is 64 bit OS then you will get in 32-bit Control Panel items (The reason is sccm is a 32 bit application) also client will be installed in windows\ccmsetup for client installation

and for client logs in 64 located in

 

64 bit client log files location screenshot is below

 

SMS / SCCM console not connecting

Above is a example screenshot

There are 3 areas of consideration when troubleshooting access to the SMS provider and the site server. 

1. Do you have the necessary privileges to the SMS provider on your site server?

2. Do you have the necessary security rights to the database?

3. Do you have the necessary privileges as far as WBEM is concerned?

4. Is WBEM working? 

http://www.myitforum.com/articles/6/view.asp?id=250
http://support.microsoft.com/kb/317872

Verify that this computer has network connectivity to the SMS Provider

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

 

 

Check the adminui.log and smsprov.log and smsdbmon.log

Site Status Components checks :- Regular checks

Site Status components are at least 51 or more than that are available. And here below of some mentioned may need to come as read / warning in your day to day operations

SMS_LAN_SENDER

SMS_EXECUTIVE

SMS_HIERARCHY_MANAGER

SMS_DISTRIBUTION_MANAGER

SMS_DESPOOLER

SMS_DISCOVERY_DATA_MANAGER

SMS_INBOX_MANAGER

SMS_MP_CONTROL_MANAGER

SMS_MP_FILE_DISPATCH_MANAGER

SMS_INVENTORY_PROCESSOR

SMS_INBOX_MONITOR

SMS_INVENTORY_DATA_LOADER

SMS_DATABASE_NOTIFICATION_MONITOR

SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT

SMS_AI_KB_MANAGER

SMS_AMT_PROXY_COMPONENT

SMS_SITE_SQL_BACKUP_AUPERPSPSS01

SMS_AD_SECURITY_GROUP_DISCOVERY_AGENT

SMS_AD_SYSTEM_DISCOVERY_AGENT

SMS_COMPONENT_MONITOR

SMS_COMPONENT_STATUS_SUMMARIZER

SMS_CLIENT_CONFIG_MANAGER

SMS_COLLECTION_EVALUATOR

SMS_WSUS_CONFIGURATION_MANAGER

SMS_WSUS_CONTROL_MANAGER

SMS_SOFTWARE_METERING_PROCESSOR

SMS_STATE_SYSTEM

SMS_STATUS_MANAGER

SMS_MP_FILE_DISPATCH_MANAGER

SMS_OUTBOX_MONITOR

SMS_PXE_SERVICE_POINT

SMS_WSUS_SYNC_MANAGER

SMS_COMPONENT_MONITOR

SMS_EXECUTIVE

SMS_SOFTWARE_INVENTORY_PROCESSOR

SMS_OUTBOX_MONITOR

SMS_POLICY_PROVIDER

SMS_REPLICATION_MANAGER

SMS_OBJECT_REPLICATION_MANAGER

SMS_OFFER_MANAGER

SMS_SITE_BACKUP

SMS_SITE_COMPONENT_MANAGER

And out of the regular ones in my case I am seeing these many times in the hierarchy

SMS_LAN_SENDER==================> in the error mentioned site systems are offline or network connectivity problem

SMS_DISTRIBUTION_MANAGER========> Targeted packages are not reached the DP or very frequently updated by some one

SMS_MP_CONTROL_MANAGER==========>

Mpcert http://sccmserverName/sms_mp/.sms_aut?mpcert

MPlist http://sccmserverName/sms_mp/.sms_aut?mplist

For MP function mpcontrol.log file.. You may get 401,403 or 500 errors mostly with IIS & SQL issues. If you see error 200 that means MP working Fine.

Log files location for a server with the sitecode of DC1

SMS_COLLECTION_EVALUATOR========> at this stage we can ignore this error

SMS_WSUS_SYNC_MANAGER===========> Solution: - open the wsyncmgr.log file check for errors and do a more sync if required from below given screenshot

Sample Error:- SMS WSUS Configuration Manager failed to configure proxy settings on WSUS Server "USDC1PSPSS02".

Possible cause: WSUS Server version 3.0 SP1 and above is not installed or cannot be contacted.

Solution: Verify that the WSUS Server version 3.0 SP1 or greater is installed. Verify that the IIS ports configured in SMS are same as those configured on the WSUS IIS website.You can receive failure because proxy is set but proxy name is not specified or proxy server port is invalid.

SMS_OUTBOX_MONITOR============> You need to connect to the Configmgr Service Manager and stop the inbox_monitor component and start it same applies to below one.

SMS_Inboxe_MONITOR=============>

SMS_PXE_SERVICE_POINT===========> Check the WDS Service in Services.msc console if the service is stopped raise a P-4 incident to start the service. MAKE SURE IF THE SERVICE IS IN STARTED STATE AND YOU ARE TRYING TO STOP IT MAY CHANGE THE STATUS TO STOPPING STATUS AND IT NEVER CHANGES IT STATUS TO RUNIING OR STOPPED STATE, AND It will not allow you to even kill the pid The solution is reboot the system (This also happens to SMS executive service also)

What and Where you can control the Network Bandwidth

Ok.. Now you want to know here are all the bandwidth can be controlled in SCCM

 

Package Movement	Bandwidth Control	Uses Binary Differential Replication?
From package source directory to site server	None.	No
From site server to standard distribution point	None.	Yes
From parent site server to child site server	Bandwidth controlled by Address settings on the sender between sites.	Yes
From child site server to child standard distribution point	None.	Yes
From standard distribution point to branch distribution point	BITS or manually pre-staged on the branch distribution point. For more information	Yes
From standard distribution point to client	BITS, if BITS-enabled distribution point is available and advertisement is configured to download and run locally.	No
From branch distribution point to client	None.	No

SCCM Senders End to End

Senders can be configured on only Primary and Secondary sites, the use of senders are instead, senders use existing network connectivity to manage the connection, ensure the integrity of transferred data, recover from errors, and close the connection when it is no longer needed.

Types of Senders : 6 types

1) Standard Sender

The standard sender is installed and configured by default on all primary and secondary sites. If your site-to-site communications occur over a LAN that uses a supported protocol, you do not need to install another sender.

if you want to apply some bandwidth restrictions between site to site communication. here are the options for Standard Sender.

 

 

2) Courier Sender

The courier sender is installed and configured by default on all primary and secondary sites. It is not displayed, and cannot be created, in the Configuration Manager console because it must be manually started from the Configuration Manager programs folder on the Start menu. Courier senders are used only for software distribution to send package data to other sites by using physical media instead of sending data over the network. To use the courier sender, you must first create a standard sender connection between the parent site and the child site. Once the standard sender is created, you then create a courier sender address for each site to use the courier sender functionality.

When you have large packages that require excessive time or bandwidth to be sent over the network, this sender can be useful. You can use courier sender at the source Configuration Manager 2007 site to create a parcel (that is, a collection of files transferred from one site to another using courier sender); write the parcel to a tape, CD, or other physical medium; and then ship the tape or CD to the destination site by mail or a courier service. At the destination site, you can then use courier sender at that site to receive the parcel and import the package data into the site.

Note :- The courier sender is installed and configured by default on all primary and secondary sites. It is not displayed in the results pane because it must be manually started from the Configuration Manager 2007 program files on the start menu.

3) Asynchronous RAS Sender

Used for communication over an asynchronous line.

4) ISDN RAS Sender

Used for communication over an ISDN line.

5) X25 RAS Sender

For RAS communication over an X.25 line.

6) SNA RAS Sender

For RAS communication over an SNA link.

Ok.. Now if you in confuse what to use in your network after reading the above, Just check the below table you will get some more clarity where what type of sender you can use

Existing network connectivity between sites	Sender
LAN or WAN	Use Standard Sender, the most commonly used sender, for sending to other sites on the same LAN, or on a WAN using routers, switches, or bridges.
Asynchronous line	Use Asynchronous RAS Sender for RAS communications over an asynchronous line.
ISDN line	Use ISDN RAS Sender for RAS communications over an ISDN line.
X.25 line	Use X25 RAS Sender for RAS communications over an X.25 line.
SNA	Use Systems Network Architecture (SNA) RAS Sender in RAS communications over an SNA link.
No Connectivity to your office or None	Use Courier Sender to send packages between the sites by using removable media instead of network wiring and protocols if you have a slow or unreliable link between a site and its parent. Courier Sender is used only for package distribution, not site-to-site communications.

For my all Primary Site i have open the communication to be open all the time however for secondary sites i have done below recommendation based on the bandwidth and  clients size : this is again for Standard Sender

WAN Link Speed	Time (Local time)	Monday – Friday	Saturday	Sunday	% of Available Bandwidth	Pulse Mode Settings
64Kbps	18:01 – 06:01	Open for all priorities	Open for all priorities	Open for all priorities		20KB every 5 seconds
06:00 – 18:00	High and Medium Priorities	Open for all priorities	Open for all priorities		20KB every 5 seconds
128Kbps	18:01 – 06:01	Open for all priorities	Open for all priorities	Open for all priorities		40KB every 5 seconds
06:00 – 18:00	High and Medium Priorities	Open for all priorities	Open for all priorities		40KB every 5 seconds
256Kbps	18:01 – 06:01	Open for all priorities	Open for all priorities	Open for all priorities		80KB every 5 seconds
06:00 – 18:00	High and Medium Priorities	Open for all priorities	Open for all priorities		80KB every 5 seconds
384Kbps	18:01 – 06:01	Open for all priorities	Open for all priorities	Open for all priorities		100KB every 5 seconds
06:00 – 18:00	High and Medium Priorities	Open for all priorities	Open for all priorities		100KB every 5 seconds
512Kbps	18:01 – 06:01	Open for all priorities	Open for all priorities	Open for all priorities	75%
06:00 – 18:00	High and Medium Priorities	Open for all priorities	Open for all priorities	50%
1024Kbps	18:01 – 06:01	Open for all priorities	Open for all priorities	Open for all priorities	75%
06:00 – 18:00	High and Medium Priorities	Open for all priorities	Open for all priorities	50%
1536Kbps	18:01 – 06:01	Open for all priorities	Open for all priorities	Open for all priorities	75%
06:00 – 18:00	High and Medium Priorities	Open for all priorities	Open for all priorities	50%
2045Kbps	18:01 – 06:01	Open for all priorities	Open for all priorities	Open for all priorities	75%
06:00 – 18:00	High and Medium Priorities	Open for all priorities	Open for all priorities	50%
3072Kbps	18:01 – 06:01	Open for all priorities	Open for all priorities	Open for all priorities	75%
06:00 – 18:00	High and Medium Priorities	Open for all priorities	Open for all priorities	50%
5464Kbps	18:01 – 06:01	Open for all priorities	Open for all priorities	Open for all priorities	75%
06:00 – 18:00	High and Medium Priorities	Open for all priorities	Open for all priorities	50%

 

Pulse mode configure options

In real World :- You will use only Standard Sender

What is SMS_SiteSystemToSiteServerConnection & SMS_SiteSystemToSiteServerConnection group

Site System to Site Server Connection Group:

 

The Site System to Site Server Connection (SMS_SiteSystemToSiteServerConnection_sitecode) group grants the necessary permissions for Microsoft System Center Configuration Manager 2007 services running on remote site systems (such as management points) to connect to the site server to access the Configuration Manager 2007 registry keys and directories on the site server. if you are runing any below role this group should be part of remote site

Servers hosting the following site system roles should be members of this group, unless they are in a remote, untrusted forest:

• Management points - MP
• System Health Validator points – SHV
• State migration points 
• Fallback status points
• Software update points
• PXE service points
• SMS Provider computers
• Asset Intelligence synchronization point (Configuration Manager 2007 R2)
• Out of band management point (Configuration Manager 2007 SP1)

 

Site to Site Connection Group

This group has the necessary permissions for a sender to connect from one Microsoft System Center Configuration Manager 2007 site to another.

 

Note both should be local /Domain Local Group membership only

SMS / SCCM Site codes Names will not work

Be careful of reserved names for site codes

Suppose you've created a new site named 'CON' and are having trouble with it. The reason for this is that you've used a Windows reserved name for your SMS site code. The list of reserved name is fairly short and includes:

• CON
• PRN
• AUX
• NUL

The reason that these site codes are reserved is pretty simple. In some places, SMS creates folders using the site code. Since these names are reserved names in Windows and are used for other specific tasks, SMS can't create the site folder.

Limitations of SCCM 2007

Below are the Microsoft Recommendation as per MS Website

SCCM TOOLS

 

1E Migration Tool

The Migration of Package and Program details along with source files
Renaming of Package and Program names during migration
Direct transfer of packages from your SMS site to ConfigMgr
Export to flat file structure from SMS site and Import into ConfigMgr from flat file
Exporting of SMSNomad command line settings to new ConfigMgr Nomad tab settings

 

Download: http://www.1e.com/downloads/freetools/index.aspx

ConfigMgr Site Bound Tool

SiteBound.exe /s {central site server} /file {excel file} /log {path}

/s Central Site Server name.
/file Path to Excel files.
/log Log file path.

Download it from http://bdpadd.codeplex.com/

ConfigMgr 2007 CCR creator tool

Run the Create_and_copy.bat file and it will

1. Create a folder on the c drive called CCRBIN
2. Copy the IPF and Machines.cvs files to the CCRBin folder

Then it will ask you to compile the IPF with SMS installer.

Then to run it use these directions

1. Add the machines that you want CCR's created for to the Machine.cvs file (it can be 1 or many)
2. Execute the EXE
    3. It will prompt you for your ConfigMgr Server
    4. Then it will prompt you for your ConfigMgr Site code
        (This info can be hardcoded just follow directions in the IPF to do that)

---Created by: Chris Stauffer download http://myitforum.com/cs2/blogs/cstauffer/archive/2008/05/21/configmgr-2007-ccr-creator-tool.aspx

ConfigMgr Branch DP Add

This tool was written in C# and requires the .NET framework 2.0 Running the tool
BDPAdd.exe /s {central site server} /file {excel file} /log {path}
/s Central Site Server name. /file Path to Excel files. /log Log file path.

download it from http://www.codeplex.com/bdpadd

Preload Package Tool for Configuration Manager 2007

Problem Scenarios:

1. When software distribution packages are created, information about them is sent to child sites in the hierarchy. If a child site has a distribution point installed that is listed in the package properties to host the content, the content is transferred over the network and uses available network bandwidth sending compressed copies of all required package source files. To avoid using network bandwidth, the Preload Package Tool can be used to copy compressed software distribution package source files to the remote child site before assigning the child site distribution point to host the package source files.
   
2. If a child site fails that has a distribution point that is assigned to host software distribution package source files for a package created at a site higher in the hierarchy, all package source files will be resent over the network when the site is rebuilt and rejoined to the site hierarchy. To avoid this, the Preload Package Tool can be used to restore backed up compressed software distribution package source (.pck) files to the distribution point before rejoining the site to the hierarchy so they will already be present.

Instructions:

1. Copy PreloadPkgOnSite.exe file to the .\program files installation directory\bin\i386 directory on the child site that you wish to preload compressed software distribution package source (.pck) files.
   
2. Copy the applicable .pck files from the parent site or from a backup location to the distribution point share on the child site manually. After manually copying the files, ensure that the read-only NTFS file attribute for the .pck file is set.
   
3. From a command prompt, run the tool using the following syntax: PreloadPkgOnSite.exe PkgID StoredPkgVersion.
   
4. Running this command will update necessary software distribution package source location information for the site and forward this information up the hierarchy.
   
5. After the package source file location information is sent up the hierarchy, the distribution point hosting the manually copied .pck files can be added to software distribution package source locations at without the need to transfer package source files over the network.

Checks:

1. The command line usage is: PreloadPkgOnSite.exe PkgID StoredPkgVersion
   
2. If software package information already exists for a package at the site where the tool is used, the tool cannot be used.
   
3. This tool is meant only for child sites and cannot be used to preload packages that were created at the child site where the tool is run.
   
4. The PkgID.pck file must exist at the child site before the tool is run.

Precautions:

• When run, this tool modifies site database information at all sites higher in the hierarchy. This tool should only be run on fully functioning child sites and only when necessary.
  
• If the Configuration Manager 2007 distribution manager process has already started processing software distribution package information to be preloaded, there is no need to run the tool

 

Download it from here:http://download.microsoft.com/download/d/e/d/ded78c6e-59a4-43ee-b601-6527be7bd881/PreloadPkgOnSite.exe

Day to Day Operations SCCM / ConfigMgr 2007 Reports

I recommend below ConfigMgr Reports to be familiar and these might be useful in day to day operations

 

Asset Intelligence:-

License 03A - Count of licenses by license status
Hardware 07A - USB devices by manufacturer

Software 02C - Software by Category and Family

Software 01A - Summary of installed software in a specific collection

This report provides a summary of installed software ordered by the number of instances found from inventory.

Desired Configuration Management – Compliance

Summary compliance for a collection by computer

Hardware

Count physical disk configurations

Computers with low free disk space (less than specified MB free)

Computers with low free disk space (less than specified % free)

Count memory configurations

Computers with low memory (less than or equal to specified MB)

Computers with a specific amount of memory

Memory information for a specific computer

Network

Count IP addresses by subnet

IP - Information for a specific computer

NAP

List of NAP-capable and NAP-upgradable computers

List of Network Access Protection policies

Operating System

Windows Server computers

Computers with a specific operating system and service pack

Computers with a specific operating system

Count operating systems and service packs

Count operating system versions

Services - Computers running a specific service

SMS/SCCM Client

Count SMS client versions

Servers with no client Installed

Client Deployment Failure Report

Client Deployment Success Report

Client Deployment Status Details

Client Assignment Failure Details

Count clients assigned and installed for each site

Computers with a specific SMS client version

Count clients for each site

Computers with duplicate MAC addresses

Computers that may share the same SMS Unique ID

Clients that have not reported recently (Collection)

& Clients that have not reported recently (in a specified number of days)

Site TO Site Reports:

Sites by hierarchy with time of last site status update

Computers in a specific site
Status messages for a branch distribution point
Site system roles and servers for a specific site

Software Inventory

Software registered in Add Remove Programs for a specific collection
Computers with specific software registered in Add Remove Programs
Computers with a specific product
Count of all instances of software registered with Add or Remove Programs
Computers with a specific product name and version
Count computers with a specific filename

Software Distribution:-

Status of a specific advertisement
All advertisements for a specific collection
All advertisements
Distribution status of a specific package
All packages on a specific distribution point
All distribution points
All active package distributions

Patching:-

Compliance 1 - Overall Compliance
Compliance 4 - Deployment (per update)
Compliance 3 - Update list (per update)
Compliance 4 - Deployment (per update)
Management 1 - Updates required but not deployed
Management 2 - Updates in a deployment
States 1 - Enforcement states for a deployment
States 2 - Evaluation states for a deployment
Scan 1 - Last scan states by collection
Scan 2 - Last scan states by site

Auditing

All audit messages for a specific user
All Task Sequence Advertisements
Deployment status of all task sequence advertisements
Progress of a running task sequence
Progress of OS deployment task sequences
Status of all unknown computers
Computers for a specific user name
WOL

All sites that are enabled for Wake On LAN
All computers targeted for Wake On LAN activity
All objects pending wake-up activitiy

Customized reports:

All computers based on AD site:

SELECT DISTINCT SYS.Name0,SYS.AD_Site_Name0,

SYS.User_Domain0,SYS.User_Name0,

SYS.Operating_System_Name_and0

FROM v_R_System SYS

WHERE SYS.AD_Site_Name0 LIKE @variable

ORDER BY SYS.AD_Site_Name0, SYS.Name0

--Prompt Query

SELECT DISTINCT SYS.Name0,SYS.AD_Site_Name0,

SYS.User_Domain0,SYS.User_Name0,

SYS.Operating_System_Name_and0

FROM v_R_System SYS

WHERE SYS.AD_Site_Name0 LIKE @variable

ORDER BY SYS.AD_Site_Name0, SYS.Name0

Lins with reports =è Hardware - General - Computer information for a specific computer; below is the screenshot

Also I prefer one to have below custom reports

Compliance - Detailed list - specific collection

Computer Information - specific collection

Computer information for a collection of computers

Computers with specific software

Distribution Points in All DP Group

Missing Patches

Network settings

Network settings for a specific collection

Servers with SCCM Client version
All Workstation Patching compliance reports
All Desktops & Laptops model & make reports

wds.txt

Option 60: "PXEClient"
Option 66: "2k3-wds.domain.local"
Option 67: "boot\x86\wdsnbp.com"


sysprep -mini -quiet -factory -reboot
c:\windows\system32\sysprep\sysprep.exe /quiet /generalize /shutdown /oobe

DP Pros and Cons

BDP PROS:

· Content on demand

· Uses bits to get content

BDP CONS:

· SCCM client breaks so does the DP

· Requires an unprotected DP to get content

· Less robust reporting than a secondary site.

DP PROS:

· Senders

· Better reporting

· No need for unprotected parent DP

DP CONS:

· No content on demand

· Uses SMB to get content

Troubleshooting WinPE and task sequence issues

You can troubleshoot some common WinPE and task sequence issues.

WinPE never starts the task sequence

Check the SMSTS.LOG file at X:\windows\temp\smstslog\smsts.log. If a package never downloaded, it is likely that you simply do not have the appropriate network drivers installed, which prevents the machine from communicating with Configuration Manager.

Check your driver catalog to ensure you have the right network drivers available and installed into the boot image, and update the boot image to your distribution points.

Additional network or storage drivers might be needed in the boot image to enable the WinPE boot to function correctly. You should add those through Drivers in the Operating System Deployment node.

The right drivers have been added to the boot image, but are not loading

The original boot.wim file (WinPE boot image) created during Configuration Manager installation is copied and modified with IBM-specific drivers and other files. Your task sequences that use the IBM Deployment Pack must use this boot image or the tools might not work properly.

Check to make sure the image into which you loaded the drivers is the same image being used by the task sequence.

This is a common error for administrators who maintain multiple boot images.

Servers will not boot using PXE

PXE is an extension of DHCP, which uses a broadcast type of communication. Broadcast communication uses standard timeout values that are not readily changeable. As a result, a computer waits for a default timeframe to receive a DHCP or PXE response before timing out and causing a failure condition.

Each time a server is rebooted, it must renegotiate the connection to the switch. Some network switches arrive configured with default settings that might incur connectivity delays. That is, the settings on the switch might cause a DHCP or PXE timeout because they fail to negotiate a connection in time.

One of the features that can be affected by this issue is Spanning Tree Protocol (STP). STP is a protocol that prevents loops and provides redundancy within a network. A networking device using this algorithm might experience some latency as it collects information about other network devices. During this period of information collection, servers might boot to PXE and time out while waiting for a response from Windows® Deployment Services. Disable the STP or enable PortFast on end-node ports for the target server to prevent such occurrences. Refer to the manufacturer’s user guide for further information.

Another feature that can be affected by this issue is the EtherChannel or Port Aggregation Protocol (PAgP). EtherChannel allows multiple links between devices to act as one fast link that shares the load between the links. Running the EtherChannel Protocol in automatic mode can cause a connectivity delay of up to 15 seconds. Switch to a manual mode or turn off this feature to eliminate this delay.

Speed and duplex negotiation can also play a role in negotiation timeouts. If auto-negotiation on the switch is set to off, and the server is not configured to that speed and duplex setting, the switch will not negotiate with that server.

For more information, see the Cisco Web site and the following Cisco documents:

• Cisco: Using PortFast and Other Commands to Fix Workstation Startup Connectivity Delays
• Cisco: Configuring and Troubleshooting Ethernet 10/100Mb Half/Full Duplex Auto‑Negotiation

Default boot order does not allow PXE to boot when a valid drive exists

When an active partition is created on a hard drive, it automatically becomes a bootable device if a valid operating system has been installed. If your PXE NIC is after the hard drive in the boot order, the hard drive tries to boot before PXE and boots to Windows, or causes an Invalid System Partition error if Windows is not installed.

To resolve this issue, be sure that PXE is placed before the hard drive in the boot order. Keep in mind that even if PXE is first in the boot order, the computer does not actually boot to PXE unless Configuration Manager has a task sequence for it to run.

When using a “Reboot” action after initializing an array controller, the task sequence fails

Configuration Manager 2007 does not allow a task sequence to reboot back to PXE. It can reboot back to WinPE or to an installed operating system, both of which require a disk partition and the appropriate installed software.

Without a disk partition, Configuration Manager will fail when attempting to reboot during a task sequence because it expects to copy WinPE to the disk. Additionally, the management point tracks when a machine has booted to PXE to run a task sequence, and once a machine has booted to PXE for a task sequence, it cannot use PXE as a boot method again for that task sequence unless the advertisement is reset.

To perform a reboot to PXE if you need to within a task sequence, use the custom action called “Reboot To PXE." This custom action, written using C# and VBScript, connects to the Configuration Manager 2007 SDK, and contains custom code to drive actions in the admin console as well as the machine being deployed. This custom action performs all the steps necessary to perform the reboot to PXE and allow for proper program flow when it occurs.

The only other way to accomplish a reboot to PXE is to use more than one task sequence, let the computer “fall off the end” of the first task sequence and manually reset the PXE advertisement for the computer.

Task sequence fails with “Failed to Download Policy” and code 0x80093102 or 0x80004005

This error code typically refers to a certificate validation issue.

The SMSTS.LOG file will show an entry with the following text:

CryptDecryptMessage ( &DecryptParams, pbEncrypted, 
 nEncryptedSize, 0, &nPlainSize, 0 ), HRESULT=80093102

or

no cert available for policy decoding

Possible causes are:

• Misconfiguration of your domain or a site server, such as DNS not pointing to the site server, or the site server not specifying a valid FQDN (which is referred to by the DNS listing).
  

  If your site server does not specify a FQDN (and only specifies the NETBIOS name), and your DNS server refers to the FQDN, a faulty lookup might cause this error.

  
  
• The certificate being used for PXE and boot media.
  

  Check the certificates under the Site Settings node and see if any certificates are blocked or missing. Open the certificates and ensure that they are actually installed into the certificate store. If not, install them.

If these actions do not work, try removing the package from the distribution point (via Manage Distribution Points) and adding the package again to regenerate the package hash.

Task sequence fails with “Failed to Download Policy” and code 0x80004005

This error code typically refers to a certificate validation issue.

The SMSTS.LOG file will show an entry with the following text:

failed to download policy

Check the certificates under the Site Settings node to if any certificates are blocked or missing. Open the certificates to ensure that the certificates are installed into the certificate store. If not, install the certificates.

Task sequence fails because the package is not downloading

In WinPE, the default option of “Download content locally when needed by running task sequence” will not work. When in WinPE, the task sequence engine will ignore (and fail) all actions that have packages set for this option.

Set all packages needed for use in WinPE to “Access content directly from a distribution point when needed by the running task sequence.”

Task sequence does not run again even after clearing the PXE advertisement

You must set the advertisement to “Always rerun” so that any time you reset the PXE advertisement, the advertisement is applied to the computer regardless of whether it ran the task sequence before.

Task sequences fail or act incorrectly after an upgrade

When upgrading from a previous version of this product, existing task sequences using these custom actions are not automatically updated.

To function correctly, open each task sequence action that uses a custom action in an editor. Add a “.” to the description and remove it to enable the Apply button. Click Apply to refresh the properties of the custom action and save any new automatic data or formatting that is required to function with the new version.

Files and logs are not being returned from the client

A number of issues can prevent the task sequence from returning files or logs from the client.

Among the possible issues that might prevent the task sequence from returning files or logs from the client are:

• Failure of the client-side script prior to the file copy, which is usually evident in the log file.
  

  Repeat the task and press F8 during the task to get to a command prompt, if you selected the check box for Enable command support on the boot image properties > Windows PE page.
  

  Then open the SMSTS.LOG file. The location varies. In WinPE via PXE, the location is at X:\Windows\Temp\Smstslog\smsts.log.

  
  
• Malformed XML in the IBM Deployment Packconfiguration file.
  
• The command being executed actually has an error but exits with code 0.
  

  This can occur when a severe error is encountered in the script while the script is set to ignore errors and use programmatic error handling. Then the error handling did not catch the same error.
  

  Report such issues to the IBM® support site, as described in Getting help and technical assistance.

  
  
• The task sequence cannot access the share or mapped drive that is the target drive for copying the files or logs.

Logs are being returned but not output files

A number of issues can prevent the task sequence from returning output files while allowing the task sequence to return log files.

Among the possible issues that might prevent the task sequence from returning output files from the client are:

• No return file parameters are specified in the configuration XML.
  
• Return file parameters in the configuration XML are incorrect.
  
• An error is occurring with the operation of the utility that generates the output file.
  
• A null variable is causing an error in the file name of the file to be returned.

Task step execution does not automatically change after a change to the configuration XML file

If you change the configuration XML, previously existing task steps do not automatically change unless you edit them.

To fix the existing task steps, open the task sequence editor and make a minor edit to each custom action step in the sequence. You can simply add a “.” to the description and then delete it to enable the Apply button. Click Apply. The task sequence steps are now saved with the automatically updated information from the new XML file.

Task sequence fails at “Apply Operating System” with “Failed to make volume X:\ bootable”

Several problems can cause this error.

This issue is indicated by log content similar to the following text:

MakeVolumeBootable( pszVolume ), 
HRESULT=80004005 
(e:\nts_sms_fre\sms\client\osdeployment\applyos\installcommon.cpp,759)

Failed to make volume E:\ bootable. 
Please ensure that you have set an active partition on the boot 
disk before installing the operating system.

Unspecified error (Error: 80004005; Source: Windows)

ConfigureBootVolume(targetVolume), 
HRESULT=80004005 
(e:\nts_sms_fre\sms\client\osdeployment\applyos\applyos.cpp,326)

Process completed with exit code 2147500037

This issue can be related to two different scenarios:

• If you are using a Format & Partition action in your task sequence to partition the hard drives, make sure that you select the check box for Make this the boot partition on one of the partitions.
  

  If you do not make a drive bootable and the computer has only the single drive, the task sequence engine automatically makes one of the partitions the boot partition. But if there are multiple drives, the task sequence engine cannot determine which drive should be bootable, and you see this error.

  
  
• If you upgraded from the Configuration Manager RTM to SP1, you might have a problem if both hard drives are completely raw. If you have never partitioned the drives, a known bug in Windows PE prevents Windows PE from determining the drive where it was booted, and you see this error.
  

  This situation is likely on a server with a RAID controller where you have just formed two or more RAID sets. The new RAID sets are completely raw because they have never existed before.
  

  The only workaround to the problem of multiple raw drives is to manually boot into Windows PE and run "diskpart" to partition at least one of the drives. Then run the task sequence again. The task sequence should work.
  

  The known problem with Windows PE is fixed in Windows Vista SP1 and hence in the Windows PE that is derived from Vista SP1.

Install Configuration Manager 2007 SP1

Configuration Manager 2007 SP1 includes the SP1 version of the Windows Automated Installation Kit (WAIK). Download and install Configuration Manager SP1 to get the new version.

Upgrading to Configuration Manager 2007 SP1 automatically updates your default boot images, but does not automatically upgrade the IBM boot images.

Upgrade the IBM boot images by rerunning the IBM Deployment Pack installer and selecting “Modify”. You must also update your distribution points so that the new images are used. You should also update the distribution points for the default boot images as well.

The product installer detects the version of WinPE that is currently in use by the default boot images. If the default boot images are not Vista SP1, the product cannot install.

How to tell if your boot images are upgraded to Vista SP1

Boot image properties contain an identifier for “OS Version.”

Perform this procedure to see the version of WinPE in your boot images:

1. Click Computer ManagementOperating System DeploymentBoot ImagesIBM Deployment.
   
2. Right-click the boot image and select Properties.
   
3. Click Images.
   
4. Check the OS Version property for a value of 6.0.6001.18000 or greater.

What to do if your boot images are not upgraded to Vista SP1

You can manually recreate your boot images using the Windows AIK and following the steps listed in Technet: How to Add a Boot Image to Configuration Manager.

If your Configuration Manager processes permit, you might find it easier to remove the old boot image packages using the Admin Console, delete the files in the OSD\boot directories, and rerun the SP1 upgrade installation.

How to tell if WAIK was upgraded to Vista SP1

1. Click Start > Run; then run the Regedit command.
   
2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ComponentStudio.
   
3. There should be a single key under this key, which is named with the number of the Windows AIK version.
   

   Note: Only one version of Windows AIK can be installed. However, an uninstall operation might have failed to remove the registry key.
   

   In such a case, the registry key with the highest version number should be the correct version number.

What to do if Windows AIK was not upgraded to Vista SP1

Configuration Manager is supposed to automatically upgrade the Windows AIK version during an upgrade to Configuration Manager SP1. If that did not occur, try manually uninstalling Windows AIK and rerunning the Configuration Manager SP1 upgrade.

To download Windows AIK, see the Microsoft Download Center: AIK page.

System environment variables are not carried over to the next action in the task sequence

When a task sequence runs, commands run in a command shell. When the task ends, so does the command shell environment, which causes the loss of any system variables that are defined in the task.

To pass variables between tasks, set the variables as “Task Sequence variables,” “Collection variables,” or “Machine variables.”

All Available IMP Links for SCCM destination

Many times people things about the destination of SCCM Available resources below are some i can suggest

Books:- Yep there are Three Books available below are the links

1) System Center Configuration Manager (SCCM) 2007 Unleashed by Kerrie Meyler $37.79 http://www.amazon.com/System-Center-Configuration-Manager-Unleashed/dp/0672330237

2) Mastering System Center Configuration Manager 2007 R2 by Chris Mosby $37.79

3) System Center Operations Manager 2007 Unleashed by Kerrie Meyler $40.94

 

CBT’s,

Yes there are two best CBT’s offered these are most popular

cbtnuggets

http://www.cbtnuggets.com/webapp/product?id=421

Exam-Pack 70-401: Microsoft Systems Center - Configuration Manager
$299.00 - Includes 20 Videos

 

CBT Planet

http://www.cbtplanet.com/microsoft-it/microsoft-system-center-configuration-manager-training-video.htm

Microsoft System Center Configuration Manager 2007 (SCCM) CBT Training Course

 

Topics Based Courses also offered from

http://blogcastrepository.com/level5/sccm/default.aspx

for some of them it is free and for most of them you need to pay :D

 

OK, Now Cools free supported WebPages for SCCM & SMS is below

• http://myitforum.com 
• http://myitforum.com/cs2/blogs/Bloggers.aspx 
• Microsoft SCCM Community Page
• System Center Home Page
• FAQShop
• System Center RSS Tags
• SCCM Tools & Utilities
• Server 2008 PKI Configurations
• technet.microsoft.com/en-us/systemcenter/cm/default.aspx
• http://blogs.technet.com/b/inside_osd/
• http://blogs.technet.com/b/configurationmgr/
• http://sccm2007.wordpress.com/
• http://blogs.technet.com/b/configurationmgr/
• http://blogs.technet.com/b/configmgr/
• http://myitforum.com/cs2/blogs/skissinger/
• http://www.windows-noob.com/forums/index.php?/forum/44-sms-sccm-2007-vnext/
• http://myitforum.com/cs2/blogs/dhite/

and also…..

Rod Trent's Blog

• myITforum Downloads
• myITforum Home Page
• myITforum News Blog
• myITforum User Blogs
• myITforum Book Store
• myITforum Columnists
• myITforum Forums Page
• myITforum User Groups
• myITforum Wiki Service
• myITforum Site News Blog
• myITforum Daily Newsletter
• myITforum Gear And Apparel
• myITforum Newsletters Blog
• myITforum Web Browser Toolbar
• myITforum Branded News Reader
• myITforum E-Mail Discussion Lists
• myITforum Home Page Search
• myITforum.com Polls

Great people Blogs:

• Anthony Clendenen
• Dan Thomson
• Garth Jones
• Michael Mott
• Rod Trent
• Ron Crumbaker
• Ying Li
• Jason Scheffelmaer
• Scott Moss
• Mike Lucero
• Matt Broadstock
• John Nelson
• Brian Tucker
• Steve Thompson
• Ronni Pedersen
• Jason Sandys
• Roger Zander
• David Stein

Below are the port Numbers used in SMS 2003

• Site Server to child and secondary sites as well as SMS SQL Server.
445 - Server Message Block (SMB)
389 - Lightweight Directory Access Protocol (LDAP)
636 - LDAP (Secure Sockets Layer (SSL) connection)

• Proxy Management point to parent SQL Server
1433 - TCP (SMS Site Server to SQL Server)
389 - LDAP
636 - LDAP (Secure Sockets Layer (SSL) connection)

• Advanced Client to Management Point and Distribution Point
80 - Hypertext Transfer Protocol (HTTP)
139 - Client sessions (for non BITS-enabled DPs)
445 - Server Message Block (for non BITS-enabled DPs)
389 - UDP (User Datagram Protocol) LDAP Ping
389 - TCP LDAP
636 - TCP LDAP (Secure Sockets Layer (SSL) connection)
3268 - TCP (Explicit connection to Global Catalog)

• Remote Control System service (Wuser32)
2703 - TCP SMS Remote Chat
2703 - UDP SMS Remote Chat
2701 - TCP SMS Remote Control (Control)
2701 - UDP SMS Remote Control (Control)
2702 - TCP SMS Remote Control (Data)
2702 - UDP SMS Remote Control (Data)
2704 - TCP SMS Remote File Transfer
2704 - UDP SMS Remote File Transfer

• Remote Control UDP *
137 - Name resolution
138 - Messaging
139 - Client sessions
* Only applies if you use NetBIOS over TCP/IP for SMS Remote Control
• Microsoft SQL Server
1433 - TCP SQL server
139 - TCP Named pipes

• Active Directory Discovery methods
389 - TCP LDAP
389 - UDP LDAP
636 - TCP LDAP (Secure Sockets Layer (SSL) connection)
135 - TCP RPC Endpoint Mapper
135 - UDP RPC Endpoint Mapper
3268 - TCP Global Catalog LDAP
3269 - TCP Global Catalog LDAP (Secure Sockets Layer (SSL) connection)
88 - TCP Kerberos
88 - UDP Kerberos

• Microsoft Windows NT UDP
53 – UDP Domain Name System (DNS)
67 – UDP Dynamic Host Configuration Protocol (DHCP)
135 – TCP Remote procedure call (RPC)
138 – UDP Windows Internet Name Service (WINS)
138 – UDP NetBIOS Datagram Service Computer Browser
139 – TCP NetBIOS Datagram Service Messenger

OSD Log Files Location

Unfortunately, the smsts.log can be stored in one of 7 locations, depending on the stage of the build and the architecture of the OS:

• WindowsPE, before HDD format:
        x:\windows\temp\smstslog\smsts.log

• WindowsPE, after HDD format:
        x:\smstslog\smsts.log and copied to c:\_SMSTaskSequence\Logs\Smstslog\smsts.log

• Full version windows, before SCCM agent installed:
        c:\_SMSTaskSequence\Logs\Smstslog\smsts.log

• Full version windows, after SCCM agent installed:
        c:\windows\system32\ccm\logs\Smstslog\smsts.log

• Full version x64 windows, after SCCM agent installed:
        c:\windows\sysWOW64\ccm\logs\Smstslog\smsts.log

• After Task Sequence has finished running
        c:\windows\system32\ccm\logs\smsts.log

• After Task Sequence has finished running(x64)
        c:\windows\sysWOW64\ccm\logs\smsts.log