Deployment Solution

Greetings all,

Long time lurker, first time poster. Is it me or did 6.9 SP4 change something with network drive mappings in the boot disk creator wizard (Step 6 of 12)? My drives no longer map because of it, and when I use the browse button to (Entire Network > Microsoft Windows Network > My Domain > My Deployment server > eXpress) it fills the path text box with the following "My Deployment server\eXpress:". As you might have guessed already that path is gibberish and does not work even though the boot disk wizard will accept it. Any ideas on how to work with the drive mapping changes? I know I can workaround this problem by using a script task with "net use f: \\deployment\express" but I would rather not add this to every job that will require it.

Thanks

Example screenshot attached.


- Errors on PXE client when drive mapping attempts to occur:

Establishing network connection....
Validating network connection (-169.254)
Mapping network drives...
System error 67 has occurred.

The network name cannot be found.

Why don't you just fill in the share?
\\servername\eXpress

That was what I was expecting to work since it always has in the past. This time it did not hence the orignal post.

Anyway rolled back to SP3 all is good.

SP4 did not change anything with the drive mappings. I've tested it in a VM and there is nothing going wrong.
Just fill in the textbox manually with the correct network share.
See the screenshot below

Do not browse just type it in.

I am having the same issue as Rmaes
the path is now wanting
server\volume:share
ive tried numerous variation and they dont work.
Anyone find a fix or workaround? I have tried changing the mapdrv.bat file but that hasn't worked; it keeps the bad path.
Ive found a temp fix; go to express\pxe\masterimages\<your menu option>\BDC\shared and edit the mapdrv.bat and then go back to the pxe config and recreate the image. You can verify the mapdrv.bat entry before you recreate it; the only problem is DONT click the edit button as it will force you to enter the valid path again which ISNT valid and then youll have to recreate it again! 

it wont accept the path as \\server\share
the only way to progress through the wizard it with the format in the example.

I've had issues mapping it as F: on the latest version (which we've always used in the past) and had to change it to a different drive letter (think I used S: )