how can I deploy Office 2010 Professional Plus using SCCM 2007 - Part 2

[anyweb]

In part one of this guide, we prepared Office 2010 X86 by downloading the files required (including the OCT), and created our own MSP file. Now we will add that customised package to ConfigMgr.



Step 1. Create the Office 2010 Package

Note: Before starting this step, copy the c:\Office2010x86 folder we created in part one of this guide, to your application sources share on your SCCM server, eg:

\\WIN-CILZXI45G1Q\apps\office2010x86

Open your ConfigMgr console, and expand Computer Management, Software Distribution. Right click on Packages and choose New Package.



Fill in your package details on the wizard screen



point it to the data source on your network share



and click next through the wizard until you see the confirmation screen.

[anyweb]

Step 2. Create the Office 2010 Program.

 

Select our newly created package from above, expand it, right click on Programs and choose New Program

 

 

fill in your program details

 

 

enter your desired requirements, here you can limit the program availability to All Windows 7 X64 and All Windows 7 X86,

 

 

set the Environment to run Whether or not a user is logged on and make sure that 'allow users to' is NOT selected.

 

 

for the Advanced properties, set allow this program to be installed from the Install software task sequence without being advertised

 

 

and then click next through to the confirmation screen.

 

 

click Close.

[anyweb]

Step 3. Distribute to Distribution Points

 

We now need to copy our package to the distribution points serving our clients. Select our package, right click on distribution Points and select New Distribution Point.

 

 

