MDT 2010 - Validation Error: The deployment share is read-only, so no changes can be made

I keep getting the above listed error when trying to update the rules on one of my deployment shares. I've even gone so far as to remove the read-only flag on everything in the share, it doesn't help.
As a workaround, I've been editing the CustomSettings.ini directly, but I'd really like this to work. Any ideas?
As an aside, the 'Alert me when someone responds to this post' never seems to work here. And yes, I've checked my spam folder as well...

Ok, it seems to be related to the MDT WizardEditor, but I'm not sure how. I logged on to the server and was able to update the deployment share several times. I closed the MMC, opened the WizardEditor, opened the Deploy.xml thing inside the WizardEditor, closed WizardEditor, reopened MMC - READ ONLY.
Very weird.

Similar Messages

What to do about Backup failed with error: The target volume is read-only

This is a weird story. My wife has a PowerBook G4/1.33 GHz that she uses in clamshell mode with a 20" Cinema Display. One day under OS X 10.5.6, her Time Machine backups (to a networked 500 GB Time Capsule) failed with the error: Backup failed with error: The target volume is read-only. So I upgraded her to 10.5.7 and erased the sparseimage file, starting a new Time Machine backup. And it just happened again. Any idea how this sort of problem arises? My wife was doing something at her computer when the Time Machine error occurred.
Please don't advise us to upgrade to 10.5.8, because her PowerBook freezes not infrequently with any OS later than 10.5.6, and I was just about to downgrade her from 10.5.7 to 10.5.6.

Pondini wrote:
odysseus wrote:
This is a weird story. My wife has a PowerBook G4/1.33 GHz that she uses in clamshell mode with a 20" Cinema Display. One day under OS X 10.5.6, her Time Machine backups (to a networked 500 GB Time Capsule) failed with the error: Backup failed with error: The target volume is read-only. So I upgraded her to 10.5.7 and erased the sparseimage file, starting a new Time Machine backup. And it just happened again.
Try repairing the sparse bundle, per #A5 of the Time Machine - Troubleshooting *User Tip,* also at the top of this forum.
I've tried this before, but it can't be repaired, because it can't be mounted.
Any idea how this sort of problem arises? My wife was doing something at her computer when the Time Machine error occurred.
One possibility is, the HD in the Time Capsule is beginning to fail (all HDs fail, sooner or later).
I'm backing up to my own sparseimage bundle just fine.
Please don't advise us to upgrade to 10.5.8, because her PowerBook freezes not infrequently with any OS later than 10.5.6, and I was just about to downgrade her from 10.5.7 to 10.5.6.
Those two things may be related. Whatever's going wrong may very well be what's corrupting the backups.
I'd recommend finding out what's wrong with the Powerbook. It's impossible to tell, of course, but that may be the root of the problem.
There's a problem with PowerBooks and Cinema Displays. I've posted a lot about this. Even after a motherboard replacement, my PowerBook G4/1.67 GHz had freezes, and eventually Apple gave me a MacBook Pro, but I think there's a failure involving hardware/software design.
If you haven't yet, I'd start by dong a +*Verify Disk+* on it's internal HD (also per #A5);
That checks out fine.
if there are no errors, or they're fixed and the problem continues, run the +Apple Hardware Test+ from the disc that came with the Mac. (One of the discs should have that, and instructions for running it, printed in tiny type on the label).
If still no help, I'd be inclined to do an +Archive & Install, preserving users & settings,+ of Leopard, then download & install the appropriate "combo" update. That's a combination (thus the clever name) of all the updates to Leopard since it was first released, so installing it should fix anything that's gone wrong since then, such as with one of the normal "point" updates. Info and download available at: http://support.apple.com/downloads/MacOS_X_10_5_8_ComboUpdate (change the last "8" to the desired number). Be sure to do a +Repair Permissions+ via Disk Utility (in your Applications/Utilities folder) afterwards.

"Time Machine Error The backup volume is read only"

