ePO 3.0 dats not updating

[malreaux]

I recently upgraded ePO 2.5.1 to ePO 3.0. I am still testing it. After the agent is upgraded to version 3.1 it will not update the dat files for VS7.

Interestingly, I have used the 3.1 agent to push VS7 down to a client. At the end of the installation, ePO automatically updates the dats.

I am running Win2K.

I am using the agent update task to attempt to update the dats (VS7 has no update task itself in ePO 3.0).

Do I have to set up a distributed repository or should I be able to update from the master repository?

Thanks.

 

[AVChap]

You should be able to update from the master repository (ePO server) just fine. Make sure that the repository is updated by running the pull task. This will ensure that the latest updates are there.

HTH,

AVChap
... my $1 worth of advise, 2cents isn't enough due to inflation

 

[malreaux]

FYI: My location uses WordPerfect Office 2002. Pushing the agent out caused errors with WordPerfect (error 1706, I think - a known WP prob) in which WP tries to perform a reinstallation and asks for installation disks. After you select cancel about 15 times, everything runs fine. But, on bootup, the user receives an UpdaterUI.exe error and the agent is not installed correctly and does not talk with the ePO server.

The fix, which unfortunately involved a lot of walking around, was to manually install the agent on the computers that the agent push did not succeed on. I would say that only about 50% of my pushes worked correctly.

 

[mrbase]

From my point of view the use of distributed repository is a option if you have more then one location and do not have the bandwidth available (or simply don't want to use it for this purpose) connecting a large number of clients directly to your master server. If you are simply in one office building it's the simplest thing to just directly let them connect to the master server, you can still setup a distributed repository as a failover.



De rooie poon....is never alone

 

[malreaux]

You do not need a distributed repository. The only time I think you might need one is of you either have many thousands of clients or a group of clients at another location that has minimal bandwidth.

Some help on the dat updating:

View the agent monitor on a client and send it a wakeup call. Does the agent receive the call? What does the agent say when it tries to update?

Is your master repository updated?

Go to a client, open up the agent monitor. Now right click on the VS7 icon and select 'Update Now' What happens?

You can try deleting a few clients from the ePO directory and wait for their agent to repopulate them and see if that improves their updating for those clients. I had to rebuild my ePO directory because some of the clients were not talking with ePO.

Good Luck.