I've used this before in a vbscript. And then later use an if/then/else to do whatever you needed to do for 32 vs 64
'---Determine x64 or x86----------------
Set objWMIService = GetObject("winmgmts:\\.\root\CIMV2")
Set colItems = objWMIService.ExecQuery("SELECT * FROM Win32_Processor")
for each obj in colItems
select case obj.addresswidth
case 32
strbit="32"
case 64
strbit="64"
end select
next
Sherry Kissinger
Microsoft MVP - ConfigMgr
mofmaster@myitforum.com
--- On Mon, 1/4/10, Andrew.Berges@everestre.com <Andrew.Berges@everestre.com> wrote:
From: Andrew.Berges@everestre.com <Andrew.Berges@everestre.com>
Subject: [mssms] SCCM Healthcheck Startup Script 1.7 for SP2 - Issues with 64-bit Architecture?
To: mssms@lists.myitforum.com
Date: Monday, January 4, 2010, 10:21 AM
Just noticed something with Chris's script… I don't think that this script will perform properly on 64-bit clients. At least, I'm not observing that. I think this is why:
At line 115 when strKeyPath is getting populated with the registry key location for ConfigMgr Client Properties, it's referring to it as "SOFTWARE\Microsoft\SMS\Client\Configuration\Client Properties", which is correct on a 32-bit system.
However, on a 64-bit system, this key will not exist as it will be located under "SOFTWARE\Wow6432Node\Microsoft\SMS\Client\Configuration\Client Properties" instead.
As a result, when the system health checks are run (specifically line 172), the StrSCCMPath string will always be blank resulting in a client install being triggered. Additionally, the logfile for the health check will be created as C:\ConfigMgr.log rather than in the client's log directory due to this blank string.
I'm not much of a vbscript guy but it seems like it should be fairly easy to check 32 vs. 64 bit architecture and change the strKeyPath appropriately depending on the OS architecture. Anyone willing to assist me in editing this code to accommodate for 64 bit platforms?
Thanks in advance,
Andrew
This e-mail is intended only for the person or entity to whom it is addressed and may contain information that is privileged, confidential, or otherwise protected from disclosure. If you are not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of this message is prohibited. If you have received this e-mail in error, please contact the sender immediately and delete the original message and all copies from your system. Statements and representations made in this message are not necessarily that of the Company.
==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/smslist/
|
