Support Response:
Is it possible that these missing machines may have been powered-off? There is a key value ("SelfInvitationExpireSeconds") in the web.config to remove any machine that has not had any session activity in the previous 24 hours. Once one of these machines is powered-on again, it should reappear on the list of Unattended sessions.

Support Response:
While there is no way to do this out-of-the-box, this forum post may help you out: Is there a way to restrict the IP address?

Support Response:
Our licensing is concurrent, so if you own two licenses then you can have two active simultaneous sessions; if you have three you can have three, and so on. We also sell an unlimited concurrent license which is the price of ten concurrent sessions. Our trial license supports two concurrent sessions, so if you are a trial customer you should be able to open two at a time.

We also support pausing sessions, so you can have customers connected to sessions and you can jump from one to the next using just one license. This can be done by hitting “x” on the host client but choosing “no” when we ask if you want to kill the session. This will keep the guest connected (no license required unless both parties are connected), then you can reconnect by clicking join. The first time you connect may take 20-40 seconds, but the second time takes only 2-3 seconds.

Support Response:
Currently the central web application, which is what you are downloading, has to be installed on a Windows system with .NET 3.5. Once that is set up on the computer/server/VM/VPS of your choice, you can access and use the software from Windows, Mac, or Linux. For technicians we also support Android and iOS mobile devices.

To explain further, ScreenConnect is configured into 3 pieces: the centralized web application that manages the sessions(Admin Client), the host client that is deployed to your technicians when they host/join a session, and the guest client which is deployed to the customer when they join a session.

• Admin Client - The centralized piece that you download from our website plays the role of admin for the host and guest. This piece does need to be installed on a Windows computer or server. This software is not very demanding and therefore does not require a server to work; a standard computer is sufficient in most applications. It manages the sessions and provides the configurable URLs that your host and guest use to connect to the software. The Admin Client is a web application, when installed it provides several configurable URLs that you can modify to integrate into your website and support process. Once configured you can provide the URLs to your technicians and clients so they can host or join sessions.
  
• Host Client - The host/technician will navigate to the Admin Client via the URL (mentioned above) and are provided 1 of 3 clients automatically when they create/join a session. The host can run sessions from their computer or mobile device including the following operating systems (Mac, Linux, Windows, Android, and iOS).
  
• Guest Client - The guest/customer are provided their client when they join a session. Guests can join sessions from their computer including the following operating systems (Mac, Linux, Windows). Guests join the session by navigating to the Admin Client via a URL that you provide them or via a link in an email.

I would recommend looking at our How It Works video, I believe it can explain a bit further. The video is being updated to reflect the new software UI, but the general principles all still apply.

I hope this helps answer your question. We would love to offer this hosted on Linux, and hopefully will soon but we are finishing a few projects that will improve functionality and close up gaps that our community frequently ask us to deliver. Many of our customers who don’t have a Windows computer or server where they can host the web application will utilize a cloud VPS service like ThrustVPS, GoDaddy, Rackspace, Amazon, or other. These services range in cost from $10-$60/month and from what our customers tell us work very well.

Support Response:
We’ve had no reports of any problems hosting ScreenConnect sessions from Android 3.2; you just need to install the app from the Marketplace beforehand and all should be fine.

If you set up your ScreenConnect security to use Windows Authentication and plan to use the Android application, then you’ll also need to be using SSL on the ScreenConnect Web Server piece. Android only supports HTTP Basic Authentication, which is clear text, so the whole channel needs to be encrypted with SSL for your passwords to be safe.

The easiest route, given that you are just trialing the product now, might be to change to Forms authentication in ScreenConnect (Administration page, Security tab). Once you change to Forms, you can create your own usernames and passwords and use it with Android without a problem.