Windows Server 2008 R2 - Help with permissions

Izi

Izi

Soldato
Joined
9 Dec 2007
Posts
2,718
I have set up a domain with DNS and a few other services. Its all working great, I was surprised how easy it was, however I need a little help setting up permissions.

I want to set up up the DC to let users login to their own computer as an Administrators - I don't want them to come to me to be able to install a program for example, however I do not want to give them a group of 'Administrators' as this will enable them to login to the main server and change settings there. I want to lock down the server, but give users admin rights to their computers.

Can some one point me in the right direction?
 
There are only 6 of us here, i trust them, mostly :)

thanks, i will give this a go.

howler - how do you do what you just said there? Would I need to login as administrator on their machines and assign the role?
 
OK so I have gone to Computer - > PC1 - > Properties. A window pops up, is it the 'Managed By' tab?
 
Personally I'd at least create a new seperate AD group with the user accounts in, then drop this group into the administrators group on each of the pcs.

Just don't like the idea of every account getting admin rights by default.

Well, if it were me I wouldn't be giving everyone admin rights anyway :p

To do it all on from the server open up an mmc with the computer management snap in, and connect to each pc from there in turn.

Then go to the local users and groups section and you can add stuff to the administrators group there.

thanks for the reply.

x2hgo.png



Although the location resolves to the right IP I get an error as shown above. the computer is on - in order to manage the computer do I have to turn on network sharing etc from the dev04 machine?
 
Might be the firewall on the remote PC preventing you accessing that

Do you know what port this connection is made on?

scrub that i'm in, however I dont see where I can add users. In the system tools -> users and groups the only users listed are local user accounts, I.E not my domain accounts.
 
Last edited:
Sorry one other question.

Is there any easy way to migrate Documents/settings to the new domain accounts?

Each user currently logins to their computer using a username/password. When I join their computers to the domain, I would like to migrate documents/settings if possible.
 
By migration you mean user profiles from a workstation to another or to the DC?

Easy Migration tool does that. If you are looking for more enterprise level tool then the User State Migration tool does that job.

That might be what you are looking for?

So currently there is no domain. We now have one and everyone will login to their PC via the DC. The problem with this all settings/files are stored in the computer user profile.

I suppose what I could do is copy files to the public folder then copy back to my documents. I was kind of hoping for something better than that thought, something which could migrate FF/Chrome profiles as well as files and other settings.

This is not a migration from 1 pc to another, its a simple migration from Workgroup user to DC user on the same machines.
 
ah, i think the easy transfer will do it. Just save the img to external then restore it. will give it a go.
 
The documents will still be on the local PC, unless you redirect them to a file share.

A domain users profile will be c:\users\username.domain (on vista upwards, documents and settings formxp) but a local user will be c:\users\username

For only a few users, manually copying them would be simple enough, just log into any machine as a domain admin and access the PCs with \\machine name\c$

I'd seriously consider redirecting them to the server though, means they will be accessible from any machine and easier to back up


I dont mind them being on the local PC, much faster that way, is it not?
 
Unless you're dealing with huge files or have a very slow network, there's no noticeable difference in practice.

Except everyone would be reading and writing files to the same data store.

I do not have the infrastructure for that. Plus we are developers dealing with hundreds of thousands of small files which get compiled so it wouldn't be worth it I don't think.
 
Back
Top Bottom