The upgrade instructions are a bit vague in places.
So process as far as i can tell is:
backup policy + assignments
Uninstall DLP management tools from ePO server
upgrade extensions/help file
load policy + assingment information
what happens to the DLP WCF process? there are no upgrade instructions so I assume this version dosnt need it? Should I uninstall it the end?
anything else to watch out for?
What's the good question regarding WCF process. I was wandering myself.
9.3 does not require WCF anymore. You may safely uninstall it.
I called up support to get a more defined answer around 'when' to uninstall it.
Support said to remove it at the same time as you remove the old DLP management tools from the server. Will be giving this a go later today and will see how it goes.
When you upgrade to 9.3 from 9.2, you must upgrade the console along with upgrading the clients.
If a client has 9.3, but you havnt upgraded the console yet. 9.3 agents or endpoints can read 9.2 policies, but they cannot recieve 9.2 policy updates.
So my suggestion would be to upgrade the console first, then the agents. Both need to be done together.
Update the extension//console first always. Apply the policy in backward compatibility mode until you are ready to update the agents.
There is no need to upgrade both at the same time.
Yes thats exactly what I did,, upgraded the management tools/console and set backwards compatability mode and now can upgrade my agents at my lesuire.
Also worth noting that one thing that caught me out was the helpdesk tools app no longer works (as it connects to the DLP WCF service you uninstall) its now all integrated with ePO which is great once you realise and permission it!
Do a Backup of your policies, check and install the new package, remove the OLD management tools, remove WCF and install the new DLP tools after you log in for first time you will see a pop up you only click on convert and this is all
This is kind of a fringe scenario, but I tested it anyway. When I upgraded to 9.2.2, my database was destroyed and I ended up doing a clean install of iManager. Since in 9.2.0, the DR backup was broken, we spend a lot of time and energy on restoring the old data to a lifeboat.
IF you have applied hotfix 883497, AND you are trying to restore your backup to a fresh build, you will get a message during the restore:
Files /data/tmp-backup/source_hotfix_sr.txt and/data/tmp-backup/dest_hotfix_sr.txt differ. Hotfixes are not compatible with backup package.
Upon reviewing the versions between my imanager and the DR archive, I found that while both are running 9.2.2 with hotfix 883497, /stingray/etc/version appears to be appended with the date the 883497 was applied.
BuildType: RELEASE, Branch:Deimos, CN: 46343, Release: 9.2.2, Product: imanager, Client: Deimos-iM-Falcon_CN46343.BN2977_20130208_1702,OS: 2.6.27-12.mlos1
The workaround I used was to actually modify /stingray/etc/version, and change the last line to match what's in the archive.
check this kb: KB78774 and the releases notes of mcafee delp endpoint 9.3: http://kc.mcafee.com/resources/sites/MCAFEE/content/live/PRODUCT_DOCUMENTATION/2 4000/PD24527/en_US/dlp_930_rn_0-b00_en-us-A.pdf