Logmein technician console windows 10 download

Q: What about Windows 10 Mobile? Q: What updates do I need to make to be ready for Windows 10? A: No updates are required; you are all ready for the launch of Windows Q: Are there any new Rescue features associated with the Windows 10 update?

A: No, this update allows all current Rescue functionality to work with Windows There should be no change in the user experience whatsoever.

Q: Do I need to update my Rescue calling card? A: No, your existing calling cards will be updated automatically to work with Windows If you have previously requested the calling card to be locked down to a specific version, you will need to manually update. Q: Do I need to download anything?

A: No Rescue downloads or changes will be necessary to begin supporting Windows Q: Are there any other changes happening with Rescue? Additionally, you can view the System Requirements for Agents. Note: Agents will be prompted to log in with their account credentials once the application has installed.

For detailed installation instructions, please see below. GoToAssist Expert desktop application This is the main software that you use to host support sessions and connect to your devices i.

Note: If you remove the GoTo Opener application at a later time, you'll need to go through the entire download process each time you start a support session from the web app. Please fix this I end up having to use TeamViewer first so I can get in I can't send out a download like for the normal installer which in turn prompts for my credentials for my LogMeIn Central account. We are working on a new release that will correct this issue, we hope to make available very soon.

I will update this topic once a firm release date is confirmed. This is not your fault, but perhaps you could suggest to QHSE that from a quality perspective it would be worth obtaining early previews of the next Windows 10 Build to perform some testing against, to make sure LMI isn't caught out again, your customers would appreciate that and probably be willing to be involved in the testing.

I too would like an update on this ASAP. We need our customized installers when deploying LMI to customer machines. We can't be giving credentials to customers in order to log in and associate their machines with our Central account. If we have to use another remote utility first so we can connect, install, and enter the login ourselves, then why are we paying so much for LogMeIn? Here's our work-around for now.

When I first ran into and troubleshot this issue, I tried some older custom installers I had to see if they worked. Some failed just like these newest ones, but I found that one of our older installers did work — one I created in February of So for now I I've posted that old installer on our website for customers to download.

That old one properly associates the customer machine with our account and puts the PC into the correct group. Then the client detects that it has an update, the customer allows the update to be installed, and we're good to go. But that's still an extra step that of course shouldn't be needed, and it doesn't cover all situations in which we deploy customized LMI installers. I should've specified that the old customized installer I have that works does work on the April update to Windows 10, aka We have released a new version, the full release notes can be read here.