Administrator but not Domain Admin
- From: "Robert Trebor" <rtrebor@xxxxxxxxxxxx>
- Date: Thu, 9 Jun 2005 21:31:45 -0400
I need to make a software vendor an administrator on a server
running SBS 2003. He demanded this access and the client caved in, so I'm
stuck. We don't want him to be a domain administrator if at all possible,
though, so he can't see another, new server on the network running a
competitor's software-- what's eventually going to replace his. Old Vendor's
software hasn't been fully retired yet and needs immediate maintenance.
Again, I'm stuck with the situation and have to make the best of it. I
started with explicit denys on the other server and unnecessary shares on
the SBS. I made Old Vendor an administrator, but I see that that gives him
the ability to make himself a Domain Admin-- which would let him change
permissions on the other server, among other things. What can I do to
prevent Old Vendor from giving himself Domain Admin privileges while still
allowing him to log on to the SBS? It doesn't have to be 100% bulletproof
but I would like to give some reasonable assurance to the client that Old
Vendor is limited to the SBS, where Old Software is installed.
.
- Follow-Ups:
- Re: Administrator but not Domain Admin
- From: Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
- Re: Administrator but not Domain Admin
- From: Matt Gibson
- Re: Administrator but not Domain Admin
- Prev by Date: Re: Terminal Services Shadowing
- Next by Date: Re: Disk Quota Information
- Previous by thread: Exchange's 16 GB store limit - any relief in sight?
- Next by thread: Re: Administrator but not Domain Admin
- Index(es):
Relevant Pages
|