ConfigMgr vNext: It just gets easier and easier.

Its about time that I write my first post about ConfigMgr vNext BETA and well I really have to say that it just gets easier and easier compared to ConfigMgr 2007. The only thing I have to get used to is that everything is in a different location.

Capture User Files and Setting Offline (WinPE) with Hard-Links

HardLinkOnOffvNextAs I have been busy a lot with capturing user files offline on my blog, lets start about how easy that becomes in ConfigMgr vNext. I still remember making BAT-files to run the ScanState –commands, in ConfigMgr vNext its just selecting the checkboxes Capture locally using links instead of copying files and Capture in off-line mode (WinPE only). After this the Capture User Files and Settings –step will run with the command C:\_SMSTaskSequence\Packages\P010000A\amd64\scanstate.exe C:\_SMSTaskSequence\UserState /o /localonly /efs:skip /all /v:5
/offlineWinDir:C:\WINDOWS /c /hardlink
/nocompress /l:X:\WINDOWS\TEMP\SMSTSLog\scanstate.log
/progress:X:\WINDOWS\TEMP\SMSTSLog\scanstateprogress.log
/i:C:\_SMSTaskSequence\Packages\P010000A\amd64\miguser.xml /i:C:\_SMSTaskSequence\Packages\P010000A\amd64\migapp.xml.

Even the variable OSDStateStorePath gets set to %_SMSTSUserStatePath% automatically by selecting Save user settings locally during the Create Task Seqeunce Wizard.

Schedule Updates on a Operating System Image

ImageProp Another cowl feature I ran into, with creating the Operating System Image for the Task Sequence, is the option to Schedule Updates for an already created Operating System Image. By doing this ConfigMgr will insert the selected updates into the Operating System Image. No more problems with installing Software Updates during the Build and Capture –proces, can it get easier then this?

After this it is also possible to see the which Software Updates exist in the Operating System Image (see picture). Now you will always be able to see how up-to-date your reference image is!

Of course there are lots and lots of more cowl feature, like the Software Center, the Online Software Catalog, the Automatic Grouping Rules for Software Updates, the Client Agent Settings, etc, etc, etc… But, at my defence, these are all to big to be covered in one post.

Configuration Manager 2007 R3 Release Candidate has been released!

I would like to make a short note of the following announcement on the ConfigMgr Connect Site (https://connect.microsoft.com/site16)

System Center Configuration Manager 2007 R3 Release Candidate (RC) has been released!

As a member of the Configuration Manager 2007 R3 Open Beta program you can download at this Connection via the downloads tab.

Feedback can be provided using the Feedback tool and also available is discussions via the Newsgroups where you can post comments and ask questions.

Thank you.

ConfigMgr Customer team

How to sequence the ConfigMgr 2007 Admin Console

Well… this has been asked (and handled) before and by different people, but always with using registry keys and dependency’s. I noticed that it is much easier to do this by just following the Best practices for sequencing in Microsoft Softgrid. So to create the sequence of the ConfigMgr Admin Console, follow these steps:

Prepare the Sequence machine

  1. Create a sequencing machine which represents a standard machine in your company.
  2. Make sure to exit any antivirus software and stop the Windows Update service.
  3. Make sure the machine has at least two partitions and configure the second partition as Q
  4. Create an empty folder on drive Q, with an 8.3 directory name (something like CFGMGR07.v01).
  5. (Optional) Install the prerequisites for the ConfigMgr 2007 Admin Console (like MMC 3.0).
  6. Install the App-V 4.6 Sequencer.

Sequence the ConfigMgr 2007 Admin Console

  1. Start the App-V 4.6 Sequencer via Start > Programs > Microsoft Application Virtualization > Microsoft Application Virtualization Sequencer.
  2. Select Create a Package and the Sequencing Wizard will start.
  3. In the Package Information page give a Package Name, (optional) some Comments and click Next.
  4. In the Monitor Installation page click Begin Monitoring.
  5. In the Browse For Folder pop-up browse to the folder which was created in step #4 of Prepare the Sequence machine and click Ok.
  6. When the Monitor Installation page shows Install the application, and then click Stop Monitoring start the installation of the ConfigMgr 2007 Admin Console to (a sub location of) the location created in step #4 of Prepare the Sequence machine.
  7. (Optional) Install the Microsoft Deployment Toolkit 2010 to (a sub location of) the location created in step #4 of Prepare the Sequence machine.
  8. (Optional) Launch the console(s) to test the functionality.
  9. (Optional) Configure ConfigMgr Integration via Start > Programs > Microsoft Deployment Toolkit > Configure ConfigMgr Integration.
  10. Click Stop Monitoring.
  11. When the Monitor Installation page shows Click Begin Monitoring when you are ready to install the application, then wait again click Next.
  12. (Optional) In the Configure Applications page, change the icon directory of the ConfigMgr Console to <Installation Directory>\AdminUI\bin\SmsSnapInResources.dll.
  13. In the Configure Applications page click Next.
  14. In the Launch Application page click Launch All and, when all applications are closed click Next.
  15. In the Sequence Package page click Finish.
  16. (Optional) On the tab Deployment add all the needed Operating Systems.
  17. Save the Sequence by clicking on the Diskette.
  18. (Important!) Modify the .osd file of the ConfigMgr Console (and if installed, also of the Deployment Workbench) to point to the local MMC.EXE by using following settings:
    PARAMETERS="%SFT_MNT%\<Installation Directory>\path to the .msc file"
    FILENAME="%CSIDL_SYSTEM%\MMC.EXE"
  19. After this save the .osd file(s) and publish the sequence. Enjoy the working virtual application(s)!

More information about the Best practices to use for sequencing in Microsoft SoftGrid: http://support.microsoft.com/kb/932137/nl

ConfigMgr 2007, Client Push Installation and (a) Firewall(s)

One of the most common problems with Client Push Installation is (are) the (Windows) Firewall(s). As I had some questions about this (again) lately, I will post here all the open ports/ firewall exceptions needed for a Client Push Installation.

Exceptions for the Windows Firewall

To be able to do a Client Push Installation you need the following exceptions in the Windows Firewall:

  • File and Printer Sharing
  • Windows Management Instrumentation (WMI)
  • TCP Port 80 (for HTTP from the client computer to a MP (Mixed Mode))
  • TCP Port 443 (for HTTPS from the client computer to a MP (Native Mode))

Specific ports for other Firewalls

To be able to do a Client Push Installation you need to open the following ports in the Firewall:

Description UDP TCP
SMB between the Site Server and client computer. 445
RPC endpoint mapper between the Site Server and the client computer. 135 135
RPC dynamic ports between the Site Server and the client computer. Dynamic*
HTTP from the client computer to a MP (Mixed Mode). 80
HTTPS from the client computer to a MP (Native Mode).   443

*The dynamic RPC ports are until Windows XP and Windows Server 2003 (R2) 1025-5000 and from Vista and Windows Server 2008 (and later) 49152-65535.

More information about the Windows Firewall Settings for ConfigMgr Clients:
http://technet.microsoft.com/en-us/library/bb694088.aspx
More information about the Ports used during ConfigMgr Client Deployment:
http://technet.microsoft.com/en-us/library/ff189805.aspx
More information about the Dynamic Port Ranges:
http://support.microsoft.com/kb/929851/nl

Capture User Files and Settings Offline (WinPE) or Online (FullOS) with ConfigMgr 2007

They always say never change a winning team, but sometimes its just cowl to see if its possible to be even better. I had the same with a previous post in which I already showed how to do a Hard-Link migration, when started from WinPE (and FullOS). The biggest part of that example is still the same, but some pieces changed to get a better result.

In this post I will go step-by-step (again) to mention the changes that I made to make it even better. At the end of both parts of this post I will shine a light on the changes that I made.

Part 1: Capture User Files and Settings

HardlinkOnOffTSFor creating a Task Sequence, that does an Online or Offline Capture, my way, a few variables and locations need to be created. After that a command line has to be run to do the actual Capture. Under here I will sum up the steps I take to do an Online and Offline Capture (also see the first red rectangle in the picture):

  • Set Started in WinPE – Set Task Sequence Variable
    This step sets the Task Sequence Variable TSStartedInWinPE to YES. This Task Sequence Variable only gets set when _SMSTSInWinPE is TRUE.
  • Set Architecture – Set Task Sequence Variable
    This step sets the Task Sequence Variable Architecture to amd64. This variable will be used for selecting the USMT 4.0 version for (in my case) 64-bit systems.
  • Set Windows Partition – Set Task Sequence Variable
    This step sets the Task Sequence Variable WindowsPartition to C:. This variable will be used for selecting the Windows partition.
  • Set State Store Location – Set Task Sequence Variable
    This step sets the Task Sequence Variable OSDStateStorePath to %WindowsPartition%\StateStore. This variable will be used for creating and selecting the User State Location.
  • Create State Store Location – Run Command Line
    This step creates the directory %WindowsPartition%\StateStore by running the Command line: cmd /c MKDIR %OSDStateStorePath%.
  • Cache USMT Files and Scripts – Run Command Line
    This step caches the USMT Files and Scripts from the USMT Package to the directory %OSDStateStorePath%\USMTFiles\ by running the Command line: xcopy * %OSDStateStorePath%\USMTFiles\ /herciy
  • Capture User Files and Settings – WinPE – Run Command Line
    This step does the actual Offline Capture of the User Files and Settings by running the Command line RunScanState_WinPE.BAT %OSDStateStorePath% %WindowsPartition% %Architecture% %_SMSTSLogPath% which has to start in the directory %OSDStateStorePath%\USMTFiles\. This step only runs when the machine is started from WinPE. This is done by checking if the Task Sequence Variable TSStartedInWinPE is set to YES.
  • Capture User Files and Settings – FullOS – Run Command Line
    This step does the actual Online Capture of the User Files and Settings by running the Command line RunScanState_FullOS.BAT %OSDStateStorePath% %WindowsPartition% %Architecture% %_SMSTSLogPath% which has to start in the directory %OSDStateStorePath%\USMTFiles\. This step only runs when the machine is started from FullOS. This is done by checking if the Task Sequence Variable TSStartedInWinPE is not set to YES. 

These are all the steps I need, to do an Online or Offline Capture with Hard-Links. Now let’s take a closer look at the batch-files which do the most of the work:

RunScanState_FullOS.BAT

REM ======================================================
REM ARGUMENT -1- OSDStateStorePath     = %1
REM ARGUMENT -2- WindowsPartition    = %2
REM ARGUMENT -3- Architecture        = %3
REM ARGUMENT -4- LogDirectory        = %4
REM ======================================================

SET USMT_WORKING_DIR=%1\USMTFiles\%3

REM ======================================================
REM RUN Scanstate
REM ======================================================

"%1\USMTFiles\%3\Scanstate.exe" "%1" /o /hardlink /nocompress /i:%1\USMTFiles\%3\MigUser.xml /i:%1\USMTFiles\%3\MigApp.xml /localonly /l:%4\ScanState.log /v:5 /progress:%4\ScanStateProgress.log /c /efs:hardlink

REM ======================================================
REM EXIT Errorlevel
REM ======================================================

EXIT /b %errorlevel%

RunScanState_WinPE.BAT

REM ======================================================
REM ARGUMENT -1- OSDStateStorePath     = %1
REM ARGUMENT -2- WindowsPartition    = %2
REM ARGUMENT -3- Architecture        = %3
REM ARGUMENT -4- LogDirectory        = %4
REM ======================================================

SET USMT_WORKING_DIR=%1\USMTFiles\%3

REM ======================================================
REM RUN Scanstate
REM ======================================================

"%1\USMTFiles\%3\Scanstate.exe" "%1" /o /hardlink /nocompress /i:%1\USMTFiles\%3\MigUser.xml /i:%1\USMTFiles\%3\MigApp.xml /offlinewindir:%2\Windows /localonly /l:%4\Scanstate.log /v:5 /progress:%4\Scanstateprogress.log /c /efs:hardlink

REM ======================================================
REM EXIT Errorlevel
REM ======================================================

EXIT /b %errorlevel%

The changes that I made in Part 1: Capture User Files and Settings are the following two:

  1. I use now a batch-file for both, and Online and Offline Capture.
    Why? Just because it gives me more flexibility and because I can get rid of a few “double” steps. For example, now I can use the same Store Location (variable) for both Captures Types.
  2. I use now a different location for the logfiles.
    Why? Just because it gives me an easy possibility to save the log until the end of the Task Sequence.

Part 2: Restore User Files and Settings

After the User Files and Settings have been captured, they need to be restored again to the new OS. This is the same for an Online and Offline Capture. Under here I will sum up the steps that I use to restore the Files and Settings:

  • Restore User Files and Settings – Run Command Line
    This step does the actual Restore of the User Files and Settings by running the Command line RunLoadState.BAT %OSDStateStorePath% %WindowsPartition% %Architecture% %_SMSTSLogPath% which has to start in the directory %OSDStateStorePath%\USMTFiles\..
  • Cleanup State Store Location – Run Command Line 
    This step cleans up the State Store Location by running the command line RunUSMTutils.BAT %OSDStateStorePath% %Architecture%
  • Restart in FullOS – Restart Computer (see the second red rectangle in the picture)
    This step will restart the computer, but only when _SMSTSLastActionRetCode is equal to 2.

These are all the steps I need, to do a Restore with Hard-Links. Now let’s take a look at the batch-files which do most of the work here:

RunLoadState.BAT

REM ======================================================
REM ARGUMENT -1- OSDStateStorePath     = %1
REM ARGUMENT -2- WindowsPartition    = %2
REM ARGUMENT -3- Architecture        = %3
REM ARGUMENT -4- LogDirectory        = %4
REM ======================================================

SET USMT_WORKING_DIR=%1\USMTFiles\%3

REM ======================================================
REM RUN LoadState
REM ======================================================

"%1\USMTFiles\%3\Loadstate.exe" "%1" /hardlink /nocompress /lac /i:%1\USMTFiles\%3\MigUser.xml /i:%1\USMTFiles\%3\MigApp.xml /l:%4\LoadState.log /v:5 /progress:%4\LoadStateProgress.log /c

REM ======================================================
REM EXIT Errorlevel
REM ======================================================

EXIT /b %errorlevel%

RunUSMTutils.BAT

REM ====================================================== 
REM VARIABLE -1- OSDStateStorePath = %1
REM VARIABLE -2- Architecture = %2
REM ======================================================

REM ======================================================
REM RUN USMTUtils
REM ======================================================

echo y| "%~dp0%2\usmtutils.exe" /rd "%1"

REM ======================================================
REM EXIT Errorlevel
REM ======================================================

EXIT /b %errorlevel%

The changes that I made in Part 2: Restore User Files and Settings are the following two:

  1. I use now also batch-file for the Restore.
    Why? Just because it gives me more flexibility and because I can get rid of a “double” step (setting the Hardlink options).
  2. I use now an optional restart of the computer.
    Why? Because I noticed that sometimes USMTUtils ends with code 2, which means that it needs a restart to get rid of the last files.

Note: The RunScanState_FullOS.BAT, RunScanState_WinPE.BAT, RunLoadState.BATand the RunUSMTutils.BAT have to be placed inside the USMT Package at the same level as the amd64- and the x86-folder.

More information about the Scanstate Syntax:
http://technet.microsoft.com/en-us/library/dd560781(WS.10).aspx
More information about the LoadState Syntax:
http://technet.microsoft.com/en-us/library/dd560804(WS.10).aspx
More information about the USMTUtils Syntax: http://technet.microsoft.com/en-us/library/dd560799(WS.10).aspx

How to install a ConfigMgr Client on a WORKGROUP computer, when the ConfigMgr Site is in Native Mode.

NativeModeWorkgroup To install a ConfigMgr Client on a WORKGROUP computer is always a nice battle, when the ConfigMgr Site is in Native Mode. I think I am not the only one who didn’t work that much with certificates before ConfigMgr. So to make the basics of this process for everyone a bit easier I wrote down these seven steps for implementing the correct certificates and installing the ConfigMgr Client on a WORKGROUP client. These same steps can also be used for separate forests.

Step 1. Export the Root Certificate for use on the WORKGROUP computer

  1. Logon to the Certification Authority server and create a folder to contain your certificate files (eg C:\Certificates).
  2. Open a command prompt and go to the just created folder.
  3. Use the following command to export the Root Certificate: certutil -ca.cert RootCertificate.cer

 

Step 2. Create a Certificate Template for the WORKGROUP computer

  1. Open the Certification Authority Console, right-click Certificate Templates, and click Manage to load the Certificates Templates console.
  2. Select Windows Server 2003 Enterprise and click Ok.
  3. Right-click the Workstation Authentication template and click Duplicate Template.
  4. In the Properties of New Template dialog box, type the name for Template display name. As my normal Client Certificate Template is named ConfigMgr Client Certificate, I will name this one ConfigMgr Client Certificate for Export.
  5. Click the Request Handling tab and select Allow private key to be exported.
  6. Click the Subject Name tab, select Supply in the request.  This allows you to supply each FQDN of the client in the separate WORKGROUP at the time you request the certificate.
  7. Click OK to close the Properties of New Template and close the Certificates Template Console.
  8. In the Certification Authority Console, right-click Certificate Templates, click New, click Certificate Template to Issue, select the certificate template name you just created (eg ConfigMgr Client Certificate for Export), and then click OK.

 

Step 3. Request and Install the Client Certificate for the WORKGROUP computer

  1. Open a text editor and copy and paste the following text into the file (replace< FQDN> with the fully qualified domain name of the server that has to use this certificate):

    [NewRequest]
    Subject = "CN=<FQDN>"
    MachineKeySet = True
    Exportable = TRUE
    KeyLength = 2048
    [RequestAttributes]
    CertificateTemplate = ConfigMgrClientCertificateforExport

  2. Save the file as ConfigMgrClientCertificate.inf in the folder created in Step 1.
  3. Open a command prompt and go to the same folder as the saved file.
  4. Use the following command to create a certificate request: certreq –new ConfigMgrClientCertificate.inf ConfigMgrClientCertificate.req
  5. Use the following command to submit the certificate request: certreq –submit ConfigMgrClientCertificate.req ConfigMgrClientCertificate.cer
  6. In the Select Certification Authority dialog box, select the CA, and then click OK.
  7. Use the following command to accept the requested certificate: certreq –accept ConfigMgrClientCertificate.cer

 

Step 4. Export the Client Certificate for the WORKGROUP computer

  1. Open the Certificates Console for the local computer, right-click the certificate that is issued to <FQDN>, click All Tasks, and then click Export to launch the Certificate Export Wizard.
  2. On the Welcome page, click Next.
  3. On the Export Private Key page select Yes, export the private key and click Next.
  4. On the Export File Format page confirm that Personal Information Exchange – PKCS #12 (.PFX) is selected and click Next.
  5. On the Password page specify a password and click Next.
  6. On the File to Export page specify the path and name of the file and click Next.
  7. On the Summary page click Finish and click OK to close the confirmation popup.

 

Step 5. Import the Root Certificate in the WORKGROUP computer

  1. On the computer in the WORKGROUP, open the Certificates Console for the local computer and navigate to Trusted Root Certification Authorities\Certificates.
  2. Right-click Certificates select All Tasks and click Import to load the Certificate Import Wizard.
  3. On the Welcome page click Next.
  4. On the File to Import page click Browse and select the root certificate file that you created. After that click Open and then click Next.
  5. On the Certificate Store page click Next.
  6. Click Finish to close the wizard and click OK to close the confirmation popup.

 

Step 6. Import the Client Certificate in the WORKGROUP computer

  1. Open the Certificates Console for the local computer and this time navigate to Personal\Certificates.
  2. Right-click Certificates select All Tasks and click Import to load the Certificate Import Wizard.
  3. On the Welcome page click Next.
  4. On the File to Import page click Browse and select the exported certificate file that you created. Next click Open and then click Next.
  5. On the Password page type the password that you specified earlier and then click Next.
  6. On the Certificate Store page click Next.
  7. Click Finish to close the wizard and click OK to close the confirmation popup.

 

To confirm that the certificates got imported well, navigate to Personal\Certificates and select the certificate that is issued to <FQDN>. Double-click the certificate and click the Certificate Path tab, this checks that the certificate successfully chains to the issuing root CA certificate.  You should see the certificate and the root CA certificate, with the Certificate status displaying This certificate is OK.  Click OK to close the certificate properties.

Step 7. Install the ConfigMgr Client on the WORKGROUP computer

  1. Open a command prompt and go to the location of the ccmsetup.exe.
  2. Use the following, or similar, command to install the ConfigMgr Client: ccmsetup.exe  /Native:FALLBACK SMSSITECODE=<SiteCode> SMSSLP=<SLP>

 

Reminder: Don’t forget to add a Boundary to your ConfigMgr Site that includes the WORKGROUP computer.

User Driven Installation with ConfigMgr 2007 and MDT 2010 Update 1

UDI_WizardA few months ago I wrote a post about User Driven OS Deployment "Modena". By then it wasn’t sure if it was going to be released to the big public. Well I can tell now (after finally looking around in the the MDT 2010 Update 1 Beta) that it is going to be released, as it is a part of the MDT 2010 Update 1 (Beta).

Of course the scripts are now made to fit with the other MDT scripts, but the look-and-feel is the same (see picture).

This means that there is now an easy way coming for everyone to get their users “involved” in an OS Deployment. The only requirements are to have ConfigMgr 2007 and MDT 2010 Update 1 (Beta) installed and to have the ConfigMgr Integration configured.

How to create a User Driven Installation Task SequenceUDI_TaskSequence

  1. Open the Configuration Manager console and browse to System Center Configuration Manager > Site Database > Computer Management > Operating System Deployement > Task Sequences.
  2. Select Create Microsoft Deployment Task Sequence in the Actions pane.
  3. Select User Driven Installation Task Sequence and click Next (see picture). After this run, through the wizard an its done!

 

To keep a short story short, take a look at Microsoft Connect to get MDT 2010 Update 1 (Beta): 
>> https://connect.microsoft.com/site14 <<

The first Beta of ConfigMgr vNext has been released!

Although there is still a ConfigMgr 2007 R3 in the making, the first beta of ConfigMgr vNext has already been released.

Take a look at the System Center Team Blog for more inside information: http://blogs.technet.com/b/systemcenter/archive/2010/05/24/the-next-generation-of-client-management.aspx
Take a look at Microsoft Connect for the download: https://connect.microsoft.com/ConfigurationManagervnext/Downloads

ConfigMgr 2007 R3 is making a step in Green IT with Power Management

This post is not meant as a guide for installing or configuring the R3 feature pack and/ or Power Management. I will just show, in a few screenshots and a bit explanation, what the possibilities are regarding the Power Management feature in ConfigMgr 2007 R3.

PwrMngmntAgentAs we all already knew, one of the coolest new features of ConfigMgr 2007 R3 would be Power Management. Another step in the direction of Green IT.  The Power Management feature provides a new Client Agent which enables you to apply power settings to client computers in the organization and monitor the power usage of these computers.

How to Enable the Power Management Client Agent

  1. Open the Configuration Manager console and browse to System Center Configuration Manager > Site Database > Site Management > <YourSiteName> > Site Settings > Client Agents.
  2. Select the Power Management Client Agent and click in the Actions pane Properties (or right-click the Power Management Client Agent and click Properties) to open the Power Management Client Agent Properties.
  3. Select Enable power management on clients and click Ok.

After a policy refresh the Power Management Client Agent will be enabled on the client.

How to Enable Power Management settings PwrMngmntSettings

  1. Open the Configuration Manager console and browse to System Center Configuration Manager > Site Database > Computer Management > Collections.
  2. Select <YourCollectionName>, click in the Actions pane Modify Collection Settings (or right-click <YourCollectionName> and click Modify Collection Settings) and select the Power Management tab to open the Power Management Settings.
  3. Select Enable power management settings, specify the power management settings (like different power plans and wake up time) and click Ok.

Now you have this possibility to enable Power Management settings on a per collection base. These settings work in a same way as setting Maintenance Windows on a per collection base.

How to view the Power Settings/ Capabilities/ Costs and Consumption

During the installation of R3 a new cab-file (MicrosoftReportPack) will be placed in <ConfigMgrInstallationDir>\Reports\Power Management.  PwrMngmntReportsWithout importing this cab-file you will not be able to see the Power Management reports, so don’t forget to import these handy reports! 

  1. Open the Configuration Manager console and browse to System Center Configuration Manager > Site Database > Computer Management > Reporting Services > <ServerName> > Report Folders.
  2. Select Power Management.
  3. Select the report that your want and click in the Actions pane Run (or right-click the report that want and click Run).

In these reports you can see all the information about Power Management, from capabilities till costs and from settings till consumptions.

ConfigMgr 2007 and editing the registry during a Task Sequence on a 64-bit OS

Disable64bitTSOf course you know, deep down, that the ConfigMgr 2007 Client is 32-bit and that it will react a bit different on a 64-bit OS. The reason for this is of course the emulation layer, also know as Windows 32-bit On Windows 64-bit (WOW64), that enables a 32-bit application to run seamlessly on a 64-bit OS. 

As the ConfigMgr 2007 (RTM, SP1, SP2) Client is only available in a 32-bit version, you may run into some bumps on a 64-bit Operation System. One of these bumps is editing a registry key in HKEY_LOCAL_MACHINE\Software, because, for the ConfigMgr 2007 Client, this will get redirected to HKEY_LOCAL_MACHINE\Software\WOW6432Node.

Luckily there is an easy solution for this in a Task Sequence of ConfigMgr 2007. Just create a Task Sequence, add a Run Command Line –step and select Disable 64-bit file system redirection. This will makes sure that the use of the WOW64 file redirector will be disabled. 

Example UserName_on_ComputerName
An often used registry edit is to rename the Computer (on XP this is My Computer) to “Username on Computername”. To do this you need to edit the  HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{20D04FE0-3AEA-1069-A2D8-08002B30309D}\LocalizedString –key. Without disabling the 64-bit file system redirection, the ConfigMgr 2007 Client will only change the key under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\CLSID\{20D04FE0-3AEA-1069-A2D8-08002B30309D}\LocalizedString. This will not make the change show in the menu or the explorer.

More information about the Run Command Line –step: http://technet.microsoft.com/en-us/library/bb632992.aspx
More information about WOW64, Registry (and File System) Redirection and Reflection: http://www.microsoft.com/whdc/system/platform/64bit/WoW64_bestprac.mspx