Change xdrp resolution - kde-plasma

I currently use Windows RDP to remote into my Ubuntu desktop running KDE and xrdp. When I do this from my desktop the resolution is fine. When I remote from my laptop the resolution is too small. Is there a simple way to change the screen resolution when I remote in from my laptop?

For Windows RDP, look for the 'Options' button on the lower left side of the connection window. Then switch tabs to 'Display'. Then adjust the slider and try connecting after making the change.

In "Remote Desktop" on Windows. Choose the remote PC that want to set the resolution...
Step 1: >> "···" >> "Edit"
Step 2: >> "Show more"
Step 3: In "Display settings" >> "Set my remote session resolution to:"
Step 4: Select the resolution you want (e.g. 1920x1080)
Step 5: Back to connect the remote PC
[ All Done! ]

Related

The console has been disconnected. Close this window and re-launch the console to reconnect

I am having an issue when trying to open to any VMs using "Launch Web Console" option via the vcsa 6.7 . I was wondering if someone could please point me in the right direction?
My environment currently looks like this:
1) vcsa 6.7
2) Three Esxi (6.7) Hosts & multiple vms are running (including windows & Linux)
Whenever I try to connect to the console, I get the following error:
The console has been disconnected. Close this window and re-launch the console to reconnect.
Console access is given through a connection to the ESXi host.
Often times I receive this message when connected to the console of a VM which has vMotioned to another host. However, I can close and re-open the console just fine.
You may also want to verify that you can access port 902 (TCP & UDP) for each of your three hosts. Example of this requirement: https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.install.doc/GUID-5071C86E-FF1E-4E54-A424-A20917401160.html
I had the same exact problem and unfortunately, the solutions I found on the internet did not solve my problem. I had to re-check my settings and found out that the problem was the proxy setting was ticked on. which it won't allow you to connect to any others services as well if you are out of range of that proxy. The Solutions "FOR MAC USERS" as follows:
1-Go to your network settings.
2-From the menu down to the right-click more options. in my picture say (Weitere Optionen) "German".
3-From the menu on the left side make sure that the proxy option is 'unticked' (not chosen).
Then click on to confirm and enjoy using your VM service. Hope this would solve your problem as well as it did to mine.
See pictures!
https://i.stack.imgur.com/1PjjP.jpg
https://i.stack.imgur.com/1jnJf.jpg
https://i.stack.imgur.com/8XiAY.jpg

How can I emulate pressing CTRL+ALT+PAUSE in my Linux VM using AutoKey?

Question:
How can I emulate pressing CTRL+ALT+PAUSE in my Linux VM using AutoKey?
I tried a script that has
keyboard.send_keys("<ctrl>+<alt>+<pause>")
in it. But it does not work.
Background:
I'm using Windows 10 and RDP to log into a Fedora Linux. Switching 100 times a day.
The RDP connection runs in Windows all the time.
If the RDP window is not in the background but active, I can press CTRL+ALT+PAUSE to go into the VM (Fullscreen). If I am inside the VM I can press CTRL+ALT+PAUSE to go back to Windows.
So far so good. I want only one button. Preferably PAUSE. Windows part is ready already with following script
Pause::
If !WinExist("RDP Tool Name")
MsgBox No Window found
WinShow, RDP Tool Name
WinActivate, RDP Tool Name
Send ^!{CtrlBreak}
Return
Is the Linux part maybe not possible because the key combination is cached somewhere before my Linux system can even notice it? Any ideas?
I solved it without any other new script. I just had to edit the RDP settings: Keyboard -> Use Windows-Hotkeys -> On this Computer

Windows 7 Ent login loop

I have a Windows 7 Ent - 64bit system.
I am stuck in a loop, where the login screen is presented, i enter my network credentials, the welcome spinner is shown, the screen flickers like when resized, then the system goes to logging off screen and then finally goes back to the control alt delete screen.
I cannot get out of that loop for the life of me.
I contacted corp support, he came over and logged in using his login (admin level) and was able to get a desktop up.
The support people are not allowed to access the registry to correct or even look at my users settings, and my user IS NOT AN ADMIN on this machine.
Question is - is there a way to blow away my profile on this machine, or reset my registry branch to that of a new user or something???
i have bitlocker enabled on the drive - so using the emergency boot disks are almost rendered useless...
im stuck, and i dont know where to look....
any ideas would be wonderful
thanks
the admin level user logged in, and turned his back for a moment, and i was able to go in and reset the autologon registry entry...
rebooted,and all is well.
Disconnect Your USB Devices
If you like using all sorts of USB devices such as the mouse, keyboard, speakers, Bluetooth speakers, USB dongles, USB Wi-Fi adapters etc. However, these connected devices might cause the Windows 7 stuck on the welcome screen for a long time issue. Therefore, a common solution to the problem is to disconnect all externally connected devices from your PC.
Disconnect from the Internet
Sometimes Windows 10 gets stuck on the login screen because it's trying to connect to your wireless connection. If your Windows gets stuck on the welcome screen, you should make sure that you are not connected to the internet before proceeding to log in.
Run system checks
In some case, corrupt system files on your computer will cause this problem – stuck on welcome screen Windows 10/8/7. Therefore, to fix the Windows 10 freezes on startup problem, you can use CHKDSK to run some checks on your computer to see if it is the corrupted files that cause your startup problem.Restart Windows Update service
You can try restarting Windows Update service and then rename few files if you still get stuck on welcome screen Windows 10 issue.
Here are the steps:
Step 1. Open command prompt.
Step 2. Type net stop wuauserv in the run dialogue and press Enter.
Step 3. Type cd %systemroot% command and press Enter.
Step 4. Type ren SoftwareDistribution SD.old and press Enter.
Step 5. Type net start wuauserv and press Enter.
Step 6. Type exit and press Enter to close Command Prompt and restart your PC.
Step 7. Now, reboot your PC/laptop and check if the stuck on welcome screen has gone.
Restore Windows by using System Restore
System Restore is a useful feature that allows you to restore your operating system to a previous state and fixes any boot problems such as Windows 10 freezes on startup, Windows 7 hangs on welcome screen, etc.

