Re: Policy's to tight maybe?

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

From: Keith Holt (kholt_at_crminc.com)
Date: 07/28/04


Date: Wed, 28 Jul 2004 15:22:42 -0400

I handled this by creating a security group on the server and putting all my
users who I want to be able to install software, or right to their local
drives for any reason, into it. Then I went to each workstation and added
that group to the local admin group. This has made life much easier because
now if I want to restrict a user from doing something on the local PC, I
just remove them from the security group and they can't do it. Plus when I
setup a new workstation I add this group by default.

Keith

"Chris Jones" <cka691@alltel.net> wrote in message
news:%23BN05MJdEHA.4004@TK2MSFTNGP10.phx.gbl...
> You can setup local Administrative users for workstations, this will not
> compromise the server, just the workstation.
> "Marina Roos [SBS-MVP]" <marina@roos.nodontwantspam.nl.com> wrote in
> message
> news:eT6uAPIdEHA.1000@TK2MSFTNGP12.phx.gbl...
>> Hi John,
>>
>> To be able to install software on W2k or XP, you need the user to be a
>> member of the local Administrators group on the workstation. After the
>> install, you can take them out if you want.
>> The local administrator doesn't give the user domain admin rights.
>>
>> --
>> Regards,
>>
>> Marina
>> Microsoft SBS-MVP
>>
>> "John D" <anonymous@discussions.microsoft.com> schreef in bericht
>> news:572901c4746c$6e0a1120$a601280a@phx.gbl...
>> > No, why would I want to? Sorry but you've lost me as to
>> > why and how I would do that globally for all users.
>> >
>> > >-----Original Message-----
>> > >Hello. Have you setup your users with Admin rights to
>> > >their individual machines?
>> > >
>> > >Scott
>> > >>-----Original Message-----
>> > >>Hello, I have a number of issues with all the XP
>> > machies
>> > >>on my SBS 2003 network and I beleive its something in
>> > >>policys thats doing it. Basically users can't write to
>> > >>there system drives on there desktop PC's.
>> > >>
>> > >>For example when Office 2003 is installed by an
>> > >>administrator it and is licenced then the administrator
>> > >>logs of and a new users logs on. When they go into Word
>> > >>or Excel etc it flashes up with the Accept, Decline
>> > >>licence screen everytime. This keeps happening untill
>> > an
>> > >>administrator logs on and goes into Word or Excel, then
>> > >>it stops happening! I figure that the administrator has
>> > >>rights to make changes to the registy/system drive and
>> > >>thats why it happens. I also have a number of other
>> > >>similar thing that happens. Can anyone help, is this
>> > >>because my policys are to tight?
>> > >>
>> > >>Thanks
>> > >>.
>> > >>
>> > >.
>> > >
>>
>>
>
>



Relevant Pages

  • Re: User unable to install software
    ... Are you talking about users installing software on the server or on ... Is showing as being a member of the administrators group on the ... Effectively this gives the user all capabiliites to the workstation ... however one user can install software and the other can't and I ...
    (microsoft.public.windows.server.sbs)
  • Re: Policys to tight maybe?
    ... > Hi John, ... > To be able to install software on W2k or XP, you need the user to be a ... > member of the local Administrators group on the workstation. ...
    (microsoft.public.windows.server.sbs)
  • Re: File Sharing not working
    ... It would not be a pemission problem. ... unc to see if you can connect from a workstation using the the servers ip ... > shared needed to install software and I can not see the ... If I go to another server I ...
    (microsoft.public.win2000.security)
  • Re: File Sharing not working
    ... How do I fix it ... >unc to see if you can connect from a workstation using ... >> shared needed to install software and I can not see the ... If I go to another server I ...
    (microsoft.public.win2000.security)
  • Re: Cant Administer a Workstation, did I break permissions?
    ... check to see if the workstation is still a member of the domain, ... having someone install software and not have a record of what was ... > We've set up SBS2k3 and one workstation. ... > the server where we are still logged in as administrator. ...
    (microsoft.public.windows.server.sbs)