During the last couple of days Microsoft has been migrating, the System Center Configuration Manager 2007 forums to a new and updated version.

The forum migration is now completed and I encourage you all to try the new forum. So far it everything seems to be both faster and more reliable.

Microsoft TechNet Forums
http://social.technet.microsoft.com/Forums/en-US/categories/ 

System Center Configuration Manager 2007 - Forum list
http://social.technet.microsoft.com/Forums/en-US/category/configurationmanager/

Here is each individual one if you are interested in only a single one:

Date: 
Friday, December 19, 2008
11:30 AM Pacific Time (US & Canada)

Microsoft System Center Configuration Manager 2007 R2 includes integrated provisioning and management support for Intel vPro/Active Management Technology (AMT) hardware management technologies. This integration provides a strong solution for enterprise management of both desktop software and hardware platforms within a single unified administration console. Join this webcast to learn how to provision and use vPro to extend the capabilities of System Center Configuration Manager to incorporate secure hardware and power management for a truly green managed enterprise desktop solution. Topics include:

• System Center Configuration Manager 2007 R2
• Intel vPro hardware management and security
• Centralized Intel vPro provisioning
• Remote troubleshooting with Intel vPro hardware management
• Centralized power management
• Secure wake and update

Presenter: Keith Mayer, Senior Consultant, WrightRobbins, Inc.
For the past 15 years, Keith Mayer has focused on design, implementation and training of Information Technology projects for large global organizations. Currently, Keith is working with Intel to support enterprise network technologies and initiatives.  Keith focuses on development and delivery of best practices in training and learning consulting services to a worldwide audience of Intel and Microsoft partners and customers. Keith also works closely with industry organizations as a subject matter expert in the areas of project management, datacenter consolidation and virtualization.

Register for this Live WebCast:
http://www.microsoft.com/events/EventDetails.aspx?CMTYSvcSource=MSCOMMedia&Params=%7eCMTYDataSvcParams%5e%7earg+Name%3d%22ID%22+Value%3d%221032392909%22%2f%5e%7earg+Name%3d%22ProviderID%22+Value%3d%22A6B43178-497C-4225-BA42-DF595171F04C%22%2f%5e%7earg+Name%3d%22lang%22+Value%3d%22en%22%2f%5e%7earg+Name%3d%22cr%22+Value%3d%22US%22%2f%5e%7esParams%5e%7e%2fsParams%5e%7e%2fCMTYDataSvcParams%5e

System Center Configuration Manager 2007 (RTM and SP1) now supports the use of SQL Server 2008 as a site database.  In order to upgrade a site-server database to SQL 2008 there are 2 hot fixes required:

• ConfigMgr 2007 RTM customers must apply hot fix KB955229
• ConfigMgr 2007 SP1 customers must apply hot fix KB955262

The following are requirements when performing a clean install on a SQL Server 2008 database:

• A clean install of ConfigMgr 2007 RTM on a SQL Server 2008 database is not supported.  You must first install SQL Server 2005, upgrade to SQL Server 2008 and then apply hot fix KB955229
• A clean install of ConfigMgr 2007 SP1 on a SQL Server 2008 database is supported, but should apply hot fix KB955262

Windows Server 2008 Hyper-V is now supported for Configuration Manager 2007 RTM and SP1

Support will be provided for client management, site server roles, and the administrator console running within a Hyper-V environment.   There are no hot fixes required for the release to support configuration scenario.  This applies to customers running Windows Server 2008 with Hyper-V RTM installed.

Application Compatibility Toolkit (ACT) 5.0.03 is now supported on Configuration Manager 2007 RTM and SP1 with the ACT Connector

Customers leveraging the ACT Connector may download ACT 5.0.3 which released on September 2, 2008.  The following is a summary of the Application Compatibility Toolkit Connector:

Update Compatibility Evaluator: Update Compatibility Evaluator Now Supports Vista and Server ’08 in addition to Win2K, XP and Server ’03 that were previously supported.

Windows Internet Explorer 8 Support: We now support Windows Internet Explorer 8. The Internet Explorer Compatibility Evaluator as well as the Internet Explorer Compatibility Test Tool are capable of identifying issues on websites and web applications when they are run on IE8.

Major Bug Fixes:

SUA:

• SUA Crashes if AppVerifier Log Entry is Badly Formed
• Failure to Create Shim Database Entry if Product Name Contains Special Characters: SUA was unable to create a shim database entry for an application if the application name contained special characters. This issue has been resolved in ACT 5.0.3.
• CorrectFilePaths Shim Fix: There was a bug in the Standard User Analyzer because of which the CorrectFilePaths shim (used to redirect the path to which files created by the application are written) was only shimming a single file-path relocation even if multiple files needed to be redirected. This has been fixed in the current version of ACT.

ACM:

• The Application Compatibility Manager no longer requires elevation of user privileges to run in Vista.

.NET Framework 3.5 SP1 is now supported on Configuration Manager 2007 RTM and SP1

The .NET Framework 2.0 is a dependency for the Admin Console and the Desired Configuration Manager (DCM) feature of the client.  Typically the .NET Framework is a side-by-side (SxS) installation so compatibility is not a concern.  However, the .NET Framework 3.5 install performs an upgrade to the .NET Framework 2.0 and .NET Framework 3.0 behind the scenes, this is now fully supported.

Source: http://blogs.microsoft.co.il/blogs/dario/archive/2008/09/25/important-updates-regarding-sccm-2007-r2.aspx

Download the evaluation copy here:
http://www.microsoft.com/downloads/details.aspx?FamilyId=7376214F-CBA3-4E0D-81FE-AD52488BE3A3&displaylang=en

System Requirements:
System Center Configuration Manager 2007 SP1 Evaluation (you cannot install this version on a Volume License or MSDN installation).

The R2 release of System Center Configuration Manager is released today. Lots of people is already blogging about this new add-on to ConfigMgr. I haven’t played with all features yet, but the Client Status Reporting or “Client Health”, is one of the features I can’t wait to show to my customers. They will love it…

Another great feature is the support for Unknown Clients without using the MDT add-on. I’ve never been a big fan of MDT, so I really enjoy this update.

Version 5 is not around the corner so I wonder what will happen next… An R3 version or Feature Packs? Only the future will tell…

The download isn’t up yet but keep an eye on the System Center Configuration Manager 2007 Web site… Hopefully it will be there soon.

What's New in Configuration Manager 2007 R2
The following features are new to Configuration Manager 2007 R2:

· Application Virtualization Management. For more information about managing virtual applications created using the Microsoft Application Virtualization platform, see About Virtual Application Packages.

· Forefront Client Security Integration. For more information, see About Forefront Client Security Integration with Configuration Manager 2007 R2.

· SQL Reporting Services Reporting. Allows you to report on Configuration Manager activity using SQL Reporting Services.

· Client Status Reporting. Provides a set of tools and Configuration Manager 2007 reports to assess the status of client computers, sometimes referred to as "client health." Clients that show a change in activity patterns might need administrative intervention.

· Operating System Deployment Enhancements. The following enhancements are included in Configuration Manager 2007 R2:

· Unknown computer support—In Configuration Manager 2007 R2, you can deploy operating systems to computers using a PXE service point without first adding the computer to the Configuration Manager database. For more information, see About Unknown Computer Support for Operating System Deployment.

· Multicast deployment—Previously, all operating system deployments used unicast. Multicast can make more efficient use of network bandwidth when deploying large images to several computers at the same time. For more information, see About Multicast for Operating System Deployment.

· Running command lines in task sequences with credentials other than the local system account.

In the Introduction to System Center Configuration Manager 2007 – Part 1, we learned how to prepare Active Directory and how to configure Windows Server 2008 for hosting the Site Server role. In this part we’ll learn how to install and configure the Microsoft SQL Server 2005, Windows Server Update Service (WSUS) and finally System Center Configuration Manager 2007.

Installing and configuring Microsoft SQL Server 2005

In this test lab, the Domain Controller, the database and the Site Server will be installed on the same virtual machine. I wouldn’t recommend this in production, but for a testing scenario it’s just fine.

	Inset the installation media or mount the ISO file to the virtual machines DVD drive. If the “auto run” feature is disabled browse to the DVD drive and launch \Servers\default.hta
	Click “Install – Server components, tools, Books Online, and samples”.
	Click “Run program”.
	Select “I accept the licensing terms and conditions” and click “Next”.
	Click “Install”.
	Click “Next”.
	Click “Next”.
	Review the System Configuration Check and click “Next”.
	Type the Name and the Company and click “Next”.
	Select “SQL Server Database Services” and “Workstation components, Books Online and development tools” and click “Next”.
	Make sure that “Default instance” is selected and click “Next”.
	Select “Use the built-in System account” and click “Next”.
	Make sure that “Windows Authentication Mode” is selected and click “Next”.
	Accept the default settings and click “Next”.
	Select if you want to help Microsoft build better products and click “Next”.
	Click “Install”
	Click “Run program”.
	When the setup progress is completed click “Next”.
	Click “Finish” to complete the installation.
	It’s not required to restart the server, but I always do it anyway.

Installing Microsoft SQL Server 2005 Service Pack 2

Service Pack 2 for SQL Server 2005 is required to support both Windows Server 2008 and System Center Configuration Manager 2007.

Download Microsoft SQL Server 2005 Service Pack 2 here:
http://www.microsoft.com/downloads/details.aspx?FamilyId=d07219b2-1e23-49c8-8f0c-63fa18f26d3a&DisplayLang=en

	Launch “SQLServer2005SP2-KB921896-x86-ENU.exe”
	On the Welcome Screen click Next to continue.
	Select “I accept the agreement”, and click Next.
	On the “Feature Selection” page, accept the defaults and click Next.
	On the Authentication page, accept the defaults and click Next.
	On the “Error and Usage Reporting Settings” page, accept the defaults and click Next.
	Click “Next”.
	Click “Install”.
	Click “Run program”.
	Click “OK”.
	Click “Next”.
	Click “Next”.
	Unselect “Launch the user Provisioning Tool” and click “Finish”.
	Restart the server.

Installing Windows Update Service 3.0 SP1

Microsoft Windows Server Update Service 3.0 SP1 (WSUS) is required in order to deploy patches to the Configuration Manager Clients.

Windows Server Update Service 3.0 SP1 can be downloaded her: http://go.microsoft.com/fwlink/?linkid=93750

	Launch the WSUSSetup_30SP1_x86.exe
	Click “Next”.
	Select “Full Server installation” and click “Next”.
	Select “I accept the terms of the License agreement”, and click “Next”.
	Select “Store updates locally“and type the location where you want to store the updates. Choosing a separate (dedicated) drive is highly recommended in production, but not required. Click “Next”.
	Select Use an existing database server on this computer, and click “Next”.
	Click “Next”.
	Select “Create a Windows Server Update Service 3.0 SP1 Web Site” and click “Next”.
	Review the installation summary, and click “Next” to begin the installation.
	Click “Finish” to complete the installation.
	When the “Windows Server Update Service Configuration Wizard” appears click “Cancel”.

Installing System Center Configuration Manager 2007

Installing System Center Configuration Manager is very simple in a test setup, where everything is installed on the same box. In a production environment, you properly want to use more than one server, and you need to consider how to secure the communication between these servers and what service accounts is running the services, and what security permissions is required on the remote servers.

In this setup we use the same account (Administrator) for everything, so we´re ready to continue.

The valuation version of System Center Configuration Manager can be downloaded here:

http://technet.microsoft.com/configmgr/bb736730.aspx

	Inset the installation media or mount the ISO file to the virtual machines DVD drive. If the “auto run” feature is disabled browse to the DVD drive and launch \splash.hta
	Click “Install – Configuration Manager 2007 SP1”.
	Click “Next”.
	Select “Install a Configuration Manager site server” and click “Next”.
	Select “I accept these license terms” and click “Next”.
	Select “Custom settings” and click “Next”.
	Select “Primary site” click “Next”.
	Select “No, I do not want to participate right now” and click “Next”.
	Click “Next”.
	Accept the default destination folder and click “Next”.
	Type the Site code (LAB) and the Site name (Demo Site) and click “Next”.
	Select “Configuration Manager Mixed Mode” and click “Next”.
	Accept the defaults and click “Next”.
	Type the SQL server name (SERVER1) and the ConfigMgr site database name (SMS_LAB) and click “Next”.
	Type the SMS Provider (SERVER1) and click “Next”.
	Select “Install a management point” and type the FQDN name of the management point (SERVER1.CORP.DEMO.LAB) and click “Next”.
	Select “Use the default port (80)” and click “Next”.
	Select “Check for updates…” and click “Next”.
	Type the path where the updates should be saved (C:\Downloads) and click “Next”. Important The folder specified must exist. Otherwise the step will fail.
	When the prerequisite components has been downloaded click “OK”.
	Review the Settings Summary page and click “Next”.
	If all required prerequisite test has completed successfully click “Begin Install”.
	After about 15 to 30 minutes all action should be completed. Click “Next”.
	Click “View Log” or open the C:\ConfigMgrSetup.log if you want to review the setup log file. Click “Finish” to close the wizard.

Congratulation. You’ve now installed System Center Configuration Manager 2007 with Service Pack 1 on a Windows Server 2008 box.

Summary

This completes part 2 of this article. In the next part we’ll configure the Site Settings and install new site roles.

Introduction
When people that are new to Microsoft System Center Configuration Manager 2007, start playing around with the product in a test lab, they often want to start with a simple OS deployment setup. But if you are new to the product and wants to deploy Windows XP, getting started could be a bit challenging. This article (not sure how many parts it will contain yetJ), will be a guide through the basic steps, that needs to be configured in order to successful deploy Microsoft Windows XP Professional with Service Pack 3 and Windows Vista Enterprise with Service Pack 1.

