cancel
Showing results for 
Search instead for 
Did you mean: 

Prognosis 11.3p2 integration with vCenter 5.5

Highlighted
05 Base Camper

Prognosis 11.3p2 integration with vCenter 5.5

Can I use a active directory domain account with Prognosis 11.3p2 and vCenter 5.5?  I am able to use a domain account with Prognosis 11.3p2 and vCenter 6.0 but not 5.5.  My security team won't allow a local account without vendor documentation saying local account is required.

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

Re: Prognosis 11.3p2 integration with vCenter 5.5

Hello Kelly,

 

If there is an AD account used for access to the vCenter Web UI, then this set of credentials should be able to be used by Prognosis as well.
If only a local account is able to access the vCenter Web UI, then Prognosis will also need to use a local account.

 

Please see this Prognosis 11.3 Online Help page about VMware monitoring setup: Prognosis Configuration for vCenter
 - If prompted for a login to see the page, use https://Community.ir.com Credentials.

 

If the above statements do not seem to be true, then opening a Support case for more specific support on this issue is recommended.

 

Thank you,
Scott Baldwin

 

View solution in original post

2 REPLIES 2
Highlighted

Re: Prognosis 11.3p2 integration with vCenter 5.5

Hello Kelly,

 

If there is an AD account used for access to the vCenter Web UI, then this set of credentials should be able to be used by Prognosis as well.
If only a local account is able to access the vCenter Web UI, then Prognosis will also need to use a local account.

 

Please see this Prognosis 11.3 Online Help page about VMware monitoring setup: Prognosis Configuration for vCenter
 - If prompted for a login to see the page, use https://Community.ir.com Credentials.

 

If the above statements do not seem to be true, then opening a Support case for more specific support on this issue is recommended.

 

Thank you,
Scott Baldwin

 

View solution in original post

Highlighted
05 Base Camper

Re: Prognosis 11.3p2 integration with vCenter 5.5

fqdn for domain was my issue.