How to best use Remote Desktop with Actual Window Manager? - Форум «Technical Support»

Новости

15.05.2019
Выпущены новые версии продуктов

21.08.2018
Выпущены новые версии продуктов

03.03.2018
Выпущены новые версии продуктов

20.06.2017
Выпущены новые версии продуктов

28.03.2017
Выпущены новые версии продуктов

Главная / Форумы / Technical Support

Тема: «How to best use Remote Desktop with Actual Window Manager? , Is there a way to pause AWM when connecting with RDP? » в форуме: Technical Support

Jim

Всего сообщений: 51
Дата регистрации: 07.04.2010

Создано: 29.05.2019 02:27:40

My workstation has 4 monitors. I frequently have to connect to it using my laptop, or my phone, over Remote Desktop. In either case that means I'm dropping from 4 monitors, to just 1 monitor that is also lower resolution than any of the 4. This makes my Actual Window Manger window rules / transparency, etc - a mess on connection and disconnection.

Right now I've been just pausing AWM when I connect via RDP, and then I unpause it when I'm next at my workstation.

But I'm guessing there is a better way to do this? Can you automated the pause/unpause when connecting via RDP? Is there a way to setup rules that only apply on connect/disconnect, etc?

Basically I'm looking for suggestions and ideas on this topic. Thanks in advance!

Наверх

Bogdan Polishchuk
Администратор

Всего сообщений: 4113
Дата регистрации: 04.04.2012

Создано: 10.06.2019 22:35:01

Hello, Jim

You can achieve the automatic pause/resume or switching to other configuration using the combination of Windows Task Scheduler and shell command script containing the commands for Actual Window Manager.

You need to create two .cmd Command Files - one for remote connection and other for local access. Launch Notepad and type the commands specified below, then save your file with a name of your choice BUT with an extension of .cmd. Make sure that the Save as type is All Files, and Encoding is ANSI.

If you want to pause/resume then type the following script commands:

file 1 - pause script commands:

Код
PUSHD "C:\Program Files (x86)\Actual Window Manager" ActualWindowManagerCenter.exe suspend POPD

file 2 - resume script commands:

Код
PUSHD "C:\Program Files (x86)\Actual Window Manager" ActualWindowManagerCenter.exe resume POPD

If you want to use different configurations for local and remote access, create two .cmd files with the following commands, where <backup_file_name.zip> is the full path and name of the .zip file with respective configuration (you can create them by adjusting the settings in the configuration module for local and remote access and saving them using the Backup Tool - configuration module > Tools > Configuration > Backup):

restore the configuration script commands:

Код
PUSHD "C:\Program Files (x86)\Actual Window Manager" START /WAIT ActualWindowManagerCenter.exe restore <backup_file_name.zip> POPD

Then you need to create two tasks in the Windows Task Scheduler to run these files automatically when you connect to the computer remotely or locally: open Task Scheduler, click "Create Task...". You need to specify "On connection to user session > Connection from remote computer" as trigger for the first task and "On connection to user session > Connection from local computer" for the second. Add a new action for each task and specify the respective .cmd script for each (pause and resume or restore different configurations).

Once you create the tasks, Actual Window Manager should pause and resume or use different configuration automatically as soon as you enter the system remotely or locally.

You can learn more about the AWM program command line parameters here.

Let us know if you're able to use this solution succesfully.

Best regards.