Re: Windows Server 2003 Auto connect printers;
- From: "paul" <paul@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 11 May 2005 15:20:02 -0700
The Domain Users group is a member of the build in Users, that's it.
Yes the TS is a member server, Authenticated Users is added to the local
Admin group to give users local admin rights. We did this to solve some
software issues. Would this be related to our printer issue and how?
Where could I check again where we set the Permission Compatibility to??
Thanks for helping out, greatly appreciated.
Paul
"TP" wrote:
> Is the Domain Users group a member of any other group?
>
> I am assuming this is a member server. Double check all
> of the local groups like Administrators, etc., and make
> sure that there are no memberships giving users more rights like
> Everyone, Users, Authenticated Users, Remote Desktop
> Users, Interactive, etc., being a member.
>
> This should not impact printer visibility, but what do you
> have Permission Compatibility set to? Full Security or
> Relaxed Security?
>
> Thanks.
>
> -TP
>
> paul wrote:
> > Thanks TP,
> > The users that connect to the TS are only members of Domain Users and
> > no other rights at all. Still you can see all other users' printers
> > connected from their sessions with the computer name. Is there maybe
> > a TS configuration or is it somehow a premission issue.
> > Any idea's are welcome.
> >
> > Thanks!
> > Paul
> >
> >
>
>
>
.
- Follow-Ups:
- References:
- Prev by Date: RE: ADOX Automation error 2k3 TS w/SP1
- Next by Date: Re: Windows 2003 Licensing Server Won't Issue CALs
- Previous by thread: Re: Windows Server 2003 Auto connect printers;
- Next by thread: Re: Windows Server 2003 Auto connect printers;
- Index(es):
Relevant Pages
|
