Deploying Office XP via GP

  • Thread starter Thread starter BJB
  • Start date Start date
B

BJB

Hi,

I'm having a little trouble deploying Office XP via group policy.

I have setup a test group policy that is assigning office xp to 2 test
computers. When I reboot the PCs, the installation starts with message
'installing managed software office xp...' but then seems to fail. When I
look at the event log it says during the installation H:\ drive is
specified, which is an invalid drive.
The H:\ drive is specified as the default document location in an MST
modification file, that I have applied to the software policy, because we
use the H:\ drive a users home drives, however they are not mapped until
after the user has logged on, and as the install is done before you get the
logon screen the drive is never mapped.

Is there a way to install office xp, and set the default drive, even though
they are not mapped, with out the install failing?

Cheers

bjb
 
Brian Desmond said:
Hi there,

Can you check out this writeup on rolling out Office via GP and see if it
helps?

http://briandesmond.com/blog/archive/2003/10/25/233.aspx

--
--
Brian Desmond
Windows Server MVP
(e-mail address removed)12.il.us

Http://www.briandesmond.com
Click to expand...

Brian,

That's a great artical, very easy to follow.

I've pretty much done most of what it says, my current problem revolves
around the 'Custom Installation Wizard' right at the end you can set program
defaults, I would like to set H: as default file locations, and T: as
workgroup templates. However because I'm assigning this software to a PC,
its installed as the machine boots up, before users logon. Its only after
users logon that they get the H: & T: drives mapped, which seems to be why
my office instalation is failing. Looking at the event log I get the 2
errors below.
If I remove the office customisation, it installs without problems, however
this means having to go in and set the H: & T: drive manually.

I was thinking last night, would it be possible to assign the base office
install to the PCs, so it installs on them, then add a published
install/modification to users, so its applied after they logon?

Cheers

bjb

-------------------------------------------------------
Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 11327
Date: 02/11/2004
Time: 14:34:36
User: N/A
Computer: TESTPC2-2K
Description:
Product: Microsoft Office XP Professional with FrontPage -- Error 1327.
Invalid Drive: H:\
-------------------------------------------------------
Event Type: Error
Event Source: Application Management
Event Category: None
Event ID: 102
Date: 02/11/2004
Time: 14:34:36
User: NT AUTHORITY\SYSTEM
Computer: TESTPC2-2K
Description:
The install of application Microsoft Office XP Professional with FrontPage
from policy Test Group Policy failed. The error was Fatal error during
installation. .
-------------------------------------------------------
 
BJB,

I think that you need to use the UNC method - as listed in Brian's
article - and *N * O *T a mapped network drive when telling AD where the
..msi file is located. So, you would use \\servername\sharename\file.msi
instead of h:\somefolder\sharename\somefolder\file.msi. As a matter of
fact, I use the UNC when doing the Administrative Installation as
well.....not that this necessarily applies to your issue.

Now, if you are trying to have the default save location for each
application ( MS Word, MS Excel, etc. ) changed from c:\documents and
settings\%username%\my documents to the h:\ or the t:\ drive then you might
want to try using the .adm files for Office 2000 / Office XP / Office 2003.
These are really awesome tools that will allow you to make a whole slew of
settings that you would otherwise have to do on each and every machine ( and
manual work is no fun! ). These .adm files are available from the Resource
Kit from each respective version. They are really really useful!

HTH,

Cary
 
Cary Shultz said:
BJB,

I think that you need to use the UNC method - as listed in Brian's
article - and *N * O *T a mapped network drive when telling AD where the
.msi file is located. So, you would use \\servername\sharename\file.msi
instead of h:\somefolder\sharename\somefolder\file.msi. As a matter of
fact, I use the UNC when doing the Administrative Installation as
well.....not that this necessarily applies to your issue.

Now, if you are trying to have the default save location for each
application ( MS Word, MS Excel, etc. ) changed from c:\documents and
settings\%username%\my documents to the h:\ or the t:\ drive then you might
want to try using the .adm files for Office 2000 / Office XP / Office 2003.
These are really awesome tools that will allow you to make a whole slew of
settings that you would otherwise have to do on each and every machine ( and
manual work is no fun! ). These .adm files are available from the Resource
Kit from each respective version. They are really really useful!

HTH,

Cary
Click to expand...

Hi Cary,

I have been using the UNC paths to the msi files for the install
(\\server\software\officexp\PROPLUS.MSI) I always try to use UNC where
possible.

As you said, its the default save locations & templates. I am currently
looking at the .adm files you mentioned. I take its just a simple case of
opening GP and right clicking add/remove template and then importing these
adm files?

bjb
 
BJB,

That would be correct!

Cary

BJB said:
Hi Cary,

I have been using the UNC paths to the msi files for the install
(\\server\software\officexp\PROPLUS.MSI) I always try to use UNC where
possible.

As you said, its the default save locations & templates. I am currently
looking at the .adm files you mentioned. I take its just a simple case of
opening GP and right clicking add/remove template and then importing these
adm files?

bjb
Click to expand...
 
Cary,

Hats off to MS on these adm files, it makes applying settings so much
easier, and the way it all ties in with GP & AD is great!

I'm looking at creating custom ADM files (kb323639). We use VNC here for
remote admin, and it would be really cool if I could create an admin
template for all the settings that have to be setup, i.e. password, which
IPs to accept as hosts etc.

Looks a little complex though, shame there isn't a GUI tool for it!

Anyway, thanks for the help!

Cheers

bjb
 
BJB,

You are welcome.

Cary

PS...I remember someone named Ben Blackmoore who used to spend a lot of time
in the AD and GPO newsgroups. If you are that person, nice to see you back!
 
Cary,

Yip, that was me, changed my handle cause I didn't think it was a good idea
to post with my full name.

It's good to be back, nice someone remembers me :-) Been off doing my MCSE
training, and deploying other aspects of AD (DFS & RIS)

bjb (ben)
 
Back
Top