I'm sorry, but we only distribute the mobile version via AppStore. Also, as you say that you cannot install it on iOS 7, I will contact our developers, clarify the current system requirements and update those on the website.
Thank you for your report. Actually, a lot of applications stopped working all of a sudden when Apple released their 9.01 update :| We did our best to update the app as soon as possible, and it took some time for Apple to review and approve it in the AppStore. They were very busy with this, as it seems, due to a lot of developer updates released at the same time.
Now we are continuing to fix some issues because Apple released the 9.1 in the middle of the approval of our application. So it seems like it will take use other few days to re-iterate with this.
I understand the premise of having it ask for the password; however, I was thinking that if the person has physical access to the machine then they could disable the function. It doesn't sound like it from how you describe it so I'm hoping for option #2!
No, this would be in violation of the common interface conventions. Whenever sensitive information such as a password is changed on a device, the user must provide the old password first. Otherwise, there is a security breach that could be exploited.
If we delete the current address book that is built on the server and create a new one, will the remote clients auto-populate the new book? Do they care or know that they are in address book "XYZ" and I deleted XYZ and created ABC. Will they simply start populating ABC?
By remote clients you mean other Viewers, correct? If so, you update the address book on the server by updating it in one of the Viewers, the address book on the server will then overwrite other books on other Viewers. At least that's how it works in theory.
Still, we are currently seriously improving the whole mechanism and the beta is coming soon. The only thing you should remember at all times in order to be safe is that you should back up your address book. By default the Viewer does that automatically for you though unless you changed the back up setting in the Options, but those backups are daily ones. So before you make any critical changes like updating the book on the server, it is recommended that you first back up your address book in the Viewer using "Export connections" option.
Is there a way to change/reset the password given in "address books settings"?
If I turn off the password, it ask for the old password - which is not available. How can you force reset it OR turn it off without loosing the address book?
It asks for the old password because the program needs to know that you are the person who is authorized to change the password. Otherwise anyone who has access to that PC with RU Server installed could change or reset the password which would make the whole idea of password protection irrelevant.
Which brings me to another question, if I have to destroy the address book, and create a new one, will the clients register with the new book?
Sorry, I didn't understand the question. Could you please clarify what you exactly mean by saying "will the clients register with the new book"?
I'm sorry to hear that version 6 didn't work out for you. However, I should add that saying that it does not work is a bit of an exaggeration. We have hundreds of paid customers of version 6 who are happy with the product. I'm sure that had they have issues they would have immediately let us know about them. They never hesitate to do so :)
Still, as our customer, you can continue using version 5 forever if you are happy with it. We can provide the old version for download.
1) paying for 5 licenses then they decide to give it away for free.
This did not affect customers who purchased their licenses previously in any way. Even now everyone can still purchase 1-10 licenses although there is a free license for up to 10 remote pcs that has the same capabilities and functionality.
2) version 5 worked perfectly, version 6 has too many issues to list and is unusable to me in its current state.
Sorry, but version 5 had a lot of issues , it's simply that they did not manifest themselves in your specific use, but they were reported by other users. Just take a look at the "fixed" items in the release notes.
If there are any specific issues you have with version 6 we would be only happy to help.
We can only regret that this update alienated some customers, but we had to do what we've done. Only a few months ago before this update we had a dozen false positives from various a/v programs, whereas now there's almost nil.