Error 53 is a standard Windows error that means the target of the drive mapping could not be resolved.
Add a hosts file to the \i386\system32\drivers\etc directory of the Windows PE provisioning image on the core (ldvpe1.img) and redeploy your PXE rep. Ensure the hosts file contains name resolution for the target of the drive mapping action.
My problem is resolved...
I change my mapping on my template (i used IP adresse and not the global variable (%corename%).
Ah yes - you want to be careful with that. The "real" NET USE doesn't work with IP addresses. It's far better using names and then hard-wiring those names via LMHOSTS :).
Yes, I know you can try this stunt in a "full" Win XP environment, but that doesn't work so well for OSD/Provisioning
LANDesk EMEA Technical Lead
NET USE * \\xxx.xxx.xxx.xxx\<sharename>
works in Windows XP environment AND in Windows PE environment (no need for a manual, never documented and fast forgotten entry in LMHOSTS, brrr).
I think, it's a "problem" of OSD/Provisioning only... :-) (In OSD deployment script the command drvmap can use ip adresses for the mapping too!)
You'll find that IP's don't work there at all - since then I got into the habit of only ever using names (that way my scripts work on whatever platform gets booted to) :p.
Get burned once too many, you start conditioning yourself ...
LANDesk EMEA Technical Lead.
You're right ,
DOS is only able to resolve netbios names (shortname resolution, no full qualified resolution possible) ...