[ms office - 2007] Office 2007 deployment - join the crusade

[ajbritton]

Want to let Microsoft know how dumb they are for breaking GPSI deployment in Office 2007? The GPO GUY suggests you leave a comment on a blog post by a member of the Office Resource Kit team. Come on folks, let's kick their butts.

 

The GPOGUY-- Group Policy Blog: Don't Like How they broke GP-based Deployment of Office 2007?

[SYNACK]

I am so there!! Their 'new' deployment method is junk and so is their new 'update' mechanism.

 

Edit: Posted concise but polite comment, now to see if it makes it through moderation.

Edited May 28, 2008 by SYNACK

[Michael]

In addition to this, slipstreaming for Office 2007 is different as well as the command switches too. One phrase comes to mind: "if it ain't broke, don't fix it".

[SYNACK]

In addition to this, slipstreaming for Office 2007 is different as well as the command switches too. One phrase comes to mind: "if it ain't broke, don't fix it".

 

Their new version of slipstreaming should not even qualify to be included under the same term. It does not actually replace the files in the installer so that the whole program is installed at once at the latest version. Instead it installs the base product at its original update level and then takes its time installing all of the update one by one over the top of the files that it has just installed.

 

A massive waste of power and time in my opinion.

[Michael]

Their new version of slipstreaming should not even qualify to be included under the same term. It does not actually replace the files in the installer so that the whole program is installed at once at the latest version. Instead it installs the base product at its original update level and then takes its time installing all of the update one by one over the top of the files that it has just installed.

 

A massive waste of power and time in my opinion.

 

I agree with you there. The MSP files are to be extracted into the \Updates folder. Office 2007 setup then picks up the new updates.

[Geoff]

Slightly derailing the thread perhaps, but for those of us not 'blessed' with Office 2k7, what exactly is different deployment wise from previous versions?

[Michael]

For your reference Geoff I have already created two guides. Office 2003 SP3 and Office 2007 SP1.

 

So the slipstreaming and patching process is different for starters, but I believe also Office 2007 doesn't use the standard MSI method, which I think is why this thread was started!

[SYNACK]

Slightly derailing the thread perhaps, but for those of us not 'blessed' with Office 2k7, what exactly is different deployment wise from previous versions?

 

With Office 2007 each application is split into its own MSI with one Enterprise MSI that is supposed to install the lot. Unfortunately the Enterprise MSI can only be run via the setup.exe or by group policy deployment which makes it irritating to test for one.

 

Next up you have the issue that the Enterprise MSI is unable to upgrade 2003, it will try, uninstalling office 2k3 and wasting 25min installing almost all of it before it fails and has to rollback and reinstall Office 2k3 again.

 

If you uninstall 2k3 first then their are still problems. MSTs are not supported and the only way to configure the Enterprise MSI is with an XML config file with rubbish documentation and no way to test it short of deployment. If you get this XML config slightly wrong it will waste 25min installing what it says is Office 2k7 but in actual fact is only the core components and the advertisement icons. Your first user to click on it then has to wait 10 minutes for it to install the rest.

 

Now we come to the 'improved' customization. You can make customization packages with a wizard which are packaged as MSTs which you just put in the updates folder.

 

Problem is the network install doen't pay any attention to the updates folder at all. Apparently you can script in a call to it in the XML file mentioned earlier but that little bit of it has not actually been implemented.

 

Being AD based GPO you may expect to be able to simply tell AD to apply a patch to the installer package but again this is unsupported.

 

Bottom line, the deployment options for GP are that broken that they are practically unusable unless you are willing to spend vast amounts of time tweaking the config file and leaving the updates up to WUS or running the actual setup.exe via a script.

 

The kicker is that the 'new' and 'improved' methods of deployment such as in image Vista deployment and their payed for SMS deployment still work and are recommended as an alternative to the free widely used method that Office 2k3 shipped with.

 

These faults are annoying enough without the so called slipstreaming method that they have brought out which I discussed earlier.

 

/rant

[RabbieBurns]

I rolled out 2007 in november and I thought the xml for the enterprise msi was fairly straight forward.

 

The problem with it being "installed" but then spending time "configuring" after a user logged on was a real pain.

 

I created a gpo to uninstall 2003, and then install 2007, but for some reason it didnt install Outlook 2007 doing it this way.

[RabbieBurns]

I rolled out 2007 in november and I thought the xml for the enterprise msi was fairly straight forward.

 

The problem with it being "installed" but then spending time "configuring" after a user logged on was a real pain.

 

I created a gpo to uninstall 2003, and then install 2007, but for some reason it didnt install Outlook 2007 doing it this way.

 

edit: I just let wsus take care of sp1 when it came out

 

edit 2: hmm first edit seems to have created a second post sorry

[contink]

This is the point where I thank my lucky stars that I purchased the 2003 media when we got new office licenses... I think I'll be steering clear of 2007 for a while.

[gshaw]

Yeah the GP deployment was a mess, we did it on our admin network and ended up with...

 

- some machines with 2007 installed OK

- some with bits of 2003 left (usually Outlook) the rest 2007

- some with 2003, 2007 not installed at all

- some with 2007 missing serial numbers, profile problems

 

In the end was having to do Office Installer cleanups to nuke 2003 then manual reinstalls of 2007, absolutely horrible! Since that I've abandoned GP software installs and use SMS for everything as I don't trust GP anymore

 

Our old method used to be a blank image with software rolled down via GP, now I put as much as possible on the image as the new Microsoft products seem to be all over the place. Can't understand why they're making so many simple, glaring errors with their new stuff... very poor show imo

[srochford]

I've tried to post a comment to the blog but it hasn't appeared - not sure if that's because it's moderated or the guy doesn't want any more grief :-)

 

I've never got the MSI to deploy with group policy. I've tried using a script but it's not easy to get it to work reliably.

 

I know the GPO MSI method doesn't scale for thousands of simultaneous deployments but there must be a good few people who only want to deploy to a few hundred (eg we use MSIs for all our staff machines; we rarely do more than a few of those at a time so it's easy and quick. Even if we want to upgrade the software on a machines we stagger the updates to 50 or so machines at a time)

 

If I were cynical I'd say this is Microsoft just trying to force us to buy deployment software :-)

[gshaw]

 

If I were cynical I'd say this is Microsoft just trying to force us to buy deployment software :-)

 

Well it just so happens that Microsoft recommend SMS 2003 \ SCCM as the supported deployment method... what a coincidence

 

Luckily we use it anyway and it's very cheap on Campus License

[contink]

If I were cynical I'd say this is Microsoft just trying to force us to buy deployment software :-)

I'd say your cynicism was bang on there.. It's going to backfire though when all the techs find themselves looking harder at Openoffice or just stay back with 2003.

[srochford]

I'd say your cynicism was bang on there.. It's going to backfire though when all the techs find themselves looking harder at Openoffice or just stay back with 2003.

 

The trouble is that people like us buy MS software on the Campus license so we've paid for Office 2007 whether we use it or not (same goes for Vista!)

 

