Software Deployment

I repacked 2007 to an msi
why punish yourself..??

http://office.microsoft.com/en-us/ork2003/HA011401941033.aspx

ORIGINAL: Lordeos
I repacked 2007 to an msi ...


It must be huge!!!
And, you dont tell us what the error is.

machines use the normal.dotm file from %userprofile%\appdata\microsoft\templates or C:\Users\%user%\AppData\Roaming\Microsoft\Templates for Vista. If no local copy exists,it looks in the workgroup location, if that doesnt exist it creates a new one locally.
And it is called "normal.dotm".

hi,

Well it is kinda huge (the office msi is 1,3 gig) ...
I do tell you what the error is "wheni open Word after deployment i get the error (the function you are trying to run requires macro language support...when program was installed...chose not to install support for macros or controls).

I already copied new normal . dotm files in it but it makes no difference .


So if i read the article right it would be sufficient to type setup.exe TRANsFORMS (mst file) ????

It's 2007 not 2003

thx,

Hi,

I can't offer any advice on the specific problem you are getting but I can point towards some info regarding packaging Office 2007.

Repackaging Office 2007 as an msi is a really bad idea that is likely to cause you major issues going forward. Luckily Microsoft have made pretty easy to customize and deploy office.

Below is an extract from http://itninja.com/link/office-2007-setup-properties . Essentially just by doing an admin install from the installation media you create an msp file that just needs to be placed in the Updates folder.

I hope this helps.

Justin

The successor of the famous Office Resource Kit Tools (ORK) to customize the Office installation is now called Office Customization Tool (OCT) and is included within the original setup so you don't need to download anything.

To start the Office Customization Tool (OCT) type setup.exe /admin.

At the end of the process, the OCT saves your choices in a MSP file, rather than the transform (MST) produced by the Custom Installation Wizard. Like a transform, the customization file results in uniform default configuration of the product for all users. Unlike a transform, however, which you had to specify explicitly on the command line or in the Setup.ini file, you can allow Setup to apply the customization file automatically by storing it in the Updates folder at the root of the network installation point.

During the installation, Setup finds and applies all the MSP files in the Updates folder - both customization files and Software Updates - that match that product. You can specify an alternate location for MSP files in Config.xml, or you can point to a particular customization file by using the /adminfile command-line option.

ORIGINAL: PuterFix.biz

Essentially just by doing an admin install from the installation media


Ahh if only that were true! Office 2007 does not allow an admin install in the traditional sense so unlike Office 2003, it's not easy to remove the dependency on setup.exe. The /admin qualifier to setup.exe just instructs the OCT to kick in and allow the creation of an MSP file.

The rest of the information quoted is, however, good to go.

Regards,

Spartacus

hi guys ,

Well , this how i fixed it ...

Indeed with the /admin you get the option to create an msp file .... in the updates folder i putted all the sp1.msi files .

To do remote deployment i use the program RemoteExec ... So i did an action to copy all the files to the remote computer and then run the setup.exe /adminfile "xxxxx.msp" command as argument .

Office is installed with Sp_1 . so mission accomplished .

Thx for all the info.
greetz mike