Ghost Solution Suite

 View Only
  • 1.  Install DAgent in Windows 10 Scripted Install

    Posted Apr 12, 2016 12:56 PM

    ive done this for years with altiris, can't get it working with gss 3.1 and win 10

    added dagent.msi to $oem$/$1/dagent/ in the deploy folder, then changed the install parameters in setupcomplete.cmd. tried dagent_x64/msi as well

    made sure the nic drivers for win 10 and winpe are present

    client gets the scripted install, but doesn't install the agent. console reports "Setup is running in GUI mode".

    any ideas?

     



  • 2.  RE: Install DAgent in Windows 10 Scripted Install

    Broadcom Employee
    Posted Apr 13, 2016 03:17 AM

    Because you have to use msiexec /qn parameter to install it without GUI.

    Try this command line:

    msiexec /i dagent.msi /qn server_tcp_addr=SpecifyHereYourGSSserverAddress server_tcp_port=402

    OR

    msiexec /i dagent_x64.msi /qn server_tcp_addr=SpecifyHereYourGSSserverAddress server_tcp_port=402

     

    Thanks,

    IP.



  • 3.  RE: Install DAgent in Windows 10 Scripted Install

    Posted Apr 14, 2016 06:01 AM
    I found with Windows 10 that I needed to install the 64 bit Visual C++ 2005 redistributable first with my Deployment Server 6.9 SP6 system (the forerunner to GSS 3.0). I use the RTM (non SP1) version, vcredist_x64.exe v6.0.2900.2180, file versions 8.0.50727.42.


  • 4.  RE: Install DAgent in Windows 10 Scripted Install

    Posted Apr 14, 2016 07:40 AM
    And there's also a SCRIPTED_INSTALL=1 parameter for the DAgent msi install, I think this helps the DAgent, once installed, to keep track of when the scripted install has finished and to let the console run the next Job.


  • 5.  RE: Install DAgent in Windows 10 Scripted Install

    Posted Apr 28, 2016 04:25 PM

    The agent will be included in the job if you import the OS files from the root of the DVD or ISO not the Sources folder on the dvd or ISO.

     

    I would ask if when you imported your SOI files did you browse to the root of the ISO or did you browse to the sources folder when you imported the files?   The reason I ask is in my lab if I browse to the root of the OS install DVD and import from there then my agent deployment is correct at the end of the job.  But if I browse to the sources folder the way the Ghost GUI suggests then the agent won't install the agent correctly.

     

    One way you can check this is if you go to your express share in the Deploy/WinOS00x/sources what is the file and folder listing.

     

    You should have the following folders I have them in my win 10 enterprise SOI that is working It is the GA build not the 1511 build but I would expect a simular set up for 1511.

    boot
    efi
    sources
    support

    and files should be
    Autorun.inf
    bootmgr
    bootmgr.efi
    setup.exe

     

    If this isn't what you have I would ask that you reimport your OS from the DVD but this time confirm you are pointed to the root of the dvd and dont browse to the sources folder.