How to create a Windows XP SP3 Reference Machine using Configuration Manager 2007 SP1 R2

In this post, I will show how to deploy Windows XP SP3 (the easiest and least customizable way) in a virtual environment (Virtual PC 2005 SP1) step-by-step. This post is inspired from “Quick Start Guide for Microsoft System Center Configuration Manager 2007” document.

In this post, I will create a reference machine with Windows XP SP3 and will capture an image of it. And in the then next post, I will use the captured image to create a new task sequence that can be used to deploy Windows XP SP3 to target machines.

My environment is described below (note that all operating systems and products used are x86 versions):

Computer Description and system resources
Home-DC1 The computer runs Windows Server 2003 SP1 with the following roles and services installed:

  • AD DS
  • DNS Server
  • DHCP Server

The system resources of the computer are as follows:

  • Processor running at 2 gigahertz
  • 128 megabytes physical memory
  • One disk partition that has 35 gigabytes (GB) available disk space and that will become the drive C partition
  • One CD-ROM or DVD-ROM drive that will be assigned the drive letter D
Home-SCCM This computer runs SQL Server 2005 SP2 and System Center Configuration Manager 2007 SP1 R2 fully working. The computer runs Windows Server 2003 SP2 R2.
The system resources of the computer are as follows:

  • Processor running at 2 GHz
  • 1024 MB physical memory
  • 33 GB available disk space
Home-XPSP3-Ref01 This is the reference computer, which runs no current operating system.
The system resources of the computer are as follows:

  • Processor running at 2 GHz
  • 1024 MB physical memory
  • 65 GB available disk space
Home-XPSP3-Tar01 This is the target computer, which runs no current operating system.

  • Processor running at 2 GHz
  • 1024 MB physical memory
  • 65 GB available disk space

So, let’s start.

Prepare the environment

Create required folders and shares

The MDT 2008 deployment process requires additional folders that are used as the source for files or to store files created during the MDT 2008 deployment process. Some of these folders need to be shared so that they can be accessed from other computers.

To create the required folders and shares:

  1. On Home-SCCM computer, create the following folders:
    • Captures
    • Packages
    • Source
  2. Configure the following shares and permissions:
    Share name Share permissions Security permissions
    Captures$
    Packages$
    Source$
    Administrators: Full Control
    Everyone: Read
    SYSTEM: Full Control
    Administrators: Full Control
    Creator owner: leave as default
    SYSTEM: Full Control
    Users: Read & Execute, List Folder Contents
  3. Create the following subfolders:
    • Source\MDT2008
    • Source\Sysprep_XPSP3
    • Source\USMT301
    • Source\Windows_XPSP3
    • Packages\CustomSettings_Reference
    • Packages\CustomSettings_Target
    • Packages\ MDT_2008_Files
    • Packages \Sysprep_XPSP3
    • Packages \USMT301
    • Packages \Windows_XPSP3
    • Packages \WinPE_Custom

Note: Please note that I do not have the “Drivers” folder as I’m installing the OS in a virtual machine and I will not use any drivers.

Obtain the required software

Besides the OS, SQL, Configuration Manager and other software installed already, we will also need the software listed below:

Obtain this software Place in this folder
MDT 2008 Update 1, available at
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=3bd8561f-77ac-4400-a0c1-fe871c461a89
C:\Source\MDT2008
Windows XP SP3 distribution files from the product CD C:\Source\Windows_XPSP3
USMT version 3.0.1 available at
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=799ab28c-691b-4b36-b7ad-6c604be4c595
C:\Source\USMT301
Sysprep for Windows XP SP3 available at
http://www.microsoft.com/downloadS/details.aspx?FamilyID=673a1019-8e3e-4be0-ac31-70dd21b5afa7&displaylang=en
Extracted files from “deploy.cab” place in C:\Source\Sysprep_XPSP3

Install User State Migration Tool

The USMT is used to save and restore user state migration information.

Install USMT on Home-SCCM in order to extract the files needed to create the System Center Configuration Manager package.

To install USMT 3.0.1:

  1. In Windows Explorer, go to C:\Source\USMT301, and then double-click InstallUSMT301_x86.msi.
  2. Complete the installation wizard by accepting all the default values.
    This installs USMT in C:\Program Files\USMT301.
  3. Copy the USMT source files from C:\Program Files\USMT301 to C:\Source\USMT301.

Install Microsoft Deployment Toolkit 2008 Update 1

To install MDT 2008 Update 1:

  1. In Windows Explorer, go to C:\Source\MDT2008.
  2. Double-click MicrosoftDeploymentToolkit_x86.msi and then click Install.
  3. Click Next to skip the welcome page.
  4. On the End-User License Agreement page, review the license agreement, select I accept the terms in the License Agreement, and then click Next.
  5. On the Custom Setup page, click Next.
  6. Click Install.
    The installation process status is displayed, then finishes.
  7. Click Finish.

Enable Configuration Manager Console integration

To enable Configuration Manager console integration:

Note: Ensure that Configuration Manager Console is closed while performing these steps.

  1. Click Start, and then point to All Programs. Point to Microsoft Deployment Toolkit, and then click Configure ConfigMgr 2007 Integration.
  2. The Configure ConfigMgr 2007 Integration script starts.
  3. In the Configure ConfigMgr Integration dialog box, in Site server name, verify that the value entered is your site server name.
  4. In Site code, verify that the value is your site code, and then click Finish.

Import and configure a task sequence to create a reference computer

The reference computer is used as the template for deploying new images to the target computers. Configure this computer (Home-XPSP3-Ref01) exactly as the target computers will be configured. An image of the reference computer will be captured and the image deployed to the target computers.

Create a MDT 2008 task sequence for the reference computer

To create a task sequence for deploying the reference computer:

  1. Click Start, point to All Programs, and then click Microsoft System Center. Click Configuration Manager 2007, and then click ConfigMgr Console.
  2. In the Configuration Manager console tree, go to Site Database/Computer Management/Task Sequences.
  3. In the details pane, click Import Microsoft Deployment Task Sequence.
    The Import Microsoft Deployment Task Sequence Wizard starts.
  4. Complete the Import Microsoft Deployment Task Sequence Wizard by using the information in the table below. Accept the default values unless otherwise specified.
    On this wizard page Do this
    Choose Template Select Client Task Sequence, and then click Next.
    General In Task sequence name, type Windows XP SP3 Reference Deployment. In Task sequence comments, type Task sequence for deploying Windows XP SP3 to the reference computer (Home-XPSP3-Ref01), and then click Next.
    Details Click Join a workgroup.
    In Workgroup, type WORKGROUP.
    In User name, type Work User.
    In Organization name, type Work Organization.
    In Product key, type product_key (where product_key is the product key for Windows XP SP3).
    In Capture destination, type \\Home-SCCM\Captures$\Home-XPSP3-Ref01.wim.
    In Capture Account, click Set, and then complete the Windows User Account dialog box by performing the following steps:

    1. In User name, type Home\Administrator.
    2. In Password and Confirm password, type domain admin password.
    3. Click OK.

    Click Next.

    Boot Image Click Create a new boot image package.
    In Package source folder to be created, type \\Home-SCCM\Packages$\WinPE_Custom, and then click Next.
    Boot Image: General Settings In Name, type Windows PE Custom.
    In Version, type 1.00.
    In Comments, type Customized version of Windows PE to be used in deployment of reference and target computers, and then click Next.
    Boot Image: Image Options Click Next.
    MDT Package Click Create a new Microsoft Deployment Toolkit Files package.
    In Package source folder to be created, type \\Home-SCCM\Packages$\MDT_2008_Files, and then click Next.
    MDT Package: MDT Details In Name, type MDT 2008 Files.
    In Version, type 1.00.
    In Comments, type Provides access to MDT 2008 software during Configuration Manager deployment process, and then click Next.
    OS Image Click Create a new OS install package.
    In OS installation folder location, type \\Home-SCCM\Source$\Windows_XPSP3.
    In Package source folder to be created, type \\Home-SCCM\Packages$\Windows_XPSP3, and then click Next.
    OS Image: Image Details In Name, type Windows XP SP3.
    In Version, type 1.00.
    In Comments, type Windows XP SP3 package used to deploy to reference computers, and then click Next.
    Client Package Click Create a new ConfigMgr client package, and then click Next.
    USMT Package Click Create a new USMT package.
    In Path to USMT executables and related files, type \\Home-SCCM\Source$\USMT301.
    In Package source folder to be created, type \\Home-SCCM\Packages$\USMT301, and then click Next.
    USMT Package: USMT Details In Name, type USMT.
    In Version, type 3.0.1.
    In Comments, type USMT files used to capture and restore user state migration information, and then click Next.
    Settings Package Click Create a new settings package.
    In Package source folder to be created, type \\Home-SCCM\Packages$\CustomSettings_Reference, and then click Next.
    Settings Package: Settings Details In Name, type MDT 2008 Reference Computer Custom Settings.
    In Version, type 1.00.
    In Comments, type Configuration settings for MDT 2008 deployment process (such as CustomSettings.ini) for the reference computer, and then click Next.
    Sysprep Package Click Create a new Sysprep package.
    In Path to Sysprep executables and related files, type \\Home-SCCM\Source$\Sysprep_XPSP3.
    In Package source folder to be created, type \\Home-SCCM\Packages$\Sysprep_XPSP3, and then click Next.
    Sysprep Package: Sysprep Details In Name, type Windows XP SP3 Sysprep.
    In Version, type 1.00.
    In Comments, type Sysprep files needed to deploy Windows XP SP3, and then click Next.
    Summary Displays a status bar that shows the progress of the tasks defined in the wizard. The Import Microsoft Deployment Task Sequence Wizard closes when the task sequence is imported.
    This process can take several minutes to finish.

