Re: Setting up a Terminal Server (TS) for multiple Console users
- From: "Garth" <Spam@xxxxxxx>
- Date: Tue, 1 Apr 2008 15:45:27 -0400
I'm not sure why anyone would tell you to TS in the the server, instead of using the console on your local WS. Yes, the console does use memory but from do you really want to use up all the RAM on your site server for multiply console vs allow that same RAM to be used to process data?
As for right click tools, they would need to be installed on each WS that has the console in order to allow them to work.
BTW With ConfigMgr do you know that all the right-tools don't work and need to be re-written for ConfigMgr. There is an update on MyITForum that add most (if not all) right click tools into ConfigMgr console.
"Bill Bradley" <BillBradley@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:A2D4629E-20CF-416D-9127-D8369EBB2318@xxxxxxxxxxxxxxxx
We've taken 3 Domain SMS Trees, and, have merged them up into a Site Server,
about 30 K users and computers, across 3 geographically huge Domains,
connected into one server...that only has 2 RDP connections, and, is across
some slow WAN links. Also...from what we are being told, the SCCM Console is
resource-intensive, requires GB of RAM per user, and, MS recommends a TS,
next to the Site server for access. And, once we get all this solidified,
we're upgrading to SCCM.
What doesn't seem to be getting installed is the SMS Tools item on the menus
(and, I did install the SMS Tools for SMS on my local computer). We make
heavy use of that, say for instance in adding in a list of computers by
dragging and dropping them into the tool, and, in doing a quick dump of
computers to the clipboard. They also allow for initiating inventories and
policy updates, etc.
Thanks.
"Garth" wrote:
This might seem like a stupid question but why not install the console on
peoples WS, instead of using remote desktop to access the console?
Which tools don’t seem to work correctly, when not on the server? I almost
never access the console anymore, so I’m curious what issues you are having?
"Bill Bradley" <BillBradley@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D38874DA-791B-4EF2-91F9-5DF4F8062440@xxxxxxxxxxxxxxxx
> We have SMS 2003 SP3, and, the biggest problem is the number of users > that
> need to use the Console ON the server, with its (only) 2 RDP > connections.
>
> It has been suggested that I setup a Terminal Sever, and, put the > Console
> on
> it, but, this suggestion seems like it has the same problems as loading
> the
> Console on your own XP computer--the SMS Tools and other things don't > seem
> to
> work right, unless you are ON the SMS Site Server, running the Console.
>
> Is there some way to configure the Console, on a TS or on your own XP
> computer, to give it all the missing functionality? Is there a KB > article
> or
> paper on this?
>
> Thanks!
.
- Follow-Ups:
- Re: Setting up a Terminal Server (TS) for multiple Console users
- From: Bill Bradley
- Re: Setting up a Terminal Server (TS) for multiple Console users
- References:
- Setting up a Terminal Server (TS) for multiple Console users
- From: Bill Bradley
- Re: Setting up a Terminal Server (TS) for multiple Console users
- From: Garth
- Re: Setting up a Terminal Server (TS) for multiple Console users
- From: Bill Bradley
- Setting up a Terminal Server (TS) for multiple Console users
- Prev by Date: Re: SP3 Upgrade: Errors: 1020 (MP), 4951 (MP), 2302 (DP),
- Next by Date: Re: Setting up a Terminal Server (TS) for multiple Console users
- Previous by thread: Re: Setting up a Terminal Server (TS) for multiple Console users
- Next by thread: Re: Setting up a Terminal Server (TS) for multiple Console users
- Index(es):
Relevant Pages
|
Loading