SCVMM 2012 won’t install! HELP!

Ran into a simple one today to share.  Wish I grabbed the screen shot today.

I noted my new install of SCVMM 2012 wouldn’t finish on my copy of Server 2008R2 Enterprise.   It complained about being unable to launch Powershell and Failover clustering in the final window.

The answer? Duh! Make sure the Failover Clustering RSAT is installed on the SCVMM Server.  I just went ahead and cheated and threw them all on.

Import-Module ServerManager; GET-WindowsFeature *RSAT* | Add-WindowsFeature; RESTART-COMPUTER

I reran the Install and I have SCVMM2012 running happily now. Smile

Get Group Membership from NT4 with Windows Powershell for Migration to Windows Server 2012

Ok.  One last bit of madness.  

I would play with an Exchange 5.5 scenario but the funny thing is, I don’t think I have the Media anywhere…. Maybe if I ask Kevin nicely.

The whole point of this task wasn’t to really so much Manage an NT4 server but to determine what data I COULD pull from a legacy Domain that was so far out of support, you’d be stuck.  I wanted to see what Powershell could REALLY do.  I’ve been impressed.

My final task I decided was to try and pull out Group memberships from archaic and stale domain.   Completely migrate whatever we could onto a new platform.

Having the Groups created in Active Directory from the old NT4 domain just saves me typing.   It’s NICE but it’s not the whole beast.   Getting the user membership migrated over, THAT’S the big time saver.

So in our CONTOSO domain we obtained the groups by Binding to the Domain with the [ADSI] provider and then running a quick Cmdlet to filter out only Groups.


$Groups=$NTDomain.psbase.children | where { $-.SchemaClassName –eq “group” }

But the bigger challenge would be to pull  out the memberships and store them into something useful (Like say a CSV file?  With the GroupName in a column?)

I found that if I ran a direct bind to a group like this



I could pull out Something.  But the something was a result like below


But thanks to a posting from Brandon Shell (@bsonposh) I found, “Enumerating Local Group Membership” this wasn’t so bad.  

Well, I fibbed.  It LOOKED bad because it involved a funky method that made my head hurt, but his solution worked perfectly.   You had to pipe each member of the returned array into THIS to get the Name of the User.


Now I know why I hated working with NT4!

So running our initial list of Group Members through Brandon’s special Powershell decoder ring….

$Groupname.members() | foreach { $-.gettype().invokemember("Name",’GetProperty’,$null,$-,$null)}

and we now have USEFUL information.


Now to pull out this pile and produce something useful CSV output

We also have the list of Groups from Before.   Within the property returned is “PATH” which is the Path we need to bind to with [ADSI].   We’ll use that to individually bind to the Groups, pull their membership and output all to a CSV file we’ll build.

# Bind to the NT4 Domain Contoso


$Groups=$NTDomain.psbase.children | where { $-.SchemaClassName –eq “group” }

# Define my Quotes and commas

# Honestly?  It’s to avoid my blog software switching the characters on me

# I could just as well use this ‘”Groupname”,”Groupmember”’

# But every so often the characters switch.

# Besides, this is more readable Smile



# Create a blank file to hold the data

NEW-ITEM C:PowershellGroupmembers.csv –itemtype file –force

# Add the Header to our CSV file

add-content –value ($Quote+”GroupName”+$quote+$comma+$Quote+”Groupmember”+$quote) –path c:powershellgroupmembers.csv

# Step through the Groups

$groups | foreach {

# Store away the Group name


# Step through the membership

$-.members() | foreach {

# Run this through Brandon Shell’s (@bsonposh) secret Decoder ring…


# Store away the data and place it into a CSV file


add-content –value $data –path C:PowershellGroupmembers.csv



At the end you should have a CSV file that looks like this


Which if you copy over to a USB key (And presuming you already created the Group names in the Server 2012 BEFORE with the previous data gathering session) you could do something like this to populate the groups.

IMPORT-CSV C:PowershellGroupMembers.csv | Foreach { ADD-ADGROUPMEMBER $-.Groupname $-.Groupmember }

Oh look.  All my memberships populated in a NEW Domain Smile Sweeeeet.

Feelin’ that Power flowing free with PowerShell

The Energized Tech

Powershell–I went slightly mad and created a user in NT4

Now listen clearly.  This is NOT a hack.  It’s meant to do this. 

I can also hear a few people (ok, MORE than a few, a LOT) screaming “WHY?! WHY?!? WHYYYY????!??!!!!”

Just cuz.  I was curious if it could work and to what degree.

So here we have a lovely little Domain on an NT4 server called “CONTOSO”, leftover from my previous session of pulling users out. 

I wanted to see just what it would take.

Process is simple actually.

Bind to the Domain

Create a user object

Populate the necessary fields

Set it in stone

Now if there are any small children watching this?  BACK AWAY!  I am working with a VERY old and INSECURE system that might just Blue Screen and eat something.

Bind to the Domain while logged as an account with Domain Admin rights


Create the User Object

$NEWUser=$NTDomain.psbase.Children.add(“John Smith”,”user”)

Populate the necessary fields


$NewUser.Put(“Description”,”Our Standard Generic User”)

Set it in stone


Yes.  It works.  It follows the exact same principals and rules when creating and modifying local machine accounts and groups in Windows 7.

I’m not quite sure where this is actually USEFUL but it was fun messing about Smile

The Power of Shell took me over!

The Energized Tech