Ghost Solution Suite

  • Private Community
 View Only

  • 1.  Creating Network Boot Package (ISO) and deploying via PXE

    Posted Jul 04, 2008 09:09 AM

    I am trying to create a network boot package (for use with GhostCast) using the Ghost Boot Wizard with GSS2.0. I do not have a floppy drive,cd rom or USB device I can use. I have opted to create an ISO image.


    I run through the process and it creates the ISO image without a problem (aproximately 26MB)

     

    How do I manipulate the ISO image so I can transfer it via TFTP to my remote hosts so, in turn, I can then deploy my image from a central locatio via ghost cast?

     

    I have set up the DHCP side of things and this works ok.



  • 2.  RE: Creating Network Boot Package (ISO) and deploying via PXE

    Posted Jul 04, 2008 05:44 PM

    I dont think ISO will be of any help. ISO is a CD image. What you are after is PXE boot package. Please use TCP/IP packages options, either managed (connected back to the Console) or non-managed (wiht just ghost in it).

    Hope this helps.



  • 3.  RE: Creating Network Boot Package (ISO) and deploying via PXE

    Posted Jul 05, 2008 10:04 AM

    Ive tried to create both network packages (.sys files) and neither work. This is very frustrating!

     

    Like I said, Im trying to use ghostcast to deploy the images and not the console.

     

    Is there any documentation for this? like a step by step guide?

     

    Thanks!



  • 4.  RE: Creating Network Boot Package (ISO) and deploying via PXE

    Posted Jul 05, 2008 04:57 PM

    Of course there is step by step guide - ghost implementation guide pdf that comes with the suite.

    Many, many, many people are using DOS (sys) and Winpe (GSS 2.5) with 3COM PXE server that GSS comes with so I dont think that PXE boot doesnt work. What is the error that you are getting? As a general rule can you please provide the error you are getting and any other useful info rather than just saying - "it doesnt work, very frustrating". This doesnt help to help you out.

    The only way for you to use Ghostcast server without the Console is to either use PXE boot or use standalone boot packages connecting back to Ghostcast session and pulling images manually.

    Hope this helps.



  • 5.  RE: Creating Network Boot Package (ISO) and deploying via PXE

    Posted Jul 07, 2008 06:48 AM

    I will consult the installation guide. Thanks for that.

     

    I havent got a specific error code, hence my frustration. The latest problem I am encountering is trying to boot from the .sys network package. The remote host simply reboots in a loop.

     

    How do I create the standalone boot package to communicate to the ghost cast server? Ideally, I want to manually push out the images from the central location.

     

    Thanks,

     

    Martin

     

     

     

    Of course there is step by step guide - ghost implementation guide pdf that comes with the suite. Many, many, many people are using DOS (sys) and Winpe (GSS 2.5) with 3COM PXE server that GSS comes with so I dont think that PXE boot doesnt work. What is the error that you are getting? As a general rule can you please provide the error you are getting and any other useful info rather than just saying - "it doesnt work, very frustrating". This doesnt help to help you out. The only way for you to use Ghostcast server without the Console is to either use PXE boot or use standalone boot packages connecting back to Ghostcast session and pulling images manually. Hope this helps.



  • 6.  RE: Creating Network Boot Package (ISO) and deploying via PXE

    Posted Jul 07, 2008 05:08 PM

    Select any preos (DOS or Winpe), click next and then select 'TCP/IP Network boot image'. This is unmanaged boot package that includes everything but runs ghost instead of ghost client agent on startup. 'TCP/IP Network ghost client boot image' is managed boot package that runs Ghost client agent on startup.

    You can provide command-line options for ghost/ghost32 so that it connects to your ghostcast session automatically on startup (-ja=session_name) so that your PXE boot is fully automated.

    For full ghost comman-line switch support please look at Ghost impl. guide Appendixes sectrion.

    Cheers. 



  • 7.  RE: Creating Network Boot Package (ISO) and deploying via PXE

    Posted Jul 08, 2008 05:51 AM

    I managed to sort this using the following;

     

     

    Setup DHCP scope in Windows

     

    Configure the following options

    013 Boot File Size 0xa (file size x 1024 and / 512)

    060 ClassID PXEClient

    043 Vendor Specific info 01 04 00 00 00 00 ff

    066 Boot Server Hostname 192.168.1.1

    067 Bootfile Name deploy.pxe

     

    Use ghost boot disk creator to create a Network Boot Package (.sys file). Choose the universal network drivers to cover all network adapters. Also set the parameters on the ghost.exe command to be –ja=rollout -sure

     

    Install 3com Network Boot Services

     

    Use the Boot Image editor to create a new PXE menu boot file.

    Add the .sys image file and give a description

    Save the file in C:\TFTPROOT as ghostboot.pxe

     

    Use the BOOTPTAB editor to modify the hosts.

     

    Create a laptop entry and set the following;

    Name: Laptop

    Address: ???????????? (wild card for all MAC addresses)

    Image: deploy.pxe

    Remove all other hosts and save the file

    When the host boots, it will be given a DHCP address and have the deploy.pxe image file loaded to it. This will then invoke the ghostboot.sys file and load in to DOS. The session will be connected to on the ghostcast server and then the image can be manually deployed to the host.