Quantcast
Channel: Microsoft Deployment Toolkit forum
Viewing all 11297 articles
Browse latest View live

Installing NetFX3 failing with

$
0
0

I have MDT 2013 Update 1 installed with Hyper-V on a Windows 8.1 Enterprise OS. I am trying to install NetFX3 during the State Restore Group in MDT. While NetFx3 is trying to install I get the message:

FAILURE (5206): The Deployment Wizard was cancelled or did not complete successfully. The deployment will not proceed.
ZTI ERROR - Unhandled error returned by ZTIOSRole: Path not found (76) Litetouch deployment failed, Return Code = -2147467259 0x80004005

The ZTIOSRole.log shows:

Microsoft Deployment Toolkit version: 6.3.8298.1000	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
The task sequencer log is located at C:\Users\admin\AppData\Local\Temp\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
Roles will be installed.	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
No items were specified in variable OSRoles.	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
No items were specified in variable OSRoleServices.	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
Features specified in Feature:	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
  NetFx3	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
  NetFx4-AdvSrvs	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
No items were specified in variable OptionalOSRoles.	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
No items were specified in variable OptionalOSRoleServices.	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
No items were specified in variable OptionalOSFeatures.	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
ZTI Heartbeat: Processing roles (0% complete	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
Using a local or mapped drive, no connection is required.	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
Copying source files locally from F:\Deploy\Operating Systems\x64\sources\sxs\	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
ZTI ERROR - Unhandled error returned by ZTIOSRole: Path not found (76)	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)

After I click Finish on the Deployment Summary, I see the DVD-ROM drive is not F:, but D:. I did the same setup on my Windows 2012 Server running Hyper-V, but I was able to install NetFx3 just fine without any errors. Anyone know why this is happening and how to fix it? Thanks.




Problems with loading LiteTouchPE_x64.wim (MDT 2013 U2)

$
0
0

Hi,

I have a really annoying problem after i updated MDT 2013 U1 to MDT 2013 U2.

I uninstalled MDT 2013 U1 and installed MDT 2013 U2 instead and updated my deploymentshares and updated the boot images in WDS.

Now when i try to boot into my deploymentshare it gets stuck when it is loading the LiteTouchPE_x64.wim image. After like 20 seconds i get an error message "Windows failed to start. A recent hardware or software change might be the cause". Status: 0xc0000001. Info: A required device isn't connected or can't be accessed.

I have tried the following:

- Uninstall Windows ADK 8.1

- Updating Windows ADK 10 to version 1511

- Try on a different computer

- Put the LiteTouchPE_x64.ISO image to a USB key and boot from it.

- Try on a virtual machine with the LiteTouchPE_x64.ISO (HERE IT WORKS!)

- Tried to use WinPE 10 drivers instead of WinPE 5.0 drivers

- Tried changing the Maximum Block Size to 1024

I have tried Google and it doesn't seems like any other had this problem before.

Do you guys have a solution for me? it would be much appreciated. Because it is in our production environment.

Changing DeployRoot path DURING Imaging

$
0
0
I'm trying to change the DeployRoot path on the fly WHILE imaging.  If i try to change the path in x:\deploy\scripts\bootstrap.ini while imaging in WinPE, it doesnt take effect, i've also tried running ztigather.wsf and some other wsf in the same directory after the change to the boot.ini file to see if that helps update whatever, but still no go.  anyone know how.  Thanks.

Issues with Win10 Upgrade TS post MDT 2013 Update 2

$
0
0

After installing the MDT 2013 Update 2 patch, my Windows 10 Upgrade TS seems to have broken. After toying around for a bit, I found if I DESELECT the option in the TS to "Dynamically update Windows Setup with Windows Update" the TS completes. If I check this box, it fails with the following:

Failed to run the action: Upgrade Windows.
Incorrect function. (Error: 00000001; Source: Windows)    TSManager    12/30/2015 2:23:28 PM    1216 (0x04C0)

The execution of the group (Upgrade the Operating System) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)    TSManager    12/30/2015 2:23:28 PM    1216 (0x04C0)

Failed to run the last action: Upgrade Windows. Execution of task sequence failed.
Incorrect function. (Error: 00000001; Source: Windows)    TSManager    12/30/2015 2:23:28 PM    1216 (0x04C0)

Task sequence execution failed with error code 80004005    TSManager    12/30/2015 2:23:28 PM    1216 (0x04C0)

RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram    TSManager    12/30/2015 2:23:28 PM    1216 (0x04C0)

GetTsRegValue() is unsuccessful. 0x80070002.    TSManager    12/30/2015 2:23:28 PM    1216 (0x04C0)


Has anyone else encountered anything similar with Update 2?

Add custom pane to select disk in MDT wizard

$
0
0
I am trying to find a way to let our technicians select the disk to deploy Windows when we boot to WinPE. By default, MDT will format and deploy the image to DISK 0 because that is how it is set in the Task Sequence. But sometimes we need to deploy an image to DISK 1. I would like to create a custom pane in the MDT Deployment wizard to select the disk prior to imaging. It needs to be an option in a custom pane every time we boot to the Deployment Wizard. How can I accomplish this? Thanks.

MDT 2013 update 1 where are the help files

$
0
0

I am probably posting this in the wrong place because I cannot find the right place in your carefully crafted menu system.

MDT 2013 Update 1 does not contain help files. What gives? This used to be included with MDT which is a relatively small package anyway. So why were the help files not included? It would be so bad if a link to the specific page on Technet  for MDT 2013 update 1 was included, but instead it provides a link to a top level page leaving you to hunt your way through to find the documentation that is appropriate. Sorry your search engines don't work well either. Google found it in seconds though.... LOL

MDT 2013 Upd2 - User backup Network location

$
0
0

Hi,

We are in phase of deployment of Windows 10 (10.586.0).

For that purpose, we use MDT 2013 update 2 and WDS (serveur 2K12 R2 std).

Everything works except the saving of the data on the network. It save on the hard drive of the computer.

Here are the information type in the configuration.ini:

SkipUserData=NO

UDShare=\\myserver\MDT\Migdata
UDDir=%OSDComputerName%

UserDataLocation=NETWORK

ScanStateArgs =/o /c /uel:180
LoadStateArgs =/c /all
USMTMigFiles001=MigApp.xml
USMTMigFiles002=MigUser.xml

I've try this option too:

UserDataLocation=%UDShare%\%UDDir%

Always same, nothing backup on the directory on the server. All access right is correct, because, it's same folder for the logs (\\myserver\MDT\Logs)

Thanks your for you help.



Problem updating images

$
0
0

I use VM Workstation to create images for our MDT environment and I usually update them monthly when the Windows updates come out but for scheduling issues I skipped December.

I updated my images last week and when I applied them to my development computer I got the following error.

Event 41014 sent: Litetouch deployment failed, Return Code = -2147467259  0x80004005LiteTouch01/08/2016 9:31:52 AM0 (0x0000)

I applied the image to a different PC and got the same error message.  I rebuilt the image from scratch and got the same error again.  My last attempt was to build an image with just the OS and no Windows updates and when I apply the image I get the same error.

Fortunately, the old WIMs from November are still working but I'm at a loss as to why I'm getting this error message.  I found one article that said there might be a dirty sequence on the computer so I used Diskpart to clean and format the drive but I still am getting the error message.

I haven't made any changes to the Task Sequences or the Deployment properties.  Any help would be greatly appreciated.

Let me know what log files are needed for viewing.


MDT 2013 Update 1: Other bugs with customsettings.ini/unattend.xml?

$
0
0

Here are other issues I am having with MDT 2013 Update 1 when deploying Windows 8.1 Enterprise x64.  Anybody else seeing these?

1) If the admin passwords in Unattend.xml are hashed using "Hide Sensitive Data", and the password is changed using the Wizard at deployment, or customsettings.ini, the password passed to Unattend.xml does not get hashed, yet the protected value stays as true, so Windows thinks the value is hashed.  This causes deployment to completely die.

There may be other circumstances where this happens but this is where I have encountered it.  A fix is to turn off Hide Sensitive Data and enter non-hashed passwords into Unattend.xml so that protected gets changed to false. (Credit to 'Josh' in the comments sections of the TechNet blog post about the MDT 2013 Update 1 release for pointing me in this direction.)

2) I set the default locale, keyboard, language and time zone in my customsettings.ini.  The Deployment wizard does not pickup the time zone anymore though, and instead gives Pacific Standard Time as the default.  Here is what I have in my customsettings.ini:

SkipTimeZone=NO
TimeZoneName=Singapore Standard Time

I am guessing that perhaps the name of "Singapore Standard Time" has changed in WinPE with Windows ADK 10, and that is the reason is isn't being picked up...  But I can't find any updated listing of time zones for Windows 10 on TechNet or elsewhere, and do not presently have any Win 10 VMs running to use the tzutil /l command.  If someone can post an output from Win10 of that command that would be greatly appreciated!

Windows Hello not working with fingerprint reader if W10 Ent is deployed with MDT 2013 U2

$
0
0

Hi everybody,

As I wrote in the title, I experienced a very very odd problem with my HP Probook 440 G3.
I'm trying to testing Windows Hello feature, but I was able to make it working only if I install my corporate VL copy of W10 Ent from the original media (ISO brought to USB key), or if I install the 90 day evaluation version, downloaded from MS site.

In such cases, when I swipe my finger on the reader, the Windows Hello setup completes successfully.

With the same install.wim file taken from the VL ISO, the OS deployed by a standard MDT 2013 U2 Task Sequence seems to behave differently. In fact, I got a "something went wrong" error while trying to complete Windows Hello setup.

Biometric device is "Synaptic FP Sensors (WBF) (PID=003f)", whose driver has been directly downloaded from MS catalog in each scenario: the failing one and the working one.

Thanks for any help :)

Please also note that I've already tried to reset fingerprint and TPM contents from HP Bios, among different installations, with no success of course :/


Using webservice with variable in the URL?

$
0
0

Having an issue trying to have a variable in a web url for webservice

I  am allowing the user to select which deployment share they want to use (Primary or Backup) on WinPE boot disk.

In my customsettings.ini I have a web service called to check what group the user is and display a list of task sequences based on a selection profile.

Issue is each server has their own webs service and I need to change the DNS name in the url

When I do:

WebService=http://%MDTServer%.company.com/Deployment%20Webservice/ad.asmx/IsUserGroupMember

it will not work. I also tried:

WebserviceURL=http://%MDTServer%.company.com/Deployment%20Webservice/ad.asmx/IsUserGroupMember

WebService=%WebserviceURL%

I can see that %MDTServer% is getting the correct name. 


Language Packs for 1511?

$
0
0

Using DISM to add the LPs, getting this message.  The OS is Win 10 Ent build 10586.  I noticed the LP is 10240.  When the customer goes to the MS site to download for me, he downloads the LP ISO from Nov ’15 which should be 1511.  Still see the same issue.  Any thoughts?  Trying to apply the Nov 11 LPs to build 10586.

Deployment Image Servicing and Management tool

Version: 10.0.10586.0

Image Version: 10.0.10586.0

Processing 1 of 1 - Adding package Microsoft-Windows-Client-LanguagePack-Package

~31bf3856ad364e35~amd64~ar-SA~10.0.10240.16384

[==========================100.0%==========================]

Error: 0x800f081e

The specified package is not applicable to this image.

There are two downloads available:

1. Windows 10 Language Pack (Released Jul '15)

2. Windows 10 Language Pack (Released Nov '15)

Windows 10 Language Pack (Released Jul '15) can only be applied on Windows 10 Professional (Released Jul '15), Windows 10 Education (Released Jul '15) and Windows 10 Enterprise (Released Jul '15)

Windows 10 Language Pack (Released Nov '15) can only be applied on Windows 10 Professional Version 1511 (Released Nov '15), Windows 10 Education, Version 1511 (Released Nov '15) and Windows 10 Enterprise, Version 1511 (Released Nov '15).


Jay Parekh

Windows 10 update Admin Account

$
0
0

Hi,

I am trying to update our workstation to windows 10. I have created an update task sequence and it run perfectly fine.

The only issue I have is regarding the final few stage where it tries to log in after reboot. We have the local admin account disabled by default and a new local admin account is create instead. So after reboot it tries to login and fails. I have edited the unattended file and added the other user but its made no difference.

<AutoLogon><Enabled>true</Enabled><Username>Admin2</Username><Domain>.</Domain><Password><Value>password2</Value><PlainText>true</PlainText></Password><LogonCount>999</LogonCount></AutoLogon>

Installing NetFX3 failing with Path not found

$
0
0

I have MDT 2013 Update 1 installed with Hyper-V on a Windows 8.1 Enterprise OS. I am trying to install NetFX3 during the State Restore Group in MDT. While NetFx3 is trying to install I get the message:

FAILURE (5206): The Deployment Wizard was cancelled or did not complete successfully. The deployment will not proceed.
ZTI ERROR - Unhandled error returned by ZTIOSRole: Path not found (76) Litetouch deployment failed, Return Code = -2147467259 0x80004005

The ZTIOSRole.log shows:

Microsoft Deployment Toolkit version: 6.3.8298.1000	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
The task sequencer log is located at C:\Users\admin\AppData\Local\Temp\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
Roles will be installed.	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
No items were specified in variable OSRoles.	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
No items were specified in variable OSRoleServices.	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
Features specified in Feature:	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
  NetFx3	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
  NetFx4-AdvSrvs	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
No items were specified in variable OptionalOSRoles.	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
No items were specified in variable OptionalOSRoleServices.	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
No items were specified in variable OptionalOSFeatures.	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
ZTI Heartbeat: Processing roles (0% complete	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
Using a local or mapped drive, no connection is required.	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
Copying source files locally from F:\Deploy\Operating Systems\x64\sources\sxs\	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
ZTI ERROR - Unhandled error returned by ZTIOSRole: Path not found (76)	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)

After I click Finish on the Deployment Summary, I see the DVD-ROM drive is not F:, but D:. I did the same setup on my Windows 2012 Server running Hyper-V, but I was able to install NetFx3 just fine without any errors. Anyone know why this is happening and how to fix it? Thanks.




Office 2016 (Volume Licencing Installer & ODT)

$
0
0

Hello, I am currently having issues installing Office 2016 with MDT using the ODT.

I get the following errors.

returned an unexpected return code: 110

returned an unexpected return code: 30088

I am also using an MSP file in the update folder just FYI this runs with no issue when clicking on Setup.exe manually.


Alex Olver



Errors once deployment is completed successfully

$
0
0

I applied Update 2 several weeks back, not sure if this is related. I deployed a Windows 7 image and got the following error;

ERROR - no credentials were returned from LTICredentials.hta, so no connection is possible. Unable to connect to deployment share\\deployment share UNC path here.

Connection OK. Possible cause: invalid credentials

Windows 7 deployment slow after upgrading from MDT 2013 to MDT 2013 update 1

$
0
0

we have been running a MDT 2013 server for system deployment before and just upgrade to MDT 2013 update1 recently.

now we found a strange problem, it's very slow to install windows 7 after upgrade. not only the DISM process but also for applying image and application installation process. it will take more time to finish a deployment than before  (twice)

but looks normal for windows 8 and windows 10 deployment. I didn't modify too much on task sequence for all of these systems. and no idea why give us so different result? anyone has any idea?  

Sysprep fails on Windows 2008 R2 after installing Windows Management Framework 5.0...

$
0
0

Hey guys,

We decided to make the recently released Windows Management Framework 5.0 a standard component in al our image builds. I was able to get it installed and use MDT to successfully capture new reference images on Windows 7 and Windows 2012 R2, but for some reason when MDT attempts to run sysprep right before capture on Windows 2008 R2 it fails. When I run the same task sequence and omit the Windows Management Framework 5.0 sysprep and capture succeeds.

Anyone know of a fix for this?

"DoNotCreateExtraPartition=YES" no longer working in MDT 2013 Update 2?

$
0
0

Hey guys,

We recently upgraded to MDT Update 2 and began to notice that images we deployed seemed to be creating both the "system reserved" and "recovery partitions" even though we are using "DoNotCreateExtraPartition=YES" in our CustomSettings.ini files. A quick examination of the logs confirmed this behavior:

 

How do we fix this?

Out of disk space during capture sequence

$
0
0

I was able to successfully create a custom for Windows 10 and deploy it with Update 2. I discovered I needed to modify some software settings in the base wim image so I fired up my hyper-v VM of 10 and made the changes. On attempting to recapture the wim the capture process hangs during Running Action: Apply Windows PE

It appears there is an e drive mounted by the capture process and the e:\ is full. According to disk part E is a 499 MB fat32 partition.

BDD.log shows these

<![LOG[  Console > 2016/01/13 16:27:01 ERROR 112 (0x00000070) Copying File E:\efi\boot\en-us\bootx64.efi.mui]LOG]!><time="16:27:02.000+000" date="01-13-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[  Console > There is not enough space on the disk.
]LOG]!><time="16:27:02.000+000" date="01-13-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply">

Is this a bug in the ADK or Update 2 or do I need to modify a script or setting somewhere?


Viewing all 11297 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>