VMware Horizon Community
rdoveu1981
Enthusiast
Enthusiast
Jump to solution

Microsoft Office 2010

Hi,

I've recently just thinapped Office 2010 which appears to have gone fine but the size of the package seems rather big 1.55gb, anyone else thinapped Office 2010 and is your package a similar size? Just asking because our version of Office 2003 is not even a quarter of that size, I expected it to be bigger but not quite this big.

Regards,

Ross

Reply
0 Kudos
1 Solution

Accepted Solutions
Lakshman
Champion
Champion
Jump to solution

Reply
0 Kudos
7 Replies
Lakshman
Champion
Champion
Jump to solution

Ross,

Are you talking about the DAT file size? If yes, 1.5 GB is quite good Smiley Happy

Reply
0 Kudos
Lakshman
Champion
Champion
Jump to solution

If you wish to reduce the size further, please try adding the below lines in the package.ini.

[FileList]

ExcludePattern=*.bak,*.msi,*.mst,*.cab,*.msp

Please add these lines before [Isolation] at the top of package.ini, rebuild and check the size.

Reply
0 Kudos
Lakshman
Champion
Champion
Jump to solution

Ross,

Any luck?

Reply
0 Kudos
rdoveu1981
Enthusiast
Enthusiast
Jump to solution

Hi Lakshman,

Sorry not got back sooner, I've managed to reduce the size of the package a lot further using the office 2010 tips guide by yourself:

http://communities.vmware.com/docs/DOC-15556

This guide also helped us solve the issue we were having with KMS, we were getting activations on our KMS host but not our client which was down to issue with standard users.

Thanks for your help.

Regards,

Ross

Reply
0 Kudos
rdoveu1981
Enthusiast
Enthusiast
Jump to solution

Sorry I forgot, I have a quick question.

On your tips guide you mention about not launching office 2010 during the capture process, how do you get around updates and stuff not being prompted for? Now we have our KMS issue resolved the user is quickly prompted about how they wish to update office 2010, previously I had launched office 2010 myself during the capture process and chose for no updates. We don't want our users to be able to control any of the updating process.

Regards,

Ross

Reply
0 Kudos
Lakshman
Champion
Champion
Jump to solution

Ross,

1. You can launch Word and say 'No update' during setup capture but please make sure you disconnect the network. If you don't disconnect network, Office 2010 will try to activate during setup capture and that may have problems when deploying to users.

2. Other option is to launch the Office 2010 ThinApp, say 'No' when the updates pop up, relaunch and check for no pop up. Now, you can do sandbox merge to the ThinApp project folder using SBMerge.

http://blogs.vmware.com/thinapp/2010/11/video-howto-using-sbmerge-to-update-a-thinapp-project.html

Reply
0 Kudos
Lakshman
Champion
Champion
Jump to solution

Glad i could help Smiley Happy

Reply
0 Kudos