MDT 2012: Force MININT and _SMSTaskSequence on C Drive

April 25, 2012, 3:55 am

≪ Previous: Deleted Outlook Express folder after migration from Windows XP to Windows 8.1 with MDT.

Hi,

I'm deploying Windows 7 X64 using MDT 2012, I format 3 partitions at the beginning of the task sequence and I assign them specific drive letters during the state restore phase.
I had no problem with MDT 2010 but since I'm using MDT 2012 MININT and _SMSTaskSequence folders are created on partition 2 so when I assign my drive letters deployment fails.
I tried to force SMSTSLocalDataDrive in cs.ini but it seems that MDT doesn't care, I can see in the variables.dat that the C drive is selected but folders are still in my second partition.
Any help?

My Blog: DeployXP [Under Construction]| Viadeo:Mathieu Ait Azzouzene | Linkedin:Mathieu Ait Azzouzene

↧

Updating many a task Sequence

October 1, 2015, 8:45 am

≫ Next: Feature Request for MDT / SCCM - Could you add in functionality to deploy WICD Provisioning Packs?

≪ Previous: MDT 2012: Force MININT and _SMSTaskSequence on C Drive

Hello

I have many task sequences in MDT 2013 Update 1 that install many applications (i guess like many other people).

For EXAMPLE Firefox

Now in the task sequences this is set to install say 40.03 but then when version 41.0 comes out, i have been adding this in as a new Application to the MDT workbench and then updating each Task sequence replacing the firefox 40.03 version with firefox 41.0.

This takes some time, so my question is

Is there a better/quicker way to update all my task sequences with a newer version?

Thanks

↧

Feature Request for MDT / SCCM - Could you add in functionality to deploy WICD Provisioning Packs?

September 25, 2015, 12:56 pm

≫ Next: MDT 2013 REFRESH TS

≪ Previous: Updating many a task Sequence

With windows 10 and the new adk and mdt it would be really nice if you could add a task sequence to deploy provisioning packs rather then having to DISM them into the wim that way if you are still testing out different options it would save a TON of time.

↧

MDT 2013 REFRESH TS

October 1, 2015, 10:26 am

≫ Next: Applying unattend.xml with DISM.exe is very slow

≪ Previous: Feature Request for MDT / SCCM - Could you add in functionality to deploy WICD Provisioning Packs?

I am working on trying to get the REFRESH (user backup) scenario working, but I am at a loss right now on exactly how it is supposed to be ran (while logged on or PXE)?

I have no issues deploying an image while PXE booting, but I would really like to get the REFRESH (user backup) portion working. This will allow me a quicker imaging turn around, due to having to manually backing up each users data. Also is it possible to define user(s) or last logged on for the user backup?

Thank you for all the help in advance!

↧

Applying unattend.xml with DISM.exe is very slow

October 1, 2015, 1:17 pm

≫ Next: MDT 2012 / Windows 7 SP1 / ZTIWIndowsUpdates.wsf SVCHOST.EXE 2 Hour Delay

≪ Previous: MDT 2013 REFRESH TS

Hi guys,

There are some posts about this on the forum, but I was wondering if you guys could suggest what I'm doing wrong. We have many different model Dell computers that we support and I imported Dell family packs into MDT to have all the drivers. However, it seems like whenever we image, it takes a long time during the step "Applying unattend.xml with DISM.exe". Is there anything I can do to speed it up? I don't want to create a task sequence for each model for each image since it would be 30+ task sequence..Thank you :)

↧

MDT 2012 / Windows 7 SP1 / ZTIWIndowsUpdates.wsf SVCHOST.EXE 2 Hour Delay

September 25, 2015, 6:11 am

≫ Next: Unattended IE11 Settings not getting set

≪ Previous: Applying unattend.xml with DISM.exe is very slow

Hi Guys,

i have a strange problem while image creation in MDT 2012.
We start from scratch (Windows 7 Professional with SP1 X64 and X86 ISO). Boot up two VM's in VSPHERE with 4GB RAM.
Then using the WindowsUpdate.wsf to poll internal WSUS-Server.
The Machines are stressed my svchost.exe for like 90-120 minutes before the Download and Installation Progress begin.
Machines are connected with 10GBIT/s.

The problem happends here:
2015-09-25   12:20:38:584   808   a0c   Handler   Using CBS interface ICbsSession7
2015-09-25   12:20:40:097   808   a0c   PT   +++++++++++ PT: Synchronizing extended update info +++++++++++
2015-09-25   12:20:40:097   808   a0c   PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://DIC-ADS001.our-domain.de/ClientWebService/client.asmx
2015-09-25   12:33:55:745   2108   b4c   Misc   =========== Logging initialized (build: 7.6.7601.18847, tz: +0200) ===========
2015-09-25   12:33:55:745   2108   b4c   Misc      = Process: c:\program files\windows defender\MpCmdRun.exe
2015-09-25   12:33:55:745   2108   b4c   Misc      = Module: C:\Windows\system32\wuapi.dll
2015-09-25   12:33:55:745   2108   b4c   COMAPI   Registered OnCompleted callback in GIT, cookie=256
2015-09-25   12:33:55:761   2108   b4c   COMAPI   -------------
2015-09-25   12:33:55:761   2108   b4c   COMAPI   -- START -- COMAPI: Search [ClientId = Windows Defender]
2015-09-25   12:33:55:761   2108   b4c   COMAPI   ---------
2015-09-25   12:33:55:761   2108   b4c   COMAPI   <<-- SUBMITTED -- COMAPI: Search [ClientId = Windows Defender]
2015-09-25   14:03:05:400   808   a0c   Agent   Update {A9134E4A-3B6F-4633-AA8F-9520F188FBF8}.101 is pruned out due to potential supersedence

See the Full Log here:

https://drive.google.com/file/d/0B8qYQyX2Z98dSW4tUEVkc3VQQ3M/view?usp=sharing

We already updated to latest Windows Update Client und patched WSUS-Server ...

The WSUS-Report is generated at 14:04:00

There are about 300 Updates to install...

Any Suggestions? I have no idea what to do further.

Thanks

↧

Unattended IE11 Settings not getting set

October 1, 2015, 8:54 am

≫ Next: Setting DesktopBackground in Unattend.xml

≪ Previous: MDT 2012 / Windows 7 SP1 / ZTIWIndowsUpdates.wsf SVCHOST.EXE 2 Hour Delay

I have two options in the Unattended answer file that are not being applied to the deployment. I have both CompatibilityViewDomains and LocalIntranetSites set. It looks like this:

The Unattend.xml file looks like this:

-<component language="neutral" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="amd64" name="Microsoft-Windows-IE-InternetExplorer" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><Home_Page>www.google.com</Home_Page><DisableWelcomePage>true</DisableWelcomePage><DisableFirstRunWizard>false</DisableFirstRunWizard><CompatibilityViewDomains>192.168.10.21</CompatibilityViewDomains><LocalIntranetSites>http://192.168.10.21</LocalIntranetSites></component>

The homepage gets set correctly but I believe that's because I also have that set in the Task Sequence settings as well. What am I missing? Why won't these settings get applied? I am using MDT 2013 to deploy Windows 7 x64. I have IE 11 already installed in my reference image.

Dan Chandler-Klein

↧

Setting DesktopBackground in Unattend.xml

October 1, 2015, 2:53 pm

≫ Next: MDT 2013 U1 - Windows 10 - FORCE driver selction?

≪ Previous: Unattended IE11 Settings not getting set

I upgraded to MDT 2013 update 1 today. Built a new task sequence for my existing Windows 8.1 image. Ran a test deployment and everything seems to have worked just fine, however the Theme did not get set.

I set my theme using the unattend file, in the oobeSystem pass by adding Themes to Windows-Shell-Setup. I then specify the background, theme name and window color. It previously worked to set a "default" theme in this manner, but now it didn't. Anyone else run into this? I couldn't find any typos in my unattend file. I'll test more as I rebuild my other task sequences over the next few days.

If this post is helpful please vote it as Helpful or click Mark for answer.

↧

MDT 2013 U1 - Windows 10 - FORCE driver selction?

October 1, 2015, 2:02 pm

≫ Next: Updating to MDT 2013 Update 1

≪ Previous: Setting DesktopBackground in Unattend.xml

Hi, I have a MDT distribution that I have configured to use OOB Drivers base on OS then Model.

I have a new Windows 10 WIM and it works on every model of machine but one, the OptiPlex 790. In this case, there are no drivers provided to it from MDT. It doesn't need them. All of the drivers it needs are provided in the Windows 10 distribution.

Firstly, I understand that Dell does not support the Optiplex 790 on Windows 10.

The driver that won't install is for: Intel(R) 6 Series/C200 Series Chipset Family USB Enhanced Host Controller - 1C2D/1C26

These devices will show up after MDT (or manual) installation of Windows 10, "splatted" as "Universal Serial Bus (USB) Controller"s.

If I attempt to update and search automatically it will fail. But if I choose "Browse" then "Let me pick..." then select the built in MS driver below. it works fine!

Is there a way to automate this somehow?

Thanks,

-Matt

There's no place like 127.0.0.1

↧

Updating to MDT 2013 Update 1

October 1, 2015, 11:40 pm

≫ Next: can't pxe * invalid credentials: The network path was not found

≪ Previous: MDT 2013 U1 - Windows 10 - FORCE driver selction?

Do I need to create all the task sequences from the scratch after the update? I'm currently using MDT 2013.

↧

can't pxe * invalid credentials: The network path was not found

October 1, 2015, 5:00 am

≫ Next: Install Win 7 image after Win 10 upgrade - Licensing/Activation question

≪ Previous: Updating to MDT 2013 Update 1

can't pxe * invalid credentials: The network path was not found, when I go into f8 I can ping my deployment server fine.

I triedadding below to my bootstrap, but I dident have there command lines before in my bootstrap ini.

UserID=xxx
UserPassword=xxxx
UserDomain=domain.root

Do you know what the problem is or how I can troubleshoot this?

I made some mistakes when I tried to create a new mdt server 2012 r8 beside the old one, it is the old one that is not working, but I took the old pc name and used it on the new server. So the old mdt server that im currently using then got out of the domain. So I rejoined both and then this problem started happening. I also gave the new server a role as wds. But Im trying to get the old one to work because I need to install some PC's do you know what I could be struggling with?

/Kjell

I can ping the mdt

I can ping our server 10.67.130.110 the mdt server, but not the name pxe1-sth, I tried chaing bootstrap to IP also..

↧

Install Win 7 image after Win 10 upgrade - Licensing/Activation question

October 1, 2015, 2:30 am

≫ Next: SCCM 2012 R2 SP1 CU1 + MDT 2013 U1 - PXE Question

≪ Previous: can't pxe * invalid credentials: The network path was not found

I'm testing Win 10 upgrade via MDT task sequence and have successfully upgraded a Win 7 Pro machine with an OEM license to Win 10, and activated it.

Now I want to automate as much of the task sequence as possible using the unattend file.

What I would like to do is image this machine back to Win 7 Pro and reactivate it, then repeat the MDT Win 10 upgrade sequence using the modified unattend. This may happen several times as I test the changes to unattend.

My concern is that if I image back to Win 7, will the OEM key still activate the product, or is this key now tied to Win 10? I know that if the Win 7 is not activated the task sequence will not run, so I could end up with an unactivated Win 7 machine and be unable to test the sequence against it.

Has anyone got any experience of trying this?

Many thanks.

↧

SCCM 2012 R2 SP1 CU1 + MDT 2013 U1 - PXE Question

