upgrading from 6.2 to 6.3 with Endpoint Operations Management and agent token

[rgcda]

I'm using Endpoint Operations Management in vROps 6.2.  The release notes indicated that I have to upgrade the EP Ops agent to 6.3 prior to the vROps upgrade as the old agent is not compatible with vROps 6.3.  They mention two KB's in the release notes.

Upgrading an Endpoint Operations Management Agent from Version 6.2 and above to Version 6.3 (2146447...

Upgrading Multiple Endpoint Operation Management Agents Simultaneously from a Script for Versions 6....

I'm using KB2146447 because I would like to test the 6.3 agent on several test servers before rolling out to everything.  The KB has you enter a string into your web browser to find the agent token.  I enter the string for a test server into my browser and it returns information but how do I know what the agent token is.  Here is an example of the output:

0100mycomputer.company.comEP Ops AdapterWindows1466789621906-5820434769761082052-20125939034453028921466789621906-5820434769761082052-2012593903445302892falseNO_PARENT1936aa2a-64fe-4ffa-aee7-9337679090470f33c81b-e520-48e5-bcc1-c68ef688500eDATA_RECEIVINGSTARTEDGREEN100.0true5

The KB doesn't indicate what the agent token would be and I cannot tell from the string it returns.  Has anybody run through this process and know what the agent token would be?

[JimKnopf99]

Hi,

i did it this way. Installing Postman. It is a REST API Client. With that, you are able to query your vrealize server.

Postman | Supercharge your API workflow

To get the agentID try the following Get Command

https://vrealizeservername/suite-api/api/resources?adapterKind=EP%20Ops%20Adapter&propertyName=fqdn&...

Then you receive an answer where you are able to see the agentID

With a second GET you are able to receive the agent version

https://vrealizeservername/suite-api/api/adapterkinds/EP%20Ops%20Adapter/resourcekinds/EP%20Ops%20Ag...

With the following command, you could update the version. But the version has to be on the vrealize server beforehand.

Frank

[rgcda]

My actual issue was that I was using Microsoft Edge.  When I switched to chrome the string returned information I needed.