Re: Weird Issue

Tech-Archive recommends: Fix windows errors by optimizing your registry

jabrandt_at_online.microsoft.com
Date: 10/21/04 

Date: Wed, 20 Oct 2004 19:45:19 -0500

Are you logged onto the client with local admin privelages?
Are you able to see any of the domain users?

Try this.
Logon to the client as a local admin.
Add your domain account, if possible admin, to the local admin group.
Log off.
Logon with your domain account you just added locally.

Try adding the groups you want again.
If this does not work please provide any error messages if you receive them 

-- 
James Brandt [MSFT]
"Nicolas Macarez" <macarez@free.fr> wrote in message 
news:eda2ZqutEHA.2184@TK2MSFTNGP12.phx.gbl...
> Hi !
>
> My issue is rather weird to define.
>
> My config is as follows :
>
> One Dell PowerEdge server with Win2K Server installed as a Domain
> Controller, DNS, DHCP server.
> A few workstations (Win2K Pro and WinNT 4.0 Workstation) have properly
> joined the domain called MYDOMAIN. All the machines are properly patched
> (Windows Update).
>
> Everything is fine except one thing.
>
> For some reasons, I want to give the end users all the local 
> administrative
> rights on any machine of the network. Usually, I do that by including the
> Domain Users group in the local Administrators group of each machine.
>
> This time, I just can't dothat: as soon as I try to browse the users and
> groups on the local machine and on the Domain (yes, it asks me my
> credentials as a Domain admin and I enter them properly, credentials as a
> member of the Domain Admin group), I am denied the access to the drop down
> list of the domain users and group ("insufficient privileges").
>
> The funny thing (weird) is that I can see the domain MYDOMAIN in the drop
> down list (if I select it, I get a grey part in the window indicating me
> that I have't got the sufficient privileges) as well a the name of the 
> local
> machine.
>
> For the Win2K Pro clients, the workaround is to include the local
> Authenticated Users group in the local Administrators group - and it's OK.
> Such a group doesn't exist on Win NT 4.0 Workstations, so I am in a dead
> end.
>
>
> Any idea ?
>
> Help greatly appreciated.
>
> Nicolas
>
>
>

Relevant Pages

  • RE: login to multiple computers
    ... the problems occur when domain users logon to a computer ... re-register the security client side extension: ... Explorer Maintenance Policy Processing" policy under Computer ...
    (microsoft.public.windows.server.sbs)
  • Re: Unable to logon thru Terminal Services
    ... Nat shouldn't matter, becasue you can logon with the administrator account, ... which mean you client side network setting is correct. ... > Domain Users ...
    (microsoft.public.windows.server.sbs)
  • RE: logon error: error occured while an inital user program was st
    ... I can also give you a place to log in on my TS server with your client to see ... Such as run this program at logon? ... and granted permissions on RDP for domain users and guest ...
    (microsoft.public.windows.terminal_services)
  • RE: logon error: error occured while an inital user program was st
    ... I can also give you a place to log in on my TS server with your client to see ... Such as run this program at logon? ... and granted permissions on RDP for domain users and guest ...
    (microsoft.public.windows.terminal_services)
  • Re: Unable to logon thru Terminal Services
    ... The user belongs to "Domain Users" which has right to ... services logon for this user in the client computer. ... >which mean you client side network setting is correct. ... >> Remote Desktop Users ...
    (microsoft.public.windows.server.sbs)