Server/Domain Controller MMC snap-ins
I'm not an Admin by any means, but I tinker all the time and got tired of searching for the MMC snap-ins. So I wrote my own program that consolidates about 90% of stuff Admins might use, however, I think my Server/Domain .msc files are out of date, started this program years ago.
Might I impose on your graciousness, how about that for kissing up, and provide me with a list of those snap-ins?
Marshall Neill
Software/Hardware used:
Windows Vista
Software/Hardware used:
Windows Vista
ASKED:
October 6, 2009 5:08 PM
UPDATED:
October 8, 2009 7:30 PM
Answer Wiki:
You'll probably be better off using the MMC snapins then your own app as the snapins are updated with new functionality with each OS release and your application isn't.
The Snapins are:
Active Directory Domains and Trusts
Active Directory Sites and Services
Active Directory Users and Computers
ADSI Edit
Group Policy Management
Group Policy Management Editor
Group Policy Object Editor
Group Policy Started GPO Editor
Resultant Set of Policy
Schema Editor
Security Configuration and Analysis
Security Templates
To see all answers submitted to the Answer Wiki: View Answer History.
A few other useful ones are:
Computer Manager
DNS
DHCP
Exchange System
IIS
Update Services
My application just kicks off the snap-in. eg.. mmc.exe ‘snap-in’… SInce my source for those snap-ins is over 2yrs old I wanted to know what the snap-ins are so I can change or leave alone the current ones I have coded.
For instance, my subroutine contains all the snap-ins by name, eg. secpol.msc, gpedit.msc, etc. The server snap-ins are the ones I don’t have access to.
So I was requesting the exact names of all the Server snap-ins. At which point my application will be able to access just about everything for Windows.
Thanks in advance.
Marshall Neill
Why not just create a new MMC console and add all the snapins into it?
The purpose of my app is to allow the IT Admin or Home User to just bring up this app, provide 95% of what is needed to administer the system.
The Server button brings up all the ???.msc’s that would be required to manage said button.
The problem I think is this, Microsoft may have changed some of those ???.msc’s to another name.
Basic button contains all the general stuff, Personalize, Backup, things like that
Security button contains all Security related matters
System button contains all the ‘system’ type stuff, Registry, Services, Group Policy editor and the like.
Networking button, all that is networking related (Not Server tho)
Hardware button all the hardware stuff, mouse, printers, device manager and the like
Additional button contains the rest, DirectX, folder options, etc.
Server button, the area in question
Marshall Neill