software deployment issues

[corey]

I cant seem to get the software to deploy to any of my
client computers or users. I have created a test OU and
put users in there and a sub OU under that with 2
computers in there.

I have created a network share with the application I wish
to be pushed out in it. I have tried several different
permissions but am now set on domain computers and domain
users as having full access.

I have setup a GPO in the test OU (named Office XP push)
and edited to GPO's software settings to point to my
network share folder.

Now I save and exit out of AD. I restart one of the test
machines and log in as one of the test users and I get
nothing. I have tried quite a few variations of the above
and have searched for everything I can find on AD software
deployment. I have to be missing one crucial step is all I
can think of. Any ideas, links, voodoo tricks....would be
appreciated.

 

[Cary Shultz [A.D. MVP]]

Corey,

There are a slew of possibilities here.

Let's take a look at the more obvious ones first.

1a) DNS - Are your clients receiving their IP Address lease from a DHCP
Server? If they are, are they also getting the 'Options' from the DHCP
Server ( typically Options 003, 006 and 015 and possibly Options 044 and 046
if you are running WINS )? If you are handing them static IP Addresses ( if
you are, consider using DHCP ) did you give them the correct DNS Server
information?

1b) DNS - are your clients pointing to the correct DNS Servers? In WIN2000
AD and WIN2003 AD all of your clients ( workstations, Member Servers, Domain
Controllers ) * M * U * S * T * point to an internal DNS server that
supports SRV records and Dynamic DNS. This does not include your ISP DNS
Servers. The only place for that information is in the DNS MMC in your
Forwarders tab.

2) Installation Point - did you create an administrative installation of
Office XP on a Networked Server? There have to be both NTFS as well as
Share Permissions set on that shared folder. Typically, I give Domain Admin
or Administrators Full Control on both and then Domain Users / Domain
Computers only READ access on both. This is all they need.

3) Creating the Package - when you told AD where the .msi file for Office XP
is did you use a UNC path ( such as \\server\share\file.msi ) or did you use
a mapped network drive ( such as f:\apps\officeXP\file.msi )? If you used
the mapped network drive the deployment of Office XP will fail. You must
use the UNC path for all application deployments through GPOs.

4) Event Logs - are there any on either the client or on the Server? Have
you looked at any of the GPO Troubleshooting guidelines? You might want to.

HTH,

Cary