This article is based on System Center Configuration Manager 2007 with Service Pack 1 and Windows Server 2008 RTM. All roles will be installed on a single box (virtual machine). Installing everything on the same box is not “best practice” in production.

The headlines for the first parts are:

• Part 1: Pre-Configuration Manager Installation tasks
• Part 2: Installing and Configuring Configuration Manager 2007 with Service Pack 1.
• Part 3: Preparing and Configuring Configuration Manager for OS deployment
• Part 4: Building the reference image
• Part 5: Deploying the client Operating System

Before we get started there are a few things that need to be configured. In my test lab I’m running Windows Server 2008 Enterprise Edition with Hyper-V, and I recommend the following settings for the virtual machine:

• CPU: 1 core (2 core recommended)
• RAM: min. 1024 MB (2048 recommended)
• Disk: 127 GB
• Network: 1 adapter (local only)

This guide assumes that Windows Server 2008 Enterprise Edition x86 with Service Pack 1 is installed and configured with the following settings:
(Installing Windows Server 2008 and Active Directory is not within the scope of this article).

• Static IPv4 address: 192.168.0.10
• Subnet mask: 255.255.255.0
• Default Gateway: 192.168.0.1
• Server name: SERVER1
• Active Directory Domain Service
  • Domain DNS name: corp.demo.lab
  • Domain NetBIOS Name: CORP
  • Forest Functional Level: Windows Server 2008
• DNS Server
• DHCP Server
  • Scope Name: SCCM Lab
  • Starting IP Address: 192.168.0.50
  • Ending IP Address: 192.168.0.99
  • Subnet Mask: 255.255.255.0
  • Default Gateway: 192.168.0.1
  • Subnet Type: Wired (lease duration will be 6 days)
  • Activate this scope: Yes

Part 1: Pre-Configuration Manager Installation Tasks

The System Center Configuration Manager 2007 requires a few things to be configured before installing the product. This part will guide you through these steps.

Extending the Active Directory Schema

Extending the Active Directory schema is a forest-wide action and must only be done once per forest. Extending the schema is an irreversible action and must be done by a user who is a member of the Schema Admins Group or by someone who has been delegated sufficient permissions to modify the schema.

Four actions need to be taken in order to successfully enable Configuration Manager Clients to query Active Directory Domain Services to locate site resources:

• Extend the Active Directory schema.
• Create the System Management container.
• Set security permissions on the System Management container.
• Enable Active Directory publishing for the Configuration Manager site.

How to Extend the Active Directory Schema Using ExtADSch.exe

You can extend the Active Directory schema by running the ExtADSch.exe file located in the SMSSETUP\BIN\I386 folder on the Configuration Manager 2007 installation media. The ExtADSch.exe file does not display output when it runs; however, it does generate a log file in the root of the system drive called extadsch.log, which will indicate whether the schema update completed successfully or any problems were encountered while extending the schema.

Step by step guide

• Backup the System State on the Domain Controller that holds the Schema Master role.
• Disconnect the Schema Master Domain Controller from the network.
• Run extadsch.exe, located at \SMSSETUP\BIN\I386 on the installation media, to add the new classes and attributes to the Active Directory schema.

• Verify that the schema extension was successful by reviewing the extadsch.log located in the root of the system drive.
• If the schema extension procedure was successful, reconnect the schema master domain controller to the network and allow it to replicate the schema extensions to the global catalog servers throughout the Active Directory forest.
• If the schema extension procedure was unsuccessful, restore the schema master's previous system state from the backup created in step 1 to reverse the schema extension actions before reconnecting the schema master domain controller to the network.

How to Create the System Management container using ADSIEdit

Configuration Manager does not automatically create the System Management container in Active Directory Domain Services, when the schema is extended. The container needs to be created once for each domain that includes a Configuration Manager Site server that will publish site information to Active Directory Domain Services. To manually create the System Management container using ADSI Edit, do the following steps:

• Log on as an account that has the Create All Child Objects permission on the System container in Active Directory Domain Services.
• Open the ADSIEdit MMC console, and connect to the domain in which the site server resides.

• In the console pane, expand Domain [computer fully qualified domain name], expand <distinguished name>, and right-click CN=System. On the context menu, click New and then click Object.
• In the console pane, expand Domain [computer fully qualified domain name], expand <distinguished name>, and right-click CN=System. On the context menu, click New and then click Object.
• In the Create Object dialog box, select Container and click Next.

• In the Value field, type System Management and click Next.

• Click Finish.

How to configure the security permissions on the System Management container.

After the System Management container has been created in Active Directory Domain Services, the primary site server's computer account must be granted the necessary permissions to publish site information to the container.

• Click Start, click Run, and enter adsiedit.msc to launch the ADSIEdit MMC console.
• If necessary, connect to the site server's domain.
• In the console pane, expand the site server's domain, expand DC=<server distinguished name>, expand CN=System, and right-click CN=System Management. On the context menu, click Properties.

• In the CN=System Management Properties dialog box, click the Security tab.
• Click Add to add the “SCCM Servers” Security Group and grant the account Full Control permissions.

• Click Advanced, select the “SCCM Servers” Security Group, and click Edit.
• In the Apply onto list, select “This object and all child objects”.

• Click OK. (3 times)

Enable Active Directory publishing for the Configuration Manager site.

Before Configuration Manager can publish site data to Active Directory Domain Services, the Active Directory schema must be extended to create the necessary classes and attributes, the System Management container must be created, and the primary site server’s computer account must be granted full control of the System Management container and all of its child objects. Each site publishes its own site-specific information to the System Management container within its domain partition in the Active Directory schema.

This part cannot be completed before Configuration Manager has been installed.

Configuring Windows Server 2008 for Site System Roles

Configuration Manager requires the WebDAV component to be installed and enabled on the management points and BITS-enabled distribution points. The WebDAV component is not included in Windows Server 2008 operating system and must be downloaded and configured manually.

Installing and configuring WebDAV for BITS-enabled distribution points and management points

• In Server Manager, on the Features node, start the Add Features Wizard.
  • On the Select Features page, select BITS Server Extensions.
  • When prompted, click Add Required Role Services to add the dependent components, including the Web Server (IIS) role.
  • On the Select Features page, select Remote Differential Compression, and then click Next.
  • On the Web Server (IIS) page, click Next.
  • On the Select Role Services page, under IIS 6 Management Compatibility, select IIS 6 WMI Compatibility.
  • Under Application Development, select ASP.NET and, when prompted, click Add Required Role Services to add the dependent components.
  • Update: Add ASP (required for ConfigMgr Reporting Point to function - thanks to Jens Ole Kragh for pointing this out)
  • Under Security, select Windows Authentication, and then click Next.
  • On the Confirmation page, click Install, and then complete the rest of the wizard.
• Download the x86 or x64 version of WebDAV at http://go.microsoft.com/fwlink/?LinkId=108052.
• Run either webdav_x86_golive.msi or webdav_x64_golive.msi, depending on your processor.
• Enable WebDAV and create an Authoring Rule, as follows:
  • Open Internet Information Services (IIS) Manager.
  • In the Connections pane, expand the Sites node in the tree, and then click SMSWEB if you are using a custom Web site or click Default Web Site if you are using the default Web site for the site system.
  • In the Features View, double-click WebDAV Authoring Rules.
  • When the WebDAV Authoring Rules page is displayed, in the Actions pane, click Enable WebDAV.
  • After WebDAV has been enabled, in the Actions pane, click Add Authoring Rule.
  • In the Add Authoring Rule dialog box, under Allow access to, click All content.
  • Under Allow access to this content to, click All users.
  • Under Permissions, click Read, and then click OK.
• Change the property behavior as follows:
  • In the WebDAV Authoring Rules page, in the Actions pane, click WebDAV Settings.
  • In the WebDAV Settings page, under Property Behavior, set Allow anonymous property queries to True.
  • Set Allow Custom Properties to False.
  • Set Allow property queries with infinite depth to True.
  • If this is a BITS-enabled distribution point, under WebDAV Behavior, set Allow access to hidden files to True.
  • In the Action pane, click Apply.
• Close Internet Information Services (IIS) Manager.

Summary

This completes part 1 of this article. In the next part we’ll install Microsoft SQL Server 2005, Windows Server Update Service (WSUS) 3.0 and System Center Configuration Manager 2007 with Service Pack 1.

Enjoy.

Living in a non-english speaking country like Denmark, I often have to deal with deploying English versions of Windows XP and/or Windows Vista, with other Regional Settings, Keyboard Settings, Time Zones etc.

In the past I've created a VBScript to modify the sysprep.inf or the unattend.xml, after laying down the image on the client. The values were configured with Collection Variables or Computer Variables. The script collected the value during deployment, and replaced the value in the sysprep.inf or unattend.xml file before restarting into mini setup.

This year at TechEd in Orlando, I attened a great session on Windows Deployment with Configuration Manager (Part 1 of 4) with Michael Kelly. In this session he showed a demo, where he created a custom variable ("XRes" and "YRes"), and typed the variable direct in sysprep.inf like this:

sysprep.inf:
[Display]
   XResolution=%XRes%
   YResolution=%YRes%

