txt” file extension onto the end of the batch file name). BAT file (while making sure that Notepad doesn’t append a “.
Otherwise, you should just be able to open up Notepad, type in the command for executing your script, and save it as a. as long as it can be successfully executed on the server). That “should” work as long as the server itself supports the file type of your script file (i.e. If it’s not, then you can try typing “ *.*” (without the quotes) into the “ File name” field and hitting the enter key so that the File Open dialog box now shows all file types (instead of it only showing the file types that WSE RemoteApp supports by default), and then select your script file from there. NOTE: I don’t know what format your script file is in (as you didn’t say), but I’ll assume that it’s in a standard “ Windows Batch File (.BAT)” format here. Click on the “ Add Another Program” button in the Publish RemoteApp Programs wizard that opens, locate/open your script file, and finish out the rest of the wizard in order to publish the script file as a RemoteApp program in WSE RemoteApp. Click on the “ RemoteApp Programs” subtab, and then click on the “ Publish RemoteApp Programs” task.ģ. Open the server Dashboard and go to the main “ WSE REMOTEAPP” page.Ģ. If you have a script that automatically creates your mapped network drives when you log into your VM desktop, then you should just be able to publish that script as a RemoteApp program in WSE RemoteApp and have it run automatically when your user’s RemoteApp sessions first start.