October 2, 2015, 6:52 am

≫ Next: Windows 10 Reference Build sysprep

≪ Previous: Install Win 7 image after Win 10 upgrade - Licensing/Activation question

Hey everyone,

I have a question regarding how PXE environment works with deploying boot images. I recently updated to MDT 2013 U1 to support windows 10 deployment. Now, I created new bootable images and distributed them to my distribution point and without replacing the boot image using WDS on the server, that boot image is now selected in my PXE and it fails until I select the option to distribute it to PXE-enabled distro points. My question is - how the heck those this work? Does PXE use the LAST boot image I give it? Always?

Thanks

Jakub

↧

Windows 10 Reference Build sysprep

October 2, 2015, 3:52 am

≫ Next: FAILURE ( 7706 ): ERROR! Drive D: was not found!

≪ Previous: SCCM 2012 R2 SP1 CU1 + MDT 2013 U1 - PXE Question

I hope everyone is well and can advise. I've been using MDT for about 3 years, for Windows 7 onwards. I'm trying to build a Windows 10 Reference build I'm on MDT 2013 Update 1, and I have built a task sequence as per the advise here:

http://deploymentresearch.com/Research/Post/496/Building-a-Windows-10-Reference-Image-using-MDT-2013-Update-1

All is well when I deploy the task sequence to a virtual machine until it gets to sysprep. The MDT Monitoring node is showing the task sequence at 92% completed (step name Executing Sysprep ) but it is not progressing.

On the VM, it is sat at a login screen, and if I try to log in, I cannot do so - the admin account is disabled. The MDT logs are not copied to the log share, because the TS isn't completed, and I can't access the logs on the hard disk of the vm, as I keep getting told the admin account is locked.

I need to know how to either add a local account into the VM, so that I can log onto it and look at the logs, or I need to know how to let the sysprep process complete, so thathe wim file is created and copied.

Yesterday I also read this thread about enabling the admin account

https://social.technet.microsoft.com/Forums/en-US/b37e1cf4-163d-4172-9cb3-724049962da7/mdt-2012-update-1-local-admin-account-disabled?forum=mdt

I have checked the xml file and the RunSynchronousCommand is present in the file.

Is this something that I am doing wrong, or has anyone else had the same issue.

How do I add an second Admin account to the Task Sequence, so that I can access the VM to look at the logs. Ultimately I need to understand why sysprep is not working as it normally does. It is probably because the admin account it locked out/disabled. I should also mention that I can run reference builds on the other task sequences for several different operating systems successfully, (I've updated my wim files on all Operating systems successfully in September using reference builds), and as far as I can tell the Task Sequence for the Windows 10 Reference build is the same as the Windows 8.1 Task Sequence.

Any advise gratefully accepted, we can't roll Windows 10 out until I masterthe Reference build.

Regards

John

Regards, John

↧

FAILURE ( 7706 ): ERROR! Drive D: was not found!

September 23, 2015, 8:11 pm

≫ Next: How to encrypt multiple drives

≪ Previous: Windows 10 Reference Build sysprep

I was wondering if anybody run into this issue and could point me in the right direction.

I have been using MDT for over 4 years and last week was the first time that I have ever seen this "FAILURE ( 7706 ): ERROR! Drive D: was not found!" message. I'm running a MDT 2013 deployment server with AIK 8.1 and this error occured while imaging a Surface Pro 3.

We successfully imaged about +10 Surface's with this MDT build however they all had 128GB SSD's and and 4GB of RAM this one that failed has a 256GB SSD and 8GB of RAM and the issue was replicated on another Surface with the exact same specs.

So far I have;

1) Tried another Surface Pro 3 of the same SKU and it had the exact same issue.

2) Successfully imaged this Surface with Windows 10 and with the Windows 8.1 Pro Surface Pro 3 recover image from Microsoft using USB media.

