A connection to the deployment share could not be made - Networking device did not have a driver installed

I have a couple of HP 8200 desktops that I think might have bad nics. When I PXE boot them and start my LiteTouch, I get a Wizard error that says
A connection to the deployment share (\\mydpshare\share) could not be made. The following networking device did not have a driver installed
PCI\VEN_8086&DEV_1502&SUBSYS_1496103C&REV_04
I have that driver in MDT and it works on other HP 8200s. Looking into the Wpeinit.log, it looks like the driver loads but maybe the nic is bad:
Installing device root\kdnic X:\WINDOWS\INF\kdnic.inf succeeded
Installing device pci\ven_8086&dev_1502 X:\WINDOWS\INF\net1ic64.inf succeeded
Spent 16903ms installing network drivers
QueryAdapterStatus: no adapters found
Spent 0ms confirming network initialization; status 0x80004005
WaitForNetworkToInitialize failed; ignoring error
Has anyone seen this before?
Orange County District Attorney

Hi,
According to your description, it should be Intel NIC driver problem. I have checked HP official website, there is new NIC driver released, please access to the link below to download the NIC driver for test:
http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdDetails/?sp4ts.oid=5037932&spf_p.tpst=swdMain&spf_p.prp_swdMain=wsrp-navigationalState%3Didx%253D2%257CswItem%253Dvc_111651_1%257CswEnvOID%253D4060%257CitemLocale%253D%257CswLang%253D%257Cmode%253D4%257Caction%253DdriverDocument&javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken
Roger Lu
TechNet Community Support

Similar Messages

A Connection to the deployment share could not be made....

Hi,
I know this question has been posted a fair number of times on the forums but so far none of the responses have fixed my issue.
I am having trouble connecting to the deployment share receiving the error message below.
"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_10EC&DEV_8168&SUBSYS_00041179&REV_10"
I have downloaded the correct network drivers and even installed Windows 7 manually and added
the drivers to check they are correct drivers.
I have added them to the OOB drivers in the deployment share and then updated and also regenerated
the deployment share. Then i have updated the .wim file in the boot images folder but yet i still cannot get past this stage.
Does anyone have any further ideas that i could try?
Thanks,
Adam

Hi,
I can exit to cmd and attempt ipconfig/ping etc. but get confirmation that there is no IP.
The imaging process is working for older versions of laptops and Netbooks but not for the newer models. They are all Toshiba models.
[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
_SMSTSORGNAME=(*****)
OSInstall=YES
SkipAdminPassword=YES
SkipApplications=YES
SkipAppsOnUpgrade=YES
SkipBDDWelcome=YES
SkipBitLocker=YES
SkipCapture=YES
SkipComputerName=NO
SkipComputerBackup=YES
SkipDeploymentType=YES
DeploymentType=NEWCOMPUTER
SkipDomainMembership=YES
JoinDomain=(*****)
DomainAdmin=Build
DomainAdminDomain=(*****)
DomainAdminPassword=(*****)
SkipFinalSummary=YES
SkipLocaleSelection=YES
KeyboardLocale=en-GB
UserLocale=en-GB
UILanguage=en-GB
SkipPackageDisplay=YES
SkipProductKey=YES
SkipSummary=YES
SkipTaskSequence=NO
SkipTimeZone=YES
TimeZoneName=GMT Standard Time
skipUserData=Yes
FinishAction=LOGOFF
I have removed some of the information of the organisation with (*****)
Thanks,
Adam

Connection to the deployment share could not be made (network driver not installed)

Hi guys! i bought the new laptop Dell Latitude E6510 and try to install the enterprise image but i got the error:
"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_10EA&SUBSYS_040B1028&REV_05."
I look on internet and i found out that it is the intel network card driver missing. So i get the driver from Dell website and i added this drivers in the MDT console.
Then i have updated the deployment share to rebuild the boot images. Everything went fine but i always get this error.
Am I missing something ?

I too was having the problem...
the single thing that I was forgetting is that while I was recreating & regenerating the images in the deployment workbench. I wasn't burning & booting from a CD...
because (aha) I'm clever & using Windows deployment services to boot across the network & save all that time burning CDs etc.
Doh, I didn't update the WIM that WDS was using...
Open your windows deployment services console,
expand out servers : <server name> : boot images
Right click your boot image (I have 2, one for x86 & one for x64),
choose "replace image" then navigate to your newly regenerated WIM images
(probably C:\deployment_share\boot) & choose the appropriate WIM file.
do this for any images you have, reboot your client machine & BAM, deployment goodness.
MS should really add a module for PXE boot (etc) into the deployment workbench rather than have 2x deployment solutions & use the deployment module from one & the boot module from the other.
Anyhoo, works now, must make a mental note to remember this in future...
Cheers Toolman
Thank you for this. This resolved the issue that I had.

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

hi,
i have deployment windows 7 by MDT，and there is something wrong with the test. i have a MDT Service and 2 clients that one is updated and another is used to capture the image.but when i captured the image,there is error."a connection to the deployment
share could not be made. connection ok"

i create and capture the image from a physical
machine,and i create the network drivers on the MDT console. And it will generate the winPE.When i capture
and restart the machine, it will get the error.

When deploy: Wizard error a connection to the deployment share could not be made "check physical connection"

Hello everybody,
yet another issue with deploying a masterdisk. I will give you a short explanation of the situation.
I need to deploy Windows 8.1 PRO x86.
Using: Microsoft Deployment Workbench Microsoft Version: 6.2.5019.0
1. Reference PC: Windows 8.1 PRO x86 is installed on ORACLE Virtual Box.
2. I installed MDT on my workstation Windows 7 x64, where "C:\DeploymentShare\Windows8" is located.
3. To change the Unattended.xml file, I have second ORACLE Virtual Box with
Windows 8.1 PRO x86 with MDT, which connected to the DeploymentShare of Windows 7 x64.
- The reason is because the Reference PC is x86 and the Unattended.xml file can be changed only if MDT is installed on x86 Windows, otherwise it is not possible.
The image capture is successful.
Then I create bootable USB device using rufus-1.4.12.exe. I use: C:\DeploymentShare\Windows8\Boot\LiteTouchPE_x86.iso
I use a real PC (not virtual machine) and when the deployment starts
I see:
1 Welcome screen, where I select: Run the deployment wizard to install a new operating system.
2. The next screen is an error screen where I see the error:
"Wizard error
A connection to the deployment share (\\ComputerName\C\DeployemntShare )could not be made
DHCP Lease was not obtained for any Networking devices!
Possible cause: Check physical connection
I am relatively new with MDT.
Any suggestions are more than welcome.

Nick,
Thank you for the answer!
Yesterday, I figured out that I need to create an offline bootable disk.
The issue is caused, because creating a bootable disk with rufus.exe include only the ISO file and not the WIM file. That is the reason why during OS installation process it asks me for the shared folder...

MDT 2013 - A Connection to the deployment share could not be made - DHCP Lease was not obtained

First, let me give you some context:
Framework: MDT 2013 with MS SDK 7.1
Task Sequence: Standard Client TS with sysprep and capture.
Target workstation (build workstation): VM Guest on ESX 5.5 host, 8 vCPU, 8GB RAM, LSI Logic SAS Controller, E1000 NIC, SSD DAS
Behavior: The VM loads and installs the OS fine in PE, VM boots into OS successfully and resumes the TS, after the first system reboot, the error message occurs and it reads:
A connection to the deployment share (\\*********\DeploymentShare$) could not be made. DHCP Lease was not obtained for any Networking device! Possible Cause: Check physical connection. Retry:...... Cancel:.....
While observing this error, I didn't notice the NIC hadn't completely initialized and obtained an IP yet (network adapter icon in systray), additionally hitting retry after the NIC was initialized resumed the TS.
This behavior reoccurs with several subsequent reboots until a few more applications (Citrix Receiver, VMware Tools) with services are installed which seem to then slow the system boot-up time and then allows the TS to start after the NIC has initialized.
From several posts I've read on this forum, this particular behavior was alleviated by a "wait for IP lease" mechanism built into the TS engine which was introduced in MDT 2010 SP1, I wasn't able to find any other confirmation whether
this mechanism is still in effect with MDT 2013. Another point worth mentioning from several other posts I was able to find is that this behavior appears to manifested itself on target workstations with SSDs, which would somewhat explain the faster
TS load time vs waiting for an IP lease. I've also tried to replicate this behavior in a non-SSD and low-performance VM environment and I wasn't able to replicate it.
My question: Does anyone else have experienced this behavior with MDT 2013 and if so, how did you resolve it? Or is this a bug?

I have this issue intermittently as well. For us, it coincided with the deployment of IP phones, which meant PoE switches all around. However, the problem persisted even after we turned off PoE to the ethernet ports from which we normally PXE
boot.
As this issue has been intermittent, I've backburnered it. When it does happen, I just wait for the lease to arrive then rerun the wizard.
Thanks for the feedback, that's true the TS can be resumed manually once the lease has occured but it defeats the purpose of an automated TS if I have to keep an eye on it and intervene if I need to.
The network guys here recommended putting wireshark or network monitor on it and figuring out just what the heck is going on. Basically, what Keith Garner said. They also disabled PortFast awhile back to see if that made any difference, and it did
not.

Connection to the deployment share could not be made (DFS share, works fine on site A, not on Site B)

I'm trying to isolate this problem with MDT..., unable to find a solution matching this error.
We have two sites, with a DFS replica between the servers, which works fine.
Server A: Windows 2012 R2 standard
Windows Automated Installation Kit for Windows 7
MDT 2012, Update 1
WDS configured for PXE boot
Distributed File Share
Server B: Windows 2008 R2 Standard
MDT 2012, Update 1
WDS configured for PXE boot
Distributed File Share
The local path on both servers is on E:\DFS-Deploymentshare
The DFS path is \\domain.com\it\deploymentshare
When deploying on Site A, the deployment run smooth without problems.
When deploying on Site B, the deployment fails to create connection to the share.
A connection to the deployment share (\\domain.com\it\deploymentshare) could not be made.
Connection OK. Possible cause: invalid credentials.
Pressing F8, to reach a command prompt. "ipconfig" shows an IP-address. I can PING the deployment server. I can mount the Deployment share using "net use" and providing the username/password added in the bootstrap.ini and "retry"
in the message box and the deployment continues.
In the BDD log i get this timeout:
<![LOG[Unable to connect to \\domain.com\it\deplomentshare. Sleeping for 5 seconds.
<![LOG[<Message containinng password has been suppressed>
<![LOG[Access is denied.
However everything is the same both in site A and B so this seems very strange!
The complete system has worked this way before.
Bootstrap.ini contains:
DeployRoot=\\domain.com\it\deploymentshare
UserDomain="domain"
UserID="mdt-account"
UserPassword="password"
I've been trying all I can think of, but Im still faced with this error and to keep in mind the same share working on another site.

Ok, so by the sounds of it, there is something wrong with the share permissions (especially if your account works fine but the MDTserviceaccount does not work even when part of Domain Admins).
So you need to do the following:
Start in Site A:
Boot into WinPE on a workstation in site A
Ping server-a
Ping server-b
Run "net use * \\server-a\deploymentshare$ /user:DOMAIN\MDTserviceaccount"
Type in the password for MDTserviceaccount when prompted
Browse to the newly mapped drive and list the files/folders
Make sure you can see the relevant MDT folders, like Applications, Out-of-Box Drivers, etc
If all that works, then you can move to site B
Start in Site B:
Boot into WinPE on a workstation in site B
Ping server-a
Ping server-b
Run "net use * \\server-b\deploymentshare$ /user:DOMAIN\MDTserviceaccount"
Type in the password for MDTserviceaccount when prompted
Browse to the newly mapped drive and list the files/folders
Make sure you can see the relevant MDT folders, like Applications, Out-of-Box Drivers, etc
By going through all of the above, you should be able to see where the problem lies.
If all of the above works with no problems, then you have the details incorrectly specified in the BootStrap.ini (or possibly CustomSettings.ini). Confirm that you have the following specified in the relevant ini file:
DeployRoot
UserID
UserDomain
UserPassword
You can have a look in the help file if you need to confirm that these properties are configured correctly. Look under
Toolkit Reference - Properties - Property Definition in the help file.
Both Site A and Site B is successfully
I have changed the Password of deployuser to test if it is correct. and i have copy/pasted the password into the DC when changing the password.
I have tested the password by logging on to a client-pc with the deployuser as username and the temp password "Pa$$w0rd" successfully.
Both UserID, UserDomain and UserPassword is entered after the help file for Property Definition.
Please see the Bootstrap.ini and Customsettings.ini (NB! Servernames, Domainname and Passwords are fictive.)
http://1drv.ms/1tGDlUt

Surface Pro 2 "A connection to the deployment share could not be made. No networking Devices were found on this machine!"

I'm trying to deploy a windows 8.1 64bit image to a Microsoft Surface Pro 2 using WDS. I am able to pxe boot the device but as soon as I click "Run the deployment wizard to install a new operating system" it comes up with the error stated above.
I have added the whole Surface driver pack into my deployment share. I'm wondering what I can do to try to get past this error.

Hi,
It is critical that the driver for the USB Ethernet Adapter is included in the boot image. When managing Windows PE drivers it recommended that you create an MDT selection profile that includes only the drivers required for Windows PE to connect to the network
and mass storage devices.
Do this then update the boot image in WDS
/ Yannick Plavonil
blog: Deploiement Windows
twitter: @yplavonil
facebook:
www.facebook.com/deploiementwindows

A connection to the deployment share could not be made. DHCP Lease was not obtained

I am having the issue which the task sequence is coming back with the error described above. It is a timing issue because I have a network connection. It takes about 10 seconds for my system to get an IP address. Once it has an IP, I can click retry and
it proceeds with no issues. How can I delay the wizard from trying to connect the instant it is logged back in? Thanks

Have you tried something like this?
http://blogs.technet.com/b/deploymentguys/archive/2009/09/23/making-winpe-wait-for-network-in-lti-deployments.aspx
-Nick O.

Network device did not have a driver installed pci\ven_10ec&dev_8168&subsys 1992103C&REV_0C

Hi: The only suggestion I can offer would be to try the driver directly from Realtek. Second driver on the list. http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false

Hello All, I have installed WDS/MDT2010 to deploying the Windows & operating system, it works with for most of my HP laptops models. When I deploy in ProBook 645 G1 it gives me foloowing error. A connection to the Deployment share could not be made.
The following network device did not have a driver installed pci\ven_10ec&dev_8168&subsys 1992103C&REV_0C
Retry : Try again to connect to the deployment share or give up. I have download all the network driver available for this model and imported them in out of box driver,update the deployment share and run again but still having the same issue. Appreciate if any one can help me on this. Thanks

Unable to launch Litetouch.vbs (LiteTouch.wsf) from UNC path - A connection to the Deploayment Share Could not be made

I am having a difficult time figuring out this issue. Here is the back story. The particular deployment share is not used in the traditional sense of deploying OS images. Instead, it is only used in deploying applications. I actually have three shares that
do this catered to three different clientele groups; IT, teachers and students.
I have these shares set up so that the Litetouch.vbs is used as a login script and tied to specific AD accounts. When launched, it goes through the normal MDT gathering process and eventually shows a list of applications to select to install.
And this has and still is working perfectly for several years with both wired and wireless computers, until recently.
My issue, I'm afraid, is with the new Intel Dual Band 7260 wireless cards/drivers (both N7260 and AC7260. The reason I suspect this is because any other desktop or laptop will launch the VBScript just fine and bring up the list of software like it has always
done. However, if I UNC to the share and try to manually run LiteTouch.vbs, I get the "A connection to the deployment share cannot be made. Connection OK. Possible cause: Invalid credentials." That's right. I can UNC to the shares all day long, but
when launching the LiteTouch.vbs or LiteTouch.wsf scripts, I always get the above error. So the wireless is working, in a way. Just not the way I need it to. I've tried different versions of drivers all with the same error. I've launched other VBScripts that
I've wrote from UNC paths and they run fine.
I am using a Domain Admin account to connect back to the deployment share through MDT. My account is a domain admin account. The share permissions are full control for Everyone and Domain Admins. The folder permissions are Read Only for Everyone and Full
Control for Domain Admins. Like I stated, this works fine on any other system.
When I look at the BDD.log file, sometimes I don't see anything, but most of the time I see the line "No physical adapters present. Cannot deploy over wireless." Which, in my case, is not true because I can use any other laptop with older
Intel wireless cards, Broadcom, Atheros or whatever and it works perfectly. And, if I hardwire the offending laptops and use Ethernet instead of wireless, I can launch the VBScript and proceed just fine.
I guess my question is, is there a way to force MDT to use any network connection, whether it's wired or wireless to deploy anything. In my case, it would be software.
We use this option as a way for students in our high schools to be able to log in with a special account and install specific software they may need for a class. It is easier to have them do it this way than to try and install different software for
different classes on a total of 4000 laptops.
I am currently running Windows Server 2012 R2 with MDT 2013. The laptops are running Windows 7 SP1 x64 Enterprise and Windows 8.1.1 Enterprise.
Any help or ideas anyone has to offer would be greatly appreciated.
~Mike

I understand that you got MDT to work on other adapters, and I understand that some people dislike the AC series.
However...
I must strongly disagree with your conclusion:
the Intel 7260 cards just will not work for this scenario. Any other wireless card works
perfectly fine...
As designed, MDT is coded to block Wireless deployment scenarios. However, the algorithm used to determine if a network adapter is wired vs wireless is highly flawed, it will check the description (caption) of the network adapter and search for the string:
"Wireless". And if I recall, it is difficult to determine Wireless vs Wired within a VBSCript.
Set colAdapters = objWMI.ExecQuery("select * from win32_NetworkAdapterconfiguration where IPEnabled = True")
For Each oAdapter in colAdapters
If Instr(UCase(oAdapter.Caption),"WIRELESS") = 0 Then
If oAdapter.IPConnectionMetric < sIPConnectionMetric Or sIPConnectionMetric = "" Then
sIPConnectionMetric = oAdapter.IPConnectionMetric
End If
End IF
If Instr(UCase(oAdapter.Caption),"WIRELESS") Then
sWirelessConnectionMetric = oAdapter.IPConnectionMetric
End If
Next
If sIPConnectionMetric = "" Then
oLogging.CreateEntry "No physical adapters present, cannot deploy over wireless", LogTypeError
ValidatenetworkConnectivity = Failure
Exit Function
End IF
On my Lenovo W530, for example, when I disable my Wired connection, my wireless adapter reports:
PS C:\> gwmi -query "select * from win32_NetworkAdapterconfiguration where IPEnabled = true" | select-object Caption
Caption
[00000002] Intel(R) Centrino(R) Ultimate-N 6300 AGN
AS you can see, no "Wireless" in the caption string. A connection to the deployment share works just fine.
Therefore...
Yes, you *may* have gotten the installation to work on the machines that *just happen* to not have "wireless" in the caption, but I would not count on this to be true on all machines in a corporate environment.
-k
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

A connection to the deployment share issue MDT2010

I am getting the following error, when the pc reboots, during any of the following: applying pre-application updates, installing applications, applying post-application updates on our Lenovo M73 Windows 7 desktop computers. It doesn't happen
on the Dell OptiPlex desktops or Lenovo/Dell Laptops.
The error is "A connection to the deployment share (\\server.xxx.local\DeploymentShare$) could not be made. DHCP Lease was not obtained for any Networking device! Possible Cause: Check physical
connection.
If I click on retry the task sequence carries on as normal but the error can happen again when the pc reboots next. I have tried changing the server name for the IP address and also just used the server name. The pc is on the network
correctly as I can get the IP address via IPConfig and it shows that it has a current lease as well. If I look in device manager the network card is installed correctly and there are no devices not found.
Here is the end of the BDD log:
<![LOG[Property InstalledUpdates167 is now = 9655393d-1b46-46a2-ac21-c4d1b5e960d1]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="ZTIWindowsUpdate" context="" type="1" thread=""
file="ZTIWindowsUpdate">
<![LOG[Property InstalledUpdates168 is now = 884c7884-5970-4fd5-8afb-f52a0bd8204f]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="ZTIWindowsUpdate" context="" type="1" thread=""
file="ZTIWindowsUpdate">
<![LOG[More to install, Please reboot and run again!]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[Property SMSTSRetryRequested is now = true]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[Property SMSTSRebootRequested is now = true]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[ZTIWindowsUpdate processing completed successfully.]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[Command completed, return code = -2147021886]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property LTIDirty is now = FALSE]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[If there is a drive letter defined, make sure we clear it now so we can *force* recalcutation.]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread=""
file="LiteTouch">
<![LOG[Property OSDTargetDriveCache is now = DIRTY]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[LTI initiating task sequence-requested reboot.]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\LiteTouch.lnk" already exists.]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="LiteTouch" context="" type="1"
thread="" file="LiteTouch">
<![LOG[Property BootPE is now = ]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Microsoft Deployment Toolkit version: 6.1.2373.0]LOG]!><time="16:50:06.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ZTIUtility!GetAllFixedDrives (False)]LOG]!><time="16:50:06.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDisk :
<time="16:50:06.000+000">\\pcnumber\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="16:50:06.000+000" date="02-28-2014" component="LiteTouch" context=""
type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition :
\\pcnumber\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"
<time="16:50:06.000+000">\\pcnumber\root\cimv2:Win32_LogicalDisk.DeviceID="C:"]LOG]!><time="16:50:06.000+000" date="02-28-2014"
component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDisk :
<time="16:50:06.000+000">\\pcnumber\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="16:50:06.000+000" date="02-28-2014" component="LiteTouch" context=""
type="1" thread="" file="LiteTouch">
<![LOG[ZTIUtility!GetAllFixedDrives =   C:]LOG]!><time="16:50:07.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found existing task sequence state information in C:\_SMSTaskSequence, will continue]LOG]!><time="16:50:07.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread=""
file="LiteTouch">
<![LOG[Not running within WinPE.]LOG]!><time="16:50:07.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeploymentMethod = UNC]LOG]!><time="16:50:07.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Validating connection to
\\server.xxx.local\DeploymentShare$.
DHCP Lease was not obtained for any Networking device! Possible Cause: Check physical connection.]LOG]!><time="16:50:07.000+000" date="02-28-2014" component="LiteTouch" context="" type="3" thread=""
file="LiteTouch">
Any advice would be appreciated as we are going to have a large quantity of these to roll out.
Many Thanks
James

I am getting the following error, when the pc reboots, during any of the following: applying pre-application updates, installing applications, applying post-application updates on our Lenovo M73 Windows 7 desktop computers. It doesn't happen
on the Dell OptiPlex desktops or Lenovo/Dell Laptops.
The error is "A connection to the deployment share (\\server.xxx.local\DeploymentShare$) could not be made. DHCP Lease was not obtained for any Networking device! Possible Cause: Check physical
connection.
If I click on retry the task sequence carries on as normal but the error can happen again when the pc reboots next. I have tried changing the server name for the IP address and also just used the server name. The pc is on the network
correctly as I can get the IP address via IPConfig and it shows that it has a current lease as well. If I look in device manager the network card is installed correctly and there are no devices not found.
Here is the end of the BDD log:
<![LOG[Property InstalledUpdates167 is now = 9655393d-1b46-46a2-ac21-c4d1b5e960d1]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[Property InstalledUpdates168 is now = 884c7884-5970-4fd5-8afb-f52a0bd8204f]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[More to install, Please reboot and run again!]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[Property SMSTSRetryRequested is now = true]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[Property SMSTSRebootRequested is now = true]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[ZTIWindowsUpdate processing completed successfully.]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[Command completed, return code = -2147021886]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property LTIDirty is now = FALSE]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[If there is a drive letter defined, make sure we clear it now so we can *force* recalcutation.]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property OSDTargetDriveCache is now = DIRTY]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[LTI initiating task sequence-requested reboot.]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\LiteTouch.lnk" already exists.]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property BootPE is now = ]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Microsoft Deployment Toolkit version: 6.1.2373.0]LOG]!><time="16:50:06.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ZTIUtility!GetAllFixedDrives (False)]LOG]!><time="16:50:06.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDisk :
<time="16:50:06.000+000">\\pcnumber\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="16:50:06.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition :
\\pcnumber\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"
<time="16:50:06.000+000">\\pcnumber\root\cimv2:Win32_LogicalDisk.DeviceID="C:"]LOG]!><time="16:50:06.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread=""
file="LiteTouch">
<![LOG[New ZTIDisk :
<time="16:50:06.000+000">\\pcnumber\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="16:50:06.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ZTIUtility!GetAllFixedDrives =   C:]LOG]!><time="16:50:07.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found existing task sequence state information in C:\_SMSTaskSequence, will continue]LOG]!><time="16:50:07.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Not running within WinPE.]LOG]!><time="16:50:07.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeploymentMethod = UNC]LOG]!><time="16:50:07.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Validating connection to
\\server.xxx.local\DeploymentShare$.
DHCP Lease was not obtained for any Networking device! Possible Cause: Check physical connection.]LOG]!><time="16:50:07.000+000" date="02-28-2014" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
Any advice would be appreciated as we are going to have a large quantity of these to roll out.
Many Thanks
James
On the problem desktop do you have a vaild IP?

A connection to the deployment share cannot be made

i am trying to update a PC from XP to windows 7 with MDT2012.
i have import the OS in the workbench,and created a task sequence,then i update the deployment share.On the XP machine I have started the LiteTouch.vbs script.After it capture the user profile,and restart the machine.The problem start.It printde "A
connection to the deployment share cannot be made".

WHen in WinPE, you can press F8 to get a command prompt. You should then go through the usual steps to debug the bad network connection, ipconfig /all, ping GZZJOPC998, net use * \\GZZJOPC998\DeploymentShare$ .
Chances are that WinPE does *not* have the latest and greatest drivers for your device. check the x:\windows\system32\wpeinit.log to verify that the OS found the driver and installed it. If not, find the driver from your OEM/IHV, and import into MDT. Don't
forget to update the deployment share when done.
Keith Garner - keithga.wordpress.com

Windows VPN: Error 720 - A connection to the remote computer could not be established

Dear all
I have a windows7 Laptop 64bit Dell 1340.
I was working with a UMTS card, was connected with a VPN to a windows 2003 server over PPTP and experienced a bluescreen. After this, I have the following errors when connecting to the VPN:
"Registering your computer on the network... Error 720: A connection to the remote computer could not be established. You might need to change the network settings for this connection"
and in the event view I receive the following:
EventID: 1, Source RasSstp
CoId={A3478DFD-FFA4-4E8F-9DA3-CE829BDA777B}:The initial Secure Socket Tunneling Protocol request could not be successfully sent to the server. This can be due to network connectivity issues or certificate (trust) issues. The detailed error message is provided below. Correct the problem and try again.
I tried to use the Rarepair.exe tool but it looks to work only on windows xp. I deleted the IP and TCP settings without any luck.
I run a registry cleaner as well with out any luck.
Your help will be greatly appreciated!
Marc

Hi,
Since it worked previously, a quick solution is to run System Restore and get back to the previous status when the issue didn’t occur.
If system restore doesn’t help, please also try the following:
1. Check if you can establish the VPN via other connections except the connection through the UMTS card.
2. Reset the PPTP and L2TP WAN miniport with running the following commands one by one in an elevated command prompt:
Netcfg -u MS_L2TP
Netcfg -u MS_PPTP
Netcfg -l %windir%\inf\netrast.inf -c p -i MS_PPTP
Netcfg -l %windir%\inf\netrast.inf -c p -i MS_L2TP
Then reboot the computer and see how it works.
Meanwhile, I would like to share the following with you for your reference:
Troubleshooting common VPN related errors
Hope this helps. Thanks.
Nicholas Li - MSFT

BB Torch - bluetooth tethering for laptop internet use: "Error 720: A connection to the remote computer could not be established

Trying to set up Blackberry Torch for laptop tethering...bluetooth. I have connection/drivers/etc. but keep getting error message: "Error 720: A connection to the remote computer could not be established. You might need to change the network settings for this connection." Where and what do I chancge setting to so this will work?
I have synched my phone and laptop wirelessly across other internet connection....just cant get this above to work. Anybody know how to fix this? Thanks!

Hi,
Since it worked previously, a quick solution is to run System Restore and get back to the previous status when the issue didn’t occur.
If system restore doesn’t help, please also try the following:
1. Check if you can establish the VPN via other connections except the connection through the UMTS card.
2. Reset the PPTP and L2TP WAN miniport with running the following commands one by one in an elevated command prompt:
Netcfg -u MS_L2TP
Netcfg -u MS_PPTP
Netcfg -l %windir%\inf\netrast.inf -c p -i MS_PPTP
Netcfg -l %windir%\inf\netrast.inf -c p -i MS_L2TP
Then reboot the computer and see how it works.
Meanwhile, I would like to share the following with you for your reference:
Troubleshooting common VPN related errors
Hope this helps. Thanks.
Nicholas Li - MSFT

A connection to the deployment share could not be made - Networking device did not have a driver installed

Similar Messages

Maybe you are looking for