Partial Unattended Install of Office 2003 + Updates

[alienvenom]

I may have to roll out Office 2003 to 100+ computers, except not all of them have a licence for Pro. I will need a slipstreamed Office 2003 Standard and a slipstreamed Office 2003 Pro version available. Is this possible? I am under the impression that only the Pro version supports the /a (administrative install flag).

Also, when I use the /a (administrative) flag, the installer will build a PRO11.MSI file. Inside this contains the serial number. While I don't want to have to put it in 100+ times, I don't want the users to be able to simply right click on the MSI and click "install" and then have access to Office 2003 Pro.

I thought about making the slipstreamed version separate from the version that will be available to the users (the files will still need to be on the network in case they need a component from Word, it wont ask for a CD), but at the same time, I don't want them to have access to the full product by copying the MSI file, bypassing whatever MST or SETUP.INI files are in place.

Is there any way to edit or modify the setup.ini file before its placed in the PRO11.MSI file after using the /a flag? Also, is there any way to slipstream Office 2003 SP2 without having the serial number in the MSI file (so it prompts for it before it installs or removes components)?

[exrcizn]

I may have to roll out Office 2003 to 100+ computers, except not all of them have a licence for Pro. I will need a slipstreamed Office 2003 Standard and a slipstreamed Office 2003 Pro version available. Is this possible? I am under the impression that only the Pro version supports the /a (administrative install flag).

Office 2003 Standard does support the /a flag.

As far as your other issues...since you're going to make two different CDs, one with Pro and one with Standard, would it work in your scenario to install these from the network? In other words, have the CD point to the network for these installs. You can then grant user permissions based on Pro or Standard.

[alienvenom]

Every user is already on the domain, and I feel it's a waste of time to manually go in and adjust permissions on each "install" based on what license they have. There should be a more "secure" way of distributing office. I'd like to somehow strip out the serial number of the MSI file, having it separate and giving only admins access to the serial number file. That way, when users need to install updates/addons, they will have access to the MSI file and even if they copy it to another comptuer, they can't just right click and click Install.

[alienvenom]

Since Office 2003 Standard does support the /a flag, I'll probably just install each one separately then point them to the network share for updates/addons/etc...

Edited March 7, 2006 by alienvenom

[Rioku]

I think the real question is how you are distributing office 2003. If you are using SMS or active directory then you should have no worry about the users getting to the MSI file. If you are having the users execute the MSI file to install office then you should be able to deny them permissions to the folder where the MSI is and create a shortcut somewhere else that points to the MSI make the shortcut read/execute only and the only thing the users can do is install office by executing it.

If this does not solve your question try explaining what your plans / current situation is a little more

Also you can deploy with a local instalation source and that will eliminate the need for them to acces the network share.

Edited March 7, 2006 by Rioku

[exrcizn]

Since Office 2003 Standard does support the /a flag

You CAN do a admin install with Office 2003 standard

[alienvenom]

then you should be able to deny them permissions to the folder where the MSI

For the 10th time, Office needs access to the MSI file when it pull updates/addons for say.. MS Query, or whatever. A "shortcut" will not work.

[Rioku]

For the 10th time, Office needs access to the MSI file when it pull updates/addons for say.. MS Query, or whatever. A "shortcut" will not work.

Try to read the whole suggestion before you comment.

If this does not solve your question try explaining what your plans / current situation is a little more.

Also you can deploy with a local installation source and that will eliminate the need for them to access the network share.

With a local installation source which is the most common and recommended by Microsoft, the users do not need access to a network source because the files that they need for updates will be on their computers.