Office 2003 Silent Install Mst

Hi, Copy the MST file to the same directory that your SETUP.EXE is located. Make sure to check the Include entire directory option (so that all of the Office 2003 files needed for setup are copied down to the targets).

Office 2003 Silent Install Mstsc. And this is what it looks like when you edit it in ORCA: Once you have made the changes you are happy with you can simply save the changes either directly to the MSI. Hi Mike, I installed/upgraded Office2000 to Office 2003 using the MaintWiz for office2003, and the whole thing went smooth,.

I have an MST file called Office2003Pro.MST. To deploy using this MST I simply added the following text to my Parameters field. TRANSFORMS=Office2003Pro.MST /qn My Installer File is SETUP.EXE. Installing Fonts Windows 7 Script Download there. Here is a snapshot of my Installer. Just a heads up. There are a lot of installation files in Office 2003. (I have 4,172).

The deployment can take a while to copy these files down to the target computers.

Hi all, We're dealing with the following situation, Our Package/MSI distribition tool can't work with MST files (VAI Deployment Center) So in most cases we apply the transform on the MSI using MS Orca Works fine in all cases.but. With office 2003 we encounter a problem with the product key.

These are our steps: 1 - Admin install to disribution location, (setup /a) 2 - Running the Admin install works, we don't have to enter a Product key 3 - Create a MST using MS 'C.I.W.' 4 - Apply te MST on the MSI with Orca and we save de new MSI as Transformed.msi 5 - running the Transformed.msi doesn't work, we have to enter the Product Key So why make a new MST only containing the Product key using WISE InstallTailor?

Won't work: search google on 'office 2003' + InstallTailor Any suggestions? Subsense, I would make every attempt to find a way to deploy the original Office.msi in a 'best practice' manner, with your.mst file being applied at the time of install. If that means not using VAI Deployment Center for Office and using AD Group Policy or some other tool to push out Office, I would do it. It sounds as if - in the past - you have actually re-compiled Office.msi's because of not being able to use.mst's. If this is what you have done, have you made sure that the original GUID for the those.msi's have not changed?

If they change, it can lead to complications and problems down the road. For example, an.msp from Microsoft cannot be applied against an admin install of Office if the GUID has been altered. You can do this.I did it for MS Project once and it worked. Open the Office msi and go to the Property table. Create a key called ProductID.exactly like that. It has to be that case for all letters. Add the Office Product key with the dashes included and save the msi.

It wont try to recompile the files so you should be ok. When the user installs it.it wont ask for a key but on its first startup.it will.

The key will be filled in the spaces already and the user only needs to hit enter and its done. As I said it worked for MS Project.so its worth a try until you sort out a reasonable deployment method. I must say tho.that I agree with Craig 100%. You are charting very murky waters if you try this sort deployment and if you get into trouble you wont be able to troubleshoot it easily. If you find that Office 'hangs' on startup for users.then find out why.permissions or for roaming users maybe a DFS or DNS problem is stopping them from seeing the Office Application Data in their profile.etc etc. MS does spend alot of time to try to make the Office Family very workable for most companies/people and if the problem is your environment then you should concentrate of fixing it in my opinion. Sorry not ranting.just hoping you dont build a big rock for your own back to carry.

OMG did I really defend Microsoft then?.time for a valium. I'm in an environment that buys many retail versions of Office and the office products. With Office 2002(XP) and earlier, my predecessor created a deployment package that installed, then on first use, required to the user to put in a Product Key. The application then will not work without a valid key. I am trying to figure out how this was done, but an trying with Office 2003. I cannot find a solution. I noticed the post in this subject that says to put insert a Property 'ProductID' for MS Project.

Have you seen this work with the full office suite? I'm not able to make it work.

Do you know of another property that might have to be changed? Any help would be greatly appreciated. Ultimix 139 Rapidshare Files.