Binary File Referral Problem

[Migration User]

I had to fix SEPM MR4 MP1a when a fellow co-worker installed php, current release, to create a wiki on the domain controller. When he did this, it stopped the reporting capabilities to stop working. I went back to a previous image of the sysem and updated MR4 to MP1a. Upon doing this, I noticed that none of my clients were communicating with the server to recieve the updates. I remade the client packages and reinstalled them on the clients and received the problem. Looking around, I looked at the server information window and was getting the following:

The binary file [hex formatted numbers] referred at the physical file [hex formatted numbers], which is referred at the software package [hex formatted numbers and directory path], does not exit.


Please advise. I am getting ready to install McAfee on the network to get around this and hopefully fix my problem. I have been dealing with for two weeks now and severely tired of messing with this. I researched the net to no avail.

[Migration User]

Are you referring to the MD5 hash signatures being different from the server and the client?
If this is the case, you might want to script something to remove the "clt-inst" (or something like that) package in the temp directory of the clients so the MD5 signatures match again...

Just a thought

[Migration User]

So, You went from MR4 to MR4MP1a and then back to MR4 and then upgraded to MR4MP1a

Good chances of something breaking for sure.

Now the Disaster Recovery depends on your number of clients. If less clients, Say below 1000, Then I would suggest to start afresh with a good SEPM MR4MP1a and use SylinkReplacer to get the clients back. Make sure you export the current policies and them import them later again for the new SEPM.

You can also use this way if quite less number of clients and no WAN links in between

http://news.support.veritas.com/connect/forums/loss-client-connectivity-re-install-endpoint-protection-manager