Ghost Solution Suite

 View Only
  • 1.  Latitude 3400 Automation Folder Install

    Posted Jul 15, 2020 02:54 PM
    I'm using GSS 3.3 RU4 through the Ghost Console. Am able to install the Remote Agent Installer but when I try to install the Automation Folder, the job runs and even shows that an automation folder has been installed but when I look at available operating systems through Windows control panel it does not show Symantec Deployment Solution Preboot environment as being installed. Also, on the automation install is shows package installation complete and gives a Status Code 0 (not sure what that means). Any help with this would be greatly appreciated.

    Thanks

    Brad


  • 2.  RE: Latitude 3400 Automation Folder Install

    Broadcom Employee
    Posted Jul 15, 2020 03:15 PM

    Hi Brad!

    try to check its state using this guide https://knowledge.broadcom.com/external/article/150208



    ------------------------------
    Software QA Engineer 3
    Broadcom Inc.
    ------------------------------



  • 3.  RE: Latitude 3400 Automation Folder Install

    Posted Jul 15, 2020 05:40 PM
    Thanks Igor, the "c:\boot" folder is there and the computer properties in the console show the automation folder is installed but when I try to boot to Windows automation I get and error "Unable to boot to windows automation error 116". I opened BCDEDIT and it does not show the c:\boot as an option, only the Windows Boot Manager.

    Thanks

    Brad


  • 4.  RE: Latitude 3400 Automation Folder Install

    Posted Jul 27, 2020 08:19 AM
    Edited by Bstaupp Jul 27, 2020 08:44 AM
    I am having the same problem. The C:\Boot folder is there, yet when I do a BCDEDIT, I am not seeing it as a boot folder option. It never boots over to automation when trying any task(s). It appears to be a problem with the boot disk creator and not properly creating the BCDEDIT command after creating the automation folder. Do we have a hot fix for this yet? 

    Thanks
    Yet another Brad...no joke...

    ------------------------------
    JCCC
    ------------------------------



  • 5.  RE: Latitude 3400 Automation Folder Install

    Posted Jul 28, 2020 04:33 PM
    Working with tech support, I believe this appears to be a bug with the latest RU4 update. I created a separate script(s) for both UEFI and BIOS configurations to get this to work correctly: 

    Traditional Boot:

     

    C:\boot\altiris\iso\bcdedit.exe  /create {e217309d-dead-beef-a315-001372be0d02} /device /d "Symantec Deployment Solution Preboot Environment"
    C:\boot\altiris\iso\bcdedit.exe  /set {e217309d-dead-beef-a315-001372be0d02} ramdisksdidevice partition=C:
    C:\boot\altiris\iso\bcdedit.exe  /set {e217309d-dead-beef-a315-001372be0d02} ramdisksdipath \boot\altiris\iso\boot\boot.sdi
    C:\boot\altiris\iso\bcdedit.exe  /create {e217309d-dead-beef-a315-001372be0d01} /d "Symantec Deployment Solution Preboot Environment" /application OSLOADER
    C:\boot\altiris\iso\bcdedit.exe  /set {e217309d-dead-beef-a315-001372be0d01} device ramdisk=[C:]\boot\altiris\iso\sources\boot.wim,{e217309d-dead-beef-a315-001372be0d02}
    C:\boot\altiris\iso\bcdedit.exe  /set {e217309d-dead-beef-a315-001372be0d01} path \windows\system32\boot\winload.exe
    C:\boot\altiris\iso\bcdedit.exe  /set {e217309d-dead-beef-a315-001372be0d01} osdevice ramdisk=[C:]\boot\altiris\iso\sources\boot.wim,{e217309d-dead-beef-a315-001372be0d02}
    C:\boot\altiris\iso\bcdedit.exe  /set {e217309d-dead-beef-a315-001372be0d01} systemroot \windows
    C:\boot\altiris\iso\bcdedit.exe  /set {e217309d-dead-beef-a315-001372be0d01} winpe yes
    C:\boot\altiris\iso\bcdedit.exe  /set {e217309d-dead-beef-a315-001372be0d01} detecthal yes
    C:\boot\altiris\iso\bcdedit.exe  /set {e217309d-dead-beef-a315-001372be0d01} bootlog yes
    C:\boot\altiris\iso\bcdedit.exe  /set {e217309d-dead-beef-a315-001372be0d01} quietboot yes
    C:\boot\altiris\iso\bcdedit.exe  /displayorder {e217309d-dead-beef-a315-001372be0d01} /addlast

    autoutil.exe /a  

     

    UEFI Boot:

     

    C:\boot\altiris\iso\bcdedit.exe  /create {e217309d-dead-beef-a315-001372be0d02} /device /d "Symantec Deployment Solution Preboot Environment"
    C:\boot\altiris\iso\bcdedit.exe  /set {e217309d-dead-beef-a315-001372be0d02} ramdisksdidevice partition=C:
    C:\boot\altiris\iso\bcdedit.exe  /set {e217309d-dead-beef-a315-001372be0d02} ramdisksdipath \boot\altiris\iso\boot\boot.sdi
    C:\boot\altiris\iso\bcdedit.exe  /create {e217309d-dead-beef-a315-001372be0d01} /d "Symantec Deployment Solution Preboot Environment" /application OSLOADER
    C:\boot\altiris\iso\bcdedit.exe  /set {e217309d-dead-beef-a315-001372be0d01} device ramdisk=[C:]\boot\altiris\iso\sources\boot.wim,{e217309d-dead-beef-a315-001372be0d02}
    C:\boot\altiris\iso\bcdedit.exe  /set {e217309d-dead-beef-a315-001372be0d01} path \windows\system32\boot\winload.efi
    C:\boot\altiris\iso\bcdedit.exe  /set {e217309d-dead-beef-a315-001372be0d01} osdevice ramdisk=[C:]\boot\altiris\iso\sources\boot.wim,{e217309d-dead-beef-a315-001372be0d02}
    C:\boot\altiris\iso\bcdedit.exe  /set {e217309d-dead-beef-a315-001372be0d01} systemroot \windows
    C:\boot\altiris\iso\bcdedit.exe  /set {e217309d-dead-beef-a315-001372be0d01} winpe yes
    C:\boot\altiris\iso\bcdedit.exe  /set {e217309d-dead-beef-a315-001372be0d01} detecthal yes
    C:\boot\altiris\iso\bcdedit.exe  /set {e217309d-dead-beef-a315-001372be0d01} bootlog yes
    C:\boot\altiris\iso\bcdedit.exe  /set {e217309d-dead-beef-a315-001372be0d01} quietboot yes
    C:\boot\altiris\iso\bcdedit.exe  /displayorder {e217309d-dead-beef-a315-001372be0d01} /addlast

    autoutil.exe /a  



    ------------------------------
    JCCC
    ------------------------------



  • 6.  RE: Latitude 3400 Automation Folder Install

    Posted Aug 10, 2020 12:16 PM
    I have the exact same issue.   It seems to be a issue during the install process of the Automation folder, i am getting errors with the bcdedit copy process.   It was working fine with 3.3RU3 but since updating to RU4 there is an error at the end of the log file for the automation folder install.

    2020/08/09 16:31:37 autoinst(2070) I: -Install - find frm file
    2020/08/09 16:31:37 autoinst(2070) D: CClient::FindFrmFile - FRM file path = 'C:\Windows\TEMP\apt0\auto.frm'
    2020/08/09 16:31:37 autoinst(2070) I: Begin DiskReadMbrSector (pMbrBuffer, pPartitionTableBuffer, nDiskNumber=0)
    2020/08/09 16:31:37 autoinst(2070) I: End DiskReadMbrSector - returning 0 (success = 0)
    2020/08/09 16:31:37 autoinst(2070) I: MbrCheckSum - returning a checksum of 0xa42a6c21 / 2754243617 for disk 0
    2020/08/09 16:31:37 autoinst(2070) D: -Install - size of frm file contents is 422007130
    2020/08/09 16:31:37 autoinst(2070) I: -Install - create install destination path 'C:\boot\altiris\iso'
    2020/08/09 16:31:37 autoinst(2070) I: -Install - extract contents of frm file 'C:\Windows\TEMP\apt0\auto.frm' to 'C:\boot\altiris\iso'
    2020/08/09 16:31:39 autoinst(2070) I: -Install - copy files listed in '[INSTALL_FILES]' from 'C:\Windows\TEMP\apt0' to 'C:\boot\altiris\iso'
    2020/08/09 16:31:39 autoinst(2070) I: Begin CClient::IniEntrysCopy (sFile='C:\Windows\TEMP\apt0\autoinst.ini', sSection='INSTALL_FILES', sSrcVar='C:\Windows\TEMP\apt0', sDstVar='C:\boot\altiris\iso', dwExitCode, bContinueOnErrors=0, pfnProgress=00897390, bSearchForSection=1, nLevel=0)
    2020/08/09 16:31:39 autoinst(2070) I: -IniEntrysCopy - Copy 'C:\Windows\TEMP\apt0\autoinst.exe' to 'C:\boot\altiris\iso\autoinst.exe'
    2020/08/09 16:31:39 autoinst(2070) D: FileCopy (sSrc='C:\Windows\TEMP\apt0\autoinst.exe' -> sDst='C:\boot\altiris\iso\autoinst.exe') returning 0 (success = 0)
    2020/08/09 16:31:39 autoinst(2070) I: -IniEntrysCopy - Copy 'C:\Windows\TEMP\apt0\autoinst.ini' to 'C:\boot\altiris\iso\autoinst.ini'
    2020/08/09 16:31:39 autoinst(2070) D: FileCopy (sSrc='C:\Windows\TEMP\apt0\autoinst.ini' -> sDst='C:\boot\altiris\iso\autoinst.ini') returning 0 (success = 0)
    2020/08/09 16:31:39 autoinst(2070) I: -IniEntrysCopy - Copy 'C:\Windows\TEMP\apt0\autoutil.exe' to 'C:\boot\altiris\iso\autoutil.exe'
    2020/08/09 16:31:39 autoinst(2070) D: FileCopy (sSrc='C:\Windows\TEMP\apt0\autoutil.exe' -> sDst='C:\boot\altiris\iso\autoutil.exe') returning 0 (success = 0)
    2020/08/09 16:31:39 autoinst(2070) I: -IniEntrysCopy - Copy 'C:\Windows\TEMP\apt0\autoutil.ini' to 'C:\boot\altiris\iso\autoutil.ini'
    2020/08/09 16:31:39 autoinst(2070) D: FileCopy (sSrc='C:\Windows\TEMP\apt0\autoutil.ini' -> sDst='C:\boot\altiris\iso\autoutil.ini') returning 0 (success = 0)
    2020/08/09 16:31:39 autoinst(2070) I: -IniEntrysCopy - Copy 'C:\Windows\TEMP\apt0\bcdedit.exe' to 'C:\boot\altiris\iso\bcdedit.exe'
    2020/08/09 16:31:39 autoinst(2070) D: FileOperation (sSrc='C:\Windows\TEMP\apt0\bcdedit.exe', sDst='C:\boot\altiris\iso\bcdedit.exe', wAction=2, fFlags=0614) returning 2 (success = 0)
    2020/08/09 16:31:39 autoinst(2070) D: FileCopy (sSrc='C:\Windows\TEMP\apt0\bcdedit.exe' -> sDst='C:\boot\altiris\iso\bcdedit.exe') returning 117 (success = 0)
    2020/08/09 16:31:39 autoinst(2070) I: IniEntrysCopy - Could not copy 'C:\Windows\TEMP\apt0\bcdedit.exe' to 'C:\boot\altiris\iso\bcdedit.exe' - error 117
    2020/08/09 16:31:39 autoinst(2070) I: End CClient::IniEntrysCopy - returning 117
    2020/08/09 16:31:39 autoinst(2070) I: End CClientBootMgr::Install - returning 117 (success = 0)

    2020/08/09 16:31:39 autoinst(2070) D: CreateChildProcess - CreateProcess (sFile='attrib', sParam='+h C:\boot') succeeded with exitcode 0, returning true
    2020/08/09 16:31:39 autoinst(2070) D: RunCommand - CreateChildProcess (sFile='attrib', sParam='+h C:\boot') succeeded with exitcode=0, returning TRUE
    2020/08/09 16:31:39 autoinst(2070) D: CClientBootMgr destructor called
    2020/08/09 16:31:39 autoinst(2070) D: CClient destructor called

    2020/08/09 16:31:39 autoinst(2070) I: AUTOINST is returning 117 (EXIT_ERR_FILE_COPY)

    2020/08/09 16:31:39 autoinst(2070) I: Ending application instance
    2020/08/09 16:31:39 autoinst(2070) I: Exit code: 117 (EXIT_ERR_FILE_COPY)
    2020/08/09 16:31:39 autoinst(2070) I: ****************************************
    2020/08/09 16:31:39 autoinst(2070) I: Application End
    2020/08/09 16:31:39 autoinst(2070) I: ****************************************


  • 7.  RE: Latitude 3400 Automation Folder Install

    Broadcom Employee
    Posted Aug 11, 2020 09:23 AM
    Hi Brad,
    It seems that this issue appears only after upgrade, not reproducible in case of fresh install.
    May you please try the following "workaround":
    1 - Create dummy bcdedit.exe (create new .txt and rename it to .exe)
    2- Create dummy BootSect.exe (create new .txt and rename it to .exe)
    3- Copy both files to the following locations on GSS server:
    • C:\Program Files (x86)\Altiris\eXpress\Deployment Server\Bootwiz\platforms\Windows\x64\Installer\
    • C:\Program Files (x86)\Altiris\eXpress\Deployment Server\Bootwiz\platforms\Windows\x86\Installer\
    4- Reinstall automation folder using newly generated automation folder packages.
    • to reinstall automation folder on affected clients, you need to uninstall existing not working AF and then install new
    • if you want to install automation folder from menu Advanced > 'Install Automation Folder...', make sure that you removed "bad" automation folder created during previous installs from C:\Program Files (x86)\Altiris\eXpress\Deployment Server\AutoFolderPkgs before reinstalling AF
    • if you want to install automation folder manually using created EXE package you need to create new AF package via Boot Disk Creator tool. 


    Thanks,Roman


  • 8.  RE: Latitude 3400 Automation Folder Install

    Posted Aug 11, 2020 01:32 PM
    That completely solved my error.   Automation folder install is now successful.

    Thanks.