Most useful Microsoft Management Console Snap-in Control Files (.msc files)

Hello, below you’ll find most useful Microsoft Management Console Snap-in Control Files that would be timesaving solution in your daily administration work. Also table with .msc files available in Windows Server 2008 and Windows Server 2012

Most useful .msc consoles are:

1. Computer Management compmgmt.msc

I think this is the common console that we’re opening everyday

2. Device Manager devmgmt.msc

Also basic well-known console

3. Disk Management diskmgmt.msc

Fast access to useful console:

4. Shared Folders fsmgmt.msc

5. Event Viewer eventvwr.msc

Known console:

6. Services services.msc

7. Task Scheduler taskschd.msc

Fast access to task scheduler

8. Windows Firewall with Advanced Security WF.msc

Simple to learn

9. Local Group Policy Editor gpedit.msc

10. Local Users and Groups lusrmgr.msc

Looser console

.msc files in Windows 2008 and Windows 2012

Search:

MSC file name	MMC name	Windows Server 2008	Windows Server 2012

adfs.msc	Active Directory Federation Services (AD FS)	+
AdRmsAdmin.msc	Active Directory Rights Management Services	+	+
adsiedit.msc	ADSI edit	+	+
azman.msc	Authorization Manager	+	+
certlm.msc	Certificates (Local Computer)		+
certmgr.msc	Certificates (Current User)	+	+
certsrv.msc	Certification Authority	+	+
certtmpl.msc	Certificate Templates	+	+
CIADV.MSC	Indexing Service	+
CluAdmin.msc	Failover Cluster Manager	+	+
comexp.msc	Component Services	+	+
compmgmt.msc	Computer Management	+	+
da6to4.msc	Performance Monitor (Network Interfaces)	+
daiphttps.msc	Performance Monitor (HTTPS traffic)	+
daipsecdos.msc	Performance Monitor (IPsec)	+
daisatap.msc	Performance Monitor (ISATAP)	+
DAMgmt.msc	DirectAccess	+
datrds.msc	Performance Monitor (Teredo Server)	+	+
devmgmt.msc	Device Manager	+	+
dfsmgmt.msc	DFS Management	+	+
dhcpmgmt.msc	DHCP	+	+
diskmgmt.msc	Disk Management	+	+
dnsmgmt.msc	DNS Manager	+	+
domain.msc	Active Directory Domains and Trusts	+	+
dsa.msc	Active Directory Users and Computers	+	+
dssite.msc	Active Directory Sites and Cervices	+	+
eventvwr.msc	Event Viewer	+	+
FailoverClusters.SnapInHelper.msc	Failover Cluster Manager	+	+
fsmgmt.msc	Shared Folders	+	+
fsrm.msc	File Server Resource Manager	+	+
fxsadmin.msc	Microsoft Fax Service Manager	+	+
gpedit.msc	Local Group Policy Editor	+	+
gpmc.msc	Group Policy Managerment	+	+
gpme.msc	Group Policy Managerment Editor	+	+
gptedit.msc	Group Policy Starter GPO Editor	+
gptedit.msc	Local Group Policy Editor		+
HCSCFG.MSC	Health Registration Authority	+	+
idmumgmt.msc	Microsoft Identity Management for UNIX	+	+
iis.msc	Internet Information Services (IIS) Manager	+	+
iis6.msc	Internet Information Services (IIS) 6.0 Manager	+	+
lsdiag.msc	RD Licensing Diagnoser		+
lusrmgr.msc	Local Users and Groups	+	+
Microsoft.IdentityServer.msc	AD FS		+
NAPCLCFG.MSC	NAP Client Configuration	+	+
nfsmgmt.msc	Services for Network File System	+	+
nps.msc	Network Policy Server	+	+
ocsp.msc	Online Responder	+	+
perfmon.msc	Performance Monitor	+	+
pkiview.msc	Enterprise PKI	+	+
printmanagement.msc	Print Management	+	+
remoteprograms.msc	RemoteApp Manager (Local)	+
rrasmgmt.msc	Routing and Remote Access	+	+
rsop.msc	Resultant Set of Policy	+	+
SanMmc.msc	Storage Manager for SANs (Local)	+
sbmgr.msc	Remote Desktop Connection Manager	+
ScanManagement.msc	Scan Management	+	+
secpol.msc	Local Security Policy	+	+
ServerManager.msc	Server Manager	+
services.msc	Services	+	+
storagemgmt.msc	Share and Storage Management	+	+
storexpl.msc	Storage Explorer	+
tapimgmt.msc	Telephony	+	+
taskschd.msc	Task Scheduler	+	+
tpm.msc	Trusted Platform Module (TPM) Management	+	+
tsadmin.msc	Remote Desktop Services Manager	+
tsconfig.msc	Remote Desktop Session Host Configuration	+
tsgateway.msc	RD Gateway Manager	+	+
tsmmc.msc	Remote Desktops	+
virtmgmt.msc	Hyper-V Manager	+	+
wbadmin.msc	Windows Server Backup	+	+
WdsMgmt.msc	Windows Deployment Services	+	+
WF.msc	Windows Firewall with Advanced Security	+	+
winsmgmt.msc	WINS	+	+
wlbadmin.msc	Windows Server Backup		+
WmiMgmt.msc	WMI Management	+	+
WSRM.msc	Windows System Resource Manager	+	+
wsus.msc	Update Services		+

Step-By-Step: Assigning VMs with Static IP addresses in a Virtual Network

Hello Folks,
in order to follow along you should be familiar with IaaS.  The easiest way to do that is to listen to the Windows Azure for IT Pros Jump Start on Microsoft Virtual Academy.
Over the last few weeks we published a lot of information regarding Microsoft Azure.  I’ve actually concentrated on the networking side of things because after many conversations with ITPros it was clear that guidance on extending your own datacenter to the cloud was the first step needed.
So with that in mind I wrote several articles on connecting your local network with a (or many) virtual networks in the cloud.

• Step-By-Step: Move a VM to a different Vnet on Azure
• Step-by-Step: Multi-Site Azure VPN
• Step-by-Step: Configure VNet to VNet Connectivity in Azure

How ever last week while I was in Redmond someone pointing out that I had left off an very important topic.  How do I assign a static IP address to a Virtual Machine running in one of my Virtual Networks on Azure.
Well…  Say no more .  Here is how it’d done.
Before we get to the steps.  There are a few things you need to know about IP addresses on Azure.
as you can see in the screen capture below.  There are 2 IP address for every VM.
The VIP (Virtual IP address):   The public IP address pointing to the cloud service where the VM deployed to.
and The DIP (an internal IP assigned by Windows Azure with DHCP): The IP address assigned to the VM for communicating within the Windows Azure virtual Network.

In this articles we will set the INTERNAL address to a static one.  This could be done because the server is a DNS server, because you have services or LOB apps that connect to the server in question using a IP address instead of a FQDN.  whatever your reason. the process is the same.

Step 1: Verify that a specific IP address is available

For sake of argument I want to set my DC02 machine to 10.2.2.10.  as you can see above it is currently set to 10.2.2.4.
To see if 10.2.2.10 is available use the following command in your Microsoft Azure PowerShell console.
Test-AzureStaticVNetIP –VNetName vNet1 –IPAddress 10.2.2.10

If you get a “IsAvailable  : True” as the result, you’re good to proceed to step 2.

Step 2: Specify a static internal IP for a existing VM

Still in your Microsoft Azure PowerShell console, type the following command, and then press ENTER. (the command is on one line).  Please note that the Machine will need to restarted to start using the new IP address.
Get-AzureVM -Name DC02 –ServiceName PR-DC02 | Set-AzureStaticVNetIP –IPAddress 10.2.2.10 | Update-AzureVM
and the result of the command is:

Once you get the “OperationStatus = Succeeded”.  if you want to verify that the VM has really been set to the new address, type the following command, and then press ENTER.
Get-AzureVM -Name DC02 –ServiceName PR-DC02

Once my Machine restarted I opened a Remote Desktop Session and verified the settings.

You will notice that the address still shows up as “IPv4 address assigned by DHCP” , and that the address you specified IS the one being assigned (10.2.2.10). But notice the Lease Expires field…
The way azure deals with static IP addresses is to create a reservation for 135 years… it’s pretty safe that it’s going to exceed the life of that machine.
I hope this helps.  Feel free to send us comments and let us know what scenarios you want us to explore for you.
Cheers!