Keep extra partition on deployment with MDT 2013

hello all,
I am using MDT 2013 to make the
deployment of some workstations in the company,
however they all have an extra
partition (D: \),
doing some testing I noticed that the
MDT does clean the entire
disk, not just on the C:\ drive.
Is it possible to get the MDT format
just drive the system keeping
the extra drive (D:\)?
Thank you.
Eduardo Sena | Microsoft Certified Professional | Embaixador Windows 8 | MVP Windows-Expert IT Pro | [email protected] Blog - www.eduardosena.com.br

if you are just replacing the OS, then I recommend the "Refresh" scenario. Refresh will take an existing Machine and refresh it to a new OS version, persisting the existing partition configuration.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Similar Messages

Creating Windows 8.1 master image with MDT 2013,cannot capture .WIM

I am having an issue with creating a master image with Windows 8.1 and MDT 2013.
I have followed extensive tutorials on how to create a master image using Microsoft Deployment Toolkit. my goal is to have a fully configured windows 8.1 image which I can deploy through Windows Deployment Services. I have been relatively successful thus far,
except for one issue I have run into, which is successfully capturing this image as a .WIM.
I have successfully created a task sequence and the task sequence is able to run all the way through until the final step. Essentially the task sequence is supposed to install Windows and Office, then suspend the task sequence to allow me to make customisations
to the start screen and desktop background, and I simply click resume task sequence, and the task sequence should sysprep reboot and capture the machine image as a .WIM file.
the task sequence is able to sysprep the machine, but upon rebooting it boots into out of box experience, and does not create a wim file. I receive an error saying: "cannot find script file C:\ltibootstrap.Vbs" after the machine completes OOBE
I am using Windows Server 2012 r2, creating my Master machine image using hyper-v, and my master image is running Windows 8.1.
Any help would be greatly appreciated.

I'm not sure about the sequence of steps here. Try taking your captured.wim file and deploying it using MDT again, or at least to another machine. MDT sometimes leaves extra files around on the captured machine, so simply rebooting it may not get a accurate
test results.
IF you are getting the ltibootstrap.vbs it is most likely because there is a stray unattend.xml file somewhere in your image that is looking for this file. Crack open your Wim file and search for any unattend.xml files.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Office365(Click to Run) Deployment with MDT Offline Media

Hi,
I have a scenario where i have to deploy Office365 using click to run with MDT offline media. Now the problem is with configuration.xml file in which we specify the source path of office files.
Here in this scenario as i have to deploy client machines with offline media, so in this case what will be the path in the config.xml file?
For testing purpose, after downloading the office source files, placed the setup.exe,config.xml file and office source folder in a same folder. Here is the config.xml file that i am using
<Configuration>
<Add SourcePath=" " OfficeClientEdition="32" >
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
</Product>
</Add>
</Configuration>
In source path, i leave it blank,so that it will use the office source files which was saved in the same folder.
Then in MDT server, created a new application for Office365.In command line used the command :- setup.exe /config configuration.xml
Created a new task sequence for OS deployment and added the step install application for installation of Office365.
After creating a selection profile for the deployment, created a offline media for deployment of client machine.
Now while i am running the offline media on the bare-metal machine, after OS installation the deployment got stuck at step install Office 365. Got error message pop up, according to which internet connection needed during installation process so that the
click to run set-up will download the office source files, It means this will not use the previously downloaded file which was saved in the same folder.
So this is what my problem is.. How can i customize the configuration.xml file so that i can install office 365 with offline media.
Regards
Pallavi

<Add SourcePath=" "
....In source path, i leave it blank,so that it will use the office source files which was saved in the same folder.
As per
https://technet.microsoft.com/en-us/library/jj219426.aspx#BKMK_AddElement
SourcePath indicates the installation source path from which to install Office when you run the Office Deployment Tool in
configure mode. If you don’t specify SourcePath in
configure mode, Setup will look in the current folder for the Office source files. If the Office source files aren’t found in the current folder, Setup will look on Office 365 for them
So, for the /configure mode, you should remove the Sourcepath element completely - do not specify as <space>
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Surface Pro 3: unable to reimage with MDT 2013

MDT 2013, Windows 8.1 with all udpates in wim file.
Download all drivers and firmware
http://www.microsoft.com/en-us/download/details.aspx?id=38826 to out of box. Update the Surface Ethernet Adapter in winpe. when i am booting i am getting following error, seems like its looking for "VEN_11AB&DEV_2B38&SUBSYS_045E0001&REV_00"
i search for hwdid, but didn't find anythings. Any help?
orion

Hi there,
I am using MDT 2013 on a WDS 2008 R2 and everytime i tried to image the tablet via PXE boot through the Surface Pro 3 ethernet adapter, i get this error:
Wizard Error:
A connection to the deployment (my deployment share) could not be made.
The following network device did not have a driver installed.
PCI\VEN_11AB&DEV_2B38&SUBSYS_045E0001&REV_00
Retry: Try again to connect to the deployment share.
Cancel: Give up, cancelling any in-progress task sequence.
PLEASE HELP!
YOu most likely need to add the microsoft networking adapter to the MDT console, and explicitly add it to the WinPE group. Don't forget to rebuild the deployment share so it regenerates the WinPE iamge.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Applying GPO Packs on Server 2012 R2 with MDT 2013

Hi All,
I'm having a problem applying a GPO Pack to Server 2012 R2 via MDT 2013 LTI offline media.
I'm using a standard server task sequence. I've copied my GPO Pack files (created with local GPO export) to the following directory:
DeploymentShare\Templates\GPOPacks\WS2012R2-MDTGPOPack
GPOPack.wsf has been modified with the following
If(Left(strOpVer,3) = "6.3") and (strProductType <> "1") then
       strOS = "WS12R2"
        ElseIf(Left(strOpVer,3) = "6.3") and (strProductType = "1") then
       strOS = "Win81"
        ElseIf(Left(strOpVer,3) = "6.2") and (strProductType <> "1") then
       strOS = "WS12"
ZTIApplyGPOPack.wsf has been modified with the following:
If (Left(sOSVersion,3) = "6.3") and oEnvironment.Item("IsServerOS") then
                   sOS = "WS2012R2"
                oLogging.CreateEntry "Using Windows Server 2012 R2 GPO Pack", LogTypeInfo
           ElseIf (Left(sOSVersion,3) = "6.3") and Not(oEnvironment.Item("IsServerOS")) then
                   sOS = "Win81"
                   oLogging.CreateEntry "Using Windows 8.1 GPO Pack", LogTypeInfo
           ElseIf (Left(sOSVersion,3) = "6.2") and oEnvironment.Item("IsServerOS") then
               sOS = "WS2012RTM"
After creating new media I've copied my GPO Pack to the media directory:
MDTMedia\Content\Deploy\Templates\GPOPacks\WS2012R2-MDTGPOPack
After I create the ISO and mount in a VM the LTI works fine and I can see in temp\ZTIApplyGPOPack logs that the GPO pack is copied to C:\minint and executed but none of my GP settings are applied.
Any ideas?
Thanks in advance

if you are using offline media (and not over the network deployment) maybe you are having this problem:
http://social.technet.microsoft.com/Forums/en-US/be2c05a0-620c-4b64-a82f-18ccc9f6cec5/apply-gpo-pack-offline-media-does-not-apply?forum=mdt

WINPE User & Keyboard Locale with MDT 2013 & Windows 8.1

Hi
I'm using MDT 2013 to deploy win8.1 (ADK 8.1 installed and so on) but I'm having trouble to set the keyboard layout when the Wizard (hta) is loaded.
We are serving multiple countries so different keyboard settings need to be pushed for our operators when they go through the Wizard in boot.wim/PE phase.
I opened up the boot.wim file that is generated when you update the deloyment share and generate the litetouch boot iso.
In there I see that a basic unnattend.xml is being used which specifies the 0409:0000409 (en-US) locale.
I was under the impression that if we made different Task sequences with their own unnattend.xml we could set the WINPE locale in the WINPE phase via the amd64_xxxx_WINPE_Neutral_xxxx component but it doesn't seem to work that way.
I know you can provide a locale in bootstrap.ini but that's a general setting for
all deployments ...
Anyone any ideas?
My next step would be to add skipbdewelcome screen in bootstrap.ini and then have some sections in the customsettings.ini (bound to gateway or site or whatever) to set LOCALEs in there ....
jgs

Hi,
Sorry for my dilatory reply. According to your description, I doubt whether your Unattened.xml file was set correctly.
To set default InputLocale during deployment, the correct format should like this:
<InputLocale>0409:00010409</InputLocale>
<SystemLocale>en-us</SystemLocale>
<UILanguage>en-us</UILanguage>
<UserLocale>en-us</UserLocale>
From:
http://technet.microsoft.com/en-us/library/cc749191(v=ws.10).aspx
In addition, here is another thread which is similar with your problem, may be helpful with your question:
http://social.technet.microsoft.com/Forums/systemcenter/en-US/9af61b5c-6407-44b9-87c4-a4044a94729c/change-regional-settings-keyboard-layout-and-locale-in-task-sequence?forum=configmgrosd
Roger Lu
TechNet Community Support

Office 2010 post SP2 updates deploy with MDT

So I'm looking forward to deploy my office 2010 pro plus (VLK media, activating via KMS host) with MDT, and I have some configs setup using Office Customization Tool to install it. I have the SP2 installer that installs after Office 2010 is installed.
Everything works well, however until i realize that are still a few hundred MB's of update (security patches etc) after the SP2 install. So allowing MDT to install the update on run time is not ideal ( consumes more time and bandwidth) so my question is where
can I get all the post SP2 updates for office pro 2010? (I'm assuming they're all .msp files where i can dump it all into the update folder in office).
Thank you for your feedback!

Hi Jack,
Microsoft Office sustained Engineering team publish news about security updates, public updates, service packs for Office in this site:
http://blogs.technet.com/b/office_sustained_engineering/archive/tags/office+2010/default.aspx
You can find all the Office updates that released each month in this site. However, the updates that applicable to your computer are really depend on your setup environment, not all that released are applicable.
I would suggest you to go to Windows Update, and Check for updates. Windows Update will automatically search updates that are applicable to your computer. You can choose to download the updates manually and save it
to your computer.
Thanks,
Ethan Hua CHN
TechNet Community Support

Help with Windows 8.1 Update 1 Offline Deployment using MDT 2013

Hi guys,
Hoping that someone has encountered this problem and that there is a simple solution that I am overlooking. Essentially the problem we seem to be having is that after the OS is installed the process of updating the boot partition incorrectly updates
the boot partition on the offline media, rather than on the local disk. Because UEFI requires boot media to be formatted FAT32 and our deployment is a little on the heavy side (upwards of 40GB) we are generating multi-partition boot media and
this seems to be creating a problem, our previous Windows 7 offline media (single NTFS partition) worked perfectly.
By looking at the BDD.log I can see where it appears to examine the potential boot partitions, finds the local disk boot partition and the external usb hdd boot partition and chooses to write to the external. The task sequence restarts the machine shortly
thereafter at which point the device cannot boot with an error "No operating system found."
Thank you in advance for any assistance.

Hello Erik,
it seems to be a bug in MDT.
The routine in ZTIDiskUtility.vbs is looking for the last available boot device:
For each oWMIDiskPart in AllDiskPartEx ( " WHERE Bootable = TRUE or BootPartition = TRUE " )
  oLogging.CreateEntry "Found bootable drive: " & oWMIDiskPart.Path_ , logTypeVerbose
  set oDiskPart = new ZTIDiskPartition
  set oDiskPart.DiskPart = oWMIDiskPart
  set oDisk = oDiskPart.GetDiskObject
  If oDisk.isOSReady( sOSBuild ) then
   set oLogical = oDiskPart.oWMIDrive( bForced )
   If isValidObject(oLogical) then
    If not bBootFiles then
     oLogging.CreateEntry "Found bootable drive (No Boot File Test) [ " & oLogical.DeviceID & " ]: " & oLogical.Path_ , logTypeInfo
     set GetBootDriveEx = oDiskPart
     ' My change
     Exit For
    ElseIf oFSO.FileExists( oLogical.DeviceID & "\ntldr" ) or oFSO.FileExists( oLogical.DeviceID & "\bootmgr" ) or oFSO.FileExists( oLogical.DeviceID & "\EFI\Microsoft\Boot\bootmgr.efi" ) then
     oLogging.CreateEntry "Found bootable drive [ " & oLogical.DeviceID & " ]: " & oLogical.Path_ , logTypeInfo
     set GetBootDriveEx = oDiskPart
    Else
     oLogging.CreateEntry "No boot files found: " & oLogical.Path_ , logTypeInfo
    End if
   End if
  End if
next
I implemented an "Exit For", so you will get the first possible boot drive.

Deployed a new computer with MDT 2013, but Windows licensing did not give me an initial grace period

Hi all,
Strange issue. I have created a Windows 7 x64 gold image to be deployed. When creating the image, I allowed Sysprep to rearm Windows. I've deployed about 10 computers in the past week and everything has worked fine.
Yesterday, I deployed another two computers. One works fine, but when I logged into the second one, I was greeted with the you need to activate Windows now screen. I was confused so I ran slmgr /dlv and sure enough my license status was not "Initial
Grace Period" but instead "Notification." (by the way, it did show remaining rearms as 2, which is expected since it was rearmed with sysprep when capturing the image, so we know it was in fact rearmed).
So my question is how and why did this happen? I was in a hurry so I just ran slmgr /rearm to burn off another rearm. I plan on putting in a KMS server at the end of the week, but I'm worried if I should redeploy the image to this machine since something
appears to be wacky.
Anyone seen this before or have any thoughts on the matter?

Either way, it was correct when I checked it today so maybe it corrected itself after Windows was installed? Not sure how else to explain this one.
Me either.
After Windows is installed, if you are domain-joining, the clock will sync to your Domain Controller.
If not domain-joined, Windows will try to sync to time.windows.com (or similar).
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Image engineering of windows xp with WADK 8.1 and deployed with MDT

Hello,
We know that image engineering of Windows XP with WADK 8.1 is not compatible then even if there is any ways to achieve this anyway....(by refresh scenario or any enabling setting).
Thanks
Richa KM

No you need the older version MDT 2012 Update 1 with ADK 8.0 to deploy XP

What To Expect With MDT 2013 Multicast from WDS 2008 R2?

I am having a hard time finding out what to expect when setting this up. I don't think anyone has posted a demo video showing it in action or even a detailed blog with screenshots. The only multicast videos I have seen were old ones of WDS multicasting
that had no reference to MDT.
What I understand is, once I have working WDS integration with PXE boot, all I need to do is go into properties of the deployment share then select the option to enable multicast support and then update the deployment share. After that everything is
supposed to work as long as the network supports multicasting.
So, how does it work from there? How do you take advantage of it?
When I boot up a workstation to deploy to, where do I configure the specific deployment task to use multicasting (or not if I am just imaging a single system)? When I boot the second and third machine to image, what are the steps to join the ongoing
multicast? Do you pick the deployment task from the wizard again or does any machine booted to MDT join any in-progress multicast automatically?
Can you use the wizard to select different optional installed applications for different machines when using a multicast?
If you are imaging 30 workstations, can you configure it start the multicast when the 30th connection is made or does it start as soon as the first one joins?

Once multicasting is set in the deployment share it will become the default method of deploying an image for clients connecteing to that deployment point. As far as I'm aware the boot disk does not need to be updated for this to take affect.
Multicasting in WDS is a rolling session.. It will start as soon as the first client connects and will end when the last machine finishes. Machines can come and go throughout the session.
There are more options that can be applied (such as number of machines to wait for) but you need to change registry settings to do this.
I did have a GUI for this on my to do list.. but never got around to it. Maybe it's worth another look.

Error when trying to connect to deployment share MDT 2013 - Using Virutal Machine as Refernce image

Hello all
I cant seem to move forward on this build and capture. I am using Hyper-V on windows 8.1 to perform the B&C on VM but keep getting this error when I boot the VM
H
Phil Balderos

IT's common practice to add the credentials (domain\username+Password) directly into the bootstrap.ini and/or customsettings.ini file to allow for totally hands off building of corporate images. Check to see if have the right credentials added in.
Additionally, you may have network connectivity problems. Best thing to do while in WinPE is to press F8, that will bring up a cmd.exe window, allowing you to do some manual debugging.
ipconfig /all
ping opsit12226
net use * \\opsit12226\deploymentshare$ /u:opsit1226\administrator *
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

MDT 2013 - A Connection to the deployment share could not be made - DHCP Lease was not obtained