Java Robot Code does not work when remote desktop window is not active

I'm running some selenium tests on a amazon cloud machine. My web application has a flash area where i'm simulating a keyboard type and click using java robot code (also tried auto it script to simulate user click and type on the flash area) . The code works when i connect to the server using remote desktop and the remote desktop window is active, but when i minimize the remote desktop window, the java robot code does not work?
Robot robot = new Robot();
robot.delay(5000);
robot.mouseMove(400, 400);
robot.mousePress(InputEvent.BUTTON1_DOWN_MASK);
robot.mouseRelease(InputEvent.BUTTON1_DOWN_MASK);
robot.delay(2000);
robot.keyPress(KeyEvent.VK_H);
robot.keyPress(KeyEvent.VK_I);
robot.keyPress(KeyEvent.VK_SPACE);
robot.keyPress(KeyEvent.VK_B);
robot.keyPress(KeyEvent.VK_U);
robot.keyPress(KeyEvent.VK_D);
robot.keyPress(KeyEvent.VK_D);
robot.keyPress(KeyEvent.VK_Y);
Issue is not with the scripts, but with the host machine's GUI settings for remote machine. To fix this, perform the following steps on the computer from which you are connecting to a remote workstation :
Configuration for current user only:
Run the regedit.exe tool.
Find the registry key HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client.
Create a DWORD value with the name RemoteDesktop_SuppressWhenMinimized and set its value to 2.
Now find the registry key HKEY_CURRENT_USER\Software\Wow6432Node\Microsoft\Terminal Server Client.
Create a DWORD value with the name RemoteDesktop_SuppressWhenMinimized and set its value to 2.
Close the regedit.exe tool.
Configuration for all users:
Run the regedit.exe tool.
Find the registry key HKEY_LOCAL_MACHINE\Software\Microsoft\Terminal Server Client.
Create a DWORD value with the name RemoteDesktop_SuppressWhenMinimized and set its value to 2.
Find the registry key HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Terminal Server Client.
Create a DWORD value with the name RemoteDesktop_SuppressWhenMinimized and set its value to 2.
Close the regedit.exe tool.
Now when you minimize the Remote Desktop Connection window on your computer, this will not affect the remote computer’s GUI and the GUI will be available to your interactive tasks.
I installed UltraVNC Server and connected using VNC client. The problem is not observed and the robot works even after disconnecting. Below is the exact steps:
Login to the remote machine using Windows Remote Desktop tool.
Install UltraVNC server as a Windows service.
Log off from the system (you are still within the remote desktop tool).
Now using VNC viewer, connect to the system.
You will be shown the login screen. You can login to the system using vnc viewer now.
Thanks, Daniel,
This resolved the issue we had while running a Synthetic Scenario where we need to use Robot Framework to perform some mouse clicks while the RDP Session is minimized.
Best Regards,
Buddhika.
Germain UX: Custom Insights, Alerts, and Automation platform to improve User Experience

Symbian Emulator start and disappear

I am new with Symbian. I downloaded Symbian SDK, Active Perl 5.6.1.635, and Carbide C++.
I tried to create a Hello World Project but whenever I execute the emulator appears, shows loading and then disappear.
Any clue?
Do you have Realtek sound chip on your PC? Try to disable it in windows device manager and try again. This is most common issue in the behaviour mentioned.
Also please refer to %temp%\epocwind.out for emulator log. Reasons of failures and panics can be found there.
EDIT:
Regarding on-device debugging:
Connect phone to your computer with USB cable.
You should have Nokia Ovi Suite or Nokia PC Suite installed, because you gonna need USB drivers for the phone;
Then go to Carbide, select debug target (GCCE UDEB) and click "Debug".
In the opened window titled "Debug As" select "Symbian OS Phone or Simulator launch";
In next form click button "Change" in "Connect to device" section;
Add new connection;
In the new connection form, go to "Install Remote Agents" tab, select Nokia -> 9.2 -> Application TRK 3.2.8 and click "Install";
Then return to "Setup Connection" tab, choose connection type USB and then select virtual COM port allocated for phone USB connection.
You can make sure that connection is ok by going to "Test Connection" tab, selecting TRK and clicking "Initiate Service Testing".
Connection should be set up for now, so now you can setup the build of SIS file, which should be deployed to the phone for debugging purposes. For this, in the opened window "New Launch Configuration Wizard" click button "Change" in "Debug process" section, and then, in "Deploy method" section select your SIS file in "SIS file to install" combo box. If you don't have any SIS files yet, refer to this page.
Once you have all this stuff set up, you can start actual debugging. Hope this helps. :)