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

Has Anyone Successfully Created USB Offline Media Split Wim Setting with at Least 2 WIM Files

$
0
0

Pretty much at my wits end with this, I have been trying to get the split wim  setting to successfully complete with more than 1 wim file included in the selection profile.

Currently the sweetspot is 1 wim file, always completes, if I add another os wim to the selection profile I 100% get a failure as per the screenshot.

I have had this issue since the feature has been introduced in the various incarnations of MDT 2013 U1\U2.

I am running the latest , greatest versions of MDT, pretty much tried every permitation to get it to work and have wasted days of my life testing this feature.

It would be great if someone could definatively say more than one wim in the selection profile will complete sucessfully.

Cheers

Ewen.


Switch language keys

$
0
0
Hi! I have didn't found an answer of my question on the Web, so I decided to ask it here - is possible via TS or CustomSettings.ini set switch language keys (ctrl+shift or alt+shift) during OS deployment?

ZTI ERROR - Unhandled error returned by LTIApply: Path not found (76)

$
0
0

Hi! Getting ZTI ERROR - Unhandled error returned by LTIApply: Path not found (76) during windows 7 x86 Ent installing. LTIApply log:

<![LOG[Microsoft Deployment Toolkit version: 6.3.8298.1000]LOG]!><time="09:54:42.000+000" date="01-25-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[The task sequencer log is located at X:\windows\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.]LOG]!><time="09:54:42.000+000" date="01-25-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Will boot into Windows PE architecture x86 to match OS being deployed.]LOG]!><time="09:54:42.000+000" date="01-25-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[OSDTargetDriveCache was determined earlier : C:]LOG]!><time="09:54:42.000+000" date="01-25-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Property OSDTargetDriveCache is now = C:]LOG]!><time="09:54:42.000+000" date="01-25-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Property OSDisk is now = C:]LOG]!><time="09:54:42.000+000" date="01-25-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Open Control File: OperatingSystems]LOG]!><time="09:54:42.000+000" date="01-25-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[------  Applying Windows image using DISM.exe ------]LOG]!><time="09:54:42.000+000" date="01-25-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[LTI applying image \\sno-fs03\d$\deploymentshare\Operating Systems\Windows 7 x86 Ent\Sources\install.wim using DISM]LOG]!><time="09:54:42.000+000" date="01-25-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Event 41023 sent: LTI applying image \\sno-fs03\d$\deploymentshare\Operating Systems\Windows 7 x86 Ent\Sources\install.wim using DISM]LOG]!><time="09:54:42.000+000" date="01-25-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Property SourcePath is now = \\sno-fs03\d$\deploymentshare\Operating Systems\Windows 7 x86 Ent]LOG]!><time="09:54:42.000+000" date="01-25-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Cleaning off old operating system]LOG]!><time="09:54:42.000+000" date="01-25-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ZTI ERROR - Unhandled error returned by LTIApply: Path not found (76)]LOG]!><time="09:54:42.000+000" date="01-25-2016" component="LTIApply" context="" type="3" thread="" file="LTIApply">
<![LOG[Event 41002 sent: ZTI ERROR - Unhandled error returned by LTIApply: Path not found (76)]LOG]!><time="09:54:42.000+000" date="01-25-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply">

Why so? Also, BDD.log have this line

<![LOG[Vista identified, skipping update of Device Path]LOG]!><time="09:54:40.000+000" date="01-25-2016" component="ZTIDrivers" context="" type="1" thread="" file="ZTIDrivers">

Why Windows 7 identified as Vista?

Restoring Windows 7 64 Bit in UEFI mode and Performing an In-Place Upgrade of Windows 10 with UEFI Native (Secure Boot On) setting.

$
0
0

I was asked by my company to start offering our customers Windows 7 64 Bit in UEFI Mode and the ability to perform an In-Place upgrade of the same device running on Windows 7 64 Bit UEFI to Windows 10 in the future, Sounds easy, but the requirement doesn't end there. During the course of an In-place upgrade the device should run on Native UEFI (Secure Boot ON) despite the fact that Windows 7 doesnt support secure boot.

I was caught totally off guard as to what i have been told about UEFI and CSM. As i have been thinking that UEFI CSM is nothing but Legacy BIOS similar to the way we have been imaging Windows 7 all these years by formatting the disk as an MBR Partition.

Though CSM (Compatibility support Module)  is a component of the UEFI firmware that provides legacy BIOS compatibility by emulating a BIOS environment, allowing legacy operating systems and some option ROMs that do not support UEFI to still be used.

Until i realized that you could restore Windows 7 in UEFI Mode by converting the Disk to GPT and ensuring that you set the BIOS to UEFI CSM Mode (Yes UEFI CSM Mode!before that) of course minus the secure boot as Windows 7 64 bit doesnt support it yet unless you do an inplace upgrade to Windows 10 later and turn on the Secure Boot . Now nobody in the world tells you that or may be not explained in simple terms that you need to use UEFI CSM Mode for Windows 7 64 bit to work on UEFI and additionally also qualify for an In-Place upgrade for Windows 10 with Native UEFI Setting (Secure Boot ON) without having to re-image the device. 

Now that i have accomplished this task. My question is does MS support switching over to Native UEFI after an in-place upgrade to Windows 10 from Windows 7 64 Bit UEFI CSM?  if Yes i could then simply turn on Secure Boot after the in-place upgrade. Please let me know if my question is not clear enough i will try to rephrase it. And sorry for the long post i couldnt shorten it as it had to be comprehensive.

Deploying 7 SP1 x64 to NVMe drives resulting in BSOD 0x7B

$
0
0

Ok, so a little bit about my setup. I'm using MDT 2013 U1. I have a wim of Windows 7 Pro 64 SP1.

I am attempting to deploy to a Dell Precision 7710. This device uses 2 M.2 PCIe SSD's in RAID1 (using Intel RST).

I have added Hotfix 3366972 by injecting it into the wim using dism (using this https://support.microsoft.com/en-us/kb/2990941 method). I did NOT inject the hotfix into the boot wim, because it is WinPE 10, so should be supported natively (my Windows 10 installation disk can install to the drives without issue). I have also injected the Intel RST f6flpy-x86 (downloaded from https://downloadcenter.intel.com/download/25165/Intel-Rapid-Storage-Technology-Intel-RST-RAID-Driver ) drivers into the boot wim, and have the f6flpy-x64 drivers injected into the installation.

I can boot into the MDT boot wim just fine. I select my task sequence, it deploys, and reboots. Upon booting Windows, the PC has a BSOD. When attempting to boot into safe mode, it halts at DISK.SYS before BSOD'ing. Obviously it doesn't like that.

I have attempted booting into an installation disk and removing DISK.SYS from C:\Windows\Drivers or C:\Windows\System32\Drivers, I cannot remember which at the moment. I didn't expect that to work because it was specifically disk.sys, and it didn't, but I figured I'd tried because I've had success removing other faulty drivers before. I have also tried reinstalling the RST drivers by booting into an installation disk and using dism to inject the drivers directly, with no effect. As a last ditch effort, I even tried running a chkdsk /f, which didn't work.

I have never had to deploy to NVMe disks before, and I am truly stumped. I know my org's switching to Windows 10 come March / April, but we haven't converted yet, and our images aren't "Golden" yet, so my manager isn't allowing us to just image this one with 10 early.

Anybody with any ideas?

MDT 2012: Application only TS Reboot Autologon problem

$
0
0
When the machine restarts it attempts to logon as Administrator but fails with a password error. Where do I tell it the password to use since there is no UNATTEND.XML?

Intermittent Error when installing Software Only on Windows 10

$
0
0

This is the error that I am getting

Application Install - Roxio Easy CD Creator 12.1 returned an unexpected return code: -1073741818 ZTIApplications 1/25/2016 9:16:36 AM 0 (0x0000)

I have deployed literally hundreds of Windows 7 and Windows 8 machines. I only get this error intermittently on Windows 10.

Where should I start when troubleshooting?

Thanks,

Rebooting Issues with Deploying to a Optiplex 7040-Setup never completes.

$
0
0

We are trying to use both MDT and SCCM to reimage this unit (Optiplex 7040). The imaging process completes normally. When the unit restarts, it goes into a constant Repair boot loop. I have rebooted it in safemode and then notice that on AMDKMPFD.sys, the unit will restart. Both deployments have been configured to use ONLY drivers for the 7040. Anyone had this issue?

I have created a MDT task sequence isolating the drivers for the 7040 and it still has the issue.


Windows 10 upgrade skipping the Post-Processing group

$
0
0

Upgrading Windows 7 Enterprise x64 to Windows 10 Enterprise x64. The upgrade task sequence appears to work fine with no errors, but the Post-Processing group does not run. Looking at the smsts.log file, it is because "Registry value HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Windows\Win10UpgradeStatusCode does not exist".

What puts that registry value there, and why would it NOT put it there? The upgrade itself seemed to go well.

Driver Found But Not Installing - MDT 2013

$
0
0

I'm working on a Windows 10 test image and I'm trying to install some USB 3 drivers on an older HP systems. I've found drivers that work from HP that were for Vista originally. I can update them in Device Manager but they don't seem to install in MDT 2013. 

ZTIDrivers.log shows the drivers are found and copied to the machine but when I look at the system after deployment, they're not installed in Device Manager.

Is there a command line method to force the installation / detection of a specific .inf file?

This is what my ZTIDrivers.log shows

Found a driver for PCI\VEN_8086&DEV_3A36: {57c8c9c8-f696-4349-b4c9-84c636e3542e} from \\MDT000\DeploymentShareBareMetal$\Out-of-box Drivers\System\2008s4el_9.1.0.1012_9DA8BEA05AD6B17A06B9EAC51A20BC7E89C76C7E\ichausb.inf

Validating connection to \\MDT000\DeploymentShareBareMetal$\Out-of-box Drivers\System\2008s4el_9.1.0.1012_9DA8BEA05AD6B17A06B9EAC51A20BC7E89C76C7E

Copying drivers from "\\MDT000\DeploymentShareBareMetal$\Out-of-box Drivers\System\2008s4el_9.1.0.1012_9DA8BEA05AD6B17A06B9EAC51A20BC7E89C76C7E" to "C:\Drivers\System\2008s4el_9.1.0.1012_9DA8BEA05AD6B17A06B9EAC51A20BC7E89C76C7E"

About to run command: cmd.exe /c xcopy /seihycd "\\MDT000\DeploymentShareBareMetal$\Out-of-box Drivers\System\2008s4el_9.1.0.1012_9DA8BEA05AD6B17A06B9EAC51A20BC7E89C76C7E" "C:\Drivers\System\2008s4el_9.1.0.1012_9DA8BEA05AD6B17A06B9EAC51A20BC7E89C76C7E" 1> NUL 2>NUL



Orange County District Attorney

Controlling Default Selected Task Sequence in Wizard

$
0
0
How do I specify the default selected Task Sequence in the MDT deployment wizard menu?

Orange County District Attorney

Having Trouble Importing Windows 10 Reference Image into MDT Operating Systems.

$
0
0

I have captured a Windows 10 build 1511 reference image using MDT and am trying to import into MDT Operating systems so it can be deployed. However the image says it imports successfully but then does not show up in the list. It does copy the files however to the the Operating systems folder. 

I have been able to import a VLSC windows 10 build with no problems. 

Just updated MDT to 2013 update 1 and upgraded the share etc. 

MDT Deployment To Windows 10 Windows To Go?

$
0
0

We have a Windows 10 deployment that lets us name the PC with custom names, installs drivers, joins the domain and installs several applications.

With Windows To Go, I copied the sysprepped WIM file into the Windows To Go creator wizard, but it ends up being a lot of manual work.  We have to go through the OOBE wizards, setting privacy settings, enable Bitlocker and and create an admin account manually that we will only have to remove later.   It also automatically creates a random computer name that we have to change later.

Then we have to rename the PC, enable the administrator account and set a password, rename the computer using our naming convention, join the domain, delete the first user account and profile and then install applications.  Lots of time consuming work.

Is there any way to use automate setting up Windows To Go in a similar manner as deploying to a physical machine via MDT?



Created Media, USB installs > 4GB and UEFI

$
0
0

We have some devices without network adaptors or docking stations that need to have their images loaded from USB sticks. They use UEFI so any bootable media needs to be fat32 with its inherent file size limits. Trouble is the ISO created by MDT is ~14Gb.

How do I get around this?

How to add Intel chipset drivers to MDT 2013

$
0
0

I've added the Lenovo SCCM driver package to MDT 2013 Update 1.

We've pushed out a build and all is fine and drivers are installed from DriverGroup001 except for the Intel Chipset drivers which are missing.

Lenovo SSCM driver package readme advises "Intel AMT driver, Intel Chipset, Intel Thunderbolt driver, Lenovo Monitor driver are not included in this package because .inf installation is not supported."

We installed the Intel Chipset drivers using .exe downloaded from Lenovo but how do I add the chipset driver to MDT "Out-of-Box Drivers"?

I've extracted the .exe which contains a setup.exe but if I extract that there are no .inf files.


MDT FAILURE(5627)run dism.exe

$
0
0

Hi all, can someone may able to provide a solution with this error.

Rolling out Windows 10 - Refresh with programs

$
0
0

Hi,

We are planning to refresh all our workstations with Windows 10. We keep the hardware but we want to save User profiles with USMT and reformat the PC then restore the user data.

I was wondering if anyone had successfully implemented a process that would first scan the computer for applications and then would update the deployment task sequence to add the extra programs before restoring the user data.

All i can think of right now is to make an inventory of apps and programs, then add these apps in MDT, then select them at deployment time. But i was wondering if anyone had managed to automate that.

Thanks

ZTI ERROR - Unhandled error returned by LTIApply: Object doesn't support this property or method (438)

$
0
0

I had a installation of MDT 2013 to Deploy Windows 8.1. I want to Deploy Windows 10 Pro.

I uninstall ADK and MDT 2013, I install ADK 10 and MDT 2013 Update 1.

I follow the archive case of windows 10 technical preview

I create the configuration of MDT, the boostrap.ini, the custommsettings.ini, I add an image of Windows 10, I add the drivers of my computer. I create the task sequence. I create My USB Key to start with the WinPE.

I start the installation on my computer, al is ready, the action create the partition, install the drivers and when it want to apply the OS the task fail and write ZTI ERROR - Unhandled error returned by LTIApply: Object doesn't support this property or method (438)

 

Can you help me please?

MDT and russian timezones

$
0
0

Hi colleagues,

I found strange issue with MDT 2013

I'm trying to deploy previosly captured image (KB2998527 has been installed in captured system)

When I'm select any time zone except Russia Time Zones (RTZ) in dropdown list, after deploying all works fine and I see correct TimeZone.

In case if I select any RTZ, after install Time Zone setup as -8.

I debug process and found, that in TIMEZONENAME variable exists "Russia TZ9 Standard time" (for example). and in tzutil I don't see such TZ Name.

As a workaround I txt file in image with links between correct TZ names and Russia TZX Standard Time and by tzutil I setup needed timezone after installation

But, could you please fix it next update for MDT 2013?

Thanks in advance

Windows 7 SP1 updates - Best way to update base install OS?

$
0
0

We are using MDT 2013 Update 2 and Win 7 SP1 Enterprise. Is there a way to download all of the current updates into the Win 7 install so when building new images from the base OS we are not pulling down 200+ updates?

Thanks

Chris

Viewing all 11297 articles
Browse latest View live


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