Server Management - Systems Insight Manager
1825759 Members
2266 Online
109687 Solutions
New Discussion

VPM - Cannot Get Scan to work for second server

 
Rob Buxton
Honored Contributor

VPM - Cannot Get Scan to work for second server

Hi All,
A step on from not working at all.
After a reboot I can now scan the HPSIM/VPM Server.
But, I cannot scan the second licensed server, I get "No file or registry access".
I have tried a number of variants on the WBEM settings.
The documentation suggests that WBEM Global properties needs to be set for just the account name if HPSIM & VPM share the same Server which is true here. The Account I've used is a Domain Account. But I've also tried with the Domain\Account format as well.
I can successfully scan the HPSIM/VPM Server but continue to get a problem with the second Server. Both are accessible by the Domain Account.
Any authoritativve guide as to what the settings should be?
It seems the System Settings don't have much impact.
In the Global Settings I've even tried using the local Administrator Account that I've checked as having the same password on both Servers. Still VPM cannot access the Server.

At the moment this has precluded me from testing / evaluating this product.
1 REPLY 1
Rob Buxton
Honored Contributor

Re: VPM - Cannot Get Scan to work for second server

I've now tried redeploying the Agent to this Server. It fails trying to logon to a local account that doesn't exist. I want to use the domain account.
I've tried changing WBEM Global to a Domain\Account setup, I've tried using System specific WBEM Paramaters for this Server. But the deployment continues to try to deploy to a Server\Username account. I've rerun the device Identification task in between each change.
Where does it get the logon information, the docs suggest line 1 of the WBEM Settings for Windows Servers. Well it doesn't appear to be.

I have set the changed password for the account in the VPM Credentials GUI. That also has the domain listed.