Intel,Altiris Group

  • 1.  NS 7.1 imaging

    Posted Apr 21, 2011 05:36 AM

    Hi everyone,

    Scenario:: NS 7.1 on windows 2008 R2, SQL on its on box

    We enabled a task to capture an image as follow:

    Run reboot to pxe, run create image, run reboot to prodcuiton

    and we get the following error:

    PXE-T00: timeout error

    PXE -E36: Error received form TFTP server

    PXE -MOF: Exiting Broadcom PXE ROM

    I read some forum info, but so far not good results,

    If you have any advice or tips will be much appreciated

    Also, I am looking for some sample (notes, videos, etc) for imaging process on NS 7.1, so I can replicated to the test environment too

    Thanks

    Mark



  • 2.  RE: NS 7.1 imaging

    Posted Apr 23, 2011 02:02 PM

    HI,

    You Might want to add Option 60 to your DHCP.. You can follow the below document for the same.

    http://www.symantec.com/docs/HOWTO1392

     

    Also check the below doc for your Ref.

    URL :  http://www.symantec.com/docs/TECH25943

    Title : PXE-E36 Error received from TFTP server

     

    Hope this helps

     

    Cheers



  • 3.  RE: NS 7.1 imaging

    Posted Apr 24, 2011 04:41 AM

    Thanks for the reference page,

    But the dhcp and pxe and in different box and for the TECH25943 is referred to 6.8 and we have DS 7.1 in the environment

    By the way I run wireshark with the following info:

    source machine to server::: TFTP; Error Code: NOt defined; Message: TFTP Aborted\000

    source machine to server:::TFTP; read request, FIle: BStrap\x86PC\BStrap.0\000



  • 4.  RE: NS 7.1 imaging

    Posted May 06, 2011 04:28 PM

    I've moved your thread to the Deployment Solution forum.

    A good place to start if you have generic questions would be the Articles, Download, and Video sections of Connect.  There is a decent amount of content available.

    Can you explain how the content provided in the KB does not work?  The instructions are for DHCP, and while it may be a little different in Windows Server 2008 R2 compared to Windows Server 2003, it should still apply.