SCCM Client 32bit Client Stopping Registry Keys In SYSWOW64 Context Only Using SYSNATIVE


I use SCCM, Operating System Deployment (OSD) and Microsoft Deployment Toolkit (MDT) 2010 update 1 to deploy Windows 7 SP1 (x64) and application installs during the build process.  The problem was a .vbs script which populates some auto-logon keys called via SCCM OSD during the application installation process was being hit with registry redirection, forcing any registry entries to go into
HKLM\Software\Wow6432Node\Microsoft\Windows NT\CurrentVersion\WinLogon
rather than HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon. Continue reading

SCCM OSD ‘No Boot Action for Device (x) found

I was receiving the above message ‘No Boot Action for Device(32123) found.’  on the PXE service point server, in smspxe.log.

The number (32123) is the resource ID of the computer object found at that SCCM site.  The device was in a collection which had an advertisement pointing to a OSD Task sequence with a valid boot image.  I realised that the message is a little misleading.  I deal with a number of boot images and this particular boot image specified in this advertised Operating System Task Sequence was not on the SMSPXE$ share (i.e. not on the distribution point). 

So things to look out for :

  • Make sure that the OSD task sequence boot images are on the distribution point
  • That the task sequence you are using have a valid boot image, easy to decommision a boot image without updating your OSD task sequence