Hello
For some reason, whenever I use MDT to deploy a Windows 10 image , after the first login the MDT process doesn't continue? I try to manually kick of the MDT Process by launching the .vbs script but nothing appears!
Any idea's please?
Thanks
Hello
For some reason, whenever I use MDT to deploy a Windows 10 image , after the first login the MDT process doesn't continue? I try to manually kick of the MDT Process by launching the .vbs script but nothing appears!
Any idea's please?
Thanks
Hello all
I am running a Windows 10 ZTI install using SCCM 2012 R2 Sp1 CU3. Image captured using MDT 2013 Update 2.
Deploying to a Hyper-V 2012 R2 VM.
Very weird issue. Deployment kicks off fine, past the point of WIM application to the OSD Install phase.
The machine comes up, and basically at the point of ZTIConfigure, im getting an error in the specialize pass.
Windows could not parse or process the unattend answer file for pass [specialize]. The settings specified in the answer file cannot be applied. The error was detected while processing settings for component [Microsoft-Windows-Shell-Setup].
This is from my setuperr.log in unattendgc
2016-06-11 12:14:48, Error [Shell Unattend] ComputerName: failed to set the computer name [hr=0x80070057][gle=0x00000057]
2016-06-11 12:37:28, Error [windeploy.exe] Setup.exe failed, returning exit code [0x1f]
2016-06-11 12:37:28, Error [windeploy.exe] Failure occured during online installation. Online installation cannot complete at this time.; hr = 0x80004005
From my Setupact.log below from unattendgc:
2016-06-11 12:14:48, Info [Shell Unattend] Running 'specialize' passExcerpt from my setupact.log from unattend showing architecture.
2016-06-11 12:13:47, Info [0x0601c1] IBS InstallWindows:Install Path = C:\WINDOWS\system32\oobeMy Unattend.xml excerpt is below. I have taken this from the failed build. Notice that the computername below under the am64 section is specialize is set correctly. However the build fails. The following x86 computername field highlighted is currently blank when the build fails. But if I edit the x86 field slightly furher down in specialize as highlighted (before the install phase starts via f8 command prompt), the build succeeds.
Why would it parse the x86 section as well for a computer name? I am using a standard MDT install, Windows 10 64bit install. And if it parses it anyway, why is it failing as it has already populated the AMD64 section.
The OSDCOmputername is retrieved from SCCM in a pre imported object in a build collection.
<component name="Microsoft-Windows-Shell-Setup" language="neutral" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Any help appreciated, really don't understand why its doing this - could it be something with using Hyper-V?
Thanks
Ian
Hi,
Scenario
Windows 10 Education VL - 1511
MDT 2013 Update 2
Windows 10 ADK
Has anyone else experienced the following issue: deployment of the standard above mentioned OS (import from ISO) fails before the first logon during deployment with the below error when the deployment share rule property SkipTimeZone=YESis set. Removing this property enables the OSD to continue and complete as expected.
"Windows could not complete the installation. To install Windows on this computer, restart the installation"
Many thanks.
Hi folks. I'm trying to use sysprep and capture task sequence for the first time and right from the start I have an error. Right after the task sequence start I get the below error:
Help appreciated. Thanks.
In MDT wizard studio, how to add timer that after 10 seconds goes to next pane if no user interaction occurs?
For example, there is a pane which asks for computer name and domain membership. Everything is filled with default settings. If technician wants to change computer name to something else, he has 10 seconds to interact with pane interface. So if he changes computer name or do something else, timer stops.
I couldn't find any HTA script block that could do it.
(I have updated the question below)
Hi,
I receive this error when the build process initiates sysprep. I uninstall some apps offline during Post-Install, but the error always points to one of the apps, I want to keep in the image. Perhaps it is not related, even though Microsoft suggests this is the cause:
Sysprep fails after you remove or update Windows Store apps that include built-in Windows images
I have found two suggested solutions (Sysprep broken in Windows 10 Build 9926)
1. Make sure the virtual machine you are using for reference images never connects to Internet.
2. Prior to run sysprep, have the task sequence delete all updated packages using PowerShell.
First option is not possible for me – I need the reference image to be online.
The second option is the same as Microsoft suggests. But how can I use a Task Sequence to delete only updated packages automatically before sysprep kicks in?
Adding the setuperr.log:
2016-05-24 20:40:15, Error SYSPRP Package Microsoft.WindowsAlarms_10.1510.12020.0_x64__8wekyb3d8bbwe was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image. 2016-05-24 20:40:15, Error SYSPRP Failed to remove apps for the current user: 0x80073cf2. 2016-05-24 20:40:15, Error SYSPRP Exit code of RemoveAllApps thread was 0x3cf2. 2016-05-24 20:40:15, Error [0x0f0082] SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'SysprepGeneralizeValidate' from C:\Windows\System32\AppxSysprep.dll; dwRet = 0x3cf2 2016-05-24 20:40:15, Error SYSPRP SysprepSession::Validate: Error in validating actions from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x3cf2 2016-05-24 20:40:15, Error SYSPRP RunPlatformActions:Failed while validating SysprepSession actions; dwRet = 0x3cf2 2016-05-24 20:40:15, Error [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x3cf2 2016-05-24 20:40:15, Error [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep generalize internal providers; hr = 0x80073cf2
I did not remove theMicrosoft.WindowsAlarms App.
Also adding some logs (I am a little desperate to get some help on this issue):
UPDATE:
I believe I know the cause of this issue now. My build process takes more than an hour, because we have some rather large applications to install. If Windows 10 is online for more than 1 hour, it starts staging appx packages. It is these packages that sysprep
does not like. So it has nothing to do with the already uninstalled apps.
If I run this after sysprep has failed:
Get-AppxPackage –Allusers | Select PackageUserInformation, Name
I get this list:
Sysprep fails at the first staged package - the WindowsAlarms.
So perhaps my question should be:
- How can I remove these staged packages?
- If I uninstall theses staged packages, will it have an impact on new users for whom I want these apps to work?
We are using MDT and using replication to 9 other sites. The deployment at our main building runs without a problem. However, the deployment was failing at the other sites. We found that in the Control folder, ts.xml, the deployment was still pointing to our server at the main building. Manually changing this to each specific site solved our problem.
Question is when replication is performed this file will be over written again. How can we configure so that the ts.xml file is specific for each school without having to manually correct it after each replication.
Thanks in advance for any help.
I have written a user exit script to set OSDComputerName from a text file using the MAC of the computer. The relevant files are here https://onedrive.live.com/redir?resid=C4BC55BF27E7E399!4420&authkey=!ADh-gRfiBmNjHEM&ithint=folder%2c
If I pxe boot to the deployment wizard the "Computer Details" page shows OSDComputerName would be "PC-<MACADDRESS001>". If I continue imaging anyway, after the machine boots into Windows, I can simulate the gather process using the process outlined here http://deploymentresearch.com/Research/Post/293/Save-time-and-avoid-pain-Create-a-MDT-test-environment and the resultant log shows me that OSDComputerName would be set as expected (the MAC is found in macfile.txt). If I then reboot and pxe boot back to the deployment wizard, now the "Computer Details" page shows the correct name from macfile.txt. It's almost as if OSDComputerName is being read from somewhere else.
Can anyone explain this?
Is there a better way to name machines using a text file in the form of <MAC> = ComputerName? This is something we've been doing since XP using vbs scripts that I've written, I'd like to begin leveraging MDT for naming but I need to keep this name file and its layout.
Running MDT 2013 Update 2
Installing Windows 7 x64 in a Hyper-V VM on a Windows 10 Host. I need to capture the WIM of my Gold Image.
If I look in the captures folder in the deployment share, I can see that 1 or 2 GB of the WIM makes it, so it would not seem to be a network and/or permission issue.
Similar solution works in my home lab; the problem occurs on the real server at work.
What would be the most common issues to cause this?
Thanks!
Hello
I have my standard TS Setup and working but i have to boot the computer using either psx or a usb drive.
I have tried windows 7 start - run and run the litetouch.wsf from the deployment share this works until it tries to boot into WinPE and install's the OS. Then i get Failure 9808 Error - Performing a Refresh from a newer OS to and Older OS is not supported.
The Machine is a windows 7 and i want it to have windows 7 on it, the only difference i can see is the there has been Windows Updates applied.
Is this why MDT thinks that it is a newer OS?
Im using MDT 2013 Update 2
Thanks
I've got a Windows 10 update Task Sequence. We do not have SCCM and I'm wanting to automatically kick off the task sequence without remoting into machines we're deploying to. I started out just trying to run "\\mdtserver\prod$\scripts\LiteTouch.vbs /TaskSequenceID:Win10x64Upg /SkipWizards:YES" (including all the required data, not just what's shown here). It didn't work, so then I created a newCustomSettings.ini file, CustomSettings-ZTWin10Upg.ini in the Control folder. I called it using "\\mdtserver\prod$\scripts\LiteTouch.vbs /rulesfile:CustomSettings-ZTWin10Upg.ini". I tried doing these both just by WinKey+R and typing in the path and using a batch file.
The CustomSettings-ZTWin10Upg.ini File:
[Settings] Priority=Default Properties=MyCustomProperty [Default] OSInstall=Y SkipCapture=YES SkipAdminPassword=YES SkipProductKey=YES SkipBitLocker=YES TaskSequenceID=WIN10X64UPGRD DeploymentType=UPGRADE SkipTaskSequence=YES SkipWizard=YES SkipFinalSummary=YES SkipSummary=YES FinishAction=REBOOT SkipBDDWelcome=YES SkipComputerBackup=YES SkipUserData=YES SkipDomainMembership=YES SkipTimeZone=YES TimeZoneName=Eastern Standard Time SkipLocaleSelection=YES UserLocale=en-us KeyboardLocale=en-us UILanguage=en-us WSUSServer=http://XXXXX:XXXXX JoinDomain=XXXXX.com MachineObjectOU=OU=XXXXX,OU=XXXXX,DC=XXXXX,DC=com DomainAdmin=XXXXX DomainAdminPassword=XXXXX DomainAdminDomain=XXXXX.com UserDomain=XXXXX.com UserID=XXXXX UserPassword=XXXXX EventService=http://XXXXX:XXXXX
It again did not work. What is happening is my TS kicks off, runs the update, goes all the way through installing Windows 10. At the end it tries to log in and fails (wrong password for some reason) and then if I log in as the Administrator on
the machine, it pops up like it's trying to start the task sequence over, says it found a task sequence already in progress in an unexpected point, then goes flashing through the TS windows again, runs the gathering task and fails since it's already on 10.
Never cleans up after itself. It shows in the monitoring section of MDT as "Running" at 29% on step 8 of 24 and just sits there.
I finally made a backup of my CS file and renamed the ZT CS file to CustomSettings.ini. I then proceeded to run theLiteTouch.vbs script, which worked this time completely automated, did everything and finished. I ran it again this time calling theLiteTouch.vbs from a batch file, worked again. So something about adding parameters to the call ofLiteTouch.vbs is breaking the process :/
Is there something special I'm missing you're supposed to do when you pass parameters that way?
So I've been using MDT on my local machine and I can't seem to get it to connect properly. It keeps saying I have invalid creds. I have given permissions for the admin to have access the shares.
Bootstrap.ini -
[Settings] Priority=Default [Default] DeployRoot=\\GENJI\MDTBuildLab2$ SkipBDDWelcome=YES UserID=Strepo UserPassword=passwordIve tried .\Strepo and GENJI\Strepo. I've even started over with a new virtual machine. I have also done the whole regenerate boot images through the update deployment. The connection to the deployment is fine but the creds aren't good. I've even took out the creds in hope that I was see something from the MDT side but that still didn't even work.
any ideas on how to resolve this???
Is it possible to find out the existence of the TPM chip if it is disabled from the BIOS?
wmi win32_tpm class does not exists until its enabled from the BIOS but that could mean that it is not there?
device manager has no indication either until activated in the BIOS?
Thanks.
<![LOG[Executing command line: netsh wlan add profile filename="WiFi-burkewpa.xml"]LOG]!><time="08:56:06.678+420" date="06-08-2016" component="TSManager" context="" type="1" thread="4808" file="commandline.cpp:828"><![LOG[Process completed with exit code 1]LOG]!><time="08:56:07.860+420" date="06-08-2016" component="TSManager" context="" type="1" thread="4808" file="commandline.cpp:1124"><![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="08:56:07.860+420" date="06-08-2016" component="TSManager" context="" type="1" thread="4808" file="instruction.cxx:805"><![LOG[Failed to run the action: Add burkewpa. Incorrect function. (Error: 00000001; Source: Windows)]LOG]!><time="08:56:07.860+420" date="06-08-2016" component="TSManager" context="" type="3" thread="4808" file="instruction.cxx:911">First time playing around with MDT and I'm starting to beat my head against the wall. Using MDT 2013 SP2 to try and deploy Windows 10 to some Surface 3 tablets. Right now I'm battling with getting the wifi profile to add. I found this article http://www.deploymentshare.com/post/how-to-deploy-a-wireless-profile-using-mdt and double and triple checked it. In state restore under Custom Tasks I created a Run Command Line task that runs netsh wlan add profile filename="WiFi-burkewpa.xml" that starts in %deployroot%\Scripts\. In the Scripts folder it has the WiFi-burkewpa.xml file. If the command is run in Windows it works perfectly, but if it runs as part of the task sequence it gives the error listed above in the code block. Any ideas?
Hey peepz,
I have setup MDT on a WDS server and all works well.
I then installed MDT on another WDS server/different building and then copied across everything in the $MDTDeploymentShare folder from the currrent to the new. Changed the bootstrap file to reflect some different server info. It all works fine as it should.... BUT
when i go to update the DeploymentShare on the current after making changes it is quick to regenerate an image, yet on the new server it takes 30-60 minutes. both servers have the same resources allocated and wondering whether there is a file i need to edit that lets it know its know its not Generating the DeploymentShare for the first time i hazard a guess each time??
THX
Hi all,
Been having an issue ever since Windows 10 "forced" update was uploaded by Microsoft.
They have changed the update that "forces" Win10 a few times...and we can't really keep up here, and now, everytime I deploy Windows 8.1 Pro to a computer using MDT, the whole thing halts until I tell it to skip the Win10 upgrade.
Is there a way to configure MDT (using a command, a task, an Unattend.xml configuration, etc.) to have this OOBE screen skipped ?
Thanks in advance all :)