OS Deployment Guide for ConfigMgr 2007

  Here is a 160 pages of step-by-step instructions on how to successfully deploy Operating Systems with SCCM. Nico does a brilliant job of augmenting MS documentation, as well as clarifying all the acronyms associated with the product.

Dowload Link here - http://cid-18bc7bd65ad851b6.skydrive.live.com/self.aspx/Public/OSD%20in%20SCCM.pdf

Windows 7 Tips&Tricks

  I found this .pdf document which is created by 'Vasu Jain' on a google search, and would like to share the same with you all. This document has few tips & tricks that has not been told in any other documents i visited.

Thanks for the same Vasu.

http://windowsvj.com/wpblog/downloads/Windows 7 Tips & Trics [Vasu Jain].pdf

Ref: http://windowsvj.com/wpblog/downloads

SCCM 2007 Superflows - Released

Check the Link below:

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

Daily SCCM Administrative Activities: ConfigMgr'07 Inboxes to Monitor

   Listed here is a list of the ConfigMgr 2007 inboxes that should be checked on a regular basis to ensure that your site(s) function as expected.

Auth\Dataldr.Box

A backlog of files can indicate problems accessing the site database.

Auth\Dataldr.Box\Process

A backlog of files can indicate problems accessing the site database.

Auth\Ddm.box\Bad_DDRs

A backlog of files can indicate a network corruption problem or a problem with the DDM

Auth\Sinv.Box

A backlog of files can indicate that the Software Inventory Processor cannot connect to the site database or that too many files were received.

Auth\Sinv.Box\Orphans

A backlog of files can indicate problems with specific clients, with management points, or with the network that could cause data corruption.

Compsumm.Box

A backlog of files can indicate that the Component Status Summarizer cannot process the volume of messages.

Dataldr.Box

A backlog of files can indicate problems accessing the Systems Management Server (SMS) database

Dataldr.Box\Badmifs

A backlog of files can indicate a bad custom MIF file or that a client computer cannot transfer the file correctly.

Ddm.Box

A backlog of files can indicate a bad DDR is preventing other DDR’s to process.

Ddm.Box\Bad_DDRs

A backlog of files can indicate a network corruption problem or a problem with the DDM

OfferSum.Box

A backlog of files can indicate a performance problem that is caused by a large number of messages.

Policypv.Box

A backlog of files in the policypv.box folder indicates that the policy provider component is not running.

Replmgr.Box\Ready

A backlog of files can indicate that the Scheduler is backlogged or is already processing files of the same priority

Schedule.Box

A backlog of files can indicate that the Sender cannot connect to or cannot transfer data to another site.

Schedule.Box\Outboxes

A backlog of .srq files indicates that the sender cannot process the number of jobs scheduled for that sender or that the sender cannot connect to or transfer data to another site.

Schedule.Box\Tosend

A backlog of files can indicate that many send requests are not completed or that the Scheduler has not yet deleted the files.

Sinv.Box

A backlog of files can indicate that the Software Inventory Processor cannot connect to the site database or that too many files were received.

Sinv.Box\BadSinv

A backlog of files can indicate problems with specific clients, with management points, or with the network, causing data corruption.

SiteStat.Box

A backlog of files can indicate a performance problem. Examine status messages for the Site System Status Summarizer for possible problems.

Statmgr.Box\Futureq

A backlog of files can indicate that some site systems' clocks are not synchronized with the site server.

Statmgr.Box\Queue

A backlog of files can indicate a problem with the Status Manager or that the component is trying to process too many messages.

Statmgr.Box\Retry

A backlog of files can indicate problems with the connection to the computer that is running SQL Server.

Statmgr.Box\Statmsgs

A backlog of files can indicate a problem with the Status Manager or that the Status Manager is trying to process too many messages

Swmproc.Box

A backlog of .sum and .sur files can indicate that the Software Metering Processor component cannot connect to the SMS database.

SCCM and SQL Reporting Services

   With the R2 release, SCCM now supports the use of SQL Reporting Services as a reporting solution.  This will be the direction for reporting going forward and offers a good number of exciting possibilities for building impactful custom reports.  In the January edition of Technet magazine Steve Rachui published an article discussing this feature and showing a sample method for building custom reports.

Create a Robust, Integrated Reporting Solution - http://technet.microsoft.com/en-us/magazine/ee914611.aspx

Difference between WQL and SQL in SCCM

Below are few points which make difference between WQL and SQL :

1. WMI provides its own query language that allows you to query managed objects as data providers
2. WMI Query Language (WQL) is essentially a subset of SQL (Structured Query Language) with minor semantic changes.
3. Unlike SQL, WQL does not provide statements for inserting, deleting, or updating data and does not support stored procedures.
4. WQL does have extensions that support WMI events and other features specific to WMI. WQL is the basis for Configuration Manager queries, whereas SQL is used for ConfigMgr reports.
5. One important advantage of WQL is that a WQL query can return WMI objects as well as specific properties.
6. Because management applications such as the Configuration Manager console interact with WMI objects, WQL queries can return result sets that you can use within the ConfigMgr infrastructure.

