Re: Adding new client to 2003 server

[Guest Stewman]

Re: Adding new client to 2003 server

 

I am also new to Terminal Servers and would like to know what are the steps

to add new Terminla Server users to a Windows 2003 Server?

 

"Vera Noest [MVP]" wrote:

> You're welcome! And yes, that happens all the time: you *expect*

> something to be complicated, and thus you overlook the easy

> solution :-)

> _________________________________________________________

> 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?VGluYQ==?= <Tina@discussions.microsoft.com> wrote on 12

> okt 2006 in microsoft.public.windows.terminal_services:

>

> > Thank you, I suppose I'm making this harder than it needs to

> > be. I appreciate the explanation!

> >

> > "Vera Noest [MVP]" wrote:

> >

> >> You don't have to do anything.

> >>

> >> TS CALs have an expiration date of 52-89 days after issueing.

> >> Licenses that are not used (because the old client does not

> >> connect to the TS anymore) will automatically be returned to

> >> the LS after the expiration date. In the meantime, your new

> >> clients will get a temporary TS CAL, which is valid for 90

> >> days.

> >>

> >> Note that these time periods are choosen to make sure that your

> >> temporary license lasts long enough for the old license to

> >> become available again. So replacing one client with another

> >> can never cause you to run out of TS CALs.

> >> _________________________________________________________

> >> 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?VGluYQ==?= <Tina@discussions.microsoft.com> wrote on

> >> 12 okt 2006 in microsoft.public.windows.terminal_services:

> >>

> >> > Thanks for the response. We are using terminal services so

> >> > all the software runs from the server. I have a question

> >> > about the TS licenses. These computers are actually

> >> > replacements. Do I need to transfer the current license from

> >> > the old computer to the replacement computer? Or is that

> >> > something I should manage in Active Directory???

> >> >

> >> > "Kshaeta" wrote:

> >> > > First, you only need terminal services if you want all of

> >> > > the software

> >> >> to run on your central server (much like a null terminal

> >> >> connected to a

> >> >> UNIX box, but prettier). It allows for centralization of

> >> >> your

> >> >> programs for easier management, as well as gives you more

> >> >> control over what people can do. It also alleviates a lot

> >> >> of security issues. Terminal services can also allow you to

> >> >> access it via web access. So (theoretically) you could

> >> >> access your data from a web browser. It makes it easier for

> >> >> users to move from computer to computer, since their

> >> >> settings are all saved on the terminal server.

> >> >>

> >> >> But that's beyond just a network. If all you want is to

> >> >> setup each workstation, and then install programs (word,

> >> >> excel, donkey kong, whatever) on each workstation, you don't

> >> >> need terminal services. You would just need to setup each

> >> >> system the way you like, and then creates directories to

> >> >> store data on the server(s), and create shares on the server

> >> >> (so the clients can connect). There are quite a few steps to

> >> >> this process, so I'll assume it's not what you want.

> >> >>

> >> >>

> >> >> For terminal server, you would need:

> >> >>

> >> >> Windows XP/2000 which comes with remote desktop (aka

> >> >> terminal services) installed.

> >> >>

> >> >> A windows 2000/2003 server to run terminal server, as well

> >> >> as a server to run terminal services licensing.

> >> >>

> >> >> You will need to purchase TS licenses, one for each user (or

> >> >> computer) from a licensed microsoft distributor.

> >> >>

> >> >> That's as brief as I get. I can't really go into the

> >> >> particulars, it would take to much time.

> >> >>

> >> >> If you go to windows website, you can find a section on

> >> >> Terminal Server and some white papers. It might help.

> >> >>

> >> >> Here are some links:

> >> >> http://www.brianmadden.com/content/content.asp?id=154

> >> >> http://www.brianmadden.com/subject.asp?ID=3

> >> >> http://www.microsoft.com/windowsserver2003/techinfo/overview/

> >> >> qui ckstart.mspx#EJAA

> >> >> http://technet2.microsoft.com/windowsserver/en/whitepapers.ms

> >> >> px

> >> >>

> >> >>

> >> >> Good luck!

> >> >> bill

>

[Guest Vera Noest [MVP]]

Re: Adding new client to 2003 server

 

Re: Adding new client to 2003 server

 

Assuming default configuration, the only thing you have to do to

give your users access to a 2003 Terminal Server is to make them

members of the local built-in "Remote Desktop Users" group on the

Terminal Server.

Best practice is to create a domain global security group, make the

users member of that group and make that group a member of the

local Remote Desktop Users group on the TS, rather than adding

individual user accounts to the local group. Makes user management

easier, especially if you have multiple terminal Servers.

_________________________________________________________

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?U3Rld21hbg==?= <Stewman@discussions.microsoft.com> wrote

on 31 okt 2007 in microsoft.public.windows.terminal_services:

> I am also new to Terminal Servers and would like to know what

> are the steps to add new Terminla Server users to a Windows 2003

> Server?

>

> "Vera Noest [MVP]" wrote:

>

>> You're welcome! And yes, that happens all the time: you

>> *expect* something to be complicated, and thus you overlook the

>> easy solution :-)

>> _________________________________________________________

>> 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?VGluYQ==?= <Tina@discussions.microsoft.com> wrote on

>> 12 okt 2006 in microsoft.public.windows.terminal_services:

>>

>> > Thank you, I suppose I'm making this harder than it needs to

>> > be. I appreciate the explanation!

>> >

>> > "Vera Noest [MVP]" wrote:

>> >

>> >> You don't have to do anything.

>> >>

>> >> TS CALs have an expiration date of 52-89 days after

>> >> issueing. Licenses that are not used (because the old client

>> >> does not connect to the TS anymore) will automatically be

>> >> returned to the LS after the expiration date. In the

>> >> meantime, your new clients will get a temporary TS CAL,

>> >> which is valid for 90 days.

>> >>

>> >> Note that these time periods are choosen to make sure that

>> >> your temporary license lasts long enough for the old license

>> >> to become available again. So replacing one client with

>> >> another can never cause you to run out of TS CALs.

>> >> _________________________________________________________

>> >> 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?VGluYQ==?= <Tina@discussions.microsoft.com> wrote

>> >> on 12 okt 2006 in

>> >> microsoft.public.windows.terminal_services:

>> >>

>> >> > Thanks for the response. We are using terminal services

>> >> > so all the software runs from the server. I have a

>> >> > question about the TS licenses. These computers are

>> >> > actually replacements. Do I need to transfer the current

>> >> > license from the old computer to the replacement computer?

>> >> > Or is that something I should manage in Active

>> >> > Directory???

>> >> >

>> >> > "Kshaeta" wrote:

>> >> > > First, you only need terminal services if you want all

>> >> > > of the software

>> >> >> to run on your central server (much like a null terminal

>> >> >> connected to a

>> >> >> UNIX box, but prettier). It allows for centralization

>> >> >> of your

>> >> >> programs for easier management, as well as gives you more

>> >> >> control over what people can do. It also alleviates a

>> >> >> lot of security issues. Terminal services can also allow

>> >> >> you to access it via web access. So (theoretically) you

>> >> >> could access your data from a web browser. It makes it

>> >> >> easier for users to move from computer to computer, since

>> >> >> their settings are all saved on the terminal server.

>> >> >>

>> >> >> But that's beyond just a network. If all you want is to

>> >> >> setup each workstation, and then install programs (word,

>> >> >> excel, donkey kong, whatever) on each workstation, you

>> >> >> don't need terminal services. You would just need to

>> >> >> setup each system the way you like, and then creates

>> >> >> directories to store data on the server(s), and create

>> >> >> shares on the server (so the clients can connect). There

>> >> >> are quite a few steps to this process, so I'll assume

>> >> >> it's not what you want.

>> >> >>

>> >> >>

>> >> >> For terminal server, you would need:

>> >> >>

>> >> >> Windows XP/2000 which comes with remote desktop (aka

>> >> >> terminal services) installed.

>> >> >>

>> >> >> A windows 2000/2003 server to run terminal server, as

>> >> >> well as a server to run terminal services licensing.

>> >> >>

>> >> >> You will need to purchase TS licenses, one for each user

>> >> >> (or computer) from a licensed microsoft distributor.

>> >> >>

>> >> >> That's as brief as I get. I can't really go into the

>> >> >> particulars, it would take to much time.

>> >> >>

>> >> >> If you go to windows website, you can find a section on

>> >> >> Terminal Server and some white papers. It might help.

>> >> >>

>> >> >> Here are some links:

>> >> >> http://www.brianmadden.com/content/content.asp?id=154

>> >> >> http://www.brianmadden.com/subject.asp?ID=3

>> >> >> http://www.microsoft.com/windowsserver2003/techinfo/overvi

>> >> >> ew/ qui ckstart.mspx#EJAA

>> >> >> http://technet2.microsoft.com/windowsserver/en/whitepapers

>> >> >> .ms px

>> >> >>

>> >> >>

>> >> >> Good luck!

>> >> >> bill

[Guest Stewman]

Re: Adding new client to 2003 server

 

Re: Adding new client to 2003 server

 

I need to add only one person to connect via TS and not sure the steps to

follow on my Win 2003 Svr. Do I go into TS MGR to add the new user? Thanks

 

"Vera Noest [MVP]" wrote:

> Assuming default configuration, the only thing you have to do to

> give your users access to a 2003 Terminal Server is to make them

> members of the local built-in "Remote Desktop Users" group on the

> Terminal Server.

> Best practice is to create a domain global security group, make the

> users member of that group and make that group a member of the

> local Remote Desktop Users group on the TS, rather than adding

> individual user accounts to the local group. Makes user management

> easier, especially if you have multiple terminal Servers.

> _________________________________________________________

> 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?U3Rld21hbg==?= <Stewman@discussions.microsoft.com> wrote

> on 31 okt 2007 in microsoft.public.windows.terminal_services:

>

> > I am also new to Terminal Servers and would like to know what

> > are the steps to add new Terminla Server users to a Windows 2003

> > Server?

> >

> > "Vera Noest [MVP]" wrote:

> >

> >> You're welcome! And yes, that happens all the time: you

> >> *expect* something to be complicated, and thus you overlook the

> >> easy solution :-)

> >> _________________________________________________________

> >> 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?VGluYQ==?= <Tina@discussions.microsoft.com> wrote on

> >> 12 okt 2006 in microsoft.public.windows.terminal_services:

> >>

> >> > Thank you, I suppose I'm making this harder than it needs to

> >> > be. I appreciate the explanation!

> >> >

> >> > "Vera Noest [MVP]" wrote:

> >> >

> >> >> You don't have to do anything.

> >> >>

> >> >> TS CALs have an expiration date of 52-89 days after

> >> >> issueing. Licenses that are not used (because the old client

> >> >> does not connect to the TS anymore) will automatically be

> >> >> returned to the LS after the expiration date. In the

> >> >> meantime, your new clients will get a temporary TS CAL,

> >> >> which is valid for 90 days.

> >> >>

> >> >> Note that these time periods are choosen to make sure that

> >> >> your temporary license lasts long enough for the old license

> >> >> to become available again. So replacing one client with

> >> >> another can never cause you to run out of TS CALs.

> >> >> _________________________________________________________

> >> >> 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?VGluYQ==?= <Tina@discussions.microsoft.com> wrote

> >> >> on 12 okt 2006 in

> >> >> microsoft.public.windows.terminal_services:

> >> >>

> >> >> > Thanks for the response. We are using terminal services

> >> >> > so all the software runs from the server. I have a

> >> >> > question about the TS licenses. These computers are

> >> >> > actually replacements. Do I need to transfer the current

> >> >> > license from the old computer to the replacement computer?

> >> >> > Or is that something I should manage in Active

> >> >> > Directory???

> >> >> >

> >> >> > "Kshaeta" wrote:

> >> >> > > First, you only need terminal services if you want all

> >> >> > > of the software

> >> >> >> to run on your central server (much like a null terminal

> >> >> >> connected to a

> >> >> >> UNIX box, but prettier). It allows for centralization

> >> >> >> of your

> >> >> >> programs for easier management, as well as gives you more

> >> >> >> control over what people can do. It also alleviates a

> >> >> >> lot of security issues. Terminal services can also allow

> >> >> >> you to access it via web access. So (theoretically) you

> >> >> >> could access your data from a web browser. It makes it

> >> >> >> easier for users to move from computer to computer, since

> >> >> >> their settings are all saved on the terminal server.

> >> >> >>

> >> >> >> But that's beyond just a network. If all you want is to

> >> >> >> setup each workstation, and then install programs (word,

> >> >> >> excel, donkey kong, whatever) on each workstation, you

> >> >> >> don't need terminal services. You would just need to

> >> >> >> setup each system the way you like, and then creates

> >> >> >> directories to store data on the server(s), and create

