|
From: Vera Noest [MVP]
<vera.noest@remove-this.hem.utfors.se>
To:
none
Subject:
Re: GPO Settings
Date:
09/24/2007 15:47:50
comments inline
"Bob" wrote on 24 sep 2007 in
microsoft.public.windows.terminal_services:
> Hi,
>
> I've a few things I'd like to do with TS and I
think the
> following GPO's will help, but I'm not sure.
Could someone
> please confirm my thoughts?
>
> EXISTING SETTINGS:
> ------------------------
> In Computer Configuration, Administrative
Templates, Windows
> Components, Terminal Services:
>
> Enabled - Restrict Terminal Services users to a
single remote
> session
> Enabled - Set time limit for disconnected
sessions (2
> hours)
> Enabled - Sets a time limit for active but idle
Terminal
> Services sessions (2 hours)
> Enabled - Terminate session when time limits are
reached
> Not Configed - Limit number of connections
>
> QUESTIONS:
> ------------------
>
> "Keep-Alive Connections"
> --------------------------
> By enabling this, I think I will return to my
prior session
> after a disconnect and all my previously opened
applications
> will return as I left them before my disconnect.
There is the
> "Keep-alive interval" setting, but I
don't understand its
> description. I would think this is used to set
how long my
> sessions is kept alive after a disconnect, but
the description
> indicates how often my session is checked?
Anyway, if I set
> this for "10", does this mean that my
that I have 10 minutes to
> re-establish my connection before my work is
lost?
KeepAlive does what the description says, it puts a
heartbeat on
the connection to detect if the connection is still
alive. Without
this mechanism, a session may not transition to a
disconnected
state and may remain active even though the client is
physically
disconnected from the Terminal Server. And that would
mean that you
cannot reconnect to the session, because the server
thinks that it
is still an active session.
If your session disconnects because of a network
problem, and the
server detects this in time because of the KeepAlive
meachanism,
the session will exist on the server for the time
specified in the
setting "Set time limit for disconnected sessions
(2 hours)". When
you connect to the server again, you will be
reconnected to the
disconnected session.
> "Set path for TS Roaming Profiles"
> ----------------------------------
> I have roaming user profiles set for my local
domain environment
> and when these same users connect via TS, they
create a local
> profile on the server at "C:\Documents and
Settings". This in
> turn can fill my C-Drive up with a lot of local
profiles. I use
> the DelProf.exe every 30-days to clear these out.
>
> Can I use the "Set path for TS Roaming
Profiles" to place these
> profiles on a different partition? And if so,
will DelProf.exe
> find them in the future?
Yes, by all means!
Note that this will still create a local copy of the
roaming
profile in C:\Documents and Settings. But you can use
this GPO
settings to get rid of them again:
Computer Configuration - Administrative Templates -
System - User
profiles
"Delete cached copies of roaming profiles"
so your server will never store more cached profiles
than the
number of concurrent users connecting to it.
I've never used delprof, but as I understand it, it
does more or
less the same as the GPO setting mentioned above.
Using a roaming profile can (but doesn't have to)
cause slightly
longer logon times, because the centrally stored
profile on the
file server has to be copied to the locally cached
profile on the
terminal Server. You can and should therefore minimize
the size of
the profile by using Folder redirection settings in
the GPO. At the
minimum, redirect the My Documents folder to the users
home
directory.
> Also, I don't understand what a "Home
Directory" is and
> therefore I don't understand how "TS User
Home Directory" may
> help here. I'm thinking a "Home
Directory" is a legacy to NT
> and it doesn't apply to my 2003 server and XP
clients?
The TS home directory is the folder in which the
\windows subfolder
is created. In this \windows subfolder, user-specific
settings are
stored (like ini files), which would reside in
%systemroot% on a
workstation.
Using Home Directories with Terminal Server
http://technet2.microsoft.com/windowsserver/en/library/a60adb56-
7f30-4984-a062-7e43143852111033.mspx
246132 - User Profile and Home Directory Behavior with
Terminal
Services
http://support.microsoft.com/?kbid=246132
> Security:
> --------
> Not a GPO question, but one about access. I now
have VPN access
> to my environment, but the users have a tough
time setting it up
> on their home computers. What risks do I run if I
open port
> 3389 on my router and direct it to my TS server
(which is
> everything else too - DC, Exchange, etc). (I
believe by opening
> this port, the VPN Client Access software on the
remote
> computers is no longer necessary).
Don't do this!
That would mean that there's only a single password
between your
domain, mailserver, and TS and the rest of the world.
Even if you enforce strong passwords on all of your
users, I would
*not* recommend it.
Running TS on a DC is not recommended either, for both
security and
performance reasons, but is sometimes the only way in
a very small
business.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email
___
Top
From: v-kzhao@online.microsoft.com (Ken
Zhao [MSFT])
To:
none
Subject:
Re: GPO Settings
Date:
09/24/2007 21:25:04
Hello Bob,
Thank you for using newsgroup and thanks Vera Noest
for his great
information sharing.
From your post,
Thanks ?
Ken Zhao
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security /www.microsoft.com/security>
====================================================
When responding to posts, please "Reply to
Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no
warranties, and confers no rights.
--------------------
| Subject: Re: GPO Settings
| From: "Vera Noest [MVP]"
| References:
| Message-ID:
| User-Agent: Xnews/06.08.25
| Newsgroups:
microsoft.public.windows.terminal_services
| Date: Mon, 24 Sep 2007 13:47:50 -0700
| NNTP-Posting-Host: h249n2fls309o851.telia.com
81.224.241.249
| Lines: 1
| Path:
TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.terminal_services:11181
| X-Tomcat-NG:
microsoft.public.windows.terminal_services
|
| comments inline
|
| "Bob" wrote on 24 sep 2007 in
| microsoft.public.windows.terminal_services:
|
| > Hi,
| >
| > I've a few things I'd like to do with TS and I
think the
| > following GPO's will help, but I'm not sure.
Could someone
| > please confirm my thoughts?
| >
| > EXISTING SETTINGS:
| > ------------------------
| > In Computer Configuration, Administrative
Templates, Windows
| > Components, Terminal Services:
| >
| > Enabled - Restrict Terminal Services users to a
single remote
| > session
| > Enabled - Set time limit for disconnected
sessions (2
| > hours)
| > Enabled - Sets a time limit for active but idle
Terminal
| > Services sessions (2 hours)
| > Enabled - Terminate session when time limits
are reached
| > Not Configed - Limit number of connections
| >
| > QUESTIONS:
| > ------------------
| >
| > "Keep-Alive Connections"
| > --------------------------
| > By enabling this, I think I will return to my
prior session
| > after a disconnect and all my previously opened
applications
| > will return as I left them before my
disconnect. There is the
| > "Keep-alive interval" setting, but I
don't understand its
| > description. I would think this is used to set
how long my
| > sessions is kept alive after a disconnect, but
the description
| > indicates how often my session is checked?
Anyway, if I set
| > this for "10", does this mean that my
that I have 10 minutes to
| > re-establish my connection before my work is
lost?
|
| KeepAlive does what the description says, it puts a
heartbeat on
| the connection to detect if the connection is still
alive. Without
| this mechanism, a session may not transition to a
disconnected
| state and may remain active even though the client
is physically
| disconnected from the Terminal Server. And that
would mean that you
| cannot reconnect to the session, because the server
thinks that it
| is still an active session.
| If your session disconnects because of a network
problem, and the
| server detects this in time because of the KeepAlive
meachanism,
| the session will exist on the server for the time
specified in the
| setting "Set time limit for disconnected
sessions (2 hours)". When
| you connect to the server again, you will be
reconnected to the
| disconnected session.
|
|
| > "Set path for TS Roaming Profiles"
| > ----------------------------------
| > I have roaming user profiles set for my local
domain environment
| > and when these same users connect via TS, they
create a local
| > profile on the server at "C:\Documents and
Settings". This in
| > turn can fill my C-Drive up with a lot of local
profiles. I use
| > the DelProf.exe every 30-days to clear these
out.
| >
| > Can I use the "Set path for TS Roaming
Profiles" to place these
| > profiles on a different partition? And if so,
will DelProf.exe
| > find them in the future?
|
| Yes, by all means!
| Note that this will still create a local copy of the
roaming
| profile in C:\Documents and Settings. But you can
use this GPO
| settings to get rid of them again:
|
| Computer Configuration - Administrative Templates -
System - User
| profiles
| "Delete cached copies of roaming profiles"
|
| so your server will never store more cached profiles
than the
| number of concurrent users connecting to it.
| I've never used delprof, but as I understand it, it
does more or
| less the same as the GPO setting mentioned above.
|
| Using a roaming profile can (but doesn't have to)
cause slightly
| longer logon times, because the centrally stored
profile on the
| file server has to be copied to the locally cached
profile on the
| terminal Server. You can and should therefore
minimize the size of
| the profile by using Folder redirection settings in
the GPO. At the
| minimum, redirect the My Documents folder to the
users home
| directory.
|
| > Also, I don't understand what a "Home
Directory" is and
| > therefore I don't understand how "TS User
Home Directory" may
| > help here. I'm thinking a "Home
Directory" is a legacy to NT
| > and it doesn't apply to my 2003 server and XP
clients?
|
| The TS home directory is the folder in which the
\windows subfolder
| is created. In this \windows subfolder,
user-specific settings are
| stored (like ini files), which would reside in
%systemroot% on a
| workstation.
|
| Using Home Directories with Terminal Server
| http://technet2.microsoft.com/windowsserver/en/library/a60adb56-
| 7f30-4984-a062-7e43143852111033.mspx
|
| 246132 - User Profile and Home Directory Behavior
with Terminal
| Services
| http://support.microsoft.com/?kbid=246132
|
| > Security:
| > --------
| > Not a GPO question, but one about access. I now
have VPN access
| > to my environment, but the users have a tough
time setting it up
| > on their home computers. What risks do I run if
I open port
| > 3389 on my router and direct it to my TS server
(which is
| > everything else too - DC, Exchange, etc). (I
believe by opening
| > this port, the VPN Client Access software on
the remote
| > computers is no longer necessary).
|
| Don't do this!
| That would mean that there's only a single password
between your
| domain, mailserver, and TS and the rest of the
world.
| Even if you enforce strong passwords on all of your
users, I would
| *not* recommend it.
|
| Running TS on a DC is not recommended either, for
both security and
| performance reasons, but is sometimes the only way
in a very small
| business.
|
_________________________________________________________
| Vera Noest
| MCSE, CCEA, Microsoft MVP - Terminal Server
| TS troubleshooting: http://ts.veranoest.net
| ___ please respond in newsgroup, NOT by private
email ___
|
Top
From: Meinolf Weber
To:
none
Subject:
Re: Event ID: 1004 - Trm srvr cannot issue a client license.
Need advise?
Date:
09/29/2007 12:18:23
Hello DougD,
Check out this one:
http://support.microsoft.com/kb/315277
Or is a thin client trying to connect?
http://support.microsoft.com/kb/827355
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS"
with no warranties, and confers
no rights.
> Hello. I have a issue where a Windows 2000
terminal server is
> displaying the Event ID: 1004 error "The
terminal server cannot issue
> a client license" message in the event logs.
A month ago the Terminal
> Server was also a backup domain controller but I
had to demote it to
> a standard member server. Since then the error
code 1004 comes up. We
> are using a new Windows 2003 domain controller
that the Terminal
> server is in the same domain as. The Windows 2003
domain controller
> does not have terminal server licensing service
running on it. Is my
> fix as simple as installing the windows 2003 term
server licensing? I
> have no plans immediately on installing terminal
services on that
> windows 2003 server since I plan on keeping the
windows 2000 terminal
> server running. Will my existing windows 2000
terminal server cals
> install on the windows 2003 server if I install
the terminal services
> licensing?
>
> Thanks for any assistance.
>
> Doug D
>
Top
From: DougD <DougD@nospam.com>
To:
none
Subject:
Re: Event ID: 1004 - Trm srvr cannot issue a client license.
Need advise?
Date:
09/29/2007 12:39:45
Hello. Meinolf. Thank you for your prompt response.
Since typing my
original request I installed the Terminal Server
Licensing on the
Windows 2003 domain controller and
the windows 2000 terminal server can see that windows
2003 server and
the terminal server licensing on it. I was able to
connect into my
terminal server via my vpn gateway where before
installing the
licensing server I was unable to do this. My fear is
my current Windows
2000 Terminal server cals will not install on the
windows 2003 terminal
server licensing without purchasing upgraded licenses.
The windows 2003
terminal server licensing is currently running in the
"not activated"
state. I assume I have 60 days before I have to active
this?
Thank you.
DougD
On 2007-09-29 13:18:23 -0400, Meinolf Weber said:
> Hello DougD,
>
> Check out this one:
> http://support.microsoft.com/kb/315277
>
> Or is a thin client trying to connect?
> http://support.microsoft.com/kb/827355
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS
IS" with no warranties, and
> confers no rights.
>
>> Hello. I have a issue where a Windows 2000
terminal server is
>> displaying the Event ID: 1004 error "The
terminal server cannot issue
>> a client license" message in the event
logs. A month ago the Terminal
>> Server was also a backup domain controller
but I had to demote it to
>> a standard member server. Since then the
error code 1004 comes up. We
>> are using a new Windows 2003 domain
controller that the Terminal
>> server is in the same domain as. The Windows
2003 domain controller
>> does not have terminal server licensing
service running on it. Is my
>> fix as simple as installing the windows 2003
term server licensing? I
>> have no plans immediately on installing
terminal services on that
>> windows 2003 server since I plan on keeping
the windows 2000 terminal
>> server running. Will my existing windows 2000
terminal server cals
>> install on the windows 2003 server if I
install the terminal services
>> licensing?
>>
>> Thanks for any assistance.
>>
>> Doug D
Top
From: Meinolf Weber
<meiweb(nospam)@gmx.de>
To:
none
Subject:
Re: Event ID: 1004 - Trm srvr cannot issue a client license.
Need advise?
Date:
09/29/2007 13:00:43
Hello DougD,
Check out this one about the upgrade of licenses:
http://techrepublic.com.com/5208-6230-0.html?forumID=101?
In 2003 you have 120 day's as grace period.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS"
with no warranties, and confers
no rights.
> Hello. Meinolf. Thank you for your prompt
response. Since typing my
> original request I installed the Terminal Server
Licensing on the
> Windows 2003 domain controller and
> the windows 2000 terminal server can see that
windows 2003 server and
> the terminal server licensing on it. I was able
to connect into my
> terminal server via my vpn gateway where before
installing the
> licensing server I was unable to do this. My fear
is my current
> Windows
> 2000 Terminal server cals will not install on the
windows 2003
> terminal
> server licensing without purchasing upgraded
licenses. The windows
> 2003
> terminal server licensing is currently running in
the "not activated"
> state. I assume I have 60 days before I have to
active this?
> Thank you.
>
> DougD
>
> On 2007-09-29 13:18:23 -0400, Meinolf Weber said:
>
>> Hello DougD,
>>
>> Check out this one:
>> http://support.microsoft.com/kb/315277
>> Or is a thin client trying to connect?
>> http://support.microsoft.com/kb/827355
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS
IS" with no warranties, and
>> confers no rights.
>>> Hello. I have a issue where a Windows
2000 terminal server is
>>> displaying the Event ID: 1004 error
"The terminal server cannot
>>> issue a client license" message in
the event logs. A month ago the
>>> Terminal Server was also a backup domain
controller but I had to
>>> demote it to a standard member server.
Since then the error code
>>> 1004 comes up. We are using a new Windows
2003 domain controller
>>> that the Terminal server is in the same
domain as. The Windows 2003
>>> domain controller does not have terminal
server licensing service
>>> running on it. Is my fix as simple as installing
the windows 2003
>>> term server licensing? I have no plans
immediately on installing
>>> terminal services on that windows 2003
server since I plan on
>>> keeping the windows 2000 terminal server
running. Will my existing
>>> windows 2000 terminal server cals install
on the windows 2003 server
>>> if I install the terminal services
licensing?
>>>
>>> Thanks for any assistance.
>>>
>>> Doug D
>>>
Top
From: Vera Noest [MVP] <vera.noest@remove-this.hem.utfors.se>
To:
none
Subject:
Re: Event ID: 1004 - Trm srvr cannot issue a client license.
Need advise?
Date:
09/29/2007 14:24:11
The 120 day grace period of 2003 is *not* applicable
in this
situation!
A grace period (which is the period in which a newly
installed
Terminal Server can function without the need to
contact a TS
Licensing Server) is a feature of a *terminal Server*,
not of a TS
Licensing Server.
The W2K Terminal Server has long past used up its
grace period.
Changing to a new TS LS on a 2003 server will *not*
gibe the W2K TS
a second grace period.
Doug, your initial problem occurred when you demoted
the W2K DC to
a member server, because a W2K TS LS must run on a
Domain
Controller. If you look in the EventLog of the W2K TS,
you will
find:
Event ID 29
"Terminal Services Licensing can only be run on
Domain Controllers
or Server in a Workgroup." and
Event ID 7024
"The Terminal Services Licensing service
terminated with service-
specific error 29."
Your decision to install the TS Licensing Service on
the 2003
server was the right decision. Now you have to
activate it as well.
About your licenses: you do *not* have to upgrade your
W2K TS CALs!
As long as your Terminal Server runs W2K, W2K TS CALs
are all you
need (+ 2003 server CALs, but you should already have
those, since
you have a 2003 DC).
If all of your clients run W2K Pro, XP Pro or Vista
Business, then
they are issued the free "Existing Windows 2000
Per Device TS
CALs", which are also present on a 2003 TS
Licensing Server.
Only if you have down-level clients (XP Home Edition,
thin clients,
unix, Macintosh), then you need purchased W2K TS CALs.
You are correct that you cannot install them on the
2003 TS
Licensing Server, because you only can install a
License Pack once.
But you can simply call the Microsoft Clearinghouse
and they will
re-issue your License Pack for installation on the new
2003 TS LS.
Make sure that you have the paperwork ready when you call
them.
291795 - HOW TO: Locate a Phone Number for the
Microsoft
Clearinghouse
http://support.microsoft.com/?kbid=291795
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email
___
Meinolf Weber wrote on 29 sep 2007 in
microsoft.public.windows.terminal_services:
> Hello DougD,
>
> Check out this one about the upgrade of licenses:
>
http://techrepublic.com.com/5208-6230-0.html?forumID=101?
> =208697?
>
> In 2003 you have 120 day's as grace period.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS
IS" with no warranties,
> and confers no rights.
>
>> Hello. Meinolf. Thank you for your prompt
response. Since
>> typing my original request I installed the
Terminal Server
>> Licensing on the Windows 2003 domain
controller and
>> the windows 2000 terminal server can see that
windows 2003
>> server and the terminal server licensing on
it. I was able to
>> connect into my terminal server via my vpn
gateway where before
>> installing the licensing server I was unable
to do this. My
>> fear is my current Windows
>> 2000 Terminal server cals will not install on
the windows 2003
>> terminal
>> server licensing without purchasing upgraded
licenses. The
>> windows 2003
>> terminal server licensing is currently
running in the "not
>> activated" state. I assume I have 60 days
before I have to
>> active this? Thank you.
>>
>> DougD
>>
>> On 2007-09-29 13:18:23 -0400, Meinolf Weber
said:
>>
>>> Hello DougD,
>>>
>>> Check out this one:
>>> http://support.microsoft.com/kb/315277
>>> Or is a thin client trying to connect?
>>> http://support.microsoft.com/kb/827355
>>> Best regards
>>>
>>> Meinolf Weber
>>> Disclaimer: This posting is provided
"AS IS" with no
>>> warranties, and confers no rights.
>>>> Hello. I have a issue where a Windows
2000 terminal server is
>>>> displaying the Event ID: 1004 error
"The terminal server
>>>> cannot issue a client license"
message in the event logs. A
>>>> month ago the Terminal Server was
also a backup domain
>>>> controller but I had to demote it to
a standard member
>>>> server. Since then the error code
1004 comes up. We are using
>>>> a new Windows 2003 domain controller
that the Terminal server
>>>> is in the same domain as. The Windows
2003 domain controller
>>>> does not have terminal server
licensing service running on
>>>> it. Is my fix as simple as installing
the windows 2003 term
>>>> server licensing? I have no plans
immediately on installing
>>>> terminal services on that windows
2003 server since I plan on
>>>> keeping the windows 2000 terminal
server running. Will my
>>>> existing windows 2000 terminal server
cals install on the
>>>> windows 2003 server if I install the
terminal services
>>>> licensing?
>>>>
>>>> Thanks for any assistance.
>>>>
>>>> Doug D
Top
From: Anders
<Anders@discussions.microsoft.com>
To:
none
Subject:
Re: Event ID : 1004 - The terminal server cannot optain a
client l
Date:
09/20/2007 09:02:02
Hi Vera
1. The Licensing Server is running on the DC
2. Yes, it is running.
3. I did found some errors in the event log :
Event Type: Warning
Event Source: TermServLicensing
Event Category: None
Event ID: 22
Date: 19-09-2007
Time: 09:25:57
User: N/A
Computer: BIWEB
Description:
The Terminal Services Licensing server BIWEB has no
license pack registered
for product 'Windows 2000 Terminal Services Client
Access License'. Use
Terminal Services Licensing administrative tool to
register the licenses pack.
Event Type: Warning
Event Source: TermService
Event Category: None
Event ID: 1013
Date: 15-02-2007
Time: 11:39:28
User: N/A
Computer: BIWEB
Description:
The terminal server has exceeded the maximum number of
allowed connections.
4. About "loosing" the Terminal Servers, I
am convinced that the "Terminal
Service Licensing Manager" once could see the
Terminal Servers, but I am not
sure.
5. Yes - At the Terminal Service Licensing Manager I
can see the licenses
tha are issued.
Existing Win 2000 license - Buil-in - Unlimited - 45
Issued
Temp license for existing win 2000 license - Temp - 2
Issued
Temp license Win 2000 term service Client Access -
Temp - 6 Issued
6. I Implementet the q239107 only at one of my
terminal servers, just to
see if it worked, but it did´nt.
Do I have to try to deactivate / reactivate the
Terminal Licensing Server ??
Best Regards
Anders
"Vera Noest [MVP]" wrote:
> comments inline
>
> =?Utf-8?B?QW5kZXJz?= wrote on
> 19 sep 2007 in
microsoft.public.windows.terminal_services:
>
> > I have a Win2000 TS licensing server and 2
Win2000 TS running in
> > AppMode.
>
> Is the TS Licensing Server running on the Domain
Controller? Have
> you checked that it is actually running?
> Are there any errors or warnings in the EventLog
on the TS
> Licensing Server?
>
> > I have about 40 users, Win XP and Intermec
devices
> > using the TS. When I try to connect with
some new clients I get
> > a 1004 error. All the "old"
clients are working fine, but I
> > cannot connect with any of the new clients.
> >
> > The licensing server have "lost"
all my TS, I can just see the
> > licensing server it self.
>
> The licensing server has no knowledge about your
Terminal Servers,
> so it can't have lost them either.
> It's the other way around, your Terminal Servers
must be able to
> find your TS Licensing Server.
>
> > When I am trying to connect to one of
> > my TS from the licensing server, I got this
message : Windows
> > cannot connect to a licensing server.
>
> When you open the TS Licensing Manager on the TS
Licensing Server,
> do you see the licenses that are issued? If not,
do you see them
> when you connect to the TS Licensing Server
(*not* a TS)?
>
> > I have tried to follow the Guidelines from
Q239107, but it still
> > dos´nt work.
>
> On which server did you try to implement KB
239107? I suspect that
> you made the registry change on the TS Licensing
Server. If so, you
> must do it on each terminal Server.
>
> > It seems that I have got a system where it
is´nt possible to
> > connect any new clients !!
> >
> > Anybody - help !!!
> >
> > Regards Anders
>
_________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private
email ___
>
Top
From: Vera Noest [MVP]
<vera.noest@remove-this.hem.utfors.se>
To:
none
Subject:
Re: Event ID : 1004 - The terminal server cannot optain a
client l
Date:
09/20/2007 14:16:15
OK, that explains your issue.
You simply have to purchase and install TS CALs for
your down-level
clients.
Seems you need 6 of them, one for each client who has
been issued a
"Temporary license Win 2000 term service Client
Access"
_________________________________________________________
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?QW5kZXJz?= wrote on
20 sep 2007 in
microsoft.public.windows.terminal_services:
> Hi Vera
>
> 1. The Licensing Server is running on the DC
> 2. Yes, it is running.
> 3. I did found some errors in the event log :
>
> Event Type: Warning
> Event Source: TermServLicensing
> Event Category: None
> Event ID: 22
> Date: 19-09-2007
> Time: 09:25:57
> User: N/A
> Computer: BIWEB
> Description:
> The Terminal Services Licensing server BIWEB has
no license pack
> registered for product 'Windows 2000 Terminal
Services Client
> Access License'. Use Terminal Services Licensing
administrative
> tool to register the licenses pack.
>
>
> Event Type: Warning
> Event Source: TermService
> Event Category: None
> Event ID: 1013
> Date: 15-02-2007
> Time: 11:39:28
> User: N/A
> Computer: BIWEB
> Description:
> The terminal server has exceeded the maximum
number of allowed
> connections.
>
> 4. About "loosing" the Terminal
Servers, I am convinced that the
> "Terminal Service Licensing Manager"
once could see the Terminal
> Servers, but I am not sure.
>
> 5. Yes - At the Terminal Service Licensing
Manager I can see the
> licenses tha are issued.
>
> Existing Win 2000 license - Buil-in - Unlimited -
45 Issued
> Temp license for existing win 2000 license - Temp
- 2 Issued
> Temp license Win 2000 term service Client Access
- Temp - 6
> Issued
>
> 6. I Implementet the q239107 only at one of my
terminal
> servers, just to see if it worked, but it
did´nt.
>
> Do I have to try to deactivate / reactivate the
Terminal
> Licensing Server ??
>
> Best Regards
>
> Anders
>
>
> "Vera Noest [MVP]" wrote:
>
>> comments inline
>>
>> =?Utf-8?B?QW5kZXJz?= wrote
>> on 19 sep 2007 in
microsoft.public.windows.terminal_services:
>>
>> > I have a Win2000 TS licensing server and
2 Win2000 TS running
>> > in AppMode.
>>
>> Is the TS Licensing Server running on the
Domain Controller?
>> Have you checked that it is actually running?
>> Are there any errors or warnings in the
EventLog on the TS
>> Licensing Server?
>>
>> > I have about 40 users, Win XP and
Intermec devices
>> > using the TS. When I try to connect with
some new clients I
>> > get a 1004 error. All the
"old" clients are working fine, but
>> > I cannot connect with any of the new
clients.
>> >
>> > The licensing server have
"lost" all my TS, I can just see
>> > the licensing server it self.
>>
>> The licensing server has no knowledge about
your Terminal
>> Servers, so it can't have lost them either.
>> It's the other way around, your Terminal
Servers must be able
>> to find your TS Licensing Server.
>>
>> > When I am trying to connect to one of
>> > my TS from the licensing server, I got
this message : Windows
>> > cannot connect to a licensing server.
>>
>> When you open the TS Licensing Manager on the
TS Licensing
>> Server, do you see the licenses that are
issued? If not, do you
>> see them when you connect to the TS Licensing
Server (*not* a
>> TS)?
>>
>> > I have tried to follow the Guidelines
from Q239107, but it
>> > still dos´nt work.
>>
>> On which server did you try to implement KB
239107? I suspect
>> that you made the registry change on the TS
Licensing Server.
>> If so, you must do it on each terminal
Server.
>>
>> > It seems that I have got a system where
it is´nt possible
>> > to connect any new clients !!
>> >
>> > Anybody - help !!!
>> >
>> > Regards Anders
>>
_________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by
private email ___
Top
From: Anders <Anders@discussions.microsoft.com>
To:
none
Subject:
Re: Event ID : 1004 - The terminal server cannot optain a
client l
Date:
09/20/2007 15:50:02
OK - maybe it is a stupid question, but I believe that
my Win XP and Intermec
terminals had a license for free at Terminal Service
2000, it is the main
reason why I choose the TS2000. I am aware of that I
have to pay for all
licenses to a Terminal Server 2003, but also TS 2000
??
"Vera Noest [MVP]" wrote:
> OK, that explains your issue.
> You simply have to purchase and install TS CALs
for your down-level
> clients.
> Seems you need 6 of them, one for each client who
has been issued a
> "Temporary license Win 2000 term service
Client Access"
>
> _________________________________________________________
> 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?QW5kZXJz?= wrote on
> 20 sep 2007 in microsoft.public.windows.terminal_services:
>
> > Hi Vera
> >
> > 1. The Licensing Server is running on the DC
> > 2. Yes, it is running.
> > 3. I did found some errors in the event log
:
> >
> > Event Type: Warning
> > Event Source: TermServLicensing
> > Event Category: None
> > Event ID: 22
> > Date: 19-09-2007
> > Time: 09:25:57
> > User: N/A
> > Computer: BIWEB
> > Description:
> > The Terminal Services Licensing server BIWEB
has no license pack
> > registered for product 'Windows 2000
Terminal Services Client
> > Access License'. Use Terminal Services
Licensing administrative
> > tool to register the licenses pack.
> >
> >
> > Event Type: Warning
> > Event Source: TermService
> > Event Category: None
> > Event ID: 1013
> > Date: 15-02-2007
> > Time: 11:39:28
> > User: N/A
> > Computer: BIWEB
> > Description:
> > The terminal server has exceeded the maximum
number of allowed
> > connections.
> >
> > 4. About "loosing" the Terminal
Servers, I am convinced that the
> > "Terminal Service Licensing
Manager" once could see the Terminal
> > Servers, but I am not sure.
> >
> > 5. Yes - At the Terminal Service Licensing
Manager I can see the
> > licenses tha are issued.
> >
> > Existing Win 2000 license - Buil-in -
Unlimited - 45 Issued
> > Temp license for existing win 2000 license -
Temp - 2 Issued
> > Temp license Win 2000 term service Client
Access - Temp - 6
> > Issued
> >
> > 6. I Implementet the q239107 only at one of
my terminal
> > servers, just to see if it worked, but it
did´nt.
> >
> > Do I have to try to deactivate / reactivate
the Terminal
> > Licensing Server ??
> >
> > Best Regards
> >
> > Anders
> >
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> comments inline
> >>
> >> =?Utf-8?B?QW5kZXJz?= wrote
> >> on 19 sep 2007 in
microsoft.public.windows.terminal_services:
> >>
> >> > I have a Win2000 TS licensing
server and 2 Win2000 TS running
> >> > in AppMode.
> >>
> >> Is the TS Licensing Server running on
the Domain Controller?
> >> Have you checked that it is actually
running?
> >> Are there any errors or warnings in the
EventLog on the TS
> >> Licensing Server?
> >>
> >> > I have about 40 users, Win XP and
Intermec devices
> >> > using the TS. When I try to connect
with some new clients I
> >> > get a 1004 error. All the
"old" clients are working fine, but
> >> > I cannot connect with any of the
new clients.
> >> >
> >> > The licensing server have
"lost" all my TS, I can just see
> >> > the licensing server it self.
> >>
> >> The licensing server has no knowledge
about your Terminal
> >> Servers, so it can't have lost them
either.
> >> It's the other way around, your Terminal
Servers must be able
> >> to find your TS Licensing Server.
> >>
> >> > When I am trying to connect to one
of
> >> > my TS from the licensing server, I
got this message : Windows
> >> > cannot connect to a licensing
server.
> >>
> >> When you open the TS Licensing Manager
on the TS Licensing
> >> Server, do you see the licenses that are
issued? If not, do you
> >> see them when you connect to the TS
Licensing Server (*not* a
> >> TS)?
> >>
> >> > I have tried to follow the
Guidelines from Q239107, but it
> >> > still dos´nt work.
> >>
> >> On which server did you try to implement
KB 239107? I suspect
> >> that you made the registry change on the
TS Licensing Server.
> >> If so, you must do it on each terminal
Server.
> >>
> >> > It seems that I have got a system
where it is´nt possible
> >> > to connect any new clients !!
> >> >
> >> > Anybody - help !!!
> >> >
> >> > Regards Anders
> >>
_________________________________________________________
> >> Vera Noest
> >> MCSE, CCEA, Microsoft MVP - Terminal
Server
> >> TS troubleshooting:
http://ts.veranoest.net
> >> ___ please respond in newsgroup, NOT by
private email ___
>
Top
From: Vera Noest [MVP]
<vera.noest@remove-this.hem.utfors.se>
To:
none
Subject:
Re: Event ID : 1004 - The terminal server cannot optain a
client l
Date:
09/21/2007 13:30:33
Only W2K Pro, XP Pro and Vista Business clients
receive a free TS
CAL from the built-in pool of licenses on the
Licensing Server (the
licenses that are called "Existing Win 2000
license - Built-in -
Unlimited").
All downlevel clients (thin clients, linux, Macintosh,
XP Home,
etc) need a purchased TS CAL.
So it's probably your Intermec clients that need a
purchased TS
CAL. You can verify that when you check which clients
have received
an temporary W2K Per Device CAL.
_________________________________________________________
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?QW5kZXJz?= wrote on
20 sep 2007 in microsoft.public.windows.terminal_services:
> OK - maybe it is a stupid question, but I believe
that my Win XP
> and Intermec terminals had a license for free at
Terminal
> Service 2000, it is the main reason why I choose
the TS2000. I
> am aware of that I have to pay for all licenses
to a Terminal
> Server 2003, but also TS 2000 ??
>
> "Vera Noest [MVP]" wrote:
>
>> OK, that explains your issue.
>> You simply have to purchase and install TS
CALs for your
>> down-level clients.
>> Seems you need 6 of them, one for each client
who has been
>> issued a "Temporary license Win 2000
term service Client
>> Access"
>>
>>
_________________________________________________________
>> 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?QW5kZXJz?= wrote
>> on 20 sep 2007 in
microsoft.public.windows.terminal_services:
>>
>> > Hi Vera
>> >
>> > 1. The Licensing Server is running on
the DC
>> > 2. Yes, it is running.
>> > 3. I did found some errors in the event
log :
>> >
>> > Event Type: Warning
>> > Event Source: TermServLicensing
>> > Event Category: None
>> > Event ID: 22
>> > Date: 19-09-2007
>> > Time: 09:25:57
>> > User: N/A
>> > Computer: BIWEB
>> > Description:
>> > The Terminal Services Licensing server
BIWEB has no license
>> > pack registered for product 'Windows
2000 Terminal Services
>> > Client Access License'. Use Terminal
Services Licensing
>> > administrative tool to register the
licenses pack.
>> >
>> >
>> > Event Type: Warning
>> > Event Source: TermService
>> > Event Category: None
>> > Event ID: 1013
>> > Date: 15-02-2007
>> > Time: 11:39:28
>> > User: N/A
>> > Computer: BIWEB
>> > Description:
>> > The terminal server has exceeded the
maximum number of
>> > allowed connections.
>> >
>> > 4. About "loosing" the
Terminal Servers, I am convinced that
>> > the "Terminal Service Licensing
Manager" once could see the
>> > Terminal Servers, but I am not sure.
>> >
>> > 5. Yes - At the Terminal Service
Licensing Manager I can see
>> > the licenses tha are issued.
>> >
>> > Existing Win 2000 license - Buil-in -
Unlimited - 45 Issued
>> > Temp license for existing win 2000
license - Temp - 2 Issued
>> > Temp license Win 2000 term service
Client Access - Temp - 6
>> > Issued
>> >
>> > 6. I Implementet the q239107 only at one
of my terminal
>> > servers, just to see if it worked, but
it did´nt.
>> >
>> > Do I have to try to deactivate /
reactivate the Terminal
>> > Licensing Server ??
>> >
>> > Best Regards
>> >
>> > Anders
>> >
>> >
>> > "Vera Noest [MVP]" wrote:
>> >
>> >> comments inline
>> >>
>> >> =?Utf-8?B?QW5kZXJz?=
>> >> wrote on 19 sep 2007 in
>> >> microsoft.public.windows.terminal_services:
>> >>
>> >> > I have a Win2000 TS licensing
server and 2 Win2000 TS
>> >> > running in AppMode.
>> >>
>> >> Is the TS Licensing Server running
on the Domain Controller?
>> >> Have you checked that it is actually
running?
>> >> Are there any errors or warnings in
the EventLog on the TS
>> >> Licensing Server?
>> >>
>> >> > I have about 40 users, Win XP
and Intermec devices
>> >> > using the TS. When I try to
connect with some new clients
>> >> > I get a 1004 error. All the
"old" clients are working
>> >> > fine, but I cannot connect with
any of the new clients.
>> >> >
>> >> > The licensing server have
"lost" all my TS, I can just see
>> >> > the licensing server it self.
>> >>
>> >> The licensing server has no
knowledge about your Terminal
>> >> Servers, so it can't have lost them
either.
>> >> It's the other way around, your
Terminal Servers must be
>> >> able to find your TS Licensing
Server.
>> >>
>> >> > When I am trying to connect to
one of
>> >> > my TS from the licensing
server, I got this message :
>> >> > Windows cannot connect to a
licensing server.
>> >>
>> >> When you open the TS Licensing
Manager on the TS Licensing
>> >> Server, do you see the licenses that
are issued? If not, do
>> >> you see them when you connect to the
TS Licensing Server
>> >> (*not* a TS)?
>> >>
>> >> > I have tried to follow the
Guidelines from Q239107, but it
>> >> > still dos´nt work.
>> >>
>> >> On which server did you try to
implement KB 239107? I
>> >> suspect that you made the registry
change on the TS
>> >> Licensing Server. If so, you must do
it on each terminal
>> >> Server.
>> >>
>> >> > It seems that I have got a
system where it is´nt
>> >> > possible to connect any new
clients !!
>> >> >
>> >> > Anybody - help !!!
>> >> >
>> >> > Regards Anders
>> >>
_________________________________________________________
>> >> Vera Noest
>> >> MCSE, CCEA, Microsoft MVP - Terminal
Server
>> >> TS troubleshooting:
http://ts.veranoest.net
>> >> ___ please respond in newsgroup, NOT
by private email ___
Top
From: Anders
<Anders@discussions.microsoft.com>
To:
none
Subject:
Re: Event ID : 1004 - The terminal server cannot optain a
client l
Date:
10/02/2007 06:26:02
Hi again
It is`nt easy !!
The Activation Status of the TS license server is
ACTIVATED.
The Temp lic for W2K TS CAL are identified, and are
not the Intermec Clients.
When I`m trying to add more Licenses, I got this info
:
The license server`s activation has expired. To use
this license server, you
must reactivate it. Do you want to reactivate the
server now?
I have`nt reactivated the server yet, because I`m not
sure what is going to
happen with my existing and OK clients. As I have
mentiont, I have newer
installed any CAL at my licensing server. I have been
told that my Intermec
terminals have a CAL for free, and it seems to be
correct, it have worked for
about 2½ year, until now.
It seems that I have to reactivate the license server,
but what will happen
with my existing Clients ??
Best Regards
Anders
"Vera Noest [MVP]" wrote:
> Only W2K Pro, XP Pro and Vista Business clients
receive a free TS
> CAL from the built-in pool of licenses on the
Licensing Server (the
> licenses that are called "Existing Win 2000
license - Built-in -
> Unlimited").
>
> All downlevel clients (thin clients, linux,
Macintosh, XP Home,
> etc) need a purchased TS CAL.
> So it's probably your Intermec clients that need
a purchased TS
> CAL. You can verify that when you check which
clients have received
> an temporary W2K Per Device CAL.
>
_________________________________________________________
> 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?QW5kZXJz?= wrote on
> 20 sep 2007 in
microsoft.public.windows.terminal_services:
>
> > OK - maybe it is a stupid question, but I
believe that my Win XP
> > and Intermec terminals had a license for
free at Terminal
> > Service 2000, it is the main reason why I
choose the TS2000. I
> > am aware of that I have to pay for all
licenses to a Terminal
> > Server 2003, but also TS 2000 ??
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> OK, that explains your issue.
> >> You simply have to purchase and install
TS CALs for your
> >> down-level clients.
> >> Seems you need 6 of them, one for each
client who has been
> >> issued a "Temporary license Win
2000 term service Client
> >> Access"
> >>
> >>
_________________________________________________________
> >> 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?QW5kZXJz?= wrote
> >> on 20 sep 2007 in
microsoft.public.windows.terminal_services:
> >>
> >> > Hi Vera
> >> >
> >> > 1. The Licensing Server is running
on the DC
> >> > 2. Yes, it is running.
> >> > 3. I did found some errors in the
event log :
> >> >
> >> > Event Type: Warning
> >> > Event Source: TermServLicensing
> >> > Event Category: None
> >> > Event ID: 22
> >> > Date: 19-09-2007
> >> > Time: 09:25:57
> >> > User: N/A
> >> > Computer: BIWEB
> >> > Description:
> >> > The Terminal Services Licensing
server BIWEB has no license
> >> > pack registered for product
'Windows 2000 Terminal Services
> >> > Client Access License'. Use
Terminal Services Licensing
> >> > administrative tool to register the
licenses pack.
> >> >
> >> >
> >> > Event Type: Warning
> >> > Event Source: TermService
> >> > Event Category: None
> >> > Event ID: 1013
> >> > Date: 15-02-2007
> >> > Time: 11:39:28
> >> > User: N/A
> >> > Computer: BIWEB
> >> > Description:
> >> > The terminal server has exceeded
the maximum number of
> >> > allowed connections.
> >> >
> >> > 4. About "loosing" the
Terminal Servers, I am convinced that
> >> > the "Terminal Service Licensing
Manager" once could see the
> >> > Terminal Servers, but I am not
sure.
> >> >
> >> > 5. Yes - At the Terminal Service
Licensing Manager I can see
> >> > the licenses tha are issued.
> >> >
> >> > Existing Win 2000 license - Buil-in
- Unlimited - 45 Issued
> >> > Temp license for existing win 2000
license - Temp - 2 Issued
> >> > Temp license Win 2000 term service
Client Access - Temp - 6
> >> > Issued
> >> >
> >> > 6. I Implementet the q239107 only
at one of my terminal
> >> > servers, just to see if it worked,
but it did´nt.
> >> >
> >> > Do I have to try to deactivate /
reactivate the Terminal
> >> > Licensing Server ??
> >> >
> >> > Best Regards
> >> >
> >> > Anders
> >> >
> >> >
> >> > "Vera Noest [MVP]" wrote:
> >> >
> >> >> comments inline
> >> >>
> >> >> =?Utf-8?B?QW5kZXJz?=
> >> >> wrote on 19 sep 2007 in
> >> >>
microsoft.public.windows.terminal_services:
> >> >>
> >> >> > I have a Win2000 TS
licensing server and 2 Win2000 TS
> >> >> > running in AppMode.
> >> >>
> >> >> Is the TS Licensing Server
running on the Domain Controller?
> >> >> Have you checked that it is
actually running?
> >> >> Are there any errors or
warnings in the EventLog on the TS
> >> >> Licensing Server?
> >> >>
> >> >> > I have about 40 users, Win
XP and Intermec devices
> >> >> > using the TS. When I try
to connect with some new clients
> >> >> > I get a 1004 error. All
the "old" clients are working
> >> >> > fine, but I cannot connect
with any of the new clients.
> >> >> >
> >> >> > The licensing server have
"lost" all my TS, I can just see
> >> >> > the licensing server it
self.
> >> >>
> >> >> The licensing server has no
knowledge about your Terminal
> >> >> Servers, so it can't have lost
them either.
> >> >> It's the other way around, your
Terminal Servers must be
> >> >> able to find your TS Licensing
Server.
> >> >>
> >> >> > When I am trying to
connect to one of
> >> >> > my TS from the licensing
server, I got this message :
> >> >> > Windows cannot connect to
a licensing server.
> >> >>
> >> >> When you open the TS Licensing
Manager on the TS Licensing
> >> >> Server, do you see the licenses
that are issued? If not, do
> >> >> you see them when you connect
to the TS Licensing Server
> >> >> (*not* a TS)?
> >> >>
> >> >> > I have tried to follow the
Guidelines from Q239107, but it
> >> >> > still dos´nt work.
> >> >>
> >> >> On which server did you try to
implement KB 239107? I
> >> >> suspect that you made the
registry change on the TS
> >> >> Licensing Server. If so, you
must do it on each terminal
> >> >> Server.
> >> >>
> >> >> > It seems that I have got a
system where it is´nt
> >> >> > possible to connect any
new clients !!
> >> >> >
> >> >> > Anybody - help !!!
> >> >> >
> >> >> > Regards Anders
> >> >>
_________________________________________________________
> >> >> Vera Noest
> >> >> MCSE, CCEA, Microsoft MVP -
Terminal Server
> >> >> TS troubleshooting:
http://ts.veranoest.net
> >> >> ___ please respond in
newsgroup, NOT by private email ___
>
Top
From: Vera Noest [MVP]
<vera.noest@remove-this.hem.utfors.se>
To:
none
Subject:
Re: Event ID : 1004 - The terminal server cannot optain a
client l
Date:
10/02/2007 15:41:25
Reactivating your LS should not have an impact on your
already
issued licenses.
Details are here:
306578 - HOW TO: Deactivate or Reactivate a License
Server Using
Terminal Services Licensing
http://support.microsoft.com/?kbid=306578
_________________________________________________________
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?QW5kZXJz?= wrote on
02 okt 2007 in
microsoft.public.windows.terminal_services:
> Hi again
>
> It is`nt easy !!
>
> The Activation Status of the TS license server is
ACTIVATED.
> The Temp lic for W2K TS CAL are identified, and
are not the
> Intermec Clients. When I`m trying to add more
Licenses, I got
> this info :
>
> The license server`s activation has expired. To
use this license
> server, you must reactivate it. Do you want to
reactivate the
> server now?
>
> I have`nt reactivated the server yet, because I`m
not sure what
> is going to happen with my existing and OK
clients. As I have
> mentiont, I have newer installed any CAL at my
licensing server.
> I have been told that my Intermec terminals have
a CAL for free,
> and it seems to be correct, it have worked for
about 2½ year,
> until now.
>
> It seems that I have to reactivate the license
server, but what
> will happen with my existing Clients ??
>
> Best Regards
>
> Anders
>
> "Vera Noest [MVP]" wrote:
>
>> Only W2K Pro, XP Pro and Vista Business
clients receive a free
>> TS CAL from the built-in pool of licenses on
the Licensing
>> Server (the licenses that are called
"Existing Win 2000 license
>> - Built-in - Unlimited").
>>
>> All downlevel clients (thin clients, linux,
Macintosh, XP Home,
>> etc) need a purchased TS CAL.
>> So it's probably your Intermec clients that
need a purchased TS
>> CAL. You can verify that when you check which
clients have
>> received an temporary W2K Per Device CAL.
>>
_________________________________________________________
>> 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?QW5kZXJz?= wrote
>> on 20 sep 2007 in microsoft.public.windows.terminal_services:
>>
>> > OK - maybe it is a stupid question, but
I believe that my Win
>> > XP and Intermec terminals had a license
for free at Terminal
>> > Service 2000, it is the main reason why
I choose the TS2000.
>> > I am aware of that I have to pay for all
licenses to a
>> > Terminal Server 2003, but also TS 2000
??
>> >
>> > "Vera Noest [MVP]" wrote:
>> >
>> >> OK, that explains your issue.
>> >> You simply have to purchase and
install TS CALs for your
>> >> down-level clients.
>> >> Seems you need 6 of them, one for
each client who has been
>> >> issued a "Temporary license Win
2000 term service Client
>> >> Access"
>> >>
>> >>
_________________________________________________________
>> >> 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?QW5kZXJz?=
>> >> wrote on 20 sep 2007 in
>> >> microsoft.public.windows.terminal_services:
>> >>
>> >> > Hi Vera
>> >> >
>> >> > 1. The Licensing Server is
running on the DC
>> >> > 2. Yes, it is running.
>> >> > 3. I did found some errors in
the event log :
>> >> >
>> >> > Event Type: Warning
>> >> > Event Source: TermServLicensing
>> >> > Event Category: None
>> >> > Event ID: 22
>> >> > Date: 19-09-2007
>> >> > Time: 09:25:57
>> >> > User: N/A
>> >> > Computer: BIWEB
>> >> > Description:
>> >> > The Terminal Services Licensing
server BIWEB has no
>> >> > license pack registered for
product 'Windows 2000 Terminal
>> >> > Services Client Access
License'. Use Terminal Services
>> >> > Licensing administrative tool
to register the licenses
>> >> > pack.
>> >> >
>> >> >
>> >> > Event Type: Warning
>> >> > Event Source: TermService
>> >> > Event Category: None
>> >> > Event ID: 1013
>> >> > Date: 15-02-2007
>> >> > Time: 11:39:28
>> >> > User: N/A
>> >> > Computer: BIWEB
>> >> > Description:
>> >> > The terminal server has
exceeded the maximum number of
>> >> > allowed connections.
>> >> >
>> >> > 4. About "loosing"
the Terminal Servers, I am convinced
>> >> > that the "Terminal Service
Licensing Manager" once could
>> >> > see the Terminal Servers, but I
am not sure.
>> >> >
>> >> > 5. Yes - At the Terminal
Service Licensing Manager I can
>> >> > see the licenses tha are
issued.
>> >> >
>> >> > Existing Win 2000 license -
Buil-in - Unlimited - 45
>> >> > Issued Temp license for
existing win 2000 license - Temp -
>> >> > 2 Issued Temp license Win 2000
term service Client Access
>> >> > - Temp - 6 Issued
>> >> >
>> >> > 6. I Implementet the q239107
only at one of my terminal
>> >> > servers, just to see if it
worked, but it did´nt.
>> >> >
>> >> > Do I have to try to deactivate
/ reactivate the Terminal
>> >> > Licensing Server ??
>> >> >
>> >> > Best Regards
>> >> >
>> >> > Anders
>> >> >
>> >> >
>> >> > "Vera Noest [MVP]"
wrote:
>> >> >
>> >> >> comments inline
>> >> >>
>> >> >> =?Utf-8?B?QW5kZXJz?=
>> >> >> wrote on 19 sep 2007 in
>> >> >>
microsoft.public.windows.terminal_services:
>> >> >>
>> >> >> > I have a Win2000 TS
licensing server and 2 Win2000 TS
>> >> >> > running in AppMode.
>> >> >>
>> >> >> Is the TS Licensing Server
running on the Domain
>> >> >> Controller? Have you
checked that it is actually running?
>> >> >> Are there any errors or
warnings in the EventLog on the
>> >> >> TS Licensing Server?
>> >> >>
>> >> >> > I have about 40 users,
Win XP and Intermec devices
>> >> >> > using the TS. When I
try to connect with some new
>> >> >> > clients I get a 1004
error. All the "old" clients are
>> >> >> > working fine, but I
cannot connect with any of the new
>> >> >> > clients.
>> >> >> >
>> >> >> > The licensing server
have "lost" all my TS, I can just
>> >> >> > see the licensing
server it self.
>> >> >>
>> >> >> The licensing server has no
knowledge about your Terminal
>> >> >> Servers, so it can't have
lost them either.
>> >> >> It's the other way around,
your Terminal Servers must be
>> >> >> able to find your TS
Licensing Server.
>> >> >>
>> >> >> > When I am trying to
connect to one of
>> >> >> > my TS from the
licensing server, I got this message :
>> >> >> > Windows cannot connect
to a licensing server.
>> >> >>
>> >> >> When you open the TS
Licensing Manager on the TS
>> >> >> Licensing Server, do you
see the licenses that are
>> >> >> issued? If not, do you see
them when you connect to the
>> >> >> TS Licensing Server (*not*
a TS)?
>> >> >>
>> >> >> > I have tried to follow
the Guidelines from Q239107, but
>> >> >> > it still
dos´nt work.
>> >> >>
>> >> >> On which server did you try
to implement KB 239107? I
>> >> >> suspect that you made the
registry change on the TS
>> >> >> Licensing Server. If so,
you must do it on each terminal
>> >> >> Server.
>> >> >>
>> >> >> > It seems that I have
got a system where it
>> >> >> >
is´nt possible to connect any new
>> >> >> > clients !!
>> >> >> >
>> >> >> > Anybody - help !!!
>> >> >> >
>> >> >> > Regards Anders
>> >> >>
_________________________________________________________
>> >> >> Vera Noest
>> >> >> MCSE, CCEA, Microsoft MVP -
Terminal Server
>> >> >> TS troubleshooting:
http://ts.veranoest.net
>> >> >> ___ please respond in
newsgroup, NOT by private email ___
Top
From: Jeff Pitsch
<Jeff@Jeffpitschconsulting.com>
To:
none
Subject:
Re: Enable Remote Desktop via group policy
Date:
09/25/2007 12:06:58
Do you mean shadowing? Simply have the shadow options
set to prompt the
user.
Jeff Pitsch
Microsoft MVP - Terminal Server
Citrix Technology Professional
Provision Networks VIP
Forums not enough?
Get support from the experts at your business
http://jeffpitschconsulting.com
Joe Murphy wrote:
> I know that I can enable this throughout our
organization using group
> policy, but what I want to be sure of is that the
end-user has control over
> whether or not to allow the remote desktop
session.
>
> I want to avoid any IT "big brother"
perception. They already think we sit
> around reading their emails. ;)
>
> Thanks,
> JM
>
>
Top
From: Joe Murphy <spam@spamthis.com>
To:
none
Subject:
Re: Enable Remote Desktop via group policy
Date:
09/25/2007 12:40:23
Not shadowing (at least I don't think so). I mean when
a user calls me for
help and I want to remotely control their desktop. I'd
like them to get a
prompt when I try to establish the remote session so
they don't freak out,
like some users do.
Thanks,
JM
"Jeff Pitsch" wrote in message
news:%23Ugm7Z5$HHA.5868@TK2MSFTNGP05.phx.gbl...
> Do you mean shadowing? Simply have the shadow
options set to prompt the
> user.
>
> Jeff Pitsch
> Microsoft MVP - Terminal Server
> Citrix Technology Professional
> Provision Networks VIP
>
> Forums not enough?
> Get support from the experts at your business
> http://jeffpitschconsulting.com
>
> Joe Murphy wrote:
>> I know that I can enable this throughout our
organization using group
>> policy, but what I want to be sure of is that
the end-user has control
>> over whether or not to allow the remote
desktop session.
>>
>> I want to avoid any IT "big
brother" perception. They already think we
>> sit around reading their emails. ;)
>>
>> Thanks,
>> JM
Top
From: Vera Noest [MVP]
<vera.noest@remove-this.hem.utfors.se>
To:
none
Subject:
Re: Enable Remote Desktop via group policy
Date:
09/25/2007 13:27:09
Do you mean Remote Assistance? So that you and the
user see and can
interact with the same screen at the same time? That
can be
configured so that the user must initiate it (invite
you to give
Remote Assistance, and allow you to connect).
Or do you mean that you rdp into the client? Thereby
effectively
logging out and shutting out the users? I wouldn't do
that when
they call you, meaning they are present in front of
their
workstation. Remote Assistance is ideal for this. You
can teach the
user while you fix the problem, and they can see what
you do.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email
___
"Joe Murphy" wrote on 25 sep 2007 in
microsoft.public.windows.terminal_services:
> Not shadowing (at least I don't think so). I mean
when a user
> calls me for help and I want to remotely control
their desktop.
> I'd like them to get a prompt when I try to
establish the remote
> session so they don't freak out, like some users
do.
>
> Thanks,
> JM
>
> "Jeff Pitsch" wrote in message
> news:%23Ugm7Z5$HHA.5868@TK2MSFTNGP05.phx.gbl...
>> Do you mean shadowing? Simply have the shadow
options set to
>> prompt the user.
>>
>> Jeff Pitsch
>> Microsoft MVP - Terminal Server
>> Citrix Technology Professional
>> Provision Networks VIP
>>
>> Forums not enough?
>> Get support from the experts at your business
>> http://jeffpitschconsulting.com
>>
>> Joe Murphy wrote:
>>> I know that I can enable this throughout
our organization
>>> using group policy, but what I want to be
sure of is that the
>>> end-user has control over whether or not
to allow the remote
>>> desktop session.
>>>
>>> I want to avoid any IT "big
brother" perception. They already
>>> think we sit around reading their emails.
;)
>>>
>>> Thanks,
>>> JM
Top
From: TP
<tperson.knowspamn@mailandnews.com>
To:
none
Subject:
Re: Enable Remote Desktop via group policy
Date:
09/25/2007 14:16:09
http://ts.veranoest.net/ts_faq_administration.htm#XPSP2remote
:-)
Vera Noest [MVP] wrote:
> Do you mean Remote Assistance? So that you and
the user see and can
> interact with the same screen at the same time?
That can be
> configured so that the user must initiate it
(invite you to give
> Remote Assistance, and allow you to connect).
>
> Or do you mean that you rdp into the client?
Thereby effectively
> logging out and shutting out the users? I
wouldn't do that when
> they call you, meaning they are present in front
of their
> workstation. Remote Assistance is ideal for this.
You can teach the
> user while you fix the problem, and they can see
what you do.
>
>
_________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private
email ___
Top
From: Vera Noest [MVP] <vera.noest@remove-this.hem.utfors.se>
To:
none
Subject:
Re: Enable Remote Desktop via group policy
Date:
09/25/2007 14:35:54
LOL!
But I actually thought that the OP was possibly
referring to Remote
Assistance, i.e. interacting with the users *XP*
desktop session,
not just the users *TS* desktop session.
Our helpdesk uses Remote Assistance all the time,
since we run a
mixture of local applications and TS applications.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email
___
"TP" wrote on 25 sep 2007 in
microsoft.public.windows.terminal_services:
>
http://ts.veranoest.net/ts_faq_administration.htm#XPSP2remote
>
>:-)
>
> Vera Noest [MVP] wrote:
>> Do you mean Remote Assistance? So that you
and the user see and
>> can interact with the same screen at the same
time? That can be
>> configured so that the user must initiate it
(invite you to
>> give Remote Assistance, and allow you to
connect).
>>
>> Or do you mean that you rdp into the client?
Thereby
>> effectively logging out and shutting out the
users? I wouldn't
>> do that when they call you, meaning they are
present in front
>> of their workstation. Remote Assistance is
ideal for this. You
>> can teach the user while you fix the problem,
and they can see
>> what you do.
>>
>>
_________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by
private email ___
Top
From: TP
<tperson.knowspamn@mailandnews.com>
To:
none
Subject:
Re: Enable Remote Desktop via group policy
Date:
09/25/2007 14:46:08
That's what is so nice about it--you can have your XP
machines
listed in your tsadmin favorites just like your
servers. When you
need to offer assistance you can right-click on the
user's name
and choose Remote Control. Another nice thing is you
can see
the list of processes the user has running.
If the user clicks yes you are connected to their XP
desktop just
like PC Anywhere, VNC, etc.
-TP
Vera Noest [MVP] wrote:
> LOL!
> But I actually thought that the OP was possibly
referring to Remote
> Assistance, i.e. interacting with the users *XP*
desktop session,
> not just the users *TS* desktop session.
> Our helpdesk uses Remote Assistance all the time,
since we run a
> mixture of local applications and TS
applications.
>
Top
From: Vera Noest [MVP]
<Vera.Noest@remove-this.hem.utfors.se>
To:
none
Subject:
Re: Enable Remote Desktop via group policy
Date:
09/25/2007 16:13:45
You're kidding :-) I've never done that, will try it
out!
Our helpdesk always uses Help and Support from the
Start menu to
offer Remote Assistance, but this sounds easier!
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*
"TP" wrote on 25 sep 2007:
> That's what is so nice about it--you can have
your XP machines
> listed in your tsadmin favorites just like your
servers. When
> you need to offer assistance you can right-click
on the user's
> name and choose Remote Control. Another nice
thing is you can
> see the list of processes the user has running.
>
> If the user clicks yes you are connected to their
XP desktop
> just like PC Anywhere, VNC, etc.
>
> -TP
>
> Vera Noest [MVP] wrote:
>> LOL!
>> But I actually thought that the OP was
possibly referring to
>> Remote Assistance, i.e. interacting with the
users *XP* desktop
>> session, not just the users *TS* desktop
session.
>> Our helpdesk uses Remote Assistance all the
time, since we run
>> a mixture of local applications and TS
applications.
Top
From: TP
<tperson.knowspamn@mailandnews.com>
To:
none
Subject:
Re: Enable Remote Desktop via group policy
Date:
09/25/2007 14:14:01
Yes, you are talking about shadowing aka Remote
Control.
Jeff's comment is correct--you can set the prompt
option. I
have never used it for XP connections so I am not
certain it
will work for them. By default it prompts the user so
if you
have not set it already there is no need.
Note that with XP Pro SP2 you need to add the
following
registry entry to each machine to do what you want:
HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server
AllowRemoteRPC REG_DWORD 0x00000001
-TP
Joe Murphy wrote:
> Not shadowing (at least I don't think so). I mean
when a user calls
> me for help and I want to remotely control their
desktop. I'd like
> them to get a prompt when I try to establish the
remote session so
> they don't freak out, like some users do.
>
> Thanks,
> JM
Top
From: Munindra Das [MSFT]
<munind@online.microsoft.com>
To:
none
Subject:
Re: double mouse pointer on rdp session
Date:
09/28/2007 16:07:38
What is your OS and Service Pack level? Which TS
client (5.0, 5.1 or 6.0)
are you using? Do you have any application installed
that can effect mouse
pointer? For example, KVM over IP switches, etc. Are
you using Virtual
Server/Client? Are you running the TS session in full
screen or smaller
mode?
I have remember seeing this issue being reported
before. The only update for
mouse pointer in TS that I can think of is
http://support.microsoft.com/kb/830209 for the 5.1 or
later client. Give it
a try.
--
This posting is provided "AS IS" with no
warranties, and confers no rights.
"David RENAUD" wrote in message
news:OXxVOOOAIHA.4984@TK2MSFTNGP06.phx.gbl...
> Hello everybody,
>
> I recently setup a windows 2003 R2 server with
terminal services enabled.
> When i connect to the server with RDP, 2 mouse
pointers are displayed :
> the first seems to follow the real mouse move and
the second reflect the
> remote pointer position.
> The local console works perfectly.
>
> Does anyone has a idea to suppress one of the
pointers ?
>
> Thanks
Top
From: David RENAUD
<d.renaud@irium-france.com>
To:
none
Subject:
Re: double mouse pointer on rdp session
Date:
10/02/2007 11:05:50
Munindra Das [MSFT] a écrit :
> What is your OS and Service Pack level? Which TS
client (5.0, 5.1 or
> 6.0) are you using? Do you have any application
installed that can
> effect mouse pointer? For example, KVM over IP
switches, etc. Are you
> using Virtual Server/Client? Are you running the
TS session in full
> screen or smaller mode?
>
> I have remember seeing this issue being reported
before. The only update
> for mouse pointer in TS that I can think of is
> http://support.microsoft.com/kb/830209 for the
5.1 or later client. Give
> it a try.
>
The Server OS is W2K3 with service pack 2, TS clients
are 5.0 and later,
I don't have any software that could affcet the mouse
pointer I think.
I don't use either Virtual Server or Client and the
symptoms are
equivalent if I run the client in full screen or not.
I already tried the update you recommended but this
doesn't work well
and did not cover my problem.
I searched during the past days in the registry about
a value that can
affect the pointer display, but found nothing.
Thank you for your answer.
Top
From: Josh Rosenberg [MSFT] <joshrose@online.microsoft.com>
To:
none
Subject:
Re: Disable RDP Encryption
Date:
09/25/2007 18:02:36
No. For security purposes, encryption cannot be
disabled.
--
Josh Rosenberg [MSFT]
SDE - Terminal Services
"Julio" wrote in message
news:E86B5477-C628-4F05-88EB-A21128909251@microsoft.com...
> Is there a way to completely disable rdp
encryption, both going from the
> client to the server and the server back to the
client?
Top
From: Sooner Al [MVP]
<SoonerAl@somewhere.net.invalid>
To:
none
Subject:
Re: Disable RDP Encryption
Date:
09/26/2007 04:51:38
"Julio" wrote in message
news:E86B5477-C628-4F05-88EB-A21128909251@microsoft.com...
> Is there a way to completely disable rdp
encryption, both going from the
> client to the server and the server back to the
client?
I'm curious as to why you would want to?
--
Al Jarvi (MS-MVP Windows Networking)
Please post *ALL* questions and replies to the news
group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no
warranties, and confers no
rights...
How to ask a question
http://support.microsoft.com/KB/555375
Top
From: Julio
<Julio@discussions.microsoft.com>
To:
none
Subject:
Re: Disable RDP Encryption
Date:
09/26/2007 09:06:03
The reason I want to disable RDP encryption is because
we are doing some RDP
Acceleration testing via a riverbed appliance over a
WAN.
Thanks for the info. guys!
"Sooner Al [MVP]" wrote:
> "Julio" wrote in message
>
news:E86B5477-C628-4F05-88EB-A21128909251@microsoft.com...
> > Is there a way to completely disable rdp
encryption, both going from the
> > client to the server and the server back to
the client?
>
> I'm curious as to why you would want to?
>
> --
>
> Al Jarvi (MS-MVP Windows Networking)
>
> Please post *ALL* questions and replies to the
news group for the
> mutual benefit of all of us...
> The MS-MVP Program -
http://mvp.support.microsoft.com
> This posting is provided "AS IS" with
no warranties, and confers no
> rights...
> How to ask a question
> http://support.microsoft.com/KB/555375
>
Top
From: TP
<tperson.knowspamn@mailandnews.com>
To:
none
Subject:
Re: Disable connection bar not working
Date:
09/21/2007 10:08:31
Hi Guy,
If you set PinConnectionBar to 0 in each user's
registry *and*
use disableconnectionbar:i:0 the bar will show
initially but will
fade away after the first click. It will not return
even if the user
bumps the mouse to the top of the screen.
It is not a perfect solution. If the user clicks the
pushpin it will
stick for the entire session as well as change the
registry back
to PinConnectionBar = 1.
-TP
Guy Yardeni wrote:
> Hi,
> I'm using Wyse V90 thin clients running XPe and
RDP client version
> 5.2. Using either the GUI checkbox or the text
line in the RDP file
> (disableconnectionbar:i:0) fails to disable the
bar for a full screen
> connection.
>
> Has anyone run into this issue before?
>
> Thanks,
> Guy
Top
From: Munindra Das [MSFT] <munind@online.microsoft.com>
To:
none
Subject:
Re: Default mail program
Date:
09/24/2007 12:46:14
You will have a better chance of getting a reply if
you post this question
to the Outlook newsgroup (microsoft.public.outlook).
Thanks!
--
This posting is provided "AS IS" with no
warranties, and confers no rights.
"Bitnisse" wrote in message
news:A1929BD3-AC0A-43AC-A15C-68D06BA4E3E0@microsoft.com...
> Hi, I have this strange problem on my Terminal
Server (2003 x64 SP2). When
> right click an item selecting send to - Mail
recipient it starts the
> default
> mail program. Office 2007 is installed on the
server and selected as
> default
> mail program in IE, so I expect Outlook to start,
but it doesn't. Instead
> the
> configuring OE wizard starts. This issue
irritates my users and me. I have
> searched the Internet for several hours with no
luck. I have seen plenty
> websites describing simular issues but nothing
with a helpful solution. So
> what do I do????
Top
From: Munindra Das [MSFT]
<munind@online.microsoft.com>
To:
none
Subject:
Re: control ids for visio 2007
Date:
09/22/2007 01:59:15
You will have a better chance of getting a reply if
you post this question
to the Visio newsgroup (microsoft.public.visio).
Thanks!
--
This posting is provided "AS IS" with no
warranties, and confers no rights.
"Robbie van der Walle" wrote
in message
news:7BE34008-1AB5-44DB-9A33-3177CBDBB448@microsoft.com...
> Hello,
>
> I am trying to find the right control ids for
visio 2007. I find already a
> few control ids but not all of them and i don't
know anything about visual
> basic.
> Important for example is trust center.
> I need this control ids to lock down visio 2007
which is running on a
> terminal server.
>
> Any ideas ?
>
> Robbie
Top
From: Munindra Das [MSFT]
<munind@online.microsoft.com>
To:
none
Subject:
Re: Connot connect to one server using RDP
Date:
09/28/2007 15:58:53
This can be due to various reasons. First check would
be to see TS service
and listener is up and running fine on the server.
Though you might have
already done it, following are things to check:
- please run "qwinsta.exe" and see listener
is running.
- run "netstat -a" and see if TCP port 3389
is being listened at.
Next would be to see if connection request is getting
to the server or not.
You can take some "netmon" traces on the
server and see if you find any
packets reaching port 3389. If connections are not
getting to port 3389, one
of the common issue is DNS name resolution. Try using
the ipaddress instead
and see if you can connect.
If nothing works, look for error entries in the event
log.
--
This posting is provided "AS IS" with no
warranties, and confers no rights.
"PSV" wrote in message
news:E9C78418-7F1F-484F-91E7-3E4D97B28064@microsoft.com...
> We have 5 windows 2003 servers in a separate
domain. 1 DC, 2 Clustered
> Servers and 2 Citrix servers. We have a domain
account used for managing
> the
> clusters. This a/c has local admin rights on both
cluster nodes. We
> noticed
> that someone had accidentally put this a/c in
domain admin group. After
> removing this a/c from doamin admins group we are
unable to connect to one
> server (node 2 of cluster). We don't even get
logon screen when we RDP in
> the
> server.
> Pls note that, we have enforced security using
GPOs. Using the GPO tool, I
> made sure that, all servers have lastest GPOs.
> I have tried the following,
> 1.rebooting the servers.
> 2. Re-registered with DNS
> 3. I compared Node 1 of cluster with Node 2 in
terms of a/c setup,
> policies,
> RDP setup, services etc. Everything looks
identical.
> 4. Checked to see whether firewall is turn on.
It's off.
> 5. RDP protocol configuration is identical.
> 6.
> I was wondering whether anyone could point me in
the right direction.
>
> The error received is,
>
> The client couldn't establish connection to the
remote computer.
> The mostlylikes reasons are,
> 1. Remote connections might not be enabled at the
remote computer
> 2. The maximum number of connections was exceeded
at the remote computer
> 3. A network error occurred while establishing
the connection.
>
> Thanks a bunch.
> PSV
Top
From: Munindra Das [MSFT]
<munind@online.microsoft.com>
To:
none
Subject:
Re: connections from outlook to exchange via terminal server
get endless password prompt
Date:
09/26/2007 14:35:03
Do you have any related entries in the event log?
--
This posting is provided "AS IS" with no
warranties, and confers no rights.
wrote in message
news:1190674965.884280.280510@r29g2000hsg.googlegroups.com...
>I posted this in an exchange group and one of the
MVP's suggested I
> post it here as well.
>
> I've recently added an exchange server to a small
domain and have ran
> into some problem with connections from a
terminal server in the
> organization. All lan users can connect fine and
are having no issues
> with exchange.
> Connections from the terminal server all fail
with an endless
> password
> loop. When I go into control panel / mail and try
to add the account
> it will sometimes validate the username, but most
of the time it just
> prompts endlessly for the un/pw. On the rare
occasions that it does
> validate the username, once I open outlook it
just loops for the
> password.
>
> Both the term server and the exchange server are
2003 server R2,
> exchange is on the latest SP. Outlook version is
2007. I have done a
> repair on the outlook installation with no
success afterwards. I've
> also tried new outlook profiles and a new account
with the smae
> results. The term server users can all connect
fine from workstations
> via outlook or OWA.
>
> I've ran netdiag and dcdiag to verify no issues
there and all tests
> were passed. I've done some basic rpcping's from
the terminal server
> to the exchange server and those appear to be
reponding, but I'm not
> familiar enough with it to go much more in depth
than that. There is
> no firewall or router between the TS and Exchange
servers.
>
>
> Can anyone offer some assistance here?
>
Top
From: jcasteel@gmail.com
To:
none
Subject:
Re: connections from outlook to exchange via terminal server
get endless password prompt
Date:
09/26/2007 20:12:11
No, it doesn't register anything in the event logs on
either side.
On Sep 26, 3:35 pm, "Munindra Das [MSFT]"
wrote:
> Do you have any related entries in the event log?
>
> --
> This posting is provided "AS IS" with
no warranties, and confers no rights. wrote in message
>
>
news:1190674965.884280.280510@r29g2000hsg.googlegroups.com...
>
>
>
> >I posted this in an exchange group and one of
the MVP's suggested I
> > post it here as well.
>
> > I've recently added an exchange server to a
small domain and have ran
> > into some problem with connections from a
terminal server in the
> > organization. All lan users can connect fine
and are having no issues
> > with exchange.
> > Connections from the terminal server all
fail with an endless
> > password
> > loop. When I go into control panel / mail
and try to add the account
> > it will sometimes validate the username, but
most of the time it just
> > prompts endlessly for the un/pw. On the rare
occasions that it does
> > validate the username, once I open outlook
it just loops for the
> > password.
>
> > Both the term server and the exchange server
are 2003 server R2,
> > exchange is on the latest SP. Outlook
version is 2007. I have done a
> > repair on the outlook installation with no
success afterwards. I've
> > also tried new outlook profiles and a new
account with the smae
> > results. The term server users can all
connect fine from workstations
> > via outlook or OWA.
>
> > I've ran netdiag and dcdiag to verify no
issues there and all tests
> > were passed. I've done some basic rpcping's
from the terminal server
> > to the exchange server and those appear to
be reponding, but I'm not
> > familiar enough with it to go much more in
depth than that. There is
> > no firewall or router between the TS and
Exchange servers.
>
> > Can anyone offer some assistance here?- Hide
quoted text -
>
> - Show quoted text -
Top
From: Vera Noest [MVP]
<vera.noest@remove-this.hem.utfors.se>
To:
none
Subject:
Re: Client disconnect problems.
Date:
09/23/2007 06:48:00
This might be caused by Vista's auto-tuning feature.
Check this for
more info:
934430 - Network connectivity may fail when you try to
use Windows
Vista behind a firewall device
http://support.microsoft.com/?kbid=934430
Remote Desktop Freezes When Connecting Through Windows
Vista
http://i.nconspicuo.us/2007/04/10/remote-desktop-freezes-when-
connecting-through-windows-vista/
_________________________________________________________
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?Q29ucmFkIEdvdHptYW5u?=
wrote on 22 sep 2007 in
microsoft.public.windows.terminal_services:
> I am using Remote Desktop client on a vista PC. I
can only stay
> connected to any TS Servers for about 10sec >
5 minutes at best
> before the client stops responding and a
disconnect message. I
> then connect again an contine once again. I have
tried to
> connect to 3 different TS Servers with the same
response. If I
> use my XP PC using the same network connection
everything works
> properly with no disconnects. Is there a known
problem with the
> vista TS Client?
Top
From: Conrad Gotzmann
<ConradGotzmann@discussions.microsoft.com>
To:
none
Subject:
Re: Client disconnect problems.
Date:
09/23/2007 07:56:02
Thanks I will have a look. The second link is a dead
link goes to a 404 page
not found error.
"Vera Noest [MVP]" wrote:
> This might be caused by Vista's auto-tuning
feature. Check this for
> more info:
>
> 934430 - Network connectivity may fail when you
try to use Windows
> Vista behind a firewall device
> http://support.microsoft.com/?kbid=934430
>
> Remote Desktop Freezes When Connecting Through
Windows Vista
> http://i.nconspicuo.us/2007/04/10/remote-desktop-freezes-when-
> connecting-through-windows-vista/
>
>
_________________________________________________________
> 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?Q29ucmFkIEdvdHptYW5u?=
> wrote on 22 sep 2007 in
> microsoft.public.windows.terminal_services:
>
> > I am using Remote Desktop client on a vista
PC. I can only stay
> > connected to any TS Servers for about 10sec
> 5 minutes at best
> > before the client stops responding and a
disconnect message. I
> > then connect again an contine once again. I
have tried to
> > connect to 3 different TS Servers with the
same response. If I
> > use my XP PC using the same network
connection everything works
> > properly with no disconnects. Is there a
known problem with the
> > vista TS Client?
>
Top
From: Vera Noest [MVP]
<vera.noest@remove-this.hem.utfors.se>
To:
none
Subject:
Re: Client disconnect problems.
Date:
09/23/2007 09:02:46
The link works perfectly for me.
Note that the URL has wrapped over 2 lines, so you'll
have to do
some cutting and pasting in your web browser.
_________________________________________________________
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?Q29ucmFkIEdvdHptYW5u?=
wrote on 23 sep 2007 in
microsoft.public.windows.terminal_services:
> Thanks I will have a look. The second link is a
dead link goes
> to a 404 page not found error.
>
> "Vera Noest [MVP]" wrote:
>
>> This might be caused by Vista's auto-tuning
feature. Check this
>> for more info:
>>
>> 934430 - Network connectivity may fail when
you try to use
>> Windows Vista behind a firewall device
>> http://support.microsoft.com/?kbid=934430
>>
>> Remote Desktop Freezes When Connecting Through
Windows Vista
>>
http://i.nconspicuo.us/2007/04/10/remote-desktop-freezes-when-
>> connecting-through-windows-vista/
>>
>>
_________________________________________________________
>> 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?Q29ucmFkIEdvdHptYW5u?=
>> wrote on 22 sep 2007
>> in
microsoft.public.windows.terminal_services:
>>
>> > I am using Remote Desktop client on a
vista PC. I can only
>> > stay connected to any TS Servers for
about 10sec > 5 minutes
>> > at best before the client stops
responding and a disconnect
>> > message. I then connect again an contine
once again. I have
>> > tried to connect to 3 different TS
Servers with the same
>> > response. If I use my XP PC using the
same network connection
>> > everything works properly with no
disconnects. Is there a
>> > known problem with the vista TS Client?
Top
From: Conrad Gotzmann
<ConradGotzmann@discussions.microsoft.com>
To:
none
Subject:
Re: Client disconnect problems.
Date:
09/23/2007 15:08:01
Thanks no more client disconnects.
"Vera Noest [MVP]" wrote:
> The link works perfectly for me.
> Note that the URL has wrapped over 2 lines, so
you'll have to do
> some cutting and pasting in your web browser.
>
>
_________________________________________________________
> 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?Q29ucmFkIEdvdHptYW5u?=
> wrote on 23 sep 2007 in
> microsoft.public.windows.terminal_services:
>
> > Thanks I will have a look. The second link
is a dead link goes
> > to a 404 page not found error.
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> This might be caused by Vista's
auto-tuning feature. Check this
> >> for more info:
> >>
> >> 934430 - Network connectivity may fail
when you try to use
> >> Windows Vista behind a firewall device
> >>
http://support.microsoft.com/?kbid=934430
> >>
> >> Remote Desktop Freezes When Connecting
Through Windows Vista
> >> http://i.nconspicuo.us/2007/04/10/remote-desktop-freezes-when-
> >> connecting-through-windows-vista/
> >>
> >>
_________________________________________________________
> >> 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?Q29ucmFkIEdvdHptYW5u?=
> >> wrote on 22 sep 2007
> >> in
microsoft.public.windows.terminal_services:
> >>
> >> > I am using Remote Desktop client on
a vista PC. I can only
> >> > stay connected to any TS Servers
for about 10sec > 5 minutes
> >> > at best before the client stops
responding and a disconnect
> >> > message. I then connect again an
contine once again. I have
> >> > tried to connect to 3 different TS
Servers with the same
> >> > response. If I use my XP PC using
the same network connection
> >> > everything works properly with no
disconnects. Is there a
> >> > known problem with the vista TS
Client?
>
Top
From: Hank Arnold (MVP)
<rasilon@aol.com>
To:
none
Subject:
Re: Client disconnect problems.
Date:
09/24/2007 05:17:31
What was the solution?
--
Regards,
Hank Arnold
Microsoft MVP
Windows Server - Directory Services
Conrad Gotzmann wrote:
> Thanks no more client disconnects.
>
> "Vera Noest [MVP]" wrote:
>
>> The link works perfectly for me.
>> Note that the URL has wrapped over 2 lines,
so you'll have to do
>> some cutting and pasting in your web browser.
>>
>> _________________________________________________________
>> 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?Q29ucmFkIEdvdHptYW5u?=
>> wrote on 23 sep 2007 in
>> microsoft.public.windows.terminal_services:
>>
>>> Thanks I will have a look. The second
link is a dead link goes
>>> to a 404 page not found error.
>>>
>>> "Vera Noest [MVP]" wrote:
>>>
>>>> This might be caused by Vista's
auto-tuning feature. Check this
>>>> for more info:
>>>>
>>>> 934430 - Network connectivity may
fail when you try to use
>>>> Windows Vista behind a firewall
device
>>>>
http://support.microsoft.com/?kbid=934430
>>>>
>>>> Remote Desktop Freezes When
Connecting Through Windows Vista
>>>>
http://i.nconspicuo.us/2007/04/10/remote-desktop-freezes-when-
>>>> connecting-through-windows-vista/
>>>>
>>>>
_________________________________________________________
>>>> 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?Q29ucmFkIEdvdHptYW5u?=
>>>> wrote on 22 sep 2007
>>>> in
microsoft.public.windows.terminal_services:
>>>>
>>>>> I am using Remote Desktop client
on a vista PC. I can only
>>>>> stay connected to any TS Servers
for about 10sec > 5 minutes
>>>>> at best before the client stops
responding and a disconnect
>>>>> message. I then connect again an
contine once again. I have
>>>>> tried to connect to 3 different
TS Servers with the same
>>>>> response. If I use my XP PC using
the same network connection
>>>>> everything works properly with no
disconnects. Is there a
>>>>> known problem with the vista TS
Client?
Top
From: Vera Noest [MVP]
<vera.noest@remove-this.hem.utfors.se>
To:
none
Subject:
Re: Client disconnect problems.
Date:
09/24/2007 15:57:29
Great! I'm glad that your problem is solved, and
thanks for your
feedback on the result, Conrad!
_________________________________________________________
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?Q29ucmFkIEdvdHptYW5u?=
wrote on 23 sep 2007 in
microsoft.public.windows.terminal_services:
> Thanks no more client disconnects.
>
> "Vera Noest [MVP]" wrote:
>
>> The link works perfectly for me.
>> Note that the URL has wrapped over 2 lines,
so you'll have to do
>> some cutting and pasting in your web browser.
>>
>>
_________________________________________________________
>> 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?Q29ucmFkIEdvdHptYW5u?=
>> wrote on 23 sep 2007
in
>> microsoft.public.windows.terminal_services:
>>
>> > Thanks I will have a look. The second
link is a dead link goes
>> > to a 404 page not found error.
>> >
>> > "Vera Noest [MVP]" wrote:
>> >
>> >> This might be caused by Vista's
auto-tuning feature. Check
this
>> >> for more info:
>> >>
>> >> 934430 - Network connectivity may fail
when you try to use
>> >> Windows Vista behind a firewall
device
>> >>
http://support.microsoft.com/?kbid=934430
>> >>
>> >> Remote Desktop Freezes When
Connecting Through Windows Vista
>> >>
http://i.nconspicuo.us/2007/04/10/remote-desktop-freezes-
when-
>> >> connecting-through-windows-vista/
>> >>
>> >>
_________________________________________________________
>> >> 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?Q29ucmFkIEdvdHptYW5u?=
>> >> wrote on 22 sep
2007
>> >> in
microsoft.public.windows.terminal_services:
>> >>
>> >> > I am using Remote Desktop
client on a vista PC. I can only
>> >> > stay connected to any TS
Servers for about 10sec > 5
minutes
>> >> > at best before the client stops
responding and a disconnect
>> >> > message. I then connect again
an contine once again. I have
>> >> > tried to connect to 3 different
TS Servers with the same
>> >> > response. If I use my XP PC
using the same network
connection
>> >> > everything works properly with
no disconnects. Is there a
>> >> > known problem with the vista TS
Client?
Top
From: Munindra Das [MSFT]
<munind@online.microsoft.com>
To:
none
Subject:
Re: Client & Network Printer settings
Date:
09/29/2007 17:45:42
This might be a known issue. Please check this
http://support.microsoft.com/kb/q243942/.
--
This posting is provided "AS IS" with no
warranties, and confers no rights.
"Brett Sadler" wrote in message
news:A32EDF1B-0BFE-4F48-8C9E-41BF9F4D874A@microsoft.com...
> Hello,
>
> Hopefully someone can point me in the right
direction with the issues I'm
> having and that I explain this in an
understandable manner.
>
> We have a TS server that we have for our
Accounting (Dynamics 9)
> department
> only. Currently, we have it setup through client
registry settings so
> that
> they have only their default printer connecting
through to the RDP
> session.
> This works fine. However, it was constantly
defaulting to the client
> printer, as opposed to being only just available.
I realize this is by
> design.
>
> Since only one person has a local printer, under
the RDP connection
> properties on the Client Settings tab, I turned
off the "Use connection
> settings from user settings" box, left
drives and printers at logon
> checked,
> but unchecked the auto default to main client printer.
>
> The reason I took this route is due to the client
printers not having the
> ability to print double sided since not all of
the printer properties are
> available. Two of our accounting people NEED this
functionality as part
> of
> their job. To try to get around this issue, we
setup policy so they
> received
> network printers.
>
> Now we are having two problems:
> 1. The user with the client printer can't set her
local printer as
> default
> after she logs in and have it persist through so
the next time she logs in
> it
> remains the default printer
> 2. The double sided print settings for our other
two users on the network
> printer won't persist through another login, so
when they make change to
> double sided (duplex) printing, and then log out
for the day, when they
> log
> back in to TS server, it has reverted back to the
single sided printing.
>
> Does this look like a printer policy issue where
the printers are being
> re-pushed at every login, overwriting settings?
Or is this an issue with
> the
> TS client? Thank you in advance!
Top
From: TP
<tperson.knowspamn@mailandnews.com>
To:
none
Subject:
Re: Clear terminal server device cals
Date:
09/20/2007 08:28:33
There is no need to. The license will eventually
expire and
return to the available pool. In the meantime the
server will
issue the new replacement device a temporary CAL that
will
be valid long enough for the old one to expire.
-TP
Theresa wrote:
> When you retire computers, how do you clear out
the terminal server
> device cals?
Top
From: Lance
<Lance@discussions.microsoft.com>
To:
none
Subject:
Re: Cannot Remote Control: Error 7054
Date:
09/20/2007 15:56:01
I'm having the same issue, My options are grayed out
under Remote Control,
but thats because I have Use remote control with
default user settings
selected (which is what I want and it doesn't matter,
I've tried to change
this option). Anyway, I have another TS server that I
am replacing with this
one, I have all the settings identical, policies
identical etc, using the
same licensing server. The old server works just fine,
but this server for
some reason will not work. If I try to remote control
from the old server to
the new I get the same message.
The only notable differences are the new server is R2
with SP2 and the old
server is just SP1, but both have all other updates installed.
This thread
is the only information I can find anywhere relating
to this error. I really
don't want to completely redo the server yet again,
any help would be
appreciated.
"Vera Noest [MVP]" wrote:
> I don't know how to continue, something seems not
right with your
> GPO's.
>
> In TSCC, Remote Control is Disabled and greyed
out, and that must
> mean that there's a policy which disables Remote
Control. I don't
> know why you don't see it in RSoP.
>
> It seems to me that the problem has nothing to do
with TS as such, to
> me it looks like a GPO problem. I'd post in the
GPO newsgroup,
> hopefully there's someone there who can help you
better:
>
> microsoft.public.windows.group_policy
>
_________________________________________________________
> 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?Sm9oYW5uZXM=?=
> wrote on 15 sep 2007 in
> microsoft.public.windows.terminal_services:
>
> > Here are the results.
> >
> > I run rsop.msc on the troubled terminal
server:
> > - "Computer Configuration" >
"Administrative templates" >
> > "Windows
> > Components" > "Terminal
Services" > "Sets rules for remote
> > control of Terminal Services user
sessions", State is Enabled
> > and GPO Name is "Local Group
Policy". When I double clicked on
> > this entry everything is greyed out. Btw,
under Terminal
> > Services, "Sets rules ..." is the
only setting available.
> > - The same thing is under "User
Configuration" >
> > "Administrative templates"
> >> "Windows Components" >
"Terminal Services" > "Sets rules for
> >> remote control
> > of Terminal Services user sessions"
> >
> > On the troubled Terminal Server, I then
executed gpedit.msc:
> > - "Computer Configuration" >
"Administrative templates" >
> > "Windows
> > Components" > "Terminal
Services" > "Sets rules for remote
> > control of Terminal Services user
sessions" has the State
> > Enable, when I double clicked on it,
"Enabled" is selected with
> > Options "Full Control without user's
permission".
> > - Exact same value and settings for
"User Configuration" >
> > "Administrative
> > templates" > "Windows
Components" > "Terminal Services" > "Sets
> > rules for remote control of Terminal
Services user sessions"
> >
> > Remote Control still does not work. How
should I proceed?
> >
> >
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> Now we're getting close!
> >> Greyed out settings on the Remote
Control tab in the rdp-tcp
> >> properties simply mean that there is a
Group Policy which
> >> prohibits remote Control.
> >> Check all GPOs which affect your
Terminal Server. Run RSoP
> >> (Resultant Set of Policies) to see which
GPOs apply.
> >>
> >> You'll find the setting in:
> >>
> >> Computer Configuration - Administrative
templates - Windows
> >> Components - Terminal Services
> >> "Sets rules for remote control of
Terminal Services user
> >> sessions"
> >> _________________________________________________________
Vera
> >> Noest MCSE, CCEA, Microsoft MVP -
Terminal Server
> >> TS troubleshooting:
http://ts.veranoest.net
>
Top
From: Meinolf Weber
<meiweb(nospam)@gmx.de>
To:
none
Subject:
Re: Cannot Login to via Remote Desktop
Date:
09/26/2007 15:15:39
Hello RM,
Can you ping the servers via ip address and server
name from the client?
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS"
with no warranties, and confers
no rights.
> I have two 2003 servers that I cannot log into
using remote desktop.
> I used to be able to but I rebooted the client
and could not access
> the servers any more. The error msg that I get is
>
> The system cannot log you on due to the following
error:
> The network address is invalid.
> I get the same error message from other clients
now when accessing
> these 2 servers. However, I can access the other
servers on the
> network w/o any problems.
>
> Any ideas ?
>
> TIA,
>
> RM.
>
Top
From: RM
<darasingha_nospam@yahoo.com>
To:
none
Subject:
Re: Cannot Login to via Remote Desktop
Date:
09/26/2007 15:47:35
Yes - all other network access works fine.
"Meinolf Weber" wrote in message
news:ff16fb665aab68c9cea1e7f92250@msnews.microsoft.com...
> Hello RM,
>
> Can you ping the servers via ip address and
server name from the client?
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS
IS" with no warranties, and
confers
> no rights.
>
> > I have two 2003 servers that I cannot log
into using remote desktop.
> > I used to be able to but I rebooted the
client and could not access
> > the servers any more. The error msg that I
get is
> >
> > The system cannot log you on due to the
following error:
> > The network address is invalid.
> > I get the same error message from other
clients now when accessing
> > these 2 servers. However, I can access the
other servers on the
> > network w/o any problems.
> >
> > Any ideas ?
> >
> > TIA,
> >
> > RM.
> >
>
>
Top
From: TP
<tperson.knowspamn@mailandnews.com>
To:
none
Subject:
Re: Cannot add favourites to Internet Explorer
Date:
09/29/2007 11:43:30
Hi,
Is this registry path correct as well for each user:
HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell
Folders
Favorites REG_SZ
Log on as an administrator, run Process Monitor, and
then have
a normal user attempt to add a favorite. Look for any
ACCESS
DENIED or other errors.
Process Monitor
http://www.microsoft.com/technet/sysinternals/utilities/processmonitor.mspx
-TP
goundhog wrote:
> Users are unable to add to favourites in Internet
Explorer 6.0 on my
> W2003 Terminal Server
>
> There is no error mesage or event viewer message
>
> Administrators can add them OK
>
> Favourites have not been redirected and users
have full rights to
> their profile on the server and on the roaming
profile share
>
> I have checked in the registry and this entry is
correct
>
> HKCU \ Software \ Microsoft \ Windows \ Current
Version \ Explorer \
> UserShell \
> %userprofile%
>
> Any ideas where to check next ?
Top
From: goundhog
<goundhog@discussions.microsoft.com>
To:
none
Subject:
Re: Cannot add favourites to Internet Explorer
Date:
09/29/2007 16:12:00
Thanks for the reply
I ran Process Monitor but there are no such errors
when the user attempts to
add to Favorites. They also cannot Organise Favorites.
Regarding
HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell
Folders
Favorites REG_SZ
That path is C:\Docouments and Setttings \
Administrator \ Favorites
"TP" wrote:
> Hi,
>
> Is this registry path correct as well for each
user:
>
>
HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders
>
> Favorites REG_SZ
>
> Log on as an administrator, run Process Monitor,
and then have
> a normal user attempt to add a favorite. Look for
any ACCESS
> DENIED or other errors.
>
> Process Monitor
>
>
http://www.microsoft.com/technet/sysinternals/utilities/processmonitor.mspx
>
> -TP
>
> goundhog wrote:
> > Users are unable to add to favourites in
Internet Explorer 6.0 on my
> > W2003 Terminal Server
> >
> > There is no error mesage or event viewer
message
> >
> > Administrators can add them OK
> >
> > Favourites have not been redirected and
users have full rights to
> > their profile on the server and on the
roaming profile share
> >
> > I have checked in the registry and this
entry is correct
> >
> > HKCU \ Software \ Microsoft \ Windows \
Current Version \ Explorer \
> > UserShell \
> > %userprofile%
> >
> > Any ideas where to check next ?
>
Top
From: TP
<tperson.knowspamn@mailandnews.com>
To:
none
Subject:
Re: Cannot add favourites to Internet Explorer
Date:
09/29/2007 19:04:23
Are you saying that when you log on as each individual
user (not administrator) and check their HKCU you
see C:\Documents and Settings\Administrator\Favorites
as the path?
That is not correct, each user normally should point
to
their own unique location.
-TP
goundhog wrote:
> Thanks for the reply
>
> I ran Process Monitor but there are no such
errors when the user
> attempts to add to Favorites. They also cannot
Organise Favorites.
>
> Regarding
>
>
HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders
>
> Favorites REG_SZ
>
> That path is C:\Docouments and Setttings \
Administrator \ Favorites
Top
From: goundhog
<goundhog@discussions.microsoft.com>
To:
none
Subject:
Re: Cannot add favourites to Internet Explorer
Date:
09/30/2007 08:59:01
Sorry - when i log on as the users there is no entry
for that !
That is clearly the problem
If I manually add it - doesn't make any difference.
When the user logs off
and on - the entry is still blank
I need to find a way of getting the correct path in
their for all users !
"TP" wrote:
> Are you saying that when you log on as each
individual
> user (not administrator) and check their HKCU you
> see C:\Documents and
Settings\Administrator\Favorites
> as the path?
>
> That is not correct, each user normally should
point to
> their own unique location.
>
> -TP
>
> goundhog wrote:
> > Thanks for the reply
> >
> > I ran Process Monitor but there are no such
errors when the user
> > attempts to add to Favorites. They also
cannot Organise Favorites.
> >
> > Regarding
> >
> > HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell
Folders
> >
> > Favorites REG_SZ
> >
> > That path is C:\Docouments and Setttings \
Administrator \ Favorites
>
Top
From: Susan Bradley, CPA aka Ebitz - SBS
Rocks [MVP] <sbradcpa@pacbell.net>
To:
Smiley <firework123@googlemail.com>
Subject:
Re: Can't rdp in Vista
Date:
09/26/2007 09:13:25
Biz ..enable the Remote tab
Home Premium if I remember right, you can't.
Smiley wrote:
> Hi,
>
> Don't seem to find a group for Vista rdp. If
wrong forum, please let me
> know.
>
>
> I have two similar problem. I am sure when one is
resolve the other will
> follow.
>
> One with Vista Home premium, one with Vista
Business premium. Can't rdp into
> either of those machines. Received the following
error : The client could
> not connect to the remote computer. Remote
connections might not be enabled
> or the computer might be too busy to accept new
connections. It is also
> possible that network problems are preventing
your connection.
>
> 1. add port 3389 to Exception in firewall on the
machine to be rdp in.
> 2. on the remote tab on my computer properties
setting. allow remote logon.
>
> Any idea what else I have missed???
>
>
> Any help appreciated.
>
>
>
Top
From: Charlie Russel - MVP
<charlie@mvKILLALLSPAMMERSps.org>
To:
none
Subject:
Re: Can't rdp in Vista
Date:
09/26/2007 09:31:40
Home Premium - no RDP. Period.
Business - enable in Remote Tab, System Properties.
AND make sure to check
the box that allows unsecured, downlevel connections.
--
Charlie.
http://msmvps.com/blogs/xperts64
"Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]"
wrote in message news:46FA6905.6060801@pacbell.net...
> Biz ..enable the Remote tab
>
> Home Premium if I remember right, you can't.
>
> Smiley wrote:
>> Hi,
>>
>> Don't seem to find a group for Vista rdp. If
wrong forum, please let me
>> know.
>>
>>
>> I have two similar problem. I am sure when
one is resolve the other will
>> follow.
>>
>> One with Vista Home premium, one with Vista
Business premium. Can't rdp
>> into either of those machines. Received the
following error : The client
>> could not connect to the remote computer.
Remote connections might not be
>> enabled or the computer might be too busy to
accept new connections. It
>> is also possible that network problems are
preventing your connection.
>>
>> 1. add port 3389 to Exception in firewall on
the machine to be rdp in.
>> 2. on the remote tab on my computer
properties setting. allow remote
>> logon.
>>
>> Any idea what else I have missed???
>>
>>
>> Any help appreciated.
>>
>>
Top
From: Smiley
<firework123@googlemail.com>
To:
none
Subject:
Re: Can't rdp in Vista
Date:
09/26/2007 10:14:22
Well, the exact tab which I used was
COMPUTER properties --> REMOTE SETTING -->
REMOTE tab and checked the
following :
1. allow remote assitant connect to this computer
2. in the ADVANCE button allow this computer to be
controlled remotely
Update on after posting the first message.
From NETWORK --> click on the network name (which
is a wireless
connection) --> Properties --> SHARE tab,
checked the following
1. Allow other network user to connect throught this
computer's internet
connection.
2. This already checked and grey out before the 1 was
checked. Allow other
netwrok user to control or disable the selected
internet connection.
When the later was checked and rpd in from xp machine
or sbs 2003 or windows
2003 server, the following error 'The remote
connection has time out' other
then this error keep coming up, nothing else happened
- just cannot connect.
Any thought ?
"Susan Bradley, CPA aka Ebitz - SBS Rocks
[MVP]"
wrote in message news:46FA6905.6060801@pacbell.net...
> Biz ..enable the Remote tab
>
> Home Premium if I remember right, you can't.
>
> Smiley wrote:
>> Hi,
>>
>> Don't seem to find a group for Vista rdp. If
wrong forum, please let me
>> know.
>>
>>
>> I have two similar problem. I am sure when
one is resolve the other will
>> follow.
>>
>> One with Vista Home premium, one with Vista
Business premium. Can't rdp
>> into either of those machines. Received the
following error : The client
>> could not connect to the remote computer.
Remote connections might not be
>> enabled or the computer might be too busy to
accept new connections. It
>> is also possible that network problems are
preventing your connection.
>>
>> 1. add port 3389 to Exception in firewall on
the machine to be rdp in.
>> 2. on the remote tab on my computer
properties setting. allow remote
>> logon.
>>
>> Any idea what else I have missed???
>>
>>
>> Any help appreciated.
>>
>>
Top
From: Sooner Al [MVP]
<SoonerAl@somewhere.net.invalid>
To:
none
Subject:
Re: Can't rdp in Vista
Date:
09/26/2007 11:07:29
"Smiley" wrote in message
news:fddt1b$deb$2$8300dec7@news.demon.co.uk...
> Well, the exact tab which I used was
>
> COMPUTER properties --> REMOTE SETTING -->
REMOTE tab and checked the
> following :
> 1. allow remote assitant connect to this computer
> 2. in the ADVANCE button allow this computer to
be controlled remotely
>
> Update on after posting the first message.
> From NETWORK --> click on the network name
(which is a wireless
> connection) --> Properties --> SHARE tab,
checked the following
> 1. Allow other network user to connect throught
this computer's internet
> connection.
> 2. This already checked and grey out before the 1
was checked. Allow other
> netwrok user to control or disable the selected
internet connection.
>
> When the later was checked and rpd in from xp
machine or sbs 2003 or
> windows 2003 server, the following error 'The
remote connection has time
> out' other then this error keep coming up,
nothing else happened - just
> cannot connect.
>
> Any thought ?
>
>
> "Susan Bradley, CPA aka Ebitz - SBS Rocks
[MVP]"
> wrote in message
news:46FA6905.6060801@pacbell.net...
>> Biz ..enable the Remote tab
>>
>> Home Premium if I remember right, you can't.
>>
>> Smiley wrote:
>>> Hi,
>>>
>>> Don't seem to find a group for Vista rdp.
If wrong forum, please let me
>>> know.
>>>
>>>
>>> I have two similar problem. I am sure
when one is resolve the other will
>>> follow.
>>>
>>> One with Vista Home premium, one with
Vista Business premium. Can't rdp
>>> into either of those machines. Received
the following error : The client
>>> could not connect to the remote computer.
Remote connections might not
>>> be enabled or the computer might be too
busy to accept new connections.
>>> It is also possible that network problems
are preventing your
>>> connection.
>>>
>>> 1. add port 3389 to Exception in firewall
on the machine to be rdp in.
>>> 2. on the remote tab on my computer
properties setting. allow remote
>>> logon.
>>>
>>> Any idea what else I have missed???
>>>
>>>
>>> Any help appreciated.
>>>
>>>
>
In the first case your mixing Remote Assistance with
Remote Desktop. As
noted by other Vista Home Premium or Basic can *NOT*
act as a Remote Desktop
host. You might look at using UltraVNC as an
alternative.
As far as Vista Business is concerned if your trying
to connect from XP or
earlier make sure you have the Vista host configured
like this...
http://theillustratednetwork.mvps.org/ScreenShots/XP/RDP6-XPClienttoVistaServerConfig.jpg
...and the XP or earlier client configured like
this...
http://theillustratednetwork.mvps.org/ScreenShots/XP/RDP6-XPClientSettings.jpg
It sounds like your trying to connect through a VPN?
Is that true? Can you
ping the Vista host when you connected to the VPN?
Perhaps you should
describe the network the Vista Business host computer
is on, ie. in a
domain, behind a firewall, etc...etc...
--
Al Jarvi (MS-MVP Windows Networking)
Please post *ALL* questions and replies to the news
group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no
warranties, and confers no
rights...
How to ask a question
http://support.microsoft.com/KB/555375
Top
From: Costas
<cpstechgroup@gmail.com>
To:
none
Subject:
Re: Can't rdp in Vista
Date:
09/26/2007 09:21:00
A couple of groups you might want to try:
microsoft.public.windows.vista.networking_sharing
microsoft.public.windows.vista.general
I assume you aren't using Small Business Server. 3389
isn't necessary to
open on the Firewall if you enable Remote Desktop. The
exception is being
added by default and you should be able to see it
under 'Exceptions'. As far
as Vista Home Premium goes, if I'm not mistaken, it
doesn't support inbound
RDP connections. For the Vista Business you should be
able to connect to
it. Take a look at he following article and see if it
helps
http://support.microsoft.com/kb/925876
--
Costas
"Smiley" wrote in message
news:fddokc$75f$2$8300dec7@news.demon.co.uk...
> Hi,
>
> Don't seem to find a group for Vista rdp. If
wrong forum, please let me
> know.
>
>
> I have two similar problem. I am sure when one is
resolve the other will
> follow.
>
> One with Vista Home premium, one with Vista
Business premium. Can't rdp
> into either of those machines. Received the
following error : The client
> could not connect to the remote computer. Remote
connections might not be
> enabled or the computer might be too busy to
accept new connections. It is
> also possible that network problems are
preventing your connection.
>
> 1. add port 3389 to Exception in firewall on the
machine to be rdp in.
> 2. on the remote tab on my computer properties
setting. allow remote
> logon.
>
> Any idea what else I have missed???
>
>
> Any help appreciated.
>
>
>
Top
From: TP
<tperson.knowspamn@mailandnews.com>
To:
none
Subject:
Re: Can I use local SCSI, USB, Paralel, Serial ports on client
compute
Date:
09/24/2007 14:46:40
Scanner redirection is not natively supported. For
this you
can use a third-party application, for example:
http://www.remote-scan.com/feature-list-connecting-scanner-to-network.php
Audio support is one-way (Output). This means that an
audio
input device (such as a recorder) from the workstation
is not
natively supported. Again a third-party app would be
required.
USB memory sticks are supported via local drive
redirection.
Make your local disk drives available in a session
http://technet2.microsoft.com/windowsserver/en/library/91e5965b-386a-4da1-ac1d-7b8128c28c271033.mspx?mfr=true
Local printer redirection is supported if the drivers
are TS
compatible or you can map to compatible printer
driver. I
recommend you install the version of the Remote
Desktop
Client located on your 2003 server's hard drive here:
C:\WINDOWS\system32\clients\tsclient\win32\msrdpcli.msi
Terminal Services and Printing
http://www.microsoft.com/windowsserver2003/techinfo/overview/tsprint.mspx
Make your local printer available in a session
http://technet2.microsoft.com/windowsserver/en/library/91e5965b-386a-4da1-ac1d-7b8128c28c271033.mspx?mfr=true
Serial port redirection is supported. You should test
with your
specific application and device to see if they are
compatible.
Make your local serial port available in a session
http://technet2.microsoft.com/windowsserver/en/library/17d44d9a-cf4b-4a6a-94ec-093cb5f8b2b71033.mspx?mfr=true
Configure settings for mapping client devices
http://technet2.microsoft.com/windowsserver/en/library/17d44d9a-cf4b-4a6a-94ec-093cb5f8b2b71033.mspx?mfr=true
Support for local device redirection has been enhanced
in
Windows Server 2008, see here:
Terminal Server Plug and Play Device Redirection
Framework in Vista and Longhorn: Part 1
http://blogs.msdn.com/ts/archive/2006/12/05/terminal-server-plug-and-play-device-redirection-framework-in-vista-and-longhorn-part-1.aspx
-TP
Daniel Valach wrote:
> I need to use applications with Fujitsu scanner
on local SCSI port,
> and local USB port with Olympus Digital voice recorder,
and USB
> memory sticks.
> Other needs would require local printer, either
parallel or USB and
> serial port use for hyperterminal command prompt
controlled devices.
> Is this possible on terminal services client or
do I need to do these
> functions locally?
> I have Windows Enterprise server 2003 R2 running
teminal services
> applications to clients.
> If yes, I need either articel or instructions on
how to do it.
>
> Daniel
Top
From: Jeff Pitsch
<Jeff@Jeffpitschconsulting.com>
To:
none
Subject:
Re: Burning a CD on Windows Server 2003 Terminal services -
FromClien
Date:
09/26/2007 12:22:12
see inline
Jeff Pitsch
Microsoft MVP - Terminal Server
Citrix Technology Professional
Provision Networks VIP
Forums not enough?
Get support from the experts at your business
http://jeffpitschconsulting.com
eric Wood wrote:
> Hello.
>
> We have a dedicated Windows Server 2003 box and
HP Thin Clients.
>
> I understand that the HP Thin Clients and the
Windows server support local
> drive mapping (For CDROM drives, USB drives,
etc), however we would like to
> take it one step further.
>
> We have a HP Read/Write CD/DVD USB drive to
accommodate the HP Thin Clients.
> We can get the Thin Client to see the CD
functionality of the USB device,
> however we are unable to get the O/S to recognize
the "burning" side.
>
> Here's my question.
> The CDROM drive can with software for burning. I
don't want to just install
> the software on the terminal server without some
sort of confidence it is
> going to work. The Terminal Server is not picking
up the drive as a CDRW
> drive, and as a result I don't see how a program
can notice the difference.
> It only knows whta the OS tells it.
No, TS doesn't recognize CD-ROM drives. The remapped
drives are
recognized as network drives. This will not work.
>
> My second question (although I think I know the
answer to this).
> Will users be able to put a music CD into the
drive, connect to Terminal
> Services, and play through the speakers? The
music CD would not be MP3, it
> would be a normal music CD which would come from
a music store.
You could potentially do this the question is do you
want too. The
enormous amount of bandwidth that would be used and
the enormous amount
of resources used on the server to play the CD's would
have a huge
detrimental effect on your users sessions.
>
> Any help would be appreciated.
>
> Thank You
>
> Eric Wood
Top
From: Vera Noest [MVP]
<vera.noest@remove-this.hem.utfors.se>
To:
none
Subject:
Re: audio delay
Date:
09/28/2007 13:32:11
There's not much that you can do about it.
Audio quality in rdp is not configurable, and it's not
very good.
It's OK for system sounds and beeps, but don't use it
for streaming
video.
Audio quality in Citrix is configurable in 3 levels,
with different
bandwidth usage, and the quality is much better.
_________________________________________________________
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?bWFydGluaGVt?=
wrote on 28 sep 2007 in
microsoft.public.windows.terminal_services:
> Hi all.
> I´am conected to a computer by rdp, this
computer is doing
> video and audio streaming.
> The video streaming without audio available is
working fine, but
> when I enable audio, both start works whit delay
and freezes.
> I think that the problem is the audio rdp driver,
is there any
> way to improve it?.
> Thanks in advance
Top
From: Meinolf Weber
<meiweb(nospam)@gmx.de>
To:
none
Subject:
Re: Application Errors
Date:
09/26/2007 16:08:51
Hello Lance,
Try calling Citrix support.
http://www.citrix.com/English/contact/index.asp?ntref=hp_nav_US
http://www.citrix.com/English/SS/supportSecond.asp?slID=38676
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS"
with no warranties, and confers
no rights.
> I recently applied the windows updates to my 2003
server running PS
> 4.5 after I applied the windows updates I have
one application that
> will no longer run. I have tried contracting the
vendor of the
> software but they tell me it's a problem with the
updates that windows
> got. They also told me that they have one other
Citrix customer that
> has the exact same problem. Any assistance would
greatly be
> appreciated. I have used the Filemon/Regmon etc
to see if there was
> anything getting denied permission etc but I
still get the following
> error message.
>
> Event Type: Error
> Event Source: Application Error
> Event Category: (100)
> Event ID: 1000
> Date: 9/25/2007
> Time: 11:31:47 AM
> User: N/A
> Computer: Citrix1
> Description:
> Faulting application BondPro.exe, version
4.0.0.0, faulting module
> BondPro.exe, version 4.0.0.0, fault address
0x00004779.
> For more information, see Help and Support Center
at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 41 70 70 6c 69 63 61 74 Applicat
> 0008: 69 6f 6e 20 46 61 69 6c ion Fail
> 0010: 75 72 65 20 20 42 6f 6e ure Bon
> 0018: 64 50 72 6f 2e 65 78 65 dPro.exe
> 0020: 20 34 2e 30 2e 30 2e 30 4.0.0.0
> 0028: 20 69 6e 20 42 6f 6e 64 in Bond
> 0030: 50 72 6f 2e 65 78 65 20 Pro.exe
> 0038: 34 2e 30 2e 30 2e 30 20 4.0.0.0
> 0040: 61 74 20 6f 66 66 73 65 at offse
> 0048: 74 20 30 30 30 30 34 37 t 000047
> 0050: 37 39 79
Top
From: Meinolf Weber <meiweb(nospam)@gmx.de>
To:
none
Subject:
Re: Advise needed on using one profile for TS/Citrix and fat
client sessions
Date:
09/21/2007 00:50:22
Hello murras68,
It is possible, BUT you will become problems with some
settings in the profile,
depending on the software and software configuration.
I suggest to use two
profiles. We have the same and had some problems in
the beginning, since
we use two profiles it is fine.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS"
with no warranties, and confers
no rights.
> Hi,
>
> Can anyone advise me on whether it is possible to
use the same profile
> for roaming users when they are using their
normal (Fat client) and
> TS/
> Citrix sessions using the group policy Loopback processing
in Replace
> mode and the UPHClean utility to resolve the
corruption issues that
> may have existed in the past.
> We want to enable our users to save and retrieve
their documents etc
> from the same location on the network instead of
having to create two
> profile paths / home directories. I have
> We also intend to use Outlook Web Access for out
external users.
> Thanks
>
> M
>
Top
From: Vera Noest [MVP]
<vera.noest@remove-this.hem.utfors.se>
To:
none
Subject:
Re: Advise needed on using one profile for TS/Citrix and fat
client sessions
Date:
09/21/2007 13:57:53
I agree with Meinolf, using the same profile is most
likely going
to cause problems.
You can still give users a central place to save their
files by
redirecting their My Documents folder in both profiles
to the same
home directory on a network share.
This is easiest done with a GPO:
User Configuration - Windows Settings - Folder Redirection
My Documents
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email
___
Meinolf Weber wrote on 21 sep 2007 in
microsoft.public.windows.terminal_services:
> Hello murras68,
>
> It is possible, BUT you will become problems with
some settings
> in the profile, depending on the software and
software
> configuration. I suggest to use two profiles. We
have the same
> and had some problems in the beginning, since we
use two
> profiles it is fine.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS
IS" with no warranties,
> and confers no rights.
>
>> Hi,
>>
>> Can anyone advise me on whether it is
possible to use the same
>> profile for roaming users when they are using
their normal (Fat
>> client) and TS/
>> Citrix sessions using the group policy
Loopback processing in
>> Replace mode and the UPHClean utility to
resolve the corruption
>> issues that may have existed in the past.
>> We want to enable our users to save and
retrieve their
>> documents etc from the same location on the
network instead of
>> having to create two profile paths / home
directories. I have
>> We also intend to use Outlook Web Access for
out external
>> users. Thanks
>>
>> M
Top
From: murras68
<murras68@hotmail.com>
To:
none
Subject:
Re: Advise needed on using one profile for TS/Citrix and fat
client sessions
Date:
09/22/2007 01:16:45
On 21 Sep, 06:50, Meinolf Weber wrote:
> Hellomurras68,
>
> It is possible, BUT you will become problems with
some settings in the profile,
> depending on the software and software
configuration. I suggest to use two
> profiles. We have the same and had some problems
in the beginning, since
> we use two profiles it is fine.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS
IS" with no warranties, and confers
> no rights.
>
>
>
> > Hi,
>
> > Can anyone advise me on whether it is
possible to use the same profile
> > for roaming users when they are using their
normal (Fat client) and
> > TS/
> > Citrix sessions using the group policy
Loopback processing in Replace
> > mode and the UPHClean utility to resolve the
corruption issues that
> > may have existed in the past.
> > We want to enable our users to save and
retrieve their documents etc
> > from the same location on the network
instead of having to create two
> > profile paths / home directories. I have
> > We also intend to use Outlook Web Access for
out external users.
> > Thanks
>
> > M- Hide quoted text -
>
> - Show quoted text -
Thanks.
What are you views on the using Appsense to manage
roaming and TS/
Citrix profiles.
Top
From: Meinolf Weber
<meiweb(nospam)@gmx.de>
To:
none
Subject:
Re: Advise needed on using one profile for TS/Citrix and fat
client sessions
Date:
09/22/2007 16:55:15
Hello murras68,
I have no experience with Appsense. But is seems to be
an additional tool
with a lot more functionalities as only managing
profiles.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS"
with no warranties, and confers
no rights.
> On 21 Sep, 06:50, Meinolf Weber wrote:
>
>> Hellomurras68,
>>
>> It is possible, BUT you will become problems
with some settings in
>> the profile,
>> depending on the software and software
configuration. I suggest to
>> use two
>> profiles. We have the same and had some
problems in the beginning,
>> since
>> we use two profiles it is fine.
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS
IS" with no warranties, and
>> confers
>> no rights.
>>> Hi,
>>>
>>> Can anyone advise me on whether it is
possible to use the same
>>> profile
>>> for roaming users when they are using
their normal (Fat client) and
>>> TS/
>>> Citrix sessions using the group policy
Loopback processing in
>>> Replace
>>> mode and the UPHClean utility to resolve
the corruption issues that
>>> may have existed in the past.
>>> We want to enable our users to save and
retrieve their documents etc
>>> from the same location on the network
instead of having to create
>>> two
>>> profile paths / home directories. I have
>>> We also intend to use Outlook Web Access
for out external users.
>>> Thanks
>>> M- Hide quoted text -
>>>
>> - Show quoted text -
>>
> Thanks.
>
> What are you views on the using Appsense to
manage roaming and TS/
> Citrix profiles.
>
Top
From: Jeff Pitsch
<Jeff@Jeffpitschconsulting.com>
To:
none
Subject:
Re: A Good GP for Terminal Servers
Date:
09/25/2007 12:08:27
There are so many variables that go into the amount of
users on a
system. No two systems are the same or are configured
the same. You
can take two systems, same hardware, same software,
and get two
different amount of users on them simply because they
use the software
differently.
Jeff Pitsch
Microsoft MVP - Terminal Server
Citrix Technology Professional
Provision Networks VIP
Forums not enough?
Get support from the experts at your business
http://jeffpitschconsulting.com
nhance wrote:
> Hi,
>
> Does anyone have a good well rounded Group Policy
for Terminal Servers and
> TS users, i do not mind buying one or a guide. It
seems some people get a
> lot more users onto one box than we seem to and i
can only think this is due
> to a good GP with maybe a automated nightly
restart?
>
> Best practices and what to disable or turn on and
off to assist with speed
> and maximum. If there are AV's and others that
allow more power out of the
> server feel free to let the info fly...
>
> Thank you
Top
From: nhance
<nhance@discussions.microsoft.com>
To:
none
Subject:
Re: A Good GP for Terminal Servers
Date:
09/25/2007 12:28:02
so what about a managed server concept, lock after so
long, reset a session,
no backgrounds etc, what makes for a good
Office, Internet, Finance Package type terminal server
GP, i just want to
run it lean on colours etc and speed for our remote
users doing office duties
and timesheets
"Jeff Pitsch" wrote:
> There are so many variables that go into the
amount of users on a
> system. No two systems are the same or are configured
the same. You
> can take two systems, same hardware, same
software, and get two
> different amount of users on them simply because
they use the software
> differently.
>
> Jeff Pitsch
> Microsoft MVP - Terminal Server
> Citrix Technology Professional
> Provision Networks VIP
>
> Forums not enough?
> Get support from the experts at your business
> http://jeffpitschconsulting.com
>
> nhance wrote:
> > Hi,
> >
> > Does anyone have a good well rounded Group
Policy for Terminal Servers and
> > TS users, i do not mind buying one or a
guide. It seems some people get a
> > lot more users onto one box than we seem to
and i can only think this is due
> > to a good GP with maybe a automated nightly
restart?
> >
> > Best practices and what to disable or turn
on and off to assist with speed
> > and maximum. If there are AV's and others
that allow more power out of the
> > server feel free to let the info fly...
> >
> > Thank you
>
Top
From: Jeff Pitsch
<Jeff@Jeffpitschconsulting.com>
To:
none
Subject:
Re: /console option doesn't seem to exist with Windows Server
2008
Date:
09/25/2007 09:51:52
If I remember correctly, MS has done away with a classic
console
connection. All sessions are now treated the same. Are
you not able to
do something while connected? I may be wrong on this
though I know it
was discussed but not sure it was truly implemented.
Jeff Pitsch
Microsoft MVP - Terminal Server
Citrix Technology Professional
Provision Networks VIP
Forums not enough?
Get support from the experts at your business
http://jeffpitschconsulting.com
Ross wrote:
> I've recently started testing Terminal Services
using Windows Server 2008
> Beta 3, and I've noticed that using the command
mstsc.exe /console does not,
> in fact, provide a console connection.
>
> Has this option been removed? Is there any way to
obtain this functionality
> using Windows Server 2008?
>
> Thanks.
>
Top
From: Ross
<ross_remov_chappell@epidirect_dot_com>
To:
none
Subject:
Re: /console option doesn't seem to exist with Windows Server
2008
Date:
09/25/2007 10:16:05
Thanks for your reply Jeff.
I haven't done extensive testing to see if there are
things that cannot be
done, so I'll need to keep an eye out. The biggest
issue so far is that the
terminal server is configured to "run the
following program when the user
logs on", but this program is meant to be run
when end-users log on and not
when administrators log on.
This wasn't an issue with Windows 2003 because
administrators would log onto
the console. Since this program presents an
application control panel that,
among other things, hides the underlying windows
desktop it makes remote
management of the server a little difficult.
--
Ross Chappell
EPI Internet Direct
http://www.epidirect.com
"Jeff Pitsch" wrote:
> If I remember correctly, MS has done away with a
classic console
> connection. All sessions are now treated the
same. Are you not able to
> do something while connected? I may be wrong on
this though I know it
> was discussed but not sure it was truly
implemented.
>
> Jeff Pitsch
> Microsoft MVP - Terminal Server
> Citrix Technology Professional
> Provision Networks VIP
>
> Forums not enough?
> Get support from the experts at your business
> http://jeffpitschconsulting.com
>
> Ross wrote:
> > I've recently started testing Terminal
Services using Windows Server 2008
> > Beta 3, and I've noticed that using the
command mstsc.exe /console does not,
> > in fact, provide a console connection.
> >
> > Has this option been removed? Is there any
way to obtain this functionality
> > using Windows Server 2008?
> >
> > Thanks.
> >
>
Top
From: Vera Noest [MVP]
<vera.noest@remove-this.hem.utfors.se>
To:
none
Subject:
Re: /console option doesn't seem to exist with Windows Server
2008
Date:
09/25/2007 13:34:57
Then you have been relying on Administrators always
connecting to
the console session to avoid the application.
Instead, configure a GPO with this starting
application, and filter
the security for the GPO to exclude Administrators
from it's
effects.
816100 - How To Prevent Domain Group Policies from
Applying to
Administrator Accounts and Selected Users in Windows
Server 2003
http://support.microsoft.com/?kbid=816100
_________________________________________________________
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?Um9zcw==?= wrote
on 25 sep 2007 in
microsoft.public.windows.terminal_services:
> Thanks for your reply Jeff.
>
> I haven't done extensive testing to see if there
are things that
> cannot be done, so I'll need to keep an eye out.
The biggest
> issue so far is that the terminal server is
configured to "run
> the following program when the user logs
on", but this program
> is meant to be run when end-users log on and not
when
> administrators log on.
>
> This wasn't an issue with Windows 2003 because
administrators
> would log onto the console. Since this program
presents an
> application control panel that, among other
things, hides the
> underlying windows desktop it makes remote
management of the
> server a little difficult.
Top
From: Vera Noest [MVP]
<vera.noest@remove-this.hem.utfors.se>
To:
none
Subject:
Re: /console option doesn't seem to exist with Windows Server
2008
Date:
09/25/2007 13:40:54
That's correct, no /console connections in 2008
anymore.
Session 0 still exists, but it hosts only services and
is not an
interactive session anymore.
Explained in detail here:
Console Behavior Differences in Longhorn Server
Terminal Services
http://blogs.msdn.com/ts/archive/2006/11/27/console-behavior-
differences-in-longhorn-server-terminal-services.aspx
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email
___
Jeff Pitsch wrote on 25 sep 2007
in microsoft.public.windows.terminal_services:
> If I remember correctly, MS has done away with a
classic console
> connection. All sessions are now treated the
same. Are you not
> able to
> do something while connected? I may be wrong on
this though I
> know it
> was discussed but not sure it was truly
implemented.
>
> Jeff Pitsch
> Microsoft MVP - Terminal Server
> Citrix Technology Professional
> Provision Networks VIP
>
> Forums not enough?
> Get support from the experts at your business
> http://jeffpitschconsulting.com
>
> Ross wrote:
>> I've recently started testing Terminal
Services using Windows
>> Server 2008 Beta 3, and I've noticed that
using the command
>> mstsc.exe /console does not, in fact, provide
a console
>> connection.
>>
>> Has this option been removed? Is there any
way to obtain this
>> functionality using Windows Server 2008?
>>
>> Thanks.
Top
From: Soo Kuan Teo [MSFT]
<sookuant@online.microsoft.com>
To:
none
Subject:
Re: /console option doesn't seem to exist with Windows Server
2008
Date:
09/30/2007 10:56:52
There's a blog about /console you may find it
informative:
http://blogs.msdn.com/ts/archive/2006/11/27/console-behavior-differences-in-longhorn-server-terminal-services.aspx
Thanks
Soo Kuan
--
This posting is provided "AS IS" with no
warranties, and confers no rights.
"Vera Noest [MVP]" wrote in message
news:Xns99B6D262F383Fveranoesthemutforsse@207.46.248.16...
> That's correct, no /console connections in 2008
anymore.
> Session 0 still exists, but it hosts only
services and is not an
> interactive session anymore.
>
> Explained in detail here:
>
> Console Behavior Differences in Longhorn Server
Terminal Services
> http://blogs.msdn.com/ts/archive/2006/11/27/console-behavior-
>
differences-in-longhorn-server-terminal-services.aspx
>
>
_________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private
email ___
>
> Jeff Pitsch wrote on 25 sep 2007
> in microsoft.public.windows.terminal_services:
>
>> If I remember correctly, MS has done away
with a classic console
>> connection. All sessions are now treated the
same. Are you not
>> able to
>> do something while connected? I may be wrong
on this though I
>> know it
>> was discussed but not sure it was truly
implemented.
>>
>> Jeff Pitsch
>> Microsoft MVP - Terminal Server
>> Citrix Technology Professional
>> Provision Networks VIP
>>
>> Forums not enough?
>> Get support from the experts at your business
>> http://jeffpitschconsulting.com
>>
>> Ross wrote:
>>> I've recently started testing Terminal
Services using Windows
>>> Server 2008 Beta 3, and I've noticed that
using the command
>>> mstsc.exe /console does not, in fact,
provide a console
>>> connection.
>>>
>>> Has this option been removed? Is there
any way to obtain this
>>> functionality using Windows Server 2008?
>>>
>>> Thanks.
Top
From: Vera Noest [MVP]
<vera.noest@remove-this.hem.utfors.se>
To:
none
Subject:
Re: /console option doesn't seem to exist with Windows Server
2008
Date:
09/30/2007 15:11:27
Eeeh, that's the link that I already provided :-)
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email
___
"Soo Kuan Teo [MSFT]" wrote on 30
sep 2007 in
microsoft.public.windows.terminal_services:
> There's a blog about /console you may find it
informative:
> http://blogs.msdn.com/ts/archive/2006/11/27/console-behavior-diff
> erences-in-longhorn-server-terminal-services.aspx
>
> Thanks
> Soo Kuan
>
> "Vera Noest [MVP]"
> wrote in message
news:Xns99B6D262F383Fveranoesthemutforsse@
> 207.46.248.16...
>> That's correct, no /console connections in
2008 anymore.
>> Session 0 still exists, but it hosts only
services and is not an
>> interactive session anymore.
>>
>> Explained in detail here:
>>
>> Console Behavior Differences in Longhorn
Server Terminal
>> Services
>>
http://blogs.msdn.com/ts/archive/2006/11/27/console-behavior-
>>
differences-in-longhorn-server-terminal-services.aspx
Top
From: Soo Kuan Teo [MSFT]
<sookuant@online.microsoft.com>
To:
none
Subject:
Re: /console option doesn't seem to exist with Windows Server
2008
Date:
10/01/2007 11:06:39
Yes! my mistake.
Thanks for point out Vera.
--
This posting is provided "AS IS" with no
warranties, and confers no rights.
"Vera Noest [MVP]" wrote in message
news:Xns99BBE1BCDF3F3veranoesthemutforsse@207.46.248.16...
> Eeeh, that's the link that I already provided :-)
>
_________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private
email ___
>
> "Soo Kuan Teo [MSFT]" wrote on 30
> sep 2007 in
microsoft.public.windows.terminal_services:
>
>> There's a blog about /console you may find it
informative:
>>
http://blogs.msdn.com/ts/archive/2006/11/27/console-behavior-diff
>>
erences-in-longhorn-server-terminal-services.aspx
>>
>> Thanks
>> Soo Kuan
>>
>> "Vera Noest [MVP]"
>> wrote in message
news:Xns99B6D262F383Fveranoesthemutforsse@
>> 207.46.248.16...
>>> That's correct, no /console connections
in 2008 anymore.
>>> Session 0 still exists, but it hosts only
services and is not an
>>> interactive session anymore.
>>>
>>> Explained in detail here:
>>>
>>> Console Behavior Differences in Longhorn
Server Terminal
>>> Services
>>>
http://blogs.msdn.com/ts/archive/2006/11/27/console-behavior-
>>>
differences-in-longhorn-server-terminal-services.aspx
Top
From: Paul <Paul@discussions.microsoft.com>
To:
none
Subject:
RE: !!! Oracle Reports rwrbe60.exe on Windows 2003 R2 x64 !!!
Date:
09/25/2007 12:14:02
Same problem here. Did you ever come up with a work
around?
"Jerry Alan Braga" wrote:
> We are a Windows 2003 TS shop and we are testing
a new dl380 g5 server
> running windows 2003 x64 R2.
>
> We have our own applications that are based on
Oracle Forms / Reports 6i.
> They work fine on Windows 2003 x32 but on x64 the
reports background engine
> that is used to run all reports that are launched
from forms starts up fine
> but does nothing after. It does not connect to
the database and the logging
> pane show nothing not even errors that are forced
that do display when in
> x32 mode.
>
> I know that when the background engine starts it
talks to windows printer
> drivers at the start in order to set the printing
env. Could it be that it
> cannot talk to the x64 printer drivers ? I have
tried creating a generic
> text only printer on the terminal server and set
that as the default with no
> luck.
>
> Does anyone have any ideas on how and where I can
look into this ? Any
> ideas how to diagnose this ?
>
> What I have tried.
>
> running rwrbe60.exe in compatibility mode
> set the dep for the rwrbe60.exe
>
> thanks in advance
>
>
>
Top
From: Munindra Das [MSFT]
<munind@online.microsoft.com>
To:
none
Subject:
Re: !!! Oracle Reports rwrbe60.exe on Windows 2003 R2 x64 !!!
Date:
09/27/2007 13:25:47
Does it happen only inside a TS session or on the
local console as well? If
it is inside a TS session only, are you using any
redirected printers
(printers that are on the client). Do you see any
errors in the event log?
You might also want to try the Oracle forum
(http://forums.oracle.com/).
--
This posting is provided "AS IS" with no
warranties, and confers no rights.
"Paul" wrote in message
news:A8F5AE25-0F6C-4217-90E9-FD103626EBDF@microsoft.com...
> Same problem here. Did you ever come up with a
work around?
>
> "Jerry Alan Braga" wrote:
>
>> We are a Windows 2003 TS shop and we are
testing a new dl380 g5 server
>> running windows 2003 x64 R2.
>>
>> We have our own applications that are based
on Oracle Forms / Reports 6i.
>> They work fine on Windows 2003 x32 but on x64
the reports background
>> engine
>> that is used to run all reports that are
launched from forms starts up
>> fine
>> but does nothing after. It does not connect
to the database and the
>> logging
>> pane show nothing not even errors that are
forced that do display when in
>> x32 mode.
>>
>> I know that when the background engine starts
it talks to windows printer
>> drivers at the start in order to set the
printing env. Could it be that
>> it
>> cannot talk to the x64 printer drivers ? I
have tried creating a generic
>> text only printer on the terminal server and
set that as the default with
>> no
>> luck.
>>
>> Does anyone have any ideas on how and where I
can look into this ? Any
>> ideas how to diagnose this ?
>>
>> What I have tried.
>>
>> running rwrbe60.exe in compatibility mode
>> set the dep for the rwrbe60.exe
>>
>> thanks in advance
>>
>>
>>
Top
From: Paul
<Paul@discussions.microsoft.com>
To:
none
Subject:
Re: !!! Oracle Reports rwrbe60.exe on Windows 2003 R2 x64 !!!
Date:
09/27/2007 13:40:00
It happens local or via a TS session. I've also tried
printing the reports
local to a client. They work perfect with a 32 bit pc.
When I try and print
them on xp 64 bit, same exact issue. I've been
searching around the web. It
appears this is a problem everyone is seeing on x64
with Oracle Reports 6i.
The issue occurs between the splwow64 thunking spooler
and the rwrbe60
process. The rwrbe60 process uses print drivers (of
you default printer) to
generate the report. The splwow64 thunker spooler
translates 64bit printer
drivers to 32bit application. For what ever reason,
this system does not
work correctly. It just goes off into la la land.
With the tons of people out there still running forms
and reports 6i, I
would think MS and/or Oracle would put out a fix for
this. I don't see any
as of yet.
Any additional help is greatly appreciated.
Thanks,
Paul
"Munindra Das [MSFT]" wrote:
> Does it happen only inside a TS session or on the
local console as well? If
> it is inside a TS session only, are you using any
redirected printers
> (printers that are on the client). Do you see any
errors in the event log?
>
> You might also want to try the Oracle forum
(http://forums.oracle.com/).
>
> --
> This posting is provided "AS IS" with
no warranties, and confers no rights.
> "Paul" wrote in message
>
news:A8F5AE25-0F6C-4217-90E9-FD103626EBDF@microsoft.com...
> > Same problem here. Did you ever come up with
a work around?
> >
> > "Jerry Alan Braga" wrote:
> >
> >> We are a Windows 2003 TS shop and we are
testing a new dl380 g5 server
> >> running windows 2003 x64 R2.
> >>
> >> We have our own applications that are
based on Oracle Forms / Reports 6i.
> >> They work fine on Windows 2003 x32 but
on x64 the reports background
> >> engine
> >> that is used to run all reports that are
launched from forms starts up
> >> fine
> >> but does nothing after. It does not
connect to the database and the
> >> logging
> >> pane show nothing not even errors that
are forced that do display when in
> >> x32 mode.
> >>
> >> I know that when the background engine
starts it talks to windows printer
> >> drivers at the start in order to set the
printing env. Could it be that
> >> it
> >> cannot talk to the x64 printer drivers ?
I have tried creating a generic
> >> text only printer on the terminal server
and set that as the default with
> >> no
> >> luck.
> >>
> >> Does anyone have any ideas on how and
where I can look into this ? Any
> >> ideas how to diagnose this ?
> >>
> >> What I have tried.
> >>
> >> running rwrbe60.exe in compatibility
mode
> >> set the dep for the rwrbe60.exe
> >>
> >> thanks in advance
> >>
> >>
> >>
>
>
Top
Post your
questions, comments, feedbacks and suggestions
|