Customize MDT 2008 configuration files

When the MDT 2008 task sequence has been imported, customize the MDT 2008 configuration files that provide the configuration settings for deploying Windows XP to the target computer. Specifically, customize the CustomSettings.ini file.

To customize the MDT 2008 configuration files for the reference computer:

1. In Windows Explorer, go to C:\Packages$\CustomSettings_Reference, and then double-click CustomSettings.ini.

2. In Notepad, add DoCapture=Yes to the end of the CustomSettings.ini file.

3. In Notepad, save the file, and then exit Notepad.

Customize the reference computer’s task sequence

By default, the task sequence sets the password for local Administrator account to a random value. At this step we will specify the password we want.

To customize the Windows Vista Reference Deployment task sequence:

  1. In the Configuration Manager console tree, go to Site Database/Computer Management/Operating System Deployment/Task Sequences.
  2. In the details pane, click Windows XP SP3 Reference Deployment.
  3. In the details pane, click Edit.
  4. In the Windows XP SP3 Reference Deployment Task Sequence Editor dialog box, go to PostInstall/Apply Windows Settings.
  5. On the Properties tab, click Enable the account and specify the local administrator password.
  6. On the Properties tab, in Password and Confirm Password, type P@ssw0rd, and then click Apply and OK.

Select distribution point for packages and image

The Import Microsoft Deployment Task Sequence Wizard created a number of packages and images. After these packages and images were modified as needed, we will select the distribution points from which the packages and images will be copied and available to target computers.

To select the distribution points for software distribution packages:

  1. In the Configuration Manager console tree, go to System Center Configuration Manager/Site Database/Computer Management/Software Distribution/Packages.
  2. In the details pane, click MDT 2008 Files.
  3. In the details pane, click Manage Distribution Points.
  4. The Manage Distribution Points Wizard starts.
  5. Complete the Manage Distribution Points Wizard by using the information in the table below. Accept default values unless otherwise specified.
    On this wizard page Do this
    Welcome Click Next.
    Select Destination Distribution Point Click Next.
    Package In Distribution points, select HOME-SCCM, and then click Next.
    Completion Click Next.
    Wizard Completed Click Close.

Repeat steps 2–4 of this procedure, substituting each of the following packages for:

  • MDT 2008 Reference Computer Custom Settings
  • USMT
  • Windows XP SP3 Sysprep
  • Configuration Manager Client Upgrade

To select the distribution points for boot images:

  1. In the Configuration Manager console tree, go to System Center Configuration Manager/Site Database/Computer Management/ Operating System Deployment/Boot Images.
  2. In the details pane, click Windows PE Custom.
  3. In the details pane, click Manage Distribution Points.
  4. The Manage Distribution Points Wizard starts.
  5. Complete the Manage Distribution Points Wizard by using the information in the table below. Accept default values unless otherwise specified.
    On this wizard page Do this
    Welcome Click Next.
    Select Destination Distribution Point Click Next.
    Package In Distribution points, select HOME-SCCM, and then click Next.
    Completion Click Next.
    Wizard Completed Click Close.

To select the distribution points for operating system installation packages:

  1. In the Configuration Manager console tree, go to System Center Configuration Manager/Site Database/Computer Management/ Operating System Deployment/Operating System Install Packages.
  2. In the details pane, click Windows XP SP3.
  3. In the details pane, click Manage Distribution Points.
  4. The Manage Distribution Points Wizard starts.
  5. Complete the Manage Distribution Points Wizard by using the information in the table below. Accept default values unless otherwise specified.
    On this wizard page Do this
    Welcome Click Next.
    Select Destination Distribution Point Click Next.
    Package In Distribution points, select HOME-SCCM, and then click Next.
    Completion Click Next.
    Wizard Completed Click Close.

