RDC to local console session

I tried to RDC to console session of SBS2000 machine using both

mstsc /console
mstsc /admin

But neither work when connecting to sbs2000 machine. I can get to work when
connecting to sbs2003 machine. What do I have to do different?

"SBS user" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I tried to RDC to console session of SBS2000 machine using both
>
> mstsc /console
> mstsc /admin
>
> But neither work when connecting to sbs2000 machine. I can get to work
> when connecting to sbs2003 machine. What do I have to do different?


Because SBS 2000 is essentially Windows 2000, you must add the Terminal
Services feature (Remote Administration Mode) in Add/Remove, Windows
Components, first. Was that added?

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum to benefit from collaboration
among responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCSE, MCSA 2003 & 2000, MCSA Messaging
Microsoft Certified Trainer
(E-Mail Removed)
http://twitter.com/acefekay

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Only items in the Terminal Services are:
Client creator files
Enable terminal services

Both of these items are checked, but they are the only 2 in there.


"Ace Fekay [MCT]" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> "SBS user" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>>I tried to RDC to console session of SBS2000 machine using both
>>
>> mstsc /console
>> mstsc /admin
>>
>> But neither work when connecting to sbs2000 machine. I can get to work
>> when connecting to sbs2003 machine. What do I have to do different?
>
>
> Because SBS 2000 is essentially Windows 2000, you must add the Terminal
> Services feature (Remote Administration Mode) in Add/Remove, Windows
> Components, first. Was that added?
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Please reply back to the newsgroup or forum to benefit from collaboration
> among responding engineers, and to help others benefit from your
> resolution.
>
> Ace Fekay, MCT, MCSE, MCSA 2003 & 2000, MCSA Messaging
> Microsoft Certified Trainer
> (E-Mail Removed)
> http://twitter.com/acefekay
>
> For urgent issues, you may want to contact Microsoft PSS directly. Please
> check http://support.microsoft.com for regional support phone numbers.

"SBS user" <(E-Mail Removed)> wrote in message news:%(E-Mail Removed)...
> Only items in the Terminal Services are:
> Client creator files
> Enable terminal services
>
> Both of these items are checked, but they are the only 2 in there.

Client Creator files is not an object in Add-Remove\Windows Components. Where do you see this setting at?

Ace

It is in my system. The two items I mentioned are the only ones in there.

"Ace Fekay [MCT]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
"SBS user" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Only items in the Terminal Services are:
> Client creator files
> Enable terminal services
>
> Both of these items are checked, but they are the only 2 in there.

Client Creator files is not an object in Add-Remove\Windows Components.
Where do you see this setting at?

Ace

"SBS user" <(E-Mail Removed)> wrote in message news:OYk$(E-Mail Removed)...
> It is in my system. The two items I mentioned are the only ones in there.
>


Where exactly, in your system?

Add-Remove\Windows Components

"Ace Fekay [MCT]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
"SBS user" <(E-Mail Removed)> wrote in message
news:OYk$(E-Mail Removed)...
> It is in my system. The two items I mentioned are the only ones in there.
>


Where exactly, in your system?

"SBS user" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>
> Where exactly, in your system?


Ok, Ihad to check on an older Windows 2000 installation, so now I know what
you mean. Sorry about that. However, I don't have an SBS 2000 to test it on.

What I can say with the Windows 2000 server, which I already have Terminal
Services installed in Remote ADmin mode, I just tested "mstsc /v:servername
/console" from a Windows 2003 server and that worked, but the /admin switch
is not an option. You can see the options by typing in "mstsc /?" and a
screen will pop up showing you the available options, which you will see
that the /admin option is not an option. That's a new option with Vista and
2008.

To look at available mstsc options, read the thread in this link:
http://forums.firedaemon.com/accessi...6e2cb2845&amp;

So if the "mstsc /v:servername /console" doesn't work, nor simply trying to
connect using Remote desktop Connection, then it would appear that Terminal
Services weren't installed correctly, where I would suggest to uninstall and
reinstall Terminal Services.

However, because this is SBS 2000, Terminal Services may have been installed
in Application Mode, which is a bit different, but it shouldn't stop you
from using the mstsc command from a 2003 or newer machine.

I am cross-posting this to the SBS group, where the SBS experts can provide
more specific help.Maybe I'm missing something that they may be more
familiar with. Jsut check back here for responses. But for future reference,
if using a newsreader (which I suggest to use and appears you alread are),
the newsgroup is called:
microsoft.public.windows.server.sbs

If using web access (which limits your optons), the URL is (watch the URL
line wrap):
http://www.microsoft.com/communities...&lang=en&cr=US

Ace


Original post:
==============
"SBS user" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I tried to RDC to console session of SBS2000 machine using both
>
> mstsc /console
> mstsc /admin
>
> But neither work when connecting to sbs2000 machine. I can get to work
> when connecting to sbs2003 machine. What do I have to do different?


Because SBS 2000 is essentially Windows 2000, you must add the Terminal
Services feature (Remote Administration Mode) in Add/Remove, Windows
Components, first. Was that added?

---
> Only items in the Terminal Services are:
> Client creator files
> Enable terminal services

Both of these items are checked, but they are the only 2 in there.
---

Thanks for that update, I will give it a try.

"Ace Fekay [MCT]" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> "SBS user" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>>
>> Where exactly, in your system?
>
>
> Ok, Ihad to check on an older Windows 2000 installation, so now I know
> what you mean. Sorry about that. However, I don't have an SBS 2000 to test
> it on.
>
> What I can say with the Windows 2000 server, which I already have Terminal
> Services installed in Remote ADmin mode, I just tested "mstsc
> /v:servername /console" from a Windows 2003 server and that worked, but
> the /admin switch is not an option. You can see the options by typing in
> "mstsc /?" and a screen will pop up showing you the available options,
> which you will see that the /admin option is not an option. That's a new
> option with Vista and 2008.
>
> To look at available mstsc options, read the thread in this link:
> http://forums.firedaemon.com/accessi...6e2cb2845&amp;
>
> So if the "mstsc /v:servername /console" doesn't work, nor simply trying
> to connect using Remote desktop Connection, then it would appear that
> Terminal Services weren't installed correctly, where I would suggest to
> uninstall and reinstall Terminal Services.
>
> However, because this is SBS 2000, Terminal Services may have been
> installed in Application Mode, which is a bit different, but it shouldn't
> stop you from using the mstsc command from a 2003 or newer machine.
>
> I am cross-posting this to the SBS group, where the SBS experts can
> provide more specific help.Maybe I'm missing something that they may be
> more familiar with. Jsut check back here for responses. But for future
> reference, if using a newsreader (which I suggest to use and appears you
> alread are), the newsgroup is called:
> microsoft.public.windows.server.sbs
>
> If using web access (which limits your optons), the URL is (watch the URL
> line wrap):
> http://www.microsoft.com/communities...&lang=en&cr=US
>
> Ace
>
>
> Original post:
> ==============
> "SBS user" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>>I tried to RDC to console session of SBS2000 machine using both
>>
>> mstsc /console
>> mstsc /admin
>>
>> But neither work when connecting to sbs2000 machine. I can get to work
>> when connecting to sbs2003 machine. What do I have to do different?
>
>
> Because SBS 2000 is essentially Windows 2000, you must add the Terminal
> Services feature (Remote Administration Mode) in Add/Remove, Windows
> Components, first. Was that added?
>
> ---
>> Only items in the Terminal Services are:
>> Client creator files
>> Enable terminal services
>
> Both of these items are checked, but they are the only 2 in there.
> ---
>

I tried what you suggested from your last post. It did not work. I was
connected to one of the terminal sessions and not console. I know that it
is not in aplication mode. Do you have any other advice?

"Ace Fekay [MCT]" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> "SBS user" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>>
>> Where exactly, in your system?
>
>
> Ok, Ihad to check on an older Windows 2000 installation, so now I know
> what you mean. Sorry about that. However, I don't have an SBS 2000 to test
> it on.
>
> What I can say with the Windows 2000 server, which I already have Terminal
> Services installed in Remote ADmin mode, I just tested "mstsc
> /v:servername /console" from a Windows 2003 server and that worked, but
> the /admin switch is not an option. You can see the options by typing in
> "mstsc /?" and a screen will pop up showing you the available options,
> which you will see that the /admin option is not an option. That's a new
> option with Vista and 2008.
>
> To look at available mstsc options, read the thread in this link:
> http://forums.firedaemon.com/accessi...6e2cb2845&amp;
>
> So if the "mstsc /v:servername /console" doesn't work, nor simply trying
> to connect using Remote desktop Connection, then it would appear that
> Terminal Services weren't installed correctly, where I would suggest to
> uninstall and reinstall Terminal Services.
>
> However, because this is SBS 2000, Terminal Services may have been
> installed in Application Mode, which is a bit different, but it shouldn't
> stop you from using the mstsc command from a 2003 or newer machine.
>
> I am cross-posting this to the SBS group, where the SBS experts can
> provide more specific help.Maybe I'm missing something that they may be
> more familiar with. Jsut check back here for responses. But for future
> reference, if using a newsreader (which I suggest to use and appears you
> alread are), the newsgroup is called:
> microsoft.public.windows.server.sbs
>
> If using web access (which limits your optons), the URL is (watch the URL
> line wrap):
> http://www.microsoft.com/communities...&lang=en&cr=US
>
> Ace
>
>
> Original post:
> ==============
> "SBS user" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>>I tried to RDC to console session of SBS2000 machine using both
>>
>> mstsc /console
>> mstsc /admin
>>
>> But neither work when connecting to sbs2000 machine. I can get to work
>> when connecting to sbs2003 machine. What do I have to do different?
>
>
> Because SBS 2000 is essentially Windows 2000, you must add the Terminal
> Services feature (Remote Administration Mode) in Add/Remove, Windows
> Components, first. Was that added?
>
> ---
>> Only items in the Terminal Services are:
>> Client creator files
>> Enable terminal services
>
> Both of these items are checked, but they are the only 2 in there.
> ---
>