Kaseya Community

Agent Procedure running a script with < or > in breaks the script

  • Hi

    I have an agent procedure that is running some SQL to check some data sets, however we are having problems in that we cannot use < or > as kaseya thinks this is the start of a managed variable.

    Is there a way to stop Kaseya behaving this way?



  • Double up those symbols when they are in a Kaseya script. For example, if you want one it needs to be ">>" in Kaseya. If you want two, then do ">>>>"

  • Try using << or >>  

    Same applies if you need a # in a string  , just enter it twice ie ##


  • A good example of two wrongs making a right Big Smile