Exchange 2010 Mailbox Moves from CSV file

October 3, 2012 7 comments

Recently during our Exchange migration I wanted a way to automate our mailbox moves.  Even though PowerShell makes this is very easy to script I couldn’t just use a normal filter because the mailboxes I am moving need go to one of three different databases.   I couldn’t use the New-MoveRequest cmdlet with a normal filter because none of the mailboxes had any common attributes to filter on.    Instead I created a CSV file with the mailbox name and the target databases.  In the past this would have meant many lines of VBscript code but with PowerShell this can all be done with a one liner!  Then using PowerShell I read this information in and pipe it over to the New-MoveRequest cmdlet to initiate the mailbox moves. 

My CSV file looks like this.

UserID TargetDB
User01 MBX01
User02 MBX03
User03 MBX02

The PowerShell script looks like this.

Import-Csv .\Filename.csv | % {New-MoveRequest -Identity $_.UserID 

-TargetDatabase $_.TargetDB}

I also created another one for ad-hoc moves.  This Powershell script allows me to specify the CSV file that I want to use instead of hardcoding it into the script.

 

$csvfile = Read-Host "Enter in the name of the CSV File that contains the mailboxes you want to move"

Import-Csv $csvfile | % {New-MoveRequest -Identity $_.UserID -TargetDatabase $_.TargetDB}

If you haven’t started using PowerShell for scripting tasks I highly recommend that you start looking into it.  It’s got a bit of a learning curve but it’s very powerful once your get a good grasp on it.

Categories: Exchange, Powershell Tags: ,

Using HP Proliant Broadcom NICs in WinPE

June 7, 2012 7 comments

We recently got in a new HP Proliant BL460c Gen8 blade with the HP 530FLB NIC. It’s a great piece of hardware but using the NIC in WinPE is not much fun.  We recently started using MDT to deploy Windows servers now but no matter what I did I could not get the NIC driver to load in WinPE.

Even though the drivers were imported into MDT and I had rebuilt my boot images it would not load.  Finally I ran HP’s driver installation utility from inside WinPE and it came up.  That’s when I discovered that the NIC needs the HP Virtual Bus Device driver loaded before it can load the NIC driver.  Looking at the PnP IDs that the driver supports I noticed they all start with b06bdrv\l2nd instead of the usual pci_<VenID>.  This is because the NIC virtual sits on top of another device. 

So why not just load the HP Virtual Bus Device in MDT?  That’s what I did but the HP Virtual Bus Device is a system-class driver and by default MDT does not copy system-class drivers into the boot images.  image

Sure you can configure it to add them but then your boot images will get much larger.  My solution was to instead put a copy of the HP Virtual Bus Device (evbd.inf) driver into my MDT boot image using the “Extra directory to add” feature in MDT.  I also imported the NIC drivers into MDT as I normally do. 

image

Once the boot image loads press F8 to open a new command window. Navigate to the folder you added to the MDT boot image (it should be right off the root) and enter drvload evbd.inf. After a few seconds the driver will load and the NIC should now be active. It’s not an ideal solution but since we don’t deploy a lot of these servers it works for me.  This same process would also apply to some of the other Broadcom NICs used in HP blades and servers like the NC373i and NC382i. 

Categories: Deployment, HP, MDT, Windows Tags: , , ,

Setup MDT 2012 to use USMT 3

May 15, 2012 4 comments

I recently upgraded our MDT 2010 Deployment share to 2012 and ran into an issue with USMT 3.  We still have some scenarios where we are deploying Windows XP so USMT 3 is required.  Whenever we ran a task sequence that needed the USMT 3 files we would get an error that the files could not be found.  I thought this was odd since the USMT 3 CAB file was in the correct location.  Or at least it was for 2010. 

In MDT 2010 you just had to leave the USMT30_x86.CAB file in the DeploymentShare\Tools\X86 folder and MDT took care of the rest.  With MDT 2012 you need to create a USMT3 folder in DeploymentShare\Tools\X86 and then unpack the CAB file into this folder.  It will not unpack the CAB file for you anymore.  Now MDT will be able to find the USMT files and continue.

Hopefully this helps out anyone else that has done an upgrade from 2010 to 2012.

Categories: Deployment, MDT Tags: , ,

DISM GUI 4.0 Feature Requests

February 20, 2012 60 comments

I’ve just started working on version 4 of DISM GUI and honestly I don’t know what features of DISM to add.  So I’m asking the community for some help here.

  • What features of DISM that you use often are missing from the GUI?
  • What changes to the graphical interface would you suggest?
  • Do you use DISM in online mode?  If so would having an online mode be a useful feature to add?

Most of my work with DISM GUI revolves around managing drivers and features but I understand my use case is not the same as everyone else’s.  I’ve tried to add what the I felt were the most used features of DISM to the application.  Leave some feedback here or head on over to the Codeplex site and leave your suggestion there.

Categories: DISM, DISM GUI Tags: , ,

DISM GUI is now on CodePlex

February 8, 2012 Leave a comment

I have finally created a CodePlex project for DISM GUI.  The latest version (3.1) can be found on the CodePlex site as well as the source code for what will eventually be version 4.0.  So for anyone that wants to see the inner workings (and my sloppy code) of DISM GUI head on over to CodePlex to take a look.  If you are interested in helping out with the development contact me through the Codeplex site.

From now on I will be keeping all releases of DISM GUI on the CodePlex site and remove it from my Skydrive account. 

Categories: DISM GUI Tags: , ,

DISM GUI 3.1

November 30, 2011 23 comments

**An Updated version of DISM GUI can be found here**

Version 3.1 of DISM GUI is ready for download.  No major changes in this just a few background changes and 2 usability updates based on feedback I received.

  • Added a confirmation dialog box to the exit button.  Now if you accidently click Exit you will be prompted to confirm exiting the program.
  • The WIM location and path can now handle quotes in the text box.
      I’m working on cleaning up the code and eventually turning this into a Codeplex project.  I really haven’t had a lot of time to work on it lately but hopefully early next year I can start on it. If you are interested in contributing to the Codeplex project when it goes live contact me
Categories: Deployment, DISM, DISM GUI, WAIK Tags: , ,

USMT 3.0 and Office 2010

November 17, 2011 1 comment

So you are still doing Windows XP to Windows XP migrations using MDT but you have deployed Office 2010.  You realize that USMT 3.0 doesn’t support Office 2010 and user’s settings are not getting carried over.  Sure USMT 4.0 supports Office 2010 but it doesn’t support Windows XP as a target.  What do you do now?

Well it turns out you can use the XML rules files from the USMT 4.0 update with USMT 3.0.  All you need to do is put them in the correct location in the MDT Deployment Share.  Just make sure that you place the MigApp.xml file in the DeploymentShare\Tools\x86 folder and USMT 3.0 will use the updated files.

I don’t know if this is supported by Microsoft but we have been using it for the past few weeks for some XP to XP migrations and it has worked out well for us.

Categories: Deployment, MDT, Office Tags: ,
%d bloggers like this: