Re: Deploying an msi application via group policy

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

No problem. I don't know how I got that backwards! Back to the books for
me it seems. Sorry bout that Mikal

--
Adam Drayer


"Cary Shultz [A.D. MVP]" <cwshultz@xxxxxxxx> wrote in message
news:O8Rv6ZrdFHA.220@xxxxxxxxxxxxxxxxxxxxxxx
> Adam,
>
> I would like to respectfully disagree with what you have written....well,
in
> part.
>
> You can indeed publish and assign GPOs to user account objects while you
can
> O*N*L*Y assign GPOs to computer account objects. When you assign the
> application via GPO to the user account side then it will be automagically
> installed ( assuming that everything is in place ) when the user logs on.
> When you assign the application via GPO to the computer account side then
it
> will be automagically installed when the computer reboots. However, when
> you publish the application via GPO to the user side ( NOTE: this is not
> available to the computer side ) then the application will appear in the
> Add/Remove Software and will only be installed once the user goes there
and
> selects it.
>
> So, the original poster can keep the software GPO on the user side and
> either assign it or publish it. Were the original poster to move it to
the
> computer side then he would have but one choice - to assign it.
>
> --
> Cary W. Shultz
> Roanoke, VA 24012
> Microsoft Active Directory MVP
>
> http://www.activedirectory-win2000.com
> http://www.grouppolicy-win2000.com
>
>
>
> "Adam Drayer" <spam@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:%23pKoWumdFHA.3040@xxxxxxxxxxxxxxxxxxxxxxx
> > If you publish the MSI, it will just sit in add/remove programs waiting
> > for
> > the user to install it. You need to assign it. You can, however, only
> > assign MSIs to computer accounts, not to user accounts. Therefore, if
you
> > wish for the program to install itself on startup, you'll need to move
the
> > GPO to an OU that contains the computer accounts, not the user accounts.
> >
> > --
> > Hope I've helped some!
> > Adam Drayer
> >
> > "Mikal" <Mikal@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > news:3CFF4953-FFAC-4349-8C5C-5A8E3322279A@xxxxxxxxxxxxxxxx
> >> Hi Cary thanks for your reply
> >> I should have been a bit more clearer - i am appling the group policy
to
> > OU
> >> containers in Active Directory - im am pushing out a logon script to
> >> users
> > to
> >> install the msi, the OS is win2k - I am using a login script to push
the
> > msi
> >> on win2k machines as if I use group policy it just sits in add/remove
> >> programs
> >>
> >> as trouble shooting I have made sure there anre any local policies
> > affecting
> >> installation and have made sure that the msi works (which it does under
> > admin
> >> account) I have run the script (batch file) from the command prompt and
> > that
> >> works fine
> >>
> >> I also tried assigning the policy to a machine but this failed too, i'm
> >> assuming it failed as it was unable to get a network connection. hence
> > find
> >> the path of the msi
> >>
> >>
> >>
> >> "Cary Shultz [A.D. MVP]" wrote:
> >>
> >> > Mikal,
> >> >
> >> > You do not deploy applications via GPO to groups. This is your first
> >> > problem! You deploy applications either to user account objects or
to
> >> > computer account objects which directly reside in the OU ( assuming
> >> > that
> > we
> >> > are talking about this level; it is possible that we are talking
about
> >> > another level...possibly the Site level? ) to which the GPO has been
> > linked.
> >> >
> >> > You have to make sure that the user account objects ( or computer
> > account
> >> > objects, but since you are trying to deploy this to user account
> >> > objects.... ) have both the Share and NTFS permissions to the shared
> > folder
> >> > in which the .msi file is located.
> >> >
> >> > You have to make sure that you tell Active Directory where the .msi
> >> > file
> > is
> >> > via the UNC method ( \\servername\sharename\file.msi ) and not via a
> > mapped
> >> > network drive ( n:\someserver\somefolder\file.msi ).
> >> >
> >> > Now, in reference to my first point: it is possible that you are
using
> >> > Security Group Filtering. This is - on the Security tab of the GPO
> > itself -
> >> > where you would remove the group 'Authenticated Users' from the
> >> > security
> > and
> >> > add your own security group. If you have done this you need to make
> > sure
> >> > that this group has both the READ and APPLY GROUP POLICY rights.
> >> >
> >> > What troubleshooting have you done? What would the OS on the clients
> > be?
> >> >
> >> > Also, you need to make sure that your clients are pointing O*N*L*Y to
> > your
> >> > internal DNS Servers ( and not to any external DNS Servers - such as
> > your
> >> > ISP's ) in their TCP/IP configuration settings.
> >> >
> >> > --
> >> > Cary W. Shultz
> >> > Roanoke, VA 24012
> >> > Microsoft Active Directory MVP
> >> >
> >> > http://www.activedirectory-win2000.com
> >> > http://www.grouppolicy-win2000.com
> >> >
> >> >
> >> >
> >> > "Mikal" <Mikal@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> > news:3EB7FCEF-CC35-44E1-8C46-71B6FF9AF1E5@xxxxxxxxxxxxxxxx
> >> > > Hi
> >> > > I am trying to deploy an msi application via group policy to a user
> > group,
> >> > > but it doesnt seem to be working. The users dont have any rights to
> > the
> >> > > local
> >> > > machine, do they need to be administrators in order for the
> > application to
> >> > > install?
> >> > > any help would be great.
> >> > >
> >> > > ta
> >> >
> >> >
> >> >
> >
> >
>
>


.

Relevant Pages

  • Computer assigned software packages fail
    ... using a GPO set on an OU that I have my computer accounts in. ... When the computer first start I see it attempt to install but ... 102 The install of application Symantec AntiVirus from policy MIK_WS_POLICY failed. ...
    (microsoft.public.windows.group_policy)
  • Computer assigned software packages fail to install
    ... using a GPO set on an OU that I have my computer accounts in. ... When the computer first start I see it attempt to install but ... 301 The assignment of application Symantec AntiVirus from policy ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: GPO Software Distribution and two users
    ... > another user who does not have such a GPO assignment. ... >> applied at start up and then any GPOs that apply to the user account ... At the next computer reboot anyone and everyone who logs on to ... >> chosen to install Office XP to the user configuration side and you are ...
    (microsoft.public.windows.server.active_directory)
  • Re: Help with configuration
    ... from the User GPO. ... then you don't have to redirect it again in the TS GPO. ... MCSE, CCEA, Microsoft MVP - Terminal Server ... domain account profile is blank, ...
    (microsoft.public.windows.terminal_services)
  • Re: Advanced Client install nightmare
    ... I can successfully install manually using the SMS account. ... MS Client Configuration Manager cannot install the Advanced Client to ...
    (microsoft.public.sms.admin)