Terminal Services

[Brian Z]

I have a Windows 2003 SErver SP2 running Terminal Services with an IP of
192.168.100.101. Everyone in the Company Remotes into this machine from Home,
and then they use RDP again to their XP or Vista desktops.

Is there ANY way I could program a Snap-in for each user on the 2003
terminal server, so they can just hit a button to get the their PC? The thing
is it always seems to forget their Domain, then they are confused about the
Local PC name coming up in the Username box.

I know there is a Snap in in the Admin Tools of 2003, but that seems
overkill. Also there is the Web Client, but I would need to program that to
remember the credentials. I would also like to save even their usernames and
passwords if possible so there is no question that it is not what they
mis-typed.

I can not tell you how much time people are spending because they are not
typing the correct things in the RDP box.

Thank You!

 

[IshmaelDS]

Re: Terminal Services

On Nov 2, 1:27 pm, Brian Z <Bri...@discussions.microsoft.com> wrote:
> I have a Windows 2003 SErver SP2 running Terminal Services with an IP of
> 192.168.100.101. Everyone in the Company Remotes into this machine from Home,
> and then they use RDP again to their XP or Vista desktops.
>
> Is there ANY way I could program a Snap-in for each user on the 2003
> terminal server, so they can just hit a button to get the their PC? The thing
> is it always seems to forget their Domain, then they are confused about the
> Local PC name coming up in the Username box.
>
> I know there is a Snap in in the Admin Tools of 2003, but that seems
> overkill. Also there is the Web Client, but I would need to program that to
> remember the credentials. I would also like to save even their usernames and
> passwords if possible so there is no question that it is not what they
> mis-typed.
>
> I can not tell you how much time people are spending because they are not
> typing the correct things in the RDP box.
>
> Thank You!

Well you can save the RDP connection settings and have all that saved
in the file including things like if you want printers mapped ect.
When you open the RDP client click on options and at the bottom left
of the window you will see a save button. Setup your settings then
click that save it, and put a shortcut on their desktops(so if they do
delete it you can make it again easily). Though I wouldn't really
reccommend that. You could setup port forwarding and change the
listening ports on the PC's in the network to each listen to an
individual port and thus cut a little bit of the lag of running a RDP
session within an RDP session. If you do that though make sure your
users have very secure passwords.

 

[IshmaelDS]

Re: Terminal Services

On Nov 2, 1:45 pm, IshmaelDS <ishmae...@gmail.com> wrote:
> On Nov 2, 1:27 pm, Brian Z <Bri...@discussions.microsoft.com> wrote:
>
>
>
> > I have a Windows 2003 SErver SP2 running Terminal Services with an IP of
> > 192.168.100.101. Everyone in the Company Remotes into this machine from Home,
> > and then they use RDP again to their XP or Vista desktops.
>
> > Is there ANY way I could program a Snap-in for each user on the 2003
> > terminal server, so they can just hit a button to get the their PC? The thing
> > is it always seems to forget their Domain, then they are confused about the
> > Local PC name coming up in the Username box.
>
> > I know there is a Snap in in the Admin Tools of 2003, but that seems
> > overkill. Also there is the Web Client, but I would need to program that to
> > remember the credentials. I would also like to save even their usernames and
> > passwords if possible so there is no question that it is not what they
> > mis-typed.
>
> > I can not tell you how much time people are spending because they are not
> > typing the correct things in the RDP box.
>
> > Thank You!
>
> Well you can save the RDP connection settings and have all that saved
> in the file including things like if you want printers mapped ect.
> When you open the RDP client click on options and at the bottom left
> of the window you will see a save button. Setup your settings then
> click that save it, and put a shortcut on their desktops(so if they do
> delete it you can make it again easily). Though I wouldn't really
> reccommend that. You could setup port forwarding and change the
> listening ports on the PC's in the network to each listen to an
> individual port and thus cut a little bit of the lag of running a RDP
> session within an RDP session. If you do that though make sure your
> users have very secure passwords.

Found this thread which you may also want to look into as well.
http://groups.google.ca/group/micro...08493/acda01301cccb87b?hl=en#acda01301cccb87b

 

[Brian Z]

Re: Terminal Services

I would like to do that on the Windows 2003 server, however, it does not give
me an option to save the domain. For some reason is it grayed out. For the
domain and password it says "You will be asked when you connect".

"IshmaelDS" wrote:

> On Nov 2, 1:27 pm, Brian Z <Bri...@discussions.microsoft.com> wrote:
> > I have a Windows 2003 SErver SP2 running Terminal Services with an IP of
> > 192.168.100.101. Everyone in the Company Remotes into this machine from Home,
> > and then they use RDP again to their XP or Vista desktops.
> >
> > Is there ANY way I could program a Snap-in for each user on the 2003
> > terminal server, so they can just hit a button to get the their PC? The thing
> > is it always seems to forget their Domain, then they are confused about the
> > Local PC name coming up in the Username box.
> >
> > I know there is a Snap in in the Admin Tools of 2003, but that seems
> > overkill. Also there is the Web Client, but I would need to program that to
> > remember the credentials. I would also like to save even their usernames and
> > passwords if possible so there is no question that it is not what they
> > mis-typed.
> >
> > I can not tell you how much time people are spending because they are not
> > typing the correct things in the RDP box.
> >
> > Thank You!
>
> Well you can save the RDP connection settings and have all that saved
> in the file including things like if you want printers mapped ect.
> When you open the RDP client click on options and at the bottom left
> of the window you will see a save button. Setup your settings then
> click that save it, and put a shortcut on their desktops(so if they do
> delete it you can make it again easily). Though I wouldn't really
> reccommend that. You could setup port forwarding and change the
> listening ports on the PC's in the network to each listen to an
> individual port and thus cut a little bit of the lag of running a RDP
> session within an RDP session. If you do that though make sure your
> users have very secure passwords.
>
>

 

[Brian Z]

Re: Terminal Services

The issue is that SP2 XP "breaks" the save password feature. I just set a
group policy, and waiting for it to fix itself. I can connect, i have no
problem there. It is just saving the credentials.

"IshmaelDS" wrote:

> On Nov 2, 1:45 pm, IshmaelDS <ishmae...@gmail.com> wrote:
> > On Nov 2, 1:27 pm, Brian Z <Bri...@discussions.microsoft.com> wrote:
> >
> >
> >
> > > I have a Windows 2003 SErver SP2 running Terminal Services with an IP of
> > > 192.168.100.101. Everyone in the Company Remotes into this machine from Home,
> > > and then they use RDP again to their XP or Vista desktops.
> >
> > > Is there ANY way I could program a Snap-in for each user on the 2003
> > > terminal server, so they can just hit a button to get the their PC? The thing
> > > is it always seems to forget their Domain, then they are confused about the
> > > Local PC name coming up in the Username box.
> >
> > > I know there is a Snap in in the Admin Tools of 2003, but that seems
> > > overkill. Also there is the Web Client, but I would need to program that to
> > > remember the credentials. I would also like to save even their usernames and
> > > passwords if possible so there is no question that it is not what they
> > > mis-typed.
> >
> > > I can not tell you how much time people are spending because they are not
> > > typing the correct things in the RDP box.
> >
> > > Thank You!
> >
> > Well you can save the RDP connection settings and have all that saved
> > in the file including things like if you want printers mapped ect.
> > When you open the RDP client click on options and at the bottom left
> > of the window you will see a save button. Setup your settings then
> > click that save it, and put a shortcut on their desktops(so if they do
> > delete it you can make it again easily). Though I wouldn't really
> > reccommend that. You could setup port forwarding and change the
> > listening ports on the PC's in the network to each listen to an
> > individual port and thus cut a little bit of the lag of running a RDP
> > session within an RDP session. If you do that though make sure your
> > users have very secure passwords.
>
> Found this thread which you may also want to look into as well.
> http://groups.google.ca/group/micro...08493/acda01301cccb87b?hl=en#acda01301cccb87b
>
>

 

[IshmaelDS]

Re: Terminal Services

On Nov 2, 2:24 pm, Brian Z <Bri...@discussions.microsoft.com> wrote:
> The issue is that SP2 XP "breaks" the save password feature. I just set a
> group policy, and waiting for it to fix itself. I can connect, i have no
> problem there. It is just saving the credentials.
>
> "IshmaelDS" wrote:
> > On Nov 2, 1:45 pm, IshmaelDS <ishmae...@gmail.com> wrote:
> > > On Nov 2, 1:27 pm, Brian Z <Bri...@discussions.microsoft.com> wrote:
>
> > > > I have a Windows 2003 SErver SP2 running Terminal Services with an IP of
> > > > 192.168.100.101. Everyone in the Company Remotes into this machine from Home,
> > > > and then they use RDP again to their XP or Vista desktops.
>
> > > > Is there ANY way I could program a Snap-in for each user on the 2003
> > > > terminal server, so they can just hit a button to get the their PC? The thing
> > > > is it always seems to forget their Domain, then they are confused about the
> > > > Local PC name coming up in the Username box.
>
> > > > I know there is a Snap in in the Admin Tools of 2003, but that seems
> > > > overkill. Also there is the Web Client, but I would need to program that to
> > > > remember the credentials. I would also like to save even their usernames and
> > > > passwords if possible so there is no question that it is not what they
> > > > mis-typed.
>
> > > > I can not tell you how much time people are spending because they are not
> > > > typing the correct things in the RDP box.
>
> > > > Thank You!
>
> > > Well you can save the RDP connection settings and have all that saved
> > > in the file including things like if you want printers mapped ect.
> > > When you open the RDP client click on options and at the bottom left
> > > of the window you will see a save button. Setup your settings then
> > > click that save it, and put a shortcut on their desktops(so if they do
> > > delete it you can make it again easily). Though I wouldn't really
> > > reccommend that. You could setup port forwarding and change the
> > > listening ports on the PC's in the network to each listen to an
> > > individual port and thus cut a little bit of the lag of running a RDP
> > > session within an RDP session. If you do that though make sure your
> > > users have very secure passwords.
>
> > Found this thread which you may also want to look into as well.
> >http://groups.google.ca/group/microsoft.public.windows.terminal_servi...
Check out this site it may have the answer for you. Other than that
I'm at a loss at this point as I tried to create a RDP connection from
scratch and it just no longer picks up the username and domain
lines.
http://blogs.msdn.com/ts/archive/2007/01/22/vista-remote-desktop-connection-authentication-faq.aspx