> >> >> >> shares on the server (so the clients can connect). There

> >> >> >> are quite a few steps to this process, so I'll assume

> >> >> >> it's not what you want.

> >> >> >>

> >> >> >>

> >> >> >> For terminal server, you would need:

> >> >> >>

> >> >> >> Windows XP/2000 which comes with remote desktop (aka

> >> >> >> terminal services) installed.

> >> >> >>

> >> >> >> A windows 2000/2003 server to run terminal server, as

> >> >> >> well as a server to run terminal services licensing.

> >> >> >>

> >> >> >> You will need to purchase TS licenses, one for each user

> >> >> >> (or computer) from a licensed microsoft distributor.

> >> >> >>

> >> >> >> That's as brief as I get. I can't really go into the

> >> >> >> particulars, it would take to much time.

> >> >> >>

> >> >> >> If you go to windows website, you can find a section on

> >> >> >> Terminal Server and some white papers. It might help.

> >> >> >>

> >> >> >> Here are some links:

> >> >> >> http://www.brianmadden.com/content/content.asp?id=154

> >> >> >> http://www.brianmadden.com/subject.asp?ID=3

> >> >> >> http://www.microsoft.com/windowsserver2003/techinfo/overvi

> >> >> >> ew/ qui ckstart.mspx#EJAA

> >> >> >> http://technet2.microsoft.com/windowsserver/en/whitepapers

> >> >> >> .ms px

> >> >> >>

> >> >> >>

> >> >> >> Good luck!

> >> >> >> bill

>

[Guest Vera Noest [MVP]]

Re: Adding new client to 2003 server

 

Re: Adding new client to 2003 server

 

Logged on to the Terminal Server, right-click My Computer - Manage

- Expand Local Users and Groups - click on Groups - double-click on

Remote Desktop Users - click Add.

 

_________________________________________________________

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?U3Rld21hbg==?= <Stewman@discussions.microsoft.com> wrote

on 31 okt 2007 in microsoft.public.windows.terminal_services:

> I need to add only one person to connect via TS and not sure the

> steps to follow on my Win 2003 Svr. Do I go into TS MGR to add

> the new user? Thanks

>

> "Vera Noest [MVP]" wrote:

>

>> Assuming default configuration, the only thing you have to do

>> to give your users access to a 2003 Terminal Server is to make

>> them members of the local built-in "Remote Desktop Users" group

>> on the Terminal Server.

>> Best practice is to create a domain global security group, make

>> the users member of that group and make that group a member of

>> the local Remote Desktop Users group on the TS, rather than

>> adding individual user accounts to the local group. Makes user

>> management easier, especially if you have multiple terminal

>> Servers.

>> _________________________________________________________ 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?U3Rld21hbg==?= <Stewman@discussions.microsoft.com>

>> wrote on 31 okt 2007 in

>> microsoft.public.windows.terminal_services:

>>

>> > I am also new to Terminal Servers and would like to know what

>> > are the steps to add new Terminla Server users to a Windows

>> > 2003 Server?

>> >

>> > "Vera Noest [MVP]" wrote:

>> >

>> >> You're welcome! And yes, that happens all the time: you

>> >> *expect* something to be complicated, and thus you overlook

>> >> the easy solution :-)

>> >> _________________________________________________________

>> >> 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?VGluYQ==?= <Tina@discussions.microsoft.com> wrote

>> >> on 12 okt 2006 in

>> >> microsoft.public.windows.terminal_services:

>> >>

>> >> > Thank you, I suppose I'm making this harder than it needs

>> >> > to be. I appreciate the explanation!

>> >> >

>> >> > "Vera Noest [MVP]" wrote:

>> >> >

>> >> >> You don't have to do anything.

>> >> >>

>> >> >> TS CALs have an expiration date of 52-89 days after

>> >> >> issueing. Licenses that are not used (because the old

>> >> >> client does not connect to the TS anymore) will

>> >> >> automatically be returned to the LS after the expiration

>> >> >> date. In the meantime, your new clients will get a

>> >> >> temporary TS CAL, which is valid for 90 days.

>> >> >>

>> >> >> Note that these time periods are choosen to make sure

>> >> >> that your temporary license lasts long enough for the old

>> >> >> license to become available again. So replacing one

>> >> >> client with another can never cause you to run out of TS

>> >> >> CALs.

>> >> >> _________________________________________________________

>> >> >> 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?VGluYQ==?= <Tina@discussions.microsoft.com>

>> >> >> wrote on 12 okt 2006 in

>> >> >> microsoft.public.windows.terminal_services:

>> >> >>

>> >> >> > Thanks for the response. We are using terminal

>> >> >> > services so all the software runs from the server. I

>> >> >> > have a question about the TS licenses. These computers

>> >> >> > are actually replacements. Do I need to transfer the

>> >> >> > current license from the old computer to the

>> >> >> > replacement computer?

>> >> >> > Or is that something I should manage in Active

>> >> >> > Directory???

>> >> >> >

>> >> >> > "Kshaeta" wrote:

>> >> >> > > First, you only need terminal services if you want

>> >> >> > > all of the software

>> >> >> >> to run on your central server (much like a null

>> >> >> >> terminal connected to a

>> >> >> >> UNIX box, but prettier). It allows for

>> >> >> >> centralization of your

>> >> >> >> programs for easier management, as well as gives you

>> >> >> >> more control over what people can do. It also

>> >> >> >> alleviates a lot of security issues. Terminal services

>> >> >> >> can also allow you to access it via web access. So

>> >> >> >> (theoretically) you could access your data from a web

>> >> >> >> browser. It makes it easier for users to move from

>> >> >> >> computer to computer, since their settings are all

>> >> >> >> saved on the terminal server.

>> >> >> >>

>> >> >> >> But that's beyond just a network. If all you want is

>> >> >> >> to setup each workstation, and then install programs

>> >> >> >> (word, excel, donkey kong, whatever) on each

>> >> >> >> workstation, you don't need terminal services. You

>> >> >> >> would just need to setup each system the way you like,

>> >> >> >> and then creates directories to store data on the

>> >> >> >> server(s), and create shares on the server (so the

>> >> >> >> clients can connect). There are quite a few steps to

>> >> >> >> this process, so I'll assume it's not what you want.

>> >> >> >>

>> >> >> >>

>> >> >> >> For terminal server, you would need:

>> >> >> >>

>> >> >> >> Windows XP/2000 which comes with remote desktop (aka

>> >> >> >> terminal services) installed.

>> >> >> >>

>> >> >> >> A windows 2000/2003 server to run terminal server, as

>> >> >> >> well as a server to run terminal services licensing.

>> >> >> >>

>> >> >> >> You will need to purchase TS licenses, one for each

>> >> >> >> user (or computer) from a licensed microsoft

>> >> >> >> distributor.

>> >> >> >>

>> >> >> >> That's as brief as I get. I can't really go into the

>> >> >> >> particulars, it would take to much time.

>> >> >> >>

>> >> >> >> If you go to windows website, you can find a section

>> >> >> >> on Terminal Server and some white papers. It might

>> >> >> >> help.

>> >> >> >>

>> >> >> >> Here are some links:

>> >> >> >> http://www.brianmadden.com/content/content.asp?id=154

>> >> >> >> http://www.brianmadden.com/subject.asp?ID=3

>> >> >> >> http://www.microsoft.com/windowsserver2003/techinfo/ove

>> >> >> >> rvi ew/ qui ckstart.mspx#EJAA

>> >> >> >> http://technet2.microsoft.com/windowsserver/en/whitepap

>> >> >> >> ers .ms px

>> >> >> >>

>> >> >> >>

>> >> >> >> Good luck!

>> >> >> >> bill

[Guest Stewman]

Re: Adding new client to 2003 server

 

Re: Adding new client to 2003 server

 

It worked out great. Thanks for your help.

 

"Vera Noest [MVP]" wrote:

> Logged on to the Terminal Server, right-click My Computer - Manage

> - Expand Local Users and Groups - click on Groups - double-click on

> Remote Desktop Users - click Add.

>

> _________________________________________________________

> 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?U3Rld21hbg==?= <Stewman@discussions.microsoft.com> wrote

> on 31 okt 2007 in microsoft.public.windows.terminal_services:

>

> > I need to add only one person to connect via TS and not sure the

> > steps to follow on my Win 2003 Svr. Do I go into TS MGR to add

> > the new user? Thanks

> >

> > "Vera Noest [MVP]" wrote:

> >

> >> Assuming default configuration, the only thing you have to do

> >> to give your users access to a 2003 Terminal Server is to make

> >> them members of the local built-in "Remote Desktop Users" group

> >> on the Terminal Server.

> >> Best practice is to create a domain global security group, make

> >> the users member of that group and make that group a member of

> >> the local Remote Desktop Users group on the TS, rather than

> >> adding individual user accounts to the local group. Makes user

> >> management easier, especially if you have multiple terminal

> >> Servers.

> >> _________________________________________________________ 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?U3Rld21hbg==?= <Stewman@discussions.microsoft.com>

> >> wrote on 31 okt 2007 in

> >> microsoft.public.windows.terminal_services:

> >>

> >> > I am also new to Terminal Servers and would like to know what

> >> > are the steps to add new Terminla Server users to a Windows

> >> > 2003 Server?

> >> >

> >> > "Vera Noest [MVP]" wrote:

> >> >

> >> >> You're welcome! And yes, that happens all the time: you

> >> >> *expect* something to be complicated, and thus you overlook

> >> >> the easy solution :-)

> >> >> _________________________________________________________

> >> >> 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?VGluYQ==?= <Tina@discussions.microsoft.com> wrote

> >> >> on 12 okt 2006 in

> >> >> microsoft.public.windows.terminal_services:

> >> >>

> >> >> > Thank you, I suppose I'm making this harder than it needs

> >> >> > to be. I appreciate the explanation!

> >> >> >

> >> >> > "Vera Noest [MVP]" wrote:

> >> >> >

> >> >> >> You don't have to do anything.

> >> >> >>

> >> >> >> TS CALs have an expiration date of 52-89 days after

> >> >> >> issueing. Licenses that are not used (because the old

> >> >> >> client does not connect to the TS anymore) will

> >> >> >> automatically be returned to the LS after the expiration

> >> >> >> date. In the meantime, your new clients will get a

> >> >> >> temporary TS CAL, which is valid for 90 days.

> >> >> >>

> >> >> >> Note that these time periods are choosen to make sure

> >> >> >> that your temporary license lasts long enough for the old

> >> >> >> license to become available again. So replacing one

> >> >> >> client with another can never cause you to run out of TS

> >> >> >> CALs.

> >> >> >> _________________________________________________________

> >> >> >> 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?VGluYQ==?= <Tina@discussions.microsoft.com>

> >> >> >> wrote on 12 okt 2006 in

> >> >> >> microsoft.public.windows.terminal_services:

> >> >> >>

> >> >> >> > Thanks for the response. We are using terminal

> >> >> >> > services so all the software runs from the server. I

> >> >> >> > have a question about the TS licenses. These computers

> >> >> >> > are actually replacements. Do I need to transfer the

> >> >> >> > current license from the old computer to the

> >> >> >> > replacement computer?

> >> >> >> > Or is that something I should manage in Active

> >> >> >> > Directory???

> >> >> >> >

> >> >> >> > "Kshaeta" wrote:

> >> >> >> > > First, you only need terminal services if you want

> >> >> >> > > all of the software

> >> >> >> >> to run on your central server (much like a null

> >> >> >> >> terminal connected to a

> >> >> >> >> UNIX box, but prettier). It allows for

> >> >> >> >> centralization of your

> >> >> >> >> programs for easier management, as well as gives you

> >> >> >> >> more control over what people can do. It also

> >> >> >> >> alleviates a lot of security issues. Terminal services

> >> >> >> >> can also allow you to access it via web access. So

> >> >> >> >> (theoretically) you could access your data from a web

> >> >> >> >> browser. It makes it easier for users to move from

> >> >> >> >> computer to computer, since their settings are all

> >> >> >> >> saved on the terminal server.

> >> >> >> >>

> >> >> >> >> But that's beyond just a network. If all you want is

> >> >> >> >> to setup each workstation, and then install programs

> >> >> >> >> (word, excel, donkey kong, whatever) on each

> >> >> >> >> workstation, you don't need terminal services. You

> >> >> >> >> would just need to setup each system the way you like,

> >> >> >> >> and then creates directories to store data on the

> >> >> >> >> server(s), and create shares on the server (so the

> >> >> >> >> clients can connect). There are quite a few steps to

> >> >> >> >> this process, so I'll assume it's not what you want.

> >> >> >> >>

> >> >> >> >>

> >> >> >> >> For terminal server, you would need:

> >> >> >> >>

> >> >> >> >> Windows XP/2000 which comes with remote desktop (aka

> >> >> >> >> terminal services) installed.

> >> >> >> >>

> >> >> >> >> A windows 2000/2003 server to run terminal server, as

> >> >> >> >> well as a server to run terminal services licensing.

> >> >> >> >>

> >> >> >> >> You will need to purchase TS licenses, one for each

> >> >> >> >> user (or computer) from a licensed microsoft

> >> >> >> >> distributor.

> >> >> >> >>

> >> >> >> >> That's as brief as I get. I can't really go into the

> >> >> >> >> particulars, it would take to much time.

> >> >> >> >>

> >> >> >> >> If you go to windows website, you can find a section

> >> >> >> >> on Terminal Server and some white papers. It might

> >> >> >> >> help.

> >> >> >> >>

> >> >> >> >> Here are some links:

> >> >> >> >> http://www.brianmadden.com/content/content.asp?id=154

> >> >> >> >> http://www.brianmadden.com/subject.asp?ID=3

> >> >> >> >> http://www.microsoft.com/windowsserver2003/techinfo/ove

> >> >> >> >> rvi ew/ qui ckstart.mspx#EJAA

> >> >> >> >> http://technet2.microsoft.com/windowsserver/en/whitepap

> >> >> >> >> ers .ms px

> >> >> >> >>

> >> >> >> >>

> >> >> >> >> Good luck!

> >> >> >> >> bill

>

[Guest Vera Noest [MVP]]

Re: Adding new client to 2003 server

 

Re: Adding new client to 2003 server

 

You're welcome!

_________________________________________________________

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?U3Rld21hbg==?= <Stewman@discussions.microsoft.com> wrote

on 02 nov 2007 in microsoft.public.windows.terminal_services:

> It worked out great. Thanks for your help.

>

> "Vera Noest [MVP]" wrote:

>

>> Logged on to the Terminal Server, right-click My Computer -

>> Manage - Expand Local Users and Groups - click on Groups -

>> double-click on Remote Desktop Users - click Add.

>>

>> _________________________________________________________

>> 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?U3Rld21hbg==?= <Stewman@discussions.microsoft.com>

>> wrote on 31 okt 2007 in

>> microsoft.public.windows.terminal_services:

>>

>> > I need to add only one person to connect via TS and not sure

>> > the steps to follow on my Win 2003 Svr. Do I go into TS MGR

>> > to add the new user? Thanks

>> >

>> > "Vera Noest [MVP]" wrote:

>> >

>> >> Assuming default configuration, the only thing you have to

>> >> do to give your users access to a 2003 Terminal Server is to

>> >> make them members of the local built-in "Remote Desktop

>> >> Users" group on the Terminal Server.

>> >> Best practice is to create a domain global security group,

>> >> make the users member of that group and make that group a

>> >> member of the local Remote Desktop Users group on the TS,

>> >> rather than adding individual user accounts to the local

>> >> group. Makes user management easier, especially if you have

>> >> multiple terminal Servers.

>> >> _________________________________________________________

>> >> 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?U3Rld21hbg==?= <Stewman@discussions.microsoft.com>

>> >> wrote on 31 okt 2007 in

>> >> microsoft.public.windows.terminal_services:

>> >>

>> >> > I am also new to Terminal Servers and would like to know

>> >> > what are the steps to add new Terminla Server users to a

>> >> > Windows 2003 Server?

>> >> >

>> >> > "Vera Noest [MVP]" wrote:

>> >> >

>> >> >> You're welcome! And yes, that happens all the time: you

>> >> >> *expect* something to be complicated, and thus you

>> >> >> overlook the easy solution :-)

>> >> >> _________________________________________________________

>> >> >> 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?VGluYQ==?= <Tina@discussions.microsoft.com>

>> >> >> wrote on 12 okt 2006 in

>> >> >> microsoft.public.windows.terminal_services:

>> >> >>

>> >> >> > Thank you, I suppose I'm making this harder than it

>> >> >> > needs to be. I appreciate the explanation!

>> >> >> >

>> >> >> > "Vera Noest [MVP]" wrote:

>> >> >> >

>> >> >> >> You don't have to do anything.

>> >> >> >>

>> >> >> >> TS CALs have an expiration date of 52-89 days after

>> >> >> >> issueing. Licenses that are not used (because the old

>> >> >> >> client does not connect to the TS anymore) will

>> >> >> >> automatically be returned to the LS after the

