Empower using Windows remote services
Currently our lab has Empower setup as an Enterprise with an Empower server. Then Empower is installed on all the LAC/E boxes and many computers in the lab as well as at the desktops of many scientists who may use Empower. This creates a huge mountain of paperwork as each node must be qualified and then keeping track of each computer to make sure IT doesn't upgrade them and then tell no one in the lab, thus we would be using an un-qualified version. Then when we upgrade it takes a week for our IT to get to every node. We discussed using Citrix, however, I was told by our IT that Citrix is way too expensive and will not be supported by our company. But they said that anything Citrix could do, Windows remote services could also do. Speaking with Waters, they agreed, but thought we might have some graphics issues or such, but generally it should work. So we created a Windows terminal server and have found some glitches in and for the most part they are based on graphics. For Agilent GCs, it doesn't recognize any of the GCs, but you can still run them, you just can't see their status. For Alliance HPLCs, you cannot switch between the separations module and any detectors without getting errors. Thus you can't write or edit instrument methods.
When will Waters work on making Empower work with Windows remote service and validate that it works for all components? In speaking with others, there are many who would prefer this due to the expense of Citrix and other issues around Citrix.