Skip navigation

So one of most common software is Microsoft Office 2010. We all want that software be installed regardless it’s on physical machine or VDI. There are so many different options you can choose and you may face. This post is focusing on deploying Microsoft Office 2010 to VDI via App-V.

 

Why do we need to use App-V?

App-V allows user to steam down application parts which this app really needs when it runs. With VDI solution, if we don’t use App-V, we may install entire Office 2010 on each VDI VM and if you have 100 VDI VMs in your environment, it may use 200 or 300GB precious SAN space easily just for this software only. With tons of benefits of using App-V, I am not going to explain it too detail.

 

Why don’t people use App-V Office?

Well, reason No.1, it’s complicated. With using App-V, it involves so many different other technologies and all of them have to work together. Second reason is App-V still has some limitation with one app working other app since each App is supposing to work in it’s own sandbox. But this is going to change with App-v 5.0 sp1 and other tools to help you deploy office.

with no further ado, Let’s start

Environment introduction

Server:

Testhyp02: Windows 2012 with Hyper-v running on it, App-V Server & Management component has been installed. For more details, please to see my last post.

Workstation:

All workstations are VMs running on Hyper-v.

You will need to have at least two workstations.

VM1:

Windows 7 SP1, 32bit (As App-v Sequencing server to catch software installation)

VM2:

windows 7 SP1, 64bit ( As VDI template to run App-V software).

Note:

You must use Windows 7 with Service Pack 1 as client. Win7 without SP1 doesn’t support App-v Client. You must use 32bit for App-v Sequencing server since there are certain software which only has 32bit version!

Preparation for your VMs:

Now, I must ask you to focus on preparation of your VMs before you start installing.

  1. Build windows 7 32bit SP1 VM from scratch. (64bit if it is VM2)
  2. Make sure you have installed Integrated Service
  3. Make sure you have join the VM into your domain
  4. Disable firewall
  5. Create Install folder under c:\

 

  Search Internet and download following software on your c:\install\Other Toolsclip_image002

Notice: You need both 32bit and 64bit Powershell to install on VM1 and VM2.

6.    Install above software

7.    Download following software and put into c:\install\AppV Prep

clip_image002[5]

                 You need both 32bit and 64bit version of Deployment Kit

  • Office 2010 SP1 Professional Plus 32bit ISO (extract to a folder)
  • Office 2010 SP1 Profession Plus Volume License (XXXXX-XXXXX-XXXXX)
  • Microsoft Desktop Optimization Package (It contains App-V 5.0 sp1 non RDS client)
  • Microsoft Application virtualization 5.0 SP1 (from Volume License Portal)

 

 

You need to extract Office Deployment Kit to separated folder like above picture shows. Also extract Sequencing kit.

clip_image002[7]

clip_image002[9]

Extract Office 2010 Professional Plus ISO (must be 32bit) to a folder. Only 32bit Office will work with integration and it can work on both 32bit and 64bit Win7.

Copy App-V_Seq_Kit into Office folder and also Deployment kit as well

clip_image002[11]

 

clip_image002[13]

 

Deploy Office 2010 App-v Kit

There are lots of articles about it on the Internet. In this case, I’m using MAK to register.

image

Few things about this deployment.

1. Must use elevated CMD to run this command

2. Must NOT USE Powershell to run, it won’t work

3. When it is running, don’t jump on Services.msc to check what’s New, it will crash the installation

 

So what this command does is to install a License service like KMS in local PC with Volume serial number of Office 2010 to make sure Office application works correctly.

After installation, you can open servcies.msc and see whether it works or not.

clip_image002[27]

 

Install App-V Sequence

Install App-V Sequence on VM1 which is running windows 7 sp1 32bit with “Other Tools” installed first. Add IP address, DNS, Join domain, disable firewall and copy all above software on the VM1.

You shouldn’t have issue to run App-V Sequence

clip_image002[15]

clip_image002[17]

clip_image002[19]

 

Run App-v Sequence and do following steps

clip_image002[21]

Add keys like following

Open the "Exclusion Items" tab and add the following: [{Common AppData}]\Microsoft\OfficeSoftwareProtectionPlatform [{Common AppData}]\Microsoft\Windows With Mapping Type = “VFS”

clip_image002[23]

 

clip_image002[25]

 

 

Capture Office 2010 with Accelerate Package

Yes, you are very lucky that Microsoft has this accelerate package which does lots of work for you.

Now, it’s time to start App-v sequence

clip_image002[29]

 

clip_image002[31]

 

clip_image002[33]

 

clip_image002[35]

If you don’t have AP, you have to capture office installation procedure and hope it’s clean capture!

clip_image002[37]

 

clip_image002[39]

With AP helps, system all generate 3 copies of appv file with some modification in each. All what you need is the last version with integration embedded.

 

clip_image002[41]

 

clip_image002[43]

 

clip_image002[45]

 

Following is the first version.

clip_image002[47]

Continue to capture running parameters, do not run Sharepoint and Outlook components

 

clip_image002[49]

clip_image002[51]

clip_image002[53]

 

clip_image002[55]

 

clip_image002[57]

 

clip_image002[59]

 

Now, start to integration procedure

clip_image002[61]

 

clip_image002[63]

clip_image002[65]

You need to be patient since VM1 is loading 1.5GB office installation appv file.

 

clip_image002[67]

 

clip_image002[69]

 

clip_image002[71]

 

clip_image002[73]

Save as your package to new folder

clip_image002[75]

 

Deploy Office 2010 with App-v

Add your App-V package

clip_image002[81]

 

clip_image002[83]

Setup connection group and grant domain users group permission to connect

image

 

Setup Package access permission with domain users

 

image

 

image

Log on Publishing port to test

If it is empty like below, then it’s time to run IISRESET on app-v server.

clip_image002[85]

 

check again

clip_image002[87]

 

Deploy on VDI client

This is VM2 which needs to install all “other tools” list above.

App-v client must be installed on this template machine which will be used to deploy VDI.

There are two typies of Client. with RDS and without RDS. With RDS version is used in Session Host. In this case, we use without RDS version.

clip_image002[89]

clip_image002[91]

 

clip_image002[93]

 

image

clip_image002[99]

You also need to run Set-AppvClientconfiguration –EnablePackageScripts 1

 

image

 

Wait for 5 mins, Office applications should be push down to this client

clip_image002[101]

 

clip_image002[103]

Prepare VM for VDI

 

clip_image002[105]

 

Once you create new pool and deploy VM as VDI, the Office 2010 will just work. Winking smile

 

Please leave any feedback.

 

 

Reference:

How to sequence Microsoft Office 2010 in Microsoft Application Virtualization 5.0 using a Package Accelerator

Advertisements

2 Comments

  1. Everything is very open with a clear description of the issues.

    It was really informative. Your website is extremely helpful.

    Thank you for sharing!

  2. Really useful thanks.

    Any chance you have any tips for getting Visio 2010 to work?


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: