Deploying MSOffice2003 to Win2000 clients from SBS2000

  • Thread starter Thread starter Plastic Man
  • Start date Start date
P

Plastic Man

Logging onto clients doesn't launch the Office installation like I've
specified using "Add Software to Computer" with SBS2000.

Office is installed in a shared folder and was installed with the
Adminstrative option.

Any hints?
 
Plastic Man,

You have given very little information.

Did you set up a Group Policy for the deployment of Office 2003? Did you
set it up for the Computer Configuration side of things or for the User
Configuration side of things? Did you Publish it or did you Assign it? To
which OU did you link that GPO? If you did this to the Computer
Configuration side of things, are the computer account objects directly
reside in the OU to which you linked this GPO? Did you assign this? GPOs
can not published to the Computer Configuration side of things. If you did
this to the User Configuration side of things, are the user account objects
directly reside in the OU to which you linked this GPO? Did you assign or
publish? When you told AD about the .msi file did you use the UNC format
( \\servername\sharename\file.msi ) or did you use a mapped network drive?
You must use the UNC format. What errors are you getting in the client
computers? To what DNS Server(s) do your clients point? They must point
ONLY to your internal DNS Server(s)!

HTH,

Cary
 
Cary,

I was hoping that SBS2000's "Define Client Applications" (Client Setup
Extensibility) would roll out Office simply. With Microsoft, even something
that appear's simple...is not.

After an application is set up using Define Client Applications I chose "Add
Software to Computer" from the Small Biz Server Admin Console. The option to
do this is Computer-specific, not User. Small Biz lied to me and told me
that the next time a user logged on to that computer, the installation
program would run.

I will investigate your advice and will, in the future, refrain from
assuming anything can be done simply. Arrggh.

Plastic Man
 
PlasticMan,

Not sure about the Define Client Applications in SBS2000. I have never used
that - but then in SBS2000 I typically do not use the wizards! Maybe that
is my mistake? Don't know.

Anyway, deploying software via GPO is a very easy thing to do. There are
several things that need to be in order before this will work and, like with
everything else, there are several things that can go wrong. This is where
you need to have a bit of knowledge ( be it simply understanding the
technology/technologies involved or knowing how to find things on Google /
MSKB ).

If an application is deployed to the computer configuration then it ( that
software application ) will not be deployed until the computer is rebooted
( assuming that a few other things have happened by that time ).

I would continue under the premise that things can be done simply. I do a
lot of things without any hitches all the time!

Cary
 
Back
Top