Forum Discussion

JodiAliceRecep's avatar
JodiAliceRecep
Active Contributor
2 years ago

After running a task that logs off a PC in task scheduler, PC goes "offline" in GoToResolve console

I have a task that involves a PC logoff at the end of the script, and when I run it on the PC via the task scheduler, it goes offline in the GoToResolve Desktop Console--but the PC is definitely not offline, as I'm able to reach it via other methods (I can ping it, and one of my test PCs is a VM, so I can see it's online).  I can't make it come back online in the console unless I reboot the PC.  Has anyone else seen this behavior?  I checked the GoToResolve Unattended service, and it's still running on the "offline" PC.  Any ideas?

  • GlennD's avatar
    GlennD
    GoTo Manager
    2 years ago

    Hi JodiAliceRecep,

     

    When a PC is listed as Offline it means that it is no longer communicating with our servers. It sounds like the script is stopping the GoToResolve service, which is why the computer appears as Offline. I've testing logging the User out while in an Unattended session and after a few seconds the connection reestablishes and does not drop, so I can sign in again as that user or another user. 

     

    • JodiAliceRecep's avatar
      JodiAliceRecep
      Active Contributor
      2 years ago

      A standard logoff wasn't doing that--only when I ran the script that ended with the command "shutdown /l".  However, once I switched it to the command "logoff" instead, that seems to have resolved the issue.  

      • JodiAliceRecep's avatar
        JodiAliceRecep
        Active Contributor
        2 years ago

        Well, I spoke too soon.  It worked a few times, but now it's offline again.  The problem is that it's not on our network, so I can't get access to it again unless someone reboots it or restarts the GoToResolve service manually.  It's so frustrating!

  • JodiAliceRecep's avatar
    JodiAliceRecep
    Active Contributor
    2 years ago

    One thing we literally just discovered is that using "shutdown /L" forces it to go offline and stay offline in GoToResolve, but when we use the "logoff" command instead, it seems to come back up without issue.