Step by Step Directions for Techs
It isn’t hard, but you have to do a few things to prep a USB drive for use in imaging with MDT. You need to mark the partition as active and you need to make sure it is formatted for NTFS.
Here is the output from my window:
You then need to format the drive as NTFS. You can do it here by:
Type “Exit” to leave the DISKPART tool.
Now, you just need to copy the contents of your MDT content folder to the drive and you are set! Don’t forget to boot off of it (by setting the BIOS or choosing an alternative boot device).
If you are using a SANDisk, you may need to do one more thing. You need to get a copy of BOOTSEC (available in WAIK). Open a command prompt and execute “Bootsect.exe /nt60 D:” (where D: is your USB drive) from the directory you put BOOTSEC into.
Never fear, a script is here (kinda).
Recently I was working to automate the installation of a poorly written program. For the life of me this thing would not install quietly. Repackaging it failed and I was running out of time. I choose to install the program and pass the appropriate keystrokes to it.
Note: This is not advised when rolling applications out if the user is at the keyboard. One click to another application and this all goes haywire.
So what I did what create an install.vbs script that looks a bit like this:
Set objShell = WScript.CreateObject(“WScript.Shell”)
‘This pulls up the “Setup” window as the active window
Do Until Success = True
Success = objShell.AppActivate(“Setup”)
‘Takes a bit before the application can take inputs. This is 6 seconds
‘This clicks the install button
‘It takes a little bit to install it
‘Close configuration window by pressing Alt-D-E
Once you have that, you launch the setup program (you can do that in this script or in another one. However, if you do it from a batch file, you need to use a start command (otherwise it waits for the process to finish before moving on):
start “” “%~dp0setup.exe”
start “” “%~dp0install.vbs”
Note: The %~dpo is a shortcut that uses the current directory it is being run out of instead of hard coding the paths.
As you can see, there is a bit of timing you have to get down. That is just trial and error. I used a virtual environment and snapshots to get the it working so I could always install on a “clean” system.
If there are other keystrokes you need, here is where I got them:
When you are copying files from one server to another or one volume to another and need to retain the file permissions, robocopy is your guy. In order to speed things up, I will frequently start multiple windows. To do this, I will put together multiple lines into a single powershell script that opens multiple windows for me. Call me lazy, but it works.
Couple things about this:
Migrating between Exchange 2007 and 2013 or Exchange 2010 and 2013? Mailbox migration speeds can be unbearably slow.
Exchange 2013 (as well as older versions, including 2010) changed the number of concurrent mailbox moves to 2… let’s change that to 5. Beware of setting it too high as it could have a serious impact on the Exchange infrastructure.
This change has to be done on all the front end servers. You should see that it will now migrate 5 mailboxes simultaneously. You can also speed things up by migrating to multiple data stores simultaneously. Some caution is needed when trying to max your migration speed as you can pretty easily overrun the storage (especially if it is local).