Re: Group Policy Deploy Questions
- From: "Anthony" <anthony.spam@xxxxxxxxxxxxxx>
- Date: Fri, 25 Aug 2006 15:22:05 +0100
The domain controller has a list with each policy and a GUID. The client has
a list of policies already processed. The client compares the two and
respond to anything new. By contrast, startup or login scripts do everything
on the list every time.
So you just create the policy with the software installation package, filter
it for the clients you want to install it on, and leave it until you want to
upgrade or remove the software,
Anthony
<biggskanz@xxxxxxxxx> wrote in message
news:1156511898.600030.48520@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi and thanks for the reply.
Ok so the group policy knows that it has been processed even after a
reboot? I'm asking cause my boss is telling me that it will try to
install the software everytime the computer reboots. His suggestion is
to just leave the group policy for about a week until we are sure every
computer has the service and then remove it.
Anthony wrote:
Quick rundown:
Group policy processing knows whether it has been processed or not.
That's
it. It can't check whether something else happened. It has either been
processed or not. So once a policy to assign software has been
successfully
processed, it is marked as done.
Windows installer packages have a self-repair facility. Every component
has
a key file. If the key file is missing when the component is run, a
Repair
is carried out.
Many packages are built with a per-computer installation and a per-user
installation. The per-user installation sets up any parameters that are
different for each user, such as preferences. Generally it runs this when
the user first fires up the application, by checking whether the per-user
components are there or not. If the package does not have per-user
settings,
there is nothing to run.
Software that runs as a service should be nice and simple to deploy. It
will
be installed when the policy is processed, running under the local system
account during startup.
Anthony
<biggskanz@xxxxxxxxx> wrote in message
news:1156458510.968342.175870@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have some questions on how Group Policy Deployment actually works.
When deploying software using the Assigning Software to Computer
method, does the GP attempt to install the software each and every time
the computer starts up untill the GP is disabled? Or does it somehow
check to see if its not installed before attempting an install.
Also in the KB article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;816102
Microsoft states: "If you assign the program to a computer, it is
installed when the computer starts, and it is available to all users
who log on to the computer. When a user first runs the program, the
installation is finalized."
How would this work if i'm deploying software that will be running as a
service?
Thanks for any insight.
Phil.
.
- Follow-Ups:
- Re: Group Policy Deploy Questions
- From: Biggs
- Re: Group Policy Deploy Questions
- References:
- Group Policy Deploy Questions
- From: biggskanz
- Re: Group Policy Deploy Questions
- From: Anthony
- Re: Group Policy Deploy Questions
- From: biggskanz
- Group Policy Deploy Questions
- Prev by Date: Re: Software RAID5 slow write speeds
- Next by Date: Re: Group Policy Deploy Questions
- Previous by thread: Re: Group Policy Deploy Questions
- Next by thread: Re: Group Policy Deploy Questions
- Index(es):
Relevant Pages
|