3) Updated my deployment share to MDT 2013 Update 1 and AIK 10 and tried both the original MDT 2013 standard deployment Task Sequence and the updated MDT 2013 standard deployment Task Sequence both modified for Surface Pro 3 (Driver Firmware, patches etc...)

4) Updated the Surface Pro 3 driver set with the very latest drivers but I noticed that even the latest drivers still uses the Intel ahci 8 driver from 2013 that the worked fine on the other 128GB SSD 4GB RAM Surface Pro 3 SKU's that we imaged before.

When looking at the BDD.log I can see that SSD drive is successfully cleared of any existing partition but it fails to create any partitions and after it fails in WinPE if you manually run Diskpart no drives seems to be available even though driver for the storage controller should still be loaded.

I have done a lot of research and I have found similar issues but none of the solution suggested has solved this issue and I'm running out of things to try.

Here are some of the Logs Files, let me know if any others are required;

https://onedrive.live.com/redir?resid=3fd6cdd8cde1b711!114&authkey=!APd0_2xdY_3izhQ&ithint=file%2cLOG
https://onedrive.live.com/redir?resid=3fd6cdd8cde1b711!115&authkey=!AIQSsEoJ0LBvCZE&ithint=file%2clog
https://onedrive.live.com/redir?resid=3fd6cdd8cde1b711!116&authkey=!AD6FuNbGaKVTpW4&ithint=file%2clog

Thanks in advanced.

↧

How to encrypt multiple drives

October 2, 2015, 8:39 am

≫ Next: Error - Missing LTIBootstrap.vbs (MDT 2013)

≪ Previous: FAILURE ( 7706 ): ERROR! Drive D: was not found!

Hello

We have recently acquired numerous laptops with multiple drives.

With our MDT Task Sequence, we are able to encrypt the primary disk by using the following cmd in the post installation installation tasks:

Command Line: cmd /c manage-bde.exe -on c: -recoverypassword

Start in: C:\Windows\System32

When i do the same for the secondary disk, it fails. Ends up encrypting the secondary disk and skipping the primary disk encryption

cmd /c manage-bde.exe -on d: -recoverypassword

When i remove this second task for the d: drive, it works flawlessly.

Additional Info:

Under New Computer tasks we have it set to:

Format and partition ssd drive, disk number 1, standard mbr, Ntfs

Format and partition data drive, disk number 0, standard mbr, Ntfs

Two Drives: Disk0 is the normal HDD, Disk1 is a SSD drive.

We want to install the OS onto the SSD drive, disk1 becomes C: & disk0 becomes D: for data

Any ideas?

Thanks,

Daniel

↧

Error - Missing LTIBootstrap.vbs (MDT 2013)

October 2, 2015, 2:02 pm

≫ Next: MDT 2013 Update 1 keeps giving me the Welcome Deployment Wizard if not using a domain admin account

≪ Previous: How to encrypt multiple drives

Hi!

I'm getting the following error when I reboot the machine after doing a deploy of a captured image. (Missing C:/LTIBootstrap.vbs)

I think the error is in that folder "MININT" is copied to the disk "D" and not on disk "C", so I have to open manualy the file from D disk to continue the Task.

If I pause the deploy after the task "Format and Partition Disk", open a DISKPART and do a "Detail Partition", I get that partition 1 is assigned the letter V: and D: drive is assigned the letter C:

I am sysprepping and capturing then deploying the captured image using a separate task sequence, and partitioning the disk in two.

Can anyone helpme?

Thanks!!

↧

MDT 2013 Update 1 keeps giving me the Welcome Deployment Wizard if not using a domain admin account

September 17, 2015, 8:01 am

≫ Next: MDT Issue

≪ Previous: Error - Missing LTIBootstrap.vbs (MDT 2013)

Hi,

I have successfully managed to hide all the deployment wizard screens and everything runs fine if i log into the client machine using the domain admin account and run the litetouch.vbs file.

