When the task finishes this is the message i get i cant seem to find what has changed as i did it a few months ago with no issues.

I have an issue with a custom wim I have incorporated into my Task sequence. When I use a custom Wim, at the point where the MDT Tasksequence begins to "Install Operating System" it slows down to a crawl. What previously took 5-10 minutes on a previous wim, is now taking 30-50. When the "Install Operating System" task begins, it starts a at a very decent rate, you can see the percentage or time increasing/changing every few seconds with out issue, but when it gets to 30% completion, it starts to slow down dramatically. Eventually it will get to 100% Completion, where it will stay for the next 5 minutes, at which point it will apply the unattend.xml which will also take a very very long time to complete.

Once it reboots from applying the Unattend.xml everything runs normal.

My Setup:

I am using MDT 2012 - with WinPE3.0

To create my Custom Wim I did the following:

I created a brand new standard tasksequence, to deploy an OS to a machine, install updates then sysprep and capture to a wim. I set a custom variable in the tasksequence which set DoCapture=Yes. This allowed me to Capture the Operating system after the windows updates were done without having to do any additional steps. I then imported the Image into the operating systems section of my MDT Deployment share, and incorporated it into my previous Tasksequence.

I have also noticed that the size of the wim file I created is about 1.5 gigs larger than my previous wim.

Steps I've Taken for remediation:

I've tried rebuilding my boot.wim several times.

Increased the scratch size from 32 -> 64 -> 256 -> 512MB  

Removed unnecessary drivers from the boot.wim

Any ideas you guys might have with regard to getting my Install Operating System phase to speed up to normal speeds with be greatly appreciated.  Is there an extra step with the install.wim that I importing into MDT that I should be doing?

Hi all. I am trying to setup our custom USMT XML files to backup some important Lotus Notes database files. The files are in .nsf format, and they can have almost any name, usually UserName.nsf. These files can be located anywhere on the hard drive. However, there are some .nsf files that have specific names that I do not want to backup (log.nsf). I just can't get my XML to work. It backs up all the .nsf, but does not exclude the ones I want it to skip. Here is my XML:

<!-- This component backs up Lotus Notes files --><component type="Documents" context="System"><displayName>Migrate Lotus Notes Files</displayName><role role="Data"><rules><include><objectSet><pattern type="File"> C:\Lotus\Notes\Data\Archive\* [*]</pattern><pattern type="File"> C:\Lotus\Notes\ [notes.ini]</pattern><pattern type="File"> C:\Lotus\Notes\Data\ [*.id]</pattern><pattern type="File"> C:\Lotus\Notes\Data\ [desktop*.ndk]</pattern><script>MigXmlHelper.GenerateDrivePatterns ("* [*.nsf]", "Fixed")</script></objectSet></include><Unconditionalexclude><objectSet><script>MigXmlHelper.GenerateDrivePatterns ("* [log.nsf]", "Fixed")</script><script>MigXmlHelper.GenerateDrivePatterns ("* [perweb.nsf]", "Fixed")</script><script>MigXmlHelper.GenerateDrivePatterns ("* [help*.nsf]", "Fixed")</script><script>MigXmlHelper.GenerateDrivePatterns ("* [*help*.nsf]", "Fixed")</script><script>MigXmlHelper.GenerateDrivePatterns ("* [as_*.nsf]", "Fixed")</script></objectSet></Unconditionalexclude></rules></role></component>

Hey I just setup all of the applications on my MDT server.  Problem:  The applications is cluttered and not alphabetized.  Can someone direct me to the easiest way to cleanup the applications.xml and the ApplicationsGroup.xml

Thanks

Hi Forum

Hopefully a relatively simple question. What effect does the option "Organisation Name" have on machines that is placed in the initial part of the Task Sequence. About where you put in the local admin and Internet Home page.

I wondered where this would (might) pop up, and if WSIM is the place to remove this to be more generic, whereabouts could I find it?

Thanks in advance
NN

Hi,

I am using MDT Toolkit Update 1 integrated into SCCM 2007 (R3 SP2) to create Windows 2008 R2 OS deployments.  Recently, I was asked to have the ability of the engineer deploying the OS to be able to choose what applications get installed as part of the build.  Thaaa... I thought, this may be a problem. ...  Then I discovered UDI and became very happy.

Anyway, it seems UDI was really geared toward deploying Windows 7...but its working for Windows 2008 R2 too (at least, in my environment).  I was able to use UDI to present the diaglog box for the engineer to pick what applications that want installed as part of the build without any problems.  However, at the very end of the OS deployment, a deployment complete dialog box is displayed...

"Windows 7 Deployment Complete"  - with three tabs... 

Actual screen shot of this dialog box: http://andysal.files.wordpress.com/2010/07/12.png

1) Is there a way to disable this diaglog?

2) Is there a way to change this dialog to say "windows 2008" instead of "Windows 7?

Thank you...

I'm new to MDT.  I can use the standard TS template to install, sysprep and capture a vanilla Windows 8.1 to an image and deploy that image to a new computer. No problem.

I added MS Office 2013 as an application.  If try to add Office 2013 to the reference image, by selecting it in the setup wizard, MDT stops at the sysprep stage, the reference machine reboots, goes through the "we are setting thing up for you...", then displays "Can not find LTIBootStrap.vbs".

I'm using a Generation 2 VM for the reference image, with the x64 boot iso media.  The only way to start it is to change the boot order from file "bootmgfw.efi" back to the .iso.  The capture stage then continues.  The captured image then seems to be corrupt as the local list is blank so the deployment cannot continue.

Why does installing Office 2013 to the reference image cause this problem?  Vanilla OS images don't have this problem.  What am I doing wrong?  I'm quite new to MDT but can't find an answer to this.

Thanks.

We cannot get our product key to work in our unattend file. Below is the unattend file (the product key portion). Anyone notice anything wrong, or have any suggestions? I have also tried adding the product key into the custom.ini settings and that didn't work either. I know the product key works and I have double check to make sure I didn't fat finger anything. We are imaging Windows 7 Professional Computers using a Windows Server 2012 WDS/MDT server.

 <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
            <ComputerName></ComputerName>
            <ProductKey>XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-</ProductKey>
            <RegisteredOrganization>Our Company</RegisteredOrganization>
            <RegisteredOwner>US</RegisteredOwner>
            <DoNotCleanTaskBar>true</DoNotCleanTaskBar>
            <TimeZone>Central Standard Time</TimeZone>
            <ShowWindowsLive>false</ShowWindowsLive>
        </component>

Hi All, 

I am having some serious issues with trying to get the auto naming working. I am trying to pre-populate the computer name during a task sequence however the computer name will be built utilising variables added to the mdt database.

Naming Convention

The current naming convention for client devices is WXXYYYZZZZ as the client is in multiple countries and offices.  This is as below

W = Hardware type - S = Server , V = VM , L = Laptop , D= Desktop etc

XX = Country code - AU = Australia , US = United states etc

YYY = Site Office - Syd = Sydney , AUC = Auckland etc

ZZZZ  = numbering of device - 0001, 0020 etc

So a fully fomulated name will be something like LAUSYD009

MDT Database modifications

I have extended the MDT DB schema to include custom variables that can be entered in the Details tab. These variables are as below

LocationVarName - Updated in the locations part of the db and populated with the county code variables explained above in the naming convention

MakeAndModelVarName - Updated in the make and models part of the db and populated with the different hardware types expected

This was discovered and tweaked using the following link.

http://blogs.technet.com/b/deploymentguys/archive/2011/08/05/dynamic-computer-naming-in-zti-deployments-using-mdt-and-configmgr.aspx

By tweaking things in the above link i can effectively get the ZTIGather.log to create the OSD computername correctly according to its Make and model and Location Variables , i.e. LAUSYD  or DNZAUC. I can also run a build of a machine and can create unique computer names by also adding the  the Serialnumber variable. Personally that is the way id prefer to name the new devices  however the business is adamant that it wants to stick with the sequence numbering it is currently using (3k computers already out there in the environment with that naming convention). So based on above i believe i have the prefix part of the computer name down packed.

The second part is the sequencing of the devices. I had a look at another link as below which advises how to auto name a computer with a defined prefix and a sequence number. This link will check the macaddress of the computer and if the name matches the mac address it will re-issue the same name. If there is no link to the mac address it will generate a new name with a incremented sequence number.

http://www.deploymentresearch.com/Research/tabid/62/EntryId/103/Generate-computer-names-in-MDT-2012-2013-based-on-prefix-and-a-sequence-number.aspx

I have tweaked the above to use the serialnumber instead of the mac address as this is imported into AD currently. Again i have got this working and can effectively name comptuers PC-0001 etc and match against the MDT database for known computers. As Prepwork i have run a couple powershell scripts and audited the AD and imported all known computers and associated serial numbers into the MDT DB already. So my MDT DB knows all devices has currently a range of 0001 to 0159 populated under the computer names tab in the DB.

What i am trying to do is get these two solutions working in conjunction.  I am trying to get the initial part of the name (LAUSYD) created from the first step and then assign a sequence number to it and check the mdt db for a connection to serial number.  This is where i am stuck. Can anyone advise how i can combine these two solutions or if there is a better way to resolve this dilemma i am currently facing.

Thanks in advance for any advice

Hello all,

We use the 'total control' method for drivers, defining Drivergroup001 as "Windows 7 x64\%Model%" and placing the appropriate drivers into the folder structure.

During build, MDT correctly identifies the model, assigns the Drivergroup001 variable and copies all drivers from that folder into the c:\Drivers folder on the machine. Operating system is then applied however none of the drivers are then installed, causing the deployment to halt as the network card is unable to reconnect due to having no driver.

If I go into device manager and select to install drivers by browsing the c:\ drive it finds the correct drivers and installs them so I know the driver files were copied correctly.. just not installed.

Any thoughts? Thank you in advance!

MCITP Windows 7 Enterprise Administrator

Hi, I did the following:

1. Integration of updates into win 7 pro with sp1 x86 installation and creation of .iso image file
2. Creation of new deployment share in MDT 2012 update 1
3. Import of win 7 pro with sp1 x86 (with integrated updates) into deployment share
4. Creation of Task Sequence for deployment of that image
5. Customization of customsettings.ini and bootstrap.ini files to achieve completely silent installation
6. Editing of unattended.xml answer file (among other things new local admin user is going to be created)
7. Updating of deployment share
8. Creating of media
9. Updating of media
10. Burning .iso file to dvd
11. Installing a brand new virtual machine from .iso file

Silent installation went flawlessly (I only got a screen to choose media file (x86 or x64)), at the end I got a screen to choose user to log on with (administrator or new local admin user). I used the second one and as last step of installation I received the following information:

LiteTouch deployment failed, Return Code = -2147023589 0x8007051B

I have found on net that this return code means:

This security ID may not be assigned as the owner of this object. 

This is too generic, does anyone have experience with this error code? Thanks in advance.

Hi, fairly new to MDT after spending years with SCCM & OSD. 

I am trying to get drivers working for both Windows 7 and Windows 8.1. I have two task sequences Windows 8.1 deploy and Windows 7 Deploy. After looking at various posts on how to manage drivers I got Windows 7 working by adding Out-of-Box drivers for each model creating a folder for each model (retreiving the model name from WMI)

so e.g I have folder structure Workstation\Windows 7\x64\Latitude E6410

Then in custom settings.ini I added

Then in the task sequence I have an Inject Drivers step, and select "Install all drivers from the selection profile" with select profile set to nothing. This seems to work fine. 

How do I get t his working for Windows 8 models ? Just add another DriverGroup like

DriverGroup002=Workstation\Windows 8\x64\%model% or would I need to set e.g task sequence variables  in the task sequence for the OS ? Can I set DriverGroup001 as a task sequence variable ?

Appreciate any help as I tad confused ! Thanks 

Hi

My end goal is to deploy a custom x86 image to a UEFI device (tablet) using a USB stick. It is likely that my .wim file will be >4GB, but for now, I'm just trying to get the process working with a standard OEM <4GB .wim file.

As per this post, I have performed steps under sections 5.1, 5.2 and 5.3 MANUALLY, by booting the tablet using a WINPE 5.0 USB and running

1) diskpart /s E:\CreatePartitions.txt 

and

2) E:\ApplyImage E:\Images\ThinImage.wim

Q: Above worked perfectly and it's exactly what I'm looking for.  How do I incorporate 1) + 2) into MDT, or do I simply attempt to replicate the code from 1) + 2) under "Format and Partition Disk" under PreInstall\New Computer only step?

Any advice or pointers would be really appreciated.

Many thanks in advance.

Hello All,

I have an issue deploying Windows 7 using MDT 2013. About every 1 in 4 times the installation fails with "Unable to find the sms task sequencer". Looking at the logs it shows it can't find the tsmbootstrap.exe file that should be in the tools folder. In fact the tools folder doesn't exist in the MININT. Neither is there an X drive mapped to the deployment share which also contains the tools folder although I don't know if there should be.

If you boot into recovery mode and diskpart / clean the disk and run the deployment again it works. Its not happening on every machine and once you have manually cleaned the disk with diskpart the error does not seem to be reproducible.

The caveats are that I am installing windows to partition 3 on the drive (from reading other posts this seems to be frowned upon when using MDT but I can't really find out why) and the disks I am imaging may have old Ghost images of windows 7 or XP on them.

Anyway - any ideas greatly appreciated.

Thanks

Just started having this issue after rebuilding my 2010 DS into 2012. Using a standard task sequence, I am not doing any special with the DiskPart either. Installing to Disk 0, Partition 1. After it goes through the PostInstall phase, it is supposed to reboot and then go into Windows and continue the task sequnce. Instead, I get a message that it is unable to find the SMS Task Sequencer. The error in the log is basically, could not locate the TSMBootStrapper in the standard locations. I look in the MININT folder and the Tools folder is missing. If I manually copy the folder from the DS and manually kick-off the LiteTouch.wsf it then continues just fine.

I need help figuring out why the folder is not being copied into the MININT folder before the reboot.

This seems to only be happening on laptops. When I deploy to a desktop or a VM, the task sequence proceeds without issue.

Hi

I can not find the user manual (and other manuals) of the Windows ADK 8.1 Update in docx or pdf format. How come?

Thanks

Bye

Balubeto

Hi all.

I'm looking for some advice around corporate branding a Windows 8.1 deployment. I.e.

• Wallpaper for all users
• Lockscreen image for all users
• User account pictures
• OEM info

I have developed a script for Windows 7 which deploys as an application during my build and capture task sequence. This script sets background wallpaper for all users, OEM logo and information and user account pictures. I then use CopyProfile in my ConfigMgr task sequence when deploying the captured image which sets the same configuration for all users. This works really well and very consistently.

I'm struggling to get the same thing working with Windows 8.1. Is it possible to do this in the same method as Windows 7? I've been doing lots or trial and error and so far the only thing that seems to work pretty well is the user account pictures.

I've tried replacing img0.jpg after taking ownership, and this partly works, but as soon as you run a SFC /SCANNOW it replaces the file with the default Windows image.

Is there a proper way to be doing this? I'm aware we could do a lot of this via group policy, in which case I will just copy down the images and leave it at that, but I would much prefer to have my captured reference images ready to roll right after the deployment. I'm aware I could perhaps use GPO Packs but due to the broken MDT 2013 support for GPO Packs and Windows 8.1, and the lack of official support for 8.1 in the Security Compliance tool to generate the proper GPO Pack, I'd rather script it as with previous OS's if possible.

Any help would be much appreciated.

I've managed to begin the image capturing process using MDT and the LiteTouch.vbs script. The source machine sysprepped and rebooted and began image capture fine. The capture process bar appears to be stuck at 13% with 10:54:39 remaining. I understand that it should take a long time to capture the image, but looking at the destination computer, the file size has not grown past the initial hour or so of activity, or since 30 minutes when I first noticed a problem. 

Am I hung here with a bad capture? Everything I've seen with people having issues it has been getting the process started. Do I just need to wait my 10 hours and check back in the morning? If it is hung, what steps should I take to halt the process and try to restart/continue it?

My source PC has an 80GB HDD...