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

Welcome Wizard Failed or Cancelled

$
0
0

Hello All,

I have successfully tested MDT image of Windows 2012 R2 on VMware and Hyper-V. This image is built on MDT server which is on Windows 2012 with ADK 8.1 and MDT is 2013.

When I run this image on HP Server BL460c G7 - I receive below error. I see the installation of Os is completed properly followed by POSTINSTALL sequence...this error is received during reboot in POSTINSTALL sequence.

I see BDD log file on C:\windows\temp\deploymentlogs\bdd.log but since I am not that expert on MDT, I am not able to find culprit while checking log file....also, not sure if I can take BDD log file from ILO console to my PC so that I can upload it here for reference..

please, anyone has any idea?


DISM Error:5 error when building boot ISO with WADK 8 and MDT 2012 sp1

$
0
0

Hi

Environment: Windows server 2008 R2(VM), 2GB RAM, WADK 8, MDT 2012 SP1

When I try to build a boot ISO using either MDT or ImageX, I receive an error when DISM is used to add packages.

Processing 1 of 1 - Adding package WinPE-HTA-Package~31bf3856ad364e35~x86~~6.2.9200.16384
An error occurred - WinPE-HTA-Package Error: 0x80070005

Error: 5

Access is denied.

This repeats for all WINPE packages being added by DISM. 

I have rebuilt the server and reinstalled but the same affect. I have tried running it as admin, editing rights and making the name of the packages lower case but cannot seem to get anywhere. Any help would be great.

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

$
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,

Windows ADK and MDT 2013 components

$
0
0

Hi

I noticed thatWindowsADKisinstalledin its32 bit versioneven though I haveWindows8.1Update64 bit.It is correct?

Then, IinstalledMDT2013 64 bit.

Now,where can I finda detailed descriptionabout the componentsof this MDT?

Having tocustomize, deployandcreate someDVDsofWindows8.1Update32/64 bit,what components should Idownload?

Thanks

Bye


Balubeto

MDT 2013 - Linked Deployment Share

$
0
0
I have MDT with WDS setup in the corporate HQ's working great.  Litetouch config either PXE booting or USB boot to the MDT share.  Now I want to image at the remote branch offices... was thinking of creating a standalone USB and shipping it to our branch offices.. I dont want to image over the WAN.  Is there documentation on creating a linked deployment?  Do I just need to install WDS (for PXE) at the remote sites locally and create and replicate a linked deployment share?

Task Sequence Editor

$
0
0

I am at the client where i have to use MDT only as a delivery tool for the OS.

Just the fact i cant open a TS in a full window drives me a bit crazy :) got used to SCCM/MDT

Just wondering if there are any other editors for the "tx.xml" task sequence with the GUI like MDT?

Thanks for the help.

Feature-Request: Ignore or disable updates that are flagged "allowedOffline=false"

$
0
0

Updates (packages in MDT terms) that contain 'allowedOffline="false"' in their update.mum file will make the OS installation stop in the offline servicing phase (KB2533552 is an example). Wouldn't it be reasonable to check this flag when importing the updates and disable the package in MDT or even refuse to import? Would make my workflow "grab all the updates *.cab detected by Windows Update from the SoftwareDistribution\Download folder and import them in MDT" a lot easier.

MDT and Computer Name

$
0
0

I'm looking at trying to keep the computer name when I reimage using WDS 2012.  We name our computers a certain way and would like to keep from having to retype the name over and over when we reimage.  Hopefully someone can help me.  I need this to work on existing computers that are being reimaged.  Our naming schema goes XXX-0YYYYY-ARRR.  XXX represents the second quadrant of the ip address it is given by DHCP, 0YYYYY represents and interna fix asset numbering system, and ARRR refers to the room location of the computer.

I know with new computer, I will have to give them a name so I would like to have the field editable when PXE booted into WinPE but just populated on the existing machine name if it had one.


MDT Network Card driver issue PCI\VEN_8086&DEV_153ASUBSYS_06251028&REV_04

$
0
0

Hi all, I have a number of new machines that need to be re imaged so its suits the requirements of the organization. They are brand new and have set the pc to boot from network port. The computers in question are Dell OptiPlex 9030 AIO's quad core and 8 GB of RAM, 64 bit. On my server I have x86 and x64 images, they all work fine on the many different machines I have.

I have been trying to find a solution for a few days now and can’t seem to find it, either I am looking in the wrong place or doing something wrong.

 

Now below is what I have done so far.

I have downloaded the driver from dells website for the Intel device for x64 bit, I then added it the out of box drivers and deployed it, and it did not work.

I then downloaded the CAB files for the drivers for the whole machines, same error appears.

I know it’s asking for the network driver but the driver is in MDT.

I checked the INF file for the x64bit for the network driver and only the PCI\VEN_8086&DEV_153ASUBSYS_06251028 part is there but its missing the&REV_04.

Any ideas what I am doing wrong or not doing?

Any help will be greatly appreciated.

 

Kind regards

Samee

MDT Network Card driver issue PCI\VEN_8086&DEV_153ASUBSYS_06251028&REV_04

$
0
0

Hi thanks for the reply.

When booting the machine I press F12 to enter the boot menu

I select Onboard NIC It then asks 'Press F12 for network boot service' which I did

It then leads me to the 'windows boot manager' which I can select an image from my server.

After I have selected the x64 image it says 'windows is loading files'.

After which it displays the windows 'welcome windows deployment' where I can select the 'Run deployment' OR 'exit to command prompt' and 'select location'.

If I select Location as UK and click run this is where I get the error

PCI\VEN_8086&DEV_153ASUBSYS_06251028&REV_04

If I just click 'exit to command prompt' and try 'IPCONFIG' no address or details load.

On another completely different machine where reimaging works if I do ipconfig I get an IP etc.

You have also asked for log files where can I get these from as I can’t seem to find a location for it.

 

I have already downloaded and extracted the CAB files from dells website and imported them into out of box drivers. I also have updated the deployment share. And still this issue occurs.

Thanks for your reply

Kind regards

Samee

 


MDT 2010 Mass Storage Driver Problem

$
0
0

Hi,

I am having problems trying to deploy XP to a new HP workstation (a stand-alone unit that will be controlling hardware that is not compatible with anything more recent than XP). Using MDT 2010 I have added the XP drivers for the correct model to Out-Of-The-Box Drivers, updated the deployment share and can boot the LitetouchPE via PXE but when I select the 32bit XP deployment it fails stating that no hard drive is detected due to missing mass storage drivers. After attempting to update the LitetouchPE with the mass storage driver using DISM I get the same result. I have gone through every thread I can find relating to this and can't find anything that suggests a fix other than to ensure the drivers are updated using the method above. Is there something I'm missing?

USMT - IE Favorites Migration

$
0
0
We are seeing an issue where by it seems that everything but IE Favorites are not being migrated when doing a pc refresh scenario. This is using MDT 2013 Win 7 Ent / Pro. If someone has any pointers, its much appreciated.

MDT 2012 - deploying windows image silently

$
0
0
Hi, I created win7 image with integrated updates (I used rt seven lite for this purpose) and then imported that into OS folder of new deployment share in mdt 2012 update 1. After creating standard task sequence I edited bootstrap.ini and customsettings.ini files in order to perform unattended installation of windows 7. Having done that I created and updated media, mounted .iso file and used it to install new virtual machine but installation was not silent - I got all these screens (welcome, choose task sequence and so on). I opened media .iso file and noticed that on it there were none of lines I added to .ini files so installation could not be silent. How did these "switches" disappear while creating media .iso file? Earlier I tested these .ini files when OS installation was over network but now I want to install OS completely silent from .iso dvd file.

MDT 2013 - Image Capture fails to upload image

$
0
0

I am attempting to capture and upload an image. The drivers for the hardware imported into MDT. Downloading images works fine.

I run the litetouch script from within the OS but when the system reboots to create the WIM and upload to the server the NIC drivers are not found. Why?

I should also add that this was working. I am unaware of any changes made other than driver imports for new models.

Thanks!


JJ


Failure trying to deploy Windows Server 2012

$
0
0

I'm trying to test deploying Windows Server 2012. I am running Deployment Toolkit 2012 Update 1 and installed the Windows Assessment and Deployment Kit. The server is running Windows Server 2012.

I added the OS as a "Full set of source files". Then created a new Standard Task Sequence. I boot my VM into LiteTouch, choose my task sequence and no other applications. Once I get to the end of the wizard, instead of installing the Deployment Summary comes up with the following error:

Litetouch deployment failed, Return Code = -2147467259 0x80004005

I tried migrating my Deployment Toolkit to a completely new server and a fresh install, but it is still not working. It did not work on Server 2008 R2 with MDT 2012 Update 1 either.

Thanks!


Start Screen Layout with Windows 8.1

$
0
0

Hi Team,

Just wondering if below Technet article for capture and deploy start screen layout applies to windows 8.1\windows 8.1 update 1?

http://technet.microsoft.com/library/jj134269#BKMK_AppFolder

As far as i understand these 3 methods are good with windows 8.0 but with Windows 8.1 , capture layout with 

Export-StartLayout and using GP is applicable. Any pointers will be appreciated. 

Regards,

Surface Pro 3 Pen and MDT

$
0
0
After reiimaging the Surface Pro 3 with Enterprise using MDT we can't seem to get the top button on the pen to work. I used the firmware/driver pack that MS provided and made sure all windows updates were installed. Has anyone else had this issue?

MDT 2013 Automatically naming computers from MDT DB Location Details variables and sequence numbers.

$
0
0

Hi All, 

I am having some serious issues with trying to get the auto naming working. I am trying to pre-populate the computer name during a task sequence however the computer name will be built utilising variables added to the mdt database.


Naming Convention

The current naming convention for client devices is WXXYYYZZZZ as the client is in multiple countries and offices.  This is as below

W = Hardware type - S = Server , V = VM , L = Laptop , D= Desktop etc

XX = Country code - AU = Australia , US = United states etc

YYY = Site Office - Syd = Sydney , AUC = Auckland etc

ZZZZ  = numbering of device - 0001, 0020 etc

So a fully fomulated name will be something like LAUSYD009


MDT Database modifications

I have extended the MDT DB schema to include custom variables that can be entered in the Details tab. These variables are as below

LocationVarName - Updated in the locations part of the db and populated with the county code variables explained above in the naming convention

MakeAndModelVarName - Updated in the make and models part of the db and populated with the different hardware types expected

This was discovered and tweaked using the following link.

http://blogs.technet.com/b/deploymentguys/archive/2011/08/05/dynamic-computer-naming-in-zti-deployments-using-mdt-and-configmgr.aspx

By tweaking things in the above link i can effectively get the ZTIGather.log to create the OSD computername correctly according to its Make and model and Location Variables , i.e. LAUSYD  or DNZAUC. I can also run a build of a machine and can create unique computer names by also adding the  the Serialnumber variable. Personally that is the way id prefer to name the new devices  however the business is adamant that it wants to stick with the sequence numbering it is currently using (3k computers already out there in the environment with that naming convention). So based on above i believe i have the prefix part of the computer name down packed.


The second part is the sequencing of the devices. I had a look at another link as below which advises how to auto name a computer with a defined prefix and a sequence number. This link will check the macaddress of the computer and if the name matches the mac address it will re-issue the same name. If there is no link to the mac address it will generate a new name with a incremented sequence number.

http://www.deploymentresearch.com/Research/tabid/62/EntryId/103/Generate-computer-names-in-MDT-2012-2013-based-on-prefix-and-a-sequence-number.aspx

I have tweaked the above to use the serialnumber instead of the mac address as this is imported into AD currently. Again i have got this working and can effectively name comptuers PC-0001 etc and match against the MDT database for known computers. As Prepwork i have run a couple powershell scripts and audited the AD and imported all known computers and associated serial numbers into the MDT DB already. So my MDT DB knows all devices has currently a range of 0001 to 0159 populated under the computer names tab in the DB.


What i am trying to do is get these two solutions working in conjunction.  I am trying to get the initial part of the name (LAUSYD) created from the first step and then assign a sequence number to it and check the mdt db for a connection to serial number.  This is where i am stuck. Can anyone advise how i can combine these two solutions or if there is a better way to resolve this dilemma i am currently facing.

Thanks in advance for any advice






[MDT] Sysprep and capture, and OOBE

$
0
0

Hi my friends, I'm experiencing a little issue.

I want to deploy custom images with OOBE. In other terms, when a client boot his computer for the first time, I want Welcome window display, and ask for account name, etc.

But now, when I boot client computer, it auto-signs in to an administrator session and finish MDT deployment. Please help me understand.  

Let's me explain how i proceed. First, I installed with an iso file my Windows, and when I get welcome windows, I enter in audit mode to add some programs etc. Then I launched my \\ServerMDT\DeploymentShare$\Scripts\LiteTouch.vbs to start Sysprep.

It reboots, and I am able to boot PXE and start capturing. Works like a charm. Now I upload my captured image in another DeploymentShare using a Standard Client Task Sequence to deploy my captured image. I updated my new DeploymentShare, etc.

The deployment looks to work great. But when it reboots, it signs in without asking for password or else, and finalize deployment. My programs are here, it is OK. But I haven't my OOBE.

What I misunderstood ? Help me guys...



Install Mdt 2012 Update 1 on Windows Server 2012 - Powershell not installed

$
0
0

Hello geeks!

Today I tried to install Mdt 2012 Update 1 on a server with OS Windows Server 2012 Standard. I installed the mdt, but when I tried to create a new Deployment Share, I got an error occur. "Powershell is required for interacting with deployment shares. Please install Powershell." And what i'm know, should windows server 2012 comes with powershell 3.0 installed.

Has someone solve this problem ?

//

Emil

Viewing all 11297 articles
Browse latest View live




Latest Images