Page 1 of 1

Publishing Empower 3 through Terminal Services

Posted: Fri Aug 02, 2013 1:31 pm
by semich01
I am setting up an Enterprise edition of Empower 3 and using Terminal services to publish the application for the end users to access. Everything has gone fine up to the point except concerning the Message Center. I can access the database, initiate runs, administer and everything else, all except see the Message center from the Thin client. For some reason the Message center is not making it through. This is all on a server running MS Server 2008 R2 and Empower 3 SR1FR1.
Any suggestions? I appreciate any help you all might have!

Re: Publishing Empower 3 through Terminal Services

Posted: Tue Aug 06, 2013 12:24 pm
by DR
Is message center on your antivirus suite's exception list?

Re: Publishing Empower 3 through Terminal Services

Posted: Tue Aug 06, 2013 1:29 pm
by semich01
It is allowed. The message center works fine if you remote into the server, but when using Remote-App it fails to load/show on the thin client.

Re: Publishing Empower 3 through Terminal Services

Posted: Wed Aug 07, 2013 2:36 pm
by DR
Have you asked Waters about it?

Re: Publishing Empower 3 through Terminal Services

Posted: Wed Aug 07, 2013 4:50 pm
by semich01
I have...but they do not support Empower thru Terminal services. The service engineer tried to help but they had nothing in their help database on the subject. They pretty much said "You can ask Microsoft, but We have no idea." I think we may have to ditch RemoteApp and go with a straight RDP connection to the server. I am also experiencing a RemoteApp disconnect of the app when the Pro Interface gets attached to the top or side of the screen essentially becoming a task bar. This causes the RemoteApp session to disconnect, and if the Empower is started again from the RemoteApp .RDP link it continues to just minimize to some secret desktop location and disconnect the session after 10-15 seconds.
I'm coming to the conclusion that running Empower 3 is just too unstable through remoteapp. It is entirely possible that it is just because I and my IT department are not configuring something correctly, but I think it is more than that. I was trying to stay away from having all of my end-users have to have a separate Remote Desktop window up, but it looks like that me be the only way.
We had a Citrix service set up, but somehow the licenses were never purchased, and instead of paying that large sum, they wanted to give Terminal services a try because the licenses are much cheaper. I guess you get what you pay for...

Re: Publishing Empower 3 through Terminal Services

Posted: Wed Aug 07, 2013 5:25 pm
by DR
Yep. It's probably time to bite the Citrix bullet. In addition to good support for Citrix, E3 also fully supports VMware, meaning you can run your Citrix client stack(s) on virtual servers. Although probably supported, I'd still tend to advocate for dedicated application server(s) over VMware.