I am in the process of installing MSOffice 2007. I have used the OCT (Office
Customization Tool) to set it up that if there is an existing profile, to
migrate the settings, amongst a handful of other settings. We deploy using
the standard MSIEXEC line with the OCT MSP file in the string, and we use the
new MS System Center Configuration Manager (SCCM), FULLY silent installation
(which uses the local SYSTEM user account to install, no UI at all)

Communicator 2005 is on the system, and it interoperates with the email
profile and holds it "open".

So after MSOffice installs, and we reboot, then after logging in
(Communicator starts automatically upon logon by default, all users leave
that on), you go to Outlook and run it.

If Communicator is not on the system, it runs fine, and email comes up. If
Communicator is on the system, it fails to find the Exchange server, and
eventually it hangs the system.

The "Automatically Start Communicator" settings are HKCU, therefore can't be
changed by installation by the SCCM package. I figured I could do a RUNONCE
Registry line and run a VBS script we have that kills processes, but if I
kill the Communicator.exe process, it only kills the window for it. It
doesn't kill the little TSR that sits down in the System Tray, and therefore
the MAPI profile is still held open, and Outlook can't start.

Can anyone identify the way to kill Communicator 2005, or have Outlook not
care about it and still do the new Outlook2007 email profile?

Thanks much

Archived from group: microsoft>public>outlook>installation