Software Deployment

ORIGINAL: gmouse
Am trying to do a complete install of Office Enterprise Suite + VISIO + Project 2007 and deploy it with SCCM 2007 SP1.
We had stability issues with using the internal Office install linking method, so are just running three linked programs in SCCM. However, we are seeing issues with adding VISIO and Project without first rebooting the computer after the install of the Suite.
I would figure I'm doing something wrong, or, this is just the way it has to be, but, thought I'd ask.

1. What's best way to do this full install?
2. Is a reboot after the Suite, prior to adding any additional Office components avoidable, and, if so, how?


You may be having problems with SCCM, not Office. To verify, manually do each of the installs separately, not rebooting between each one, and see if you get the same problem/error. What is the "stability issue" - just not running, problems with the app?....
Seems like you should not have to reboot between office components. While Visio and Project aren't in the main office suite, they are still "Features" really of the main office product, in fact are called "Microsoft Office Visio" and Project IIRC

Well, by flaky, I mean that using Office linking to add VISIO and Project didn't alway get successful installs (seems it worked better with Office 2003), so, using linked programs in SCCM, one for each product (Suite, VISIO, Project) always seemed to work.

On the reboot issue, it seemed there were some integration issues or corrupt installs--could be in any program, not just VISIO or Project. Running the full Detect & Repair would always fix. When we added in a reboot after the Suite, THEN installed VISIO and Project (no reboot between them), all was well.

Like I said, I may be doing something wrong, but, that's been our experience.

My problem with a reboot in the middle, is that we have encrypted laptops and remote computers that you must logon through the encryption screen, prior to getting into Windows, so, with the reboot in the middle, and, most deployments being at night or remotely (using BITS, so, takes a long, slow download, then an install, whenever), unless someone is sitting right there with the laptop when the reboot occurs, it can't install the last two programs. Otherwise, I really wouldn't care about the reboot (I'd probably ALWAYS reboot AFTER the full install, just CYA).

Thanks.

Running the full Detect & Repair would always fix.My insatiable curiosity and a desire to do a professional job simply wouldn't allow that situation to go by without finding out EXACTLY what got fixed. Once you know that, you know how to fix it before the situation arises. Use a lightweight snapshot tool e.g. In Control or InstallWatch to do that.

Not disagreeing. Sometimes available time to do this is the issue...<G>

I just thought that...it may have been normal to have to reboot, after installing the Suite, and, prior to installing any additional Office programs. If this is not, and others are having no issues, then, I'll delve further.

Thanks.

True, but I'd argue that time spent "debugging" now means fewer cheesed off users. Experience suggests that management would prefer not to alienate their user base.

True, that.

I've actually got a call in with Microsoft Premier, so, will get (hopefully) the straight scoop on if a reboot IS required.

Thanks.