We recently upgraded the servers to EEM 5.2 with some clients running 5.1.3 and others running 5.2 with the goal to upgrade all our clients to 5.2. We use group policy to deploy the clients. Our GP's had some permission issues so some of the encrypted 5.1.3 clients also had the 5.2 client install. Now I have machines with both clients on them. When I click the tray manager and show status it is blank. My research reveals that the tray manager is now 5.2. After performing a sync I navigate to the 5.1.3 install directory and open the log file, it shows it can still communicate and update when needed. I am trying to get my machines back to just having 5.1.3 installed. Can anyone help with this?
So far I have attempted the following...
One other thing to note is that after removing 5.2 it still shows in Add/Remove programs.
Any help is greatly appreciated...rebuilding machines is NOT an OPTION.
What is status it is showing on server ? (cleint version activated) ???
if it is showing 5.1.3 (ofcourse it would be showing 5.1.3 only).
I would try (only on test machine or after taking bakcup)
1. select the problematic machine > properties
2. Files Tab
3. Change the Safeboot Client files group from 5.1.3 to Safeboot Client files group 5.2.x (or McAfee Endpoint encryption file group 5.2.x)
4. Synch the machine...
5. it should unlod TRay icon... (see the sbclient log)
6. reboot machine (it should upgrade to latest version)
(I have not tested it but it should work in your case)Message was edited by: Ram Dudani on 1/13/11 9:47:32 AM CST
Why not to remove decryption and client completely (Boot protection - "Remove").
Confirm that there is no trace of EEPC on client PC.
Delete machine object for that PC.
Run new EEPC install set on the client PC.
Or, better yet, swap install sets for machine object, then perform sync. That would not perform lengthy decryption/encryption.
better yet, swap install sets for machine object, then perform sync. That would not perform lengthy decryption/encryption.
how ?Message was edited by: Ram Dudani on 1/13/11 9:55:50 AM CST
Select machine object, go to Files side menu.
Unselect older client file set, select newer client file set.
Perform Sync from client (or EEM, if IP is current).
You should be able to resolve this by running a full install package over the top of the missmatch machines - that should reset everything to the files in the install package?
Pushing the new client files did not work. The client did get them and updated but I am still having the same issue.
To the latest post...
How would you do a full installation? Isn't that done when the 5.2 msi is kicked off?
v5 is normally deployed via the eepc.exe built from EEM - are you deploying via EPO? If so the question is different and I'm not sure what the answer is - the whole reason EEPC5 didnt use MSI's is because of this kind of problem.