Home | Site Map | Cisco How To |  Net How To | Windows Vista | Case Studies | Forums | Services | Donations | Careers | About Us | Contact Us|

Terminal services 0703 RE: problem with Licenses in Win2000 TS Server and PocketPC Re: Printing to a MAC Connected Printer via TS Session Re: Printer Redirection Re: Printer Compatability RE: Prevent Power Users from rebooting terminal server Re: policy Re: Outlook web access Re: Office Licensing Re: Office 2000 install  on terminal server Windows Enterprise ser RE: Non-Roaming mandatory profiles Re: New 2003 Installation with RDP Printing Problems Re: Multihomed Terminal Server Re: More than Two Admins (THANKS!) Re: More than Two Admins From: v-kzhao@online.microsoft.com (Ken Zhao [MSFT]) To: none Subject: RE: problem with Licenses in Win2000 TS Server and PocketPC Date: 09/26/2007 21:07:51 Hello Fran, Thank you for using newsgroup! From your post, I'd like to provide you with the following suggestions for your reference: 1. Install TS CALs From my understanding of the problem, this problem only occurs when the clients are using temporary licenses. Try installing some permanent licenses to test this. 2. Hotfix 827355 Install this on the TS Licensing machine. 827355: Event ID 1004 is logged when a thin client tries to obtain a Terminal Services license http://support.microsoft.com/?id=827355 Workaround: Access the registry and delete the following line on your PPC 2003. HKLM\Software\Microsoft\MSLicensing\Store\LICENSE000 This should resolve the problem, but only for the next login. Please understand that Windows Mobile and PocketPC are out of our support boundary. Regarding questions related to Windows Mobile and PocketPC, we invite you to post to the public newsgroup for peer experience and recommendations. You may leverage the peer assistance in the public newsgroups at: microsoft.public.pocketpc You can find these newsgroups by connecting your news reader to Publicnews.Microsoft.com. For more information, see: Q171164 OLEXP: How to Configure Outlook Express for Internet http://support.microsoft.com/?id=171164 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. -------------------- | Reply-To: "Fran Vázquez" | From: "Fran Vázquez" | Subject: problem with Licenses in Win2000 TS Server and PocketPC | Date: Wed, 26 Sep 2007 12:49:28 +0200 | Lines: 33 | X-Priority: 3 | X-MSMail-Priority: Normal | X-Newsreader: Microsoft Outlook Express 6.00.2900.2180 | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 | X-RFC2646: Format=Flowed; Original | Message-ID: | Newsgroups: microsoft.public.windows.terminal_services | NNTP-Posting-Host: router.gelos.es 212.9.66.214 | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.terminal_services:11266 | X-Tomcat-NG: microsoft.public.windows.terminal_services | | Hi, | | | We have a Win2000 Std TS (application mode per device) that has 5 licenses | installed. We've 3 mobile devices (Pocket PC) that connect to this TS | without any problem. | | However suddenly one of the devices stopped working, it cannot connect to | the TS. What we've noticed is that: | | -Event ID 1004 'The terminal server cannot issue a client license.' appears | every time it tries to connect | -In TS manager, the connection appears as 'connectquery' when this device | tries to connect and then it disappears (the device cannot connect) | -In our Licensing server, we still have 2 available licenses that has not | been granted to any device | -If we delete the 'licensing registry keys' in our mobile device registry, | the first time it tries to connect the connection is OK! But the 2nd time it | cannot connect. And so on... | | Our license server is located in another server, and the TS Server has the | correct registry key so it can locate it (and it can locate it via Netbios). | | | We were thinking about reactivating the TS server, but since we have 2 free | licenses we're not sure that this will be a solution.. what can we do? | | | Thanks in advance for your answer | | | | | Top From: Fran Vázquez <fvazquez@newsgroup.nospam> To: none Subject: Re: problem with Licenses in Win2000 TS Server and PocketPC Date: 09/27/2007 00:33:52 Hi Ken, Thanks for your answer. Your 1st point is not valid for me, since I see in my license manager that I still have 2 free licenses. Your 2nd point is OK, but this is strange since this PocketPC was connecting to this TS for more than a year ago... Your 3st point have been tested by us, and as you say this only works the 1 st time. This is also strange since I think I should have 90 days of evaluation, but I cannot connect the 2nd time. Regarding your affirmation ' Please understand that Windows Mobile and PocketPC are out of our support boundary. ' I really cannot understand that if PocketPC, that is a Microsoft product, has a client for connecting to a Windows Terminal Services (that is also a Microsoft Product), this configuration may be 'out of support'!!!! This sounds very weird to me. Sincerely, I cannot accept that. I'll contact MS Support Services, since this is clearly a bug of a Microsoft product (Pocket PC or TS, I dont care) Thanks for your answer Fran. ""Ken Zhao [MSFT]"" escribió en el mensaje news:OzZQMtKAIHA.4200@TK2MSFTNGHUB02.phx.gbl... > Hello Fran, > > Thank you for using newsgroup! > > From your post, I'd like to provide you with the following suggestions for > your reference: > > 1. Install TS CALs > From my understanding of the problem, this problem only occurs when the > clients are using temporary licenses. Try installing some permanent > licenses to test this. > > 2. Hotfix 827355 > Install this on the TS Licensing machine. > 827355: Event ID 1004 is logged when a thin client tries to obtain a > Terminal Services license > http://support.microsoft.com/?id=827355 > > Workaround: > Access the registry and delete the following line on your PPC 2003. > HKLM\Software\Microsoft\MSLicensing\Store\LICENSE000 > > This should resolve the problem, but only for the next login. > > Please understand that Windows Mobile and PocketPC are out of our support > boundary. Regarding questions related to Windows Mobile and PocketPC, we > invite you to post to the public newsgroup for peer experience and > recommendations. > > You may leverage the peer assistance in the public newsgroups at: > microsoft.public.pocketpc > > You can find these newsgroups by connecting your news reader to > Publicnews.Microsoft.com. For more information, see: > > Q171164 OLEXP: How to Configure Outlook Express for Internet > http://support.microsoft.com/?id=171164 > > 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. > > > > > > -------------------- > | Reply-To: "Fran Vázquez" > | From: "Fran Vázquez" > | Subject: problem with Licenses in Win2000 TS Server and PocketPC > | Date: Wed, 26 Sep 2007 12:49:28 +0200 > | Lines: 33 > | X-Priority: 3 > | X-MSMail-Priority: Normal > | X-Newsreader: Microsoft Outlook Express 6.00.2900.2180 > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 > | X-RFC2646: Format=Flowed; Original > | Message-ID: > | Newsgroups: microsoft.public.windows.terminal_services > | NNTP-Posting-Host: router.gelos.es 212.9.66.214 > | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl > | Xref: TK2MSFTNGHUB02.phx.gbl > microsoft.public.windows.terminal_services:11266 > | X-Tomcat-NG: microsoft.public.windows.terminal_services > | > | Hi, > | > | > | We have a Win2000 Std TS (application mode per device) that has 5 > licenses > | installed. We've 3 mobile devices (Pocket PC) that connect to this TS > | without any problem. > | > | However suddenly one of the devices stopped working, it cannot connect > to > | the TS. What we've noticed is that: > | > | -Event ID 1004 'The terminal server cannot issue a client license.' > appears > | every time it tries to connect > | -In TS manager, the connection appears as 'connectquery' when this > device > | tries to connect and then it disappears (the device cannot connect) > | -In our Licensing server, we still have 2 available licenses that has > not > | been granted to any device > | -If we delete the 'licensing registry keys' in our mobile device > registry, > | the first time it tries to connect the connection is OK! But the 2nd > time > it > | cannot connect. And so on... > | > | Our license server is located in another server, and the TS Server has > the > | correct registry key so it can locate it (and it can locate it via > Netbios). > | > | > | We were thinking about reactivating the TS server, but since we have 2 > free > | licenses we're not sure that this will be a solution.. what can we do? > | > | > | Thanks in advance for your answer > | > | > | > | > | > Top From: v-kzhao@online.microsoft.com (Ken Zhao [MSFT]) To: none Subject: Re: problem with Licenses in Win2000 TS Server and PocketPC Date: 10/01/2007 01:41:28 Hi Fran, Thanks for your response and if you have any results, please feel free to let us know. Please understand we do not support it since our mobility support is targeted at server side sync in our managed newsgroup. If you have any questions about PocketPC, I suggest you post your question on the Microsoft public newsgroups (Microsoft.public.pocketpc) where other users may have already experienced this issue. Thanks for your understanding. 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. -------------------- | Reply-To: "Fran Vázquez" | From: "Fran Vázquez" | References: | Subject: Re: problem with Licenses in Win2000 TS Server and PocketPC | Date: Thu, 27 Sep 2007 07:33:52 +0200 | Lines: 158 | X-Priority: 3 | X-MSMail-Priority: Normal | X-Newsreader: Microsoft Outlook Express 6.00.2900.2180 | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 | X-RFC2646: Format=Flowed; Original | Message-ID: | Newsgroups: microsoft.public.windows.terminal_services | NNTP-Posting-Host: router.gelos.es 212.9.66.214 | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.terminal_services:11311 | X-Tomcat-NG: microsoft.public.windows.terminal_services | | Hi Ken, | | | Thanks for your answer. | | Your 1st point is not valid for me, since I see in my license manager that I | still have 2 free licenses. | Your 2nd point is OK, but this is strange since this PocketPC was connecting | to this TS for more than a year ago... | Your 3st point have been tested by us, and as you say this only works the 1 | st time. This is also strange since I think I should have 90 days of | evaluation, but I cannot connect the 2nd time. | | Regarding your affirmation ' Please understand that Windows Mobile and | PocketPC are out of our support boundary. ' I really cannot understand that | if PocketPC, that is a Microsoft product, has a client for connecting to a | Windows Terminal Services (that is also a Microsoft Product), this | configuration may be 'out of support'!!!! This sounds very weird to me. | Sincerely, I cannot accept that. | | I'll contact MS Support Services, since this is clearly a bug of a Microsoft | product (Pocket PC or TS, I dont care) | | | Thanks for your answer | | | Fran. | | | | ""Ken Zhao [MSFT]"" escribi?en el mensaje | news:OzZQMtKAIHA.4200@TK2MSFTNGHUB02.phx.gbl... | > Hello Fran, | > | > Thank you for using newsgroup! | > | > From your post, I'd like to provide you with the following suggestions for | > your reference: | > | > 1. Install TS CALs | > From my understanding of the problem, this problem only occurs when the | > clients are using temporary licenses. Try installing some permanent | > licenses to test this. | > | > 2. Hotfix 827355 | > Install this on the TS Licensing machine. | > 827355: Event ID 1004 is logged when a thin client tries to obtain a | > Terminal Services license | > http://support.microsoft.com/?id=827355 | > | > Workaround: | > Access the registry and delete the following line on your PPC 2003. | > HKLM\Software\Microsoft\MSLicensing\Store\LICENSE000 | > | > This should resolve the problem, but only for the next login. | > | > Please understand that Windows Mobile and PocketPC are out of our support | > boundary. Regarding questions related to Windows Mobile and PocketPC, we | > invite you to post to the public newsgroup for peer experience and | > recommendations. | > | > You may leverage the peer assistance in the public newsgroups at: | > microsoft.public.pocketpc | > | > You can find these newsgroups by connecting your news reader to | > Publicnews.Microsoft.com. For more information, see: | > | > Q171164 OLEXP: How to Configure Outlook Express for Internet | > http://support.microsoft.com/?id=171164 | > | > 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. | > | > | > | > | > | > -------------------- | > | Reply-To: "Fran Vázquez" | > | From: "Fran Vázquez" | > | Subject: problem with Licenses in Win2000 TS Server and PocketPC | > | Date: Wed, 26 Sep 2007 12:49:28 +0200 | > | Lines: 33 | > | X-Priority: 3 | > | X-MSMail-Priority: Normal | > | X-Newsreader: Microsoft Outlook Express 6.00.2900.2180 | > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 | > | X-RFC2646: Format=Flowed; Original | > | Message-ID: | > | Newsgroups: microsoft.public.windows.terminal_services | > | NNTP-Posting-Host: router.gelos.es 212.9.66.214 | > | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl | > | Xref: TK2MSFTNGHUB02.phx.gbl | > microsoft.public.windows.terminal_services:11266 | > | X-Tomcat-NG: microsoft.public.windows.terminal_services | > | | > | Hi, | > | | > | | > | We have a Win2000 Std TS (application mode per device) that has 5 | > licenses | > | installed. We've 3 mobile devices (Pocket PC) that connect to this TS | > | without any problem. | > | | > | However suddenly one of the devices stopped working, it cannot connect | > to | > | the TS. What we've noticed is that: | > | | > | -Event ID 1004 'The terminal server cannot issue a client license.' | > appears | > | every time it tries to connect | > | -In TS manager, the connection appears as 'connectquery' when this | > device | > | tries to connect and then it disappears (the device cannot connect) | > | -In our Licensing server, we still have 2 available licenses that has | > not | > | been granted to any device | > | -If we delete the 'licensing registry keys' in our mobile device | > registry, | > | the first time it tries to connect the connection is OK! But the 2nd | > time | > it | > | cannot connect. And so on... | > | | > | Our license server is located in another server, and the TS Server has | > the | > | correct registry key so it can locate it (and it can locate it via | > Netbios). | > | | > | | > | We were thinking about reactivating the TS server, but since we have 2 | > free | > | licenses we're not sure that this will be a solution.. what can we do? | > | | > | | > | Thanks in advance for your answer | > | | > | | > | | > | | > | | > | | | Top From: Vera Noest [MVP] <vera.noest@remove-this.hem.utfors.se> To: none Subject: Re: Printing to a MAC Connected Printer via TS Session Date: 09/21/2007 14:08:41 Which version of MacRDC is she using? The current version is 1.0.3, and with that version, you *must* use a PostScript driver. Many Mac users have installed the beta version of the Mac RDC 2.0 client, which doesn't have this requirement any more. You might want to post in the mac rdc newsgroup for more help: microsoft.public.mac.rdc _________________________________________________________ Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server TS troubleshooting: http://ts.veranoest.net ___ please respond in newsgroup, NOT by private email ___ "David G. Hoch" wrote on 21 sep 2007 in microsoft.public.windows.terminal_services: > I have a user that is connecting from her MAC (using the RDP > software for MAC) to a Terminal Server 2003 box. She wants to > be able to print to her locally attached printer. I've loaded > the Server 2003 drivers for the printer on the server, but when > she connects to the server it does not automatically recongnize > her printer and make it available. This works for clients using > PC's to launch their remote session. Is this something that can > work in a MAC RDP Session, or is that incompatible? > > Thanks for your help. > --David Top From: David G. Hoch <dhoch@dghtechnologies.com> To: none Subject: Re: Printing to a MAC Connected Printer via TS Session Date: 09/21/2007 14:56:15 Thanks. I'll have to find out which version of the RDC, but it was downloaded from the Microsoft website within the last 4 months. I know I did not load a Post Script driver so I'll change that. I will post on the other group. Thanks again. --David "Vera Noest [MVP]" wrote in message news:Xns99B2D718B6AD9veranoesthemutforsse@207.46.248.16... > Which version of MacRDC is she using? > The current version is 1.0.3, and with that version, you *must* use a > PostScript driver. > > Many Mac users have installed the beta version of the Mac RDC 2.0 > client, which doesn't have this requirement any more. > > You might want to post in the mac rdc newsgroup for more help: > microsoft.public.mac.rdc > _________________________________________________________ > Vera Noest > MCSE, CCEA, Microsoft MVP - Terminal Server > TS troubleshooting: http://ts.veranoest.net > ___ please respond in newsgroup, NOT by private email ___ > > "David G. Hoch" wrote on 21 sep 2007 > in microsoft.public.windows.terminal_services: > >> I have a user that is connecting from her MAC (using the RDP >> software for MAC) to a Terminal Server 2003 box. She wants to >> be able to print to her locally attached printer. I've loaded >> the Server 2003 drivers for the printer on the server, but when >> she connects to the server it does not automatically recongnize >> her printer and make it available. This works for clients using >> PC's to launch their remote session. Is this something that can >> work in a MAC RDP Session, or is that incompatible? >> >> Thanks for your help. >> --David Top From: Vera Noest [MVP] <vera.noest@remove-this.hem.utfors.se> To: none Subject: Re: Printer Redirection Date: 09/20/2007 14:19:25 Check the configuration of printer redirection in the RDP client, update the RDP client to at least the XP SP2 version or apply KB article 302361 to get support for redirection of non-standard local port names. 302361 - Printers That Use Ports That Do Not Begin With COM, LPT, or USB Are Not Redirected in a Remote Desktop or Terminal Services Session http://support.microsoft.com/?kbid=302361 _________________________________________________________ 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?R29sZm9yZm9vZA==?= wrote on 20 sep 2007 in microsoft.public.windows.terminal_services: > I am running Terminal Services on Windows Server 2003 R2. I > have 3 users who are using Remote Desktop to login to Terminal > Service. All three users and coming in from different locations > and they all have the same printer an HP Laserjet P3005 plugged > into their local computer. For 2 of the users there printers > are redirecting no problem. The third person's printer is > working locally but not when she logs into Terminal Services. > When she logs in her printer does not even show up. Is there > something else I should check on her local computer? What port > should her computer be loaded on her local computer. She also > has other printers plugged into her local computer. Would this > cause any problems. > > Thanks for your help Top From: Jeff Pitsch <Jeff@Jeffpitschconsulting.com> To: none Subject: Re: Printer Compatability Date: 09/25/2007 10:03:17 There is no way I'd install drivers for a photo printer on a terminal services. It would most likely be a noncompatible driver and cause stability issues. Your lucky there is no driver. you can try the fallback drivers or this article for compatibility: http://support.microsoft.com/?kbid=239088 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 Andrew Mallette wrote: > am i correct in assuming that if there are no server drivers for a > printer it can not be supported in windows terminal server 2003. The hp > printer i need to install drivers for is a hp photosmart 3310 which only > offers drivers for windows xp and vista. Top From: Andrew Mallette <andrewm270@aol.com> To: none Subject: Re: Printer Compatability Date: 09/25/2007 18:57:25 That is almost good news, As long as i can tell the user truthfully, my concious is clear. Jeff Pitsch wrote: > There is no way I'd install drivers for a photo printer on a terminal > services. It would most likely be a noncompatible driver and cause > stability issues. Your lucky there is no driver. you can try the > fallback drivers or this article for compatibility: > http://support.microsoft.com/?kbid=239088 > > 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 > > Andrew Mallette wrote: > >> am i correct in assuming that if there are no server drivers for a >> printer it can not be supported in windows terminal server 2003. The >> hp printer i need to install drivers for is a hp photosmart 3310 which >> only offers drivers for windows xp and vista. Top From: TP <tperson.knowspamn@mailandnews.com> To: none Subject: Re: Printer Compatability Date: 09/25/2007 14:34:17 Hi, If I am reading HP's chart correctly then your printer is not supported under Terminal Services: HP printers supported in Citrix Presentation Server environments - July 2007 http://h71028.www7.hp.com/ERC/downloads/4AA0-8465ENW.pdf -TP Andrew Mallette wrote: > am i correct in assuming that if there are no server drivers for a > printer it can not be supported in windows terminal server 2003. The > hp printer i need to install drivers for is a hp photosmart 3310 > which only offers drivers for windows xp and vista. Top From: Lanwench [MVP - Exchange] <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> To: none Subject: Re: Prevent Power Users from rebooting terminal server Date: 09/21/2007 09:35:12 Brian wrote: > Windows 2003 TS. > Has QuickBooks on it, which requires Power Users membership in order > to function correctly (well, maybe not, but that is what Intuit > claims, Yes, sigh. > and it is likely easier to get an answer to my question here > than get any info the actual rights required from Intuit Have you tried? > - it's much > easier for them just to say the user must be a member of Power Users > in order to run QB). Correct, but a) you should still holler at them - it's sloppy code and b) you may be able to work around it anyway. http://msmvps.com/blogs/bradley/archive/2005/04/23/how-to-run-quickbooks-under-user-mode.aspx ...and a lot of Google hits. Much depends on your version of Quickbooks, which you haven't mentioned.... http://www.google.com/search?hl=en? > > So...I need to prevent Power Users from rebooting the server. > > How? Group policy or local policy - but honestly, this is only one of *myriad* Bad Things a power user could inadvertently (or advertently) do, and you'll always be chasing your tail here. A power user is pretty nearly a full-fledged administrator. Since this is a TS box and not someone's individual workstation, you're running with scissors if you give them more rights than they should have. Another tool that may help you - Process Monitor from Sysinternals (now MS) http://www.microsoft.com/technet/sysinternals/utilities/processmonitor.mspx Top From: TP <tperson.knowspamn@mailandnews.com> To: none Subject: Re: Prevent Power Users from rebooting terminal server Date: 09/21/2007 10:00:11 Hi, Please take a look at the instructions Vera has on her site. If you are unable to get it working with those, let me know. You do *not* need to make normal users a member of the Power Users group in order to run QuickBooks. http://ts.veranoest.net/ts_apps_qb.htm I use a different technique that is more complicated which uses per-user class registration entries. -TP Brian wrote: > Windows 2003 TS. > Has QuickBooks on it, which requires Power Users membership in order > to function correctly (well, maybe not, but that is what Intuit > claims, and it is likely easier to get an answer to my question here > than get any info the actual rights required from Intuit - it's much > easier for them just to say the user must be a member of Power Users > in order to run QB). > > So...I need to prevent Power Users from rebooting the server. > > How? Top From: ThomasT. <ThomasT@nospam.nospam> To: none Subject: Re: Prevent Power Users from rebooting terminal server Date: 09/21/2007 10:09:12 ? Hi, I didn't know that Vera is a woman :-) , I was thinking she was a guy, that's cool, there are not too much woman high tech like her (in public forums or on the web) . Have a nice weekend all Thomas "TP" <tperson.knowspamn@mailandnews.com> wrote in message news:OzAnf$F$HHA.3780@TK2MSFTNGP06.phx.gbl... Hi, Please take a look at the instructions Vera has on her site.  If you are unable to get it working with those, let me know. You do *not* need to make normal users a member of the Power Users group in order to run QuickBooks. http://ts.veranoest.net/ts_apps_qb.htm I use a different technique that is more complicated which uses per-user class registration entries. -TP Brian wrote: > Windows 2003 TS. > Has QuickBooks on it, which requires Power Users membership in order > to function correctly (well, maybe not, but that is what Intuit > claims, and it is likely easier to get an answer to my question here > than get any info the actual rights required from Intuit - it's much > easier for them just to say the user must be a member of Power Users > in order to run QB). > > So...I need to prevent Power Users from rebooting the server. > > How? Top From: Vera Noest [MVP] <vera.noest@remove-this.hem.utfors.se> To: none Subject: Re: Prevent Power Users from rebooting terminal server Date: 09/21/2007 13:49:06 LOL! _________________________________________________________ Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server TS troubleshooting: http://ts.veranoest.net ___ please respond in newsgroup, NOT by private email ___ "ThomasT." wrote on 21 sep 2007 in microsoft.public.windows.terminal_services: > Hi, > > I didn't know that Vera is a woman :-) , I was thinking she was > a guy, that's cool, there are not too much woman high tech like > her (in public forums or on the web) . > > Have a nice weekend all > > Thomas > "TP" wrote in message > news:OzAnf$F$HHA.3780@TK2MSFTNGP06.phx.gbl... Hi, > > Please take a look at the instructions Vera has on her site. > If you are unable to get it working with those, let me know. > > You do *not* need to make normal users a member of the > Power Users group in order to run QuickBooks. > > http://ts.veranoest.net/ts_apps_qb.htm > > I use a different technique that is more complicated which > uses per-user class registration entries. > > -TP > > Brian wrote: > > Windows 2003 TS. > > Has QuickBooks on it, which requires Power Users membership > > in order to function correctly (well, maybe not, but that is > > what Intuit claims, and it is likely easier to get an answer > > to my question here than get any info the actual rights > > required from Intuit - it's much easier for them just to say > > the user must be a member of Power Users in order to run QB). > > > > So...I need to prevent Power Users from rebooting the server. > > > > How? Top From: Johan Strange <JohanStrange@discussions.microsoft.com> To: none Subject: RE: Prevent Power Users from rebooting terminal server Date: 09/21/2007 12:38:01 If you put the TS in its own OU then create a GPO linked to this OU. Then on the GPO go to Computer Settings / Windows Settings / Local Policies / User Rights Assignment and then under "Shut down the System" Enter the account for Domain\Administrator or any other Admin user that you would like to have these rights. This will prevent users accidentially shutting the Server down. I do this as part of a standard TS lockdown strategy. "Brian" wrote: > Windows 2003 TS. > Has QuickBooks on it, which requires Power Users membership in order to > function correctly (well, maybe not, but that is what Intuit claims, and it > is likely easier to get an answer to my question here than get any info the > actual rights required from Intuit - it's much easier for them just to say > the user must be a member of Power Users in order to run QB). > > So...I need to prevent Power Users from rebooting the server. > > How? Top From: Patrick Rouse <PatrickRouse@discussions.microsoft.com> To: none Subject: RE: Prevent Power Users from rebooting terminal server Date: 09/23/2007 13:52:00 What we usually do is remove Domain Admins from the local administrators group, and add a different group that is responsible for maintaining the Terminal Servers. Users should NEVER be members of the Power Users or Administrators groups, as there is always a way to tweak certain registry or file system permissions to accomodate a specific application. -- Patrick C. Rouse Microsoft MVP - Terminal Server Provision Networks VIP Citrix Technology Professional President - Session Computing Solutions, LLC http://www.sessioncomputing.com "Johan Strange" wrote: > If you put the TS in its own OU then create a GPO linked to this OU. Then on > the GPO go to Computer Settings / Windows Settings / Local Policies / User > Rights Assignment and then under "Shut down the System" Enter the account for > Domain\Administrator or any other Admin user that you would like to have > these rights. This will prevent users accidentially shutting the Server down. > > I do this as part of a standard TS lockdown strategy. > > > "Brian" wrote: > > > Windows 2003 TS. > > Has QuickBooks on it, which requires Power Users membership in order to > > function correctly (well, maybe not, but that is what Intuit claims, and it > > is likely easier to get an answer to my question here than get any info the > > actual rights required from Intuit - it's much easier for them just to say > > the user must be a member of Power Users in order to run QB). > > > > So...I need to prevent Power Users from rebooting the server. > > > > How? Top From: Munindra Das [MSFT] <munind@online.microsoft.com> To: none Subject: Re: policy Date: 09/28/2007 13:04:37 Do you mean the connection bar on top of the TS Window? Unfortunately there is no policy to fade out the connection bar today. -- This posting is provided "AS IS" with no warranties, and confers no rights. "mark walser" wrote in message news:%23Sz4%23YBAIHA.4496@TK2MSFTNGP06.phx.gbl... > hello ng > > how I can fade out the yellow bar on top of the screen with policies? > > thanks > Top From: Munindra Das [MSFT] <munind@online.microsoft.com> To: none Subject: Re: Outlook web access Date: 09/22/2007 02:00:21 Does it happen only inside a TS session and not on a local session? If yes, please forward your post to either IE or OWA newsgroups. -- This posting is provided "AS IS" with no warranties, and confers no rights. "Andrew Story" wrote in message news:%231uWHs3%23HHA.5404@TK2MSFTNGP02.phx.gbl... > Hello NG, > > I have a win2k TS which is used for a financial application. I need to > have the users who logon using Outlook web access. When 'some' users open > OWA IE just closes on it's own! > > Anyone seen this before? It's not profile related as I have recreated > some of the user ones with this problem but does not work. > Top From: Andrew Story <andrewDOTstoryATjameswalkerDOTbiz> To: none Subject: Re: Outlook web access Date: 09/24/2007 03:27:25 Hi, yes it is only in a TS session. We use appsec, could this be casuing it? "Munindra Das [MSFT]" wrote in message news:%237jJ$YO$HHA.4732@TK2MSFTNGP04.phx.gbl... > Does it happen only inside a TS session and not on a local session? If > yes, please forward your post to either IE or OWA newsgroups. > > -- > This posting is provided "AS IS" with no warranties, and confers no > rights. > "Andrew Story" wrote in message > news:%231uWHs3%23HHA.5404@TK2MSFTNGP02.phx.gbl... >> Hello NG, >> >> I have a win2k TS which is used for a financial application. I need to >> have the users who logon using Outlook web access. When 'some' users >> open OWA IE just closes on it's own! >> >> Anyone seen this before? It's not profile related as I have recreated >> some of the user ones with this problem but does not work. >> > Top From: Munindra Das [MSFT] <munind@online.microsoft.com> To: none Subject: Re: Outlook web access Date: 09/24/2007 12:49:06 What specific controls are you setting using appsec? Are you blocking IE or any specific executable? Can you try disabling it and see if users can open OWA? -- This posting is provided "AS IS" with no warranties, and confers no rights. "Andrew Story" wrote in message news:O3ZL%23So$HHA.536@TK2MSFTNGP06.phx.gbl... > Hi, yes it is only in a TS session. We use appsec, could this be casuing > it? > > > "Munindra Das [MSFT]" wrote in message > news:%237jJ$YO$HHA.4732@TK2MSFTNGP04.phx.gbl... >> Does it happen only inside a TS session and not on a local session? If >> yes, please forward your post to either IE or OWA newsgroups. >> >> -- >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> "Andrew Story" wrote in message >> news:%231uWHs3%23HHA.5404@TK2MSFTNGP02.phx.gbl... >>> Hello NG, >>> >>> I have a win2k TS which is used for a financial application. I need to >>> have the users who logon using Outlook web access. When 'some' users >>> open OWA IE just closes on it's own! >>> >>> Anyone seen this before? It's not profile related as I have recreated >>> some of the user ones with this problem but does not work. >>> >> > > Top From: Andrew Story <andrewDOTstoryATjameswalkerDOTbiz> To: none Subject: Re: Outlook web access Date: 09/25/2007 02:15:18 I disabled appsec and OWA works. IE is set to allow in appsec and I wasn;t aware of OWA using any other executables (that's all you can block in appsec, executables). I think I have found a way around it, disable appsec and the user can use OWA, then enable appsec and the user can still use OWA - strange eh? "Munindra Das [MSFT]" wrote in message news:egNn0Mt$HHA.3916@TK2MSFTNGP02.phx.gbl... > What specific controls are you setting using appsec? Are you blocking IE > or any specific executable? Can you try disabling it and see if users can > open OWA? > > -- > This posting is provided "AS IS" with no warranties, and confers no > rights. > "Andrew Story" wrote in message > news:O3ZL%23So$HHA.536@TK2MSFTNGP06.phx.gbl... >> Hi, yes it is only in a TS session. We use appsec, could this be casuing >> it? >> >> >> "Munindra Das [MSFT]" wrote in message >> news:%237jJ$YO$HHA.4732@TK2MSFTNGP04.phx.gbl... >>> Does it happen only inside a TS session and not on a local session? If >>> yes, please forward your post to either IE or OWA newsgroups. >>> >>> -- >>> This posting is provided "AS IS" with no warranties, and confers no >>> rights. >>> "Andrew Story" wrote in message >>> news:%231uWHs3%23HHA.5404@TK2MSFTNGP02.phx.gbl... >>>> Hello NG, >>>> >>>> I have a win2k TS which is used for a financial application. I need to >>>> have the users who logon using Outlook web access. When 'some' users >>>> open OWA IE just closes on it's own! >>>> >>>> Anyone seen this before? It's not profile related as I have recreated >>>> some of the user ones with this problem but does not work. >>>> >>> >> >> > Top From: Lanwench [MVP - Exchange] <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> To: none Subject: Re: Office Licensing Date: 09/26/2007 11:01:12 APT SA wrote: > Is it possible to have 20 users connecting to a Terminal server and > 10 want office Pro and 10 want office sbe from a licensing > standpoint? And do I have to install both editions or can I just > install Office pro and restrict Access from sbe users? I believe you'll have to install a single copy of Pro, but I doubt restricting users from using Access will be at all useful from a licensing standpoint. For any and all licensing questions, it's always best to call MS or your licensed MS reseller. Top From: Daniel Valach <DanielValach@discussions.microsoft.com> To: none Subject: Re: Office 2000 install  on terminal server Windows Enterprise ser Date: 09/20/2007 21:52:00 I did, without success to follow the instructions, since I did not have the right tech article. I opted for payed support from microsoft, the support guided me trough in 40minutes or so I had the office 2000 installed with service packs etc and running as well as had the appropriate tech article link if I need to reinstall I could not do this every day pay the support but this was worth it, my time etc. Thanks for trying. "TP" wrote: > Hi Daniel, > > What specific questions do you have? > > Have you downloaded and installed the office 2000 resource > kit? > > http://download.microsoft.com/download/6/b/3/6b34f4c7-44e6-4d85-91d9-1acf9479da7d/orktools.exe > > Have you run the Custom Installation Wizard and customized > the TermSrvr.mst transform file? > > Have you followed these instructions: > > How to Install Office Disc 1 on a Windows Terminal Server > > http://office.microsoft.com/en-us/ork2000/HA011379561033.aspx > > -TP > > Daniel Valach wrote: > > I need step by step installation of MS Office premium on Enterprise > > server 2003 terminal server ( remote desktop) > > I have reviewed the info Using office 2000 with window terminal > > serve, but I am unable to follow the details are not 100% clear to me > > this is first time I am trying to install the office on terminal > > server. > > Appreciate help > > Daniel > Top From: TP <tperson.knowspamn@mailandnews.com> To: none Subject: Re: Office 2000 install  on terminal server Windows Enterprise ser Date: 09/21/2007 10:03:06 Hi Daniel, You are welcome. Glad you were able to get it installed. Thanks for letting us know the resolution. -TP Top From: Johan Strange <JohanStrange@discussions.microsoft.com> To: none Subject: RE: Non-Roaming mandatory profiles Date: 09/21/2007 12:44:02 Hi, I often want to apply a strict way of controlling TS users and always manage to do so using Group Policies. This way users can have access to there PC and access to a TS with different restrictions rather than imposing mandatory settings to the user object. "Joseph T Corey" wrote: > Sorry for the cross-post from server.general... > > Has anyone successfully created a terminal server environment where you had > non-roaming mandatory profiles? I'd like to take the idea of a mandatory > profile and apply it to all new local accounts that are created, but for > numerous reasons I can't use roaming or TS roaming profiles. I'd accept a > solution that just deleted the local account at logoff. I've looked at > delprof, but that seems to be better suited as a startup or shutdown script. > Any help is appreciated! > > -- > Joseph T. Corey MCSE, Security+ > Systems Administrator > jcorey@cmu.edu > > Top From: Jeff Pitsch <Jeff@Jeffpitschconsulting.com> To: none Subject: Re: New 2003 Installation with RDP Printing Problems Date: 09/27/2007 14:50:23 Unfortunately i did not find that driver in hp's terminal services compatibility document (http://h71028.www7.hp.com/ERC/downloads/4AA0-8465ENW.pdf). you may want to use printer redirection and map it to a compatible driver: http://support.microsoft.com/?kbid=239088 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 Mark Stoker wrote: > We have just installed a new 2003 R2 terminal server solution in one of our > retail stores. We are using Wyse S30 terminal with HP P2014 printers > attached via the USB connection. I am using the Windows 2003 driver. > > Most of the time the users can print fine but we have seen the following > problems. > > i) If say the printer jams and the user has the intervene the print job > seems the get 'stuck' in the print queue. Re-starting the print spooler > service usally does the job getting it to print. > > ii) Sometimes when the users logs off the instance of the printer is not > removed. Subsequetly when the user logs back in there are 2 instances of the > printer and they cannot print. > > This is our 1st 2003 installation (our other 10 stores all run Windows 2000 > TS) and the printing is letting us down - any thoughts ? > > Mark Top From: Mark Stoker <MarkStoker@discussions.microsoft.com> To: none Subject: Re: New 2003 Installation with RDP Printing Problems Date: 09/28/2007 03:14:00 "Jeff Pitsch" wrote: > Unfortunately i did not find that driver in hp's terminal services > compatibility document > (http://h71028.www7.hp.com/ERC/downloads/4AA0-8465ENW.pdf). you may > want to use printer redirection and map it to a compatible driver: > http://support.microsoft.com/?kbid=239088 > > 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 > > Mark Stoker wrote: > > We have just installed a new 2003 R2 terminal server solution in one of our > > retail stores. We are using Wyse S30 terminal with HP P2014 printers > > attached via the USB connection. I am using the Windows 2003 driver. > > > > Most of the time the users can print fine but we have seen the following > > problems. > > > > i) If say the printer jams and the user has the intervene the print job > > seems the get 'stuck' in the print queue. Re-starting the print spooler > > service usally does the job getting it to print. > > > > ii) Sometimes when the users logs off the instance of the printer is not > > removed. Subsequetly when the user logs back in there are 2 instances of the > > printer and they cannot print. > > > > This is our 1st 2003 installation (our other 10 stores all run Windows 2000 > > TS) and the printing is letting us down - any thoughts ? > > > > Mark > Just for interest, what causes the spooler to hang i.e why are they not compatable ? Top From: Mark Stoker <MarkStoker@discussions.microsoft.com> To: none Subject: Re: New 2003 Installation with RDP Printing Problems Date: 09/28/2007 07:08:00 Looking at the HP document the P2010 Printer is listed. However on the HP web site the P2010 is a 'series' of printers and If you chosse the driver for the P2010 it gives you the P2014 driver ?? "Jeff Pitsch" wrote: > Unfortunately i did not find that driver in hp's terminal services > compatibility document > (http://h71028.www7.hp.com/ERC/downloads/4AA0-8465ENW.pdf). you may > want to use printer redirection and map it to a compatible driver: > http://support.microsoft.com/?kbid=239088 > > 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 > > Mark Stoker wrote: > > We have just installed a new 2003 R2 terminal server solution in one of our > > retail stores. We are using Wyse S30 terminal with HP P2014 printers > > attached via the USB connection. I am using the Windows 2003 driver. > > > > Most of the time the users can print fine but we have seen the following > > problems. > > > > i) If say the printer jams and the user has the intervene the print job > > seems the get 'stuck' in the print queue. Re-starting the print spooler > > service usally does the job getting it to print. > > > > ii) Sometimes when the users logs off the instance of the printer is not > > removed. Subsequetly when the user logs back in there are 2 instances of the > > printer and they cannot print. > > > > This is our 1st 2003 installation (our other 10 stores all run Windows 2000 > > TS) and the printing is letting us down - any thoughts ? > > > > Mark > Top From: Jeff Pitsch <Jeff@Jeffpitschconsulting.com> To: none Subject: Re: New 2003 Installation with RDP Printing Problems Date: 09/28/2007 07:45:01 And of course I may simply have missed it. :) Are you using the correct version of the driver? That can be just as important. Not all print drivers are compatible with terminal services because of the multi-user nature of terminal services. What your experiencing sounds like a classic case of a bad print driver. 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 Mark Stoker wrote: > Looking at the HP document the P2010 Printer is listed. However on the HP web > site the P2010 is a 'series' of printers and If you chosse the driver for the > P2010 it gives you the P2014 driver ?? > > "Jeff Pitsch" wrote: > >> Unfortunately i did not find that driver in hp's terminal services >> compatibility document >> (http://h71028.www7.hp.com/ERC/downloads/4AA0-8465ENW.pdf). you may >> want to use printer redirection and map it to a compatible driver: >> http://support.microsoft.com/?kbid=239088 >> >> 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 >> >> Mark Stoker wrote: >>> We have just installed a new 2003 R2 terminal server solution in one of our >>> retail stores. We are using Wyse S30 terminal with HP P2014 printers >>> attached via the USB connection. I am using the Windows 2003 driver. >>> >>> Most of the time the users can print fine but we have seen the following >>> problems. >>> >>> i) If say the printer jams and the user has the intervene the print job >>> seems the get 'stuck' in the print queue. Re-starting the print spooler >>> service usally does the job getting it to print. >>> >>> ii) Sometimes when the users logs off the instance of the printer is not >>> removed. Subsequetly when the user logs back in there are 2 instances of the >>> printer and they cannot print. >>> >>> This is our 1st 2003 installation (our other 10 stores all run Windows 2000 >>> TS) and the printing is letting us down - any thoughts ? >>> >>> Mark Top From: Mark Stoker <MarkStoker@discussions.microsoft.com> To: none Subject: Re: New 2003 Installation with RDP Printing Problems Date: 09/28/2007 08:19:00 Jeff There only seems to be 1 version of the software on the HP site (http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en? I have set up the same printer on our test server and so far I have not been able to make it crash. The users on the live system have also reported very long log off times (up to 10mins) when they try and log off the terminal after experiencing the printer problem. We have other users with identical set-up's that have experienced no problems at all. Very frustrating !! Mark "Jeff Pitsch" wrote: > And of course I may simply have missed it. :) Are you using the > correct version of the driver? That can be just as important. Not all > print drivers are compatible with terminal services because of the > multi-user nature of terminal services. What your experiencing sounds > like a classic case of a bad print driver. > > 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 > > Mark Stoker wrote: > > Looking at the HP document the P2010 Printer is listed. However on the HP web > > site the P2010 is a 'series' of printers and If you chosse the driver for the > > P2010 it gives you the P2014 driver ?? > > > > "Jeff Pitsch" wrote: > > > >> Unfortunately i did not find that driver in hp's terminal services > >> compatibility document > >> (http://h71028.www7.hp.com/ERC/downloads/4AA0-8465ENW.pdf). you may > >> want to use printer redirection and map it to a compatible driver: > >> http://support.microsoft.com/?kbid=239088 > >> > >> 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 > >> > >> Mark Stoker wrote: > >>> We have just installed a new 2003 R2 terminal server solution in one of our > >>> retail stores. We are using Wyse S30 terminal with HP P2014 printers > >>> attached via the USB connection. I am using the Windows 2003 driver. > >>> > >>> Most of the time the users can print fine but we have seen the following > >>> problems. > >>> > >>> i) If say the printer jams and the user has the intervene the print job > >>> seems the get 'stuck' in the print queue. Re-starting the print spooler > >>> service usally does the job getting it to print. > >>> > >>> ii) Sometimes when the users logs off the instance of the printer is not > >>> removed. Subsequetly when the user logs back in there are 2 instances of the > >>> printer and they cannot print. > >>> > >>> This is our 1st 2003 installation (our other 10 stores all run Windows 2000 > >>> TS) and the printing is letting us down - any thoughts ? > >>> > >>> Mark > Top From: TP <tperson.knowspamn@mailandnews.com> To: none Subject: Re: New 2003 Installation with RDP Printing Problems Date: 09/28/2007 11:19:36 Hi Mark, This printer is a host based printer, and as such is not a good TS printer (unless you are using a 3rd party universal printer driver solution). It will use much more CPU and bandwidth for each print job when compared to a printer that has the native ability to understand ? Another down side of host based printers is that you do not have the flexibility to map to a more basic driver like the HP LaserJet 4. Mapping to a basic driver is a common technique if the manufacturer-supplied driver is not TS compatible. The basic drivers often produce smaller print jobs as well and are fine for many business document needs. I did a quick test for you to illustrate what I mean. I opened a 43KB text file in notepad, and printed it to the P2014 host based driver. The document was 12 pages. The amount of print data that downloaded to my workstation was 1,487KB!! In addition, CPU usage on the TS was heavy during the entire time the print job was downloading to the client. Next I printed the same file from Notepad to an HP P2015 PCL 5 driver. The amount of print data that downloaded to my workstation was only 128KB!! There was a brief spike in CPU usage while the 12 pages were spooled from notepad, but then it went back to 0% afterwards. If you have several users printing on your TS, using a host based printer could quickly bring the server to a crawl because of the CPU and/or bandwidth used. The above test was relatively basic. Real world printing will involve multiple fonts, colors, some graphics, which will amplify the problem. NOTE: When I ran the test with the P2014 I noticed strange behavior. After the notepad print job completed downloading I noticed many "phantom" print jobs accumulating in my local print queue. In just 30 seconds I had over 100 jobs sitting there. When I attempted to log off of the server it took several *minutes*, hanging on "Executing C:\WINDOWS\system32\wlnotify.dll". Normally logoffs are instant. I have extended messages enabled on this test server or else I would not have known where in the logoff process it was hanging. Based on my own direct observations and your description of problems I would say this driver is *not* TS compatible. -TP Mark Stoker wrote: > We have just installed a new 2003 R2 terminal server solution in one > of our retail stores. We are using Wyse S30 terminal with HP P2014 > printers attached via the USB connection. I am using the Windows 2003 > driver. > > Most of the time the users can print fine but we have seen the > following problems. > > i) If say the printer jams and the user has the intervene the print > job seems the get 'stuck' in the print queue. Re-starting the print > spooler service usally does the job getting it to print. > > ii) Sometimes when the users logs off the instance of the printer is > not removed. Subsequetly when the user logs back in there are 2 > instances of the printer and they cannot print. > > This is our 1st 2003 installation (our other 10 stores all run > Windows 2000 TS) and the printing is letting us down - any thoughts ? > > Mark Top From: Mark Stoker <MarkStoker@discussions.microsoft.com> To: none Subject: Re: New 2003 Installation with RDP Printing Problems Date: 09/28/2007 11:39:01 TP Thanks for the details explanation (and your time). Yes, the driver does seem to be the root of the problem. I'm just looking at the 'ThinPrint' solution which seems to involve by-passing the driver. Regards Mark "TP" wrote: > Hi Mark, > > This printer is a host based printer, and as such is not a good > TS printer (unless you are using a 3rd party universal printer > driver solution). It will use much more CPU and bandwidth for > each print job when compared to a printer that has the native > ability to understand ? > > Another down side of host based printers is that you do not > have the flexibility to map to a more basic driver like the HP > LaserJet 4. Mapping to a basic driver is a common technique > if the manufacturer-supplied driver is not TS compatible. The > basic drivers often produce smaller print jobs as well and are > fine for many business document needs. > > I did a quick test for you to illustrate what I mean. I opened a > 43KB text file in notepad, and printed it to the P2014 host > based driver. The document was 12 pages. > > The amount of print data that downloaded to my workstation > was 1,487KB!! In addition, CPU usage on the TS was heavy > during the entire time the print job was downloading to the client. > > Next I printed the same file from Notepad to an HP P2015 > PCL 5 driver. > > The amount of print data that downloaded to my workstation > was only 128KB!! There was a brief spike in CPU usage while > the 12 pages were spooled from notepad, but then it went > back to 0% afterwards. > > If you have several users printing on your TS, using a host > based printer could quickly bring the server to a crawl because > of the CPU and/or bandwidth used. > > The above test was relatively basic. Real world printing will > involve multiple fonts, colors, some graphics, which will amplify > the problem. > > NOTE: When I ran the test with the P2014 I noticed strange > behavior. After the notepad print job completed downloading > I noticed many "phantom" print jobs accumulating in my local > print queue. In just 30 seconds I had over 100 jobs sitting there. > > When I attempted to log off of the server it took several > *minutes*, hanging on "Executing C:\WINDOWS\system32\wlnotify.dll". > Normally logoffs are instant. I have extended messages enabled > on this test server or else I would not have known where in the > logoff process it was hanging. > > Based on my own direct observations and your description of > problems I would say this driver is *not* TS compatible. > > -TP > > Mark Stoker wrote: > > We have just installed a new 2003 R2 terminal server solution in one > > of our retail stores. We are using Wyse S30 terminal with HP P2014 > > printers attached via the USB connection. I am using the Windows 2003 > > driver. > > > > Most of the time the users can print fine but we have seen the > > following problems. > > > > i) If say the printer jams and the user has the intervene the print > > job seems the get 'stuck' in the print queue. Re-starting the print > > spooler service usally does the job getting it to print. > > > > ii) Sometimes when the users logs off the instance of the printer is > > not removed. Subsequetly when the user logs back in there are 2 > > instances of the printer and they cannot print. > > > > This is our 1st 2003 installation (our other 10 stores all run > > Windows 2000 TS) and the printing is letting us down - any thoughts ? > > > > Mark > Top From: Phillip Windell <philwindell@hotmail.com> To: none Subject: Re: Multihomed Terminal Server Date: 09/24/2007 12:05:43 "nhance" wrote in message news:0FFACCDA-8683-435E-928D-A1C7BB4C06FB@microsoft.com... > I have a requirement for a terminal server to have 2 network cards both > going to different internet interfaces Then the "requirement" needs to change. That is a very bad idea. > My main NIC 1 has always worked well, both router have the ports forwarded > correctly and on Nic1 i can access remotely, on NIC 2 i cannot access from > extrernally on NIC2 > > Is it a routing issue, a Gateway issue? Yes. You cannot have two Default Gateways. That's why it is called a *Default* Gateway. Default Gateways are "global" for the entire machine and that is what creates the "0.0.0.0" entry in the Routing Table. The OS would have warned you about this with a popup dialog when you tried it,...you would have had to ignore the warning to proceed. -- Phillip Windell www.wandtv.com The views expressed, are my own and not those of my employer, or Microsoft, or anyone else associated with me, including my cats. ----------------------------------------------------- Top From: Jeff Pitsch <Jeff@Jeffpitschconsulting.com> To: none Subject: Re: Multihomed Terminal Server Date: 09/24/2007 16:55:53 You need to manually configure the routes for the NIC that won't have the default gateway. Route.exe will be your friend in this case and don't forget to make them persistent otherwise they won't stay when you reboot/shutdown the server. 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 Phillip Windell wrote: > "nhance" wrote in message > news:0FFACCDA-8683-435E-928D-A1C7BB4C06FB@microsoft.com... >> I have a requirement for a terminal server to have 2 network cards both >> going to different internet interfaces > > Then the "requirement" needs to change. That is a very bad idea. > >> My main NIC 1 has always worked well, both router have the ports forwarded >> correctly and on Nic1 i can access remotely, on NIC 2 i cannot access from >> extrernally on NIC2 >> >> Is it a routing issue, a Gateway issue? > > Yes. You cannot have two Default Gateways. That's why it is called a > *Default* Gateway. Default Gateways are "global" for the entire machine and > that is what creates the "0.0.0.0" entry in the Routing Table. The OS > would have warned you about this with a popup dialog when you tried > it,...you would have had to ignore the warning to proceed. > Top From: nhance <nhance@discussions.microsoft.com> To: none Subject: Re: Multihomed Terminal Server Date: 09/24/2007 18:38:01 Hi Jeff, I have not done a lot in this area over the years it would seem The Network card is 10.0.1.6 and the default gateway is 254 Can you please give me the route command as i am not getting it right route 10.0.1.0 255.255.255.0 10.0.1.254 10.0.1.6 MERTIC 20 IF 3 Matthew "Jeff Pitsch" wrote: > You need to manually configure the routes for the NIC that won't have > the default gateway. Route.exe will be your friend in this case and > don't forget to make them persistent otherwise they won't stay when you > reboot/shutdown the server. > > 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 > > Phillip Windell wrote: > > "nhance" wrote in message > > news:0FFACCDA-8683-435E-928D-A1C7BB4C06FB@microsoft.com... > >> I have a requirement for a terminal server to have 2 network cards both > >> going to different internet interfaces > > > > Then the "requirement" needs to change. That is a very bad idea. > > > >> My main NIC 1 has always worked well, both router have the ports forwarded > >> correctly and on Nic1 i can access remotely, on NIC 2 i cannot access from > >> extrernally on NIC2 > >> > >> Is it a routing issue, a Gateway issue? > > > > Yes. You cannot have two Default Gateways. That's why it is called a > > *Default* Gateway. Default Gateways are "global" for the entire machine and > > that is what creates the "0.0.0.0" entry in the Routing Table. The OS > > would have warned you about this with a popup dialog when you tried > > it,...you would have had to ignore the warning to proceed. > > > Top From: Phillip Windell <philwindell@hotmail.com> To: none Subject: Re: Multihomed Terminal Server Date: 09/25/2007 08:40:52 Sorry, I guess I should have "finished the story" by mentioning the addition of the static routes after removing the DFG. -- Phillip Windell www.wandtv.com The views expressed, are my own and not those of my employer, or Microsoft, or anyone else associated with me, including my cats. ----------------------------------------------------- "Jeff Pitsch" wrote in message news:%23GHutWv$HHA.2268@TK2MSFTNGP02.phx.gbl... > You need to manually configure the routes for the NIC that won't have the > default gateway. Route.exe will be your friend in this case and don't > forget to make them persistent otherwise they won't stay when you > reboot/shutdown the server. > > 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 > > Phillip Windell wrote: >> "nhance" wrote in message >> news:0FFACCDA-8683-435E-928D-A1C7BB4C06FB@microsoft.com... >>> I have a requirement for a terminal server to have 2 network cards both >>> going to different internet interfaces >> >> Then the "requirement" needs to change. That is a very bad idea. >> >>> My main NIC 1 has always worked well, both router have the ports >>> forwarded >>> correctly and on Nic1 i can access remotely, on NIC 2 i cannot access >>> from >>> extrernally on NIC2 >>> >>> Is it a routing issue, a Gateway issue? >> >> Yes. You cannot have two Default Gateways. That's why it is called a >> *Default* Gateway. Default Gateways are "global" for the entire machine >> and that is what creates the "0.0.0.0" entry in the Routing Table. The >> OS would have warned you about this with a popup dialog when you tried >> it,...you would have had to ignore the warning to proceed. >> Top From: nhance <nhance@discussions.microsoft.com> To: none Subject: Re: Multihomed Terminal Server Date: 09/25/2007 10:00:03 Hi All, The thing with posting on these sites is to request some support and draw on the collective knowlege of all contributors. Many times the concept is know but the details fuzzy, out of the replies i am still not getting a result. Can somone please confirm my steps and advise if i am wrong as i am 12hrs difference and i need to get this resolved asap. We need extra bandwidth to allow RDP access only so we purchased a 2nd ADSL2+ service and want to use this for external access. We still need this device to be available via it's 192 address for local land and the ADSL service 1 to come in and out also. Network 1 (Internal LAN) 192.168.0.6 255.255.255.0 192.168.0.254 DG (Procurve Router, Main Internet Device) Network Interface #2 Network 2 (ADSL 2+ RDP ONLY) 10.0.1.6 255.255.255.0 0.0.0.0 DG 10.0.1.254 (Netcomm NB9 Router) Network Interface #3 Do i leave the 2nd interface DG blank and add a static route route add -p 10.0.1.0 255.255.255.0 10.0.1.254 METRIC 1 IP 3 Please tell me if this is right or wrong to get the result as i need this resolved. matthew Top From: Phillip Windell <philwindell@hotmail.com> To: none Subject: Re: Multihomed Terminal Server Date: 09/25/2007 11:56:59 "nhance" wrote in message news:CFC6189E-0F99-465A-A302-22E8671DC82B@microsoft.com... > The thing with posting on these sites is to request some support and draw > on > the collective knowlege of all contributors. Many times the concept is > know > but the details fuzzy, out of the replies i am still not getting a result. > Can somone please confirm my steps and advise if i am wrong as i am 12hrs > difference and i need to get this resolved asap. I'm sorry, ...you're getting the results of your post, I'm afraid it just isn't what you want to hear. You can *NOT* have two "Internet" nics,...period. The Internet, by the very fact of what it is,..is an "unknown" destination (0.0.0.0),...therefore is handled only by the Default Gateway and there can be only *one* functioning Default Gateway at a time. Concering the nic it "comes from".... Traffic always shows comming from the Primary IP# of the Nic that matches the Route found in the Routing table which is determined by the Destination. For the Internet this is always the 0.0.0.0 Route (the Default Route) and will always show comming from the Nic with the Default Gateway and if that nic has more than one IP# then it will always be the Primary IP#. The IP# (and/or Nic) that the traffic was originally received on is completely and totally irrelevant. You have a flawed network design based on flawed theory. In a correct design this server would have only one nic. Concerning other routing matters,... You get more bandwidth by getting a faster line,...you don't get more bandwidth by adding another Line, that is one of the flaws in your theory. The second flaw might be that this is RDP,..which has very *low* bandwidth requirements and doesn't need a new line just for it. What a second Line gets you is more Routes or more Routing Options,...or more often just more Routing Confusion. The only gain in Bandwith comes from moving some of the traffic over to the second Line to free up bandwidth on the first,...*BUT* that only works when the environment and the topology have been properly designed for it and,...this is very important,...you approach it with the right expectations for the right reasons. It typically does not work for inbound traffic, or at least is a whole lot more complicated and limited in options because of the "response" to the traffic not following the same path (which appears to be your problem). I am speaking from experience. At our place we have: 2 DSL lines 1 CableTV internet line 1 commercial grade connection built from 2 T1 lines that are "merged" These all have different purposes, but they all work with the same company LAN, and they all work perfectly with no problems. My Terminal Server has only one Nic. We are a TV Station with equipment that causes heavy bandwith usage to the outside. So I divide up that equipment into groups of similar or related purposes and configure each "group" to use a particular "internet connection". In most cases the Destination is "specific" so the Routing can be handled by our LAN Router to move the traffic to the correct connection. If the desitnation is "not specific" then the equipment must be in the correct subnet to use the chosen "internet connection" as its default gateway (that's the correct topology stuff I mentioned) while using local static routes to deal with the rest of the LAN's segments. So now when I get to the Terminal Server, I have it just use the "normal" main internet connection for the LAN because I have plenty of bandwidth due to how I moved the other equipment to use specific dedicated connections for what they do. -- Phillip Windell www.wandtv.com The views expressed, are my own and not those of my employer, or Microsoft, or anyone else associated with me, including my cats. ----------------------------------------------------- Top From: Phillip Windell <philwindell@hotmail.com> To: none Subject: Re: Multihomed Terminal Server Date: 09/25/2007 12:02:40 You could treat the Terminal Server the same way I did my "special equipment" by getting rid of one nic, setting the correct Default Gateway on the correct nic to us the correct connection. Then use Static routes in the OS to tell it how the "find" the rest of the LAN. But if your LAN is a single subnet then you don't need any static route. This is pretty much what we suggested in the first place. -- Phillip Windell www.wandtv.com The views expressed, are my own and not those of my employer, or Microsoft, or anyone else associated with me, including my cats. ----------------------------------------------------- Top From: nhance <nhance@discussions.microsoft.com> To: none Subject: Re: Multihomed Terminal Server Date: 09/25/2007 12:24:04 Hi Phillip, Appreciate all you are saying but bandwidth isn't that cheap in australia, nor that fast yet (mobile data here is one of the worlds best though) We have Cisco, Juniper, and ProCurve doing this task at other sites to get more bandwidth, on this one i was just hoping we could use the 2nd nic to serve a seperate internet user group. I may just need to tell the client to put a 2nd WIC in their router and do it here. Mind you there are other posts that say it can be done and with success it seems Matthew "Phillip Windell" wrote: > You could treat the Terminal Server the same way I did my "special > equipment" by getting rid of one nic, setting the correct Default Gateway on > the correct nic to us the correct connection. Then use Static routes in the > OS to tell it how the "find" the rest of the LAN. But if your LAN is a > single subnet then you don't need any static route. > > This is pretty much what we suggested in the first place. > > -- > Phillip Windell > www.wandtv.com > > The views expressed, are my own and not those of my employer, or Microsoft, > or anyone else associated with me, including my cats. > ----------------------------------------------------- > > > Top From: Phillip Windell <philwindell@hotmail.com> To: none Subject: Re: Multihomed Terminal Server Date: 09/25/2007 12:24:55 "Phillip Windell" wrote in message news:%23ufTjX5$HHA.4656@TK2MSFTNGP04.phx.gbl... > You could treat the Terminal Server the same way I did my "special > equipment" by getting rid of one nic, setting the correct Default Gateway > on the correct nic to us the correct connection. Then use Static routes > in the OS to tell it how the "find" the rest of the LAN. But if your LAN > is a single subnet then you don't need any static route. Sorry, I didn't "finish the story" again. To do the above both internet connections need to come into the LAN,..not directly into any machine. They would require a NAT-based or Proxy-based Firewall. For example a typical Linksys box is a cheap low-dollar NAT Firewall. The internal facing interface of both devices would be on the LAN. Then you control which connection gets used by how you control the routing. The Terminal Server would have one nic. -- Phillip Windell www.wandtv.com The views expressed, are my own and not those of my employer, or Microsoft, or anyone else associated with me, including my cats. ----------------------------------------------------- Top From: nhance <nhance@discussions.microsoft.com> To: none Subject: Re: Multihomed Terminal Server Date: 09/25/2007 12:32:04 ok, so did u use a black box type agregator appliance or seperate routers, this is that hard bit, i know you have all resolved the issues but some details and description would be a massive help "Phillip Windell" wrote: > You could treat the Terminal Server the same way I did my "special > equipment" by getting rid of one nic, setting the correct Default Gateway on > the correct nic to us the correct connection. Then use Static routes in the > OS to tell it how the "find" the rest of the LAN. But if your LAN is a > single subnet then you don't need any static route. > > This is pretty much what we suggested in the first place. > > -- > Phillip Windell > www.wandtv.com > > The views expressed, are my own and not those of my employer, or Microsoft, > or anyone else associated with me, including my cats. > ----------------------------------------------------- > > > Top From: Phillip Windell <philwindell@hotmail.com> To: none Subject: Re: Multihomed Terminal Server Date: 09/25/2007 14:03:41 I don't know if the way I did it is what you want, but... For clarification, when I say "router" I mean a real router,..an LAN Router,..which has nothing to do with the Internet. When I refer to the internet device I will call it a NAT Firewall or a Proxy Firewall depending on how it does its job. All of my "connections" have some form of a Firewall on them. None of the them go "directly" into any PC The merged T1 pair -- ISA2006 (both NAT and a Proxy) ADSL #1 --- some odd-ball brand of NAT box that I can't remember ADSL #2 --- an Linksys NAT box CableTv Conn -- a DLink NAT box The boxes all have the internal interface on the same IP segment on the LAN The last three are used for special purposes. The individual machines that use them use the Default Gateway that matches the specific connection they want to use, and then they use Local Static Routes to specify the LAN Router as the Path for all the other LAN's subnets. The rest of the normal machines use the LAN Router as the Default Gateway which in turn uses the ISA2006 as its Default Gateway which causes the T1 lines to be the "normal" connection used for the majority of all the machines. There are variations of these techniques, but my specific techniques meets my needs in my situation. Linksys (and probably others) makes a Duel-WANport device that can take in two different internet connections and can load blance between them (or do fail-over). that may be a solution for you. I don't have any model numbers, but you should be able to figure that out by reading through the product descriptions. -- Phillip Windell www.wandtv.com The views expressed, are my own and not those of my employer, or Microsoft, or anyone else associated with me, including my cats. ----------------------------------------------------- "nhance" wrote in message news:7BBA3E96-1E9C-449D-95B0-C2F0F82753C8@microsoft.com... > ok, so did u use a black box type agregator appliance or seperate routers, > this is that hard bit, i know you have all resolved the issues but some > details and description would be a massive help > > > > > > "Phillip Windell" wrote: > >> You could treat the Terminal Server the same way I did my "special >> equipment" by getting rid of one nic, setting the correct Default Gateway >> on >> the correct nic to us the correct connection. Then use Static routes in >> the >> OS to tell it how the "find" the rest of the LAN. But if your LAN is a >> single subnet then you don't need any static route. >> >> This is pretty much what we suggested in the first place. >> >> -- >> Phillip Windell >> www.wandtv.com >> >> The views expressed, are my own and not those of my employer, or >> Microsoft, >> or anyone else associated with me, including my cats. >> ----------------------------------------------------- >> >> >> Top From: Lynn <Lynn@discussions.microsoft.com> To: none Subject: Re: More than Two Admins (THANKS!) Date: 09/23/2007 22:08:00 Thanks to you both for the prompt answers! "Vera Noest [MVP]" wrote: > Actually, you can get 3 admins in simultaneously, 2 normal sessions > and 1 to the console (mstsc /console). But that's the limit. > _________________________________________________________ > 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 Lynn, > > > > Not possible, it's by design. And remote administration mode you > > can use without a CAL. > > > > Best regards > > > > Meinolf Weber > > Disclaimer: This posting is provided "AS IS" with no warranties, > > and confers no rights. > > > >> Ah, yes. My very special snowflake systems. :P > >> > >> I have a system that because of the nature of the work, > >> requires multiple admins to be logged into my 2003 Enterprise > >> Server. We have four admins who need remote access. We even > >> have CAL's for these admins. > >> > >> TS is currently set up in remote admin mode, which everyone > >> knows allows 2 concurrent connections. > >> > >> I do not want to run TS in Application mode, there's no need > >> the server to serve applications. Besides, installing TS it > >> would break the proprietary software that lives there. > >> > >> I need to be able to allow remote administration for FOUR > >> admins concurrently (don't ask, it wasn't my idea!) using > >> remote administration. Is there any way to make this work or > >> should I wish for a pink pony and a million dollars, while I am > >> at it? > >> > >> Thanks very much for any insight! > Top From: Vera Noest [MVP] <vera.noest@remove-this.hem.utfors.se> To: none Subject: Re: More than Two Admins (THANKS!) Date: 09/24/2007 15:51:00 You're welcome, Lynn! _________________________________________________________ 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?THlubg==?= wrote on 24 sep 2007 in microsoft.public.windows.terminal_services: > Thanks to you both for the prompt answers! > > "Vera Noest [MVP]" wrote: > >> Actually, you can get 3 admins in simultaneously, 2 normal >> sessions and 1 to the console (mstsc /console). But that's the >> limit. >> _________________________________________________________ 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 Lynn, >> > >> > Not possible, it's by design. And remote administration mode >> > you can use without a CAL. >> > >> > Best regards >> > >> > Meinolf Weber >> > Disclaimer: This posting is provided "AS IS" with no >> > warranties, and confers no rights. >> > >> >> Ah, yes. My very special snowflake systems. :P >> >> >> >> I have a system that because of the nature of the work, >> >> requires multiple admins to be logged into my 2003 >> >> Enterprise Server. We have four admins who need remote >> >> access. We even have CAL's for these admins. >> >> >> >> TS is currently set up in remote admin mode, which everyone >> >> knows allows 2 concurrent connections. >> >> >> >> I do not want to run TS in Application mode, there's no need >> >> the server to serve applications. Besides, installing TS >> >> it would break the proprietary software that lives there. >> >> >> >> I need to be able to allow remote administration for FOUR >> >> admins concurrently (don't ask, it wasn't my idea!) using >> >> remote administration. Is there any way to make this work or >> >> should I wish for a pink pony and a million dollars, while I >> >> am at it? >> >> >> >> Thanks very much for any insight! Top From: Meinolf Weber <meiweb(nospam)@gmx.de> To: none Subject: Re: More than Two Admins Date: 09/21/2007 00:47:22 Hello Lynn, Not possible, it's by design. And remote administration mode you can use without a CAL. Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. > Ah, yes. My very special snowflake systems. :P > > I have a system that because of the nature of the work, requires > multiple admins to be logged into my 2003 Enterprise Server. We have > four admins who need remote access. We even have CAL's for these > admins. > > TS is currently set up in remote admin mode, which everyone knows > allows 2 concurrent connections. > > I do not want to run TS in Application mode, there's no need the > server to serve applications. Besides, installing TS it would break > the proprietary software that lives there. > > I need to be able to allow remote administration for FOUR admins > concurrently (don't ask, it wasn't my idea!) using remote > administration. Is there any way to make this work or should I wish > for a pink pony and a million dollars, while I am at it? > > Thanks very much for any insight! > Top From: Vera Noest [MVP] <vera.noest@remove-this.hem.utfors.se> To: none Subject: Re: More than Two Admins Date: 09/21/2007 13:53:04 Actually, you can get 3 admins in simultaneously, 2 normal sessions and 1 to the console (mstsc /console). But that's the limit. _________________________________________________________ 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 Lynn, > > Not possible, it's by design. And remote administration mode you > can use without a CAL. > > Best regards > > Meinolf Weber > Disclaimer: This posting is provided "AS IS" with no warranties, > and confers no rights. > >> Ah, yes. My very special snowflake systems. :P >> >> I have a system that because of the nature of the work, >> requires multiple admins to be logged into my 2003 Enterprise >> Server. We have four admins who need remote access. We even >> have CAL's for these admins. >> >> TS is currently set up in remote admin mode, which everyone >> knows allows 2 concurrent connections. >> >> I do not want to run TS in Application mode, there's no need >> the server to serve applications. Besides, installing TS it >> would break the proprietary software that lives there. >> >> I need to be able to allow remote administration for FOUR >> admins concurrently (don't ask, it wasn't my idea!) using >> remote administration. Is there any way to make this work or >> should I wish for a pink pony and a million dollars, while I am >> at it? >> >> Thanks very much for any insight! Top Post your questions, comments, feedbacks and suggestions