>> >> >> >> expiration date. In the meantime, your new clients

>> >> >> >> will get a temporary TS CAL, which is valid for 90

>> >> >> >> days.

>> >> >> >>

>> >> >> >> Note that these time periods are choosen to make sure

>> >> >> >> that your temporary license lasts long enough for the

>> >> >> >> old license to become available again. So replacing

>> >> >> >> one client with another can never cause you to run out

>> >> >> >> of TS CALs.

>> >> >> >> _______________________________________________________

>> >> >> >> __ 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?VGluYQ==?= <Tina@discussions.microsoft.com>

>> >> >> >> wrote on 12 okt 2006 in

>> >> >> >> microsoft.public.windows.terminal_services:

>> >> >> >>

>> >> >> >> > Thanks for the response. We are using terminal

>> >> >> >> > services so all the software runs from the server.

>> >> >> >> > I have a question about the TS licenses. These

>> >> >> >> > computers are actually replacements. Do I need to

>> >> >> >> > transfer the current license from the old computer

>> >> >> >> > to the replacement computer?

>> >> >> >> > Or is that something I should manage in Active

>> >> >> >> > Directory???

>> >> >> >> >

>> >> >> >> > "Kshaeta" wrote:

>> >> >> >> > > First, you only need terminal services if you want

>> >> >> >> > > all of the software

>> >> >> >> >> to run on your central server (much like a null

>> >> >> >> >> terminal connected to a

>> >> >> >> >> UNIX box, but prettier). It allows for

>> >> >> >> >> centralization of your

>> >> >> >> >> programs for easier management, as well as gives

>> >> >> >> >> you more control over what people can do. It also

>> >> >> >> >> alleviates a lot of security issues. Terminal

>> >> >> >> >> services can also allow you to access it via web

>> >> >> >> >> access. So (theoretically) you could access your

>> >> >> >> >> data from a web browser. It makes it easier for

>> >> >> >> >> users to move from computer to computer, since

>> >> >> >> >> their settings are all saved on the terminal

>> >> >> >> >> server.

>> >> >> >> >>

>> >> >> >> >> But that's beyond just a network. If all you want

>> >> >> >> >> is to setup each workstation, and then install

>> >> >> >> >> programs (word, excel, donkey kong, whatever) on

>> >> >> >> >> each workstation, you don't need terminal services.

>> >> >> >> >> You would just need to setup each system the way

>> >> >> >> >> you like, and then creates directories to store

>> >> >> >> >> data on the server(s), and create shares on the

>> >> >> >> >> server (so the clients can connect). There are

>> >> >> >> >> quite a few steps to this process, so I'll assume

>> >> >> >> >> it's not what you want.

>> >> >> >> >>

>> >> >> >> >>

>> >> >> >> >> For terminal server, you would need:

>> >> >> >> >>

>> >> >> >> >> Windows XP/2000 which comes with remote desktop

>> >> >> >> >> (aka terminal services) installed.

>> >> >> >> >>

>> >> >> >> >> A windows 2000/2003 server to run terminal server,

>> >> >> >> >> as well as a server to run terminal services

>> >> >> >> >> licensing.

>> >> >> >> >>

>> >> >> >> >> You will need to purchase TS licenses, one for each

>> >> >> >> >> user (or computer) from a licensed microsoft

>> >> >> >> >> distributor.

>> >> >> >> >>

>> >> >> >> >> That's as brief as I get. I can't really go into

>> >> >> >> >> the particulars, it would take to much time.

>> >> >> >> >>

>> >> >> >> >> If you go to windows website, you can find a

>> >> >> >> >> section on Terminal Server and some white papers.

>> >> >> >> >> It might help.

>> >> >> >> >>

>> >> >> >> >> Here are some links:

>> >> >> >> >> http://www.brianmadden.com/content/content.asp?id=15

>> >> >> >> >> 4 http://www.brianmadden.com/subject.asp?ID=3

>> >> >> >> >> http://www.microsoft.com/windowsserver2003/techinfo/

>> >> >> >> >> ove rvi ew/ qui ckstart.mspx#EJAA

>> >> >> >> >> http://technet2.microsoft.com/windowsserver/en/white

>> >> >> >> >> pap ers .ms px

>> >> >> >> >>

>> >> >> >> >>

>> >> >> >> >> Good luck!

>> >> >> >> >> bill