Need a little help please.....

[jim]

I have the Windows 2000 Server Administrator's Companion (Microsoft Press),
but it's not been very helpful (or I have been very dense).

I have been tasked with caring for an ancient Windows 2000 Server and the
users on its small domain.

What I need to do is have a user desktop that is set up with applications,
printers, desktop links, favorites, etc. (everything they need to do their
job) and restrict them from changing those things, installing applications,
getting to the control panel, running unauthorized apps, etc.

It is for a location that cannot seem to get its workers to stop installing
crap on the local PCs and they want it locked down. (I said just fire the
people that don't listen and your problem is solved....but that is not the
path they have chosen.)

Are there any resources that may be helpful to me in this (more helpful than
the MS tome that I can't seem to figure out)?

jim

 

[Danny Sanders]

If the users are not members of the Administrator group on their local PCs,
this will go a long ways towards stopping them from installing stuff on the
local PC.


hth
DDS

 

[jim]

I'm hoping to only have Guest active on the local PC (no other accounts
active locally - and maybe not that if I can get away with it) and force
them to logon to the domain using a Mandatory Profile.

I've seen it done at other companies - this is just my first time having to
administer a Windows 2000 Server.

With all of the How Do I.... sites out there, you'd think there'd be one for
admins.

If there is, I haven't found it yet.

Jim

 

[Roger Abell [MVP]]

I have the Windows 2000 Server Administrator's Companion (Microsoft Press),
but it's not been very helpful (or I have been very dense).

I have been tasked with caring for an ancient Windows 2000 Server and the
users on its small domain.

What I need to do is have a user desktop that is set up with applications,
printers, desktop links, favorites, etc. (everything they need to do their
job) and restrict them from changing those things, installing
applications, getting to the control panel, running unauthorized apps,
etc.

It is for a location that cannot seem to get its workers to stop
installing crap on the local PCs and they want it locked down. (I said
just fire the people that don't listen and your problem is solved....but
that is not the path they have chosen.)

Are there any resources that may be helpful to me in this (more helpful
than the MS tome that I can't seem to figure out)?

hi jim,

Since they will not fire at will, ask won't they then promulgate
quite visibly their policy on PC usage and violation penulty.
If you have an uplevel domain environment perhaps subsumming
them in some new OU with an imposed user profile migration
would be much shorter than config of a W2k for your specs
unless you overlay a pushy, fully forceful account restriction
set in the existing W2k domain (via alien, remote mgmt ?).

Roger