Re: Deploying SP 4 through Group Policy
From: Cary Shultz [A.D. MVP] (cwshultz_at_mvps.org)
Date: 05/28/04
- Next message: Troy Devin: "RE: Active directory problem"
- Previous message: Troy Devin: "RE: Loading Personal Settings"
- In reply to: anonymous_at_discussions.microsoft.com: "RE: Deploying SP 4 through Group Policy"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 28 May 2004 08:19:31 -0400
Mike,
Let's take this one step - by - step.
Let's start with the basics ( I am sure that you have tried all of this
already but let's go with this for a second ).
What happens if you log on to a particular WIN2000 system with a user
account that is a member of the Domain Admins group ( and thus a member of
the computer's local Administrators group ) and then navigate to the
update.msi file and double-click on it? Does it install completely? If it
does not, then there is either a problem with the file or there is some
networking issue going on. Can you copy the entire folder structure down to
the local PC and successfully run it then? If not, then I would suggest
that you replace that extracted version of SP4 and try with the new one.
Are you seeing any event ids on the computer accounts that indicate failure
of this deployment? Have you used any TS tools, like gpotools? If you
have, what is it telling you?
Let's assume that we have verified that you current SP4 extraction is not
corrupted and that there are no networking issues. How did you share the
folder that holds the directory structure for SP4? What Share and what NTFS
permissions have you applied? For a Service Pack I typically use
'Administrators' @ F/C and 'Domain Computers' @ Read. This has worked each
and every time I have done it. No need for any users to have any sort of
access to this directory.
So, that is hopefully clear. Now, all of the computer account objects that
you want to be affected by this GPO have been placed in an OU ( or a
sub-OU ). You are creating this GPO from scratch or are you linking an
existing GPO to this OU? If you are creating it from scratch, I an sure
that you are applying this to the computer configuration side of things ( I
know that you know this;-) ). Also, when you are telling AD about the
location of update.msi I am sure that you are using the UNC method and not a
mapped network drive. So, in the box you would have something like
\\servername\sharename\update.msi and not something like
S:\servername\sharename\somefolder\someotherfolder\update.msi. The mapped
network drive will never work.
Have you given everything about 15 minutes after creation of the GPO to
settle? Did you reboot several systems? What happened if you did? If
nothing happened then I would suggest that you reboot again. I have seen it
where nothing happens on the first reboot and if you give it a couple of
minutes more and then reboot you have your deployment of SP4.
And, finally, are all of your WIN2000 systems pointing to the correct
I*N*T*E*R*N*A*L DNS Server in their TCP/IP Configuration settings? Your
ISP's DNS Server information should be found in one place and one place
only - in the Forwarder's tab in your DNS MMC. But I am sure that you know
this as well!
HTH,
Cary
<anonymous@discussions.microsoft.com> wrote in message
news:1395a01c44400$56ea4920$a501280a@phx.gbl...
> I added my specific test computer account to the share and
> folder permissions as full control, and the package still
> did not install.
- Next message: Troy Devin: "RE: Active directory problem"
- Previous message: Troy Devin: "RE: Loading Personal Settings"
- In reply to: anonymous_at_discussions.microsoft.com: "RE: Deploying SP 4 through Group Policy"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
