So I've recently been tasked with getting an MDT/WDS server online, as we're moving from a strictly WDS environment (2008 R2) to a 2016 Server install with WDS and MDT. For the most part, things have gone well, except when it's come to capturing
an image.
The long story short, is that I have the bootstrap.ini file configured to provide the username, domain, password, and deployshare information, which has worked well for the deployment aspect of deploying a Windows 10 Pro 1809 image for testing. The issue comes, when I'm trying to CAPTURE an image. The method that I'm using to capture an image is rather traditional - sysprep the image, power down, boot to network, choose the task sequence to capture an image, and then let it go. I get no complaints through the entire process UNTIL it finishes, and reports 3 "Network Path not found" errors. No error codes - just 3 messages saying the same thing ("Network path not found"). The image, however, seems to have been deposited on the "captured" directory within the deployshare.
Upon further investigation, I was advised to look further into the BDD.log, and the part that jumped out at me, was this:
"<![LOG[DeploymentMethod = UNC]LOG]!><time="12:08:26.000+000" date="04-19-2019" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Unable to connect to share: The network path was not found.
( 0x80070035 ) , trying to connect without username. ]LOG]!><time="12:09:02.000+000" date="04-19-2019" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[The network path was not found.
]LOG]!><time="12:09:02.000+000" date="04-19-2019" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
<![LOG[Unable to connect to \\WDS\DeploymentShare$. Sleeping for 5 seconds.]LOG]!><time="12:09:02.000+000" date="04-19-2019" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Unable to connect to share: The network path was not found.
( 0x80070035 ) , trying to connect without username. ]LOG]!><time="12:09:07.000+000" date="04-19-2019" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[The network path was not found.
]LOG]!><time="12:09:07.000+000" date="04-19-2019" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
<![LOG[Unable to connect to \\WDS\DeploymentShare$. Sleeping for 10 seconds.]LOG]!><time="12:09:07.000+000" date="04-19-2019" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Unable to connect to share: The network path was not found.
( 0x80070035 ) , trying to connect without username. ]LOG]!><time="12:09:17.000+000" date="04-19-2019" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[The network path was not found.
]LOG]!><time="12:09:17.000+000" date="04-19-2019" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
<![LOG[Unable to connect to \\WDS\DeploymentShare$. Sleeping for 15 seconds.]LOG]!><time="12:09:17.000+000" date="04-19-2019" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Mapped Network UNC Path Z: = \\WDS\DeploymentShare$]LOG]!><time="12:09:32.000+000" date="04-19-2019" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Existing UNC Path Z: = \\WDS\DeploymentShare$]LOG]!><time="12:09:32.000+000" date="04-19-2019" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Successfully established connection using supplied credentials.]LOG]!><time="12:09:32.000+000" date="04-19-2019" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">"
My first thought, was that the NIC wasn't connecting to DHCP quickly enough, so I added in a command (wscript.sleep 60000) to have the script pause for a minute to give the machine time to establish a good connection, and that basically didn't have any effect.
I'm at a bit of a loss as I'm not sure what's going on. The process itself seems to complete, however, those 3 "Network Path not found" errors seems to indicate that something couldn't find the share. So, I guess I have 2 questions. 1 - Being that the process completes, how concerned should I be that the captured WIM will have issues? 2 - How can I go about troubleshooting this error so that I can actually end up with a clean summary? I'll post the entirety of the BDD.log file shortly.
Much appreciated.
The long story short, is that I have the bootstrap.ini file configured to provide the username, domain, password, and deployshare information, which has worked well for the deployment aspect of deploying a Windows 10 Pro 1809 image for testing. The issue comes, when I'm trying to CAPTURE an image. The method that I'm using to capture an image is rather traditional - sysprep the image, power down, boot to network, choose the task sequence to capture an image, and then let it go. I get no complaints through the entire process UNTIL it finishes, and reports 3 "Network Path not found" errors. No error codes - just 3 messages saying the same thing ("Network path not found"). The image, however, seems to have been deposited on the "captured" directory within the deployshare.
Upon further investigation, I was advised to look further into the BDD.log, and the part that jumped out at me, was this:
"<![LOG[DeploymentMethod = UNC]LOG]!><time="12:08:26.000+000" date="04-19-2019" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Unable to connect to share: The network path was not found.
( 0x80070035 ) , trying to connect without username. ]LOG]!><time="12:09:02.000+000" date="04-19-2019" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[The network path was not found.
]LOG]!><time="12:09:02.000+000" date="04-19-2019" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
<![LOG[Unable to connect to \\WDS\DeploymentShare$. Sleeping for 5 seconds.]LOG]!><time="12:09:02.000+000" date="04-19-2019" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Unable to connect to share: The network path was not found.
( 0x80070035 ) , trying to connect without username. ]LOG]!><time="12:09:07.000+000" date="04-19-2019" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[The network path was not found.
]LOG]!><time="12:09:07.000+000" date="04-19-2019" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
<![LOG[Unable to connect to \\WDS\DeploymentShare$. Sleeping for 10 seconds.]LOG]!><time="12:09:07.000+000" date="04-19-2019" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Unable to connect to share: The network path was not found.
( 0x80070035 ) , trying to connect without username. ]LOG]!><time="12:09:17.000+000" date="04-19-2019" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[The network path was not found.
]LOG]!><time="12:09:17.000+000" date="04-19-2019" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
<![LOG[Unable to connect to \\WDS\DeploymentShare$. Sleeping for 15 seconds.]LOG]!><time="12:09:17.000+000" date="04-19-2019" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Mapped Network UNC Path Z: = \\WDS\DeploymentShare$]LOG]!><time="12:09:32.000+000" date="04-19-2019" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Existing UNC Path Z: = \\WDS\DeploymentShare$]LOG]!><time="12:09:32.000+000" date="04-19-2019" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Successfully established connection using supplied credentials.]LOG]!><time="12:09:32.000+000" date="04-19-2019" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">"
My first thought, was that the NIC wasn't connecting to DHCP quickly enough, so I added in a command (wscript.sleep 60000) to have the script pause for a minute to give the machine time to establish a good connection, and that basically didn't have any effect.
I'm at a bit of a loss as I'm not sure what's going on. The process itself seems to complete, however, those 3 "Network Path not found" errors seems to indicate that something couldn't find the share. So, I guess I have 2 questions. 1 - Being that the process completes, how concerned should I be that the captured WIM will have issues? 2 - How can I go about troubleshooting this error so that I can actually end up with a clean summary? I'll post the entirety of the BDD.log file shortly.
Much appreciated.