Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Deploying MSP file as a group policy
- Thread starter mrtoledo
- Start date
I had a tough time with this one. I wanted to deploy it with SR3 installed also.
A) Get the Office 2K Resource Kit. Then you use it to create an .MST file, which is basically a Transformation file that you can tell your policy to use in conjunction with your MSI file for an unattended install
B) Repackage your Office with SR-1A and then SR-3 patches. You need to use the MS Installer commands (MSIEXEC). You can slipstream the patches onto your office installation by using the /P option in MSIEXEC. If you noticed, when you install Office 2K (no service release) and then you update to SR1a and then SR3, Office will ask you for the CD or installation path everytime you attempt to change something in office or have a new user and new profile created in the machine. Look up MS Knowledge Base on "Office asking for files" and you will find the Q article explaining how to slipstream the Office directly to SR-3 and it won't bug you with that ever again.
I admit, it was hard work to finally figure it out, but it was worth the effort. I can deploy Office 2K SR-3 anywhere with Group Policies and all the correct files are on the machine, so no prompting for files, especially on a laptop when it's miles away from home.
"In space, nobody can hear you click..."
A) Get the Office 2K Resource Kit. Then you use it to create an .MST file, which is basically a Transformation file that you can tell your policy to use in conjunction with your MSI file for an unattended install
B) Repackage your Office with SR-1A and then SR-3 patches. You need to use the MS Installer commands (MSIEXEC). You can slipstream the patches onto your office installation by using the /P option in MSIEXEC. If you noticed, when you install Office 2K (no service release) and then you update to SR1a and then SR3, Office will ask you for the CD or installation path everytime you attempt to change something in office or have a new user and new profile created in the machine. Look up MS Knowledge Base on "Office asking for files" and you will find the Q article explaining how to slipstream the Office directly to SR-3 and it won't bug you with that ever again.
I admit, it was hard work to finally figure it out, but it was worth the effort. I can deploy Office 2K SR-3 anywhere with Group Policies and all the correct files are on the machine, so no prompting for files, especially on a laptop when it's miles away from home.
"In space, nobody can hear you click..."
- Thread starter
- #3
Hmm.. maybe I didn't type it our right...
You must apply SR-1A first, then SR-3. This can be done with the GPO's, sure.. BUT... by doing that, everytime somebody requests something new from Office, or a new user (profile) tries to open an Office product, it will look for the original files from it's original source. It's an MSINSTALLER issue. Imagine a laptop not being able to open PowerPoint when they log on locally as an administrator at the big corporate meeting at some hotel conference room because it's looking for DATA1.MSI...
"In space, nobody can hear you click..."
You must apply SR-1A first, then SR-3. This can be done with the GPO's, sure.. BUT... by doing that, everytime somebody requests something new from Office, or a new user (profile) tries to open an Office product, it will look for the original files from it's original source. It's an MSINSTALLER issue. Imagine a laptop not being able to open PowerPoint when they log on locally as an administrator at the big corporate meeting at some hotel conference room because it's looking for DATA1.MSI...
"In space, nobody can hear you click..."
- Status
Similar threads
- Locked
- Question
- Locked
- Question
