Office 2010 deployment

anything I don't mind · 4 Jul 2012 at 10:41

I have tasked with rolling out office 2010 to 100 users. I have found the Microsoft document that is 475 pages that is specifically written for deployment in enterprise environments. I was wondering if anyone else has done it yet and has any tips or helpful hints that might save me a head ache.

How did you roll it out, what method?

What problems did you encounter, if any?

Where I am doing this there is no software deployment software, so i have to do it with scripts and group policy etc. I also have to integrate it with a document manage system and templates and other software. So it is quite a big project.

Deleted member 77746 · 4 Jul 2012 at 10:50

We used SCCM + MDT 2012 to roll it out to 6000 users.

InertProtocol · 4 Jul 2012 at 10:50

Maybe this will help? http://technet.microsoft.com/en-us/library/ee656739.aspx

anything I don't mind · 4 Jul 2012 at 11:18

Thanks for that link. Looks like it is going to be a bit of nightmare because our dms requires reinstallation after roll out. I might go as far as creating a new desktop image because it may be easier. Plus all the users have roaming profiles so it may be an option, although seems a bit extreme.

Mattitude · 4 Jul 2012 at 13:48

We upgraded both office and the OS from XP/2007 --> W7/2010 and we will be rolling out W8/2013 and that will be deployed using SCCM 2012 once we upgrade from 2007 SP3

Mattitude · 4 Jul 2012 at 13:50

Oh another thing we have configured recently and works a treat is App-V. We virtualise most things now for people im sure you could do the same for Office. We keep it local for reasons but if it works for you maybe that?

Little_Crow · 4 Jul 2012 at 15:01

We use Novell ZenWorks for our software deployment.
You don't need Netware or eDirectory and all that palaver, it'll happily integrate with AD, which is what we do.
It also does imaging, asset management, remote access.

Having to rollout a sizable application like office via login scripts and GPO's would fill me with dread.
Only real advice I can give, is to pre-stage the install files to the PC's if you can, and to push it out in small phases.

anything I don't mind · 4 Jul 2012 at 16:23

Turns out what I may end up doing is a semi automated installation from usb. As the users go in to word training some IT individuals, will just log in with a domain admin account that has been created specifically for the roll out and will be deleted afterwards. Then they run a script and follow some instructions reboot and run another script and then reboot it should be ready to go. I will still use the customized office installation and have to do some 2010 group policy for view settings and things like that. But all the settings moved over ok. I will have to update three different bits of software and templates as well as office. But they all updated ok on my test machine. Turns out it is not a nightmare after all and i don't foresee any problems with it, well at this point

I said i could do the network install and cache the install locally. But the network here is not so good so might be better and easier to just do the usb method.

SoundsGood · 4 Jul 2012 at 18:34

Here you go, everything you need to know in 1 page:
http://technet.microsoft.com/en-us/library/ff602181.aspx

I did this a couple of days ago and it works perfectly, you may need to add some more registry checks if some of your users already have different versions of 2010 installed.

Deleted member 77746 · 4 Jul 2012 at 19:14

groen said:
I said i could do the network install and cache the install locally. But the network here is not so good so might be better and easier to just do the usb method.

Time to get new kit then.