cancel
Showing results for 
Search instead for 
Did you mean: 

Agent 4.0 with Deep freeze invalid sequence number, is there no solution?

Jump to solution

Good day,

I am having an issue that's been going on forever with agent/server communication when Deep Freeze is installed on the client computers. I have ePO 4.0 patch 5 and most agents are 4.0.0.1494. I have tried everything imaginable, including uninstalling the agent / rebooting, update task, cleaning the registry entries, etc. Then it works fine during my tests but when I come back the next day it has reverted to the problematic state (there is a deep freeze maintenance period on some computers, it seems from this point the sequence number is not accepted). Then there is no communication anymore. I obviously can't be alone in this predicament as there are Knowledge base articles about it, but no real solution. It just shows how to identify the problematic agents in the database table.

There is an option in the server where you can disable the sequence check, but it is not recommended by McAfee... anybody using this?

Thanks!

1 Solution

Accepted Solutions

Re: Agent 4.0 with Deep freeze invalid sequence number, is there no solution?

Jump to solution

Yes you will have to disable the sync check in the server.ini. Or not freeze the registry.

1. Stop the ePO Services
2. Add the following to the server.ini (under the server section)
    ConnectionsRequireValidSequenceNumber=0
3. Restart the epo Services.

You will have to have patch 5 or 6 on the epo server as well for this feature to work.

2 Replies

Re: Agent 4.0 with Deep freeze invalid sequence number, is there no solution?

Jump to solution

Yes you will have to disable the sync check in the server.ini. Or not freeze the registry.

1. Stop the ePO Services
2. Add the following to the server.ini (under the server section)
    ConnectionsRequireValidSequenceNumber=0
3. Restart the epo Services.

You will have to have patch 5 or 6 on the epo server as well for this feature to work.

Re: Agent 4.0 with Deep freeze invalid sequence number, is there no solution?

Jump to solution

Thanks a lot, this is doing the trick without any apparent drawback­. The errors are still occuring but they no longer disturb the console.