Policys fail to be picked up within LDMS 2016 via the vCSA
deactivateduser20 Aug 22, 2016 9:53 AMWhen trying to pull policies from the remote core server via the vCSA. Nothing happens. both by running policysync.exe and by refreshing the portal. No task xmls are being downloaded.
Inventory and security scans can interract with the core via the vCSA without issue.
The following error can be seen in the proxyhost.exe.log after a policy sync:
2016-08-22 15:42:03(1736-2136) proxyhost.exe:Call UpdateCSAROIFile() with numberofDirectConnectSuccess = 0 numberofDirectConnectFailure = 1 csaName = bCsaSuccess = 1
2016-08-22 15:42:03(1736-2136) proxyhost.exe:127.0.0.1:49557 Unable to start session with bps-core:80 internal.proxyhost.directfailed sessionrc=3
2016-08-22 15:42:03(1736-2136) proxyhost.exe:Made direct (non-proxy) connection to xx.xx.xx.xx
2016-08-22 15:42:03(1736-2136) proxyhost.exe:Connect to CSA successfully with host = xx.xx.xx.xx and IP = xx.xx.xx.xx
2016-08-22 15:42:03(1736-2136) proxyhost.exe:Call UpdateCSAROIFile() with numberofDirectConnectSuccess = 0 numberofDirectConnectFailure = 0 csaName = xx.xx.xx.xx bCsaSuccess = 1
2016-08-22 15:42:03(1736-2136) proxyhost.exe:127.0.0.1:49557 Connection close 0 0 0 0
2016-08-22 15:42:03(1736-2136) proxyhost.exe:127.0.0.1:49557 - - [22/Aug/2016:16:42:03 0000] "POST http://landesk/ApmService/PolicyRequest.asmx HTTP/1.1" 200 784 1792
2016-08-22 15:42:03(1736-2136) proxyhost.exe:127.0.0.1:49557 Connection terminated reading request line for socket 4 error code -2
There is no domain in the environment therefore the COM+ objects are still running as LANDESKComPllus and the scheduler account is running as local system.
Other devices, including LDMS 9.5 client have errored with the above as well as working without issue.
If I run policysync /taskid=xxx with the specific task ID then the policy is downloaded and executed wihtout issue.
I've tried rebuilding the client side database but an unsure as to whether this is still used. If so, when using the validate switch, the client errors with this message: