System Center Web Log by Dan Conley : SCCM

ConfigMgr 2007 TechNet Chat Transcripts have been posted

dconley — Tue, 07 Aug 2007 22:43:00 GMT

Last month we ran a series of TechNet web chats on some of the features in ConfigMgr 2007. The transcripts to those chats have now been posted to TechNet. The best way to get to them is via the new ConfigMgr TechNet Tech Center's community page. The link is right at the top: http://technet.microsoft.com/en-us/configmgr/bb625749.aspx

SCCM 2007 Deployment Pre-flight checklist

dconley — Fri, 27 Jul 2007 19:30:00 GMT

**Update****

I have received feedback that some folks are having problems with the below link. I will work with the connect folks to figure that out, in the meantime, I have attached the file directly to the blog. Hopefully, that will help.

********

When preparing to deploy SCCM 2007 in your lab or production environment there are a lot of things you need to do to help ensure that the server setup will run smoothly.

We developed something that we call the "Pre-Flight Checklist" as a way to help ensure that those tasks are complete before you even lauch setup.

It is in a format that enables it to be used the "good old fashioned" way, by printing it out, and phyiscally "checking off" each item once it is complete.

Please check it out and send us feedback on what you think works, doens't work or if anything you feel is missing.

https://connect.microsoft.com/content/content.aspx?ContentID=6028&SiteID=16

**Update****

I have received feedback that some folks are having problems with the above link. I will work with the connect folks to figure that out, in the meantime, I have attached the file directly to the blog. Hopefully, that will help.

Patching Standards or Objectives

dconley — Fri, 20 Jul 2007 21:15:00 GMT

Steve Pruitt has created a great blog post this topic. Check it out: http://myitforum.com/cs2/blogs/spruitt/archive/2007/07/19/patching-standards-or-objectives.aspx

SCCM 2007 RC1 has shipped!

dconley — Mon, 16 Jul 2007 19:38:00 GMT

RC1 of Configuration Manager 2007 has just been declared and is now available on Connect: http://connect.microsoft.com.

Look under Available Connections for Systems Center Configuration Manager 2007. Note you must be registered and signed in to Connect to see this Connection.

Spread the word.

Got Questions about System Center Configuration Manager?

dconley — Fri, 22 Jun 2007 22:02:00 GMT

Over the next few weeks the SCCM product team will be hosting a collection of TechNet web chats focusing on the following features:

· Deployment

· Operating Systems Deployment
Software Updates Management

· Desired Configuration Monitoring

· Internet Based Client Management and Native Mode

These web chats are a great way for you to interact directly with members of the product team in an informal “Q & A” online chat format.

We look forward to seeing you there!

Deploying System Center Configuration Manager 2007
Q&A with the SCCM 2007 Deployment Feature team.

Add to Calendar

June 29, 2007
10:00 A.M. Pacific Time
Additional Time Zones

EnterChatRoom

Operating System Deployment with System Center Configuration Manager 2007
Q&A with the SCCM 2007 OSD Feature Team

Add to Calendar

July 10, 2007
10:00 A.M. Pacific Time
Additional Time Zones

EnterChatRoom

Software Updates Management with System Center Configuration Manager 2007
Q&A with the SCCM 2007 Software Updates Management Feature Team

Add to Calendar

July 12, 2007
1:00 P.M. Pacific Time
Additional Time Zones

EnterChatRoom

Desired Configuration Monitoring with System Center Configuration Manager 2007
Q & A with the SCCM 2007 DCM Feature Team.

Add to Calendar

July 19, 2007
10:00 A.M. Pacific Time
Additional Time Zones

EnterChatRoom

System Center Configuration Manager 2007 Internet Based Client Management and Native Mode
Q & A with the SCCM 2007 Client team focusing on Internet Based Client Management and Native Mode Security Configuration.

Add to Calendar

July 24, 2007
10:00 A.M. Pacific Time
Additional Time Zones

EnterChatRoom

Inventoy Tool for Custom Updates

dconley — Tue, 19 Jun 2007 23:45:00 GMT