This means that Microsoft get our money and don't really care if we don't like the software - we have to keep paying them even if we want to stay with Office 2003/Windows XP. There is a buyout option but it's not cheap and it's not easy (the beauty of the "rental" system is that you're licensed for every machine for all the software you add to the agreement - this makes it easy to make sure you have enough licenses but it also could be expensive!)

[gshaw]

Did anyone see the article in Computing magazine that if Microsoft don't resolve their differences with Becta schools will be going Open Source by 2012

[contink]

Not sure if this has been posted elsewhere but when it comes to sorting out the actual deployment of Office 2007 this little document is proving quite useful for many of the config.xml flags...

 

http://go.microsoft.com/fwlink/?LinkID=94264 ... pages 53 - 60

 

There's a few example config.xml files around as well but the one I was looking at has gone walkabout.. so I can't post a link...

 

Not looking forward to this though.. because staff here have had 2k7 on their laptops the pressure's there for it to be deployed for all..

[contink]

This is seriously starting to p*ss me off...

 

MS have so much conflicting ruddy information out there about this POS package that it makes no sense when you are actually "well informed".

 

I've been trying to get the SP1 to deploy with fresh Office 2007 installs and keep hitting problems. I suspect because I have a custom config.xml file which doubtless stops certain things working in the patching process and thus borks everything.. Wonderful!

 

Any intel on this though would be appreciated... I really don't want to put ALL of the cr*p on each machine when it's not used.

 

 

This proves particularly unhelpful when compared to the "accepted known approach" to deploying SP1

 

Use Group Policy Software Installation to deploy the 2007 Office system

 

Challenging to maintain, because updates must be applied to all client computers. This can be done by using a logon script or other delivery method. It is not possible to use the Updates folder to apply security updates or service packs for initial deployment of the Group Policy object (GPO).

 

This goes against EVERYTHING I've read elsewhere about slipstreaming for office 2007

Logistix IT Consultancy and Support Services

 

 

 

I'd love to say that WSUS would be the solution but when you consider that I have a wireless system here and limited capacity in terms of power sockets and physical space it's really something I'd prefer got rolled out immediately and not in 15 weeks time in the middle of a lesson.

[srochford]

One thing you could do is set the config.xml to do a cache of the local installation source but not install (). That will give you a whole set of files under c:\msocache\all users - you can then copy this whole folder tree to each machine. Once it's completely copied then you can run setup from there - this is basically what things like SMS do; I think they use BITS to "trickle" the files in so that you don't trash your network bandwidth but you do get it all cached eventually.

 

Once you start running setup, it's running from the c: drive and should run reasonably quickly. I've done basically this and it does use the MSP files in the updates folder.

[contink]

Thanks Steve, appreciate the suggestion... I think there's something else going on here though that's going to cause problems with the whole setup regardless.

[Psymon]

Think we might have cracked it partly.

 

Configure Config.xml to contain Product key, user, company etc...

Deploy complete suite via GPSI

use MSIEXEC.exe to install an MSP - AppDeploy > FAQs > How Do I Deploy A MSI Patch (MSP)?

Can use 2 instances one for 07 SP1, the other to install the MSP Customisation file

 

Anyone tried this? Were about to give it a go in the next week on a test network.

[Michael]

This goes against EVERYTHING I've read elsewhere about slipstreaming for office 2007

 

By the looks of things, deploying Office 2007 using GPOs won't pick up hotfixes or service packs within the \Updates folder, however if you run Setup.exe using a script then it should. Extracting MSP files into the \Updates folder is the only method. You cannot actually integrate updates as you could with Office 2003.

[srochford]

there are good and bad things about the new method.

 

With the office 2003 (and earlier) MSIs you did an admin install to the server, deployed to clients and all is well. A user then wants (say) equation editor and the workstation connects back to the server, picks up the new item and installs it - all is good :-)

 

You then download the service pack and update the admin install. You start installing new machines from this location - no problems.

 

Another user with machines from the first batch wants a new component. The MSI recognises it needs to go back to the server share but now it falls over - it doesn't recognise the files on the server because they are effectively a different install.

 

The only way round this is to force a redeploy from the original folder -that way all your machines get updated (real pain because it's slow and we have WSUS to push out updates). Alternatively, you create a new admin install point for SP1 and start deploying from there. You now have 2 install points and have to make sure that machines are picking up from the right one. If you have a standard group policy to push out packages and you update it ready for new machines it forces a re-deploy for the old ones.

 

Office 2007 gets round this; it copies everything to the local hard disc, MSPs and all, and installs it from there. If new updates come out you put them on your server share; new machines will get them, older machines get updated through WSUS and all is well.

 

It does have to do more work for the initial install (every machine has to do the patching rather than just the one admin install) but it's probably faster (running the process from local hard drive rather than over a network)

 

I still don't like it :-(

[pmassingham]

Did anyone see the article in Computing magazine that if Microsoft don't resolve their differences with Becta schools will be going Open Source by 2012

 

This is my excuse for not installing it.