[THIN] Re: Windows Server 2003
- From: "Jay Moock" <jmoock@xxxxxxxxxxxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Fri, 6 Feb 2004 11:48:20 -0500
I'll answer your second question first because it's the easiest. Under
Server Settings Terminal Services Configuration there is a "Restrict each
user to one session setting". Change it from No to Yes and you'll be all
set.
Printer creation is much more complicated in MF XP than it was in MF 1.8. A
couple of things to check in the CMC are:
In the ICA Client Options section of properties for the Published App, check
your "Start this application without waiting for printers to be created
setting". If you can get away with enabling this it may speed up the time
that it takes the application to load. The downside is that if the app
opens before the printers are created then it may have the proper print
selected when the user goes to print.
In the Printers section of the properties of Printer Management you can
choose whether it creates all client printers or only the default. If you
only need the default client printer then you can enable this setting and
speed up logins some.
Hope that helps.
Jay
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On
Behalf Of Brookus, Tony (ITCD)
Sent: Friday, February 06, 2004 11:07 AM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Windows Server 2003
Hey guys. Finally set up a Win 2003 box with Metaframe XP FR1 SP3 (haven't
set it to FR3 yet). So far it's fine except for two weird things I've
noticed and was wondering if anyone else has seen them.
Published apps seem to take a bit longer to open (compared to NT-TSE).
After it runs through the usrlogon.cmd it just seems to set for a few
seconds and then finally opens up the application. I can open an app on NT
in about 10 seconds and that same app takes about 20-25 seconds on 2003.
Using the same account and getting a default profile each time. I have all
the 2003 patches and XP patches loaded. Anyone else noticed this?
Other strange thing was that I was testing an application as a user who was
already logged into that same application. So she had published Word open
and was working away and I launched the published Word as her. It
disconnected her session and connected me to it. So she lost her screen and
I stole it, when I was expecting it to just open a new Word. Win NT didn't
do this and I don't think 2000 did. Is there some kind of setting about
this that I'm missing?
Thanks,
Tony
********************************************************
This Week's Sponsor - RTO Software / TScale
What's keeping you from getting more from your terminal servers? Did you
know, in most cases, CPU Utilization IS NOT the single biggest
constraint to scaling up?! Get this free white paper to understand the
real constraints & how to overcome them. SAVE MONEY by scaling-up rather
than buying more servers.
http://www.rtosoft.com/Enter.asp?ID=147
**********************************************************
Useful Thin Client Computing Links are available at:
http://thethin.net/links.cfm
***********************************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://thethin.net/citrixlist.cfm
********************************************************
This Week's Sponsor - RTO Software / TScale
What's keeping you from getting more from your terminal servers? Did you
know, in most cases, CPU Utilization IS NOT the single biggest
constraint to scaling up?! Get this free white paper to understand the
real constraints & how to overcome them. SAVE MONEY by scaling-up rather
than buying more servers.
http://www.rtosoft.com/Enter.asp?ID=147
**********************************************************
Useful Thin Client Computing Links are available at:
http://thethin.net/links.cfm
***********************************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://thethin.net/citrixlist.cfm
Other related posts:
