First, double check if you have the latest Viewer installed and Host package downloaded. As of now, March 4 2014 the latest version is 188.8.131.52.
Secondly, make sure that you don't do any prior configurations on that Host file , because the default option for the Standard MSI option is to overwrite the Host package. So you might end up with an already configured Host package accidentally. In other words, it should be a purely vanilla Host package freshly downloaded from the site.
David wrote: Can you please post the MSI GUID for each of your products and versions? I'd like to automate or script the Host uninstall process. I think it would benefit the those of us that use this tool in the enterprise.
We'll see what we can do and I'll get back to you in this thread.
On another note, I tried to search the KB for the GUIDs and obviously couldn't find them, but I came across this very strange issue with the search function on your site. When I searched the KB for the term "msiexec" (without quotes), the search failed and said that I didn't enter any valid characters. The search box then showed "ьышучус". I obviously didn't search for non-English characters from the character map. Off the top of my head it looks like the data getting passed through the search box isn't getting sanitized properly. Anyway, I just figured I'd pass along the info so your web developers can take a look
Ok, we'll check it out.
Edit: Oh no... The last 4 or 5 posts to this forum look like bad news...
There has been a lot of spam recently on the forum and we clean it up day and night :)
I read that you plan to implement a web-based account system ... Can I presume that this will also display the meaningful computer names, instead of the Internet ID numbers?
Yes, not just with the web based system (it requires some time and effort before we implement one) but in the nearest mobile updates.
Finally (correct me if I'm wrong), when entering the Internet ID, it seems like it's CaSe sEnSiTiVe. These IDs are hexadecimal characters (I think), so the A-F's should not be required to be entered in uppercase.
We'll think about whether it is possible (code- or architecture-wise) to make it non-case-sensitive.
Again, thanks very much. It seems like you've done all the hard work getting the functionality and speed. It's just the UI (and management of Hosts) which is surprisingly lacking obvious functionality (with the greatest respect).
You are welcome :) We are aware of the reported issues and suggestions we are given and we do our best to gradually implement them.
Thank you for the report. It looks like BitDefender categorizes our software as "potentially dangerous". Sometimes the term "not-a-virus" is used to distinguish potentially dangerous software from viruses.
We have already contacted BitDefender regarding this issue. We also encourage you to send a false positive report yourself.
It would be nice if the chat session (including history) didn't just disappear when the chat session is either closed by the remote user, or when there is a network failure that temporarily disconnects the Host fr om the Viewer. In instances such as these, I'd like to be able to retain the chat history on screen and be able to pick up wh ere I left off once the network communication resumes.
Chat history is already on our roadmap.
Additionally, as an admin I'm always using the keyboard. Having to stop and use the mouse to click the "Send" button is cumbersome. If the chat window uses Windows Forms, setting the "Send" button as the default element on the form would remedy this. To overcome the fact that you would not be able to enter multi-line chats, just have something like Shift+Enter create a new line in the active chat, while keeping Enter to send the chat message.
Is there a Host Setting I missed that needs to be set to enable access from a mobile device?
No, there's no such setting.
I forgot to add that I'm using desktop Version 184.108.40.206 and the latest Android version on both devices, and that I'm trying to connect using an Internet ID, which I am able to do with no problem from a desktop Viewer.
We'll have to wait until the next mobile update is out, because currently there's no logging in the mobile Viewer which would help us diagnose the issue. Sorry for that.