This was a simple example, but it gave me a lot of ideas to work with. And as a result of this, I no longer need my "fancy" script to take care of my deployments anymore. This is how I do it now (example):

For my Windows XP deployments I've created a sysprep.inf that looks like this:
(This can also be done with Windows Vista deployments, but you’ll need to use the unattend.xml and the format should be in XML).

sysprep.inf:
[GuiUnattend]
   TimeZone=%LAB_OSDTimeZone%
[ResionalSettings]
   SystemLocale=%LAB_OSDSystemLocale%
   SystemInput=%LAB_OSDSystemInput%
[Display]
   XResolution=%LAB_OSDXResolution%
   YResolution=%LAB_OSDYResolution%

The sysprep.inf file should be place in a package in order to use it from the task sequence.

In the “Deploy Windows XP” Task Sequence, you need to specify the sysprep.inf file in the “Apply Operating System” section, like this:

In order to use the sysprep.inf containing the variables we need to assign some variables to our collection first.

How to Create Collection Task Sequence Variables:

	In the Configuration Manager console, System Center Configuration Manager / Site Database / Computer Management / Collections.
	To assign a variable to a collection, right-click the collection, and then click Modify Collection Settings.
	Open the <New> Variable dialog box, click the Collection Variable tab, and then click the New icon.
	In the New Variable dialog box, specify a name (example: “LAB_OSDSystemInput”) for the variable. On the Value line, specify the Value (Example: 0406:00000406 for danish keyboard) of the variable, and if the value is masked, enter the value again to confirm the variable on the Confirm Value line, and then click OK.

You can also specify Precedence by selecting a numeric value from the drop-down list, where 1 is the lowest precedence, and 9 to specify the highest precedence. The Precedence level will be used when a computer is a member of multiple collections with differing precedence levels assigned.

You can also specify per-computer task sequence variables, by right-clicking the computer object, click Properties, and then click the Variables tab. Per-computer variables will allways overwrithe per-collection variables.

That’s all folks… No more scripting for modifying the sysprep.inf file during deployment :-)

Additional resources:

TimeZone codes: (scroll down to the end where you’ll find “TimeZone”)
http://technet2.microsoft.com/windowsserver/en/library/1cd05ce1-7eaa-4b03-bef5-772bb2d799eb1033.mspx?mfr=true

Locale ID’s and Input Locale:
http://www.microsoft.com/globaldev/reference/winxp/xp-lcid.mspx

Configuration Manager 2007 SP1 now offers full support for management with Windows Vista SP1 and Windows Server 2008, integrates customer feedback, feature Integration with Intel vPro Technology and enhances Asset Intelligent features.

Service Pack 1 itself includes: 

• Rollup of hotfixes since RTM
• Full Windows Vista SP1 and Windows Server 2008 Support
• Intel AMT Integration
• Asset Intelligence 1.5

Download

Download Size: 1039.0 MB... Happy Downloading :-)

When you deploy a Windows XP client with Configuration Manager OSD, and the user hits CTRL+ALT+DELETE, the user gets the usual logon screen, but with the target set to the machine name, and not the domain the computer is joined to. This is not the biggest problem on the planet, but why deal with it the problem could go away?

There are many workarounds to this issue, but I prefer using a "Post Configuration Task" in my Task Sequence. All you need to do is to configure two steps (Run Command Line) that will run the following commands:

reg add "HKLM\software\microsoft\windows nt\currentversion\winlogon" /v altdefaultdomainname /t REG_SZ  /d "DOMAINAME" /f

reg add "HKLM\software\microsoft\windows nt\currentversion\winlogon" /v defaultdomainname /t REG_SZ  /d "DOMAINAME" /f

“DOMAINNAME” in both lines must be replaced with actual domain name :-). Both steps must be executed before the last restart in the Task Sequence.

A question that seems to popup from time to time, is how to import HDC Storage drivers in Configuration Manager RTM.

When importing storage drivers into Configuration Manager 2007, not all types (Class), can be used (selected) from the Task Sequence wizard. This is a known bug.  At the time ConfigMgr 07 shipped, Microsoft were not aware of any mass storage drivers that used the HDC class, so only SCSIAdapters were flagged as boot critical (UPDATE: This issue is fixed in Service Pack 1). To workaround this issue you need to do the following:

When you import HDC storage drivers you need to point at the TXTSETUP.OEM file. This file depends on the *.inf file(s) where the Class is specified. If the “Class” is configured to “hdc”, you can’t select the driver from the “Apply Driver Package” in the Task Sequence. In order to use the driver you need to modify the *.inf file before importing the driver into the driver repository. Replace the “Class=hdc” with “Class=SCSIAdapter” under the [Version] section.

