Oh my my my... I just joined this forum a couple days ago and I could spend weeks answering questions on this forum explaining how I have gotten around the shortcomings of the consoles inadequacies and the fact that i have asked for many many of these features reqpeatedly in product updates but have given up because Symantec turns a deaf ear.
Bottom line YES YOU CAN spawn ghostcast servers to different machines from the console. It requires replacing the ghostsrv executeable on the console server with a custom one (such as one I wrote). The command line arguments passed to it tell it what server to remotely spawn the ghostcast session on and it does so. Some prerequisites involve having the image file in place already on the remote machine.
If you want to PXE boot I wrote something up yesterday in a different thread for someone wanting to keep a statically running ghostcast session. I use them daily with PXE boots. SRVANY.EXE will allow you to spawn a ghostcast session with a static name that your PXE boot can referance and its always available unless in use. I actually trap the error thrown if the session is in use if another machine is netbooted after the sessions starts, sleep for a few minutes and then retry to join again over and over until it does.
Ghost could be such a better product if they actually listenend to the customer. Having spent the time I have talking to development people and tech support people I can see why it is lacking.
SO.. for the love of god symantec, stop requiring WINS when the console and clients are in a different subnet. You pass the {Editted for Content} console server name, whats wrong with passing its IP instead?? ARGHH..
Sorry had to rant, I have been asking for that for years now.
Message Edited by David.Poprik on 04-26-200706:29 AM
Mod Note: Please do not use any profanities in the the forums. For guidlines please see the Discussion Forums Terms and Conditions.
Thank you.
Message Edited by John_B on 04-26-2007 07:14 AM