DO NOT USE A MAPPED DRIVE! Use the UNC!

Follow this example to create a shortcut: Create Shortcut Manually

To assist with this first method, we provide a program called the Shortcut Wizard. This program will create a shortcut using a correct command line and will automatically register all ActiveX controls. If you’d rather not manually create the shortcut, use this program to create a desktop shortcut for you.

Using the shortcut Wizard.

Watch this video on using the wizard: ETShortcutWizard

 This window will be unresponsive as long as the bottom status bar is blinking red and white with the message, “Loading user control data. This may take a couple minutes so be patient.” It’s compiling a list of all ActiveX controls and DLLs that need to be registered. When it’s done you’ll see the status bar remain white with the message, “Control data loaded. Verify folder and terminal number and proceed." At this point, you’ll also notice that the ‘Create Shortcut’ button has appeared. A window will appear with several options. Since the program was run from the Execu/Suite folder, you don’t have to locate the folder, that field will already be filled with the correct folder.  To create a shortcut for Execu/Suite, you simply need to select your desired terminal number then click the ‘Create Shortcut’ button. You won’t be notified if your selected terminal number is already in use, so be sure you’re selecting the correct terminal number to avoid any confusion or security warnings when running Execu/Suite.

The Execu/Suite is best run using the ‘Environment’ tab of the user in ‘Active Directory Users and Computers’. Rather than placing the command line in ‘Target:’, you’ll place it in ‘Program file name’. If your server and Terminal Services server aren’t the same machine, be sure to use the UNC, just like in the first option. Otherwise, you should use the drive letter, just like in the example image. Using the UNC when the software is installed locally will cause severe performance issues.

Failure to configure this setting can leave files locked that may prevent other users from running the software. They may experience errors caused by the locked files that can't be resolved until the disconnected sessions are ended. Make sure that the disconnected session settings are set in accordance to the needs of the property. You may want to be able to reconnect to a session after a few minutes if you experience frequent disconnects. You also want to make sure that a disconnected session doesn’t remain in that state indefinitely, causing the number of available users to be reduced by one even though the session isn’t in use.   Setting an appropriate duration to ‘End a disconnected session’  can give the user time to reconnect if needed but allow the count of active users to be accurate if you’re unable to reconnect and close Execu/Suite, properly. We find that 5 minutes is a good setting. This can be set at the server level or user level, whichever your IT prefers.

Remote Desktop Printers If you have a lot of terminals, it's important that the printers for each terminal are not published into the list of printers that all other terminals will see. This can create huge delays when the the software needs to display a printer dialog and can make printer selection confusing for the users.