Legacy apps on Windows Server 2003

From: Mark (lil_at_OlMe.com)
Date: 02/27/04 

Date: Fri, 27 Feb 2004 11:05:26 -0600

I couldn't find any news groups specific to Server 2003, so I hope this is
OK to post here.

We just installed a W2k3 server specifically for Terminal Services. We have
1 application that uses some fairly old controls that I'm guessing are
considered "legacy." When I allow all users to log in as Power Users, they
can run the program fine, but when I put them back to regular users, the
program doesn't work porperly.

I've read several articles about using secedit /configure /cfg compatws.inf
... but that suggestion was written for 2000 Server and doesn't seem to
change anything on my 2003 Server. I can run the secedit command and it
seems to work fine, but regular users still can't run the application until
I re-promote them to Power User status.

Any ideas?

Relevant Pages

  • Re: User CALs
    ... When I refer to 15 staff users, these will specificially need access on their own profiles [which will be roaming profiles], as they are regular users and need e-mail - fax etc.and also need to log onto different computers to where they might normally be stationed. ... and it boots faster and responds faster on initial access to any settings than the dual 3 Ghz dual Xeon machine that I have started using with the new SBS server. ...
    (microsoft.public.windows.server.sbs)
  • Re: License Plate: DR GOY
    ... My server does carry a limited selection of binaries groups, ... (But I'm not sure how many regular users there are; ...
    (alt.usage.english)
  • New Application installation
    ... terminal server mode currently hosting 2 applications. ... installed office2K using the TermSrvr.mst file ... Now upon running a test for regular users we are receiving ...
    (microsoft.public.windows.terminal_services)
  • Re: domain log in thinks it is local log in?
    ... There is a security policy setting called Log on locally. ... regular users cannot interactively log on to a Domain Controller. ... I have just setup a trial Win 2003 Enterprise server with a Win XP Pro ... but from the XP client. ...
    (microsoft.public.windows.server.active_directory)
  • Re: permission to start spooler
    ... Anyway, if you go into SERVICES.MSC on the server, and open up Print ... Spooler, you can set "Recovery" options that will automatically restart the ... Windows Printing/Imaging/Hardware "troy" wrote in message ... > How can I give regular users in a Windows 2000> server/client domain the right to start and stop the print ...
    (microsoft.public.win2000.printing)