AAA, NAC, Guest Access & BYOD

Domain machine check for windows 7 Pc's using Onguard fails with error :domain registry check failed

Aruba Employee
Problem:

Receive an error in the dashbord logs as shown below: 
Output Posture Attributes -
RegistryKeys:HealthStatus = Not Healthy

Output Posture Evaluation Results -
Posture:WindowsUniversal:Registry Keys = UNHEALTHY
RegistryKeys:Mandatory:Missing = [Key=HKEY_CURRENT_USER\\\\Volatile Environment|Valname=USERDOMAIN|Type=1|Valdata=LOGICALIS|Remmsg=domain registry check failed]
 



Diagnostics:

RegistryKeys:Mandatory:Missing = [Key=HKEY_CURRENT_USER\\\\Volatile Environment|Valname=USERDOMAIN|Type=1|Valdata=LOGICALIS|Remmsg=domain registry check failed]

As per the above output, incorrect registry key: "Volatile Environment" was used in posture policy to do a domain check for windows 7 PC.

Possibility is that incorrect registry key for domain check was configured:
HKEY_CURRENT_USER\Volatile Environment\USERDOMAIN

 

On a windows 7 PC, execute the command "regedit". 
On executing the command, it will open the registry of the windows 7 PC
Doing a  search  in registry using the keyword: "Domain" and obtained one of  the below path: 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Domain.

 

Use the registry key:"Domain" to validate if windows 7 PC is part of domain. 

On doing a posture check, the dissolvable agent should now be able to detect the registry key and posture status will be"HEALTHY'.



Solution

On a windows 7 PC, execute the command "regedit". 
On executing the command, it will open the registry of the windows 7 PC
Doing a search  in registry using the keyword: "Domain" will show one of  the below path: 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Domain

Version history
Revision #:
2 of 2
Last update:
‎10-07-2016 01:57 PM
Updated by:
 
Labels (1)
Contributors
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: