Download !NEW! Remote Desktop Commander Lite
Raphael Dyen
Read about how to extend Remote Desktop Commander Lite with amazing shadowing/remote assistance capabilities, the ability to delegate RDS management tasks to help desk staff without making them admins, and the ability to monitor multiple live sessions all from a single window.
I'm using the NPM version of Meshcommander (0.9.5-a) to connect to a headless Dell Optiplex 7040 from my Macbook M1 Pro. I have a HDMI dummy/terminator plug in the first video output of the Dell. Intel ME is version v11.8.92.
I tried rebooting the Dell from within ESXi. In Meshcommander remote desktop I see ESXi shutting down, and after a while of no updates to the screen, I see ESXi starting up. So I fully missed the boot splash screen and option to enter BIOS/EFI.
Any ideas what it might be? I am stuck. I'm thinking it either is something with the video not activated in the startup cycle or Meshcommander being unable to connect to Intel AMT during the startup cycle.
Edit: I have tried this from a Windows based PC at work and have been able to enable TLS (IDE-R works but slow) - perhaps it is a problem with the Mac version of Mesh commander? I have gone back to the Mac and TLS still does not work.
I followed the TLS video ( =PNpQV6C0Gb8 MeshCommander - TLS & Mutual-TLS - YouTube) for mesh commander, and the certificate is issued using the software for TLS, so I assumed it would work for MTLS also. I did not realise anything further was required (the video i used to successfully set up TLS doesn't suggest anything further) - I'll have a look at the document you link to when I get chance and see if I can find a solution.
My home workstation is equipped with Corsair Commander Pro and H110i and iCUE can controll these perfectly apart from when I remote desktop into my workstation, I get the the message "No Device Detected" :
Yeah ... I do the same thing. From what I understand, iCue disconnects when the workstation is locked. Since the workstation gets locked when you connect remotely with Remote Desktop, guess what? Yeah ... that.
So if the SDK app is running at work or at home and I remote desktop to the other endpoint, the SDK's emitted keys are recognized on the other computer and behave as such (which is pretty sweet). I do not suspect Cue has anything to do with that behavior, but possible worth noting.
I was looking into this for remote monitoring and I spoke to DevBiker about it and he said RDP didn't work with iCue at this time. I am have limited use of Window's consumer products. I mostly use Windows Server level operating systems. From what I just read Windows 10 does not support mutli-user mode or multipe/sessions. I wonder if it would work on Windows 2012 R2 or 2016? That is if the limitation is due to locking.
PS: not sure if it matters, but the native resolution of my client (local PC) is 3000x2000, the native resolution of the server I think is like 1920x1280 or the like, but in the remote desktop it works in the high dpi 3000x2000.
RDPSoft Remote Desktop Commander is what I use. It has saved countless hours of my life when I'd have to log into the RDP server, wait for server manager to load, and then shadow the session. I installed it on my desktop, added my terminal servers, and boom, could end sessions, shadow sessions, send messages...etc. They have a free trial
I'm trying to setup Intel vPro AMT KVM (Remote Desktop). I enabled AMT using the Intel SCS AMT Wizard. I'm now trying to use MCTME (shown in screenshot) to remotely connect to the computer. It works, but I need someone to read off an access code to me. This is what I assume to be "local user consent". When I try to disable it I get the error shown in the screenshot.
Attackers often gain entry to your systems via remote access. As a recent example, attackers took control of software at a US water treatment facility and changed the amount of chemicals entering the system. The computers used to control the water system were reportedly unpatched Windows 7 machines and using the TeamViewer desktop sharing software. The change was noticed and reversed quickly, but the incident underscored the potential to do harm remotely in other venues.
In this era of remote working, remote access is mandatory, but so is monitoring for access and ensuring you are protecting remote access. The FBI recommends the following steps to better protect remote access:
I recommend following guidance provided by Andy Milford in adding Sysmon to your remote desktop deployments so that you can better review and scan for attacks. You can use various configuration files to fine-tune the Sysmon configuration depending on your needs. Recommended guidance found on Github and elsewhere provides you with a solid start for monitoring events. The Sysmon configuration provided by Olafhartong maps the events to MITRE ATT&CK sequences to better target events where attacks will occur.
In reviewing my own Remote Desktop connections, you can see that cellular connections are often not shown as accessing from the city the user is located. Rather, it may show a regional location for the vendor. You may have to do additional correlations to determine if users are accessing remotely appropriately.
Finally, always add two-factor authentication (2FA) wherever you can. I use Duo to add 2FA to my remote desktop needs. Requiring users have something other than their username and password to access their resources will reduce risk from ransomware and other attacks.
When a Tosca Distribution Agent configured for unattended execution receives a test to execute, the Tosca RDP Server opens a remote desktop (RDP) connection to the agent. The Tosca RDP Server runs as a service on the same machine as the Tosca Distribution Agent. Once the agent has executed the test, the system closes the RDP connection.
This weekend, I was glad to have Intel vPro set up on some remote client machines. Windows had lost network connection (a DHCP issue) but fortunately vPro still had the most recent IP. I was able to use MeshCommander 0.6.3 to access the vPro Remote Desktop functionality.
Is there a way I can launch a RDP session to a remote Windows server, and perform a file transfer to the local computer? Versions of the remote Windows Server varies. Ranges anywhere from 2000 to 2008.
Thanks for all suggestions. Would like to add that the remote servers are securely locked down and I'm not allowed to install SSH servers, FTP servers, or shared drives. The only way for accessing the remote machine is through RDP, and these machines are also on separate VLANs to which only authorised users can use RDP to access these machines. I'm trying to create a script that can help authorised users to download the required files.
Once you have mapped the drives you want using mstsc, you can use \\tsclient to access the file system of the local machine i.e the Terminal services client from which you have RDP'ed on to the remote box.
Once you have mapped the needed drives as Andy says, you can execute remotely a LOCAL batch file every time you connect specifying it's local path (using \\tsclient\c to refer your local drive) in the Programs tab at RDP properties.
Remember to write cmd /c before that path.
The rdp connection will automatically close once the batch file ends, but you can add the pause command to the end to see what happened during execution.
2) If you are allowed to setup more than one user on the remote server, have a 2nd user and then have user2 session connect rdp session to user1. This will keep the user1's gui alive in the cloud without having to remain logged in to rdp locally.
Then use AmmyyAdmin AnyDesk on user1's desktop to connect and manipulate the desktop. This includes using AnyDesk's file manager's ability to browse any folder you need and copy. AnyDesk can be free if you connect via direct IP connection. Most vps servers have dedicated IP addresss or subdomain address so this should not be a problem. Good idea to password protect your AnyDesk login and which IDs have access to unattended remote connections. The AnyDesk file manager is a bit crude, but it works. Their big thing is simplicity and speed.
Note: Use portable mode only on the remote user's desktop; Do NOT fully install AnyDesk. Also, the CPU usage might increase to stream the desktop screen, somewhat related to the size of the RDP window. I am using 1280 x 2048 window with 4 cores and the CPU usage is 22-25% idle or moving things around. This might decrease if there is more video ram or graphics processor on the target server. But, if you only "browse files" (use only the file manager without streaming the desktop), CPU usage >0.3% idle and >1 avg% when transferring files (burst up to 5-6% when the file is finished uploading and the pieces are being finalized).
Running on a computer that is logged in from Remote Desktop, the local drives can be accessed on the remote machine under \\TSClient (If Remote Desktop is configured to show drives on the remote computer).
The Network virtual filesystem plug-in will detect if Multi Commander is running in a Remote Desktop session. If it is, and there are remote connected drives, a TSClient entry will also listed. It works in the same way as any other computer entry listed.
AWRC Pro allows you to remotely gather and manipulate more information than remote privileged users can dream about. It is by far and large the most powerful remote audit and inventory software you can find. And with its great set of tools, you can do virtually anything on the remote system you can on the local system.
Nowadays, connecting to a virtual machine in VMWare has multiple methods. You can do it through the VMWare workstation program, or use LogMeIn, TeamViewer, or other remote access software, or you can even do it manually.
PCoIP stands for PC over IP. It is one of the best remote connection protocols which provides adaptive technologies for the best user experience. PCoIP technology delivers a high definition and secures a remote access experience.
df19127ead