How to use the 3Com Boot Services (and SolarWinds TFTP) with Symantec Ghost Solution Suite 2.5 using WinPE

Article:TECH110765  |  Created: 2009-01-03  |  Updated: 2014-03-27  |  Article URL http://www.symantec.com/docs/TECH110765
Article Type
Technical Solution


Environment

Issue



What is an alternate method to booting Windows PE and Ghost through PXE other than using the 3Com TFTP server?

Symptoms
With 3Com TFTP can only connect to one client at a time via PXE

  • Error messages are vague in 3Com TFTP
  • Configuration is limited in 3Com TFTP
  • Other errors or issues sending boot packages via the 3Com TFTP



 


Cause



The 3Com TFTP server software is antiquated


Solution



The 3Com PXE Boot Services works with Ghost Solution Suite 2.5's DOS and Windows PE environments. These Operating Systems will allow for a greater variety of hardware and software platforms to be included to:
 

  • Restore an image of a disk or partition from a file server.
  • Create an image of a disk or partition and save it on a file server.


When using PXE, client computers boot to the computer's Network Interface Card ( NIC ) rather than a Ghost Network Boot Disk. While outside the scope of this document, PXE can also be used with the Ghost Console.

The steps below cover the updated Windows PE boot environment. The setup procedure for the DOS boot environment has not been altered. You can refer to the following knowledge base document How to use the 3Com Boot Services with Symantec Ghost for a step-by-step guide to setting up the DOS environment:

 


Notes:

  • Support for PXE is available online at Argon Technologies. Check the link http://www.argontechnology.com/support/3com/index.html.
  • 3Com Corporation has discontinued development and support for the 3Com Boot Services.
  • SolarWinds is an independent network management software developer. Check their website at http://www.solarwinds.com/
  • Symantec Technical Support for PXE is limited to the use and troubleshooting of Ghost. Support is not offered for configuring or troubleshooting PXE operations outside the functionality of Ghost.
  • Symantec Technical Support for Windows PE is limited to the use and troubleshooting of Ghost. The operation of this OS outside the use of Ghost is not supported by Symantec.

 

Overview of Preparation
 

Install the 3Com Boot Services.

  1. Install SolarWinds TFTP server.
  2. Create a TCP/IP Network Boot Image with the Ghost Boot Wizard.
  3. Specify the boot file to be delivered in the BOOTPTAB Editor

Preparation


1. Install the 3Com Boot Services.
 

    More information is available in the file "boot_services_quickstart.pdf" on the Ghost install CD:
    1. From the Ghost Install, select Install Tools and Utilities.
    2. Select Install 3Com Boot Services PXE Server.
    3. Click Install 3Com Boot Services.
    4. Continue the install wizard. You will see a window entitled 'Setup Type.' Specify Server rather than Administrator or Custom.
    5. Accept default values for the rest of the installation.
    6. When done with the wizard, click on Finish, and exit all windows.
    7. Run the PXE Server.
      1. Click Start and Programs.
      2. Select 3Com Boot Services and click PXE Server. You will be prompted to create a DHCP proxy. If you are installing 3Com Boot Services on a computer that does not run a DHCP Server, answer 'Yes.' When the installation is complete, verify that the proxy was installed.
      3. Click Options.
      4. If there is no check mark next to Proxy DHCP, click Proxy DHCP and restart the computer.
    • A DHCP server must be installed somewhere on the network in order to use the PXE protocol.
      • If the PXE Boot Services are installed on the DHCP Server, you must use the option that adds the "Option 60 PXEClient Tag String" to DHCP packets.
      • If the PXE Boot Service are installed on a different computer, you must enable the ProxyDHCP function in the PXE Server software. The first time you run the PXE Server, you will be prompted to enable ProxyDHCP.
      • Symantec recommends that the PXE, Ghost and DHCP be installed on the same subnet. These instructions assume that this is true.
    8. Close the PXE Server.

2. Install SolarWinds TFTP server.
 

