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

Down-arrows in the Start Menu

$
0
0

I'm working on creating a Windows 10 Edu 1607 image using MDT. After deploying the wim to a vm, the Start Menu of local Administrator, or any other user I login as, has down-arrows on many of the tiles like this:

If I click any of the tiles with the down-arrows it brings me here:

When I install using the DVD I don't end up with any tiles with down-arrows.  For what it's worth I have a contact at another organization who's also working on a Windows 10 Edu 1607 image using MDT and he has the same issue.

Can anyone explain this?


Running Windows Server dedup to disk that is holding MDT Deployment Share

$
0
0

Does anyone know can Windows Server (2016) dedup cause any problems to MDT deployment share? Especially the driverstore. 

Custom properties added to MDT database, values return blank in query. Why?

$
0
0

I am having issues with some custom properties that i have added to the MDT database for scripting Out Of Band management.

They have been successfully added to the database, the view has been refreshed and from the MDT management workbench i am also able to see the custom properties.



I have also successfully injected values from my prestaging script as can also be seen from the screenshot.

The issue is, when i try to fetch the values from the database, they return blank.

In my customsettings.ini i have also added the properties:

[Settings]
Priority=CSettings, CRoles, RSettings, TaskSequenceID, Default
Properties=OOBIPAddress, OOBSubnetmask, OOBGateway, OOBPassword

The script i am using to try to fetch the properties looks as follows

if($MDTIntegration -eq "YES"){    $OOBIPAddress = $tsenv.Value("OOBIPAddress")    $OOBSubnetmask = $tsenv.Value("OOBSubnetmask")    $OOBGateway = $tsenv.Value("OOBGateway")    Write-Output "$ScriptName - IP Address: $OOBIPAddress"    Write-Output "$ScriptName - Subnet Prefix Length: $OOBSubnetmask"    Write-Output "$ScriptName - Gateway: $OOBGateway"}


If i use the same script for some of the built-in properties, they return just fine and as expected:

if($MDTIntegration -eq "YES"){    $IPAddress = $tsenv.Value("OSDAdapter0IPAddressList")    $Subnetmask = $tsenv.Value("OSDAdapter0SubnetMask")    $Gateway = $tsenv.Value("OSDAdapter0Gateways")    Write-Output "$ScriptName - IP Address: $IPAddress"    Write-Output "$ScriptName - Subnet Prefix Length: $Subnetmask"    Write-Output "$ScriptName - Gateway: $Gateway"}


Both scripts are making use of the $tsenv = New-Object -COMObject Microsoft.SMS.TSEnvironment. So it has something to do with the properties in some way.

I am totally puzzled and have used so  many hours to find out why - on the edge of giving up.

Maybe it is something simple - i really hope you guys have an answer - 'cause i'm tearing out my hair!

Findings:

Although I have refreshed the view as suggested in many articles that describe adding custom values, i do not see the new values in the actual updated view. Here in stead is a long list of properties specified. But not those added. Could this have something to do with it?

MDT build 8443 breaking Sysprep and Capture

$
0
0

We recently updated one of our MDT servers to MDT build 8443 that was just released.  Everything had been working fine until we went to sysprep and capture via a standalone Capture Task Sequence.  Basically what is happening is whether we boot to the MDT Deployment Share or manually kick off the LiteTouch script to start the Deployment Wizard, after we select the standalone Sysprep and Capture task sequence in the wizard we are not getting the Capture Screen in the wizard where you select to sysprep and capture and specify the file name / location, etc.  It just skips right to the computer name / domain join screen. 

We have verified that SkipCapture=NO in our customsettings.ini and have even created new sysprep and capture task sequences but nothing seems to work.    

Just wondering if anyone else has ran into this since updating to MDT build 8443 and has found a fix for it yet.

Thanks.

MDT 2012 - Error while importing driver CABs

$
0
0

Hello community,

I have a huge problem with MDT2012 since yesterday: I cleaned my driver repository a little and now I cannot import driver CAB´s anymore, every time it ends with this error:

System.Management.Automation.CmdletInvocationException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index ---> System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
   at System.ThrowHelper.ThrowArgumentOutOfRangeException()
   at System.Collections.Generic.List`1.get_Item(Int32 index)
   at Microsoft.BDD.PSSnapIn.Verifier.AddDriver(String theInfFile)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ProcessRecord()
   at System.Management.Automation.CommandProcessor.ProcessRecord()
   --- End of inner exception stack trace ---
   at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
   at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()
   at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()

Funny: For testing I have created a second (new) "deployment share" and the same CABs gets imported without problems there. So the problem must be somewhere in my old share, but I have no clue how to fix this.

I crawled tho hole web and can not find anything! I don´t wont to move my whole share to the new one :(

Any advise?



Problems imaging a HP ProBook 650 G2

$
0
0

Hi,

We use WDS&MDT to deploy our Windows 7 images on different brands and models of machines. Recently we bought some HP ProBook 650 G2 laptops with which we have a lot of problems reimaging them. This is a summary of the problems when we try to deploy a Win 7 Pro x64bit image:
a. if I define the task sequence variable DriverGroup001 and create a folder for the Make and Model of the model, after the wim file is deployed, when Windows try to start for the first time I have BSOD. This happens even the Model folder doesn't have any drivers loaded.
b. the same thing happens if I don't define the TS variable and I just set the TS too look for all matching drivers 
c. if I define the TS variable, but I don't create the folder tree (Make&Model) then the image deploys and Windows starts with no drivers loaded indeed (and TS fails as expected because of lack of network connectivity to continue - no ethernet drivers).
d. I was only able to deploy a very old image (with a version of Windows last updated in 2014), but on the moment I updated it fails too 
e. if I deploy the image using "c" option and after I load the drivers manually, Windows works without problems. Also Windows works well if I deploy the old image and after the imaging process I update Windows manually. 
f. I checked the BDD.log but I couldn't find anything useful. 
g. I incline to think there is a problem somewhere between windows updates, model drivers and how MDT works (injecting the drivers), but I couldn't find anything helpful until now. 
Any suggestions are much appreciated! Thank you!



MDT 2013 Update 2 Build 8443 - Issue creating media

$
0
0

Stats

  • MS Server 2016 Standard (Also issues with MS Server 2012 R2 Std)
  • Windows ADK 1607
  • MDT 2013 Update 2 Build 8443

Process

  • Imported Captured OS WIM
  • Imported Drivers
  • Created Standard Task
  • Created selected profile for media (included OS, Driver, Task) we will call it "PortableMDT"
  • Created media with selected profile "PortableMDT"

Starts to create media and puts OS WIM but then fails on importing drivers with "Unable to find the specified file."

What am i doing wrong? I have recreated deployment share too. Please help

MSVCR100.dll is missing?

$
0
0
I'm using Deployment Workbench [Version 5.1.1642.01] for imaging. I've recently been getting an error when Setup is checking the video performance. I've tried different workstations and also using different Wim files [custom and directly from the Win 7 SP1 x64 iso].

Creating Local Accounts with MDT and Config Mgr OSD: How to?

$
0
0

We are using an MDT 2012 UDI deployment Task Sequence  in Config Mgr 2012. I have attempted to create and add a local account to the administrators group during deployment using both the default unattend.xml and a custom answer file. In both cases this setting is ignored. I am a little confused because other settings I specify in the answer file such as IE home page are preserved after deployment, but the local account is never created.

Is this possible to do via the method I am describing or is there another method I must use?

Driver management

$
0
0

Morning

Im using the latest version of MDT and currently using the Johan Arwidmark way of deploying drivers which works well providing you have the drivers in yourWindows 7\x64\%model% .

This question is more about if anyway has a good way to know about driver updates?

for example we have been imaging some dell xps laptop recently all working fine, however one has just come in and the MDT image failed, the reason being that the drivers being different on this hardware to others.

Of course afterwards i went to the dell website, entered in my service tag and downloaded drivers and installed fine.

so does anyone have any good suggestions as to how i could either be notified of these driver updates or a way MDT can get these drivers automatically and keep them updated?

thanks

Unable to Capture windows 10 reference image

$
0
0

Hi All,

I am trying to capture windows 10  from a reference computer (Virtual Machine)

MDT version :- 6.3.8443

but getting error as 

FAILURE ( 5208 ): Invalid DeploymentType value "" specified.

not sure where i am doing wrong, can anyone help with this please. thanks in advance.

Regards,

Manoj

Slow PXE boot and Task Sequence execution after migrating to VM

$
0
0
I recently migrated my MDT/WDS server from a physical machine to a VMware virtual machine. Prior to migrating it, my PXE TFTP transfers took less than 20 seconds and they are currently taking a few minutes. Nothing in my environment changed other than migrating to the virtual. Additionally, after migrating to VM my boot.wim loads and boots but does not run the start of my task sequence. This happens intermittently, sometimes a reboot or two fixes the issue and the task sequence runs without any issues. I have attempted to change my max TFTP block sizes to 16784 but this had no effect. I am only running these deployments in unicast with a max of three or four machines pulling images. Today, for instance I have two machines on my bench. One imaged fine, the other wont contact the Deployment server. It does not even register with the MDT monitoring server. Not sure what else can be done. I have not done any packet caps but given that nothing in my network changed I am not sure that would yield any results. 

MDT2013 stuck on install office2016

$
0
0

hi

I created a TS to install Win7 and office2016. However, the TS will be stuck on install office2016.

When the TS try to install office2016, it will show prepare required document, then the whole application will hang and not responding. if now, I restart the comptuer, then everthing will be fine, office 2016 will be installed. The TS will be completed sucessfully. 

I have not idea why the TS stuck in the first place ( the first time install office2016)

But if I use this TS with office 2013, then everything is fine, not stuck.

anyone has idea?

Thanks

Jack

Windows MDT 2013 Update 1 & Injecting driver problems

$
0
0

Hello,

Since I started working with MDT 2013 Update 1 and the Windows 10 ADK, I am experiencing problems with the model based driver injection. I already found a thread that exactly described my problem from the beginning to the end. Sadly enough this thread was closed and I am afraid I will never get a answer on my reply.

https://social.technet.microsoft.com/Forums/en-US/18bba33c-490d-4334-a88f-af18c4c791e6/mdt-2013-update-1-not-injecting-drivers?forum=mdt

In this thread, Keith Garner wrote a reply that this problem is not related to MDT, most likely to WinPe or Intel.

Like Roy-Batty already wrote in the original thread, I can confirm that this issue occurs during the ZTIGather process in the new WinPE.

System: Intel NUC D34010WYK

In the same thread, Mirfster asked the question if the information was available after the deployment was done and all drivers were installed manually. By coincidence I am using the same workstation as the one I am trying to image. As requested, I Installed the most recent drivers and BIOS updates. To test if this would solve my problem, I did the following:

  1. Open msinfo32.exe to see if there was any system information: Empty strings

  2. Execute “wmic computersystem get model” in command prompt: Empty string.

  3. Executed the Wbemtest.exe solution that Keith Garner provided in the original thread: Empty strings

So it seems the problem also occurs within Windows 10 itself. To be sure I checked the information on a HP Pro 3120 MT workstation with Windows 10 64-bit installed, al the necessary information was there. This made me believe that this indeed is an Intel problem.

With all the information gathered, I decided to open a chat support with Intel. After 1 hour of explaining, the answer was:Remember that this is an issue within the operating system, not from the hardware. The software reads the information from the hardware, why the software is not reading this information correctly is a question to the operating system developer which in this case is Microsoft.

So I am kinda stuck on this one. Who should I contact to find out what is causing this problem?

I also would like to point out that the driver injection during the deployment of Windows 8.1 or Windows 7 also fails. The only difference with windows 10 is that after the deployment all information is available trough msinfo32 or a WMI query in command prompt.

All help is appreciated.

No MDT Imported Drivers Loading, only PnP drivers - Elitebook 840 G1

$
0
0

I am deploying a custom wim of Windows 10 x64 enterprise.  I built the image on VM and now trying out a USB media deployment.  The Deployment goes through till finish with no errors.  After the deployment I checked Device manager and had several bangs for missing drivers.  

I am using the "Total Control" method.


- I verified the name structure of my Out of Box MDT Folder "Windows 10\HP EliteBook 840 G1"

- I verified the WMI name is "HP EliteBook 840 G1"

- I built a CAB file using the HP SDM and imported that CAB into my Deployment Share.

- I verified in the TS that the pre-install "Set Drivergroup" sequence has the value of "Windows 10\%Model%"

- I verified in the TS that the pre-install "Inject Drivers" sequence selection profile is set to "Nothing" and "Install all drivers from selection profile."

- I see drivers being injected during the pre-install phase of deployment.

- No network cable is ever plugged in during the deployment or any moment after the deployment finishes (so driver logs can be as clean as possible on client side)

- Checked ZTIDrivers.log and see lots of drivers being copied to C:\Drivers. I do NOT see a C:\Drivers folder after deployment (Should I?)

- BDD.log shows at the beginning "Unable to determine asset tag by WMI"  but a few lines later in the log Property Model information is populated to be correct.

When it was all said and done I was able to verify some network drivers that did load were not the ones I imported (different versions, verified by updating driver and selecting my USB Deployment share Out of Box folder to search, it did load the driver from that search.)  I also updated devices that loaded generic windows drivers with the drivers from the Out of Box Folder.  Also, devices that had missing driver bangs were all able to be updated by manually selecting update driver and pointing the search to my USB Out Of Box Drivers folder.

So it seems my deployment is not loading any of my imported drivers and only loading built Windows drivers and I am not sure why.  I have looked over logs but this is kind of new territory for me and I am sure I am overlooking something.  I have to be, right?

You should be able to find the logs I think someone may need to help at this location:  Logs here

Thank you for any help that could be offered!


Problem with Dell ZIP driver injection into MDT.

$
0
0

I've been using Dell's CAB files without any issue until recently when I worked on a Latitude 5414.
The CAB fails when importing drivers to the Out-Of-Box. Its a known issue they are working on.
Meanwhile, Dell directed me to their ZIP file download page. It is more of Family Pack groups.
The ZIP allows all drivers to be imported (.inf) but at the desktop at the end of the TS, I get prompted to click OK for about 4 or 5 installation programs. The tech I spoke to was completely confused as to why INF files would prompt me to allow .exe files to install.

Has anyone seen this occur in MDT? If so, what is needed to automate the installation of these exe drivers? I've never seen this happen before. It does not come up with CAB files.

Link to Dell's Family Pack zip files:

http://en.community.dell.com/techcenter/enterprise-client/w/wiki/11438.dell-family-driver-packs

Autopopulate deployroot network credentials only for specific hardware model?

$
0
0

We would like workstations of a specific model to automatically launch an OSD with no prompts, but any other model device to prompt for credentials before being allowed to access the MDT wizard.

If we add network credentials to bootstrap.ini, it will apply to every system instead of only this model.

How can I configure customsettings.ini to allow this?


automation

$
0
0

I am looking for a solution to install application application based on values mentioned in a excel sheet.

in excel sheet .. against  each  computers values like {02cff604-e308-437f-9892-82bf0bc08ad3} and {9b2636d1-2e98-497f-96c0-c6c14701ac0f} is mentioned .MDT task sequence should open excel sheet ..search this computer and read value based the computer name and retrive  on the application ID (ex : {02cff604-e308-437f-9892-82bf0bc08ad3})  ....

then update MDT application variables ...

then install applications step in Task sequence after ztigather so that applications gets installed based on the variables 

MandatoryApplications001={02cff604-e308-437f-9892-82bf0bc08ad3}
MandatoryApplications002={9b2636d1-2e98-497f-96c0-c6c14701ac0f}

in sccm I was able to get it worked...by opening the excel shhet and retrive value and update dynamic variables..

Set objXL = CreateObject("Excel.Application")
Set objWB = objXL.WorkBooks.Open("\\XYZ\computerSpecficApps.xlsx")
Set objWS = objXL.ActiveWorkBook.WorkSheets("AppsMapping")
Set objTSEnv = CreateObject("Microsoft.SMS.TSEnvironment")

is this possible with MDT ?  does MDT aslo have Microsoft.SMS.TSEnvironment ? if it is not there what other objectis is available in MDT


verification


Captured Windows 10 WIM file too small

$
0
0

So I am trying to capture my reference image of Windows 10. It goes through everything as normal but the WIM file it spits out into the captures folder is only 3.4mb. The wizard says complete though with no errors? I have sifted through some log files but with no answers.

Anybody have any ideas?

Joel

Newbie to MDT World

$
0
0

I worked with MDT for several years but never had the opportunity to actually set one up from scratch and need some help.

Followed this guide http://deploymentresearch.com/Research/Post/540/Building-a-Windows-10-v1607-reference-image-using-MDT-2013-Update-2

The deployment starts off with the MDT Screen, goes to Gathering the tasks, then to this screen. I enter the Admin password which I have verified several times in the customsettings and bootstrap files but the deployment never kicks off. What am I missing?

Viewing all 11297 articles
Browse latest View live




Latest Images