Thanks to all who have contributed to this thread.
I've visited the links above (which I read) before my very 1st post (I did not know then about the bug thread). Please note one of my first responses (3rd post from the top):
Thanks for this pointer
You do not necessarily need FOG as you can also serve images from your SME Server using this contrive: http://wiki.contribs.org/Tftp_server
I'm looking through the threads on this - very interesting. This contrib promotes a one stop shop, which can be ideal.
I've not yet read how to provide a xp image to a pxe client, though. I assume this is feasible?
My attempts to mail Trevor Batley failed. I wanted to ask him: "Serving" an image via his contrib means
a) booting and running a workstation (which may not even have a hard drive) over the network,
or
b) sending a complete image to a fat client
or both.
The Thinclient usage page doesn't explicitly say an image (windows or *nux) can be
multicasted to one or more pxeclients, I decided the FOG option was the way to go, however it overwrites several config files on installation - unsuitable on sme (surely).
The following Wikipedia definition of "thinclient" is how I understand it:
A thin client (sometimes also called a lean or slim client) is a client computer or client software in client-server architecture networks which depends primarily on the central server for processing activities, and mainly focuses on conveying input and output between the user and the remote server. In contrast, a thick or fat client does as much processing as possible and passes only data for communications and storage to the server.
I wrongly assumed my original question was clear enough:
We need to
multicast an image (initially) xp-pro, to many pc's as one might do using proprietary Ghost software from Symantec.
25 Replies
8320 Views