In my experience, this is usually one of two things -- Rights or Name Resolution.
- Do the domain\username and password combination you are using have rights to read from the share you are mapping?
- From the WinPE, can you ping CORP14.domain.internal by name? If not, I'd say that's your issue...
The account I'm using has full administrative rights to the domain so it can't be that. I did ping the server from the client's PE Console and yes I can get to it. I also changed the path of the server to represent the IP address and it still doesn't work.
I would recommend trying the following 2 things:
1 - Try a net use command for the same share using the same un/pw combination that you use in the drvmap command and let us know the results.
2 - If it's successful, retype the password in the script to make sure it's stored correctly.
Also, are other tasks working correctly, or is this a universal problem with all your captures/deployments?
No good. I can ping, I can map the drive using net use, I have entered, re-entered and entered again the account information "Domain\username" Nothing works. Always the same error.
This is an upgraded version of LD9 from LD8.8 SP3. Is it a possibility ldrun or drvmap.exe is corrupt or not the correct version?
have you tried fqdn in your username, ie. CORP14.domain.internal\username
also you can test to see if drvmap is working or at least see if it is erroring out.
in winpe, open up a command prompt and browse to:
syntax would be:
drvmap.exe username password driveletter share
drvmap.exe CORP14.domain.internal\bigbob password1 N: \\CORP14.domain.internal\wkimages
see if that works and let us know...
Thanks for the ideas I'm out sick today so I won't be able to test at all but I should be back tomorrow.
1 of 1 people found this helpful
Not sure if this is resolved yet or not. I had the same problem after upgrading to LD9. Updating the PXE rep resolved the issue. Not sure why, but until I updated it, it would fail when mapping the drive.
Great suggestion. Perfect timing as well just got back in the office today and was planning on working on this today. Got done rebuilding the PXE reps about 10 minutes ago and am trying this now.
Oooo... pretty background... Oh hey ImageX just kicked on!
Zachry Sum had the right answer. Just had to upgrade my PXE server all was fine with the world again. Thanks!
Nicely done Zachry!
Froggmann, glad to hear you've got it going.