Example of an INF file:

[version]
CatalogFile=iaAHCI.cat
Signature="$WINDOWS NT$"
Class=SCSIAdapter
ClassGuid={4D36E96A-E325-11CE-BFC1-08002BE10318}
Provider=%INTEL%
DriverVer=03/21/2007,7.5.0.1017

This is how it should look like after the import:

If you modify the inf file after the import the driver should be deleted and re-imported.

Then you should be able to select the driver from the Task Sequense:

Download the Visio add in and the web server component to connect and generate datasets to connect to your existing diagrams or auto generate your diagrams for your infrastructure monitoring needs. See your data from OpsManager and ConfigManager live in Visio diagrams.

http://www.microsoft.com/downloads/details.aspx?FamilyID=521B3884-1EDA-4B9D-8AD7-67D00FE9CE8A&displaylang=en

The Software Updates Synchronization SuperFlow is a dynamic, interactive dataflow model that provides all of the information needed to understand the software updates synchronization process in Configuration Manager 2007. The SuperFlow also provides an animation for the process and resource files and links that provide information related to the process.

For many enterprise products, technical flowcharts can be an invaluable tool for IT Professionals to help them understand a feature or process within the product and to help them troubleshoot issues that might occur. The SuperFlow is a new concept that takes a technical flowchart to the next level by providing the following:

Interactive Flowchart

• General and in-depth technical information about each step in the process.
• Sample log files, status messages, including sample log file entries, procedures to accomplish tasks, troubleshooting information, and more!

Animation

• A visual representation for the steps in the SuperFlow process.
• A detailed description for each step in the SuperFlow process.

Resources

• Links to internal resources such as the detailed dataflow for the process, sample log entries for the end-to-end process, verification checklists, etc.
• Links to external Web resources that provide more information about the product and SuperFlow process.

Download:
http://www.microsoft.com/downloads/details.aspx?FamilyID=d509a9f4-e397-4d0a-89bb-fa3d68b9e8be&DisplayLang=en

This article contains links to all of the ConfigMgr 2007 Audiocasts on the Microsoft website.

System Center Configuration Manager 2007: Setup and Deployment (13 mins 25 secs)
Jeff Wettlaufer, Sr. Technical Product Manager, System Center Configuration Manager
Wally Mead, Sr. Program Manager, System Center Configuration Manager
In this episode of the Configuration Manager audiocasts, listen to Jeff Wettlaufer and Wally Mead discuss the best practice guidance and recommendations for how to install System Center Configuration Manager. From SMS upgrades to green field deployment, hear from the early experiences of Configuration Manager customers about deploying the infrastructure and clients.

System Center Configuration Manager 2007: Windows Deployment (11 mins 1 sec)
Jeff Wettlaufer, Sr. Technical Product Manager, System Center Configuration Manager
Michael Kelley, Sr. Program Manager, System Center Configuration Manager
A significant investment in System Center Configuration Manager 2007 is focused around Operating System Deployment. Taking advantage of new technologies in Windows Vista and Windows Server 2008, listen to Jeff and Michael talk about concepts such as the Task Sequencer, Driver Catalog, WinPE and other areas of OSD. Learn how the same toolset can be used for both Client and Server deployments, and how Configuration Manager can drive end to end automation into your next deployment project.

System Center Configuration Manager 2007: Desired Configuration Management (10 mins 22 secs)
Jeff Wettlaufer, Sr. Technical Product Manager, System Center Configuration Manager
Jeffrey Sutherland, Sr. Program Manager, System Center Configuration Manager
One of the key abilities in System Center Configuration Manager 2007 is the concept of Desired Configuration Management. DCM is a new approach to configuration management, using SML concepts to define Configuration baselines that can be used to monitor your enterprise. In this audiocast, listen to Jeff and Jeffrey discuss the concepts of configuration management, how to define configuration items, baselines, and the deployment of these in the network. Learn how to interpret this information, and understand the concept of analyzing Configuration Drift.

System Center Configuration Manager 2007: Software Distribution (9 mins 9 secs)
Jeff Wettlaufer, Sr. Technical Product Manager, System Center Configuration Manager
Dave Randall, Sr. Program Manager, System Center Configuration Manager

In this edition of the Configuration Manager audiocast series, listen to Jeff and Dave discuss the concepts of Software Distribution, what has improved, what is new, and the benefits these enhancements will bring to your organization.

