we've done this. We've a lot of sites which are connected to different core's. All the sites use the same PE image.
In your PE image you've to change the entry in your all.reg file (or create your own). In this file the core servername is stored.
What we do:
add a line "call GetOurCoreServerName.cmd" in startnet.cmd
... :nofix factory -winpe call GetOurCoreServerName.cmd reg import all.reg \ldclient\wait4ip /t 180 ...
In the batch GetOurCoreServerName.cmd you must check in which VLAN (on which site) your client resides.(ping -n 1 YourPXEServer.yoursite.com) (hopefully you've a explicit attribute in your VLAN)
Extract the name of this PXE server, and check the name against a (manually created) list of dependencies...
List of dependencies:
pxe server name1; core server name1
pxe server name2; core server name1
pxe server name3; core server name1
pxe server name4; core server name2
pxe server name5; core server name3
pxe server name6; core server name3
. . .
The prerequisite is a common share on every site (I don't know how it is possible in VLAN's).
We've many VLAN's on every site, but we use one PXE server per site! It is a setting on the DHCP server (don't ask me which.. :-) )
This doesn't answer your question as well, but we use one PXE Rep for multiple vlan's by taking advantage of the DHCP options in Microsoft Windows Server 2003/2008:
Thank you for the link Dan.
In our environment it was done by our DNS/DHCP/Network guys centrally...
You can use this as replacement for your hardcoded server:
REMEXEC22=drvmap.exe user 1084E90896AB83A0CA51C202F67 I: \\%Computer - LANDesk Management - PXE Holding Queue - Proxy Host Name%\image
When PXE booting the LANDesk Inventory contains a field representing the PXE Rep it is booting from. You can use that to point to the shares on that same PXE Rep.
Be aware though, that you can use this script only for PXE boot. If you want to push an OSD script to a PC that is on, it won't PXE boot but store the bootfiles on c: so it won't have a record indicating PXE Representative. If you want to deploy OSD also in this way, you need 2 scripts: 1 for PXE boot and 1 for Vboot.
Thanks for your answer, this seems a suitable solution. In the meantime we found another solution. I wrote an vbscript that that determines the location of the PXE representative server based on the 3th octet of the ip address. There is just one PXE representative \ Software Distribution server per VLAN so it will map the drive to that (local) server. The rest of the OSD script will continue based on the drive letters.
We will test this your solution later on and communicate the results.
Thanks all guys for the input, this is much appreciated