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

Need help imaging one SSD and not a storage drive.

April 1, 2019, 4:38 pm
$
0
0

I was given a pc today and I dropped an image on it. Everything to me looked fine as the C: was a whopping 984G.

What I later found out was that the pc also has a 512G solid state drive and that is where they want the OS to be (C:).

Every pc that runs through MDT gets one whole drive and the OS resides there, C:. I have no idea how to have MDT drop my image onto the smaller drive and leave the large one as storage (D: maybe?).

I'm thinking it must be in the partition section of MDT, yet then I'd have to have that step apply only to the Precision 7530 model.
How do I go about either configuring the BIOS so that C: and the OS is the 512G drive and the other is a storage drive? Would I also have to hard-code that drive as a letter?
I've never had this situation before and they're in a hurry for it, as usual.

↧
Search

Default Gateway Settings Specified In customsettings.ini Only Work Sporadically

April 1, 2019, 5:24 pm
$
0
0

I have been trying to specify the OU the machine is joined to the domain in based on the location the workstation is deployed to.

This works sometimes and sometimes it just uses Default settings even when imaging from Site 2.


[Settings]
Priority=DefaultGateway,Model,ByIsUEFI,Default
[DefaultGateway]
192.168.0.1=Site1
10.0.100.1=Site2
[Site1]
MachineObjectOU=OU=Site1,OU=NewDeployment,OU=Workstations,DC=Domain,DC=COM
[Site2]
MachineObjectOU=OU=Site2,OU=NewDeployment,OU=Workstations,DC=Domain,DC=COM

[Default]

JoinDomain=domain.com
MachineObjectOU=OU=Site1,OU=NewDeployment,OU=Workstations,DC=Domain,DC=COM

===========================================================================

How can I make this reliable?  Is there another setting I can use instead of DefaultGateway that works better for setting OU based on deployment site?

Sometimes Site2 works as expected and the machine is joined to the correct OU.  So, I know it CAN work.

I read something from an old post from many years ago (2009) about adding a delay to make the deployment wait for the network to be detected so default gateway settings are applied, but they say that issue was fixed with MDT 2010.

https://blogs.technet.microsoft.com/deploymentguys/2009/09/23/making-winpe-wait-for-network-in-lti-deployments/



↧
↧

Windows server 2012R2 installed ADK and MDT, Windows7 system batch upgrade Windows10, office2010 upgrade office2016

April 2, 2019, 1:29 am
$
0
0

hello

Windows server 2012R2 installed ADK and MDT, Windows7 system batch upgrade Windows10, office2010 upgrade office2016

When the upgrade is complete, you can still see office2010 residues on Windows10, but you can also see office2016 and 0ffice2016 is available, that is, you can see office2010 residues in the add and remove options

Excuse me, is there any problem in the setting of MDT deployment software?

thank ！

↧

Hostname not the same as OSDComputerName on imaged Surface Products

March 28, 2019, 11:36 am
$
0
0

Hello all. My customsettings.ini is setup to pull the Asset Tag from the BIOS and then add "D" for Desktop chassis (1234D) and "L" for Laptop chassis (5678L) to create a computer's hostname. This has worked successfully for many months for all desktops (IsDesktop=True), all laptops (IsLaptop=True) and for all Surface products we use (IsLaptop=True). Since I moved the DeploymentShare to a new location over the weekend (and generated a new boot WIM), the naming scheme no longer works for any Surface product, only. The desktops and laptops are still named correctly like before. The Surface products pull the correct asset tag number and IsLaptop still = True, but MDT does not add the "L" to its hostname. I've dumped the variables that LTI is using at the end of a load and see that the OSDComputerName is still set correctly (1234L), but the hostname ends up being 1234. Did I miss regenerating something in the move or somehow tweaked a setting? I don't understand why laptops are named correctly but Surface products are not when they share the same chassis type. Thanks in advance for any ideas.

Anthony

↧

"Please fix all errors before continuing" error - trying to import win10 1809 OS

March 28, 2019, 9:53 am
$
0
0
We are running MDT 6.3.8456.1000 on Windows Server 2008 R2 Standard and Windows 10 ADK 10.1.17763.1 and I'm trying to simply import a Windows 10 1809 OS that I downloaded via the Media Creation Tool. I've tried mounting the .iso file as a drive as well as extracting the files to a folder, rebooting the server, updating the deployment share. I believe I have the full set of source files but I've also read that MDT will not import this way and that you need to download via the VLSC. Can someone confirm this, please? Thanks. --Scott
↧
↧

ztigather script desktop =false on dell optiplex 760 AIO

April 3, 2019, 3:19 am
$
0
0

hello, When the ztigather script runs on the new Dell optiplex 760 AIO it is = to flase.

although i would class this machine as a desktop machine.

I have a rule that install mandoratory applications based on whther the hardware is a desktop or not, anyway know why or how to alter this script so that this hardware = true for isDesktop?

Thanks 

↧

HP 800 G3 MDT deployment fails with UEFI

April 3, 2019, 5:04 am
$
0
0

Hi,

I am facing strange issues with this model deploying Windows 10 x64 1809 UEFI. I downloaded WinPE 10 drivers v1.6 from HP, and they are injected to LiteTouchPE_x64.wim using Out-of-the-Box drivers. This machine has two drives, first is 120GB SSD and the other is 1TB HDD. Also, BIOS deployment is not working, at least the image is installed and the machine reboots, but into a page where it says a required device isn't found or can not be accessed.

MDT 6.3.8456.1000, ADK10..

UEFI smsts.log

thanks

↧

MDT 2013, WDS, Server 2012 R2 multicasting not working rc = -1073740940

July 28, 2014, 7:39 am
$
0
0

Hi,

I have been reading all over the internet and not able to find an issue that we are having.  We have setup MDT 2013 and WDS on a Server 2012 R2 server.  Unicast has been working fine for us and we have the PXE boot working great too.  We have recently tried setting up Multicast.  Every time we try and deploy an image we receive the following error when the client tries to run the multicast.  I have pulled this error from the ltiapply.log on the client.  The error is: Multicast transfer could not be completed, rc = -1073740940, falling back to using \\mdtserver\deploymentshare\operating systems.  We have also made sure we have IGMP enabled on all our switching and VLan's.  We have tested with mcast.exe and Wireshark and the packets are hitting the machine for multicast but we always seem to get this error.  Any help would be great.

Thanks,

↧
Search

MDT 8456/ADK 1809 - deployment of windows server 2019 StandardCore - OOBE System skipped ??

April 4, 2019, 5:35 am
$
0
0

I am trying to deploy windows server 2019 Core - which works - but there is an odd thing I am trying to sort out:

by using WISM - to modify Unattend.xml - we run a powershell script during phase 7 oobe system.
by default (I presume built in by MDT) it contains 1 SynchronousCommand (wscript.exe %SystemDrive%\LTIBootstrap.vbs) under FirstLogonCommand.
we always add another script after this command - to run a powershell script. this script works find for the desktop experience install - but during the core install, this powershell script is not executed.

I put in a pause in the MDT Task sequence before finishing the deployment, and manually executed the powershell script - and then it ran fine, but I believe the OOBE System phase - firstLogonCommand is executed right after booting up/logging in as administrator

I am trying to find out if the OOBE phase 7 is skipped for the Core install, but that does not seem to be the case. but I am puzzled why it does not seem to be executed at all.
commandline = PowerShell.exe -ExecutionPolicy Bypass %ProgramData%\custom\custom.ps1

(the script is available at the location)

↧
↧

MDT 2012 - Failed to Run Action: Install Operating System Access is Denied (Error: 0000005; Source: Windows)

July 3, 2013, 11:53 am
$
0
0

Unable to deploy any image with WIM file. Vanilla or Custom Image gives the following error:

ZTI Error – Unhandled error returned by LTIApply: invalid procedure call or argument (5)

Litetouch deployment failed, Return code = -2147467259 0x80004005

Failed to run action: Install Operating System.

Access is denied (Error: 00000005; Source: Windows)

Tried Giving Everyone Full rights to the deployment share

Rebooted Server

Updated Deployment Share

Any ideas would be great!

Thanks

Rick

Richard Ray

↧

WinPE\Bitlocker issue after upgrading to MDT 8456 and ADK 1809

March 30, 2019, 11:05 am
$
0
0

Sit back and relax. This post will be lengthy. I have been racking my brain on this for over a week, and I desperately need a hero. Let me start with the scenario. We use a combination of MDT\WDS to deploy our images (we also have an SCCM environment that is not integrated with MDT). We are in the middle of using MDT's refresh capability to replace our Windows 7 bitlockered OS' with Windows 10. The refresh process goes like this:

  1. Litetouch.vbs is executed from within a running Windows 7 OS that has Bitlocker enabled.
  2. Task sequence is executed, and performs the following key steps: (a) backs up user profiles via USMT, (b) disables BDE protectors, (c) applies Windows PE, (d) reboots to MDT to continue the task sequence
  3. Once the PC has booted into the MDT environment, the task sequence continues on like this (key elements only): (a) applies the WIM, (b) converts the bios to UEFI via Dell CCTK, (c) converts the MBR to GPT via the Microsoft MBR2GPT utility, (d) reboots to load Windows 10 for the first time.

This last reboot is where the issue lies. As soon as the task sequence hits that 'Restart' task, it blue screens with an 'fvevol.sys' error, and a 'DRIVER IRQL NOT LESS OR EQUAL' error, and it just sits there until the power is cycled. Now once you cycle the power, the task sequence continues without error, but we kick these off remotely. So our only option right now is to either have the end user cycle the power, or be physically present at the workstation.

Now...with the previous iteration of WinPE, we were still getting this blue, but it would at least reboot automatically, and continue on with the task sequence. I have scoured the internet, and cannot find anything related to this. I find it hard to believe that no one is encountering this, as it happens on EVERY machine of ours (not a random thing). Here is what I have tried so far:

  1. Removed the built-in 'Disable BDE protectors' task in MDT, and replaced it with a script of my own (no change).
  2. Mounted the 'LiteTouchPE_x64.wim' and edited the registry entry "AutoReboot" value from 0 to 1. This change causes the PC to shutdown after the bluescreen instead of rebooting.
  3. Mounted the 'LiteTouchPE_x64.wim' and edited the registry so that it does not load fvevol.sys (a bitlocker driver). This causes the PC to boot straight to the MDT menu (task sequence does not continue), as it can no longer read the scripts from the drive due to encryption. I thought this was rather strange since the bde protectors get disabled before it reboots to WinPE. This tells me that WinPE is possibly re-enabling bitlocker.

The only thing I have not tried is fully decrypting the drive. I suspect this would work, but I shouldn't have to do this. Also, this issue does not occur if we boot straight to MDT using a 'New Computer' deployment type scenario.

I would greatly appreciate any feedback on this! Thanks to all in advance!

↧

MININT and _SMSTaskSequence folders are creating in C:\ drive after deployment

April 8, 2019, 2:23 am
$
0
0

Hi All,

I m using MDT 8450 and ADK and WinPE add-on for 1809 OS.

I captured the image using MDT.

Imported the captured image into MDT.

Crated the TS. edited the Unattend file and added only OOBE under

Under OOBE I enabled EULA, Hide Online account, Protect PC 3 etc., my requirement is user has to choose region, keyboard, enter the Work or school account\Local account (if no network).

I modified the TS with above requirement and deploying the image. deployment went successful however if I go to C:\ drive, it is showing below folders and file created.

C:\_SMSTaskSequence (folder)

C:\MININT (folder)

C:\LTIBootstrap.vbs (file)

when I check the BDD.log it is showing message that.

If there is a drive letter defined, make sure we clear it now so we can *force* recalcutation.

Property OSDTargetDriveCache is now = DIRTY

LTI initiating task sequence-requested reboot.  this is the last line in BDD.log

TS not completing and not cleaning up the things.

if I use default TS unattend file (without modifying) folders are not creating and it is directly logging with local admin account which is not my requirement.

please update me about this issue. this is frustrating me for long time.

Thank you.

 

↧

MDT 8450 Windows 10 1803 Deployment Issues. Domain Join

May 7, 2018, 8:31 am
$
0
0

Hello All,

I am trying to deploy the new Windows 10 1803 image, however I am having a little trouble. I have MDT 8450 build (latest) & Windows 1803 ADK. Basically when I go to Deploy, everything seems to get work except domain join. It will finish deployment but not join my to my domain. It also seems to get stuck for awhile on the "Getting Ready" screen a lot longer than 1709 did. 1709 was working perfectly. Any advice or is anybody else having this issue?

↧
↧

MDT 8456 and ADK 1809 error 0xc000001

April 8, 2019, 11:13 am
$
0
0

Hello

I have upgraded to the new version of MDT 8456 and Windows ADK for Windows 10, version 1809. After doing the update I am not longer PXE boot I get error 0xc000001. I have addedBCP47Langs.dll and BCP47mrm.dll from a Windows 10 v1809 into winpe using the xtra Files feature and still no PXE. I have created an new Share and imported the Drivers into the share and still getting the PXE error. What am I missing? All the boot files and WDS fil have been regenerated after the update. I want as far as reinstalling WDS.

Thanks



↧

Installation Failing at Install Operating System 100%

April 8, 2019, 7:11 pm
$
0
0

I building MDT with WDS for our school image process and its keep failing at the stage where the its needs to restart.

I've tried image VM with the same MDT and it works.

But when I am trying with physical machines it's failing at the same stage.

tried recreating whole procces and still the same issue. used clean windows image and same happened. 


↧
Search

Step by Step Process to build MDT Standalone Media with Captured Image

April 8, 2019, 9:00 pm
$
0
0

Hello Guys,

Check this guide and provide me your valuable inputs.

Link

↧

CustomSettings not applying in MDT 8456

April 9, 2019, 4:08 am
$
0
0

My Custom Settings rule not appling in MDT 8456 & ADK 1809

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
OSInstall=Y
SkipCapture=YES
SkipAdminPassword=YES
SkipProductKey=YES
SkipLocaleSelection=YES
SkipTaskSequence=NO
SkipTimeZone=YES
SkipApplications=YES
SkipBitLocker=YES
UserDataLocation=AUTO
SkipComputerBackup=YES

↧
↧

MDT Transfer CSV to the database

April 9, 2019, 7:23 am
$
0
0

Hi I have install a WDS to a new server and I will transfer CSV files after I have Export from the old server.

How will I do to do that ? I have three files, like :-  

  • Computers
  • Roles
  • Make and Model

Please help :-)

---- S-O-K-O-B-A-N -----



↧

How can I get setupcomplete.cmd to run during windows 7 OEM > 10 upgrade?

April 9, 2019, 9:22 am
$
0
0

Hi,

We are trying to use MDT to upgrade our Dell OEM Windows 7 computers that came with W10 licenses to Windows 10. We have gotten the upgrade to install but none of the post-processing steps are running. The reg key is not being set that the post-processing group looks for. A search in the scripts folder indicates that setupcomplete.cmd script is what is supposed to set this registry. The logs say that setupcomplete.cmd is not run because an oem key is detected. I followed the steps in this page support.microsoft.com/en-us/help/4494015/task-sequence-does-not-continue-after-windows-setup-or-in-place-upgrad to set the OSDSetupAdditionalUpgradeOptions  variable to /pkey W269N-WFGWX-YVC9B-4J6C9-T83GX (w10 kms client key)

and also tried setting the kms client key in the unattend.xml file

But still the setupact log indicates that an oem version is detected

Not sure what else to try except just changing the conditions on the post-processing group. Any help is appreciated.


↧

"Please fix all errors before continuing" error - trying to import win10 1809 OS

March 28, 2019, 9:53 am
$
0
0
We are running MDT 6.3.8456.1000 on Windows Server 2008 R2 Standard and Windows 10 ADK 10.1.17763.1 and I'm trying to simply import a Windows 10 1809 OS that I downloaded via the Media Creation Tool. I've tried mounting the .iso file as a drive as well as extracting the files to a folder, rebooting the server, updating the deployment share. I believe I have the full set of source files but I've also read that MDT will not import this way and that you need to download via the VLSC. Can someone confirm this, please? Thanks. --Scott
↧
Viewing all 11297 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>