First, let me give you some context:
Framework: MDT 2013 with MS SDK 7.1
Task Sequence: Standard Client TS with sysprep and capture.
Target workstation (build workstation): VM Guest on ESX 5.5 host, 8 vCPU, 8GB RAM, LSI Logic SAS Controller, E1000 NIC, SSD DAS
Behavior: The VM loads and installs the OS fine in PE, VM boots into OS successfully and resumes the TS, after the first system reboot, the error message occurs and it reads:
A connection to the deployment share (\\*********\DeploymentShare$) could not be made. DHCP Lease was not obtained for any Networking device! Possible Cause: Check physical connection. Retry:...... Cancel:.....
While observing this error, I didn't notice the NIC hadn't completely initialized and obtained an IP yet (network adapter icon in systray), additionally hitting retry after the NIC was initialized resumed the TS.
This behavior reoccurs with several subsequent reboots until a few more applications (Citrix Receiver, VMware Tools) with services are installed which seem to then slow the system boot-up time and then allows the TS to start after the NIC has initialized.
From several posts I've read on this forum, this particular behavior was alleviated by a "wait for IP lease" mechanism built into the TS engine which was introduced in MDT 2010 SP1, I wasn't able to find any other confirmation whether
this mechanism is still in effect with MDT 2013. Another point worth mentioning from several other posts I was able to find is that this behavior appears to manifested itself on target workstations with SSDs, which would somewhat explain the faster
TS load time vs waiting for an IP lease. I've also tried to replicate this behavior in a non-SSD and low-performance VM environment and I wasn't able to replicate it.
My question: Does anyone else have experienced this behavior with MDT 2013 and if so, how did you resolve it? Or is this a bug?

I have this issue intermittently as well. For us, it coincided with the deployment of IP phones, which meant PoE switches all around. However, the problem persisted even after we turned off PoE to the ethernet ports from which we normally PXE
boot.
As this issue has been intermittent, I've backburnered it. When it does happen, I just wait for the lease to arrive then rerun the wizard.
Thanks for the feedback, that's true the TS can be resumed manually once the lease has occured but it defeats the purpose of an automated TS if I have to keep an eye on it and intervene if I need to.
The network guys here recommended putting wireshark or network monitor on it and figuring out just what the heck is going on. Basically, what Keith Garner said. They also disabled PortFast awhile back to see if that made any difference, and it did
not.

Eufi partition on MDT 2013

I am using LT for deploying Windows desktop with MDT 2013. What I would like to do is to be able to customize the partition layout for any eufi capable system. I know how to create a diskpart script to do the job. If I am going to create a custom Task sequence
for the eufi layout, how does MDT handle the situation if the system is not uefi capable\enabled?
Thanks

Hi,
You can create an answer file to customize disk configuration.
DiskConfiguration
http://technet.microsoft.com/en-us/library/ff715671.aspx
The unattended file is applied to both BIOS-Based and UEFI-based computers. If you don’t want the configuration applied, you have to remove the file.
In addition, answer file should be placed to the right place.
Methods for Running Windows Setup
http://technet.microsoft.com/en-us/library/cc749415(v=ws.10).aspx
Please notice “Implicit Answer File Search Order”.
Hope this helps.

MDT 2013, Deploying Windows 8.1 on Surface and Dell Venue Tablets

I'm having numerous issues with Capturing Images and Deploying to Windows 8.1 Tablets. We are currently using Surface Pro 1, 2, and Dell Venue 11 Pro tablets. I am using a Windows Server 2012 computer with MDT 2013 installed. I can't get the tablets
to:
1-sysprep and capture using MDT 2013
2-Deploy a Task Sequence with a WIM and other applications attached. (I've tried using the simple standard task seq option with no luck)
3-I found another way to get a WIM (using imagex) but when i deploy task sequence it ignores my selection of applications to install outside the WIM and only installs the WIM (WIM 14gb = Win 8.1 Ent, Office 2013 x32, MS Updates)
Any help would be greatly appreciated. Everything is being performed within the LAN and with USB 2.0 thumbdrives for media.

Hi altimav8,
Are you trying to find out how to deploy Surface Pro method? Before capture the Surface pro image please download the latest drivers for the surface and made sure that they
were the only drivers that were going to be deployed. There have a specific MDT deploy support forum more about the MDT deploy related issue you can ask in MDT support forum.
MDT support
forum:
https://social.technet.microsoft.com/Forums/en-US/home?forum=mdt
The related guide:
Surface Pro - Enterprise Deployment Quick Start Guide
http://download.microsoft.com/download/2/0/7/2073C22F-2F31-4F4A-8059-E54C91C564A9/Surface%20Pro%20-%20Enterprise%20Deployment%20Quick%20Start%20Guide.pdf
Thanks for your understanding and support
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Keep extra partition on deployment with MDT 2013

Similar Messages

Maybe you are looking for