While working with a client on Provisioning in LDMS 2016 we ran into something interesting. One issue we needed to overcome was the drivers for the Dell 7270’s and 7240’s. There are articles on the community about the glitches with these devices and how to find and add the correct drivers. We researched the NIC on the devices, found the correct drivers, installed them into the boot.wim file, redeployed the PXE rep then tried to capture an image. All seemed to go well. The template was kicked off on the device; it received an IP address, then the Provisioning template began to run but as soon as the capture image section of the template started; the process thought about it for a few minutes that it failed.
We looked at the log files which indicated that the process couldn’t map a drive. We went back to the template to check the account we used. We checked the public variables again verifying the account, the domain, the core name and that the passwords were correct. We double check the preferred server folders as well as the accounts used with the preferred server.
All looked good so we kicked of the Provisioning job again. All seemed to be going well just as it did the first time but then the process failed on capturing the image.
We took a step back. Maybe there was something wrong with the device we were using? Maybe there was a network issue preventing the process to map a drive? Maybe, Maybe, Maybe?
We decided to see if an image deployment template would work. We used the create image deploy template, named it, selected Image X, filled in the location of the image to be deployed, selected the agent, the unattend script and HII. Before we started the template we double checked all of the configurations.
We’re good to go. The configurations look correct, the device was added to the bare metal devices folder, and then template was stared. The Provisioning template started, the device Vbooted, the default partitions were created but when it came to deploying the image the template failed.
This was driving us nuts. What is breaking the process? We talked to another Provisioning guru. He looked over the templates, ran the templates just as we did and they failed. Now were all scratching our heads? I can’t tell you how many time we created new templates and reviewed them. Trying to find anything that would break the process.
Than we discovered the issue. The problem we found is the UNC path to the image file is case sensitive. We copied the UNC path from the image folder into the capture image template. When the validate button was pressed we noticed something had change in the command line parameters box. Looking closely at the UNC path and the information in the verify box, there were the same. We started that template and this time it captured the image and the entire Provisioning template completed successfully.
With this new information we looked at the deploy image template. We took screenshots of the template before any changes were made. We did the same with this template as we did with the capture template and something did change. Looking at the screenshots we found a letter had changed from lower case to upper case. For example when the UNC path that was copied in was \Core_serverPackagesxxx. Before the validate button was pressed the UNC path in the command line parameters was \Core_serverpackagesxxx. The “P” was lower case in the command line parameters box.
I don’t remember having to worry about upper and lower case letters in previous versions. I researched this but didn’t find specific information about case sensitivity. Another interesting note about this is we have another long time LDMS Provisioning user who ran into the case sensitive issue.