click next at the welcome, then select your Distribution Points from the list (don't select any SMSPXE dps)

 

 

click close at the confirmation screen.

[anyweb]

Step 4. Advertise the Office 2010 Package

 

Ok you've nearly got everything in place, now you want to advertise the Package to a collection, if you havn't already done so create a collection called Office 2010.

 

Expand software distribution and select Advertisements, right click on advertisements and select new advertisement.

 

 

fill in the details

 

Name=Microsoft Office 2010 Professional Plus

Package=Microsoft Office 2010 Professional Plus X86 English

Program=Microsoft Office 2010 Professional Plus

Collection=Office 2010

 

 

We want the schedule to be optional, so leave it as it is

 

 

set the Distribution Point settings as follows

 

 

and click through to the confirmation screen

 

 

click close to finish.

[anyweb]

Test the Office 2010 Deployment

 

Now that we have the groundwork done, you'll want to test the package on some Windows 7 clients. To do so you could use direct membership to add those computers to the Office 2010 collection, or better yet, setup a query on the collection and use Active Directory Group Membership to do it for you.

 

But for the purpose of this guide, let's add a virtual machine (Windows 7) to our Office 2010 collection using direct membership.

 

right click on your Office 2010 collection and choose properties

 

 

click on the Membership Rules tab, then click on the new direct membership button

 

 

in the create direct membership wizard, use the drop down menus to select

 

Resource Class: System Resource

Attribute Name: Netbios Name

Value: Win7client01

 

input the values to match your computername you wish to test... in my case I used a virtual machine called win7client01

 

 

click next at collection limiting and on the Select resources screen, place a checkmark on the clients you want to add to the collection

 

 

click finish to exit the wizard.

 

On your Windows 7 client, monitor it until you see the New Program Notification prompt (or you can go into Configuration Manager Client, Actions tab and kick off the Machine Policy retrieval to speed things up).

 

The program becomes available in RAP.

 

 

Select it and click Run

 

due to our Advertisements distribution settings for the package, we are informed that the program must be downloaded before being run. This is the desired effect as we do not want it to start downloading and have users interupt the process midway by turning off. They can do so with this setting and it will resume the next time they start the computer.

 

 

click on Download and the program download begins

 

 

when the Program is fully downloaded you'll be informed that it is ready to run. Click on Run. At this point Office 2010 is being installed in the background silently unless of course you are having a problem, in which case you should check the following folder on the client.

 

C:\Windows\Temp

 

Look for the setupexe log and check it to determine if there are any failure messages.

 

All things should go well however and Office 2010 will be installed !

 

 

 

 

 

Further reading:-

 

Technet: Troubleshooting a Configuration Manager 2007 Installation of Office 2010

[scumi]

Great Guide, will there be a Guide for seperate LPs also, or can it be considered the same as witht the office 2007 language packs?

[Kevin79]

Edit: Wrong thread...

[Kevin79]

Is there a specific reason to using New "Package" instead of New "Package from Definition"?

[Teriyaki]

Great Guide ! Many thanks

[michl]

Hi,

first of all thank you for this great guide.

But i have a few questions and i hope you could help me.

1. We want to install office 2010 without any user promts but with a progressbar, because the user should recognize that Office is intalling / updating at the moment. I am using OCT like you do it in your guide just changing display level to basic and i checked supress modal dialogs and no cancel. But Office is allways installed completly silent. Do you have any idea?

 

2. After Office is installed it is not activated. I am using MAK with a valid Office Key. In OCT i add AUTO_ACTIVATION 1 (dont know the exact syntax right now) but it has no effect.

 

Any suggestion is welcome.

[Peter van der Woude]

1. Did you by any change configure the Program to run Hidden?

2. Where does it has to activate? On the internet? If so, then probably the SYSTEM account (which is used by default for admin installs) doesn't have rights to go on the internet.

[stewcowie]

Hi there,

 

I have what may be a silly question I hope you can help with. You mention having to copy the config.xml file into the root off the Office source directory - even though we have customized with OCT (single transform in updates folder). Is there any editing of the config.xml file required in addition to the OCT config - e.g. by default my config.xml file says to use US language and MAK key - whereas I have OCT configured to use GB language and KMS.

 

In summary my question is once we have configured with OCT, what has to remain at minimum in the config.xml file to be copied to the Office source root and do things have to match up with OCT config?

 

Cheers,

 

Stewart

[lee1976]

hi Nice guide

 

I having lil issue here. My download stuck at 0% and not moving. any log i can look at?

[Peter van der Woude]

start with looking at the cas.log

[Zeus_at_Work]

I followed an almost identical walk-through for this process, prior to finding this one, from http://technet.microsoft.com/en-us/library/ff404178.aspx. I had completed the walk through on that link and it basically just seemed to do nohing. I tried several times and each time waiting for up to an hour to see if anything had changed on the test PC. (Checking to see if the installed Office 2007 was magically now Office 2010). Needless to say it did not work for me. I then did some more searching and found this walk-through which reads very much the same as the above link, with the exception being the portion regarding the config.xml file. So I started over ... created a second .msp using OCT, ... created all the neccessary SCCM components (half was already done since I had just done it on the previous walk-through). I stopped at that point to check what I needed to do with the config.xml and I am not clear. I opened the .xml file in notepad just to see what it contained, and it is generic, containing none of the info that was specified in the OCT/msp creation. So I guess I am confused.... is the xml file intended to be generic even after running through the OCT process? Is that the xml file SCCM requries? I would appreciate some more explanation around the xml file.... before I run off and try more tests hopefully.

 

Thanks in advance if anyone is still responding to this thread.

[lee1976]

Thank you. I got it working fix. My IIS was blocking .mdb

[Zeus_at_Work]

Hi there,

 

I have what may be a silly question I hope you can help with. You mention having to copy the config.xml file into the root off the Office source directory - even though we have customized with OCT (single transform in updates folder). Is there any editing of the config.xml file required in addition to the OCT config - e.g. by default my config.xml file says to use US language and MAK key - whereas I have OCT configured to use GB language and KMS.

 

In summary my question is once we have configured with OCT, what has to remain at minimum in the config.xml file to be copied to the Office source root and do things have to match up with OCT config?

 

Cheers,

 

Stewart

 

Did you ever get a reply anywhere from anyone? It seems we have the same question/issue.......

[Zeus_at_Work]

Well I have tried 20 variants of the above ..... nothing seems to work for me...... Office 2010 never appears in RAP (not sure if it even should with some of the specific attempts I've tried). I set it up.... leave the test machine alone for a couple hours and nothing ever happens..... nothing ever appears in RAP, nothing is ever installed, no errors are presented..... It just seems to sit there and blink like a dear in the headlights..... I am not sure where to go from here. I have started completely from scratch twice with the same result.... I have posted issues in here with no response..... I see others asking the same question, also getting no response....

[Peter van der Woude]

Did you take a look at the execmgr.log?

[SjefG]

Hi, I followed your tutorial, setup.exe is run on the client but it looks like it gets stuck right after starting.

The setupexe log file is only 4 kb and ends with this section:

Product: PROPLUSR

AddOnGroup Culture: nl-nl

AddOnId: WORD.NL-NL

AddOnId: OFFICE.NL-NL

...

...

AddOnId: POWERPOINT.NL-NL

 

I copied the config.xml to the root of the install dir (same as where setup.exe lives) but still the setup stalls somehow.

Could it be my office dvd, I used the x64 version from my technet subscription.

[dani3l]

i tried this but it doesn't work. The Client don't find the advertisment (even if i make the advertisment mandatory) but other advertisments like VLC or Adobe Reader works fine.

Do you have an idea?

[rackattack]

Will this tutorial work with SCCM 2012?

[Peter van der Woude]

It will work, but I would use the new application model in ConfigMgr 2012 and do something like this: http://blogs.technet.com/b/meamcs/archive/2012/05/08/deploy-office-2010-using-system-center-2012-configuration-manager.aspx

[andy_aus]

Guys,

Again great tutorial. I just got another doubt! I have created multiple msp files ( ex-Office 2010Std, Office 2010Pro & Office 2010ProPlus) and moved those to root folder. What is the commandline for adding specific msp according to user requirement? You mentioned that if we run setup.exe it will pick msp from update folder and can only place one msp in there.

 

Thanks again for your tutorial

[Peter33]

setup /adminfile "myadminfile.msp"

 

You can also refer to an additional configfile if you want to, by using the switch /config myconfig.xml