Re: Time zone redirection

OK, I understand.

There are a couple of differences between Remote Desktop for
Administration and full-blown Terminal Services.
And there should be, because the objectives of the two are quite
different.
Your scenario is non-standard in that you want the functionality of
full-blown Terminal Services, but for just a single user.

But I'm glad that you have been able to solve the problem in a
different way.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Graham Stevenson" <grahams@xxxxxxxx> wrote on 01 apr 2007 in
microsoft.public.windows.terminal_services:

Vera,

Yes - although I thought I had made it quite clear in the first
post - never mind. It looks like Terminal Services, it smells
like Terminal Services, and you connect just like Terminal
Services, and you manage it via 'Terminal services Manager' - so
I assumed that it WAS Terminal Services but just limited to two
client connections :-O. Never thought it was a different
application :-O - some strange thinking going on over in
Redmond......

All I needed it for was to allow another colleague to be able to
administer a specific application, which I thought required his
TimeZone.

Well - obviously that does not work in Remote Desktop Admin mode
- which is a great pity really and I don't see why it has been
disabled.

I hoped that this would be a quick win to a simple scenario - OH
NO....

I have now had to turn the issue around and address the
applcation (which is probably what I should have done in the
first place) - and why it is/was using the wrong timezone - I
think that I have it fixed now, he just needs to try it out.

Many thanks for your assistance however ;-)).

Regards

Graham

"Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in message
news:Xns99059DF915632veranoesthemutforsse@xxxxxxxxxxxxxxxx
I was beginnng to suspect something along these lines.
I *believe* that the problem was a licensing problem per sé,
but the fact that you simply hadn't installed Terminal
Services, you were just using Remote Desktop for
Administration.

And that would also mean that it's not going to work on your
Web Edition server, because a Web Edition server cannot run
terminal Services, only Remote Desktop for Administration.

I'm unclear about your needs, though.
Do you really want Terminal Services, and if yes, on which box?
Note that you have a maximum of 3 concurrent connections to
each server without the need of a Licensing Server or TS CALs.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Graham Stevenson" <grahams@xxxxxxxx> wrote on 01 apr 2007 in
microsoft.public.windows.terminal_services:

Well - I have FINALLY managed to fix that issue - and YES it
is a licensing issue.

I had to install a 'TS Licensing Server' (and activate it) -
then change the settings on my Terminal Server to 'Per User'
mode.

Now - when I connect - my TimeZone is correctly implemented.

So - two issues remain :

1. WHY do the configuration tools (including RSOP) fail to
point this out. They incorrectly state that the policies are
enabled etc. and make no mention of the fact that as the TS is
not licensed and activated, these settings will be ignored.
This has cost me a days work to get this far!!.

2. Will this setup work on a Windows 2003 Server (Web Edition)
?? - as per my original posting. If not - then this whole
exercise has been a complete waste of time.

Many Thanks

Regards

Graham

"Graham Stevenson" <grahams@xxxxxxxx> wrote in message
news:eHUIJiDdHHA.4172@xxxxxxxxxxxxxxxxxxxxxxx
Vera,

Is this simply a licensing issue ????.

I am trying to use the 2 included licenses, as my 'other'
user (where I need TZ control) requires access to administer
a specific application and not full admin rights to the box.

My TS mode is limited to 'Remote Desktop for Administration'.

NB I have a number of additional 2003 CAL's - should these be
added, and if so - will they provide better TS integration
??.

Thanks again...

Graham


"Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message
news:Xns9904DACB0C967veranoesthemutforsse@xxxxxxxxxxxxxxxx
Pass-through authentication (username and password for
client logon is passed through to the server) is not a
feature of Windows 2003 TS. You would need Citrix for that.

But in your situation, no add-on product could do that for
you, since your local username on the PC has no meaning to
the server. You have to be authenticated on the server,
which in your case means that you have to log in with a
username which is a local account on the server.
Pass-through authentication is only possible with the server
and the PC in the same or trusted domains, and using a
domain account (and Citrix).

But I don't think this is the problem either, because this
is a normal situation (client and server not in same or
trusted domains).

I assume that there is nothing in the EventLog?
I think that my next step would be to enable verbose userenv
logging on the server.

221833 - How to enable user environment debug logging in
retail builds of Windows
http://support.microsoft.com/?kbid=221833

Interpreting Userenv log files
http://technet2.microsoft.com/WindowsServer/en/Library/ccd7b4
30 - 99a5-40fd-b68a-6c1979e565a21033.mspx
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Graham Stevenson" <grahams@xxxxxxxx> wrote on 31 mar 2007
in microsoft.public.windows.terminal_services:

Vera,

I have just tried a few more things....

Using 5.1 and 6

1. SET TZ=EST+05 in my user environment variables on the
client

2. Create a server user with the same credentials as my
desktop user.

3. Changing TZ in the tasktray clock as well as the TZ
environment variable

All = same results.

Now here is a thought. The remote system asks for my
credentials, and never seems to be able to accept my Client
PC login ??? - ie the server is assuming that I am a local
user, and so possibly won't use my Client PC's settings
???. I have yet to figure out how to make RDP try to use my
client login credentials - is this possible and could this
be my problem ??.

Thanks

Graham
"Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message
news:Xns9903EB4494D87veranoesthemutforsse@xxxxxxxxxxxxxxxx
I don't think that the absense of a AD domain should have
any
impact.
For the sake of troubleshooting, can you install the rdp
5.2 client and check if that works?

And you're not connecting to the console session, are you?
The console session always uses the server's time.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Graham Stevenson" <grahams@xxxxxxxx> wrote on 30 mar 2007
in microsoft.public.windows.terminal_services:

Hi,

This problem is driving me mad. Wasted about 5 hours
yesterday trying to get my RDP (V6) client to redirect
its timezone to two different 2003 servers. Neither will
work
:-( - and always show the current server time, with admin
and standard user accounts.

Redirection is enabled in LGPO and shows as enabled using
RSOP.

Both 2003 servers are stand-alone no domain or AD in
sight. I guess this is why it doesn't work...

After enabling TZ redirection I set my client (XP Pro X64
- and an XPPro 32 bit VM) to a different TZ. Then connect
to the server(s) and the desktop clock shows server time.
In case it was just the clock - opened up a cmd prompt
and typed TIME - same result.

One Server 2003 is Web edition with SP2, the other is
Standard with SP1.

Hope someone has some ideas ;-O.

Thanks

Graham
.

Relevant Pages

  • Re: Users Cant Log Into Local Machine That Is Attached To A Domai
    ... Are you trying to access to a T.S server? ... Are you trying to access via RDC (Remote desktop connection) to a Windows ... Terminal Services Client Error Message: You Do Not Have Access to Logon to ... You do not have access to logon to the Session. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Client behind a firewall!
    ... Microsoft MVP - Terminal Server ... Internet with Remote Desktop enabled when I'm at work, ... Remote Desktop client is blocked, and I just can't use it. ...
    (microsoft.public.windows.terminal_services)
  • Re: terminal services and 70-290
    ... Wish they would just call it remote desktop protocol and keep it uniform. ... do have a little server set up on virtual pc and installed the remote admin ... Terminal Services uses the RDP for communicating ... Configure a server to enable Remote Desktop For Administration ...
    (microsoft.public.cert.exam.mcse)
  • Re: Does Terminal Server Licensing turn off Remote Desktop for Adm
    ... Why would you keep Terminal Server Licensing Service, ... There is no need whatsoever for TS Licensing in this situation. ... Remote Desktop for Administration does *not* need any TS CALs, ... a license after I have installed Terminal Services?" ...
    (microsoft.public.win2000.termserv.apps)
  • Re: Recommendations for how to connect to SBS from a remote site please?
    ... >> server for email, database access, file access and client/server access ... >> Now I know that SBS2000 has terminal services built in, ... >> services built in, just remote desktop. ... what do I recommend to my client: ...
    (microsoft.public.windows.server.sbs)