Re: server requirement
No, the profiles cannot contain the same files, so you can't copy
the workstation profile into the TS profile. That's the whole
point, many of the user-specific settings in the profiles are not
valid in the other environment.
If your users currently are in the habit of saving user documents,
like Word and Excel documents, in their profile, then it's high
time to give them a home directory and redirect their My Documents
folder to it. The user profile should not contain user documents,
especially not if it is a roaming profile. And you can make the
same folder, which contains the users documents, available to them
from both their workstation and their TS session.
I don't understand what you say about "As long as it's a terminal
server, it won't log me on to the console session of the server,
but instead a session inside the terminal server manager".
You can always make a connection to the console, with mstsc
/console. Doesn't matter if the server is configured for Remote
Desktop for Administration or for Terminal Services.
And NO, you can NOT install applications just like on any
workstation. The application installation procedure on a TS is
rather special, to ensure multi.user functionality. The server has
to be in "install mode" when you install applications, and no users
can be connected to it while you do so. Many applications also need
some additional adjustments after installation to make them work
properly.
I really suggest that you take your time to read up a bit on this,
and whatever you do, don't install and test on a production server!
Use any workstation-like PC and install Windows Server + TS on it,
just for testing purposes. Don't bother about performance at this
stage, it's sufficient if the testserver can handle 2 or 3
sessions.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting:
http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
=?Utf-8?B?cGV0ZTAwODU=?= <pete0085@discussions.microsoft.com>
wrote on 25 sep 2007 in
microsoft.public.windows.terminal_services:
> As for the TS profile path. Can it contain all the same files
> and folders as the regular roaming profile, but have a different
> path? Will this cause a problem. For ex if my profile path is
> \\server\profiles$\username. Then have a path of
> \\server\tsprofiles$\username but include all the same files.
>
> Think that helped with one question. I do want to test it first
> before buying any licenses to see how it would work in our
> environment. As long as it's a terminal server, it won't log me
> on to the console session of the server, but instead a session
> inside the terminal server manager as long as I buy licenses
> before the 120 days.
>
> I can also install applications as I would on the client
> workstation and they will be accessible without me doing
> anything else to it, correct?
>
> "Vera Noest [MVP]" wrote:
>
>> Yes, there is a grace period of 120 days, in which you can test
>> and use the Terminal Server, without the need to install TS
>> licenses. Just install Terminal Services, in Control Panel -
>> Add/Remove programs - Add Windows components.
>>
>> And yes, users should have a TS profile which is different from
>> there normal profile. If you use the same profile for their
>> workstation and their TS sessions, a lot of settings will not
>> work, and the profiles will become corrupt over time.
>> These TS-specific profiles can be local to the Terminal Server,
>> or they can be roamin. Just store them on a different share on
>> your file server.
>>
>> There is really not one single link which explains it all.
>> That's why there are numerous *books* written on the subject.
>>
>> You can find a number of links to articles about planning,
>> installation, etc on my website. Or read Brian Madden's book
>> again
>> 
and then install TS on a test server and play around with
>> :it.
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> *----------- Please reply in newsgroup -------------*
>>
>> =?Utf-8?B?cGV0ZTAwODU=?= <pete0085@discussions.microsoft.com>
>> wrote on 25 sep 2007:
>>
>> > I would like to be able to test this. I remember reading
>> > something about allowing you a 180 day trial before you
>> > purchase a license. How would that work in this scennario
>> > where I or a couple users could try it out and see if it
>> > would be a proper solution.
>> >
>> > Someone else is giving me advice that the profile path for TS
>> > should not be the same as the roaming profiles. How would a
>> > user logon or how would the desktop follow the user if they
>> > aren't using the regular roaming profile. I admit I'm
>> > confused about this among other things.
>> >
>> > I've been reading an online book by brain madden that goes
>> > into detail about the design, but isn't as helpful for an
>> > admin trying to setup a TS server.
>> >
>> > A good link, article would be helpful.
>> > "Vera Noest [MVP]" wrote:
>> >
>> >> When users log on to the Terminal Server with the Remote
>> >> Desktop client, they *are* logging on remotely to the server
>> >> itself! There's really no difference between Remote Desktop
>> >> connections (to a server which is configured for "Remote
>> >> Desktop for Administration") and Terminal Server connections
>> >> (to a server which is configured for "Terminal Services,
>> >> i.e. in application mode).
>> >>
>> >> And the server has no way of knowing why someone logs on or
>> >> what they are going to do on the server, that's why *all*
>> >> connections to a server configured for terminal Services
>> >> need a license. The only exception is a single connection to
>> >> the console of the server (with mstsc /console), which is
>> >> always free of TS CAL requirements.
>> >>
>> >> Ideally, a Terminal Server should be a dedicated server,
>> >> both for performance and security reasons. But in small
>> >> environments, this isn't always realistic. So you can also
>> >> use the same server as a file server, but don't run TS on a
>> >> Domain Controller, and don't combine it with SQL or Exchange
>> >> if you can avoid it.
>> >> _________________________________________________________
>> >> Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server
>> >> TS troubleshooting: http://ts.veranoest.net
>> >> ___ please respond in newsgroup, NOT by private email ___
>> >>
>> >> =?Utf-8?B?cGV0ZTAwODU=?=
>> >> <pete0085@discussions.microsoft.com> wrote on 25 sep 2007 in
>> >> microsoft.public.windows.terminal_services:
>> >>
>> >> > I mean does it have to be a deticated server or could I
>> >> > host it an another server that acts as an application
>> >> > server for one of our programs or what is typically
>> >> > recommended for a small environment where it will not be
>> >> > heavily used.
>> >> >
>> >> > Also, how does the server know you are not logging on
>> >> > remotely as you would with remote desktop? Lets say a
>> >> > regular user wants to logon to the terminal server, how
>> >> > does it figure out they are not trying to logon to the
>> >> > server to perform maintenance on the server, etc.
>> >> >
>> >> > That has confused me a bit. I'm guessing users use the
>> >> > remote desktop connection to connect to the terminal
>> >> > server. I just want to ensure they are logging on to their
>> >> > terminal session and not actually logging on to the server
>> >> > itself. Does this make any sense with what I'm trying to
>> >> > say???
>> >> >
>> >> > "Munindra Das [MSFT]" wrote:
>> >> >
>> >> >> The article at
>> >> >> http://technet2.microsoft.com/windowsserver/en/library/cb2
>> >> >> 019 37- 8f68-4d0f-9521-99e090ddd6b11033.mspx?mfr=true
>> >> >> will provide you with some details on how to plan a
>> >> >> terminal server. But it will also depend on what Windows
>> >> >> (2000, 2003) you are running and what applications the
>> >> >> users are likely to run. For a 2003 Terminal Server with
>> >> >> 12 users, you will require a minimum of 128 MB memory.
>> >> >>
>> >> >> I am not sure what you mean by "Could it be an another
>> >> >> application server or does it have to be a deditcated
>> >> >> server". You can please provide a little more detail.
>> >> >>
>> >> >> --
>> >> >> This posting is provided "AS IS" with no warranties, and
>> >> >> confers no rights. "pete0085"
>> >> >> <pete0085@discussions.microsoft.com> wrote in message
>> >> >> news:1E25A8B3-6BF5-4A33-B8B1-9615384FDCCD@microsoft.com...
>> >> >> > Brief question about server requirement for a single
>> >> >> > terminal server.
>> >> >> >
>> >> >> > There would be a max of 12 users accessing the server
>> >> >> > at one time. With disk space not being an issue, what
>> >> >> > would be a recommendation for memory for
>> >> >> > such a server?
>> >> >> >
>> >> >> > Could it be an another application server or does it
>> >> >> > have to be a deditcated
>> >> >> > server?
>> >> >> >
>> >> >> > Can someone briefly explain why accessing resources
>> >> >> > through a terminal server doesn't take up as much
>> >> >> > bandwidth and is faster then accessing it over
>> >> >> > a Wan link? 