Monday, April 23, 2012

How to install MDT (Microsoft Deployment Toolkit) - 05

Adding Applications to MDT 2010: Office 2010 

We can add applications using a simple wizard. for that,

1.    Deployment Workbench” > “Distribution Share” > “Applications” > “New”.

2.    Select “Application with source files”.

3.    Complete the data about the application.

4.    Select the “Source Directory”. Since I have it on the hard drive, I’ll check “Move the files to the distribution share instead of copying them”. 

5. Keep the directory name as suggested: “Microsoft Office 2010”.

6. On “Command Details” introduce the name of the executable for Office 2010: “setup.exe” and click on “Finish”. We’ll add the special arguments to achieve silent installations in next steps.

Wednesday, April 18, 2012

How to install MDT (Microsoft Deployment Toolkit) - 04

 Creating a Deployment Task Sequence 

Now we have the distribution share with a clean image of Windows 7, we can create a task sequence to deploy the operating system.
1.    In “Deployment Shares”, expand the deployment share created, right click “Task Sequences” and select “New Task Sequence”. 

2.    Insert a “Task Sequence ID”, I’m using “WIN7”. And a “Task Sequence name”, in my case “Deploy Windows 7 clean image”. Click “Next”.  

3.    Accept the default option in “Template”: “Standard Client Task Sequence”. Click “Next”.

4.    Select the operating system to deploy. Click “Next”. 

5.    The “Product Key” section can be used to not specify a key at this point. Click “Next”.

6. Complete the information about the registered user and click “Next”. 

7. In my case I’m also selecting the local Administrator password. Click “Next”. 

8. In the “Summary” page click “Next”.

9. Once the process is complete we can click “Finish”.

Note: There’s an option of “View Script”, which we can use to retrieve an automated script to use for every time we want to create a similar Task Sequence (we only need to change the values)

10. The process is completed once we update the Deployment Share. In the Deployment Share name, right click and select “Update Distribution Share”. 

11. select the option for “Optimize the boot image updating process”. Click “Next”. 

12. Click “Next” on “Summary”. This process can take a few minutes since it will be creating new files, including the boot images “LiteTouchPE_x86.iso” and “LiteTouchPE_x64” which can be used for the clean operating system deployment. 

The drivers section we can create simple wizard where we can add device drivers into the operating system deployment. This is support “.inf” extension, we can add the components directly; but always remember to use the “Update Distribution Share” once you change the deployment share

How to install MDT (Microsoft Deployment Toolkit) - 03

Adding Windows 7 Operating System

Once the deployment share is created, the next step is to add the files from the Windows 7 image. In my case I’m using a Windows 7 64bit image.
1.    In “Deployment Shares”, expand the deployment share we’ve just created, right click “Operating Systems” and select “Import Operating System”.

2.      Since this is a clean image from the Windows 7 media, select “Full set of source files” and click “Next”. 

3. I’m selecting the D:\ directory since I have attached the Windows 7 media in this drive. Click “Next”.

4. Select the “Destination directory name” and click “Next”.  

5. in the “Summary” page click on “Next”.
6. Once the process is complete, click on “Finish”.  

In my case, the images added will look like this in the MDT console.  

Tuesday, April 17, 2012

How to install MDT (Microsoft Deployment Toolkit) - 02

Adding a Clean Image to MDT 2010

After MDT installation, we can create a new deployment share


1. Create the distribution share.
2. Add operating system files to the distribution share.
3. Create a task sequence for the reference computer. 

Creating the Distribution Share

1. In the MDT Console, right click on “Deployment Shares” and select “New Deployment Share”.

2. in the wizard, click on “Browse”.
3. Select a folder where you want to store all the binaries (applications, operating system, etc.) As a recommendation use a separate partition.

4. Click on “Next”.

5. Accept the name of the “Share Name” and click on “Next”. 

6. In the next page we can add a short description for the distribution share. Click “Next”.
7. Ensure that the option “Ask if an image should be captured” is checked and click “Next”.

8. If you want you can select “Ask user to set the local administrator password”

Click “Next”.

9. You can select “Ask user for a product key” or you can set this option in task sequence of each operating system deployment. Click “Next”. 

10. Review the “Summary” page and click “Next”.
11. Wait for the process to complete and click “Finish”.

Once the process completes, you can see this in our MDT 2010 Management Console.

How to install MDT (Microsoft Deployment Toolkit) - 01

MDT - Microsoft Deployment Toolkit

MDT is a free application given by Microsoft and you can download it from

FYI: Microsoft Deployment Toolkit 2012 RC1 is also now available!

 Features in MDT 2010,
·         Comprehensive tools and guidance to efficiently manage large-scale deployments of Microsoft Office 2010.
·         A new User-Driven Installation (UDI) deployment method that utilizes System Center Configuration Manager. UDI lets end users initiate and customize an OS deployment on their PCs—via an easy-to-use wizard.
·         Automatically detects the true supported platforms for drivers, reducing deployment issues.

I’m going to use “Lite Touch Installation (LTI) for the deployment of Windows 7”. For  "Zero Touch Installation of Windows 7”  we can use Microsoft Deployment Toolkit 2010 with System Center Configuration Manager 2007 R2 SP2.

These are the things that I will explain here,
  • Install and configure Microsoft Deployment Toolkit 2010 – Update 1.
  • Create a Task Sequence and deploy clean Windows 7 images.
  • Adding and configuring Microsoft Office 2010 in MDT 2010 for deployment.
  • Creating and capturing a reference image of Windows 7 and Microsoft Office 2010.
  • Deployment of the customized Windows 7 images with Microsoft Office 2010 installed.

Requirements for MDT 2010
I have configured my Active Directory and DNS infrastructure and operational.
DHCP configured with Windows Deployment Services (WDS).
Windows Deployment Services (WDS) configured.
Windows 7 source files.
Microsoft Office 2010 installation files.

Windows Automated Installation Kit (WAIK) 2.0. You can download it from

  MSXML 6.0.
 Net Framework 3.5 SP1

 Note: Even though .Net Framework 2.5 SP1 is not a requirement for MDT 2010 installation; one of its features, User-Driven Installation (UDI), does requires the latest Microsoft Framework installed.

MDT 2010 Installation
 All Microsoft Deployment Toolkit versions, the installation is a straight forward procedure: Just download, execute the installer and complete the installation wizard.

Once installed, we can access any of the components from the “Start Menu”.

 “Getting started”: All the steps involved to get MDT 2010 functional. 


Documentation”: All necessary links to start working with the tool.

Also another important section is “Components” where we can verify that all necessary requirements were installed (plus other optional installations). 

Tuesday, April 10, 2012

How to change SQL Server 2008 Database name.

This is having only few steps and you have to run tree commands. Steps are bellow, 

   1.  First log in to SQL Server management Studio. In here you can select Windows Authentication Mode or the SQL Server Authentication.

    2. Then Run a new Query

   3.  Then Check the existing SQL Server Database name by using “SP_helpserver” command and click “Execute”. The existing Database name will show in the second window.

   4. Then copy that name and run “SP_ Dropserver Existing Server name” command and click Execute to execute the command.

    5.  Now you have removed the old Database name and run “ SP _Addserver new Server name” command to change the SQL Database name. Don’t forget to click Execute.

   6.  Now you change the Database name and you will able to run you SharePoint 2010 or the CRM wizard without any authentication errors. 

FYI: When you are executing these commands if you get some error massage. Just use “” marks between your Server name. Or you can find the reason of the error by checking the error details.

And another small thing.. Add a new AD user under logins (Security > Logins). This will help you to run your SharePoint configuration using different User