You now have Windows 7 and Windows Server 2008 R2 support for ConfigMgr 2007 and 2007 R2.  Service Pack 2 has been released and adds a bunch of new functionality:

“Service Pack 2 for Configuration Manager 2007 delivers new platform support for Windows 7 client, Windows Vista SP2, Windows Server 2008 R2 and Windows Server 2008 SP2. In addition, Service Pack 2 delivers continued innovation with Intel vPro technology, support for Branch Cache enabled environments, and continued development for 64 bit architectures.

New Operating System Support

• Windows 7
• Windows Vista Sp2
• Windows Server 2008 R2
• Windows Server 2008 SP2

New Features in Out of Band Management

In addition to providing feature parity with SP1 and AMT firmware versions 3.2.1, 4.0 and 5.0, the following new features are supported:

• Wireless management with up to 8 wireless profiles
• End point access control: 802.1x support
• Audit logging
• Support for different power states
• Power control options at the collection level
• Data storage
• Scheduling configuration for in-band provisioning

Asset Intelligence Certificate Requirement Removal

Configuration Manager Service Pack 1 introduced Asset Intelligence v1.5. This version allowed customers to configure an online synchronization to ensure that their catalogue was up to date with the latest Microsoft inventory for both hardware and applications. This initial release required a certificate. With Service Pack 2, the requirement to have the certificate has been removed, so any customer can configure their Asset Intelligence capabilities to connect online and update their catalogue. Software Assurance is not required for this functionality.

64-bit Architecture Development

Service Pack 2 will also continue to deliver new support for x64 architectures, including the following:

• X64 support for Operations Manager 2007 Client Agent
• Update to Management Packs for 64-bit operating systems - SP2 will ship 64-bit performance counters (the management pack is a separate release)
• Remote control support added for x64 XP and x64 Server 2003

Improved Client Policy Evaluation

• Faster policy processing
• More efficient software distribution configured to run at user logon

Branch Cache Support

Support for scenarios where Windows Server 2008 R2 and Windows 7 Client are present and Branch Cache is enabled”

Architecturally, the BranchCache support is quite a cool option.  Now you can start looking at the need for branch distribution points.  Secondary sites are probably still a requirement in bandwidth sensitive branch sites to restrict and control that management traffic in larger individual branch office deployments.

You’re also starting to see how the ConfigMgr team is paying attention to power at the desktop.  See what’s happening with the R3 release and you’ll see they are very serious about conserving power in the office.

The beta (pre release testing) program of SCE 2010 has started.  SCE is the product that includes some of the key features of System Center Configuration Manager and Operations Manager in an integrated package.  Some of the new features included are:

• Integrated server virtualization management support, built on VMM 2008 R2 technology, including easy template-based creation of new virtual servers and live migration
• Adjusted licensing limits to allow for management of virtual servers
• Rewritten setup for an easier, intuitive installation
• Built-in automatic Microsoft Update subscription maintenance
• Provided flexible computer grouping
• Added additional software distribution target criteria

You can read that 1st one as VMM 2008 R2 integration.

Microsoft announced the future for ConfigMgr (SCCM) with a 2007 R3 release.  The focus appears to be squarely on power conservation on the desktop.  Expect a beta at the end of October and a RTM in Q1 2010.  More details of features will be released later.

The Configuration Manager Support Team has posted a step-by-step guide for doing OSD (operating system deployment) using ConfigMgr 2007.

Microsoft has published the first part of an article on out of band management using System Center Configuration Manager 2007.

“Out of Band Management is a management technology that does not rely on an operating system to manage target machines. Currently, both Intel Active Management Technology (AMT) and DMTF's Desktop and mobile Architecture for System Hardware (DASH) support Out of Band Management. In ConfigMgr 2007 SP1, we have integrated AMT technology into the product - this becomes the so called Out of Band Management feature …”

Have a read of it.  Once you do, you'll see the power that can be in the hands of administrators.  This helps you with branch office infrastructure cost optimisations no end.  Zero-touch management and deployment is here and it's for real.

Dell takes integration with Microsoft System Center very seriously.  Proof of that is their MVP’s on staff.  They’ve released the Dell Deployment Pack to assist with deploying your Dell systems with Configuration Manager 2007 SP1.  It’s a GUI tool so less confusing command line magic is required.  According to the site:

“Overview of Dell Deployment Pack Features

Using the ConfigMgr Task Sequence Editor, you can do the following with the Dell Deployment Pack:

• Configure your system's Baseboard Management Controller (BMC), Dell Remote Access Controller (DRAC), Redundant Array of Independent Disks (RAID), and BIOS. You can configure BIOS and RAID using .ini files. You can configure your system settings using the GUI or command-line interface (CLI) options. You can also configure RAID using the Array Builder wizard.
• Create a Dell-specific boot image that will be used in the OS deployment.
• Create and apply driver installation packages for specific Dell systems.

System Requirements

• Microsoft System Center Configuration Manager with Service Pack 1 or newer
• At least 1 GB of free disk space on the same drive that contains the ConfigMgr installation files
• A configured Network Access Account for ConfigMgr site(s).

Supported Hardware Systems

The Dell Deployment Pack 1.0 supports the following Dell PowerEdge™ systems:
PowerEdge 800, 830, 840, 850, 860, 1850, 1855, 2800, 2850, 6800, 6850, 1900, 1950, 1955, 2900, 2970, 6950, SC1435, 2950, T105, R200, R900, R805, M600, M605, T605, R300, T300, R805, PV0100, PV0500, PV0600, NX1950, M805, M905, and R905.

Supported Operating Systems

• Microsoft Windows Server® 2003, Small Business Server (SP2, R2)
• Microsoft Windows Server 2003 x86, x86_64 Edition SP2 and SP2 R2
• Microsoft Windows Server 2008 Standard and Enterprise Editions (x86) and (x86_64)
• Microsoft Windows® Small Business Server 2008 x64 (64 bit Edition)
• Microsoft Windows Essential Business Server 2008 x64 (64 bit Edition)”

I just saw an updated support statement for SMS 2003 and Configuration Manager 2007 with SQL 2005 SP3.

MS has released SCUP 4.5 for publishing your own updates via ConfigMgr 2007/2007 R2 or SCE 2007.

• SQL 2008 is supported.  This requires 2 hotfixes.
• Hyper-V is supported as a VM platform for site systems.
• Windows Mobile 6.1 is supported.
• Application Compatiibility Toolkit 5.0.3 is supported.
• .NET 3.5 SP1 is supported for the admin MMC and Desired Configuration Management.

One of the things I've disliked about OSD or OS Deployment in SMS and SCCM 2007 was the need to pre-configure computer accounts using information gathered from the hardware.  It kinda killed the idea of zero touch deployment.

SCCM 2007 R2 takes care of that and you can read how in this article.

Microsoft has released a ConfigMgr Desired Configuration Management template pack for auditing the energy saving settings of your computers.  Whether you believe in global warming or not, there's no denying that oil reserves are reducing and energy costs are rocketing.  Governments are also considering carbon footprint charges.  Anything you can do to reduce energy costs, i.e. reducing that carbon footprint, will save the business money.

Make use of the power control settings in Vista (via group policy) and make use of Configuration Manager DCM to monitor them and you might just reduce the operating costs of your business.

Microsoft has just released this very handy utility for SCCM 2007.  It previously was released for SMS 2003.

Imagine this scenario.  You've got a HQ running System Center Configuration Manager 2007.  You've got a series of branch offices with limited bandwidth and local distribution points.  You want to deploy your latest build of Office 2007.  Now that is a big package.  You could let it replicate over the WAN at the weekend but maybe your business is open 7 days a week.  I've seen this scenario where SMS controlled the PC's in a retail operation whose market was 7 days a week.  Using this tool, you could conceivably distribute the package via DVD and manually load it into your distribution points.  Sure, this is manual work but it's meant to be used in only those exceptional circumstances where there are huge packages to replicate.  Once you've imported the package on the distribution point, you add the site to the package properties in the SCCM console.

Here's how MS describes it:

"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".

System Center Configuration Manager 2007 Release 2 (SCCM R2) is available for download for the purposes of testing and evaluation.  What does this offer you?

• Support for application virtualisation (SoftGrid) - I like the sound of SoftGrid and know some people who rave about it.  Haven't played with it yet because it's got a limited (Software Assurance) market.
• ForeFront Client Security integration - I was just asked about this yesterday.
• Report on SCCM 2007 R2 using SQL Reporting Services - This will probably appeal to the larger customers who have SQL Reporting skills in house.  Honestly, that's not all that common a skill.
• Client health monitoring using a set of tools and reports - Yeah!  This is necessary.  The most common problem I have had with the SMS family is clients failing because of "stale" computer accounts.
• OS Deployment Improvements: Deploy to a computer without pre-configuring a computer account.  Excellent!  Who needed all that extra manual work.  I might as well have just used ImageX.  Now we have a solution I can live with.  Multicast Deployment is added.  That's the last justifiable criticism the Ghost fans had.  You can also now run command line tasks using alternate credentials.

One final note.  Some of the rather quick SCCM MVP's have found that the R2 installation (20MB which installs on top of SCCM 2007 SP1) will only install on an evaluation edition of SCCM 2007 SP1.  Doh! 

I'm planning on installing a Hyper-V lab at home this week so I can get playing.

WOW!  I just got a mail from the folks in Microsoft telling me that I've been awarded an MVP for SCCM 2007.  I am absolutely chuffed.  I'm supposed to be living on a budget but I feel some nice beer coming my way tonight.

That email was a real shot in the arm.  Gotta get back to the writing again :)