Re: Remote boot server feedback
From: KM (konstmor_at_nospam_yahoo.com)
Date: 01/12/05
- Next message: YaronM: "Urgent: Do an EWF Commit under limited User session"
- Previous message: KM: "Re: How to get the User Name?"
- In reply to: Desi: "Remote boot server feedback"
- Next in thread: Desi: "Re: Remote boot server feedback"
- Reply: Desi: "Re: Remote boot server feedback"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 12 Jan 2005 11:37:34 -0800
Desi,
I thought about the same problem a while ago. Although I never had time to come up with a final solution.
Some possible solutions:
- Some BIOS allow you to modify the "boot" option to switch from LAN boot to HDD boot, etc. through CMOS posts.
If you can't find a BIOS with the option available, you always have a choice to buy a custom BIOS (like GeneralSoftware,
Phoenix, etc.)
- You can choose to run PXe client off a boot floppy (search Google for ready solutions). Then you can make it to run only once
or the number of times you need (just make sure the floppy is writtable to store your flags :-) ).
This may not be a good solution because having PXe option in BIOS is so cheep and popular now.
- From the booted XPe image you can have access to the RBS server and change the "rbsprov.ini" file (normally under Program
Files\Windows Embedded\Remote Boot Service\) and change particular client setting to start abortpxe.com boot program for it. Mostly
you don't even have to re-start the RBS service on the server.
This is really not hard to implement but obvious disadvantages: hardcoded path to a server share on your network; write access
to the rbsprov.ini from XPe clients (not really secure).
The security problem, though, could be fixed if you have access to the server share only on the XPe client boot from
Administrator account with a particular required password. Then you can change the password, clean up everything and reboot the
client.
Or you can create your own client-server application(s) to work on the server with the "rbsprov.ini" file. Then you are going
to be responsible on how you implement that client-server communication the most secure way.
- From XPE image you can have access to the DHCP server (through DHCP server API or netsh dhcp) and change some DHCP option
(e.g., 067) to break the PXe scheme for all the clients. Again, easy to implement with "netsh dhcp" but not really secure to do that
from a client so you would also want a clean-up on first boot.
- Request RBS server API documentation from Microsoft and create your own client-sever way to change the RBS settings.
--
Regards,
KM, BSquare Corp.
> All,
>
> I would like to use Remote Boot server to boot my targets to a
> lightweight image in RAM, connect to a network share, and use SDIMGR to
> write a new image to the target's CF module.
>
> What is missing is a way to let the remote boot server program know
> that the image download/write operation is completed and the "start
> program" for the device should be reset to "abortpxe.com" in remote
> boot server, so that the targets boot to their local compact flash
> drives.
>
> Has anyone come up with a creative way to do this that minimizes user
> interaction at the server?
>
> Desi
>
- Next message: YaronM: "Urgent: Do an EWF Commit under limited User session"
- Previous message: KM: "Re: How to get the User Name?"
- In reply to: Desi: "Remote boot server feedback"
- Next in thread: Desi: "Re: Remote boot server feedback"
- Reply: Desi: "Re: Remote boot server feedback"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
