I am trying to run an AcuCobol software application through Remote Desktop Services on a Windows Server 2019. The Remote Desktop Services collection has been successfully deployed. I added the wrun32.exe program to the list of allowable programs using the full network path and then published it. I see it on the Remote Desktop Website. I downloaded the .rdp icon on the remote machine through the Remote Desktop Website. I then change properties of that .rdp icon through Notepad on the local user machine to include the necessary parameters that the software app requires to run (C:\\Acucorp\\AcuGT\\bin\\wrun32.exe -C C:\\ETC\\GUICONFIG User_Login 001 Main_Menu). This works fine on the local server. I just can't get it to run on the remote machine which accesses this server thru RDS.
I get the error as follows:
Windows cannot start the RemoteApp program. The following RemoteApp program is not in the list of authorized programs: wrun32.exe.
Have you checked this registry setting? That is the setting which normally causes that behaviour from what I can see online:
HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Terminal Server\\TSAppAllowList
Find the key “fDisabledAllowList”
It will be set to “0”
Change to “1”.
Thank you
Have you checked this registry setting? That is the setting which normally causes that behaviour from what I can see online:
HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Terminal Server\\TSAppAllowList
Find the key “fDisabledAllowList”
It will be set to “0”
Change to “1”.
Thank you
This setting was actually set correctly within the registry. I did however find my problem! It was an easy solution. I should have found it a long time ago. Ugh!
My RemoteApp parameter property was set to “Do Not Allow any command-line parameters” for the wrun32.exe program. Since it was not using the config file parameter that I was using in the remoteapplicationcmdline within the rdp icon properties, it didn’t know where to access the program that the wrun32.exe was calling. The error message that I was receiving was a bit misleading and sent me on a wild goose chase.
I changed the parameter setting for the wrun32 program within the RDP Collection. I now have it set to “Allow any command-line parameters”. Now it recognizes the parameter within the rdp file on the local machine when calling the program on the Terminal Server.
Thanks so much for your time and your suggestion. I appreciate it!