System Center Configuration Manager 2007: Software Update Management (8 mins 33 secs)
Jeff Wettlaufer, Sr. Technical Product Manager, System Center Configuration Manager
Marc Umeno, Sr. Program Manager, System Center Configuration Manager
In this edition of the Configuration Manager audiocast, listen to Jeff and Marc speak about the improvements in Software Update Management. Some great improvements have been made to the previous collection of tools and processes, and learn how to employ these today in your organization.

Are you struggling with setting up ConfigMgr 2007 Operating System Deployment and integrating MDT? - download and view the video walkthrough that shows you how to:

• Setup the server environment for ConfigMgr 2007 OS deployment
• Configure the ConfigMgr 2007 Site Settings
• Configure the ConfigMgr 2007 Computer Management Settings
• Configure the ConfigMgr 2007 Operating System Deployment Settings
• Setup and use MDT integration with ConfigMgr 2007
• Add a reference machine object to ConfigMgr 2007
• Create a build and capture reference image for mass deployment using ConfigMgr 2007

Download from here (51.2Mb)

Source: The Deployment Guys

The Configuration Manager 2007 Software Development Kit (SDK) has been released and is now available on the Microsoft Download Center.

In addition to Service Pack 1 support for Windows Vista, MDT 2008 also has the following  new features:

• Full support for Windows Server 2008
• Additional Actions including Configure DHCP, Authorize DHCP, Configure DNS, and Configure ADDS
• New scripts that will automate the installation of Mass Storage Drivers for Windows XP and Windows 2003 Systems
• Ability to use a WSUS server for the Windows Update script
• Improved performance for the PXE Filter for System Center Configuration Manager unknown computer support
• Improved documentation including a new Quick Start Guide for System Center Configuration Manager and a guide for implementing the Management Pack for System Center Operations Manager

Download:
http://www.microsoft.com/downloads/details.aspx?FamilyId=064A995F-EF13-4200-81AD-E3AF6218EDCC&displaylang=en

Event ID: 1032369053

Language(s): English.
Product(s): System Center.
Audience(s): IT Professionals.
Duration: 90 Minutes
Start Date: Wednesday, February 27, 2008 1:00 PM Pacific Time (US & Canada)

Event Overview
Microsoft System Center Configuration Manager 2007 shipped recently, but we are not done yet! This year, we will also release a service pack and an R2. In this session, we cover the changes we are making in the System Center Configuration Manager 2007 Service Pack 1 (SP1) timeframe, in addition to the following System Center Configuration Manager 2007 R2 release. We briefly introduce System Center Configuration Manager, but our focus is on the new elements to support Windows Vista Service Pack 1, Windows Server 2008, in addition to some additional changes for Asset Intelligence and Intel AMT Integration.

Presenter: Jeff Wettlaufer, Senior Technical Product Manager, Microsoft Corporation

Register here.

What's New in Configuration Manager 2007 SP1

• Microsoft System Center Configuration Manager 2007 SP1 introduces a new feature for out of band management.
• Configuration Manager 2007 SP1 provides significant enhancements to the Asset Intelligence feature introduced in Systems Management Server (SMS) 2003 and included in Configuration Manager 2007.
• The length of the evaluation period has changed in Configuration Manager 2007 SP1 to be more consistent with other Microsoft products. In Configuration Manager 2007, the evaluation period is 120 days. In Configuration Manager 2007 SP1, the evaluation period is 180 days.
• The Application Compatibility Toolkit (ACT) Connector and the System Center Updates Publisher are no longer included with the Configuration Manager 2007 SP1 installation media.
• Microsoft System Center Configuration Manager 2007 SP1 provides support for Windows Server 2008 as clients and site systems.

Note
Windows Server 2008 does not include WebDAV by default, which is required for Configuration Manager 2007 management points and distribution points. For more information, see the release notes.

What's New in Configuration Manager 2007 R2

• Application Virtualization management support
• Forefront Client Security Integration
• SQL Reporting Services Reporting - Allows you to report on Configuration Manager activity using SQL Reporting Services
• Client Status Reporting - Provides a set of tools and Configuration Manager 2007 reports to assess the status of client computers, sometimes referred to as "client health." Clients that show a change in activity patterns might need administrative intervention.
• Operating System Deployment Enhancements
  • Unknown computer support
    In Configuration Manager 2007 R2, you can deploy operating systems to computers using a PXE service point without first adding the computer to the Configuration Manager database.
  • Multicast deployment
    Previously, all operating system deployments used unicast. Multicast can make more efficient use of network bandwidth when deploying large images to several computers at the same time.
  • Running command lines in task sequences with credentials other than the local system account.

If you haven't already joined, to get access to the program, which includes the ability to provide feedback, download pre-release bits, and use newsgroups for discussing product topics, please apply for the program here:
https://connect.microsoft.com/programdetails.aspx?ProgramDetailsID=1829