Deploy Windows XP SP3 and capture an image of the reference computer

Create task sequence bootable media

A method must be provided for starting the computer with Windows PE and the necessary software to initiate the MDT 2008 process. At this step we’ll create the task sequence bootable media by using the Task Sequence Media Wizard and will use the .iso file to boot a new virtual machine with no operating system installed, just a new unformatted virtual hard disk.

To create task sequence bootable media:

  1. Click Start, point to All Programs, and then point to Microsoft System Center. Point to Configuration Manager 2007, and then click ConfigMgr Console.
  2. In the Configuration Manager console tree, go to System Center Configuration Manager/Site Database/Computer Management/Operating System Deployment/Task Sequences.
  3. In the details pane, click Create Task Sequence Media.
  4. The Task Sequence Media Wizard starts.
  5. Complete the Task Sequence Media Wizard by using the information in the table below. Accept the default values unless otherwise specified.
    On this wizard page Do this
    Select Media Type Click Bootable media, and then click Next.
    Media type In Media file, type \\Home-SCCM\Captures$\ConfigMgr2007_TS_Boot_Media.iso, and then click Next.
    Security In Password and Confirm password, type P@ssw0rd, and then click Next.
    Boot image In Boot image, click Browse.
    In the Select a Boot Image dialog box, click Windows PE Custom, and then click OK.
    Click Next.
    Summary Click Next.
    Confirmation Click Close.

The wizard creates the “ConfigMgr2007_TS_Boot_Media.iso” file in the \\Home-SCCM\Captures$ shared folder.

Create an advertisement for the reference computer task sequence

As I want to deploy Windows XP SP3 to bare-metal machines (which ConfigMgr doesn’t know about), I have to create an advertisement for All Unknown Computers collection.

To create an advertisement for the task sequence:

  1. In the Configuration Manager console tree, go to System Center Configuration Manager/Site Database/Computer Management/Operating System Deployment/Task Sequences.
  2. In the details pane, click Windows XP SP3 Reference Deployment.
  3. In the details pane, click Advertise.
  4. The New Advertisement Wizard starts.
  5. Complete the New Advertisement Wizard by using the information in table below. Accept the default values unless otherwise specified.
    On this wizard page Do this
    General In Comment, type Advertisement to deploy Windows Vista to the reference computer and then capture an image of the reference computer.
    In Collection, click Browse.
    In the Browse Collection dialog box, click All Unknown Computers, and then click OK.
    Select the Make this task sequence available to boot media and PXE check box.
    Click Next.
    Schedule Click Next.
    Distribution Points Click Next.
    Interaction Click Next.
    Security Click Next.
    Summary Click Next.
    Confirmation Click Close.

As “Home-XPSP3-Ref01” is a virtual machine, at this point I will start it and boot from the created ISO file.

On the Welcome to the Task Sequence Wizard page, in the Password field type P@ssw0rd and press Next. You will see that there is only one assignment: Windows XP SP3 Reference Deployment. Select it and click Next to start the operating system deployment.


The last task sequence action will capture an image of the reference computer.


If any problems occur during the deployment, consult the MDT 2008 documentation or learn how to troubleshoot task sequence issues in Configuration Manager.

In the next post I will use the captured image to create a task sequence for target machines.

All .mp3 files on Desktop and My Documents folder

Want to know if your users store mp3 files on Desktop or My Documents folders?

  1. Add .mp3 file type to Software Inventory Client Agent properties
      1. Navigate to Site DatabaseSite ManagementSite NameSite SettingsClient Agents and double click Software Inventory Client Agent
      2. Select Inventory Collection tab
      3. Click the new button and type *.mp3 as a file name.
    1. Set the location: All client hard disks or Variable or path name
    2. Click OK to close all open windows
  2. Wait for Software Inventory to run and collect data
  3. Create a report using the following query: SELECT TOP (100) PERCENT SYS.Netbios_Name0, SF.FileName, SF.FileSize / 1024 AS [Size, KB], SF.FilePath FROM dbo.v_GS_SoftwareFile AS SF INNER JOIN dbo.v_R_System AS SYS ON SYS.ResourceID = SF.ResourceID WHERE (SF.FileName LIKE '%mp3') AND (SF.FilePath LIKE '%My Documents%') OR (SF.FileName LIKE '%mp3') AND (SF.FilePath LIKE '%Desktop%') ORDER BY SYS.Netbios_Name0

Deploy Office 2007 with custom Quick Access Toolbar commands

Receiving some complaints that users can’t find the Open, New etc. commands in the new Office 2007 interface, I had a task to customize Quick Access Toolbar so that all users can have these commands installed by default.

Office 2007 applications (Access, Excel, PowerPoint, Outlook, Word) use a Quick Access Toolbar setting file (.qat). Every application has its own .qat file (Access.qat, Excel,qat, Outlook.qat, PowerPoint.qat and Word.qat). In order to customize and deploy these files using Office Customization Tool, we must add a registry entry to enable roaming user profiles to access the .qat file during deployment. This is because, by default, qat files are not saved in a roaming location.

I did this using the OCT:

  1. Open or create a new setup customization file (.msp) for Microsoft Office 2007.
  2. Under Additional content, select Add registry entries and click Add.
  3. Select HKEY_CURRENT_USER in the “Root” select box.
  4. Select REG_DWORD in the “Data type” select box.
  5. Enter Software\Microsoft\Office\12.0\Common\Toolbars in the “Key” input box.
  6. Enter QuickAccessToolbarRoaming as a “Value name”.
  7. Enter 1 as a “Value data”.
    Add/Modify Registry Entry
  8. Click OK.

After this, the default folder for .qat files will be: %APPDATA%\Microsoft\Office.

Now log in to any computer that has this modification and customize the Quick Access Toolbar for every Office 2007 application as you want. When you’re done, navigate to “%appdata%\Microsoft\Office” folder and copy all .qat files from there to a USB media for example.

QAT files

Now you have two methods of distributing these files: copy these files to all computers manually/using a script or use OCT. It depends on your needs… I will use OCT to have these files copied during the installation of Office 2007.

To do this, open the same office customization file (.msp) as earlier and do the following modifications:

  1. Under Additional content, select Add files and click Add.
  2. In the Add Files to MSP File dialog box, open the folder that contains your *.qat files, select the Excel.qat file (for example) and then click Add.
  3. In the File Destination Path dialog box, select the path [AppDataFolder]\Microsoft\Office for the “Destination path on the user’s computer”.
    File Destination Path
  4. Click OK.

Next time when you will install Office 2007, Quick Access Toolbar in every application will have the commands you set. In my case, Excel’s Quick Access Toolbar looks like this:

Quick Access Toolbar commands

Install drivers by computer model using WMI query

When using task sequence, you might want to install different driver packages for different computer models. This can be accomplished by using a WMI query.

First of all you need to have driver packages for all your computer models and know the exact model name for every computer.

To find this, open a command prompt and type WMIC ComputerSystem GET Model (use this command on every computer to find its model).

Then, Edit your task sequence. Add how many steps you need with “Apply Driver Package”. Select the driver package you have created for a certain computer model (HP dc5700 in my case).

Apply Driver Package

In the Options tab, click Add Condition and select Query WMI. In the WMI Query Properties window, make you sure you have root\cimv2 as WMI Namespace and write the following query in the WMI Query input box:

SELECT * FROM Win32_ComputerSystem WHERE Model LIKE “%dc5700%” for HP Compaq dc5700 computer models.

WMI Query

Now, for every driver package, replace the model name with the computer model name the driver package is for. This way, the task sequence will install the correct drivers on every computer that will match the model specified in the query and will skip other steps sending the following status message: “The task sequence execution engine skipped the action (HP Compaq dc5700) in the group (Apply driver packages) because the condition was evaluated to be false”.

Deploy ePolicy Orchestrator (ePO) agent

Having to create a package with McAfee ePO agent, I wanted to make it available to task sequence too so it can be installed during the operating system setup. For this, I had to make it install unattended or silent not requiring any user input. As I have never worked with McAfee, first, I did not understand what the purpose of this agent is. I couldn’t understand why you should install the agent and not the antivirus software itself? When I did, I started to think how to deploy it easily and with no user interaction.

So, to do this, simply put FramePkg.exe into a folder, say “ePO”, and create a package as you normally would. Then create a program that has the following command line FramePkg.exe /install = agent /silent.

If you want to install ePO as part of one task sequence, make sure the program can run whether or not a user is logged on and do not allow users to interact with the program.

This way, after the computer is added to domain, it will connect to the server and will receive all necessary settings (for example install antivirus software, patches and latest definition updates).