3. Create a TCP/IP Network Boot Image with the Ghost Boot Wizard.
 

    1. Click Start > Programs > Symantec Ghost > Symantec Ghost Boot Wizard.
    2. Select Windows PE [Default]
    3. If you are going to be using DeployAnywhere, check the box to "Include Deploy anywhere Driver Database with the image." See the document How to run Deploy Anywhere from the Ghost Boot CD for more information.
    4. Click Next.
    5. Select TCP/IP Network Boot Image option and click Next.
        1. Confirm the location of the client type and add in any additional Parameters you like.
          • Optionally, you can add -ja=sessionname to the additional Parameters section so that this boot image will automatically connect to a Ghost Cast Server Session named "sessionname". For more information about automating the Ghost process, see the document Switches: User intervention
        2. Click Next.
        3. On the "Network Client Configuration" screen, click Next.
        4. Select your IP options.
        5. Click Next.
        6. Add any additional files you like. Note that if you are going to use the Deploy Anywhere feature with PXE, you need to include both Ghdplyaw32.exe and Ghconfig32.exe in the package. Both files can be found in c:\Program Files\Symantec\Ghost on the computer that has the Ghost software installed.
        7. Click Next.
        8. Browse to where you want your TFTP Root directory to be stored.
        9. Provide an 8 character filename for the Network Boot Image that uses only lower case letters.
        10. Click Next twice.
        11. Click Finish
    • Note: After completing your boot image (regardless of whether it's a network boot image or a Ghost client boot image), copy bootmgr.exe from C:\TFTPBOOT\boot to C:\TFTPBOOT. This places the boot manager in the common folder so that it can be served by the TFTP Server. 
       
    • (Note: The method described in steps A - K below is an alternate method of PXE booting that allows your Ghost Client to appear in the Ghost Console. If you'd rather use a Ghost Console task instead of using the Ghost Cast Server, you can create the TCP/IP Network Ghost Client Boot Image instead of the TCP/IP Network Boot Image.)
      • TCP/IP Network Ghost Client Boot Image - Use this option to create a Windows PE client for use with the Ghost Console. You could use this option instead of the TCP/IP Network Boot Image. This will allow you to connect your client, via PXE, to the Ghost Console.
        1. Confirm the location of the client type and add in any additional Parameters you would like.
        2. Click Next.
        3. On the "Network Client Configuration" screen, click Next.
        4. Select your IP options.
        5. Click Next.
        6. Add any additional files you like. Note that if you are going to use the Deploy Anywhere feature with PXE, you need to include both Ghdplyaw32.exe and Ghconfig32.exe in the package. Both files can be found in c:\Program Files\Symantec\Ghost on the computer that has the Ghost software installed.
        7. Click Next.
        8. Browse to where you want your TFTP Root directory to be stored.
        9. Provide an 8 character filename that uses only lower case letters.
        10. Click Next twice.
        11. Click Finish
      (If there is no record of the client computer in the Console Database, the client will appear in the Default Machine Group. If there is a record of the client already in the Console database, the client will be present in its previous location in the machine groups.)
      • Note: After completing your boot image (regardless of whether it's a network boot image or a Ghost client boot image), copy bootmgr.exe from C:\TFTPBOOT\boot to C:\TFTPBOOT. This places the boot manager in the common folder so that it can be served by the TFTP Server.
         

4. Specify client computers in the BootPTab Editor.
 

    1. Click Start > All Programs > 3Com Boot Services > BootPTab Editor.
    2. Click Edit and then click Add Host to open the Edit Host window.
    3. Provide the information as follows:
      • Name: This is the computer name of the client computer, or host computer. If you don't want to specify a particular computer name, click the box to "Use node for name"
      • Node: Specify the MAC address of the client computer that should use the PXE menu. If you want to specify multiple computers based on MAC addresses, you can use a question mark as a wildcard character. For example, if one computer's MAC address is 123456889988 and another is 123456852963, notice that the first 6 digits are the same. Using the MAC address of 123456?????? in the Node field would allow both machines to connect to use the PXE package. This will work as long as there are no other BootPTab host entries that exactly match the MAC address of the computers. You can also use all wildcards (???????????) to allow all of your clients to receive the PXE package.
      • IP #: Do not use this box.
      • Image: Type the information as follows exactly as follows: /boot/pxeboot.n12
    4. Click OK. The entry should be reflected on the Hosts tab.
    5. Click on File, and Save. Do NOT change the file name of the BOOTPTAB. It must be named 'BOOTPTAB' (without any extension) and be located in C:\TFTPBOOT.
    6. Close the BootPTab Editor.

Execution


The execution involves starting the TFTP Server and the PXE Server, running a GhostCast Server session and booting the client computers.


To use Ghost with the 3Com Boot Service:
 

  1. Start the servers:
    1. At the 3Com Boot Server, click Start > Programs > SolarWinds TFTP Server > TFTP Server.
    2. In the TFTP Server, go to File > Configure, and change the Storage setting to point to C:\TFTPBOOT. Under Status, click Start.
    3. At the 3Com Boot Server, click Start > Programs > 3Com Boot Services > PXE Server.
    4. Start the GhostCast Server. Starting and configuring the GhostCast Server must be done before the client computers are booted to the network.
    5. Configure the GhostCast Server as you would normally would.
      1. Click Start > Programs > Symantec Ghost > Ghost Cast Server
        • Note: If you opted to use the TCP/IP Network Ghost client Boot Image in step 2 , you can use the Ghost Console instead.
      2. Select Restore Image.
      3. Enter the session name that was provided in step 2 under the Additional Parameters section
      4. You must specify the disk number. For one disk only, use a value of 1. If you are restoring a single partition, specify the partition instead.
      5. Click Accept Clients. The GhostCast Server will then wait for the client computers to join the session.
    6. On the client computers, the temporary boot order should be set to perform a network boot first. This can often be set on a one-time basis by pressing F12 at boot and choosing the network boot option. For more information about how to invoke a temporary network boot, please contact your hardware manufacturer.
    7. Upon network boot a menu should appear based on the file name you gave your boot image. Note that if you only have one boot image, then you will not be prompted to choose a boot option.
    8. Select the appropriate item from the menu and allow Windows PE to load. Once Windows PE has loaded, Ghost will automatically execute. If you included the -ja=sessionname switch in the Additional Parameters section in Step 2, the client should automatically join the Ghost Cast Server session.




References
To use PXE on different subnets, switches involved need to be configured to match PXE standards according to ' IPHelper ' configuration. The name of the configuration varies from switch to switch. Symantec does not support configuring networks as part of support for Ghost. Sample documentation on IPHelper is available at http://www.winexpertise.nl/kb/Altiris_Article001.shtml

Title: How to run Deploy Anywhere from the Ghost Boot CD
URL: http://service1.symantec.com/support/on-technology.nsf/docid/2008050913544860

Title: Switches: User intervention
URL: http://service1.symantec.com/support/on-technology.nsf/docid/1998082609222725

Title: How to use the 3Com Boot Services with Ghost
URL: http://service1.symantec.com/support/on-technology.nsf/docid/2000103113200725?Open&seg=ent

Large portions of this document were taken from the original:

Title: 'How to use the 3Com Boot Services with Symantec Ghost Solution Suite 2.5 using WinPE'
Document ID: 2008050613274260
http://service1.symantec.com/support/on-technology.nsf/docid/2008050613274260?Open&seg=ent


Technical Information
PXE Protocol

Computers use a variety of protocols for booting from the network. PXE is one of these protocols. A PXE-enabled computer is one that has a network boot option hard-coded into the computer's BIOS or into a ROM chip on the network interface card, and where the code conforms to the PXE protocol. A computer can be hard-coded for more than one network boot protocol.

The PXE standard by default is configured to operate on the same subnet as the DHCP server and the client system that is booting from PXE. The Symantec Ghost Support Team does not offer assistance on network configurations. Please contact your network hardware provider for any network troubleshooting that may be needed.

 



Legacy ID



2009060307534660


Article URL http://www.symantec.com/docs/TECH110765


Terms of use for this information are found in Legal Notices