If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
You mean running Shoretel in a thin client / Terminal server enviornment? We have several customers utilizing the call manager via terminal services and thin clients with no issues. The only thing I can ever think of is if somebody tried to redirect there audio when playing from there outlook (by default, it plays on the phone). Terminal services and audio don't mix very well.
You just have to make sure you install the Call Manager for a Terminal Server.
Follow the instructions in the Planning/Installation guide, Appendix F (Shoreware Clients on Citrix and Windows Terminal Servers
Be sure to be prepared to reboot the Terminal Server after installation , just like workstations. The main difference, you want to be sure tehy are prepared. (Alot of people may be connected to it).
Glad to be of service. One other tip, though. After you delete the connector, run the TSPinstall, and go back to the Phone/Modem properties, the screen may not match the example in the book. I usually just login to the Call manager to verify that it's operational. Don't waste your time trying to figure out why they don't match.
We are a Citrix shop and run PCM. There are 5 servers in our farm. Each day a user could be on a differnt Citrix server and we use roaming profiles. Shoretel PCM saves the history of the PCM to a place that does not get propagated by roaming profiles. This means each day if a user ends up on a different Citrix server, their previous days history will not be in the PCM.
Suppossedly, this is going to be fixed in version 8. I am guessing that will be released late summer 08...
Comment