Eg: Configuration Manager collections are based on WQL queries.

Ref: http://systemcentersupport.blogspot.com/2010/01/what-is-wmi-query-langauge-or-wql.html

ConfigMgr Patch Installer Tool/Script

   The ConfigMgr Patch Installer is a tool (vbscript) which can be used for installing updates which are advertised from SCCM. If the updates are advertised without a deadline. Especially it is useful for Windows Server 2008 Core edition as they do not have a GUI and so the updates can't be installed. This tool will query SCCM for each Update which is advertised to the System and will install it. The result can be displayed in a output logfile.

The Tool can be downloaded at:

• systemcentercentral.com - http://www.systemcentercentral.com/tabid/144/indexId/64192/Default.aspx

• winoneclick.com - http://www.winoneclick.com/

Ref: http://pleasepressanykey.blogspot.com/2010/08/configmgr-patch-installer.html

Microsoft Information Worker Management Pack

Applies To: Microsoft Office, Operations Manager 2007, Operations Manager 2007 R2.

   The Microsoft Information Worker Management Pack monitors the health, reliability, and performance of Microsoft Office applications and certain Microsoft Windows applications such as Microsoft Windows Explorer, Microsoft Internet Explorer, Windows Media Player, Microsoft Mail and Outlook Express.

Objects Discovered by the Information Worker Management Pack

   The Information Worker Management Pack discovers the object types described in the following list in this section. All the objects are automatically discovered by default. You can use overrides to disable objects you do not plan to monitor.

Information Worker Applications	Application Versions
Internet Explorer	5 through 7
Media Player	6 through 11
MSN and Windows Messenger	3 through 7
Outlook Express	Internet Explorer 5 through 7
Windows Explorer	Windows 2000 and Windows XP
Access	Office XP, Office 2003, and Office 2007
Communicator	2005 and 2007
Excel	Office XP, Office 2003, and Office 2007
FrontPage	Office XP and Office 2003
Groove	Office 2007
InfoPath	Office 2003 and Office 2007
LiveMeeting	Internet Explorer 7 and Office 2007
OneNote	Office 2003 and Office 2007
Outlook	Office XP, Office 2003, and Office 2007
PowerPoint	Office XP, Office 2003, and Office 2007
Project	Office XP, Office 2003, and Office 2007
Publisher	Office XP, Office 2003, and Office 2007
Visio	Office 2003 and Office 2007
Word	Office XP, Office 2003, and Office 2007

The Information Worker Library Management Pack provides generic monitoring capabilities that work for all the applications, and specific monitoring capabilities for individual applications.

• Generic monitoring:
• Crash detection
• Hand detection
• CPU utilization
• Memory utilization
• Individual application monitoring:
• Outlook mail access
• Web access
• Data source access

Ref: http://technet.microsoft.com/es-es/library/dd351475.aspx

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

Configuration Manager (SCCM) Features

   If you install a Microsoft System Center Configuration Manager 2007 site but do not configure any of the features, the site is essentially useless. Features provide the actual functionality of Configuration Manager 2007. You can install just one feature or several features. Some features have dependencies on other features, for example Network Access Protection requires the software updates feature be operational first.

   The following features are provided in Configuration Manager 2007:

• The administrator console
• Collections
• Inventory
• Queries
• Reporting
• Software distribution
• Software updates
• Software metering
• Mobile Device management
• Operating system deployment
• Desired configuration management
• Remote tools
• Network Access Protection
• Wake On LAN
• Out of band management
• Client Status Reporting
• SQL Reporting Services
• Power Management

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

Teredo - Windows

   Teredo is an IPv6 transition technology that allows automatic IPv6 tunneling between hosts that are located across one or more IPv4 NATs. To traverse IPv4 NATs, IPv6 packets are sent as IPv4 User Datagram Protocol (UDP) messages. If the NAT supports UDP port translation, then the NAT supports Teredo. The exception is a symmetric NAT.

   Teredo allows nodes located behind an IPv4 NAT to obtain IPv6 unicast connectivity by tunneling packets over UDP/IPv4. This service has 3 entities: the "Teredo Server", the "Teredo Relay" and the "Teredo client". A Teredo Server is stateless whereas the Teredo Relay keeps a state of each peer.

   Teredo is designed as a last resort transition technology for IPv6 connectivity. If native IPv6, 6to4, or Intrasite Automatic Tunnel Addressing Protocol (ISATAP) connectivity is present, the host does not act as a Teredo client. As more IPv4 edge devices are upgraded to support 6to4 and IPv6 connectivity becomes ubiquitous, Teredo will be used less and less until finally it is not used at all.

   Note: Teredo interface is primarily supported by Windows Vista & Windows Server 2008. Limited functionality of Teredo Interface supported (solicited traffic can be received) by Windows XP SP2 & Windows Server 2003.

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