[THIN] Re: Slow MMC

Hi,


The CMC (PSC)  and now Citrix MMC Add-on (AMC or whatever) are basically too
chatty, because in addition to being configuration interfaces, they also
provide some semi-realtime management which can mean a lot of update
information from the data collector. So the closer you are to the datastore
(startup speed and read/write speed for IM, printers etc) and data
collector, the faster things will be.

With the CMC you can choose your connection server, which is going to be
fastest if you connect to a data collector. The ASC MMC add-on kind of lets
you do this when you configure the servers to poll in the discovery option.
Put in your data collector.

But if it isn't local, it isn't going to be fast.

In terms of comms optimization, it's almost inevitable that your T1 will be
used for stuff other than ICA. Unless you're going to be using something
like Packeteer (or maybe WANScaler) it's going to be essential to use QOS on
your T1, with higher priority for port 1494 for ICA (and maybe 2598 for
session reliabilty - ICA V2) and also include ports 2513 for the management
consoles connection, 2512 for inter-data collector comms and  port 1433 for
the Datstore connection. Set your SQL client connection port to static
rather than dynamic and make sure you use SQL authentication.

In terms of farm configuration, 2 zones are going to be better than
a single zone configuration because you then have the option of a local data
collector for connection. And if you were to replicate your datastore so
it's local as well, preferably with the master copy at your end things would
be a lot faster. Then there's nothing stopping you having 2 license servers
with split licenses as well but that could get messy in terms of available
licenses in a DR scenario.

That'll  be as good as it gets and after that the only other option
is publishing the MMC add-on as a published app from the data collector in
Georgia.

regards,

Rick

--
Ulrich Mack
Commander Australia


On 5/31/07, bbeckett2000@xxxxxxxxxxx <bbeckett2000@xxxxxxxxxxx> wrote:


 Joe -

Running from a server here. You're right, running from a server up there
works alot better but they have some restrictions that I won't get into.
Therefore, I was trying to see if I am just stuck with the speed of the T1
running from a server in GA. 2 Zones, seperated geographically



-------------- Original message --------------
From: "Joe Shonk" <joe.shonk@xxxxxxxxx>

Where are you running the MMC from?  Best thing to do is run the AMC/CMC
from a server in MI.  Also, are all the servers in one zone or two?



Joe



*From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On
Behalf Of *bbeckett2000@xxxxxxxxxxx
*Sent:* Wednesday, May 30, 2007 8:41 AM
*To:* thin@xxxxxxxxxxxxx
*Subject:* [THIN] Slow MMC



Running PS 4.0 on Windows 2003 servers. I am joining PS 4 servers from one
farm to a new farm. Servers in the old farm were geographically in Georgia
while the new farm is based in Michigan. The Datastore resides in MI, as
well as the license server, web server, etc. The link between the two
locations is a T1 but I have found that after moving the servers into the MI
farm, running the MMC is painfully slow. Is there any way to speed this up?

Other related posts: