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

Invalid credentials when trying to capture win 10 image with MDT WDS

$
0
0

I've setup an new MDT server to capture a win 10 image with application installed. intiall im able to connect to the deploymentshare folder using my ad credential that is a domain admin and also a local admin on the MDT server and has permission to the deploymentshare. I also give everyone full right to the deployment share to rule out any permission requirement. when I lounch the litetouch vbs script from the win 10 machine, it ask me for my credentials and then strats running, then on the second prompt I get invalid credential error. 

below is my rules 

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
OSInstall=N
SkipCapture=NO
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerBackup=YES
SkipBitLocker=YES
DoCapture=YES

I hve also added my userid to the bootstrap.ini file with out any sucess. I also can mat the deployment share from the wim 10 machine I can ping the MDT server from the win 10 machine. I'm out of option, does anyone experience this issue? 


Deploy computer as if new

$
0
0

I am working on a OS deployment in MDT and have met an unfamiliar issue. For this particular deployment I need the computers to be deployed with a Win 10 image just like it they were new. This means no OOBE stuff, i just want the image applied and nothing else. The reason for this is that this way, when the machine is first started, the users can log on with a Microsoft account and Intune will handle the rest based on this account. The problem I face when using an OS task sequence in MDT is that the local Administrator account will log on during the deployment process to finish the task sequence, so the first real person to log on is not actually the first account on the computer.

Any advice on how to achieve this will be much appreciated.

Error Code 0xc0000001 when trying to PXE boot

$
0
0

Good Morning, 

 Yesterday I was working in MDT to add a App package. It wasn't working so I deleted it and updated the Deployment Share. When I try to PXE boot now, I am getting this error:

Nothing else changed except for me deleting the app package I was trying to install. Everything was working fine until I updated the deployment share. Any ideas on what went wrong here?


SC

"Ignoring Image Index 1" Custom WIM does not appear in MDT Console.

$
0
0

Greetings,

I encounter a problem while trying to import a wim file into my Deployment Share.

But, before describing this error, let's explain the situation :

  • I'm deploying some laptops with a very specific configuration, those laptops have a C partition and a D partition (Windows 7)
  • I captured and imported the C (system) partition without problems
  • I captured the D (data) partition using imagex with the following command "Imagex /compress fast /capture D:pathtowimfile
  • It generates without any error a wim file
  • But when i try to import this wim file into my deployment share, it takes few seconds to import and i have the following message : "Ignoring Image index 1"
  • The weirdest is when i check the content of the deployment share, the wim file appears but it does not appear in the MDT console
  • I tried to import this file in a other deployment share, i have the same problem.

What am I doing wrong ? Can anyone help me ?

Is there another way to capture a system with 2 partitions ??

Thanks !!!

Some additional informations :

I run MDT 2013 on W2016 server

Benjamin.

Event 41002 sent: FAILURE ( 5208 ): Unable to find the SMS Task Sequencer

$
0
0

Hi.

I got a problem i cant find a solution too. :( 

My MDT worked fine to about 1 month ago and i started to get this error when i capture 1803 or 1809. I tried to make a new Deploymentshare and it have the same problem. New image file 

The file TsmBootstrap.exe is int \tools\x64 and x86 

- FindFile: The file TsmBootstrap.exe could not be found in any standard locations.LiteTouch2019-02-22 11:32:130 (0x0000)
- FAILURE ( 5208 ): Unable to find the SMS Task Sequencer.  The deployment will not proceed.LiteTouch2019-02-22 11:32:380 (0x0000)
- Event 41002 sent: FAILURE ( 5208 ): Unable to find the SMS Task Sequencer.  The deployment will not proceed.LiteTouch 2019-02-22 11:32:390 (0x0000) 

Any ides? ;)

Windows Server 2019 can't connect to ?DT share

$
0
0

Hello,

I'm trying to depoy Windows Server 2019 and I get:

"A connection to the deployment share could not be made".

This is not a network issue I've got connectivity.

It's related to the permissions of connection to a share with Windows Server 2019.

Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters" -Name "AllowInsecureGuestAuth" -Type DWord -Value 1

I don't get why this behavior since MDT uses credentials to establish the connection.

Copy Task sequences seems to behave wierd !

$
0
0

WOW this is maddening.
I am trying to copy Task sequences in the workbench.
Simple objective. Create a task sequence – test it – copy it – modify the copy– test the changes - maintaining the original if all goes wrong with the modifications… and on and on and on….

Ah but these task sequences don’t behave like previous MDT and SCCM task sequences do they !

You cant copy a task sequence into the same folder and rename it in the process ?
So I create a Sub folder  - copy the task sequence there. – ok – Rename it – and hey!! Its renamed the original too.

So this is going to make it tricky to test  Develop my Task sequences in my normal way. Unless I am doing something really stupid (not the first time ) in my copy task process.

So how do you do it.

Trying to set folder permissions for users yet to sign onto pc.

$
0
0

I have a RunOnce working on Panasonic units to turn off Numlock for each user who signs on. I configure it under the Default user with a VB script and place it in the registry under RunOnce.

What I'd like to do now is set permissions on a folder under the user\appdata\local location for a folder that gets created for each user who signs on. I am not sure if I can copy the permissions/folder from an existing pc and use that somehow.

The standing issue is that the appdata\local folder had a folder in it that has to have authenticated users having full control, but for each user who signs on. We manually do this, but it gets skipped by some techs during the manual setup, so I'd like to have this happen during imaging if possible. I can't modify the installer because I don't even know what software was used to build the application.


Reference Image for 2019 BSOD after sysprep "PNP Watchdog"

$
0
0

I'm trying to get about as basic of a 2019 reference image built as possible, but I keep failing after it executes sysprep and reboots to capture.  It'll reboot to the windows icon with a spinner, but eventually BSOD's with a "Driver PNP Watchdog" message.  

MDT 8456

ADK 10.1.17763.1

Using server 2019 standard iso released in November.  

Vsphere 6.7, using e1000 NIC (have no issues with server 2016/12 or Win10/7)

I can use the same ISO and manually build the OS without issue.  

From the logging tab, it always gets to execute sysprep step 78 of 86.  It'll just continue to reboot and BSOD after this.

Any pointers on where to look to see what exactly is going on, would be greatly appreciated.

Office Click-to-Run in MDT Image

$
0
0

I am looking to create a customized Windows 10 image. I have installed an MDT 2013 Update 2 server to do the install. Within my image I would like to install Office Click-to-Run 2016. I am using the following article for guidance:

https://technet.microsoft.com/en-us/library/dn314789.aspx

I am using MDT to both deploy and capture the image. When the image finishes capturing I am getting the following warning:

"Unexpected return code while re-arming Office 2016, RC = -1073425660"

Image

Any help in determining if this is an issue and fixing it would be appreciated.

Thanks,

Mike


Solutions Architect

USMT - Query

$
0
0

We are observing large amount of data from USMT backup

Is there a way to find which file type  contributes more to size ?

Example : Is there any command which shows me what files or file types or folders  in the USMT is consuming more space? This will help to analyse and optimise the script accordingly.


verification

MDT upgrade question in Distributed environment

$
0
0

I inherited a 3 server MDT 2013 distributed environment that replicate via DFS. I need to upgrade MDT and I noticed Server A has MDT 2013 (build 8298), Server B (build 8298), Server C doesn't have MDT installed yet it's used for imaging workstations all the time?  My question is, do you need to install MDT on all three servers or does it only need to be installed on one server and then replicate the Deployment Share via DFS? 

Also, can I upgrade MDT to the latest build from build 8298?

Automatic Installation Volume License Office 2019 with MDT

$
0
0

Hello,

i want a automatic installation of Office 2019 deployed with MDT (as application).

With earlier versions of MS Office i did by : setup.exe /config proplus.ww\config.xml

I think this is not possible anymore with Office 2019.

Until now i can deploy office 2019 with the setup.exe and configuration-Office365-x64.xml

My xml-file is:

<Configuration>
  <Add OfficeClientEdition="64" DownloadPath ="http://officecdn.microsoft.com/pr/ea4a4090-de26-49d7-93c1-91bff9e53fc3">
    <Product ID="ProPlus2019Volume"> PIDKEY="xxxxx-xxxxx-xxxxx-xxxxx-xxxxx" >
      <Language ID="MatchOS" />    
    </Product>
  </Add>
  <Updates UpdatePath="http://officecdn.microsoft.com/pr/ea4a4090-de26-49d7-93c1-91bff9e53fc3" />
</Configuration>

With this setup, the volume licensing version is downloaded, and installed.

Problem:

After starting an Office Application, office must still be activated with the same key.

Anybody having a (better?) solution for the deploying Office 2019 with mdt?

Anybody having a solution for the activation-problem?

Thx

MDT OSDComputerName to pull First word of Make as the computer name

$
0
0

This is my current syntax to getting the OSDComputerName

:Set ComputerName
OSDComputerName=#Left("%Make%",9)#-#right("%SerialNumber%",4)#

This however does not properly name my computer if it comes from different manufacturers.

eg. AsusTek Computer Inc, Dell, Lenovo, Microsoft Corporation

With my current syntax, it will grab the first 9 character from the left, so if its an asus PC being deployed, it'll show as
AsusTek C-SerialNumber.

Is there any way to make it so that as soon as it finds the first Space, then the previous characters of the %Make% are used for OSDComputerName.

HideShell during non-OS Deployment

$
0
0

 I require HideShell to run in a Task Sequence that does not deploy an OS, it just initiates a reboot, installs a few applications, produces some logs and reboots again. This is a highly sensitive environment and no user interaction is allowed during the TS. Does anyone know of any way to use HideShell in this context, so not during an OS Deployment?

Thanks


quick question... update DS after new capture TS shows no changes

$
0
0

Hi,

I created a new Capture TS.

When update DS it didn't find any changes... "No changes were made, existing boot images will be kept."

So I don't have new Boot image.

What could be wrong.

Thx.


--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis


Task Sequence Wizard displays after OS install

$
0
0

I just updated MDT and the ADK for Windows 10 1709. I've noticed that when I run a task sequence to install an image (intiated via WDS), after the OS install and reboot, the Windows Deployment Wizard displays again and asks which task sequence I would like to run. The first time I noticed this, it was on a task sequence that I had made a copy of by copying the xml files, so I thought it was a result of that. I created a new task sequence without any copying and it does the same thing. In both cases, if I click through the wizard, it keeps going and finishes the sequence, but it shouldn't be displaying that wizard twice like this. In the second task sequence that I created, I used the Standard Client Task sequence template and the only thing I changed was the OS image to install and removed application installation. Anyone have ideas on how to fix this? 

Windows Deployment Wizard

MDT 6.3.8450.1000

Server 2012 R2 with Windows Deployment Services


MDT 2013 Install Language Packs

$
0
0

Using MDT 2013 and Windows 7 Enterprise.

I have downloaded the LP.cab files for each of my languages. I need to know how to import them to my deployment share and how/where to install it during my lite touch installation?

SkipPackageDisplay ignored

$
0
0

Hi all, I am on MDT 8456 and I am trying to install some additional language packs as part of OSD of win10 1809. I have done the following:

  1. Imported language packs to the deployment share under the packages folder
  2. Created a selection profile and assigned them to the language packs folder
  3. Configure the customsettings.ini with SkipPackageDisplay=NO (it did not work when set to Yes either)
  4. created an array for the language packs: LanguagePacks001={guid}
  5. in the task sequence selected the selection profile for the Apply Patches task (even when set to ALL Packages, it did not work)

Doing all that is still not making the wizard appear so I can select a package. Aside from that, the language packs are not getting installed. Please help, and thanks in advance.

Display driver not being installed

$
0
0

I have a new model of desktop Dell OptiPlex 5060, which I'm trying to image with an existing Windows 10 ts.  I've been using the "Total control" method outlined at https://deploymentresearch.com/Research/Post/325/MDT-2013-Lite-Touch-Driver-Management for years, but with this new model the display driver is not being installed.  That is, once the machine is imaged, I open Device Manager and it says it's using the "Microsoft Basic Display Adapter".




To be clear, I've download the 5060 version A04 (01/22/2019) .cab, from https://www.dell.com/support/article/ca/en/cadhs1/sln312414/dell-command-deploy-driver-packs-for-enterprise-client-os-deployment?lang=en, imported the .cab to a new folder under the Out-of-Box Drivers node called OptiPlex 5060 and I have the ts configured as shown here and here.  In the BDD.log it shows DriverGroup001 being set correctly and I can also see the display drivers being injected here.

Does anyone know where to go from here?

Thank so much for the help.

Viewing all 11297 articles
Browse latest View live


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