You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Windows 10/11 system
For a single user, I give access to a single remote machine. I set this as a mapping in MeshRouter.
I've been in the habit of placing the MeshCentralRounter.exe in the C:\Program FIles\Mesh Agent\ folder, and then saving the saved mappings to the desktop, so then when the desktop icon for mappings is double clicked the MeshRouter interface opens.
I've edited the saved mappings, adding a password, and then the user double clicks, then adds their 2FA code, and a VPN is created. Next to the saved mappings I save a RDP connection for the appropriate ports, so that the double clicking it will open an RDP connection to 'their' machine
Has worked really well, until the MeshROuter updated last week.
Users were told that they needed to upgrade to use the MeshRouter, but pressing enter generates this error
Perhaps we could set a directory to install the router into, same as we set a directory for the mesh agent to be saved in (same directory is fine by me), and optionally create a shortcut on the windows desktop.
The text was updated successfully, but these errors were encountered:
the error you are seeing is because the application is being run as a USER, rather than ADMIN.
User's dont generally have permission to copy/paste/download/etc directly into the Program Files folder (UAC)
so its best to store the exe elsewhere like AppData\Roaming maybe?
MeshAgent installs to that folder (or whatever folder I set)
Currently MeshRouter doesn't install, it is simply downloaded. It runs from downloads folder or desktop or where ever.
It makes sense to me for it to be installed to the existing mesh agent folder
plz can you try the new version of meshcentral 1.0.45?
it contains a new version of meshcentralrouter, which can be downloaded from the webui after update
Windows 10/11 system
For a single user, I give access to a single remote machine. I set this as a mapping in MeshRouter.
I've been in the habit of placing the MeshCentralRounter.exe in the C:\Program FIles\Mesh Agent\ folder, and then saving the saved mappings to the desktop, so then when the desktop icon for mappings is double clicked the MeshRouter interface opens.
I've edited the saved mappings, adding a password, and then the user double clicks, then adds their 2FA code, and a VPN is created. Next to the saved mappings I save a RDP connection for the appropriate ports, so that the double clicking it will open an RDP connection to 'their' machine
Has worked really well, until the MeshROuter updated last week.
Users were told that they needed to upgrade to use the MeshRouter, but pressing enter generates this error
Perhaps we could set a directory to install the router into, same as we set a directory for the mesh agent to be saved in (same directory is fine by me), and optionally create a shortcut on the windows desktop.
The text was updated successfully, but these errors were encountered: