You’re offline. This is a read only version of the page.
Technical Environment: GP 10.00.1400 | Dexterity: 10.0.324.0 on a Windows Server 2008 R2 Terminal Server; GP is published using RDWEB applications. All printers are direct to the application server via TCP/IP. Companies connect via site-to-site IPSEC VPN tunnels.
User/Company Environment: Multiple finanically separated companies utilize GP. Named printer users in our corporate center use fat installations on their local workstation, so they are able to utilize named printers correctly. Named printer users in two other companies use the TS version of GP, and therefore the same ST_MachineID is used. We utilize different .set files based on what modules we load, as we have conflicting modules in use. We also utilize separate but shared dex.ini files based on which dictionary we are loading.
Problem: I cannot set different named printers for the same task for multiple companies who utilize the same terminal server for GP access. If I set a company/system/user printer for one company (I created template users for this per company), it dissappears if I update for another company. It's a well-known problem, somewhat fixed in GP 2010, and I've read every article I can think of on this subject. Using the debugging tools to create a pop-up about settings being erased doesn't seem to me as a solution, work-around or fix... it just prevents somewhat initially at actually going through with the change in named printers, and erasing past settings.
What I'm looking for: A real and reliable way, no matter the route it takes, to be able to assign company/system/user named printers for different companies/locations. I cannot have the issue where Company A prints checks and it ends up on Company B's printer. I'm getting tired of doing the named printer dance, and am open to nearly everything (except upgrading GP, as we will be doing that mid next year).
What I've tried: Creating individual dex.ini files per user and sticking them in their user profile directory on the TS. However, when I publish the app via RDWeb, I cannot use %username% in the command line argument as it doesn't parse correctly. I can only use a hard path. I've also attempted to create dex.ini files, to be shared, on the TS in user directories based on roll (i.e. c:\users\Dynamics_STD_CompanA\windows\dex.ini). In this dex.ini file, I create a fake ST_MachineID. What I'm running into though, is that once I launch GP, it would seem that I can only set the machine ID once, and even when changing the settings of the named printers themselves are not changing based on machine ID entered. In the end, it would seem that if GP is launched from a TS environment, I can only get away with using one machine ID. If this is the case, it would seem impossible to have different companies in different locations printing to different named printers, while using the same terminal server. Would me only option be to utilize a separate TS for each company?
Thanks for any help or insight into this!
*This post is locked for comments
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (