Microsoft Deployment Toolkit (2010) - Revision history

Lars: /* Overview */

2013-05-31T19:57:10Z

Overview

← Older revision		Revision as of 19:57, 31 May 2013
Line 1:		Line 1:
			== Important ==
			Due to the variety of hardware and driver issues, MDT2010 is proving to be a very fragile and maintenance-intensive deployment tool. As of May 2013, we are looking into alternative deployment methods.

	== Overview ==		== Overview ==
	As of January 2011, we are now using the Microsoft Development Toolkit (MDT2010) for deploying installations of Windows XP and Windows 7.		As of January 2011, we are now using the Microsoft Development Toolkit (MDT2010) for deploying installations of Windows XP and Windows 7.

Lars: /* Useful Tips */

2012-11-20T20:21:23Z

Useful Tips

← Older revision		Revision as of 20:21, 20 November 2012
Line 47:		Line 47:
	* An XP deployment that was built using a 32-bit reference machine will probably not work when deployed to a 64-bit machine.		* An XP deployment that was built using a 32-bit reference machine will probably not work when deployed to a 64-bit machine.
	* Windows 7 installations can only be deployed three times. After that it cannot be sysprepped for a fourth deployment. That means that if a reference machine's deployment "ancestry" involves using that same particular OS installation 3 times, you cannot use it for a reference machine anymore.		* Windows 7 installations can only be deployed three times. After that it cannot be sysprepped for a fourth deployment. That means that if a reference machine's deployment "ancestry" involves using that same particular OS installation 3 times, you cannot use it for a reference machine anymore.
			* Windows 7 source installations should not have recovery partitions built into them. In other words, when building your source installation, first partition and format the disk manually, and THEN install Windows 7. Don't let the Win 7 install do the partitioning and formatting.

	== Notes ==		== Notes ==

Lars: /* Useful Tips */

2011-10-14T17:11:15Z

Useful Tips

← Older revision		Revision as of 17:11, 14 October 2011
Line 46:		Line 46:
	* If you are going to use a virtual machine for your reference, make sure you add the drivers (network, scsi, etc) for that vm to the Out of Box drivers in the Task Sequence.		* If you are going to use a virtual machine for your reference, make sure you add the drivers (network, scsi, etc) for that vm to the Out of Box drivers in the Task Sequence.
	* An XP deployment that was built using a 32-bit reference machine will probably not work when deployed to a 64-bit machine.		* An XP deployment that was built using a 32-bit reference machine will probably not work when deployed to a 64-bit machine.
			* Windows 7 installations can only be deployed three times. After that it cannot be sysprepped for a fourth deployment. That means that if a reference machine's deployment "ancestry" involves using that same particular OS installation 3 times, you cannot use it for a reference machine anymore.

	== Notes ==		== Notes ==

Lars: /* Useful Tips */

2011-02-18T16:50:53Z

Useful Tips

← Older revision		Revision as of 16:50, 18 February 2011
Line 46:		Line 46:
	* If you are going to use a virtual machine for your reference, make sure you add the drivers (network, scsi, etc) for that vm to the Out of Box drivers in the Task Sequence.		* If you are going to use a virtual machine for your reference, make sure you add the drivers (network, scsi, etc) for that vm to the Out of Box drivers in the Task Sequence.
	* An XP deployment that was built using a 32-bit reference machine will probably not work when deployed to a 64-bit machine.		* An XP deployment that was built using a 32-bit reference machine will probably not work when deployed to a 64-bit machine.


			== Notes ==
			The images don't always install properly on a machine, and this could be due to a myriad of reasons. For those cases, I am building a Task Sequence that only installs software and drivers, not the OS. This TS will take longer than installing an image, but it should also work on all machines.

	==Sources==		==Sources==

Lars at 17:09, 4 February 2011

2011-02-04T17:09:41Z

← Older revision		Revision as of 17:09, 4 February 2011
Line 1:		Line 1:
	~~'''NOTE: This article is in progress.'''~~
	== Overview ==		== Overview ==
	As of January 2011, we are now using the Microsoft Development Toolkit (MDT2010) for deploying installations of Windows XP and Windows 7.		As of January 2011, we are now using the Microsoft Development Toolkit (MDT2010) for deploying installations of Windows XP and Windows 7.

Lars: /* Sources */

2011-02-04T17:09:10Z

Sources

