I checked and the extensions were already checked in. Phew, it wan't THAT simple All other agents are 4.8 so I have no problems with that. As all machines have been rebooted by maintenance in between including the ePO server itself, I tried again today but still the same results. I'm gonna let this rest for a while.
I upgraded ours from 4.6.8 to 5.0.3 yesterday, and have the same situation.
Our clients are communicating on the previous v4.8.x client, and 5.0.3 client is in evaluation.If we deploy our remotely, then the clients are unmanaged - however running the framepkg locally, updates the client, but it takes a while
I have just installed a fresh server with ePO 5.3.2. It automatically downloads Windows Agent 220.127.116.113. I deploy the agent to a fresh 2008R2 server in this case, and still exactly the same issue as the one I opened this topic for. However as I intend to move to a completely fresh ePO setup, not migration the database and stuff. I want to export the policies and systems and such (and I don't want to discuss that move ). However as 5.x is still not working and I can't move that new server back to 4.8. Still not fixed. I think I'm gonna log another ticket for this. Or has anyone managed to fix this already?
I had the same issue. The only fix I was able to find to fix the issue was to create a new agent-server secure communications key under configuration>servers settings> security keys. I am still testing but the systems are now in managed mode. I am now able to run task and I can deploy products without an issue. In anyone else is having the issue please let me know. Thank you.
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.
Thousands of customers use our Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership: