We have figured out the issue of the clients not connecting to Policy Manager due to them having the incorrect host port number after a recent upgrade. I think now the windows autodiscover service will only discover computers on it's own network and we'll have to manually enter the ip address of computers we need to import, which is not that big of a deal. Thanks for the response, it helped me to stop focusing on the recent VLAN changes and look at the host configurations.
... View more
I recently implemented separate VLAN's for each floor and server network. Lets just say we have three different subnets. 192.168.1.0/24, 192.168.2.0/24 and 192.168.3.0. Before this change everything including Client Security Policy Management server was on one network 192.168.1.0/24 and worked just fine. Now the Policy manager cannot connect to the clients not on it's own network and vice versa. I spoke with business support and he told me policy manager can see whatever the dos command "net view" can see. Net view can only see what is on it's own network from my tests. I have created a very basic network design and would expect an application not to really on a single broadcast domain to work correctly. Am I missing something or do I need to install a policy server on each subnet and manage rules on each one. Please any help would be greatly appreciated.
... View more