if i log into the client as a new user i have created in AD (MDTDeployment) i can't seem to avoid getting the wizard that prompts for task sequence and applications and so on.

MDTDeployment user is:

part of the local admins of the client
full access NTFS on the deployment share
has its username and password put into the bootstrapsettings.ini file
i have also added it as a user in SQL for the MDT database and allowed all the membership and schema permissions i can find
I have even added this user to the domain admins group and it still prompts me for the task sequence

where else do i set user permissions for an MDT deployment, i must be missing something somewhere

thanks

Steve

↧

MDT Issue

September 2, 2015, 6:28 am

≫ Next: Closing IE with Lockdown manager in Windows 8.1 embedded.

≪ Previous: MDT 2013 Update 1 keeps giving me the Welcome Deployment Wizard if not using a domain admin account

Hi All,

I'm hoping someone can help with this issue, I will provide a little background before introducing the problem to try and make my situation as clear as possible.

Background

- I have recently upgraded MDT from 2010 to 2013 and integrated Windows Assessment and Deployment Kit for Windows 8.1

- My task sequences are split into two folders (x86 and x64), both of these folders contain a deployment image for our commonly purchased PCs. They have been created using a sysprep and capture which was working swimmingly.

- The first time I imaged two new 64x PCs since the upgrade, MDT went through the installation OK (it took all day which is unusual but it did complete), the speed of installation was going to be my next issue however I was faced with a bigger one.

Problem

We have received two new 64x PCs which I am trying to image, however the deployment wizard errors and cancels at the stage of 'Installing Operating System', with the following error:

Litetouch deployment failed, Return Code = -2147467259 0x80004005
Failed to run the action: Install Operating System.
Incorrect function. (Error: 00000001; Source Windows)
The execution of the group (Install) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source Windows)
Failed to run the last action: Install Operating System. Execution of task sequence failed.
Incorrect function. (Error: 00000001: Source Windows)
Task Sequence Engine Failed! Code: enExecutionFail
Task Sequence execution failed with error code 80004005
Error task sequence manager failed to execute task sequence. Code 0x80004005

This seemed strange as I haven't touched anything since the last successful image. I've been researching the following error and the first thing that I initially tried was to Completely Regenerate the Boot Images when updating the deployment share. Since then I can no longer PXE boot to the 64x WDS, instead it eventually brings up command prompt with X:\windows\system32 that sits on top of the Microsoft Solution Accelorator background, nothing else happens at this point. If I boot to the 32x WDS if does load the deployment wizard where I can actually see the 64 bit task sequence, if however I try to run this I'm prompted with that exact same error above.

The second thing I tried was disabling 'Injecting the drivers' as I thought that the network driver may have been causing a problem and disconnecting me from the deployment share, this however didn't work either.

I'm totally baffled now to be honest and would appreciate anyone helping me out?

Many thanks in advance,

↧

Closing IE with Lockdown manager in Windows 8.1 embedded.

October 12, 2015, 4:50 am

≫ Next: Office 2016 and MDT

≪ Previous: MDT Issue

Hi All,

We are deploying Windows 8.1 Embedded with MDT Task Sequence. MDT TS deploys Windows 8.1 Embedded with few Lob apps & google earth. In the build we are running Google earth in offline mode & when google earth runs in offline mode it checks for internet& prompt for a diagnostic test (The user gets a messages if they want to run the diagnostic test, The message has Yes/No button) If the user click Yes then Google earth runs the diagnostic test & displays the result in IE. Now, in our Windows 8.1 Embedded build we are blocking this google earth message using lock down manager & when this message is blocked google earth is taking the Yes value by default & runs the diagnostic test showing the result in IE.

So, the problem is that when a user launch Google Earth in the build, IE always comes up with google earth other messages are blocked but when we try to block IE using lock down manager entire application gets blocked.

Is there a way to block IE Google earth page without getting IE completely blocked.

Please Help !

Thanks,

Pranay.

↧

Latest Images