Unattended Computer disappearing from GoToAssist?

Unfortunately, I'm still seeing the issue.

While Googling the issue, I saw some older references to computers being reimaged could potentially be an issue. All computers we reimage are to a stock Windows 10 computer with unique UUIDs.

Also, GoTo is never part of the image. That is the last step in our process. After adding to the domain and installing antivirus.

I only mention this because the issue is random and I'm literally "grabbing for straws" here out of desperation.

So process is as follows:

1. Image computer (can be a brand new Dell straight from the factory or one that has been repurposed)
2. Install necessary Windows updates.
3. Perform Dell Command updates.
4. Activate MS Office license.
5. Add to domain.
6. Add end user profile.
7. Install antivirus.
8. Install GoTo Expert v4 and assign to appropriate Unattended "group"/"list".
9. Deliver computer to end user.

Everything seems to work fine for a couple hours (the shortest time I've seen yet) to a few weeks until..... poof! It drops from the unattended list.

Once we get the computer back we check and GoTo is actually installed and running on the system in question. The service is intact and running.

We uninstall GoTo, reinstall GoTo and everything is working until it disappears again. There appears to be no rhyme or reason to it.

For example, last night I had to assist an end user. I have manually uninstalled and reinstalled GoTo twice before this incident. I was able to RDP to her PC and, for the third time in less than a month, reinstall GoTo.

Everything was working great. This morning I get to work and her PC still showed in the Unattended list (but was greyed out because it was offline at the time). I checked back when I knew she would be in and it was still in the list and now "lit up" (active or on) in the list. Approximately an hour later I check the list again and... you guessed it. POOF! Gone.

Hopefully this novel worth of babble can help steer me in the right direction to get this fixed.

Thanks again for not letting this topic die until we can figure it out!