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

Invalid Credentials: The network name cannot be found

$
0
0

Hi everybody !

I have a issue with WDS + MDT2010.

First of all, I can only access to the server remotely, I have a person who does the tests but he don't have skills in this domain so I'm a bit alone face to the problem and I'm lost.

The network is composed like this :

HQ based in FR (where I am) and an office in the USA, this is the same domain for the two.

We have a working deployment server here in FRANCE but impossible to make working the server at the USA. This server is too DC, DNS, DHCS etc.

The issue is showed by this picture : http://imageshack.us/photo/my-images/444/20531368.jpg/

Voici le fichier Bootstrap.ini :

[Settings]

Priority=Default

[Default]

DeployRroot=\\"SERVERNAME"\DeploymentShareMDT$

The person who tries to deploy the computers can't use the admin rights, he is not allowed to use them so he use an user account. But in the past he ever had deployed laptops with his credendials.

Is someody had a good idea about my problem? They have laptops to deploy and make pressure on me...

Best regards all !!


MDT WinPE Network Driver Issue for ThinkPad X250

$
0
0

Hi guys,

When I use MDT2013&ADK8.1 to deploment Windows7X64 into ThinkPad x250, I got network driver issue.

 A connection to the deployment share (\\...) could not be made. The deployment will not proceed. The following networking device did not have a driver installed. PCI\VEN_8086&DEV_15A2&SUBSYS_222617AA&REV_03"

And I check the solution including download correct drivers and create a new profile ..etc but the problem still happened....

Anyone met this before?

Wondering if anyone could help me about this, I almost crazy....

PS  server OS is windows2008r2


ZTI ERROR - Unhandled error returned by LTIApply: Permission denied (70)

$
0
0

I am having so much problems with creating a syspreped image, I figured I would try to create the sysprep image with WDT.  So I tried that, turned of UAC and tried creating an image.  Like with everything else I have done with MDT, nothing seems to work out. 

Here are the bdd.log 

BDD.log

MDT Build Share Update - Question

$
0
0

Hello All,

Hoping for some guidance here. 

Current Build Share = MDT 2013

Intended Build Share = MDT current release (MDT 2013 Update 2)

My question is perhaps simple for many who have upgraded their MDT 2013 > Update 2. I am familiar with steps of upgrading, though I just want to ensure that updating the deployment share won't cause new image captures to fail. As many, we use VM's to capture images i.e (during build, TS goes into suspend mode, we modify the OS, shut it down, take a snapshot, start up the OS, and continue the TS to capture the image).

Would updating the build share cause any files to change etc. causing the image capture to fail, in case it is looking for some specific version of file / script that MDT looks for? The idea is to upgrade the current Build Share and start doing some testing for WIN10 build & capture.

Comments are much appreciated. Thanks.

Windows 8.1 not installing through MDT

$
0
0

I apologize in advance as this is my first time working with this so I am a bit lost. I am creating a virtual environment to practice sccm in and cannot seem to get one of the vms to work with windows 8.1. I select the correct media and get an error that states

"operating system deployment did not complete successfully."

Failure (5640): False: verify file E:\deploy\operating sytems\w81x64\sources\install.wim

Using notepad's open menu I was able to see that the install.wim file that is in the source location (c: on the physical server) is somehow not showing on the virtual machine during install. Instead there is an install.esd file. 

Has anyone seen this issue? I can provide the bbg.log logs if that will help.

Thanks in advance! 

Error installing MSI

$
0
0

Hello, I am having a problem getting one program that we use in house to install. The file is a .msi file and I have it set with the msiexec command that I can use to install the program using the /quiet function and I keep getting a return code of 1603 at the end of my deployment. Other msi files install just fine using the same commands I can run from the command prompt. I am stumped. I downloaded trace32 to see if I can find the problem but the only thing I get is that the program returned an unexpected return code: 1603. I have the pre-requisites for the program installed with it's own Install Application task sequence, and even a reboot to ensure that it was installed like it should and still get the error. This is the last step I have to get past so I can use the deployment completely.

Thanks

 

WinPE 5 802.1x Support with SCCM 2012 R2

$
0
0

Please see updated information a few posts down.

I am trying to get 802.1x support working to deploy windows 7-8 machines using MDT2012.  I have checked IEEE 802.1x network authenication protocol under features of the deployment share properties.  I am trying to follow the guide on the deploymentguys. I have my files on the boot image and can do a net start dot3svc, we are not using certificates at the moment for our 802.1x so I am skipping that line.  doing a netsh lan add profile filename="X:\8021x\ Local Area Connection.xml " interface="Ethernet2" does work.  I am having a problem with the third step when I run the following command netsh lan set eapuserdata filename=x:\8021x\Wired-WinPE-UserData-PEAP-MSChapv2.xml allusers=yes interface="Ethernet2"  All i get is error setting user data for interface ethernet2, the operation is not supported.

How does one get 802.1x working in WinPE 4.0?

Heres the latest updated in this first post so you dont have to scroll way to the bottom to get the latest relevant information:

So here's the current situation and hopefully someone has seen it before.

My boot image has the prestart command set to x:\8021x\configure8021x.cmd.  If i make a USB boot media this command will run and work with an 8021x wire plugged in.  If I PXE boot with a non8021x wire plugged in this command will run.  If I PXE Boot with an 8021x wire plugged in it does not run the command.  If the boot image gets staged from the windows software center it also will not run my command.

Does anyone know why the staged boot image and booting from PXE are not running my prestart command?  It seems that during PXE and staged boot that the network initializes BEFORE it runs any prestart commands?


MDT service account not getting past the connect to deployment share

$
0
0

Hi Everyone, 

I have configure WDS and MDT to work great with my own account which is a domain admin account. I got a custom image, I have injected drivers and set application to install in the task sequence. works great with my account. Now I am trying to automate it as much as I can for my team to use it without having to sign in every time. 

I created my service account, gave it rights to be able to add to the domain. I also gave it full access to the share and the folders. (even though I read that read only is enough) I also updated the bootstrap.ini to include the service account name and password. I updated the WDS share and re-imported the Windows PE boot .wim's

It signs into the deployment share but just sits there with the Windows deployment Toolkit background and doesn't get passed that screen. 


MDT 2013 U2 UDI Wizard preview not working

$
0
0

Hello. Has anyone else noticed that clicking the UDI Wizard preview does not do anything ?

I have tried on several systems with the same result, nothing happens.

I monitored the activity with process monitor, but the processes it fires seems to exit normally.


eshe

MDT 2013 U2 - no c:\drivers

$
0
0

Hi,

When the deployment reach "desktop" phase i have connection error - no ethernet driver.

after reading logs a think that ZTIdrivers dont probe for hardware ID and dont copy drivers to c:\drivers (i think). 

my logs https://drive.google.com/drive/folders/0ByMSSj2D--v6bU81aTZLUmVkZFk?usp=sharing

What do You think about that?

MDT 2013 Update 2 Monitoring errors

$
0
0

We just upgraded our MDT server to Update 2.  After the update, monitoring is not longer working.  The service is running and the settings in cs.ini are correct.  The bdd.log on the client shows an error from the web service - "Unexpected response from web service: 400 Bad Request"

The monitoring service was working perfectly before upgrading to Update 2.  Has anyone seen this issue?

Windows ADK w/ UWP App Installed

$
0
0

** hopefully this is the correct forum.  It involves UWP and Microsoft ADK.

Hi there --

I am using the latest version of the Windows 10 ADK to create a Windows 10 OS image.  The Windows Imaging and Configuration Designer (ICD) works well but I have run into a snag.  I've spent several days trying to get a default Windows UWP app to be included within the ICD image. I am following the directions described here

Documentation https://msdn.microsoft.com/en-us/library/windows/hardware/dn916109(v=vs.85).aspx

...It seems so easy and I just can't seem to get it to work.  My UWP app already exists in the store -- so I know that it passes WACK.  I am just including the .appx (also tried .appxbundle) package.   ICD accepts the package and saves the entry within the configuration.  When the OS is deployed my app cannot be found.

Does anyone know where errors are reported for UWP onboarding during the OS initial install?  Separately, has anyone had success with this before?

OK, one last question -- there is a field in the documentation for an XML license.  I'm not familar with any XML licenses for UWP apps -- does anyone know what this may be referring to?


Thanks,

Shaun


I am receiving an error message whenever I import a Captured Image (WIM) file on Microsoft Deployment Toolkit 2013

$
0
0

The following error message:

Performing the operation "import" on target "Operating system".
Data error (cyclic redundancy check)
Data error (cyclic redundancy check)
System.ComponentModel.Win32Exception (0x80004005): Data error (cyclic redundancy check)
   at Microsoft.BDD.Core.DirectoryUtility.CopyFile(DEInfo sourceFile, DEInfo destFile, String destFullName)
   at Microsoft.BDD.Core.DirectoryUtility.BeginCopyFile(String theSourceFile, String theDestFile)
   at Microsoft.BDD.PSSnapIn.ImportOperatingSystem.ImportWim(String sourceWim, String directoryName, String setupDir, Boolean moveFile)
Import processing finished.

Would appreciate the help on how to resolve this.  Thank you!

"The task sequence has been suspended. LiteTouch is trying to install applications. This cannot be performed in Windows PE."

$
0
0

MDT 2012 Server is up and running. I mistakenly deleted a Task Sequence step called "Install Application" that I thought was not needed (I know I should have disabled it and tested).

I have a problem now, when I went to image a computer I did not get application list (This used to work before I deleted the above TS step) with items to check and uncheck for installation.  "Install Application" TS was readded but now when I try to image I get this error:

"The task sequence has been suspended. LiteTouch is trying to install applications. This cannot be performed in Windows PE."

I've tried moving it to different positions on the list (Higher and lower) to no avail, I always get the same error. Please advise.

-Thanks in advance!






Out-of-box drivers showing blank : MDT 2013 u2

$
0
0

MDT 2013 update 2   : ADK 10.1.14393.0 - Installed on Windows server 2012 R2 - MDT Share with DFS

Hi all,

  I have a strange issue with MDT. All my Out-of Box drivers in MDT showing blank but when i browse to out-of-box drivers in explorer, they are all in there.

So, i have uninstall MDT (REBOOT), Uninstall (adk) reboot. Reinstall ADK (reboot), reinstall (mdt) reboot, no luck.



has anyone seen this issue?


orion


MDT 2013 - using WSUS with Windows 10 reference image

$
0
0

I have used a process to connect to our internal WSUS server and install latest patches before capturing the reference image on Windows 7 successfully for a long period of time. Now I am trying with Windows 10 and it doesn't seem to behave the same way so I'm looking for someone to tell me what I'm doing wrong. Here is my process:

- MDT 2013 selecting Windows 10 1607

- I have a Pause in my selection task so I can import our internal WSUS server certificate.

- During this pause I also install KB 3189866 manually to fix the WSUS issue 1607 was experiencing

- I have a selection task created to perform Windows Updates and in the customsettings.ini file I have specified our internal WSUS server as the WSUS server it should connect to

- when I resume the Windows Update task starts and it connects to the WSUS server and installs all appropriate updates

- when done I have verified there are no more updates the reference machine needs from the WSUS console and I also can  see all the updates that were installed in the update history section on the reference machine

- The process continues on and I capture the WIM file

However, on the reference image I am now no longer able to see anything in the update history section and when I use the new reference image and connect the machine to WSUS it wants to download and install the exact same updates as if they hadn't been installed before. Can someone explain why this is different than Windows 7 and what the heck I'm doing wrong?

MDT with HP laptops (license in recovery / BIOS)

$
0
0

Hello,

We have around 1k laptops here, ATM when we need to reinstall those machines we are just booting on the recovery and reinstallating them, everything is fine, and we get back the Windows license, etc, but it's very slow (reinstalling manually softwares etc).

So we would like to reinstall them by using WDS/MDT (drivers / softwares) everything work fine, but we have 1 left problem, we don't now how to get back the original key from the BIOS/Recovery.

I hope you understand my question, sorry for my bad english.

Thanks in advance.


MDT 2013 Windows 8.1

$
0
0
Hello, I need advice.I havedoneadjustedfor the company's imageon a USB drive and would love toget herinto thedeploymentworkbench,whereIperformed some changes.It'ssomething simpleto editit again?I would not wantto do it allagain settingimage.

MDT 2013 (Microsoft Deployment Toolkit) Using Litetouch.vbs does not capture an image.

$
0
0

Our MDT 2013 fails to capture an image, when we run cscript litetouch.vbs, it skips the prompt for the location of the image, and completes.

The last time, we tried to capture an image was July 2015, when all was working well. This was discovered because after applying MDT 2013 Update 2, for Windows 10 deployment, (deployment of Windows 8.1 and 10 Reference Tasks Sequences remain ok and perfect), but we cannot capture....Windows 8.1 and Windows 10, so after the update we've rolled back to January 2016 backups in isolation in the Lab.

So something changed between July 2015 and January 2016, not sure we have backups, that far to go back. (not checked yet!). Only changes are regularly Windows Updates. We used to be able to deploy and capture the image.

1. The current Windows 8.1 image Task Sequence can be deployed successfully.
2. The current Windows 10 image Task Sequence can be deployed successfully. (Vanilla Image from WIM Imported ISO)
3. Captures for Windows 8.1 fail.
4. Captures for Windows 10 fail.
5. A new Capture Task Sequence has been created, and also fails.
6. This was working in July 2015, last time an image was captured.
7. Between July 2015 - January 2016, something has broken.
8. Only Windows Updates have been applied to MDT 2013.

We really need a MDT expert, that uses this on a daily basis, to discuss this issue, unless you have seen this issue.

(We've also tried updating to MDT 2013 Update 2, ADK 10, and the issue also remains, so this is something that has changed which causes this!)

bdd.logs and customsettings.ini available, we would love to be able to capture again!



Andrew Hancock

MDT and Windows Product Keys

$
0
0

In my organization we use Windows 10 Pro and purchase all of our systems from Dell as Windows 10 Pro downgradable to Windows 7 Pro.  We have a volume licensing agreement so I am able to use MDT to deploy the systems with a customized Windows 10 Pro image.  We use the OEM keys that come embedded in the BIOS to activate them after deployment.  I am trying to find a way to automate the Activation.  Either by having Windows grab the key from the BIOS, which doesn't look like is possible unless you are an OEM or have MDT ask for the key when the Tech starts the Deployment.

Are there any solutions out there for this?  Since we don't buy the licenses through the VL agreement I am not sure if we could do KMS or not, and I don't see a KMS key on the VL site anyway.

Thanks

Viewing all 11297 articles
Browse latest View live


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