Software Deployment to Machines

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

anonymous_at_discussions.microsoft.com
Date: 05/26/04


Date: Wed, 26 May 2004 04:44:05 -0700

Have you given the workstations read permissions on the
share?
I've got Office installing on boot up on the workstations
and without giving the workstations read access it will
fail

Ollie

>-----Original Message-----
>Let me start out by saying this worked under W2K server.
>I'm trying to deploy Office to a select number of
>computers running XP/W2K Wkstn/2003 Server. Following
the
>best practices protocol:
>I created a global security group in the computers
>container and placed the above mentioned machines into
the
>list of members.
>I created a domain local security group and made the
above
>mentioned global group a member of.
>I created a shared directory to place the MSI package
into
>and set the permisions on the share to read only for
>authenticated users nothing was denied.
>I went into gpmc and created a new GP and edited it from
>there.
>Under computer configuration-software setting I created a
>new package which I selected as advanced assigned. This
>was done so that I could apply a MST under the
>modifications tab.
>Back in gpmc I removed the authenticated users from the
>security filtering area and added the domain local
>security group I created above.
>I then linked the GP at the domain level.
>I then ran gpupdate /force on the same server that all of
>the other tasks above was run on and if everything was
>going to function correctly I would be greeted with a
>prompt that says a re-boot would be required in order to
>install the software. That was not the case.
>Obviously I missed something but I don't see where.
After
>reading several posts I was asking myself that maybe the
>permissions on the share should be set to everyone read
>because when the computer side GP is applied the machine
>doesn't have an authenticated user attached to it. I
have
>tried numerous combinations over the past week and have
>not gotten the modeling section to agree with what
>actually happens on the client.
>.
>



Relevant Pages

  • RE: AD Migration broke CA web enrollment
    ... Server 2003 SP1 introduces enhanced default security settings for the DCOM ... Activation permissions. ... Determine if the CERTSVC_DCOM_ACCESS Local Security group has been ... the domain that hosts the Certification Authority. ...
    (microsoft.public.windows.server.migration)
  • Re: granting folder access to network users
    ... It is really easier to work with groups for configuring permissions ... account is used for example form the windows installer when new software ... Please post the complete share permissions and the folder NTFS permissions, ... In AD create a security group and add the user to this group. ...
    (microsoft.public.windows.server.setup)
  • Re: Cant assign calendar permissions to a group
    ... to be able to use a security group so that I can manage membership of ... By testing I have verified that a resource calendar's permissions can ... integral concept within Active Directory. ... Only individual users can be granted membership. ...
    (microsoft.public.exchange.admin)
  • Re: Unlock acct permissions
    ... >>>>-->>Joe Richards Microsoft MVP Windows Server Directory Services>>www.joeware.net>> ... I'm just trying to give a user>>>account unlock permission for an OU by making them a member of a security>>>group in that OU with permission to unloack accounts. ... Every one will have to full admins unless I can make>>>this Windows permissions work as desired. ... The correct permissions are on the security group, the user I>>>>>added to the security group still cannot do anything with account unlock or>>>>>password reset. ...
    (microsoft.public.win2000.active_directory)
  • Re: how to restrict users to search in their own Organizational Unit
    ... will be given the necessary permissions. ... Who would you DENY? ... decided a script can make it possible to accomplish, ... If I need to create a security group per OU and then add all users ...
    (microsoft.public.windows.server.active_directory)