Endpoint version updating on console

Considering the young age of these forums (they still have that new forum smell), I'm really not sure if this is the correct forum in which to post this topic...I beg for mercy if it is not. :)

We've noticed some behavior for which we don't have enough solid data to be able to explain. So, I'm seeking the experience of others.

What are others noticing for version data on the console when endpoints are upgraded? Does the version information for endpoints update properly or does the version information still show the old version?

For some of our endpoints (~18k) we see the version data update on the console, but for other endpoints we don't. As we are very distributed in our deployment and use of the Identity Finder client software, we haven't been able to determine if the updated information is a function of platform, version, upgrade path, deployment method, or if it has some time component.

Thanks!

-Dan


Edited by danlehman - 06 Dec 2010 at 10:17am

Following up on this thread with some results from recent testing...

Using Console version 4.7 in our testing environment, a Win XP SP3 virtual machine with Client version 4.6.1 that is upgraded to version 4.7 shows an updated Client Version on the console only after a search has been performed on the endpoint. Restarting the Identity Finder Endpoint Service does not appear to affect the version displayed on the console.

Now, a few notes about the testing and results. The tests were run on a very compressed time scale. Changes would be made, services restarted, searches started and stopped before completion, and the console checked, all within a couple minutes. This client is the only client currently connected to our testing console. And, these tests were part of some larger testing on updating clients via the new feature of Console version 4.7. But, the versions do appear to update, so we've got that going for us, which is nice...

-Dan

To minimize load on the server, client version information is only sent to the console during initial registration (when a GUID is requested) and when a search is completed.

I wanted to also put my two cents in on this - that I've also suggested this to support in past as I agree updating the client version after the upgrade makes sense for managing client upgrades. The version doesn't have to be sent every poll - just during the update.

Thank you all for the discussion.  There are a lot of complexities to this issue, so the solution that we plan to implement is to create a service job that will request clients to report their version information.  You will be able to run this job whenever you'd like or on a schedule to update the information across all endpoints or specific tags or endpoints. 

Basically, the service job will run, on next poll, a client will receive the request, process the request, and the send the requested information back to the console.

We'd love to hear feedback to know if this will meet everyone's needs.