The issue starts if we lose a WAN link and the office has to revert to their backup internet ADSL line. Any thin client will work whilst the the WAN is running as it is a dead simple setup. Home users access using the web plugin (of varying versions) their home printers are mapped to, in their session using the Citrix printer mapping. We do have a 2k3 print server, each share is linked to the IP port of the printer and works fine if the WAN is functioning. We run a XenApp5 farm (5 servers all based on win2k3 (legacy apps that are not verified in 2k8 or 64bit!!!) + a DC again 2k3). Those 1200s have served us very well so far.they are still going but they know their days are numbered! Although it would make things easier in the long run. I would suggest that you try and standardize the web-plugins on the latest version, but that might be easier said than done. When we moved from 2k3 to 2k8 it fixed some random authentication issues with Citrix, especially with our remote offices. Also, I would suggest upgrading your DC to 2k8 R2 as well. It should prevent other printer issues from happening as well since it is a true print server, unlike the previous iterations that MS has produced. I would highly suggest that you setup a 2k8 R2 print server. IP, no need for CSG access, and other associated headaches.
little slow but was reliable.Īt that point you should be able to forget about the local printer installs, the issues with DNS vs.
We had it set up that the router at the remote site would connect through a VPN to the main site's router and through that connection the two sites would work near perfectly. We used to use that as a primary connection at an office that was only open two days a week. If you have the ability and equipment or funding for the equipment, you should set up the ADSL to be used as a VPN connection to your main office. And it would help simplify this entire setup tremendously. Sounds like there is room for improvement with the backup ADSL.
0 kommentar(er)