Failed to Run Task Sequence – 0x80072EE7

If you receive the following error: “An error occurred while retrieving policy for this computer (0x80072EE7)” when Task Sequence Wizard starts, this can happen if you have DHCP or DNS problems.

You should check if you can contact the DHCP server in order to get an IP address or you can configure a static IP address.


If you have a switch with STP enabled, you might want to read this post.

Failed to Run Task Sequence

I just spent half an hour trying to understand why my task sequence cannot find the files on a distribution point; although the TS runs normally, I see all available TSs and I can choose the one I need. Then I found why: I missed something I never missed before and that must not be forgotten! I forgot to configure the network access account.

So, if you receive the following error: “This task sequence cannot be run because the program files for <your package here> are inaccessible on the distribution point.”, you should check if your network access account are configured and the information is correct.

To resolve this issue, you must correctly configure the System Center Configuration Manager 2007 client network access account. To do this, follow these steps:

  1. Use an account that has administrative permissions to log on to a computer that has the System Center Configuration Manager 2007 Administrator Console installed.
  2. Click Start, click All Programs, click Systems Management Server, and then click SMS Administrator Console.
  3. Expand ServerName, expand Site Management, expand SiteName, and then expand Site Settings.
  4. Click Client Agents, right-click Computer Client Agent, and then click Properties.
  5. In the Computer Client Agent Properties dialog box, next to the network access account that you want to configure, click Set.
  6. In the Windows User Account dialog box, enter the user name and the password that you want to use for the network access account, and then click OK two times.

Here is Microsoft’s article about this: http://support.microsoft.com/kb/935914

Create an advertisement only for Windows 7 systems

Let’s suppose you create a package with one program and want to advertise it only to a few selected platforms, including x86 and x64 Windows 7 systems. Because Windows 7 is not supported yet with Configuration Manager 2007 SP1, you cannot choose it from the supplied list of platforms. As a result of this, after receiving and downloading the package, the system will give you the following message:
Program rejected (wrong platform). Advertisement "XYZ12345" from site "XYZ" was rejected because the client's platform is not supported.

It is expected that SP2 will add support for Windows 7, but until then we can use the following workaround:

  1. Create a collection with all Windows 7 systems
    select sms_r_system.ResourceID, sms_r_system.ResourceType, sms_r_system.Name, sms_r_system.SMSUniqueIdentifier, sms_r_system.ResourceDomainORWorkgroup, sms_r_system.Client from sms_r_system where OperatingSystemNameandVersion like '%Workstation 6.1%'
  2. Create a new program (for example Program for Win7) for the same package and select “This program can run on any platform” as a requirement.
  3. Create a new advertisement and use “Program for Win7” program. Advertise it to Windows 7 collection created earlier.

That’s it. This may not be the best workaround, but it worked very well for me, at least until SP2 will RTM and I can install it in production.

Create a collection with all x64 systems

As I have some free time, I’m testing different things with SCCM, mainly in creating different collections that I might need. Bellow you can find the query that will show you all x64 systems, client and server operating systems.

select SMS_R_SYSTEM.ResourceID, SMS_R_SYSTEM.ResourceType, SMS_R_SYSTEM.Name, SMS_R_SYSTEM.SMSUniqueIdentifier, SMS_R_SYSTEM.ResourceDomainORWorkgroup, SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_G_System_COMPUTER_SYSTEM.SystemType = "x64-based PC"

You can further customize this so it will show you only x64 servers or only x64 Vista systems etc.

Failed to extend the Active Directory Schema

Usually, extending the Active Directory schema is the last step I do when installing SCCM. This time, while installing SCCM in a virtual machine, you have to provide a path to a folder with SCCM updates or download these updates from the internet. Working in a virtual machine with a “Local only” network adapter, I couldn’t download those updates; so I switch the network adapter to an external one. After downloading the updates, next step is “Installation Prerequisite Check” and at this step I extend the AD schema.

Well, the following error was written in ExtADSch.log file:
Unable to connect to RootDSE - Cannot update Active Directory. Error code = 1355.
Failed to extend the Active Directory Schema.

Error 1355 is: ERROR_NO_SUCH_DOMAIN. That means that the specified domain could not be contacted or does not exist. The problem here is that I did not switched back to “Local only” network adapter and so the Active Directory could not be contacted. Setting the adapter to “Local only”, I could contact the Domain Controller and extending the schema was successful.

What I learned? Always make sure you can reach your domain.