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

Custom bootstrap.ini in MDT - how to get it to boot over PXE? Imported into WDS, but that just does standard WDS boot.

September 27, 2019, 11:52 am
$
0
0

I have a standalone WDS server functioning over PXE. There is no AD environment. I can capture and deploy images with WDS, I just have to put in a name and password every time.

So I build a new share in MDT, and added the share credentials to its Bootstrap.ini:

KeyboardLocale=en-US

UserDomain=WinDeployServer

UserID=ShareUser

UserPassword=SharePassword

It's definitely in there, saved, and valid. Next I right click and "Update Deployment Share" Once that's done, I added the boot.wim from that MDT share into my WDS boot images. But when I PXE boot and select my MDT boot image, it still goes into WDS Windows setup. It asks me for the credentials, and once I provide them, it gives me a list of my regular WDS images to choose from. My MDT customization just isn't entering the picture at any point.

↧
Search

Unable to View Windows PE Tab Under Deployment Share Properties

September 27, 2019, 12:09 pm
$
0
0

Issue: I can't view the 'Windows PE' tab under my deployment share's properties. Instead I get an error message and the Deployment Workbench crashes completely.

Error: "MMC has detected and error in the snap-in and will unload it"

So far I've got a fresh install of Windows Server 2012 R2 ver. 6.3, the latest Windows ADK, and the latest MDT. I have imported Windows 10 Enterprise x64 into my OS's and I have built a mostly default Task Sequence for it. Otherwise this is a brand spanking new VM.

I wasn't allowed to included a screenshot of the error I get every time I attempt to view the Windows PE tab under the deployment share properties. I've uninstalled and re-installed the MDT and Windows ADK at least three times at this point. I've re-downloaded the source ISO for my image from VLSC twice now to be sure those files aren't somehow corrupted, again to no avail. 

I'm somewhat new to SCCM, MDT, and the Windows ADK. So I apologize if this is a simple fix.

Any and all help is greatly appreciated.

↧
↧

New MDT build - capture fails

September 27, 2019, 9:48 am
$
0
0

I created a reference build TS.xml that worked fine from my default MDT install.  For a new environment (new domain, new MDT, new everything), I  create a TS and then copy that original TS.xml into the control\ts\ts.xml of this new deployment. (I edit the OS location entry and everything looks fine)

It lays the OS down fine, does all the steps fine, starts executing capture WIM step fine (i see it create the WIM file in the captures folder and the size starts to grow).  Eventually it crashes with the following errors.   I need to be able to automate the installation and configuration of MDT for multiple domain builds and this is the only piece that is eluding me.   

From BDD: you see it starts fine then acts like it drops connection...?


↧

to disable admin password while running windows deployment tool kit

September 29, 2019, 9:29 am
$
0
0
i am using wds for installing os (win 10).when i running the wds in my client side,it is asking admin password and domain. i want to disable those things. how can i do that
↧

Static IP does not get saved on Deployment Toolkit during boot

September 30, 2019, 6:44 am
$
0
0

When I boot from USB to configure my Notebook Lenovo P52, I cannot specify the static IP network settings to be used. Every time I enter the numbers, it does not get saved and go back with tick mark "Enable DHCP".

Would appreciate feedback.

↧
↧

Server 2008 R2 SP1 Cant boot after apply OS completes (0x000000d)

September 30, 2019, 10:29 am
$
0
0

Using latest versions of MDT and ADK. I have created images for Server 2012 R2 and they work great. Tried capturing and deploying Server 2008 R2 SP1 and it will not successfully install. The capture works great with MDT. Get 0 errors. When i deploy the OS, it will completely apply the OS to the HDD, but then after it reboots it will just go to a Windows Boot Manager error with status: 0xc000000d. I have tried a combination of older versions of MDT as well as ADK versions. Still get the same error. I cant figure this one out. Happens for both UEFI and non UEFI. VM and physical. I even tried using the vanilla WIM from Microsoft volume license center and it gets the same error after deploying from MDT. Any ideas? 

↧

PXE Boot; TFTPTimeout; Error EventID 4101; Windows Failed to Start. A Recent Hardware of Software change...0xc0000001

September 30, 2019, 1:01 pm
$
0
0

I am having the hardest time with this error.  

My environment is all Server 2016 (Vmware 6.7)

MDT 8456

ADK and WinPE - 17763.1 (1903)

Regardless of what option i go with. EFI, BIOS, x86,x64 (Nic VMXnet, e1000, e1000e). WDS Set TFTP Max size to 0,512,1024,2048 up to max, or disabling Variable Window Extension I cannot get the TFTP downnload to complete.  DHCP hands out an IP, PXE response is there, it gets the boot file and starts the download of the WIM but almost always fails.  I can throw out 30 VM's and maybe 2 or 3 will get all the way to the WINPE environment. Doesnt *seem to present the issue in a physical workstation (But I cant roll the quantity like i can in a virtual environment to test).  All the rest will fail with the error I have in the Title.

WDS server shows the Error code 1460

Followed all the links and NOTHING is helping me.  

Troubleshooting1 

Troubleshooting2  

Alot of people talking about the March Update from this year causing this, but I'm on CU for the month so unless it was re-introduced I'm not sure what the cause is.  This environment has been working for over a year.  

I've cleared my entire DHCP reservations so there are no duplicates or anything of that nature.

I've tried completely removing WDS and the share and then re-installing/configuring and regenerating Boot files.

No Dice.



↧

MDT and multiple languages

September 30, 2019, 5:34 pm
$
0
0

Hi All


I've been researching and trying to get this to work for a while now, and would like to see if someone has a definitive answer.

I'm deploying Windows 10 Pro v1903 at a company, who block access to the Windows Store. The systems need to have multiple languages installed as these machines will be used in a variety of remote locations and the users may want to use their native language rather than EN_US. I have been given the multi language ISO from the VLSC and have imported the required languages into MDT as packages. I have created a selection profile and added this to a part of the task sequence to install updates offline.


I have MDT setup and deploying the image perfectly, it just doesnt seem to install the additional languages at all. I cannot see any errors in the logs.

Does anyone have any suggestions on where I can look next or how better to accomplish this? Reminder, the Windows Store is not an option I can make use of and these need to be installed for all users from build

Thanks in advance

↧
Search

Allowing MDT to create computer names in AD.

October 1, 2019, 7:46 am
$
0
0

Currently, we manually pre-create computer names in AD prior to cloning. As long as that computer name is in the appropriate OU then MDT will join the pc to our domain and then create a Bitlocker key as well. Of course, we check pc name availability before creating a name to avoid duplication.

If I skip pre-creating a pc name in AD and allow MDT to create it and join to the domain with that name, is it a requirement to check availability of that name still, to avoid duplicate names?

How does MDT handle a duplicate name issue in AD, or is it just that you must check ahead of time before typing a pc name into the MDT Wizard? I'd just like to cut out the manual addition to AD if I can.

↧
↧

Windows 7 pro to windows 10 education Upgrade

October 2, 2019, 12:28 am
$
0
0

Hello, 

Can i use an upgrade client task sequence in MDT to upgrade a windows 7 professional client to a windows 10 education ?

The windows 7 pro use a MAK Licence key and the windows 10 use a KMS activation.

thank you.

↧

Help, My Capture Image Task Sequence Keeps Failing to Sysprep

September 23, 2019, 7:13 am
$
0
0

I am using MDT to capture an image from a Windows 10 version 1903 Hyper-V vm and once I run litetouch.vbs from within the VM and it reboots, it fails with the errors in the attached screenshot ("Failed to run the action: Execute Sysprep").  I have tried creating a fresh VM and running the task sequence again but it still fails with the same error.  I have also tried creating a new capture image task sequence and it still fails.  I am running MDT version 6.3.8456 and I have updated my deployment share

Deployment failure: ZTI ERROR - Unhandled error returned by LTISysprepAny help or advice would be appreciated.

Johnnie Davis, Technology Specialist

↧

Stuck at MDT splash screen after reboot after sysprep trying to capture Win 10 reference image

October 2, 2019, 8:18 am
$
0
0

Hello all,

I've been using my deployment server and MDT deployment share for years to capture and deploy Win 7 and even did one image of Win 10 1703 (I believe, I can't remember exactly the version it was over a year ago at this point).

Now I am trying to update my deployment process to include Win 10 1903. I upgraded the ADK to the latest version, installed the latest WinPe add-on, upgraded MDT to 8456, upgraded the deployment share, regenerated the boot files, and replaced the boot wims on my WDS with the latest images.

I have a Standard Client Task Sequence that installs Win 10 1903 to a VM, runs Windows updates, and installs Office before running sysprep to capture a reference image. Everything works fine up until a certain point. Sysprep runs, the machine reboots, and WinPE loads but it stays stuck at the Microsoft Solutions Accelerator splash screen. I can't even press F8 to bring up a command prompt.

If I reboot the machine from the stuck splash screen and choose to PXE boot instead, I can log in and see my task sequences. If I choose the task sequence, it picks up where it left off and starts capturing the image.

Has anyone seen this issue before and how can I fix it? Thanks!

↧

Upgrade from Windows 7 to Windows 10

October 2, 2019, 10:51 pm
$
0
0

Hi, i'm not new to MDT but i can't figure it out how to make TS which allows me to do following steps in this order:

1. Backup User state to network share (it's working already)

2. Wipe computer hard disk, create new partitions(also resize) and deploy clean Windows 10 (This is working also)

3. Restore User state from network location (This also working)

Step 1 is separate task sequence and step 2,3 is separated TS. 

Can i run all these steps in single TS? If yes, how?

↧
↧

Office Customization Tool missing from MDT

October 4, 2019, 9:44 am
$
0
0

I recently downloaded Office 2019 and noticed the change to xml deployment file. I have the file setup for a standard install, but with Office 2016 I use to have the customization tab on the application window where I could change granular options for all Office apps. I don't see the tab for Office 2019. I'm guessing I need to add these changes to the xml file instead? All I want is to disable the Junk Email folder. 

↧

Having trouble modifying Wizard pane.

October 4, 2019, 11:24 am
$
0
0

I can edit my DeployWiz_ComputerName.xml file to only show

Computer Name, Join a domain and Join a workgroup.  I removed Domain to join, Org Unit, Username, password, Domain.

I use MDT Wizard Studio and when I preview editing the xml, it looks fine.
I need to modify the VSB as well, but when I try, I get several VBS errors. I'm not sure what to edit/remove so that the VBS works to reflect what I see in the preview, after editing the XML.

All I need to show is: Computer Name, Join a domain (nothing under it) and Join to workgroup (and workgroup name box).

↧
Search

Deploying Windows 10x64 with Office 2019x64

October 6, 2019, 2:08 pm
$
0
0

I am trying to deploy Windows 10x64 with Office 2019x64 with MDT then import it into SCCM. I have it working with Office 2013x86 and Office 2016x86 but when I try to deploy Office 2019x64 I get "

Windows Could Not parse or process unattend answer file for pass [specialize]

Thanks,

Rick.

↧

Language to Install Missing

October 7, 2019, 4:18 am
$
0
0

Hello,

So i was playing around for the first time with MDT and in the first time i created the MEDIA, i install the ISO via usb pen and i boot a old PC... When i was in the deployment Toolkit i got in a part where i need to put "language to install" and all that appears its a blank space.

I searched online and i saw i need to install the language pack via MDT Packages, but i cant find this languages packages anywhere. I m bit lost as i m still a noob at windows image deployment :) .

Can someone help me out?

Thanks!!


↧
↧

Network Driver Not Installing

October 8, 2019, 12:30 am
$
0
0

Good Morning,

Ive been banging my head against this issue for the last few days and I'm totally stuck!  Im trying to build a HP EliteDesk machine and it fails everytime with failure to get DHCP lease and this is generated because the NIC isn't installing.

Ive installed the latest drivers from the HP Driver Matrix into MDT.  Ive also read the BDD logs and I see that the task sequence is selecting DriverGroup001 and selecting the right folder.  I also see the copying of the drivers fine.  I've also copied all the drivers Ive imported into the MDT driver folder and if I install them manually onto the machine it they work fine.

Any ideas?

BDD log - https://controlc.com/70f2cea0

Thanks,

Brad


↧

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!

↧

Can MDT check existing names in AD prior to domain joining?

October 8, 2019, 12:05 pm
$
0
0

I've just started allowing MDT to join computer names to AD. Prior to this, we have always manually added the name after verifying it doesn't already exist. If you try, AD will bark and say it is already there.

I manually created a computer name on one OU, then had MDT create the same computer name in a different OU.
What I saw was...no computer added in the new OU but rather the pc assumed it was the one in the other OU.

Rather than have someone forget to check names and we are bumping devices off the domain, how can MDT check if a name exists in any OU we have? I don't have a DB set up. Just adding computers manually or, for my testing purposes, having MDT create a name I know isn't there. It works, provided you check. So, if there is a way, I'd be interested in giving it a go.

↧
Viewing all 11297 articles
Browse latest View live
Search