Friday, March 5, 2010

Problem with deploying REG file with SCCM 2007 R2 to 64-bit Windows Server 2008

Registry modification REG file by SCCM 2007 R2 can deploy with this command:

regedit.exe /s MyRegFile.reg

where /s is used to suppress the confirmation dialog

BAT file, including this command, is created and it works on the way how we want.

Ex: If we execute this BAT manually, MyRegFile.reg creates all nesseccery REG folders and sub keys under:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags]

When this BAT is pushed by SCCM 2007 R2 on Windows Server 2008 or Windows 7 64-BIT MACHINES it creates folders and keys under:

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\AppCompatFlags]

I'm not sure why it does working on this way, but the alternative to avoid this issue is to deploy this BAT file with GPO.

All REG folders and files are created under:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags]


  1. This is the exact issue I am facing right now. I am trying to deploy reg edits to Windows 7 x64. Based on my research, this is happening because the SCCM client is a 32 bit application. So, it is automatically being redirected to the Wow64 node. GPO will process the 64 bit regedit.exe to allow this work the way we want it to. My issue is that I don't have access to editing GPO. But, I do have access to deploy changes with SCCM. Making GPO changes in my company takes an act of Congress.

  2. Same issue here. Manual batch file executes imports the registry keys perfectly, but the same file fails when installed by SCCM. GPO's isn't an attractive option in my environment because of the way these clients are scattered across the OU's. We specifically bought SCCM to be able to use collections for this sort of thing.

  3. You could use a task sequence "Run Command Line" to run your BAT and tick the "Disable 64-bit file system redirection"

  4. %windir%\syswow64\cmd.exe /c %windir%\sysnative\reg.exe