Dell OptiPlex 3060

[talksr]

Hi,

I have a suite of around 40 Dell OptiPlex 3060 systems.

Almost all of them need driver updates. Does anyone know if there is an easier way of getting the driver updates than manually installing the Dell Driver Update software?

This software is pretty good in finding and installing the driver updates, but it only seems to come as an EXE file. Which means I have to manually install it to each computer before checking for an installing updates.

 

Thanks in advance.

[oododkodkdo]

You can deploy them in MDT and capture the image of a Dell with the updates installed and after that, you can install the OS and the drivers with it as well.

It’s free as well!

[talksr]

You can deploy them in MDT and capture the image of a Dell with the updates installed and after that, you can install the OS and the drivers with it as well.

It’s free as well!

 

Thank you, just looking into that as we use MDT, but I tend to run a blank image onto the systems with just Microsoft Office installed.

Will see if I can build something and capture it as you suggest.

 

Will let you know how I get on.

[LeMarchand]

Thank you, just looking into that as we use MDT, but I tend to run a blank image onto the systems with just Microsoft Office installed.

 

You can still do that, but set up a driver store and target the drivers to the appropriate machines.

 

Just set up one machine with all the drivers you need and capture the drivers first.

 

TBH I cheat and let the setup process choose the drivers it wants. This is probably a Bad Thing.

 

Edit: You may find that one or two of the machines have slightly variant hardware, so you may have to add those drivers separately.

Edited July 31, 2019 by LeMarchand

[oododkodkdo]

Thank you, just looking into that as we use MDT, but I tend to run a blank image onto the systems with just Microsoft Office installed.

Will see if I can build something and capture it as you suggest.

 

Will let you know how I get on.

 

You’ll need to startup MDT and create a new task sequence and name it then, select Sysprep and Capture and select the OS on the Dell PC do the rest of that stuff.

 

Then, open Deployment Share properties and switch to the Rules tab. SkipCapture option must be set to NO

 

It’s best that you install the programs that you need such as Chrome and the Dell drivers.

 

After that, you’ll need to sysprep and go to this location on the Dell PC.

 

\\DEPLOYMENTSERVER\deploymentshare$\Scripts

 

Then, open LiteTouch.vbs

 

 

 

Now, select the Task Sequence that you made.

 

 

Enter the Local Admin password so, it can logon when it restarts.

 

Then, select Capture an image of this computer and set the path to store this.

 

 

After that, enter your Domain Credentials and let it do its thing.

 

It’ll take a long time.

 

Next, go to the MDT server and import it.

 

Then, create the Task Sequence and you’re done!

[talksr]

Thanks very much for your help with this.

I seem to be having an issue.

I updated my ADK, then added the new Windows 10 1903 image to Deployment Workbench using Import Operating system.

It has gone on no problem and is showing in Deployment Workbench, however when I am F12 booting to Windows Deployment Wizard, I select Lite Touch Windows PE (x64) and after authenticating, I am getting these options...

 

I have a task sequence for it, but it is not listing.

I have opened Deployment Workbench, updated Deployment Share and got the following error:

 

===

Making sure the deployment share has the latest x86 tools ===

 

=== Processing LiteTouchPE (x86) boot image ===

 

Building requested boot image profile.

 

System.Management.Automation.CmdletInvocationException: Unable to open the specified WIM file. ---> System.Exception: Unable to open the specified WIM file. ---> System.ComponentModel.Win32Exception: The system cannot find the path specified

--- End of inner exception stack trace ---

at Microsoft.BDD.Core.BDDWimFile..ctor(String wimPath, Boolean forUpdate)

at Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.UpdateBootImage(String template, String platform, String dpPath, Boolean createISO, String isoName)

at Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.ProcessRecord()

at System.Management.Automation.CommandProcessor.ProcessRecord()

--- End of inner exception stack trace ---

at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)

at Microsoft.BDD.Wizards.UpdateProgress.WizardProcessing()

at Microsoft.BDD.Wizards.WizardProgress.InitiateWizardProcessing()

 

Does anyone have any ideas on what the issue is?

[oododkodkdo]

Have you done this in all of the correct steps?

If not, you need to do this again.

My advice is to give deploymentshare$ read permissions for everyone and for where the Windows 10 Capture Image is.

And after you done that, do this again.

Oh yeah as well, make the Task Sequence Template after you have imported the Windows 10 Capture Image into Standard Client Task Sequence.

If this doesn’t work, you need to play with the rules on the Task Sequence which captures the OS and in the rules, you need to change OSInstall to NO before you capture the Windows 10 Image and also, you need to go to Windows PE and change the platform to X64 or X86.

Edited August 2, 2019 by SamA2V2

[talksr]

Have you done this in all of the correct steps?

If not, you need to do this again.

My advice is to give deploymentshare$ read permissions for everyone and for where the Windows 10 Capture Image is.

And after you done that, do this again.

Oh yeah as well, make the Task Sequence Template after you have imported the Windows 10 Capture Image into Standard Client Task Sequence.

If this doesn’t work, you need to play with the rules on the Task Sequence which captures the OS and in the rules, you need to change OSInstall to NO before you capture the Windows 10 Image and also, you need to go to Windows PE and change the platform to X64 or X86.

 

Hi, yes followed all steps for ensuring my Deployment Toolkit is working. Have not got to your steps yet as I cannot get the latest version of Windows 10 to show on WDS.

 

I followed this guide to install the newer 1903 version:

 

When I got the error as show in the last post, I went ahead and uninstalled then re-installed

Windows ADK for Windows 10 version 1903 and Windows PE add-on for the ADK.

The error then cleared when I did a refresh, but again, I am unable to see Windows 10 v1903 from the Task Sequence within Windows Deployment Wizard.

This is all I am getting:

 

This is not right. I have followed the instructions exactly.

 

Here is my newly imported OS:

 

And here is the new task sequence, which should be showing but is not:

 

The two sequences it is showing are within the main Task Sequences folder. I have a Deploy Office sequence and an old v1809 sequence. Cannot understand why it is still not showing my new 1903. I have deleted and started from fresh as well as updated the deployment share countless times.

 

It is like WDS and Lite Touch Windows PE/Windows Deployment Wizard are not talking to each-other and recognising the newer OS.

The only difference I can see is that in the YouTube video, he was Microsoft Deployment Workbench V 6.3.8456.1000 and I have 6.3.8460.1000. But I re-downloaded from Microsoft site today, so I must have the latest version.

Edited August 2, 2019 by talksr

[talksr]

Following on from my last post, if I go through your instructions to create a Task Sequence to capture the version of Windows I have set up, I am able to add the task sequence no problem....

 

 

But when I run LiteTouch.vbs on a client system I would like to capture, as you can see, the exact same Task Sequence list is showing, and your Capture Task Sequence is not on the list.

So I am currently unable to deploy Windows 10 1903 and I am also unable to capture any version of Windows 10.

 

 

You mentioned:

you need to go to Windows PE and change the platform to X64 or X86.

 

Where do I find this?

Edited August 2, 2019 by talksr

[oododkodkdo]

Alright new plan, PXE boot with your Dell PC with the drivers installed and the Task Sequence you select is your Windows 10 Edu V1809 and select Capture an Image of this reference computer and set the UNC path which you can write to and then you can make a WIM file and you can import that and then, create a Task Sequence called Dell OptiPlex 3060 Windows 10 Edu V1809 (change if you want) and leave everything as it is (if you want to) and change the OS to the Image of the Dell.

 

Forget the platform because now, it’ll auto detect

Edited August 2, 2019 by SamA2V2

[oododkodkdo]

Following on from my last post, if I go through your instructions to create a Task Sequence to capture the version of Windows I have set up, I am able to add the task sequence no problem....

 

[ATTACH=CONFIG]54585[/ATTACH]

 

But when I run LiteTouch.vbs on a client system I would like to capture, as you can see, the exact same Task Sequence list is showing, and your Capture Task Sequence is not on the list.

[ATTACH=CONFIG]54583[/ATTACH]

So I am currently unable to deploy Windows 10 1903 and I am also unable to capture any version of Windows 10.

 

 

You mentioned:

 

 

Where do I find this?

 

How’s everything going?

[talksr]

How’s everything going?

 

Hi Sam, just about to try what you have suggested as site was closed over weekend, so I couldn't get in.

Will let you know once the process has completed.

[talksr]

Alright new plan, PXE boot with your Dell PC with the drivers installed and the Task Sequence you select is your Windows 10 Edu V1809 and select Capture an Image of this reference computer and set the UNC path which you can write to and then you can make a WIM file and you can import that and then, create a Task Sequence called Dell OptiPlex 3060 Windows 10 Edu V1809 (change if you want) and leave everything as it is (if you want to) and change the OS to the Image of the Dell.

 

Forget the platform because now, it’ll auto detect

 

 

Sam,

Bad news,

Here is what I did:

Windows Boot Manager

Selected: Lite Touch Windows PE (x64)

 

Microsoft Deployment Toolkit

Selected: Run the Deployment Wizard to install a new Operating System

 

Credentials

Entered in username, password and domain.

 

Task sequences are displayed. But there is no capture sequence.

 

As you can see, the capture task is not showing on the Task Sequence when booting from PXE boot:

 

This is becoming such a headache!

[oododkodkdo]

Go back to your MDT server and create a brand new folder in the Task Sequence section and then, create a new Task Sequence and the template must be the default and all the settings you apply is your choice but, on the OS section, select the OS that is on the Dell computer.

After that, refresh your deployment share.

Go back to PXE booting and when you see the screen about Sysprep, select it and let it do it’s thing.

Go back into Lite Touch and capture the image and set a UNC path.

[talksr]

Go back to your MDT server and create a brand new folder in the Task Sequence section and then, create a new Task Sequence and the template must be the default and all the settings you apply is your choice but, on the OS section, select the OS that is on the Dell computer.

After that, refresh your deployment share.

Go back to PXE booting and when you see the screen about Sysprep, select it and let it do it’s thing.

Go back into Lite Touch and capture the image and set a UNC path.

 

 

 

Thanks for your help on this.

Ok, I think I know why this could be.

I have done as you suggested, but when I create the new Task Sequence, the only OS available in Select OS is Windows Edu 1903. This is the one which does not come up during the Light Touch Windows PE pxe boot when using Microsoft Deployment Toolkit. I have manually upgraded the system in question from 1803 to 1903. I will try again the PXE boot now and see if it shows the option.

 

It really seems to me that parts of MDT and Deployment Workbench are not talking to eachother.

[talksr]

Thanks for your help on this.

Ok, I think I know why this could be.

I have done as you suggested, but when I create the new Task Sequence, the only OS available in Select OS is Windows Edu 1903. This is the one which does not come up during the Light Touch Windows PE pxe boot when using Microsoft Deployment Toolkit. I have manually upgraded the system in question from 1803 to 1903. I will try again the PXE boot now and see if it shows the option.

 

It really seems to me that parts of MDT and Deployment Workbench are not talking to eachother.

 

Quick update, same problem. No capture is being listed. Exactly the same as before, just Deploy Office 2016 or Windows 10 v1809 x64 TS

[oododkodkdo]

Choose Windows 10 v1809

[talksr]

Choose Windows 10 v1809

 

Ok, but that will re-install Windows 1809 again. It is not the task sequence I made to capture Windows. It is the one to install it. So I will loose all of the drivers and additional software I put on.

[oododkodkdo]

Go through the options and check if you can Sysprep the computer and select it.

[oododkodkdo]

If you don’t, go to Windows 10 1809 Edu and go to rules and you’ll see SkipCapture which is set to yes.

You MUST set it to NO.

Then, refresh your share and PXE back into Lite Touch and check if you can find Sysprep.

[talksr]

If you don’t, go to Windows 10 1809 Edu and go to rules and you’ll see SkipCapture which is set to yes.

You MUST set it to NO.

Then, refresh your share and PXE back into Lite Touch and check if you can find Sysprep.

 

Ok thanks. I will give it a try.

[oododkodkdo]

Is everything smooth or bad news?

[talksr]

Is everything smooth or bad news?

 

Hey, I am afraid it was further bad news. Everything I tried would not work, so I have gone ahead with the 1803 to all stations purely on the basis I had wasted about three days and got absolutely nowhere.

 

Really frustrated with Windows 10. Have had noting but problems and issues with it from Start Menus not working, UAC issues when trying to open apps to so many issues deploying it.

It has by far cost us the most in terms of my time in trying to sort it all.

 

Anyway, thanks very much for all of your help on this.

[oododkodkdo]

Hey, I am afraid it was further bad news. Everything I tried would not work, so I have gone ahead with the 1803 to all stations purely on the basis I had wasted about three days and got absolutely nowhere.

 

Really frustrated with Windows 10. Have had noting but problems and issues with it from Start Menus not working, UAC issues when trying to open apps to so many issues deploying it.

It has by far cost us the most in terms of my time in trying to sort it all.

 

Anyway, thanks very much for all of your help on this.

 

No problem and also, Windows 10 always seems to have issues with WDS even the new versions and took me setting up a WDS Image about a couple of days as well so, I ended up capturing Windows 8.1 Enterprise.

[talksr]

No problem and also, Windows 10 always seems to have issues with WDS even the new versions and took me setting up a WDS Image about a couple of days as well so, I ended up capturing Windows 8.1 Enterprise.

 

Thanks again for all of your efforts.

I really hope Microsoft will take note. Smaller schools like this are being forced onto Windows 10, which is not as smooth to administer as Windows 7. There are so many issues with it, and the smaller ones simply cannot afford the hours to put things right.

It makes the OS look sloppy and incomplete which is a shame as Windows 7 was not like this.