Jump to content

Recommended Posts

Posted (edited)

Can anybody verify that I'm using the correct driver.

 

I'm getting this error and can't seem to get it to work.

 

 

"A connection to the deployment share (*****deploymentshare$) could not be made.

The following networking device did not have a driver installed

pci\ven_10EC&DEV_8168&SUBSYS_308917AA&REV_04"

 

 

I'm I using the correct driver according to the error.

 

PCI Vendor and Device Lists

Realtek

 

8111DP DASH All-In-One installation kit for WinXP/Vista/Win7

 

I'm having a really hard time getting that driver to work.

 

 

 

I have also tried

http://support.lenovo.com/us/en/products/desktops-and-all-in-ones/thinkcentre-m-series-desktops/thinkcentre-m78?type=Tablets&c=1

 

I can't get that one to work either

 

It's on Lenovo M78 (10BSS02P00) win 7 x86

 

 

 

Thank you

Edited by denmyos
Posted
Hi denymos,

 

I replied to one of your earlier threads regarding the problem you are having with the Lenovo drivers

 

http://www.edugeek.net/forums/o-s-deployment/142101-deployment-win7-x64-run-extremly-slow-2.html

 

what media are you using to create your lite touch boot image or what boot.wim file are you using? the one from windows 7 or windows 8.1

 

I'm using Win7.

I'm just using the the boot wim that MDT creates.

\\deploymentshare\boot\litetouchPE_x86

 

I don't have access to a win8.

 

My pxeboot is not working so I'm using USBstick to boot from.

 

The weird thing about all this is:

slow deployment;

It has be running really fast the last two weeks, down to a couple of minuts for a full deployment, without apps.

Suddenly a hour ago, it went down to 1 hour to deploy the same image, I didn't change anything.!!??

I ended up reboot my MDT server, and it went back to a couple of minuts to deploy.!!??

 

 

Driver issues;

It seem like when I use the "total chaos" method it will deploy without any driver issues.

But when I use the "total control" method and put the same NIC drivers as I used in my "total chaos" in my winPE, and change the properties->driver and patches to my WinPE x86 folder,, it will fail upon booting.

 

"A connection to the deployment share (*****deploymentshare$) could not be made.

The following networking device did not have a driver installed

pci\ven_10EC&DEV_8168&SUBSYS_308917AA&REV_04

 

When I change the "properties->driver and patches" to "nothing" it will boot again and deploy without any problem.

 

It turn out that it will happend with both lenovo M78 and Dell Optiplex 7010, I still have a few other lenovo and Dell models I need to test.

Posted

What version of MDT are you using, if you're not using MDT 2013 and the newer ADK for windows 8.1 (both free downloads) it may be worthwhile downloading them and setting up on another machine than you are currently using for your MDT Server. It's possible that they will have better drivers than the boot.wim file created if you are using The windows 7 WAIK toolkit.

 

It's worth a try

 

you say that you don't have PXE boot working but you are booting from a usb stick, why is this? you do have a wds server running somewhere on your network don't you? You should be able to copy the file created on your MDT deployment share and then import it to the boot images on your wds server (you would have to copy it to a location on the WDS server as it doesn't ever seem to import from a network share in my experience).

on your network don't you? You should be able to copy the file created on your MDT deployment share and then import it to the boot images on your wds server (you would have to copy it to a location on the WDS server as it doesn't ever seem to import from a network share in my experience).

Another thing to do might be to set up a Virtual network using Virtualbox or Vmware and setup a few servers and install the WDS role on one and MDT on another. Download the evaluation versions of Server 2012R2, Windows 8.1, Windows 7 from the microsoft website (registration or a microsoft logon required) and have a play at getting the PXE boot side of WDS and MDT working as it will make life much easier than having to use a USB pen and doesn't interfere with your real network while you try things out. Obviously set the virtual network to only use the software's internal or custom networks as you don't want a DHCP or other type of server on your real network.

I'm not sure iof you've used the virtualization software before but install the guest additions cd which allows you to use shared folders with the host system. You can then download the files on your work network and share them with the virtual machines.

If you need any help just ask as i've been playing with this type of setup for a few weeks now and will have come across most of the problems you will encounter on the virtualisation side of it. Another thing to consider for the clients when you start deploying them on the virtual machines is to set the client to have two or four processors, this will speed up testing considerably.

Posted (edited)
What version of MDT are you using, if you're not using MDT 2013 and the newer ADK for windows 8.1 (both free downloads) it may be worthwhile downloading them and setting up on another machine than you are currently using for your MDT Server. It's possible that they will have better drivers than the boot.wim file created if you are using The windows 7 WAIK toolkit.

 

It's worth a try

 

you say that you don't have PXE boot working but you are booting from a usb stick, why is this? you do have a wds server running somewhere on your network don't you? You should be able to copy the file created on your MDT deployment share and then import it to the boot images on your wds server (you would have to copy it to a location on the WDS server as it doesn't ever seem to import from a network share in my experience).

 

 

 

on your network don't you? You should be able to copy the file created on your MDT deployment share and then import it to the boot images on your wds server (you would have to copy it to a location on the WDS server as it doesn't ever seem to import from a network share in my experience).

 

Another thing to do might be to set up a Virtual network using Virtualbox or Vmware and setup a few servers and install the WDS role on one and MDT on another. Download the evaluation versions of Server 2012R2, Windows 8.1, Windows 7 from the microsoft website (registration or a microsoft logon required) and have a play at getting the PXE boot side of WDS and MDT working as it will make life much easier than having to use a USB pen and doesn't interfere with your real network while you try things out. Obviously set the virtual network to only use the software's internal or custom networks as you don't want a DHCP or other type of server on your real network.

I'm not sure iof you've used the virtualization software before but install the guest additions cd which allows you to use shared folders with the host system. You can then download the files on your work network and share them with the virtual machines.

If you need any help just ask as i've been playing with this type of setup for a few weeks now and will have come across most of the problems you will encounter on the virtualisation side of it. Another thing to consider for the clients when you start deploying them on the virtual machines is to set the client to have two or four processors, this will speed up testing considerably.

 

http://www.edugeek.net/forums/o-s-deployment/139580-no-contact-pxeboot-wds.html

This is my problem with pxe.

vmware works flawlessly, but on the psysical pxeboot I get this error

TFTP.

PXE-t04: Access violation

DASH-E36: Error received from TFTP server

DASH-M0F: Exiting option ROM

 

I will look into updating my ADK.

To be honest, i'm not sure why I need ADK or WAIK.?

 

Thanks :)

Edited by denmyos
  • 7 months later...
Posted
http://www.edugeek.net/forums/o-s-deployment/139580-no-contact-pxeboot-wds.html

This is my problem with pxe.

vmware works flawlessly, but on the psysical pxeboot I get this error

TFTP.

PXE-t04: Access violation

DASH-E36: Error received from TFTP server

DASH-M0F: Exiting option ROM

 

I will look into updating my ADK.

To be honest, i'm not sure why I need ADK or WAIK.?

 

Thanks :)

 

 

I am having literally the exact same issue.

My school has the same model of lenovo and the same pxe connection error.

I was wondering if this was ever able to get resolved?

If yes, can you give me some insight into how i can address this issue.

 

Thank you so much; any help is VERY much appreciated!

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...