snk-nick's community posts

David Hester,
We get it, you don’t like the notice.

Now kindly stop editing your message over and over, every time you do it notifies everybody subscribed to the thread.

Also it's been over a week and the upgrade is still being blocked, same message. I've obviously submitted it to BitDefender myself but don't you guys have a relationship with the major AV guys to prevent this stuff?

Sorry to be clear, I have C:\Program Files (x86)\Remote Utilities - Host\ as well as the specific application whitelisted on all my clients. As mentioned in my original post the "infection" was picked up in the temp folder with a random string.

This actually caused me a significant amount of work to resolve, far more clients failed than I anticipated so I had to roll out a new RU package to recover them all. Not exactly ideal.

Douglas Crawford wrote:

Are you saying that this makes it possible for a bad actor to substitute his own RU Server?

I run my own RU servers and there is zero difference between them and the company hosted ones, you simply set the installer to point to your server URL instead. Making it more complicated just opens up more potential for problems.

As a commercial user, I’m a fan of anything that lowers the ease and ability for bad actors to use RU… if you’re using it for personal use the restrictions are a fair trade off for free software and if you are using it professionally then you should purchase a professional license - negates all these issues.

Conrad Sallian wrote:
In one of the upcoming updates we will implement saving/exporting configurator settings to a file so that you could quickly load your previous choices.

Not to keep an old topic going but was this ever implemented?

Performing a simple upgrade on multiple Windows Servers from host 7.1.1.0 to 7.1.2.0, upgrade was blocked by Bitdefender with the following:

Advanced Threat Control has blocked a process that has been detected as malicious.Process path: C:\Windows\Temp\host_upgrade_{8CECBA23-E6C4-4B16-859A-0B45E9BA486A}.exe. Threat name: ATC.SuspiciousBehavior.D4B82CC334736729.

On most servers the upgrade does seem to have still gone through, but on a couple the RU host program is effectively deleted and required a reinstall.

I mean… no, it can be easily fixed by either allowing the file path to be typed in to a field, providing a text field for the license, or adding an option to specify it via the command line.

Adding the desktop experience bloats servers, uses more resources, and potentially increases your attack surface, not ideal and that’s why the default for servers is to not install the Desktop.

I can work around this for now but this, your lack of a Linux server, and the terrible mobile apps your software is really falling behind the competition.

Yep that's the one.

Conrad Sallian wrote:
I believe a fix in this case is installing the GUI. It will be needed anyway since RU Server is easier to use with GUI.

Not really, it works just fine without one and doesn't waste storage/resources.

I notice that the new server update has a note saying "Minor improvements to RU Server license registration mechanism." - I thought this might be a fix to the issue however it doesn't seem to have changed anything..?

Exactly the same issue using Windows Server 2019 - brand new server run up with nothing else installed. Thought it might have been a quirk with RDP or something but no luck directly accessing the server either.

Edit: having checked your video I can tell what the problem is - Windows Server 2016+ doesn't include Windows Explorer unless you install the GUI (Desktop Experience) and so you can't bring up the explorer window to select the license.

Surprised this hasn't come up before, I would expect that this would be the most common use case for the server.. Either way just needs to allow the license to be pasted in as text, problem solved.

In the meantime is there a way to add the key some other way? I installed it on a local machine, added the key, but can't find where it's stored so not sure where I'd go to move it to the server.