I know I am doing something wrong. We are using Server 2012 WDS and MDT 2013 to deploy windows 8.1 to Surface Pro. We are using the official Surface Pro Ethernet Adapter but I am seeing this error:
No networking adapters found, The network drivers for your device are not presentLiteTouch 12/10/2013 10:10:28 AM 0 (0x0000)
What do I need to do to fix this?
hi,
i have deployment windows 7 by MDT，and there is something wrong with the test. i have a MDT Service and 2 clients that one is updated and another is used to capture the image.but when i captured the image,there is error."a connection to the deployment
share could not be made. connection ok"
The problem I am about to describe doesn't exist with MDT 2010 update 1, MDT 2012, or MDT 2012 update 1 when using the either WAIK or ADK. I have not attempted to reproduce this problem with older versions of MDT or pre-release versions of MDT 2013. The problem definitely exists with MDT 2013 RTM.
This is the same problem as Inconsistent DISM.EXE error when applying unattend.xml during LTI deployment - Possible bug!, but this is more concise and provides details on how to reproduce the problem.
Status as of 2014-01-08 (Previous workaround deemed unusable - core bug still present)
Keith Garner determined that DISM.EXE was failing while processing the <offlineServicing> section in the unattend.xml file. Removing this section resolves the issue, but this section is needed to inject drivers into the image during WinPE and is needed The presence of this section didn't cause any problems with previous releases of MDT/ADK - it is likely an interoperability bug within the DISM.EXE tool. See replies below for details.
Problem:
When deploying Windows 7 Pro x64 w/SP1 and enabling/disabling features using unattend.xml, deployment often (almost 100% of the time) fails with this dialog:
Steps to reproduce ("bare-metal"):
*When installing Windows Updates:
Launch MDT Workbench:
From another new, clean virtual machine:
At this point, the deployment will succeed every time.
Now, edit the task sequence and edit the unattend.xml:
Deploy the task sequence again using the directions above (for each attempt, I used a new, unused VM), and it will fail nearly every time!
Notes:
From results.xml:
<?xml version="1.0"?><Results><Errors>8</Errors><Warnings>0</Warnings><RetVal>-2147467259</RetVal><DeploymentType>CUSTOM</DeploymentType><Messages><![CDATA[FAILURE ( 5456 ): Unable to determine Destination Disk, Partition, and/or Drive. See BDD.LOG for more information. Litetouch deployment failed, Return Code = -2147467259 0x80004005 Failed to run the action: Apply Windows PE. Unknown error (Error: 00001550; Source: Unknown) The execution of the group (Capture Image) has failed and the execution has been aborted. An action failed. Operation aborted (Error: 80004004; Source: Windows) Failed to run the last action: Apply Windows PE. Execution of task sequence failed. Unknown error (Error: 00001550; Source: Unknown) 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]]></Messages></Results>I have not only regenerated my boot files while updating my deployment share, I have completely rebuilt the MDT 2012 deployment share from scratch, and I'm still getting the exact same errors. I can't figure out what is causing this. The only hits for these errors seemed to say that the -214... error is likely related to a missing file, but I don't know how to figure out what that might be. I don't know what the FAILURE ( 5456 ) could be caused by, either, although it seems to be related to not knowing what partition should be imaged or imaged to. I haven't been able to find any reference to MDT needing a partition to image from/to set in a CS.ini property or in a task variable.
how I can run a command line during the Windows Deployment Wizard before picking the Task Sequence, I would like to run ipconfig /setclassid "Local Area Connection" XXXXX,, I know I can press F8 and run the command manually, but is there a way to make this process automatically.
thank you
So I recently upgraded our MDT server from MDT 2012u1 to MDT 2013 (on a Windows Server 2012 R1), during the process I also removed ADK 8 and replaced it with ADK 8.1.
I had DART8 already installed, but I uninstalled it and made sure to reinstall DART 8 SP1 from MDOP 2013.
I also added Windows Server 2012 R2 and Windows 8.1 full sources from vanilla images from MS VLSC to MDT.
I do get the DART option in my boot images but I don't get the Windows Recovery Wizard and the Registry Editor, Locksmith, Comp Mgmt, etc are disabled. as it seems to be using the Windows PE WIM image from ADK and not those from the Windows 8.1 or 2012 source.
Windows PE WIM C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us\winpe.wim will be used.WIM file mounted.
Is there something wrong ? Do I have to wait for the new DART/new MDOP ? (why don't those things get updated at the same time?) or is there a way to make sure it uses the WinRE from Windows 8.1 or 2012 for the boot image ?
Another question: Will DART and the Recovery Wizard on a Windows RE 5.0 boot image work for a Windows 7 installed system ?
I am getting an error when I do update deployment share in MDT. It only happens if I fill the "extra directory to add" or add in "packages". If I don't have any packages or leave the extra directory blank, the share updates successfully. I am using MDT 2012 and have tried from different computers. I have enough space and full write access to the MDT share. Any help would be appreciated.
Joe
Set Windows PE system root.
Set Windows PE scratch space.
Copy: \\gvault\galdeploy$\Extra Files\x64 to c:\temp\2\MDTUpdate.2440\Mount\
System.Management.Automation.CmdletInvocationException: Access to the path 'c:\temp\2\MDTUpdate.2440\Mount\Windows\System32\bcdboot.exe' is denied. ---> System.UnauthorizedAccessException: Access to the path 'c:\temp\2\MDTUpdate.2440\Mount\Windows\System32\bcdboot.exe'
is denied.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.File.Delete(String path)
at Microsoft.BDD.Core.DirectoryUtility.CopyFile(DEInfo sourceFile, DEInfo destFile, String destFullName)
at Microsoft.BDD.Core.DirectoryUtility.CopyDirectory(String theSource, String theDest)
at Microsoft.BDD.Core.DirectoryUtility.CopyDirectory(String theSource, String theDest)
at Microsoft.BDD.Core.DirectoryUtility.CopyDirectory(String theSource, String theDest)
at Microsoft.BDD.Core.DirectoryUtility.BeginCopy()
at Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.UpdateBootImage(String template, String platform, String dpPath, Boolean createISO, String isoName)
at Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.ProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord()
--- End of inner exception stack trace ---
at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()
at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()
We are aware that SCM does not have a basline for Windows 8.1. I have seen Johan post about adding the code to the ZTIApplyGPOPack.wsf for support for Windows 8.1. Also do we need to update GPOPack.wsf located in \Templates\GPOPacks\Name of GPO PACK.
So what is the best approach for creating and applying a GPO PACK to Win 8.1?
Thanks
Hi Team,
Just wondering if it is suggested not to open or use MDT console workbench once its been integrated with configuration manager?
I been using it for a while and never faced any issues. I believe it should be fine to use the MDT and configuration manager both even after they been integrated. I generally use MDT workbench for building image and then use Configuration manager MDT based TS to deploy it. I don't see any technical risk. Any advice\best practice? Thanks.
Regards,
Hi,
I have an issue similar to this one:
I am running MDT 2012 SP1 on Server 2008 R2. will that solution work on server 2008?
when I deploy the task sequence to one system it completes without an error.
when I deploy to more than one, it fails on a custom task for .net 4 extended install.
the error states source, unknown. (I will have more details tomorrow)
any thoughts? and what added details can I provide?
Thanks.
Hi,
Apologies for creating another thread but I am currently getting no where with this.
I have tried to apply the fix to this thread:
Basically the only thing which is stopping me having a fully automated Build, sysprep & Capture process is that when I add a restart before the sysprep (this is to apply some custom changes made to the reference Image) the PC reboots and the Litetouch process is unable to connect to the deploymentshare. This is because the PC has not picked up its DHCP Lease before the Litetouch.vbs scripts runs following the restart.
The above thread seemed to be the only logical solution, so I modified the ZTIUtility.vbs file with a sleep in the same position:
I updated the deploymentshare and created another boot disc. But I get the following error, ONLY when I select to capture the reference Image:
I've search most of the scripts and cannot find a variable called ValidateCaptureLocation.
If I take "wscript.sleep 5000" out of ZTIUtility.vbs file then it's fine apart from the original issue.
Maybe there is somewhere else I can add the delay which will run before the script Litetouch.vbs restarts the deployment?
Thanks,
Jason.
P.S. I've tried the Local Policy to "Wait for network connection before logon", this doesn't work consistently.
Thanks, Jason.
With MDT 2012 Update 1 to have settings per task sequence in customsettings.ini, the code had to be edited (see: http://social.technet.microsoft.com/Forums/en-US/e17a1952-d1f7-41ef-8231-0d6fcc41882e/mdt-2012-settings-per-task-sequence?forum=mdt)
Does MDT 2013 support settings per task sequence, or must the code be edited for MDT 2013 as well?
I need some help getting CustomSettings.ini populated dynamically.
There are a lot of hits out there when I search for using web services or vbs scripts but I'm failing to join the dots and actually populate a value.
I am trying to get the computer name via the web service. I.e. the CustomSettings.ini value 'OSDComputerName'
I have made a .vbs script that successfully queries a web service and then selects the appropriate value from the XML:
<job id="MDTMenu_name"><script language="VBScript" src="..\ZTIUtility.vbs"/><script language="VBScript" src="..\ZTIDataAccess.vbs"/><script language="VBScript">
Dim oService
Dim oXML
Set oService = New WebService
oService.IniFile = "CustomSettings.ini"
oService.SectionName = "asset_query"
Set oXML = oService.Query
' Configure the namespace
Dim ns
ns = "http://unitedwholesale.com.au/webservices/external/"
oXML.SetProperty "SelectionNamespaces", "xmlns:ns ='" & ns & "'"
If oXML Is Nothing Then
oLogging.CreateEntry "Unable to call UserGetName web service.", LogTypeWarning
WScript.Echo "Not Found" & vbcrlf
Else
WScript.Echo oXML.SelectSingleNode("/ns:AssetInfo/ns:ID").Text
Dim OSDComputerName
OSDComputerName = oXML.SelectSingleNode("/ns:AssetInfo/ns:ID").Text
End If</script></job>My CustomSettings.ini looks like this:
[Settings] Priority=Default Properties=MyCustomProperty [Default] OSInstall=Y SkipCapture=NO SkipAdminPassword=YES SkipProductKey=YES SkipComputerBackup=YES SkipBitLocker=NO SkipUserData=YES SkipDomainMembership=YES JoinDomain=xxx.net DomainAdmin=yyy DomainAdminDomain=zzz DomainAdminPassword=xxx UserDataLocation=NONE [asset_query] WebService=https://mywebservice.example.com/assetservice.asmx/GetAssetByMacAddress Parameters=macAddress
I know I am missing some fundamentals but I can't seem to find any useful posts about how to actually link back my extracted XML values in my script to variables in my CustomSettings.ini.
Any pointers appreciated!
We are presently imaging Lenovo E530 laptops. We start the network boot and pxe provides the choices of 32 or 64 bit. Once we make our selection it begins to load and then we are presented with: Windows Boot Manager (server ip) Windows failed to start. A recent hardware or software change might be the cause.
We added network drivers to MDT and rebuilt the boot wim and copied them into WDS. Restarted the service and continually receive the same error.
Any help would be appreciated.
HI All,
I'm running MDT 2012 with 3 Link Deployments.So can we move to New Server with MDT 2013 ?
If so what are the Steps?
AS
Is there an easy way to take the UserID MDT variable from bootstrap.ini and have a task sequence step to make it part of the Administrators group?
Idea here is to automate the process of adding users who provide their credentials before LiteTouch deployment to the local administrators group.
Can I use the property Administrators000=%UserID%?
Seems like the UserID variable from WinPE isn't carrying to CustomSettings.ini...
Hi everyone, been pulling my hair the whole day about this...
I just had a brand new Lenovo X240. Tried to PXE boot yesterday, made it to MDT LiteTouch deployement but failed once in Windows because I had not included the new drivers.
I added the driver, but after that I had the "proxydhcp service did not reply to request on port 4011" error. Still, other system were fine with MDT. I added a bunch of driver for the system, now I have the "PXE-E53: No boot filename received" error. Still, other system are working fine.
Now I don't know where to look. I completly reinstalled WDS just in case but no luck yet.
Anything left for me? I'm about to throw everything through the windows...
Thanks!
I've been having a problem getting the LiteTouch wizard to display the correct Task Sequences and Application when running it from a OS..
i'm starting litetouch from the BDD_Autorun.wsf in the scripts folder in the deployment point.
When i run litetouch from a windows 7 64-Bit OS. i get the option to install the 32-bit Office 15. Even thought it is set to be 64-bit clients only.
I get the same problem in reverse when i try to set a TS to be "All x86 windows 7 or newer" and "All x64 Windows 7 or Newer" then run the litetouch in a windows 7 OS. the TS doesn't show up in the list.
As a side note we do not use ConfigMGR.
Is there something i'm missing in my setup to get this to work correctly?
