mm access another computer

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

hey im using the mmc to connect to another computer which is fine, but it shows an 'x' next to lcla users and groups, what do i do to allow me to view these properties from a mmc on the server. an image is attached.

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

its not a domain controller by any chance, if so you dont get local users on those!

 

im on the server, which is the DC, im using mmc to access another computer (192.168.0.10), which is done, but i get the x and access denied when i try to see local users and groups

 

If the server you are accessing is a domain member, user accounts will be controlled by the DC in Active Directory Users and Computers, not the Computer Management console.

 

ummm. thats not entirely correct. A domain member (be it a DC or a workstation) still maintains its local users and groups. Its entirely possible to create local accounts on a machine and continue to log into them after they join a domain.

Consider this - if your domain dies, but the server is still running, you would need to use the local admin account on the server to log in in order to check out the services etc.

Domain members still contain (and give access) to the local users and groups area via the OPs method - I can confirm this, since I've made use of it in domain environments in the past.

Edit: Further proof - THe GPO at my previous work explicity added our servicedesk group to the local administrator accounts on every machine on the network, every time they logged into the domain, in order to grant SDesk admin rights on the machines. If local accounts/groups were no longer in existance, this wouldnt even be possible, let alone useful.

 

You might want to go back and read your books again. A Domain Controller does not have access to Local Users and Groups.

"You cannot use Local Users and Groups to view local user and group accounts once a member server has been promoted to a domain controller. However, you can use Local Users and Groups on a domain controller to target remote computers (that are not domain controllers) on the network. Use Active Directory Users and Computers to manage users and groups in Active Directory."

http://technet2.microsoft.com/windo...70a8-43b3-97d8-43196a7860b81033.mspx?mfr=true

Although it does have a local SAM but it is just used for Directory Services Restore Mode or the Recovery Console.

"If you have physical access to a domain controller, you can restart the domain controller in Directory Services Restore Mode locally. Restarting in Directory Services Restore Mode takes the domain controller offline. In this mode, the server is not functioning as a domain controller.

When you start Windows Server 2003 in Directory Services Restore Mode, the local Administrator account is authenticated by the local Security Accounts Manager (SAM) database. Therefore, logging on requires that you use the local administrator password, not an Active Directory domain password. This password is set during Active Directory installation when you provide the password for Directory Services Restore Mode."

http://technet2.microsoft.com/Windo...395a-4c21-971f-9c3b6f4563631033.mspx?mfr=true

 

I have just set up a virual network with lots of different users and as far as I have done its all been through active directory users & groups.

From what I understand is you can view them through the computer management console but to edit you need to be in active directory.

 

you are confusing local and domain accounts bruce,
AD Users & Computers - Domain accounts
CM Users & Group - Local accounts

 

yep so I have.

 

Ah yes, oops. Confirmed this this morning with our DC. The DC's dont use the LUG stuff, but domain members that are not DC's still contain it.

That said, the OP's problem is still not related to this. On members, it shows up in the mmc fine, and on the DC, it just doesnt show up at all.

 

I'm not trying to be a jerk or anything but this is not correct either. If you open management on a DC Local Users and Groups are not shown but when you connect to a remote computer that is a DC Local Users and Group IS shown. Take a look when you get a chance.

 

want to read my post again? thats exactly what i just said.

 

hmmm. double post. oops

 

Seconds out... Round 2

 

You said the following:

"That said, the OP's problem is still not related to this. On members, it shows up in the mmc fine, and on the DC, it just doesnt show up at all."

He is currently on a DC connected to a another machine. He never really was clear on if he was connecting to a DC or a non DC. If he was connecting to a non DC from a DC he should not see that error.

 

since you choose to be pedantic about exactly what I said, rather than taking a second and realising i meant when connected to a DC/non-DC with mmc, I'm going to drop this, save a slight reiteration (I hope its specific enough for you).

This is likely unrelated to the OP's issue, since when looking at a DC with the MMC module, the LUAG is not visible, whereas on a non-DC, it is visible. Since the MMC is showing it, but not permitted access, I doubt this is linked. Furthermore, the OP has subsequently confirmed that he is connected from the DC to another computer, further confirming that the DC issue has nothing to do with the problem.

Now, back to topic, lets see if we can help the OP at all now shall we?

I came across another thread on another forum indicating that someone else had this issue after upgrading the machine to XP from win2k, is this what happened here? Another forum has someone indicating that using the setup disc to repair xp resolved the issue, this might be worth a try.