Ok, so. I'm kind of the specialist here on program deployment for our company -
I've got around most of the issues we've seen, but the Application system is
totally new to me (we just upgraded from SCCM 2007, where "applications" don't
exist).
I'm trying to create a deployment for Office365 - I can get it
to install, that's no problem. I used the appV packager part of the setup file,
so it even does the streaming.
The problem I've got is that we're upgrading
to that from Office 2007, which was installed via MSI. I found a page that
describes the steps required to add it into the system (given the setup file is
an exe, and the application system imports from msi). I imported the
ProPlusWW.msi file as recommended, and changed the install/uninstall commands to
use the setup.exe file (setup.exe /uninstall for removal). Now, when I set the
system up for O365 to supersede office 2007, it should remove the old version,
right? I run the application from the software centre, and lo! setup.exe *32
appears, which should be the removal.
It sticks at a low amount of
RAM, confirmed to match the amount used when it's got to the "are you sure you
want to remove this software?" prompt. So, I go and create a new xml file with
"displaylevel="none" in it, and reboot value="NEVER" to get it to remove without
prompt, and without rebooting the PC in the middle of someone working... It
still sticks the process at the low level of RAM use (1740k), and I've
left it for over 30 minutes to make sure - should be more than enough time for
it to do what it needs to do.
Anyone have any ideas? Please ask if you
need any more information to help me.... Being as I can't figure out the issue,
I can't be sure what you might need to know about it.
Thanks.