Re: Windows 2003 Terminal Service and MS Access 2003



Pearl wrote:
We are testing MS Access 2003 application on a Windows 2003 Terminal Server in Remote Management mode (no licenses available for testing). Have installed MS Access 2003 using change user /install + install Access 2003 + change user /execute. Afterward, I tried to have 2 individuals login to the terminal server. Both logged in ok but only one person can launch MS Access at a time. Has anyone seen this happen before or is it a function of the TS being in remote admin mode and not application server mode with licenses?

What error do you get? The fact you used change user /install does not do anything in Remote Administration mode.
You can have a full TS working without any licenses for up to 210 days. A licensing server must be there in 120 days and once you set it up, users will NOT need licenses for 90 days. And if you set the TS to use per user licensing, it will NEVER track that, meaning you could run with no licenses forever. It is up to you to be legal and you should be of course.
But even if using per device, you have 210 days to test your app. I cannot imagine you need more than 210 days for testing...
Once the TS is installed properly and Office is installed, it should work properly.

--
Claudio Rodrigues
CEO, WTSLabs Inc.

http://www.wtslabs.com
"WebTS: TSWeb the way it should have been done since day one"

Microsoft MVP
Windows Server - Terminal Services
.



Relevant Pages

  • Re: terminal server that hands out licenese to other servers..
    ... I've worked in a lot of place but have never had a reason to allow 10 admins on one server at time. ... Microsoft MVP - Terminal Server ... Does that mean you have to install all terminal services in "application mode" on all servers that will need more than two connections? ... To provide licenses for the user connections, install the Terminal Server Licensing component on a domain controller and use the Terminal Server Licensing administration tool to activate your licenses. ...
    (microsoft.public.windows.terminal_services)
  • Re: Other access option for term server?
    ... And the five licenses don't have to be all for MS Office. ... to work on ANY server is via volume licensing for the product MS ... I'll have my person connect to the term server and from ... All you have is Remote Desktop on a W2003 server. ...
    (microsoft.public.windows.terminal_services)
  • Re: Some servers still getting temp licenses
    ... Windows Server 2003 Terminal Server Licensing White paper ... MCSE, CCEA, Microsoft MVP - Terminal Server ... But if you see a lot of temporary licenses in the TS Licensing ...
    (microsoft.public.windows.terminal_services)
  • Re: Connecting ONE remote PC to SBS 2003
    ... Using that license to do anything other than server administration violates ... It is called "Remote Administration Mode" for a reason...so ... TS licenses are for systems that can run TS, ...
    (microsoft.public.windows.terminal_services)
  • Re: Licensing issue
    ... Is the Terminal Server set to use "Per ... I have purchased 40 per user licenses ...
    (microsoft.public.windows.terminal_services)