Upgrading networker when services are under different account

We had Networker 7.6.3.1 on Windows 2003 with Data Domain and DDBoost. As it gave errors like:

nsrmmd SYSTEM error: Writing to a file failed ([5040] calling system(), returns nonzero).

nsrmmd Cannot write to - No error

As there was hotfix for it (http://solutions.emc.com/emcsolutionview.asp?id=esg127675) then I decided to upgrade Networker and install SP4 at first. Some time ago we changed Networker remote exec and Backup server service account from LocalSystem to server\user because there were problems accessing files from NFS share otherwise. And this was first upgrade after changing service accounts. Earlier upgrades were easy, uninstall and install new and all worked okay. But now...  I just spent a day troubleshooting and refreshing my networker related knowledge with this upgrade.

I run setup.exe, clicked next, next ... Finish and Wow! Networker was empty like freshly installed. No groups/clients/schedules and media database. Nothing. I wasn't even administrator anymore.

Ok, started figuring out what was problem and trying to add myself as administrator again. Then I noticed that Networker services were back under Local System account. Also noticed that I wasn't able to access  files under res and mm folder. Appears, that even when there is no Creator/Owner account under security, Netowrker creates files so that only service account can access media database and some other files. Files created by networker services won't inherit security permissions from folder. Ignoring some my mistakes and waiting time as scanner scanne the tapes I, at last put the Networker services back under server\user account and run mmrecov -b under the same account under what Networker services ran. I got back my configuration and media database and after some minor fixes to DD and some tape devices which were displayed as full when they weren't I was happy that all was okay. But it wasn't...

  Next day I figured out that Networker wanted to back up and clone some groups and clones that weren't supposed to run according to schedules. It just ignored all schedules from client under the group. I deleted all clients under one group and recreated them and then it didn't run any of them any more. Skipped all clients even when schedule said that there is full backup on this day. As I couldn't figure this out I got latest cumulative hotfixes and installed them correctly. That means, put administrator as owner on all Legato subfolders and files and replaced all permissions also. Ran setup under server\user account, installed server/client and as setup changed service account again to local system then I stopped services after install and put server\user account back again. Installed management console and somehow all was okay again. Networker honored schedules and at first glance all seemed to be in order( I will see it tomorrow, I guess).

After long story now there is a question, is there anywhere written procedures/solutions where are described steps that you must take to upgrade your Networker when you run Networker services under different account as LocalSystem? I figured it out myself now but is it really just trial/error way? I tried to search some but didn't find any similar cases at first.