Conrad Sallian's community posts

Hello Mike,

Thanks for the update. So the version you are rolling out sets the recovery option in the host service to run the exe with the -restart flag (like what is configured by your CMD file?

Not only that. The bulk logoff bug will also be fixed.

As for AV false detections, it seems Google or Windows Security is blocking my current custom EXE installer v7.1.7.0. Does the code signing certificate expire?

The expiration date for the certificate only matters for signing. The expiration of the certificate does not invalidate the signature for the files already signed.

If this is Microsoft detection, I recommend that you send a false positive report on this page https://www.microsoft.com/en-us/wdsi/filesubmission

Hi Mike,

Actually we are ready to release, we are just waiting for some test results on this issue.

Also, given how intolerant and indiscriminate antiviruses have become, this time we'll have to first initiate the virus checks and  make sure that at least the most critical false detections are removed before we make the version public. This may delay the release from a few days to a week, but this is a necessary evil.

Hello Matthew,

Yes, of course. In the Host log it should say that the Host has been restarted.

Hello Everyone,

Have you had a chance to test the Hosts running with the new settings applied by the script? Please, let us know. Thanks.

Hi Tom,

Actually you must be able to submit a ticket. Any user with a commercial license can submit tickets. And your status says 'Starter' (see the label at the top right corner of the forum message window) which means that support tickets are available to you.

Let us investigate why your ticket wasn't working properly and get back to you.

UPD: I've sent you a message via the ticket you created. If you cannot answer, please update this thread. You can send a screenshot of the error message directly to support@remoteutilities.com for further investigation.

Hello Tom,

Thank you for your report.

We understand your frustration and we are also concerned by the quality of modern antivirus software, which fails to do a simple task of distinguishing legitimate, digitally signed program from malware.

Of course I can't make exceptions for every temp case because the paths and files are often random names. I can't fix this from my end.

Neither can't we. It's the antivirus software vendor that can fix their errors (but they never acknowledge them). We do our best to alleivate this situation by sending false positive reports.  If you as their customer would send a false positive report and specifically mention that faulty operation of their software distrupts your work process, the issue would certainly be resolved faster.

Updated the script file - it now accomodates 32-bit OS too. The previous script wouldn't work properly on 32-bit OSes.

Thanks.

Bob Smith wrote:

Thanks for your reply Conrad and that's great news. Let’s hope the next version isn’t 2 years away ;)

Definitely not . A few other issues were fixed so we'll release them all in one update as soon as possible.

Hello Bob,

Sorry if my colleague was a bit straightforward explaining the reason why we implemented this message in the first place.

UPD: I modifed this forum message a bit. The notification won't be movable. We'll simply remove it showing on the Viewer side, just as planned. This will be available in the very next update.

UPD 2: For technical reasons, hiding the notification message on the Viewer side will only be possible if Host is running on Windows 10 version 2004 (20H1) or later.

Hello Keith,

Thank you for the report. Indeed, there is a bug which wasn't evident at first. Actually, the mass logoff works but when the groups are enabled (Viewer Options -> View tab -> Use group view). When groups are disabled, mass logoff only works on the last item.

We'll add the fix to the nearest update of the Windows version, which is pretty soon.