Having some issues figuring out automation for RDP on win10. Would appreciate any tips you guys got.
What I am trying to accomplish:
Use an AutoIt script to:
Open a remote desktop connection
Check 'Don't ask me again for connections to this computer', click
connect
Allow for remote desktop to load
Disconnect
Attempted to run the remote desktop connection with mstsc.exe, but got the error
The shortcut name is
My code so far
Have also tried Run("C:\Users\Public\Desktop\RDP Consoles\administrator#windows-1") to no avail.
Anyone know why I am getting this error? Or of a better way to perform this task?
Run() actually starts a cmd process, so you have to obey the rules of cmd too.
cmd expects filenames with spaces (and some other "poison chars") to be quoted (and it has to be double-qoutes). In your example, you run mstsc with two parameters: C:\Users\Public\Desktop\RDP and Consoles\administrator#windows-1. To make it one parameter, quote it. Best practice: also quote any paths or filenames (to again avoid problems with spaces):
$x=Run('"C:\Windows\system32\mstsc.exe" "C:\Users\Public\Desktop\RDP Consoles\administrator#windows-1.rdp"', '')
Nope. On my Win 7 Ultimate and my Windows Server 2019 it sure works this way:
Run("C:\Windows\system32\mstsc.exe")
WinWaitActive("Remote Desktop Connection","")
Send("Put your Remote Desktop IP here")
Send("{ENTER}")
WinWaitActive("Windows Security","")
Send("Put your Remote Desktop user name here")
Send("{TAB}")
ClipPut("Put your Remote Desktop password here")
Send("^v")
Send("{ENTER}")
Related
i got following cmd command, i want to start an .exe installer with this, but when i execute it the message after it pops up.
START "DSM-Agent setup..." /WAIT /D %PATH% InstallClient.exe
The Message:
I already tried adding domains or something to the registry but nothing worked.
This is in an automation script, so the message is very deal breaking.
I hope someone can help me.
Additional Info:
The script should run on Windows Server OS
The exe is on another server
Are you running it from a network location?
This is the reason for the message.
The network share is not trusted by your computer, so it warns you.
You need to add the network server to your trusted servers:
In Internet Explorer:
Internet Options → Security tab
Local Intranet → Sites
Check Automatically detect intranet network
Advanced → Add this website to the zone:
Enter → file://path → OK
** You need to restart explorer.exe for the changes to take effect
All the computers in our company are configured with a custom protocol that runs a vbs script, so when you click on a link with that user protocol, the vbs script starts and performs operations that interact with the file system and applications otherwise inaccessible to the browser.
This is the .reg file used to register the protocol:
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\<name>]
"URL Protocol"=""
#="Url:<Description>"
"UseOriginalUrlEncoding"=dword:00000001
[HKEY_CLASSES_ROOT\<name>\DefaultIcon]
#="C:\\Windows\\System32\\WScript.exe"
[HKEY_CLASSES_ROOT\<name>\shell]
[HKEY_CLASSES_ROOT\<name>\shell\open]
[HKEY_CLASSES_ROOT\<name>\shell\open\command]
#="C:\\Windows\\System32\\WScript.exe \"C:\\Program Files\\<name>.vbs\" \"%1\""
The script has worked beautifully since 2014 without problems on ~50 computers.
Last week one user complained that it stopped working. I found out that WScript.exe doesn't work anymore, so I copied it creating WScript2.exe, modified the custom protocol to run WScript2.exe and it restarted working.
This morning also my computer didn't listen to the clicks on my custom protocol. I made a copy of WScript.exe to WScript2.exe and it restarted working.
I am expecting my phone to start ringing soon.
Why did WScript.exe stop listening to the custom protocol?
Why its identical copy still works?
EDIT (answers to comments)
Perhaps if I knew how to better describe "it stopped working" then I would know how to fix it :)
I don't know if it stopped working because of a Microsoft update, an anti-virus update or a change on the IT infrastructure/configuration. Here is a quick summary of what led me to the workaround:
I compared my custom protocol to a working one, I picked mailto as a reference
I noticed that changing the last line of the .reg file (see above) it would work with any other executable, but it wouldn't work with wscript.exe
I compared the execution of wscript.exe on the affected computers to its execution on computers (not yet) affected and there is no difference
A double click shows the same Windows Script Host Settings dialog
The execution from a command prompt with the same arguments used by the custom protocol works as expected
The custom protocol passes the correct arguments when executing another executable
At this point I thought that Windows blacklisted wscript.exe and I started searching for an alternative
I tried to rename wscript.exe to wscript2.exe but I couldn't because I don't have TrustedInstaller permission
I made a copy instead of renaming it
I tested the copy from the command prompt and it was working like the original
I tested the copy from the custom protocol and it was working like the original once did
EDIT 2 (more answers to comments)
All the computers have Windows 10 Pro.
Clicking on Settings - Updates & Security - View update history it says Feature update to Windows 10, version 1803 Succesfully installed on 5/22/2018. Clicking on Show what's new in this update shows nothing useful.
EDIT 3
Doesn't work = no symptoms, nothing happens, nothing is executed, nothing is logged (as far as I know).
I tried with a simple vbscript with a single line MsgBox "Hello". It works running it from the command line, but it doesn't work from the custom protocol. The task manager doesn't show anything popping up, but I don't know if it doesn't show it because the lifespan is too short to show or because it doesn't execute. The same script works with wscript2.exe.
My feeling is that something (Windows, anti-virus, ...) is blacklisting the custom protocol + wscript.exe thing, but not the custom protocol + any other executable or any other environment + wscript.exe. That's why I tried to copy wscript.exe to wscript2.exe. And I was pleasantly surprised to find out that it works.
Been trying to find a way to do this for a while.
Opening a link in an windows explorer window instead of a browser.
For example using this link : ftp://username:pass#ftp.domain.com:80
And opening it in Windows Explorer.
Is it possible to dictate how windows should react when clicking on that link in a email ?
Thank you Fabian H!
Your solution works fine for me :-)
I made just a small change to your code, infact I wrote:
[HKEY_CLASSES_ROOT\IE.FTP\shell\open\command]
#="C:\\Windows\explorer.exe" %1
Instead of:
[HKEY_CLASSES_ROOT\IE.FTP\shell\open\command]
#="C:\\Windows\\explorer.exe %1"
This second one didn't work for me :-(
But now I can finally enjoy using explorer.exe as the default FTP Client!!
PS:
Tested on WIndows 7
Save these lines in a file with a file name ending .reg and double klick the file:
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\IE.FTP\shell\open\command]
#="C:\\Windows\\explorer.exe %1"
[HKEY_CLASSES_ROOT\IE.FTP\shell\open\ddeexec\Application]
#="Explorer"
Tested on WIndows 8.1 64bit.
Thanks to Perneel for his link.
The Windows registry keys shown before didn't work for me, but this works:
HKEY_CURRENT_USER\Software\Microsoft\FTP
Use Web Based FTP = "yes"
Just change value to "no".
(Windows 7 Pro x64)
I was fumbling around looking for how to do this and I ultimately decided to go with the "Add Network Location" wizard method as described here by "nhinkle".
However after doing so, I got a link that generated this shortcut:
ftp://MYFTP_LOGINID#FTPADDRESS/Some/Folder/Navigation/&Stuff/
More what it actually looks like:
ftp://123445_65432#78.13.223.184/root/main/servers/current/
Then was prompted for my login credentials, and thats it. Does not open in Chrome and I just did Send To > Desktop (shortcut) and moved that shortcut to the folder I wanted it in. Now I can open the FTP location from explorer by hitting the link instead of typing the address into the address bar, and it is not opening up in any internet browsers.
I only have one ftp account, dont know much about any background magic that the wizard may have done regarding registry/etc, and I feel like deleting the shortcut wont really undo any of that if it did happen, so if someone could test this and confirm whether or not it works, that'd be great.
Just my 2c :)
HKCU\Software\Microsoft\Windows\Shell\Associations\UrlAssociations\ftp\UserChoice
Check it out, i got the above answer working by deleting this entry
For regularly used FTP sites, if you don't want to make registry edits, create a shortcut using the following format and your site will open in Windows Explorer.
%windir%\explorer.exe ftp://
I have just set up a Guest Windows 2008 R2 Standard Edition 64bit (VirtualBox on Windows 7 64 bit host) for some testing.
I have found that while "inside" the remote desktop environment (i.e. I remote onto the guest ip from the host) that copy and paste does not work. When I say "does not work" let me be explicit.
Assume I am logged onto the Win2008 machine via RDC
Nothing is in the copy/paste buffer. I can mouse click some text and then rclick copy. I can then right click and click "paste" but nothing happens. I can see the "choice" is enabled to paste bu nothing happens. The caret stays put.
CTRL+C / CTRL-V / CTRL-X does not work in RDC land
I am not talking about going in-between copy/paste RDC land/host land.
HERE is the double whammy: when I do the above it then "infects" my host pc so that copy paste is unavailable there too. if PRT SCR doesn't work any more.
I have tried:
restarting the guest os and host os
in group policy editor I have disabled "do not allow clip board redirection" ( I can't give you the full path to this copy/paste just broke again)
I have made sure that in RDC "options" for local resources include clipboard.
NB: if I don't touch RDC at all and log into the guest OS via the console copy paste works perfectly
Kill the rdpclip.exe process using the Task Manager. Then, create a new process named rdpclip.exe. This will solve your problem.
Follow these steps in Remote Machine.
Stop the rdpclip process
Open Task Manager.
Go to process tab and find rdpclip
Choose rdpclip and End that task.
Start rdpclip.exe
Go to start menu and open Run command
Open rdpclip.exe and click Ok button.
Copy paste should work now.
it appears this is a flaw with VirtualBox
these posts covers it
https://forums.virtualbox.org/viewtopic.php?f=6&t=44498 (read the last post)
https://github.com/FreeRDP/FreeRDP/issues/230
(In VirtualBox) SETTINGS->GENERAL->[Advanced]->Shared Clipboard {disabled}
There are multiple things to check.
Restarting rdpclip.exe is a worthy try if the copy/paste fails sporadically, meaning we might on a process in a previous session.
On the client side, we check the RDP Options. Click on the Show Options button in the bottom, pick the third tab Local Resources. Make sure Clipboard is checked.
On the remote server side, we want to check Remote Desktop Session Host Configuration (Win Server 2008+).
Double click the connection to open its Properties window.
In the tab named Client Settings, Make sure Clipboard is not disabled.
We need to log off from the remote desktop.
Workaround
Use an online shared text box like this one:
https://pastebin.com/
My operating system is Windows 7 32bit. I installed RedMon1.7, Ghostscript 8.71 and GSview 4.9; installations were successful.
I went to Add New Local Printer in Windows Devices and Printers, clicked on Create A New Port, and selected Redirected Port from the Type of Port list. Clicked Next and in the Add New Port window I named RPT1: and clicked OK but it says Specified port cannot be added. Operation could not be completed (error 0x00000001)
I tried giving different names to the port, RPT2:, RPT4:, VPport: etc but all gave same result. Disabled Windows Firewall and tried but it continues to give same error, Disabled the Antivirus (Avira) but no change.
What can be preventing windows 7 from adding redirected port?
BTW I was following instructions in this tutorial in order to create a postscript printer.
http://www.stat.tamu.edu/~henrik/GSPSprinter/GSPSprinter.html
Appreciate any ideas or suggestions. Thanks
Run cmd.exe as Administrator and then run:
rundll32 printui.dll,PrintUIEntry /il
from the elevated cmd.
Go to your Start Menu,
Type Print,
Right-Click "Print Management",
Select "Run as administrator",
In Print Management; Expand "Print Servers" and Select "Ports".
Right-Click in the "Ports" pane (on the right hand side) and Select "Add Port...".
I'd also recommend configuring a Port from Print Management, as opposed to trying to do it in a Printers Properties. ;)
Adam Reed describes a workaround in his blog:
http://borntoidentify.blogspot.com/2010/09/configuring-virtual-printer-using.html
Not very comfortable, but works for me ...
EDIT: This link appears broken, but here's the content:
https://web.archive.org/web/20120628120209/http://borntoidentify.blogspot.com/2010/09/configuring-virtual-printer-using.html
The gist is that under Win7, you need to run explorer with elevated rights. This can be done using another browser, or, as mentioned in the comments on the original post:
Open a CMD window by right clicking and running as administrator
Kill the process explorer.exe from the task manager
Run explorer.exe from the command prompt window, now as an administrator.
Be very careful when running explorer as an administrator.
You need to enable Admin mode OR log with the Admin account!
This is cause by the new Vista/Win 7 security system.
Try reseting the firewall (Windows 7)
(be warned tho, the firewall will reset to the default setting)
*go to Control Panel
*go to Windows Firewall
*on the left choice pick "Restore Defaults"
It works for me, i hope it works for you.
F3lix's rundll32 method works but after you've created the port you most probably would need to configure its settings. Elsewhere in the net there are instructions to open Port management as Administrator, but in Windows 7 Home that seems to be very much impossible. One can only view the virtual port settings. The only workaround I found is to edit registry directly with the Registry editor at
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\Redirected Port\Ports\RPT1:
(Replace your port name in the end.)
It seams to be tricky. In my case it only works, after creating an new User account with the name "admin" / group " Administratoren" (de).
Before with my real Nickname User "Nick.." / group "Administratoren" (de) it dosent work´.
Takes several hours to discover ...
Accepted solution did not work for me...I found an other command line that worked well (I'm on windows 10):
%systemroot%\system32\printmanagement.msc
It opens the print management in administrator mode, and I was able to create the port with no problems.