Software Deployment

I seem to be having some issues with a MSI file.. I'm currently "repackaging" Microsoft personal folder backup. This is a microsoft MSI with a executable wrapper around it. Extracted the MSI, but now it doesn't install for all users that well. What seems to be the problem:
it's a plugin for Outlook. Outlook checks a specific folder (C:\Program Files\Microsoft Office\OFFICE11\ADDINS) for COM+ addins. However, when the MSI is installed for all users (adding allusers=1 to commandline) the windows installer installs the files in the user profile.
Took another look at the package, tried to create a transform. One way or another, Wfwi isn't able to create a transform. (MS MSI's [:@] ) ..So i decided to edit the msi directly. (Bad practise i know, but i hate working with Orca so what's a man to do? :P) Changed some bad file source paths (e:\office?) and saved the MSI. It seems the package writes a local machine key when installed normally, figured out it needed a current user key to "find" the plugin in the right directory per user. Key:

[HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\Addins\Microsoft.OutlookBackup.1]
"FileName"="C:\\PROGRA~1\\MICROS~2\\OFFICE11\\Addins\\outbak.dll"
"FriendlyName"="Outlook Backup Addin"
"LoadBehavior"=dword:00000003

The problem is installing the key per user. Created a CURRENTUSER feature in the MSI, at the top of the feature tree (parent) and the standard feature under that. The package seems to work now. (if another user logs on, outlook loads the plugin, it is selectable etc.) However, when removing the program, the currentuser keys, created by the currentuser feature, aren't removed. Did i miss something when creating the current user feature, or do i have to add or change someting to the registry/installexecutesequence table within the MSI or something? TIA