← Older revision		Revision as of 17:09, 4 February 2011
Line 49:		Line 49:

	==Sources==		==Sources==
	* http://technet.microsoft.com/en-us/solutionaccelerators/dd407791		* [http://technet.microsoft.com/en-us/solutionaccelerators/dd407791 Microsoft Deployment Toolkit Web Page]
	* http://social.technet.microsoft.com/Forums/en/mdt/thread/033c0659-664b-4dc0-9d3d-c433bd5cb56d		* [http://social.technet.microsoft.com/Forums/en/mdt/thread/033c0659-664b-4dc0-9d3d-c433bd5cb56d Newbie Questions Regarding MDT2010 Theory]
	* [http://ruhle.wordpress.com/2009/10/20/injecting-intel-storage-drivers-into-xp-wims-via-mdt/\|Intel Storage Drivers into XP WIMs via MDT]		* [http://ruhle.wordpress.com/2009/10/20/injecting-intel-storage-drivers-into-xp-wims-via-mdt/ Intel Storage Drivers into XP WIMs via MDT (Ruhle's Blog)]
	* [http://deploywindows.net/archives/2261 MDT2010 Trouble Shooting the Log Files]		* [http://deploywindows.net/archives/2261 MDT2010 Trouble Shooting the Log Files]
	* [http://blogs.technet.com/b/askcore/archive/2009/10/06/how-to-run-a-sysprep-and-capture-task-sequence-from-mdt-2010.aspx How to run a Sysprep and Capture Task Sequence From MDT 2010]		* [http://blogs.technet.com/b/askcore/archive/2009/10/06/how-to-run-a-sysprep-and-capture-task-sequence-from-mdt-2010.aspx How to run a Sysprep and Capture Task Sequence From MDT 2010]
	* [http://technet.microsoft.com/en-us/edge/windows-7-deployment--introduction-to-deployment-part-1-of-8.aspx Windows 7 Deployment with MDT2010 - VIDEOS]		* [http://technet.microsoft.com/en-us/edge/windows-7-deployment--introduction-to-deployment-part-1-of-8.aspx Windows 7 Deployment with MDT2010 - VIDEOS]

Lars: /* Sources */

2011-02-04T17:06:51Z

Sources

← Older revision		Revision as of 17:06, 4 February 2011
Line 50:		Line 50:
	==Sources==		==Sources==
	* http://technet.microsoft.com/en-us/solutionaccelerators/dd407791		* http://technet.microsoft.com/en-us/solutionaccelerators/dd407791
			* http://social.technet.microsoft.com/Forums/en/mdt/thread/033c0659-664b-4dc0-9d3d-c433bd5cb56d
			* [http://ruhle.wordpress.com/2009/10/20/injecting-intel-storage-drivers-into-xp-wims-via-mdt/\|Intel Storage Drivers into XP WIMs via MDT]
			* [http://deploywindows.net/archives/2261 MDT2010 Trouble Shooting the Log Files]
			* [http://blogs.technet.com/b/askcore/archive/2009/10/06/how-to-run-a-sysprep-and-capture-task-sequence-from-mdt-2010.aspx How to run a Sysprep and Capture Task Sequence From MDT 2010]
			* [http://technet.microsoft.com/en-us/edge/windows-7-deployment--introduction-to-deployment-part-1-of-8.aspx Windows 7 Deployment with MDT2010 - VIDEOS]

Lars: /* How It Works */

2011-02-04T16:33:52Z

How It Works

Lars: /* How It Works */

2011-02-04T15:36:14Z

How It Works

← Older revision		Revision as of 15:36, 4 February 2011
Line 20:		Line 20:

	== How It Works ==		== How It Works ==
	The actual MDT2010 program can be installed on any computer, but the deployment share where all the installation and capture files will be stored should be set up on a server. In this case, we are using<br />'''\\Hurricane\software\windows\deployment2'''.		The actual MDT2010 program can be installed on any computer, but the deployment share where all the installation and capture files will be stored should be set up on a server. In this case, we are using:<br />'''\\Hurricane\software\windows\deployment2'''.

	A detailed, step-by-step discussion of how to setup MDT2010, build and capture images, and deploy the final image is beyond the scope of this entry. For that, I strongly encourage you to go through the links in the Sources section of this entry. But generally speaking, the process goes like this:		A detailed, step-by-step discussion of how to setup MDT2010, build and capture images, and deploy the final image is beyond the scope of this entry. For that, I strongly encourage you to go through the links in the [[#Sources]] section of this entry. But generally speaking, the process goes like this:

	'''One time only tasks:'''		'''One time only tasks:'''

Lars: /* How It Works */

2011-02-03T21:51:05Z

How It Works

← Older revision		Revision as of 21:51, 3 February 2011
Line 20:		Line 20:

	== How It Works ==		== How It Works ==
	The actual MDT2010 program can be installed on any computer, but the deployment share where all the installation and capture files will be stored should be set up on a server. In this case, we are using '''\\Hurricane\software\windows\deployment2'''.		The actual MDT2010 program can be installed on any computer, but the deployment share where all the installation and capture files will be stored should be set up on a server. In this case, we are using<br />'''\\Hurricane\software\windows\deployment2'''.

	A detailed, step-by-step discussion of how to setup MDT2010, build and capture images, and deploy the final image is beyond the scope of this entry. For that, I strongly encourage you to go through the links in the Sources section of this entry. But generally speaking, the process goes like this:		A detailed, step-by-step discussion of how to setup MDT2010, build and capture images, and deploy the final image is beyond the scope of this entry. For that, I strongly encourage you to go through the links in the Sources section of this entry. But generally speaking, the process goes like this:

			'''One time only tasks:'''
	# Import the operating systems we'll need into the MDT deployment folder.		# Import the operating systems we'll need into the MDT deployment folder.
	# Import the drivers we'll need for our machines. We group them into two folders, 32- and 64-bit. 32-bit machines will automatically get drivers from the 32-bit folder, and 64-bit will get from the 64-bit folder.		# Import the drivers we'll need for our machines. We group them into two folders, 32- and 64-bit. 32-bit machines will automatically get drivers from the 32-bit folder, and 64-bit will get from the 64-bit folder.
	# Create a task sequence (TS) that deploys the OS to a reference machine. A reference machine is the computer we're going to use as the source for the image which will then be copied to all other machines.		# Create a task sequence (TS) that deploys the OS to a reference machine. A reference machine is the computer we're going to use as the source for the image which will then be copied to all other machines.
	# ~~Update the deployment folder, which will then generate the ISO file~~ that ~~can be burned onto a boot disk. Note: Clicking on update doesn't always re-generate the ISO file. Since these deployments are based on pulling the~~ image ~~over the network, most of the time the ISO file itself doesn't need to be changed. After the folder update, we'll see~~ a ~~message that tells us whether or not the boot file was re-created. If it was, we'll need to burn it to disk~~.		# Create a TS that captures an image from a reference computer.
	# Boot the reference machine with the MDT boot disk that was just created. In the list of options, we choose the task sequence we created to install the OS.		# Boot the reference machine with the MDT boot disk that was just created. In the list of options, we choose the task sequence we created to install the OS.
	# Once the task sequence has completed and the OS is installed on the reference machine, we can start installing the programs ~~that we want on all the computers~~ (eg: MS Office, Photoshop, etc.).		# Once the task sequence has completed and the OS is installed on the reference machine, we can start installing the programs (eg: MS Office, Photoshop, etc.).
			# After the programs have been installed, we open a command line window in Windows, and then run the the LiteTouch.vbs script to call up MDT:<br /> '''cscript.exe \\hurricane\software\windows\deployment2\litetouch.vbs'''<br />After it loads, choose the Capture an Image TS. This will create an image of the reference computer.

			'''Deploying a captured image'''
			# Import an operating system but instead of specifying an operating system, we import a WIM file (the WIM file was created when we did an image capture in the earlier step).
			# Next, create a TS to deploy that "OS," or new image that we just imported.
			# Update the deployment folder and burn a new boot disk if required.
			# Boot the target machine with the boot disk, and then choose to deploy the captured image onto that machine.

			The '''deploy image / modify the target machine / capture image''' cycle can be repeated indefinitely to support software updates or additions.

			''Note: Every time we make any kind of a change within the deployment folder, we must update the folder (right-click on the folder, then choose '''Update Deployment Share'''). At the end of the update process, if it says that the boot ISO file was changed, then we'll need to burn a new MDT boot disk, as well.''

	== Useful Tips ==		== Useful Tips ==

← Older revision		Revision as of 16:33, 4 February 2011
Line 22:		Line 22:
	The actual MDT2010 program can be installed on any computer, but the deployment share where all the installation and capture files will be stored should be set up on a server. In this case, we are using:<br />'''\\Hurricane\software\windows\deployment2'''.		The actual MDT2010 program can be installed on any computer, but the deployment share where all the installation and capture files will be stored should be set up on a server. In this case, we are using:<br />'''\\Hurricane\software\windows\deployment2'''.

	A detailed, step-by-step discussion of how to setup MDT2010, build and capture images, and deploy the final image is beyond the scope of this entry. For that, I strongly encourage you to go through the links in the [[#Sources]] section of this entry. But generally speaking, the process goes like this:		A detailed, step-by-step discussion of how to setup MDT2010, build and capture images, and deploy the final image is beyond the scope of this entry. For that, I strongly encourage you to go through the links in the [[#sources\|Sources]] section of this entry. But generally speaking, the process goes like this:

	'''One time only tasks:'''		'''One time only tasks:'''
	# Import the operating systems we'll need into the MDT deployment folder.		# Import the operating systems we'll need into the MDT deployment folder.
	# Import the drivers we'll need for our machines. We group them into two folders, 32- and 64-bit. 32-bit machines will automatically get drivers from the 32-bit folder, and 64-bit will get from the 64-bit folder.		# Import the drivers we'll need for our machines. We group them into two folders, 32- and 64-bit. 32-bit machines will automatically get drivers from the 32-bit folder, and 64-bit will get from the 64-bit folder (based on some settings we made on the deployment folder's properties).
	# Create a task sequence (TS) that deploys the OS to a reference machine. A reference machine is the computer we're going to use as the source for the image which will then be copied to all other machines.		# Create a task sequence (TS) that deploys the OS to a reference machine. A reference machine is the computer we're going to use as the source for the image which will then be copied to all other machines.
	# Create a TS that captures an image from a reference computer.		# Create a TS that captures an image from a reference computer.
	# Boot the reference machine with the MDT boot disk that was just created. ~~In the~~ list of ~~options, we choose~~ the ~~task sequence~~ we created to ~~install the OS~~.		# Boot the reference machine with the MDT boot disk that was just created. It will present us with a list of available TS's. We'll click on the TS we created for deploying an OS to a reference machine.
	# Once the ~~task sequence~~ has completed and the OS is installed on the reference machine, we can start installing the programs (eg: MS Office, Photoshop, etc.).		# Once the TS has completed and the OS is installed on the reference machine, we can start installing the programs (eg: MS Office, Photoshop, etc.).
	# After the programs have been installed, we open a command line window in Windows, and then run the the LiteTouch.vbs script ~~to call up MDT~~:<br /> '''cscript.exe \\hurricane\software\windows\deployment2\litetouch.vbs'''<br />~~After it loads~~, ~~choose~~ the ~~Capture~~ an ~~Image TS~~. This will create an image of the reference computer.		# After the programs have been installed, we open a command line window in Windows, and then run the the LiteTouch.vbs script:<br /> '''cscript.exe \\hurricane\software\windows\deployment2\litetouch.vbs'''<br /> This time, when presented with the list of available TS's, click on the TS for capturing an image. This will create an image of the reference computer.

	'''Deploying a captured image'''		'''Deploying a captured image'''
	# Import an operating system but instead of specifying an operating system, we import a WIM file (the WIM file was created when we did an image capture in the earlier step).		# Import an operating system but instead of specifying an operating system, we'll import a WIM file (the WIM file was created when we did an image capture in the earlier step).
	# Next, create a TS to deploy that "OS," or new image that we just imported.		# Next, create a TS to deploy that "OS," or new image that we just imported.
	# Update the deployment folder and burn a new boot disk if required.		# Update the deployment folder and burn a new boot disk if required.
	# Boot the target machine with the boot disk, and then choose to ~~deploy~~ the captured image onto that machine.		# Boot the target machine with the boot disk, and then choose to that new TS we created for deploying the captured image onto that machine.

	The '''deploy image / modify the target machine / capture image''' cycle can be repeated indefinitely to support software updates or additions.		The '''deploy image -> modify the target machine -> capture image''' cycle can be repeated indefinitely to support software updates or additions.

	''Note: Every time we make any kind of a change within the deployment folder, we must update the folder (right-click on the folder, then choose '''Update Deployment Share'''). At the end of the update process, if it says that the boot ISO file was changed, then we'll need to burn a new MDT boot disk, as well.''		''Note: Every time we make any kind of a change within the deployment folder, we must update the folder (right-click on the folder, then choose '''Update Deployment Share'''). At the end of the update process, if it says that the boot ISO file was changed, then we'll need to burn a new MDT boot disk, as well.''