Windows 10: MSTSC from Mac

I installed Microsoft Remote Desktop on my Mac and created a configuration called "pc" unter the "PCs" tab. Can I run MSTC from command line and connect to "pc" automatically as a command line parameter?open "/Applications/Microsoft Remote Desktop.app"

:)

 

MSTSC Not working?


Helo everyone,I have some problems with mstsc.
So I have 2 windows 10 pro PC,one with good specs and one with fair specs.
Both of them are in same LAN.
I tried to use one of them as a server for Minecraft (a famous game)
I just can't connect to it,I have disabled firewall,added user to the list,connectec to internet.
I tried to connect to my second PC's IP but it still failed,neither connecting with its full name.
Someone please help and I will appreciate your help! <3

 

CLI mstsc errorlevel

Thanks for the suggestion. Unfortunately we have a strictly controlled environment so I have to try to work with standard windows tools. I was working with call and then netstat to check for an active connection to the right server, but the question is
the timing, when to kick off another mstsc. It would be simple if there was just ONE connection, so tasklist would work, but since we may have more than one connection at a time and I can't determine how to use tasklist, even w. /V to identify the specific
process kicked off by the current iteration. Again, thanks for the suggestion.

 

CLI mstsc errorlevel

I have an issue trying to connect to a remote system with mstsc. Occasionally it times out. I have a rough outline of a decent bat to try to connect, then try again if mstsc fails. The issue that's complicating matters is that once mstsc is executed even
if it fails to connect I get errorlevel 0.

As an experiment, I tried to connect to a non-existent system. I got the popup re: Remote Desktop can't connect to the remote computer for one of these reasons: but the bat thought it was successful. As an experiment I tried a more direct test with the
test code below from my beta bat, which displayed IT SAYS IT DID WORK.

start /WAIT mstsc %srv%.rdp /h:1280 /w:1024 /v:%srv% /prompt && echo IT SAYS IT DID WORK

if I tried the reverse, it did NOT return the expected error message.

start /WAIT mstsc %srv%.rdp /h:1280 /w:1024 /v:%srv% /prompt || echo IT SAYS IT FAILED

Of course I also echoed the errorlevel, and it's 0 whether or not I actually connect/log in.

Am I missing something? Does anyone have a non-powershell method to actually determine if mstsc fails?