Path is not Working Remotely as Expected
Hello,
We were able to reproduce this issue internally. We've opened a ticket and will let you know once we have an update.
Regards
@Jonathan Del Signore
thanks
Path is not Working Remotely as Expected
i'm trying the Setup a path Entry like this
\\appreconsp01\c$\CoronaCS\7.9\mss\demo\Cards\Batch\logs\
and its not working as Embedded Tab, its only working fine externally
Remote Windows Services
this is great , its fine , i thought its should be in a somehow seperate way/item, but this is fine ,
yes you are correct , i'll never RDP to that Server, i just want to check services remoteley
IBM MQ Entry
it would be really nice if we got a new type of entry for IBM Message Queue Hosts,
Remote Windows Services
Hello,
Good news - this is already possible! 😎
You can find this section in the Macros/Scripts/Tools Dashboard of the respective session.
Regards,
Min
@Min Destens
thanks for your interest, but what i'm looking for is to manage services for Remote Server/PC
Remote Windows Services
it would be really nice if we got a new type of Entry to manage remote Windows Servers Services, instead of opening that server via RDP and manage its service within the session,
RDM version 2026.2.5 - PowerShell session with Windows Terminal problems
We're building 2026.2.10 today, so it should be available either tomorrow or wednesday.
excellent , thanks @Jonathan Del Signore
Add a new Type of Entry WSL
just like a Windows Terminal type of Entry, but it just launches WSL (Windows subsystem for Linux)
Windows Terminal is no more working
Hello,
Thank you for your response.
I can confirm that this issue is expected to be resolved in version 2026.2.10.0, which is scheduled for release soon. While we do not have an official ETA at this time, we expect this version to be released during this week.
We will keep you updated on any developments.
Best regards,
thanks @Tommy Sanders
Windows Terminal is no more working
Hello,
Thank you for contacting us regarding this matter.
Could you please provide some additional details about the issue you are experiencing?
Specifically:
Are you receiving any error messages? If so, please share the exact message.
Do you have any relevant application logs that you can provide?
Which workspace and datasource are you using?
Are other users experiencing the same issue, or are you the only one affected?
We look forward to your response.
Best regards,
Hello @Tommy Sanders
i think this is related to this Ticket
RDM version 2026.2.5 - PowerShell session with Windows Terminal problems
RDM version 2026.2.5 - PowerShell session with Windows Terminal problems
Hello,
This issue will be fixed with version 2026.2.10.0.
Regards
@Jonathan Del Signore
Hello
is there is expected date for this
Windows Terminal is no more working
Hi Tommy,
Are you receiving any error messages? If so, please share the exact message.
nop , it just opens for a sec and closes again
simpley , you can reproduce it by just selecting (Tools -> Windows Terminal)
Do you have any relevant application logs that you can provide?
nop, but if there is way to allow more logs or to locate it , i'm welcoming for sure
Which workspace and datasource are you using?
i used it just for my personal usage
Are other users experiencing the same issue, or are you the only one affected?
only me,
RDM version 2026.2.5 - PowerShell session with Windows Terminal problems
just downloaded 2026.2.8.0 64-bit (PreJIT) and the issue still exists
RDM version 2026.2.5 - PowerShell session with Windows Terminal problems
i got the same issue, I'm not able to start any windows terminal or PowerShell terminals any more after last update
Could not access starting directory
whenever i start session that is locally a PowerShell , i got the following error
[error 2147942667 (0x8007010b) when launching `"C:\Program Files\PowerShell\7\pwsh.exe"']
Could not access starting directory "E:\BIN""
Windows Terminal is no more working
all sessions based on (Windows Terminal ) is no more working after (2026.2.7.0 64-bit (PreJIT)) update