This may be my first post, but i must admit that this forum ahs already helpded me out so much already, so a BIG thank you to start with!
My task at hand is to provide the ability to 're-image' a remote device ad-hoc, when the windows OS becomes corrupt (happens fairly often!).
I have created a Winpe3.0 boot.wim, which i have been able to inject all my NIC drivers and the Script packages so when our device does PXE boot via TFTPD32 it discovers its own IP address, maps a drive to a local computer (where the image will be stored) and loads VNC. This all works perfectly, and i am in the stage of a live trial now.
The issue i have now is that the people that will be using this tool will be doing so via a simple interface (simple DOS menu structure ATM). This DOS structure will prompt the analyst what machine they are trying to PXE boot and guide them along the way.
The final stumbling point i have got to now is changing the TFTpd32.ini file (or registry entry) to reflect the local network IP structure. This is key especially for VNC for i need to ensure the WinPE environment knows where the local default gateway is, so the analyst can VNC in a reimage (if needed). The server machine that will run the TFTpd32 on the local machine will have a local IP address, this allows me to write a script that can assertain variables to set the IPPool and Default gateway.
I saw the post reply for 'NetFanTom' here http://reboot.pro/15...__fromsearch__1 saying;
tftpd32 coded the ip number:
192.168.0.1 = 1 * 256 ^ 3 +0 * 256 ^ 2 +168 * 256 ^ 1 +192 = 16820460
255.255.255.0 = 0 * 256 ^ 3 +255 * 256 ^ 2 +255 * 256 ^ 1 +255 = 16777215
It could be my poor Math skills, but this didn't add up for me? Also i am failing to see how i would be able to script this update?
Has anyone had a simlar situation to mine? Anyone got any ideas how i can move forward?
Many thanks indeed!