Lately, every time I try to backup to my Time Capsule using Time Machine it fails and I get a message saying "Time Machine Error The backup volume is read only. To select a different volume, open system preferences and choose Time Machine" So I do that and I see the Time capsule listed. I don't want to select anything but the Time Capsule, cuz what else do I have, right? Am I wrong in assuming the "backup volume" is the Time Capsule? Anyway, I have tried changing the permissions on the time capsule, but when I get the "get info" box for the time capsule, there is not an option to change those settings, they are grayed out. Every thing worked well for about a week and then this started. My backup volume must have been "Read & Write" at first, because I can see what was backed up when I open Time Machine. Anybody have a clue what's going on? How can I make the back up volume "Read & Write" again and why did it change to "Read Only?"

Nope, I am using the same passwords as ever, both users have the same password, BTW. The password I gave to the Time Capsule is different, tho, but that password is for the wireless aspect of the Time Capsule, so that wouldn't have anything to do with it, would it?
I also get a message box that says "Disk Repair The disk "Backup of XXX's Computer" was not repairable by this computer, it is being made available to you with limited functionality. You must back up your data and reformat the disk as soon as possible." This box appears in conjunction with the appearance of the Norton's virus scan box scanning the time capsule.

"The selected cells are read-only" error on Custom Field when trying to insert in Datasheet mode

I have a custom field that works completely fine. Yesterday our QA team found out that when trying to insert in Datasheet format, the error "The selected cells are read-only" was thrown. Any ideas? I tried passing the following property to my fldtypes_field.xml file:
    <Field Name="ReadOnly">FALSE</Field>
No luck.Victor Palma

Unfortunately it did not work. I also developed the code and access the field and checked its property called "ReadOnlyField" which is already set to false.
Below is the xml that i am using. Can you please share the xml that you had used?
<?xml version="1.0" encoding="utf-8"?>
<FieldTypes>
  <FieldType>
   <Field Name="TypeName">MyCustomField</Field>
   <Field Name="ParentType">Text</Field>
   <Field Name="TypeDisplayName"> My Custom Field</Field>
   <Field Name="TypeShortDescription"> My Custom Field</Field>
   <Field Name="AllowBaseTypeRendering">True</Field>
   <Field Name="ReadOnlyField">False</Field>
   <Field Name="UserCreatable">TRUE</Field>
   <Field Name="ShowInListCreate">TRUE</Field>
   <Field Name="ShowInSurveyCreate">TRUE</Field>
   <Field Name="ShowInDocumentLibraryCreate">TRUE</Field>
   <Field Name="ShowInColumnTemplateCreate">TRUE</Field>
   <Field Name="FieldTypeClass">My Assembly Information goes here</Field>
  </FieldType>
</FieldTypes>

Cannot make changes to the contents of this read-only folder

I recently got a new laptop and loaded Office 2013. We have three inboxes in Outlook and are using Cox IMAP. I get the following message when I try to delete emails from the primary inbox "Cannot make changes to the contents of this read-only
folder". Emails can be deleted from the other folders with no problem.
Does anyone know what could be causing this and how to fix it?

Hi
As per the information and details provided by you, to solve the problem of Outlook inbox folder, please follow these steps: -
Step 1: - If you are unable to delete all emails from a given Outlook folder, most likely that folder is locked.
Restarting Windows should fix it.
Step 2: - If you are unable to delete only some emails, then your
Outlook data file might be corrupted.
Step 3: -
Empty your Deleted items mail folder, then try again to delete emails.
Step 4: -
Hard deletes the selected emails – While the emails are highlighted/selected, keep the
Shift key pressed and hit the Delete key.
Step 5: -
Restart Outlook in Safe Mode and try deleting the emails from there.
Step 6: -
Edit the culprit email (Actions > Edit Message), save it back and try to delete it.
I hope this information will be helpful for you.
Thanks and regards
Shweta@G

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.

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 - iaStorA.sys error when starting up, Status: 0xc0000098, multiple errors updating deployment share

I recently had rearranged our imaging by creating selection profiles for each computer model and then creating a task sequence for each model so that it looks for a model and only injects the drivers for that model. Everything had been working great
and then we got a new batch of Dell Latitude E6440's in. I checked over the machine and just wanted to make sure nothing changed so i grabbed a couple drivers off of it and uploaded them into mdt under that model. I went to update the deployment
share and started to get a whole host of Error: 2, no driver packages were found on the specified path. Verify the driver .INF file are in the specific location and try the command again. It points to the dism log and exit code is =2 then it says DISM
/Add-Driver failed, rc = 2 and lists all the drivers that had failed. It was a whole bunch for both the x86 and x64. Although i didnt add all these drivers. I only messed with the wifi and nic driver and it was only two files. I ran
through imaging and there were no issues it rebooted windows is about to start and it goes to the black screen with the iaStorA.sys message. I checked everything, i looked over all the chipset drivers i knew i imported and those were still there. I
downloaded the WINPE stuff from dell and found the driver and made sure to import everything in that folder and it skipped it as it said it was still there. I wanted to make sure it wasnt the whole mdt server so i imaged a different computer model all
together and that worked. So i deleted every driver out for this model made sure to delete it if it was in other places. I am now in the process of only including very specific drivers ie just the nic and display and audio and see if it will get
passed first bootup. But what would make it go from working every time for about 3 weeks now to all of a sudden not injecting drivers through updating the deployment share and causing a problem for just this image. I am including the dism log and
it is lengthy. The drivers are all sitting all sorted out in their respected folders on the desktop of the share. This has never been an issue before. here is the log
=== Making sure the deployment share has the latest x86 tools ===
=== Processing LiteTouchPE (x86) boot image ===
Building requested boot image profile.
Determining if any changes have been made in the boot image configuration.
No existing boot image profile found for platform x86 so a new image will be created.
Calculating hashes for requested content.
Changes have been made, boot image will be updated.
Windows PE WIM C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\en-us\winpe.wim will be used.
WIM file mounted.
Deployment Image Servicing and Management tool
Version: 6.3.9600.17029
Image Version: 6.3.9600.16384
There was a problem opening the INF file. D:\Windows7\Out-of-box Drivers\hdc\iaAHCI_8.9.8.1005_157DE4AE7437DC1A46C7E0E4B3294E513CB47D80\iaAHCI.inf Error: 0x80070002.
Error: 2
No driver packages were found on the specified path.
Verify that the driver .INF files are in the specified location and try the command again.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Exit code = 2
DISM /Add-Driver failed, rc = 2.
Injected driver Intel hdc iaAHCI.inf 8.9.8.1005 (2)
Injected driver Intel hdc ibexahci.inf 7.0.0.1013 (14)
Deployment Image Servicing and Management tool
Version: 6.3.9600.17029
Image Version: 6.3.9600.16384
There was a problem opening the INF file. D:\Windows7\Out-of-box Drivers\hdc\ibexahci_7.0.0.1013_CDE6EABDFCC22A23476F9CB4EA115D63FF4A6DBE\ibexahci.inf Error: 0x80070002.
Error: 2
No driver packages were found on the specified path.
Verify that the driver .INF files are in the specified location and try the command again.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Exit code = 2
DISM /Add-Driver failed, rc = 2.
Injected driver Intel hdc ibexahci.inf 7.0.0.1013 (15)
Injected driver Intel hdc ibexid2.inf 9.1.1.1013 (6)
Deployment Image Servicing and Management tool
Version: 6.3.9600.17029
There were about 2,000 plus more lines of the same stuff.
For future purposes where should the driver be when import them into mdt and do i need to then keep them? I am still learning all this stuff after taking over the roll in October of 2014. Any help would be greatly appreciated.

Hi KheenanHalvorson,
According to the log ,it seems that there is something missing in the driver package .
According to your description ,I assumed that you have configured the whole process correctly.
To deploy the drivers in this way the driver package should include two files an INF and SYS file .We may need to replace the driver package with another one including the INF file .
Here is a link for reference:
How to manage Out-of-Box Drivers with the use of Model Specific Driver Groups in Microsoft Deployment Toolkit 2012 Update 1
http://blogs.technet.com/b/askcore/archive/2013/05/09/how-to-manage-out-of-box-drivers-with-the-use-of-model-specific-driver-groups-in-microsoft-deployment-toolkit-2012-update-1.aspx
"One thing to note about Driver injections is that the driver must have an INF and SYS file in order for us to install the driver this way. If a driver installs via an EXE and there is no way to extract that driver to reveal the actual INF
and SYS file, then you would be forced to add that driver EXE package as an application and install it as an application. "
Best regards
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

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 - 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

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

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 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 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.

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

MDT 2010 - Validation Error: The deployment share is read-only, so no changes can be made

Similar Messages

Maybe you are looking for