Windows 2000 - Read only access for developers.

  • Thread starter Thread starter news.easynews.com
  • Start date Start date
N

news.easynews.com

Hi guys, hope someone can find a few minutes to offer some advice.

Is it possible to give a user with logon access to a Windows 2000 server but
with
only 'read-only' permissions? The development teams need to view the
systems
but are not allow to change them directly.

If a logon isn't possible i'll have to look at building on top of the
default access
granted to a normal user remotely (like the event logs and COM+ out of the
box).

Many thx
Oli
 
The easiest and best solution is to give them a development test box.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Hi guys, hope someone can find a few minutes to offer some advice.
|
| Is it possible to give a user with logon access to a Windows 2000 server
but
| with
| only 'read-only' permissions? The development teams need to view the
| systems
| but are not allow to change them directly.
|
| If a logon isn't possible i'll have to look at building on top of the
| default access
| granted to a normal user remotely (like the event logs and COM+ out of the
| box).
|
| Many thx
| Oli
|
|
|
|
|
|
|
 
Cheers Dave,

Problem is they alreayd have 130 test server, 15 staging servers, 18 servers
creating a support environment and 45 live servers.

Don't mean to be cheeky. ;-)

The problem at that scale is that you need a bullet proof source and
deployment control system to keep everything exactly in parellel. The
department hasn't invested in such a system so problems start occuring
exclusively in systems. Its a real pain.
 
Depends a lot on what they need read-only access to. Most items they might
need to see would typically have access denied from say the guest account.
You'd probably need to make some major policy changes to your production
servers in order to effect this.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Cheers Dave,
|
| Problem is they alreayd have 130 test server, 15 staging servers, 18
servers
| creating a support environment and 45 live servers.
|
| Don't mean to be cheeky. ;-)
|
| The problem at that scale is that you need a bullet proof source and
| deployment control system to keep everything exactly in parellel. The
| department hasn't invested in such a system so problems start occuring
| exclusively in systems. Its a real pain.
 
Interesting, I've never considered the guest account, is it of any use in
Server2000? I'll read up on its designed purpose.

In the internal domain developers can already see the Event Viewer and COM+
remotely using a normal domain account permissions, I think this is default
behaviour, if it not then the server team must have turned this access on
via GPO or something. In addition the developers will need shares to
relevant directories (not as a problem) but also a view into IIS and the
Registry.

The last two I suppose are the problem, I've never tweaked the permissions a
lot for these (outside tiered app/web/db permission structures that is).

The thing is, the more key services I make available remotely via different
methods the more dispersed all the information becomes and the more the
developers will dislike it. I was hoping for a quick fix but looks like I'm
going to have to take the long road?!?

Thoughts always welcome!

Oli.
 
Probably not. I only threw that out as an example.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Interesting, I've never considered the guest account, is it of any use in
| Server2000? I'll read up on its designed purpose.
<snip>
 
Back
Top