Push out Office via AD/Group policy

[Steve Grosz]

Ok, I have gone through the process to install Office 2007 through
AD/Group Policy Management Console on machines in our domain.

With other applications we push out, if the application isn't installed,
it installs it. If it is installed, it doesn't do anything else.

It appears though that with the Office Enterprise 2007 that if it IS
installed, that it re installs Office 2007...

Is there a way to configure AD/GPMC to only install Office if it ISN'T
installed already?????

Thanks

 

[Peter Foldes]

Steve

Phone Support for Office Enterprise is free. See the below

Here you will find the Phone numbers and email addresses as to where and whom to
contact about Office Enterprise and your issue.
Scroll down to the bottom of page to North America
https://licensing.microsoft.com/eLicense/L1033/overview.asp

 

[Florian Frommherz [MVP]]

Howdie!

Is there a way to configure AD/GPMC to only install Office if it ISN'T
installed already?????

You need to use Group Policy startup scripts to do that. The Office team
found it would be good to change the setup routine (that worked
perfectly well with Office 2003 and GPSI) and disable unattended
installation/customized installations for Office 2007. Office 2010
doesn't look any better.

Your best bet is rolling out the MSI using a startup script and
providing an answer XML.

Cheers,
Florian
--
Microsoft MVP - Group Policy
eMail: prename [at] frickelsoft [dot] net.
blog: http://www.frickelsoft.net/blog.
ANY advice you get on the Newsgroups should be tested thoroughly in your
lab.

 

[Mark Heitbrink [MVP]]

Am 11.12.2009 07:42, schrieb Florian Frommherz [MVP]:

Your best bet is rolling out the MSI using a startup script and
providing an answer XML.

Even better:
using the setup.exe in Startup Script and MSP file in .\updates ;-)
because the MSP can be much more customized, than the XML but the
MSP can only be used with setup.exe not MSI :-(

Remember to integrate a "runonce" in Script like:
if not exist "%programfiles%\microsoft office" setup.exe ....

Mark

 

[Steve Grosz]

We don't actually HAVE startup scripts, all of our drives are mapped
though GP, printers are done the same......

 

[Mark Heitbrink [MVP]]

Am 11.12.2009 18:38, schrieb Steve Grosz:

We don't actually HAVE startup scripts,

You knoiw the difference between Startup Script and Login Script?

Startup = Computer
Login = User

You can not deploy office in a Login script, because it runs in the
user credentials and a "USER" ist not allowed to install software.
So it needs to be a computer startup script, which runs in SYSTEM
context.

Mark

 

[Robert Sudbury]

Another option to consider if you have a volume license, is to use the
Microsoft Office Customization Tool:

http://technet.microsoft.com/en-us/library/cc179097.aspx

Far more granular control than the .xml option.

Be sure to use the correct version for your service pack.

for an sp2 installation:
http://www.microsoft.com/downloads/...c0-da87-4bc2-bbf6-260e700519a8&displaylang=en

Am 11.12.2009 18:38, schrieb Steve Grosz:

You knoiw the difference between Startup Script and Login Script?

Startup = Computer
Login = User

You can not deploy office in a Login script, because it runs in the
user credentials and a "USER" ist not allowed to install software.
So it needs to be a computer startup script, which runs in SYSTEM
context.

Mark
--
Mark Heitbrink - MVP Windows Server - Group Policy

Homepage: www.gruppenrichtlinien.de - deutsch
Discuss : www.freelists.org/list/gpupdate

__________ Information from ESET NOD32 Antivirus, version of virus
signature database 4682 (20091212) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

--
[Robert]


__________ Information from ESET NOD32 Antivirus, version of virus signature database 4682 (20091212) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

 

[Mark Heitbrink [MVP]]

Hi,

Am 13.12.2009 00:40, schrieb Robert Sudbury:

Another option to consider if you have a volume license, is to use the
Microsoft Office Customization Tool:

The resulting MSP file can only deployed with the setup.exe
Thats the reason why you need to use the script instead of the
MSI installer and the GPSI.

Mark

 

[Steve Grosz]

I was actually pushing this out via the Computer (startup
script).....but I need it to determine if Office is already installed,
and if so, not install it again.........

 

[Mark Heitbrink [MVP]]

Am 14.12.2009 17:56, schrieb Steve Grosz:

...but I need it to determine if Office is already installed,
and if so, not install it again.........

if /i not exist "%programfiles%\microoft office"
\\server\share\office2007\setup.exe

Mark