Jump to content


Recommended Posts

Detection method is fine.  I ended up figuring it out yesterday evening then proceeded to drink both our shares of single malt. I intentionally changed the test to be non-compliant "not equal to" and discovered that the detection method looks at two places in the registry...  even if specifically pointing it to the registry path in this case:  HKLM:\Software\Microsoft\Windows\CurrentVersion\OEMInformation. The detection also looks at the 32bit side of the house: HKLM:Software\Wow6432Node\Microsoft\Windows\CurrentVersion\OEMInformation. Checked the box "This registry value is associate with a a 64-bit application" and all is right with the world.  Thanks to Jason Sandys's post  I also added %windir%\sysnative\WindowsPowerShell\v1.0\powershell.exe to my scripts in SCCM to make sure they always run at the architecture level of the OS.  Appreciate the help Garth.

2017-07-25_20-01-10.jpg

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.