Okay here is what I found is happening:

The machines we found having this issue are Dell Laptops with ATI card.

What happened is that there was some update either from Microsoft or Dell for 
the ATI card (still trying to find that, but whatever that was, came out within 
two days) and this created the
Registry entry under \HKEY_LOCAL_MACHINE\Software\Wow6432Node\ATI Technologies

Now, Clean Access being very 'smart' has a check called pc_XP32/pc_XP64 looking 
for the existence of this directory
Wow6432Node to declare if it's a 32bit or 64bit machine. Hence, now when it 
sees this directory now exist in there, it thinks it is a 64bit machine and 
hence fails the machine for other checks too.

Here is the fix:

1. Change the directory \HKEY_LOCAL_MACHINE\Software\Wow6432Node\ to something 
else like \HKEY_LOCAL_MACHINE\Software\6432WowNode\ or other name and it will 
go through

2. We request Cisco to please come up with some other way to discriminate a 
machine for 32/64 and modify the check pc_XP32 and pc_XP64

Hope that helps.

Thanks
Muhammad/.


Muhammad I. Ismail
Network Security Specialist
Western CT State University
(203) 837-8991 (O)
[EMAIL PROTECTED]



-----Original Message-----
From: Cisco Clean Access Users and Administrators [mailto:[EMAIL PROTECTED] On 
Behalf Of Muhammad Ismail
Sent: Thursday, November 13, 2008 12:49 PM
To: [email protected]
Subject: Re: Wow6432Node on 32-bit XPSP3?

We have couple of machines one Windows XP Pro/Home and one Windows XP Media 
Center Edition. It appears that some update that came out recently is breaking 
machines.

Anyone has any fixes, please share.

Thanks
Muhammad/.


Muhammad I. Ismail
Network Security Specialist
Western CT State University
(203) 837-8991 (O)
[EMAIL PROTECTED]



-----Original Message-----
From: Cisco Clean Access Users and Administrators [mailto:[EMAIL PROTECTED] On 
Behalf Of Terry Mitchell
Sent: Wednesday, November 12, 2008 2:50 PM
To: [email protected]
Subject: Wow6432Node on 32-bit XPSP3?

Wondering if anybody else is seeing this starting today (CAM 4.1.3.1/various
agent versions):

A number of XPSP3 machines are reporting failures on check pc_XP32 which
appears to use this key \HKEY_LOCAL_MACHINE\Software\Wow6432Node\ to
identify a 32-bit/64-bit OS. If it does not exist, then machine should be
32-bit. Unfortunately some 32-bit systems appear to include the
HKLM/Software/Wow6432Node reg. key for some reason.

Adding the key to a XPSP3 machine that didn't previously have the key
results in failure to pass through mandatory policies for XP updates (see
below), reflecting the issue/error log entries we're seeing in user machines.

Anyone else seeing this issue?

Thanks.

Terry


Failure (Wow6432node present):

XP_Post_SPX_Patches (Mandatory)

    * Passed Checks:
    * Failed Checks:
      pc_XP32, Registry Check [\HKEY_LOCAL_MACHINE\Software\Wow6432Node\
does not exist ]
      pc_Windows-XP-SP2, Registry Check
[\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\CSDVersion
contains Service Pack 2]
      pc_Windows-XP-SP2-int, Registry Check
[\HKEY_LOCAL_MACHINE\system\CurrentControlSet\control\windows\CSDVersion
equals 512]
    * Not executed Checks:

Success (no Wow6432node):

XP_Post_SPX_Patches (Mandatory)

    * Passed Checks:
      pc_XP32
      pc_IE7_0
      pc_KB951698_MS08-033_XP
      pc_KB954593_MS08-052_XP
      pc_Windows-XP-SP3
      pc_KB958644_MS08-067_XP_SP3
      pc_Flash_6_0_79
      pc_MSXML3_MS08-069_XP
      pc_KB952954_MS08-046_XP_SP3
    * Failed Checks:

Reply via email to