Answer by Andreas G. ·
When the agent is bootstrapable the Collector will sent the agent the updated version during the restart of the Agent
Answer by Andreas G. ·
thanks for the update. always good to know when folks find their own solutions. So - you are all set now?
Answer by matt S. ·
i think I found the issue. When looking at the agent configuration I noticed I was in version 5.0. We have 5.0 & 5.5 running on the same machine, not so much on purpose but more we just never uninstalled the old version. When I look at the agent configuration for 5.5 its now saying
.Net agent is still loaded but has been deactivated. Please restart or system reboot is required
I uninstalled 5.0 so 5.5 is the only one installed.
I did installed the 6.1 collector and as I mentioned above and in the Agents Overview in 6.1 its now listing this agent stating version 5.5 restart required.
Answer by matt S. ·
On a server I'm monitoring using dt 5.5 I'm seeing this warning in the agent configuration. I've seen it before when installing dt for the first time and a few reboots worked it out. The odd thing is that we're getting events and data just fine. I can look at recent purepaths ok and for all intents and purposes appears to be working fine.
Should I be concerned?
I'm about to upgrade this to version 6 and I was going to...
1) shut down the collector (we run collectors on the same servers as the agents themselves )
2) install the 6.1 collector
3) configure it to point to the new dt server
4) start up the collector
5) let dt do the rest
by #5 I mean at some point dt will upgrade the agent to the newest version. I know this is the way things work but in the past I've manually upgraded the agents so that I can control when it happens as I expect to have to reboot it to get it fully connected (i.e to get rid of the error message Agent did not connect or did not find matching profile).
Thank you.
JANUARY 15, 3:00 PM GMT / 10:00 AM ET