Hi,
I'm trying to create a Deployment Share with MDT 8443. I would like to use this share in a Media (variable DeploymentMethod=MEDIA). My question is about the file media.tag: is it automatically generated or is it up to me to create it? I do not remember having this issue (file not found) when using MDT 2013 U1.
Thanks in advance for your support
When deploying Windows 10 1607 Enterprise with MDT I will get the "an update is being installed" and OneDrive starts updating. Any good ideas how to do this automatically and prevent that autoupdate feature of OneDrive?
I am using MDT to automatically create the core/gold image for deployment. The creation process works fine. Previously I had been able to run a Sysprep and Capture task sequence which would create a new WIM file of the OS in the \Capture folder. I did this on the reference computer, mapping a drive to the MDT share, and executing Litetouch.VBS and from there I would select through the menus. I have done this 3-4 times using this same PC (re-imaging by laying down the core/gold image task sequence).
Starting today when I run my normal Sysprep and Capture I now get an error that LiteTouch.wsf cannot be found. And the network card no longer works (which sort of explains why it can't reach the share). The odd thing is this is how I always did all of my captures and this never happened before.
I haven't changed anything on MDT and the reference PC is continually re-built with the core/gold image task sequence so nothing there.
Has anyone else run into this? Or can explain why it is happening all of a sudden?
Thanks
Christopher Westpoint - Infrastructure Architect
Hi,
I am getting an error as per subject line in MDT when I am trying to deploy Dell Latitude E7270. I tried many drivers directly from Dell website, Intel other compatible Lenovo but no solution work.
here is the attached error I am getting.
Thanks
Jayant
Jayant
Hello.
We use MDT 8443 to deploy clients (Windows 10) and servers (Windows Server 2016) and have issues with "Dirty environment found".
Both clients and servers use UEFI booting. We initiate installations by PXE booting from a WDS server.
On clients, some models install without a hitch and some consistently present a "Dirty Environment found" dialog, if you answer "No" and let the task sequence continue it finishes successfully.
On servers, one model (HP ProLiant ML110 Gen9) applies the OS image and reboots, after reboot it boots to PXE. If we boot from WDS again, we get a "Dirty Environment found" dialog", answer "No", the server reboots and boots off internal disks. The installation seems to finish properly, but we get an error from ZTITatoo, "FAILURE ( 9601 ): ERROR - ZTITatoo state restore task should be running in the full OS, aborting" in the summary.
If we run the same server task sequence on a VMWare virtual server, it finishes successfully without booting from PXE or displaying errors from ZTITatoo.
Does anyone have an idea what goes wrong when we end up with a dirty environment?
Hi,
I updated MDT 8443 and integrated it with SCCM 1610 following this article.
Then I recreated my task sequence that was working before. (MDT Toolkit and Boot image were also recreated)
My main issue is the OSDJoinPassword variable that is no longer works for the UDI wizard.
Instead of automaticcaly complete the password for the defined account to join the computer to the domain like it did before, I only got 1 character.
According to this : https://blogs.technet.microsoft.com/mniehaus/2010/04/26/dumping-task-sequence-variables/
I am able to see the OSDJoinPassword variable and it contain de right value (password).
I did many things.
I deleted and recreated the Task sequence viriable.
I created a new XML (UDI Wizard)
Finally, I got it working bye adding a " (Quotation marks) for the first caracter of the OSDJoinPassword variable. Of course, I had to change the password for my user too.
Any ideas?
Am i missing something?
Thank you
Trying to run build & capture task sequence against Windows 10 Enterprise 1607 x64. Getting this error when trying to run sysprep? This has something to do with those modern apps. Any idea how to deal with this one?
so here is my issue. i am trying to create a updated image to deploy. i created the updated image and deployed it but when i do it doesnt auto join my domain and add my default profile. im assuming that its not completing the sysprep at some part, either when i capture the new image or when its running on the task sequences.
my old capture works just fine but when i try the new one it wont.
the task sequence is identical on both.
on the new image when it installs, it still has the administrator profile from the OS i used the capture the image which is what im thinking its not doing the sysprep on the capture but im new at this and still learning so im not sure.
neither the capture or the install give me an error.
does anyone have an idea on how i can fix this?
I downloaded our volume license iso of windows 7 from Microsoft then extracted it using 7 zip. In MDT, created a new windows 7 capture under operating system. Next I created a task sequence. When I go to update the MDT 2013 deployment share I get error below. The windows 7 version was 64 bit.
Server is fully patched and is running Microsoft Server 2012 R2. Can you advise what I can do to get around this error below so I can start to evaluate MDT.
=== Making sure the deployment share has the latest x86 tools ===
=== Processing LiteTouchPE (x86) boot image ===
Building requested boot image profile.
System.Management.Automation.CmdletInvocationException: Unable to open the specified WIM file. ---> System.Exception: Unable to open the specified WIM file. ---> System.ComponentModel.Win32Exception: The system cannot find the path specified
--- End of inner exception stack trace ---
at Microsoft.BDD.Core.BDDWimFile..ctor(String wimPath, Boolean forUpdate)
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.Runspaces.PipelineBase.Invoke(IEnumerable input)
at Microsoft.BDD.Wizards.UpdateProgress.WizardProcessing()
at Microsoft.BDD.Wizards.WizardProgress.InitiateWizardProcessing()
Dear all,
I'm trying to install Office 2016 with a configuration file (.MSP). The customization works fine.
My issue is when MDT install the application, it install normaly (Excel, word, etc... opens normally). But I get an Windows Installer error... When I do it manually it works fine.
The problem signature :
Problem Event Name:BEX
Application Name:MsiExec.exe
Application Version:5.0.7601.18896
Application Timestamp:557f3924
Fault Module Name:MSI161F.tmp
Fault Module Version:16.0.4266.1001
Fault Module Timestamp:55ba13c8
Exception Offset:0000adc6
Exception Code:c0000417
Exception Data:00000000
OS Version:6.1.7601.2.1.0.256.4
Locale ID:4108
Additional Information 1:e278
Additional Information 2:e278ee052d0bee6f82c872b65f2a2129
Additional Information 3:6de9
Additional Information 4:6de912981659ab9d5453e66bb66a5db1
My configuration in MDT :
Quiet install commande : setup.exe /adminfile 0_HEC_Config.MSP
Working directory : .\Applications\Microsoft Office 2016 Professional
Does anyone have an idea ?
I have just upgraded MDT 2013 to Update 2 (skipped Update 1) and tested one of many self contained Media deployment ISO images we have. These use a specific Task Sequence ID which is hidden from the Wizard using "SkipTaskSequence=YES" and"TaskSequenceID=..." in CustomSettings.ini.
Unlike the previous MDT2013 (non-updated) version, the install now fails to proceed past the "Wizard Ready" stage with the error 'Invalid DeploymentType of "" '.
The Deployment Type (NEWCOMPUTER) is not set in CustomSettings.ini (never has been), but the logs clearly show it is discovered correctly set (to NEWCOMPUTER) by ZTIGather and LiteTouch; but the Wizard log then reports it as equal to "" at the very end of the Wizard run. Same thing happens if I actually add "DeploymentType=NEWCOMPUTER" to customsettings.ini.
I reinstated the TaskSequence Wizard page based on a previous posting, selected my Task Sequence in the Wizard at install and voila it worked!
So what has changed? Why can I no longer skip the TS Wizard page? What is resetting DeploymentType from NEWCOMPUTER to blank? Where should I be looking? Why does an update make things worse?
Logs available, any and all help appreciated!
STEVE
I was wondering if anyone might have an idea on how to fix an issue I'm running into. The issue I'm running into is modifying machine accounts in AD that were created by a domain admin. When we first started using WDS and MDT for our imaging process as a company we started using a domain admin account to join the machines to the domain. Well with MDT storing that password in plain text we want to stop using that account and using a more toned down service account. Everything works fine if the machine isn't already in AD, our service account will join the machine to the domain like it should but when we try to join a machine that was created with our domain admin account we get a permissions issue.
Has anyone else had a run in similar to this and is the only option left to manually delete the machine before imaging? I've tried to run a PowerShell script during a task sequence but since the machine isn't joined to the domain the script isn't able to access AD.
I am deploying a custom wim of Windows 10 x64 enterprise. I built the image on VM and now trying out a USB media deployment. The Deployment goes through till finish with no errors. After the deployment I checked Device manager and had several bangs for missing drivers.
I am using the "Total Control" method.
- I verified the name structure of my Out of Box MDT Folder "Windows 10\HP EliteBook 840 G1"
- I verified the WMI name is "HP EliteBook 840 G1"
- I built a CAB file using the HP SDM and imported that CAB into my Deployment Share.
- I verified in the TS that the pre-install "Set Drivergroup" sequence has the value of "Windows 10\%Model%"
- I verified in the TS that the pre-install "Inject Drivers" sequence selection profile is set to "Nothing" and "Install all drivers from selection profile."
- I see drivers being injected during the pre-install phase of deployment.
- No network cable is ever plugged in during the deployment or any moment after the deployment finishes (so driver logs can be as clean as possible on client side)
- Checked ZTIDrivers.log and see lots of drivers being copied to C:\Drivers. I do NOT see a C:\Drivers folder after deployment (Should I?)
- BDD.log shows at the beginning "Unable to determine asset tag by WMI" but a few lines later in the log Property Model information is populated to be correct.
When it was all said and done I was able to verify some network drivers that did load were not the ones I imported (different versions, verified by updating driver and selecting my USB Deployment share Out of Box folder to search, it did load the driver from that search.) I also updated devices that loaded generic windows drivers with the drivers from the Out of Box Folder. Also, devices that had missing driver bangs were all able to be updated by manually selecting update driver and pointing the search to my USB Out Of Box Drivers folder.
So it seems my deployment is not loading any of my imported drivers and only loading built Windows drivers and I am not sure why. I have looked over logs but this is kind of new territory for me and I am sure I am overlooking something. I have to be, right?
You should be able to find the logs I think someone may need to help at this location: Logs here
Thank you for any help that could be offered!
Hi,
I'm setting up an MDT test environment mostly according to this excellent guide by Michael Niehaus. I'm in "Step 7: Configure the MDT production deployment share". In that step, we are directed to copy files from D:\Setup\Sample Files\MDT Production\Control folder to E:\MDTProduction\Control.
The only problem is, I can't find those setup files in any of the documentation leading up to this step. I can find setup files from other guides that might or might not be the same. It says that they should overwrite the existing bootstrap and customsettings file, but I don't know whether or not there are other files in that directory which should be copied over as well. If it's just a matter of configuring the 2 rule files according to the example, would it be necessary to overwrite the existing ones? I'm happy to help clarify anything that's unclear. Any help here would be much appreciated!
Thanks,
-G
we currently deploy Windows 10 images (with the 1511 update) to a small 500 clients in our infrastructure with MDT 2013 update 2 and ADK 1511.
As the 1607 update was released this month, we started updating our images to that version. We also noticed Microsoft released a new version of ADK (1607). The description states we need this in order to deploy Windows 10 images with the 1607 update in our network.
Running the setup for ADK 1607 however, we get an error saying we have to delete ADK in order to install the latest version.
This seems a bit drastic to me, and I was wondering if there was a simpler update procedure for ADK. I was also wondering if 1511 images can still be pushed using the 1607 ADK and the other way around.
There is a fullscreen popup when the deployment first gets to the desktop that has to be exited. Is there a way to suppress this window?
MDT v 8443. Windows 10 Pro 64, the wim is a capture of a fully updated VM that was otherwise unchanged
Hello community,
I have a huge problem with MDT2012 since yesterday: I cleaned my driver repository a little and now I cannot import driver CAB´s anymore, every time it ends with this error:
System.Management.Automation.CmdletInvocationException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index ---> System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
at System.ThrowHelper.ThrowArgumentOutOfRangeException()
at System.Collections.Generic.List`1.get_Item(Int32 index)
at Microsoft.BDD.PSSnapIn.Verifier.AddDriver(String theInfFile)
at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
at Microsoft.BDD.PSSnapIn.ImportDriver.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()
Funny: For testing I have created a second (new) "deployment share" and the same CABs gets imported without problems there. So the problem must be somewhere in my old share, but I have no clue how to fix this.
I crawled tho hole web and can not find anything! I don´t wont to move my whole share to the new one :(
Any advise?
Hello
This problem with ConfigMgr/MDT has been around for a while. With variables like SMSTSReserved1/2 and storing the passwords clear text.
In my scenario the NAA credentials are being used for connections or any MDT access.
When I do a webservice call GET the ZTIGather.log is logging all the necessary stuff to make this sort of a security risk.
For example:
CHECKING the [CallWebservice] section
Property UserDomain is now = DOMAIN
Property UserID is now = USERNAME
Property UserPassword is now = CLEARTEXTPASSWORD
Does someone has a good idea at least how to avoid this log from being written in ZTIGather.log which is afterwards copied to CCM Logs?
Many thanks.
I use wds to load windows 7 images onto our Dell PCs. I am able to do this successfully.
We recently purchased Dell OptiPlex 3040 that came with Windows10. I am not able to connect to the deployment share with these PCs. The following is the message I received when I attempt to image the PC:
A connection to the deployment share (\\server\deploymentshare$) could not be made. The following networking device did not have a driver installed. PCI\VEN_10EC&DEV_8168&SUBSYS_06BB1028&REV_15.
As a solution to THAT issue, I upgraded to WinPE10. This seems to have fixed the connection issue, as I no longer receive that error.
Now, however, I am not able to capture an image. These are the steps I follow: open \\ImageServer\DeploymentShare$ . Run LiteTouch.vbs. Follow the steps to capture the reference.
When I do this, I don't get any errors, and the status bar loads as if its working. But then it just goes away and nothing happens.
Ryan Piselli