Release Date: 8/8/2018
For Elliott users who have a remote warehouse, the easiest solution to let warehouse users have access to Elliott is to let them use a remote desktop to login to the terminal server hosted at the user's location. While the warehouse user can access Elliott's screen and print documents like pick tickets on their local printer with ease, one issue that's more challenging is the printing of UCC-128 labels.
Elliott prints UCC-128 labels through the software program Bartender. in Elliott Shipping Verification, the system can optionally produce needed CSV files for Bartender to print UCC-128 labels. To do this, the following requirements need to be met:
- The Bartender and its automation tool need to be installed on the warehouse user's local computer.
- The Elliott session running through the remote desktop needs to create the needed CSV file on the warehouse user's local computer.
- The automation tool will need to be configured to monitor that CSV file. Once detected, grab it and merge with the pre-designed label layout to print the UCC-128 label.
This article focuses on item "2" above. Some have attempted to do this with VPN. Based on our past experience, doing this with VPN is more challenging and sometimes not reliable. So we focus our discussion here on mapping the local drive through the remote desktop built-in's ability:
Step 1 - Create a LABEL Folder on Warehouse User's C: Drive
By convention, we write the CSV file to warehouse user's C:\LABEL folder.
Step 2 - Allow Remote Desktop Session Access to Local Drives
In your remote desk connection, go to the "Local Resources" tab, and in the "Local devices and resources" area click on the "More..." button:
Then expand the "Drives" and check the "C:" drive to make it available to your remote desktop session:
Step 3 - Login to Remote Desktop to Confirm
Now login to your remote desktop session and bring up Windows Explorer. You will see your local drives show up:
Step 4 - MAP L Drive to \\TSCLIENT\C\LABEL
But Elliott can't access these local drives yet. You will need to map a network drive, such as the L: drive, as follows:
You can also automate this in your startup script by using the "net use" command like the following:
net use <drive letter> \\tsclient\<drive letter>\LABEL
or in this case, it would be:
net use L \\tsclient\c\LABEL
Our convention is to map the L drive for local label printing purposes.
Step 5 - Set Up Your EDI Profile Label Path
Now you can go to the customer's EDI profile and set up the proper label path like the following: