Ghost Solution Suite

 View Only
  • 1.  Product Enhancement Request - WOL (post HF3)

    Posted Dec 07, 2015 06:50 AM

    Hello GSS development folks, I have a request for future development post HF3.

     

    I just started using GSS 3 with the release of HF3 (and autmotion folders as a replacement for the virtual partition).  SO far, so good, but I've only done some basic stuff so far and I'm beginning to absorb the learning curve of possibilities.

    One item that has caught my attention is the way GSS3.0 manages WOL vs. the 2.5 system.  It appears that GSS3 looks for an active agent on a local subnet to relay the WOL packets (proxy WOL) form the server.  It looks like in order to do so the (Altiris) agent needs to be pre-configured to act as a WOL proxy, no more than 2-3 computers recommended per subnet, and of course one of them has to be up-and-running.

    In he 2.5 console WOL was a 'no brainer' for us  ...create a task involving WOL, identifiy a computer or group of computers and execute.  Beautiful.

    Do you know if there is a way I can configure a switch or router to relay do the job of the agent, I can certainly give that a try.  I guess I would need to know the type of packets sent from the GSS server (and\or the WOL standard used) so my network folks could maybe do a reconfig for forwarding.

     

    Thank you.

     

    -->Mark S.



  • 2.  RE: Product Enhancement Request - WOL (post HF3)

    Trusted Advisor
    Posted Jan 26, 2016 12:11 PM

    This is an excellent enhancement request -GSS3 should send WOL packets direct to the client by IP Address. This would be a very good compliment to the agent wol-proxy service.

    I'll add this to the ehnancement spam I send to the Product Manager (David Evans)



  • 3.  RE: Product Enhancement Request - WOL (post HF3)

    Posted Feb 01, 2016 06:34 PM

    Sorry to ask a question I should know but for the sake of learning and posibly a new idea here I will put it out there.    Can't we install the agent on to the GSS 3 server?   Then you could set the agent on the server as the WOL proxy for this subnet.    You would still need another proxy on other subnets but if your clients and server are on the same wouldn't this work?

      
    I don't recall how 2.5 worked out subnets and WOL I think it just didn't work or you had to open your switches up so the 3.0 options may be better assuming there is one server on each subnet that can run the agent and then be set as WOL proxy but if it is just one subnet you could make the ghost server the wol proxy by installing the agent to it.  

    If I get some time I will try that out or if you know Ian tell me where my thinking is wrong.    As an enhancemtn for sure the GSS 3 Server should take care of it's subnet's WOL packets by default with out the need to install the agent locally so still a valid enhancement.  

    Thanks. 

     

     

     



  • 4.  RE: Product Enhancement Request - WOL (post HF3)

    Trusted Advisor
    Posted Feb 02, 2016 07:28 AM

    Hi ICHCB,

    The GSS3 server will wake machines up which are hosted on the same subnet. No need to a proxy on the same subnet as the server itself. The WOL Proxies are only required to server WOL packets to subnets other that the one the GSS3 server sits on.