MMC Snapin in list

List of Snap-in MSC files for Server 2012R2 Standard

AdRmsAdmin.msc

adsiedit.msc

azman.msc

certlm.msc

certmgr.msc

certsrv.msc

certtmpl.msc

CluAdmin.msc

comexp.msc

compmgmt.msc

devmgmt.msc

dfsmgmt.msc

dhcpmgmt.msc

diskmgmt.msc

dnsmgmt.msc

domain.msc

dsa.msc

dssite.msc

eventvwr.msc

FailoverClusters.SnapInHelper.msc

fsmgmt.msc

fsrm.msc

fxsadmin.msc

gpedit.msc

gpmc.msc

gpme.msc

gptedit.msc

HCSCFG.MSC

idmumgmt.msc

iis.msc

iis6.msc

lsdiag.msc

lusrmgr.msc

Microsoft.IdentityServer.msc

NAPCLCFG.MSC

nfsmgmt.msc

nps.msc

ocsp.msc

perfmon.msc

pkiview.msc

printmanagement.msc

rrasmgmt.msc

rsop.msc

ScanManagement.msc

secpol.msc

services.msc

storagemgmt.msc

tapimgmt.msc

taskschd.msc

tpm.msc

tsgateway.msc

virtmgmt.msc

wbadmin.msc

WdsMgmt.msc

WF.msc

winsmgmt.msc

wlbadmin.msc

WmiMgmt.msc

wsus.msc

wsus.msc

List of MMC Snap-in MSC files for Windows 7 Home Premium PC

azman.msc

certmgr.msc

CIADV.MSC

comexp.msc

compmgmt.msc

devmgmt.msc

diskmgmt.msc

eventvwr.msc

fsmgmt.msc

gpedit.msc

iis.msc

iis6.msc

lusrmgr.msc

mscorcfg.msc

NAPCLCFG.MSC

nfsmgmt.msc

perfmon.msc

printmanagement.msc

rsop.msc

ScanManagement.msc

secpol.msc

services.msc

taskschd.msc

tpm.msc

WF.msc

WmiMgmt.msc

# PowerShell script to list MMC snap-ins on a Win7 Home Premium PC

$Dir = get-childitem C:\ -recurse

# $Dir |get-member

$List = $Dir | where {$_.extension -eq ".msc"}

$List |Sort-Object -descending| format-table name

Technet-Windows MMC Snap-ins (.MSC)

unlock user accounts with powershell

You can import the Active drirectory module by typing in a Powershell session

import-module activedirectory

You might want to check that it is available first by typing

get-module -listavailable

For more information you want to follow this link Win2k8R2 AD PoSh Module

Anyway...I had a strange call where the Active Directory Users and Computers showed an account was in a normal unlocked state and so did the lockoutstatus tool. Bit starnge...so I ran a script that I have that brings me back some account information (I'll post this script later) one of the things it reports is if the account is locked or not....and...it showed the account was locked!

Anyway a quick method of unlocking the account...imported the activedirectory module and with a little help from a the CMD shell

dsquery user -name "*DisplayNameString*" | dsget user -upn -dn

for example..

dsquery user -name "*bloggs*" | dsget user -upn -dn

will return the User Principal Name of the user object and the Distinguished Name of the user object from the AD containing the text string bloggs ...

I also brought back the UPN so that I can prove what type of account the customer was using...some enterprises may prefix the account name alphanumerically to seperate out Higher Level Access accounts or just plain DOMAIN ADMIN accounts, I verified what type of account the customer was refering to by double checking the UPN and the DN of the user object. And since I have my Powershell and CMD shell set for copy and pasting...I can easily copy the DN from the CMD shell to Powershell and use the activedirectory module to unlock the account....

unlock-adaccount -identity "this_is_the_DN_path"

and the " " characters?...well they just take care of the spaces in the DN path.

Powershell Profiles and Snap-Ins

Instead of me blabbering on about Powershell Profiles I’ve found a good Microsoft Technet page that does all that for me!! And…you can find it here….

http://technet.microsoft.com/en-us/library/bb613488(VS.85).aspx

you may also have to look at the execution policy of the system and you can see how to do all that from this link here….

http://technet.microsoft.com/en-us/library/bb648601(VS.85).aspx

The execution policy is a security measure so it’s not there just to rain on your parade!!!!

Getting back to Powershell Profiles…..I have found three good utils, or rather snap-ins….the Quest active roles I’ve mentioned before and to compliment that I’ve downloaded the Microsoft Powershell Community Extensions or rather to give it a nickname……PSCX. And from VMWare the PowerCLI a powershell snap-in for VMWare OSs.

Now….here is the thing….the bad rub of the green….the rain on your parade!!! Once you have these installed the Powershell GUI or CLI interface does not…. No dont cry….it’s all to do with your blank profile….edit your own profile (Notepad or wordpad will do!) and to make sure that for each GUI or CLI powershell session picks up the snap-in, permanently, enter the command
add-pssnapin quest.activeroles.admanagement
save the file, and any powershell session will now execute that command when you launch a powershell session.

The Snap-Ins I use I have scripted, any time I launch Powershell I just run the scrip to load the snapins...the script contains these lines

Add-PSSnapin quest.activeroles.admanagement (Quest Active Roles) Add-PSSnapIn VMware.VumAutomation (VMWare) Add-PSSnapin VMware.VimAutomation.Core (VMWare)

For the Microsoft Powershell Community Extensions, run the MSI file and take the option AMMEND TO PROFILE and now you have both snap-ins configured for any Powershell session.

You can configure system wide profiles, I just configured my own profile though.

Opps before I forget links for PSCX ,PowerCLI and QAD stuff are here….
http://pscx.codeplex.com/   you may need to register for MSCX
http://www.quest.com/powershell/activeroles-server.aspx

http://communities.vmware.com/community/vmtn/server/vsphere/automationtools/powercli