Noticed on friday while doing trouble shooting of NAP, that while VistaBiz was assigned (192.168.145.145) an ip address set in the dhcp scope range (192.168.145.145 - 192.168.145.254), client2 (192.168.145.143) was not. Which we think is the cause of health policy's not working properly (as it isn't using dhcp enforcement, properly)

Asked Mr Kravitz if he had any idea what was causing this dhcp assigning to be wrong, and told us that instead of using NAT as our network adapter settings to use a customed setting (VMnet2) instead.

After changing network adaptor settings for all the stations, restarted all of the machines.

client2 now assigned with a proper address (192.168.145.146) within the range, tested out auto-remediation of firewall by turning firewall off.
health alert shows limited connectivity and lack of anti virus.

created client3 by copying client2 and renaming machine. checked ip address to make sure it's in the scope range. Installed Symantec EndPoint anti virus on client3. Rebooted. Check health status.
Lack of update of health status due to no internet connectivity (using customed network). Tried to use VMnet8 (nat) to which allowed internet connection for domain controller (ADS) and VMnet2 for the rest(NAP, client2, client3) but unable to connect to ads. reverted back to VMnet2.