I created a base VM for someone to remote into and add software. I added a pause to the TS so this could be done.
Now they have finished and I'm in the VM, but clicking on Resume does nothing. I still have a _SMSTaskSequence folder and the MININT folder on C: but nothing takes off from the Resume shortcut.
I need to get this captured and I'm relying on the Resume TS to kick off as it should.
Any ideas?
If anything, for now, what can I run manually to get the TS to continue on to do a Capture?
Hi All,
I am going around in circles with creating an existing Windows 10 full deployment with USB Offline.
I have followed the MS Docs guide to do this but it fails every time and it is taking too long to generate the ISO each time to test it. Does anybody have a full step by step guide with how to do get this to work?
I have used these guides and followed them step by step already and I have had no luck in successfully installing the Windows 10 OS offline on a USB.
##windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt#use-offline-media-to-deploy-windows10##
vkernel.ro/blog/creating-an-offline-mdt-deployment-media
I can get the SMSTS logs and a picture of deployment summary errors if required?
Hi,
In my task sequence I have a few Powershell scripts. I use the task "run powershell script". There are 2 scripts which returns a ZTI Non-zero return code by ZTIPowerShell, rc = 1. In the final notice I get 2 warnings and see the warnings in the
BDE.log too.
However the scripts executes just fine. I understand from the log the return code is 1. I see in the task, one can define success code. By default it is 0 and 3010. I added 1 in the hope the script would not return a warning. It didn't. Then I replace the 0 with 1. Unfortunately no change.
How can I tell MDT that the script ran fine? It's more a cosmetic issue which bothers me.
Thanks
Edy from Switzerland
This is fairly unrelated to MDT itself, but wondering if someone has a solution to a Checkpoint issue I have...
I have an initial Checkpoint made of my VM and two more after that. I'm trying to either select one or delete it but all it shows is
Loading details for selected items...
and will not do anything. If I try to remove it, I get:
An error occurred while attempting to delete the selected checkpoint, failed. The operation passed a parameter that was not valid.
I'd like it gone. I guess it wouldn't matter if it stayed around but I don't need it. I can rename it BAD or something and ignore it but I'm wondering about the error...and sure don't want to corrupt my whole checkpoint chain.
Hi all,
I've been trying to build an image with custom Internet Explorer settings, on Windows 10 1803. I've installed a clean copy of Windows 10 Pro, booted to Audit mode, made my desired changes, sysprep'd with a CopyProfile answer file, captured using DISM, and deployed with WDS, but none of the changes I make to IE stick.
Any fix out there?
Hello guys,
does one of you know the problem that the Bitdefender deletes the shortcut LiteTouch.lnk and classifies it as a Trojan (Trojan:Script/Cloxer.A!cl)?
startup: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\LiteTouch.lnk
The installation doesn't continue automatically. Is it possible to deactivate Bitdefender in the offline image?
Best Regards,
Stephan
I built a VM (three times) using Standard Client TS. Added a Suspend and took a Checkpoint.
Then I installed a few things, shut it down, replaced the checkpoint with a new one.
Launched the VM and clicked Resume. It began the rest of the steps, WinPE, all that then I noticed Sysprep started and went away quickly.
The VM rebooted and went right to the desktop again, now with the Resume shortcut gone.
Hi All,
I've trying for the past weeks to find a solution to an issue that I have when upgrading Windows 7 Pro machines to Windows 10 Pro (versions from 1803 to 1903) via MDT.
In order to have the have the computers upgraded, I've created a Standard Client Upgrade Task Sequence and setup MDT's rules accordingly so that the process is simply started by massively pushing a .bat file.
The issue that I've noticed is that in many machines, when the Upgrade OS step is complete, we are presented with a Log On screen which states that the .\Administrator account is disabled, please contact your system administrator. Apparently, once the upgrade
is done the system tries to log in under built-in Administrator (which by default MDT uses) in order to go ahead with the remaining Task Sequence steps.
This happens to many machines as stated above, not to all, so this does not seem a GP related issue. In case it helps, there is no GPO that disabled the built-in Administrator in the client machines.
I've tried running adding CMD tasks that enable the .\Administrator, I've also tried modifying in the unattend.xml, but nothing seems to help.
Any help is appreciated!
We are using SCCM 1902 and Windows 10 19H1. Trying to create the MDT Task sequence using SCCM 1902 but BDD WMI classes are missing.
Please suggest if SCCM 1902 and Windows 10 19H1 are supported with MDT latest version?
Running MDT 8456.
On the Details tab of an application in the "This can run only on the specified client platforms:" section neither Windows Server 2016 and Windows Server 2019 appear, is this by design?
I see a few quirks in 2016, nothing major just annoyances...
Quick Access, pointing it to This PC, after capturing, still points to Quick Access.
Setting UAC to Never Notify on the VM doesn't stay after Capturing/Deployment.
Maybe there are registry settings to affect these changes? It's always held in 7, 1703, 1803. Now I'm deploying Server2016 to our new servers (about 50 of them) and would like this to hold.
Hi all
I am new to MDT 2013 and self taught over the last few weeks.
I am trying to install a custom Win10 image. I have this working, my problem is the recovery. At the moment I install Win10 through MDT 2013 onto the C: drive. MDT also sets up a hidden RECOVERY drive and copies over WinRE files. I activate windows, install office and activate. I will then SYSPREP the pc to OOBE and shutdown for the customer.
I then boot to WinPE and use DISM to capture for a recovery image. I put the captured WIM file on the recovery drive and power off.
When I tried to use the recovery WIM file, it does not use this WIM file but the original install files that I used to deploy the original image. All my customisation is lost.
Basically what I want to do is:
1. Deploy a standard image
2. Customize the image with Office and other software including activation
3. Sysprep to OOBE and shutdown
4. Capture the custom image and place on recovery drive
5. Be able to deploy the custom image as a recovery image either through SYSTEM IMAGE RECOVERY (if pc is not booting) or from RESET PC in windows.
Any help would be great.
Jay
I have been managing an MDT environment for the last 3 - 4 years and I was wondering if anyone has ever managed to deploy an Application task sequence only through MDT and Wireless connectivity?
I know that there is a configuration change that I need to do in the ZTIUtility.vbs file, but I just want to see if anyone has successfully done this.
Hi,
I am upgrading Windows 7 machines to Windows 10 1809 x64.
We do some custom steps before the upgrade (a bios update mainly), but they seem to behave fine.
Once the upgrade step (LTIApply) is running, the system reboots a few times, as expected, but during the final reboot of the upgrade process (after which the upgrade step finishes), the MDT starts running before Windows has fully booted.
When Windows gets loaded by the BIOS, the Windows logo appears together with the loading dots, at that moment a terminal pops up, the boot process is halted, and MDT starts running. The MDT runs correctly from there, including reboots, except for the suspend
step. The logs indicate that the suspend step has correctly been processed, but the tasksequence continues. When finished, the deployment summary is shown, still in this boot state.
Alt + tab can be used to switch between the terminal and the windows logo, a cursor is not yet loaded.
It would be nice if you guys could help me figure out why the machine won't boot into Windows before finishing the TS.
My TS is to large to post here, but custom settings is included.
TS: https://drive (dot) google (dot) com/open?id=1OwJ54FEsaRKwnZmrgjYIH3XidDyJsXl7
MP4 showing the problem: https://drive (dot) google (dot) com/open?id=1eBq9vxlkdn-d_AWAC8Rj7y5Hka_jX0G8
Custom settings:
[Settings] Priority=TaskSequenceID, Default Properties=MyCustomProperty ;;;;;;;;;;;;;;;;;;;;;;;; ;; Default settings ;; ;;;;;;;;;;;;;;;;;;;;;;;; [Default] _SMSTSORGNAME=Windows Upgrade _SMSTSPackageName=Upgrade %MODEL% OSInstall=Y SkipCapture=YES SkipAdminPassword=YES SkipProductKey=YES SkipComputerBackup=YES SkipBitLocker=YES ;Bitlocker settings BDEinstallSuppress=NO BDEWAITForEncryption=False BDEDriveLetter=S: BDEDriveSize=2000 BDEInstall=TPM BDERecoveryKey=AD BDEKeyLocation=<**Deployment share**>\Backup\Bitlocker TPMOwnerPassword=******** SLShare=<**Deployment share**>\Logs SLShareDynamicLogging=<**Deployment share**>\Logs\Dynamic EventService=<**EventService**> ;Bios version, Make, Model (Voor Generic BIOS upgrade script (Dell bios upgrade) ;Dell = SMBIOSBIOSVersion + Make + Model ;Hewlett-Packard = BIOSVersion + Make + Model ;LENOVO = SMBIOSBIOSVersion + Make + ProductVersion SMBIOSBIOSVersion=#SetSMBIOSBIOSVersion()# BIOSVersion=#SetBIOSVersion()# ProductVersion=#SetProductVersion()# UserExit=TestTheUserExit.vbs
I've been using MDT for deployment for about a year now, and have captured WIM files for my reference image multiple times in the past. However, recently I have been failing to capture a good reference image for Windows 10 1809 and 1903. Even if the whole process goes fine, without any errors, the captured WIM at the end is always only 4,247KB. As great as it would be to have a working image as small as 4MB... this one does not work. I've found only one other post about this problem, here https://social.technet.microsoft.com/Forums/en-US/8d74d46c-df09-45a0-bd83-ff18a7e887f2/captured-windows-10-wim-file-too-small?forum=mdt
The eventual conclusion they came to was that it was capturing the mounted CD drive instead of the drive containing the Windows directory. I do not believe this is happening in my case, as my logs are stating that I'm capturing the C: drive, which is correct. I have also tried all the proposed solutions in that post to no avail. I have not modified any default settings regarding the backup drive. I was initially encountering this problem using MDT2013, but have since upgraded to version 8456 and experience the same problem still. I've tried everything I can come up with in the past few months, but am still unable to create a working reference image.
Any advice would be very welcome! See below for links to my BDD log files shared from Box.com. The first is a recent one, which is not working. The second is from the last time I was able to create a working reference image.
Not working - https://hopeinternational.box.com/s/0i4gig7buyv7sicx1ooi3zrpuyd3m4k3
Working - https://hopeinternational.box.com/s/0as9j0b3n86a638qw0xxmh1vopw9ih1k
Thanks in advance!