I recevied some feedback that I didn't include information about the ITCU when I did my post about the SMS 2003 scan tools.

So, here you go:

Inventory Tool for Custom Updates (ITCU): This scan tool ships as one of the features of SMS 2003 R2. It operates similarly to the other scan tools in that it has a scan component and a catalog of metadata that is used to detect applicability, installation and "IsInstalled" rules. The big difference is that the catalog is not sync'd on a schedule and must be manually done via the Custom Updates Publishing Tool (CUPT).

The publishing tool is where the real magic and power of this feature come into play as it enables customers, ISV's, OEM's, etc. to generate thier own catalogs for LOB or 3rd party updates. There are already a few ISV's that have created catalogs, you can find them here: http://www.microsoft.com/smserver/partners/itcucat.mspx

System Center Updates Publisher (SCUP): This is the next generation of the publishing tool, and primarily designed for use with System Center Configuration Manager and System Center Essentials. You can find more information about SCUP in Jason Lewis's blog here:

http://blogs.technet.com/jasonlewis/default.aspx

SMS 2003 Patch Scan Tools

dconley — Tue, 05 Jun 2007 03:56:00 GMT

Hello everyone! My name is Dan Conley and I am a Program Manager on the SMS/SCCM Sustained Engineering team. One of the many areas I am responsible for is the monthly "Patch Tuesday" processes for the SMS team. This means that my team tests and validates that all of the SMS Patch tools can successfully detect and deploy that months security updates prior to thier release.

As the inagural post of this blog, I thought I would answer a question that I get a lot: "What are all of the Patch Scan tools that SMS 2003 supports, and when should I use one vs. the other"?

SMS 2003 supports the following software update (a.k.a. patch) scan tools:

Security Update Inventory Tool (SUIT) - This was the first "generation" of the SMS scan tools and is based on the MBSA 1.2.1 scan engine.

Office Inventory Tool for Updates - (ODT) This scan tool is based on the Office Updates Dectection Tool (ODT) from the Office Deplopyment Resource kit. This is also the same technology that the stand alone version of MBSA 1.2.1 uses for its Office update detection.

Both of the above scan tools are bundled together and are collectivley called the "Systems Management Server 2003 Service Pack 1 Scan Tools" Don't be confused by the name, as both of these tools work just fine on SMS 2003 SP2 and SMS 2003 SP3.

Entended Security Update Inventory Tool (ESUIT) - this scan tool is based on the stand alone Enterprise Scan Tool (EST). The MBSA 1.2.1 scan engine has a hard coded list of products it can support. Therefore we were forced to create a tool to "fill the gaps" so to speak. The ESUIT is fills that gap. Unlike the SUIT or ODT which will automatically (in the default configuration) "sync" a new catalog every month, the ESUIT must be downloaded and installed on the site servers in order to ensure you are scanning with the latest catalog.

The combination of the SUIT, ODT and ESUIT will provide SMS 2003 customers with complete Microsoft Security Update detection and deployment coverage for all but the latest products.

This is important: Due to the limited archtiecture of these legacy scan tools, most new products are not supported. For example, Windows Vista, Internet Explorer 7, SQL Server 2005, Exchange 2007, etc. Check out the MBSA home page for the latest product list and information.

Intventory Tool for Microsoft Updates (ITMU) - This is the latest generation of security update scan tools for SMS 2003. It is based on the Microsoft Update offline catalog, and contains security udpates, update rollups, and service packs for all products supported by WSUS. ITMU was designed to replace the need for the original 3 separate scan tools, and allow SMS admins to only have to manage one scan tool.

If all of the prodcuts in your environment are currenlty supported by WSUS, then you can (and should) only use ITMU as your security update tool for SMS 2003.

The most common caveot that I see is that some customers still need to support Office 2000 in thier environment, and ITMU does not support Office 2000 updates. In these cases, you have a few options, but all of the scan tools can coexist, therefore it is possible to run ITMU for everything, and just use the ODT for the machines that are still running Office 2000.

Thanks,

-Dan-