zerocredibility

Hi,

Is it possible to stop Windows session screens from locking? My company has a group policy that locks remote session screen after inactivity.

Is there a way to prevent this eg by simulating activity.

Failing that, is there a way to unlock automatically perhaps with a shortcut key.

Otherwise I have to either enter the password or reconnect to the session. I am running version 11.1

Regards,

Todd

Thanks. I have added the tool and entered the path to my powershell exe, but when I use it it connects but I just get a blinking cursor, with no prompt appearing - I left it for at least 5 minutes but no prompt came up - screenshot in attached document.

Also, how would I get this tool working if I wish to open a remote powershell to a server using different credentials, ie as below

$SecurePassword = 'password' | ConvertTo-SecureString -AsPlainText -Force

$Credential = New-Object Management.Automation.PSCredential 'Domain\administrator', $SecurePassword

Enter-PSSession -Computername Server1 -Credential $Credential

Cheers

This will be a basic question but I have to admit I haven't had much luck understanding how to create a tool.

I want a tool or session entry that opens a remote powershell session. Probably RDM already does this natively but I haven't been able to find it. Under 'Other' in Session Types there is a Powershell entry - maybe I just need help configuring that?

If that is not the right way to do it, how can I create a tool that would run the following script (this is the long-winded way I do it from a Powershell window in my PC now) - with a variable replacing the 'Server' name in the final line below:

$SecurePassword = 'password' | ConvertTo-SecureString -AsPlainText -Force

$Credential = New-Object Management.Automation.PSCredential 'Domain\administrator', $SecurePassword

Enter-PSSession -Computername Server -Credential $Credential

Do not assume I know anything in your answer - step by step instructions please! Thanks in advance.

To clarify, when I said a non-admin session, I mean a non-admin console session.

I have a non-admin microsoft rdp session set up - I want to reconnect to a recently disconnected non-admin session but RDM opens a new session instead.

See attachment/image - I have started a new ID 3 when I wished to reconnect to ID 1.

Is there somewhere I can specify to reconnect to a specific ID number, eg 0 for admin console?

I'm running latest RDM on Windows 8.1

Thanks,

Todd

Brandur, I am not running 64 bit version, I noticed that is not recommended yet. Thanks for info on your setup, looks foolproof.

Maurice, I guess the reason I stored it in system32 is because "thats the way I've always done it". An excellent reason, to be sure!

I suppose I've always put things in system32 because then they are found no matter which directory they are called from.

I have now moved them to same path as you use and added that path to the PATH environment variable and everything works fine.

I do have a couple more questions:

1. This one is nitpicky but when opening the remote command prompt on a session linked to a vpn it doesn't open the vpn first. Either the rdp session must be open or the vpn must be started manually first. Can I set it up so it will check for the vpn, open it if needed, then run the psexec tool?

2. The remote command prompt logs me on as the session user. How would I change this to a different user, for example with domain admin permissions. Manually, the command would be psexec \computername -u <username> -p <password> cmd /k. I thought I might be able to do this by selecting the 'Run as different user' checkbox within the tool, but that did not make any difference. Am I best to set this up as a separate tool?

Thanks

Todd

Auckland, New Zealand

Hi, new user here.

I'm trying to open a remote command prompt on an standard rdp host session. My PC is running windows 7, I am running latest RDM Enterprise version.

Steps I have taken so far:

Unzipped the pstools suite to my system32 directory

Imported the 'Remote Command Prompt' tool using Macro/Script/Tool Manager - this has a green tick next to it

On the properties of the tool, I have checked the 'Run as Administrator' box

When I run the tool against the session entry, a UAC warning comes up "Do you want to make the following changes?" The details of the warning are:

Program Location: "C:\Windows\SysWOW64\cmd.exe" /k "C\Windows\System32\psexec.exe" <HOSTNAME> cmd.exe /k - note that the cmd.exe is being opened from my SysWOW64 folder.

I select the Yes button.

The following error comes up:

'C:\Windows\System32\psexec.exe' is not recognized as an internal or external command, operable program or batch file.

If I exit RDM then open the syswow64 cmd.exe outside of RDM and run psexec the same error occurs. But there is no problem running it from the cmd.exe within the System32 folder.

The only way I have found so far to get the remote command prompt tool to work within RDM was to copy the psexec.exe file to my SysWOW64 folder.

Will I have to do this with every tool? Does anyone have a better way?