Re: Sharing Application Through Terminal Services

Hi Vera,
You are right. The TS is running on a Domain Controller. So is there
anyway I could have the power users facility back coz it would solve my issue
I believe...

Jamie

"Vera Noest [MVP]" wrote:

> Could it be that the absense of the Power User security group
> reveals that the Terminal Service is running on a Domain
> Controller?
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> "Jeff Pitsch" <jeff@xxxxxxxxxxxxxxxxx> wrote on 22 nov 2005 in
> microsoft.public.windows.terminal_services:
>
> > did you try the filemon piece at all??? You can also try regmon
> > as well.
> >
> > and Windows 2003 DOES have a power users group. I'm not sure
> > where your getting that it doesn't.
> >
> > Jeff Pitsch
> > http://www.sbcgatekeeper.com
> > Your Terminal Services Security Website
> >
> >
> > "Jamie" <Jamie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > news:D3725896-FBED-49CE-9D96-735D56AA60FC@xxxxxxxxxxxxxxxx
> >> Hi Lukas,
> >> Thanks for sharing. I can only use TS coz my clients are
> >> not in the
> >> same area. Windows Server 2003 does not have a group called
> >> Power Users. And
> >> that is why we are facing this issue now. In the past, that is
> >> how we have overcome the issue. And yes, all rights are given -
> >> Full Control to anything
> >> and everything relating to ACCPAC, and yes too, when in Windows
> >> we logon as
> >> Admin, all ACCPAC users can access ACCPAC without any errors.
> >>
> >> Therefore, it must be some form of settings on Windows Security
> >> that prohibits the ACCPAC users from being able to register the
> >> User Interface for
> >> ACCPAC coz when we logon as a Domain Users, ACCPAC can launch,
> >> but certain of
> >> the programs when called upon will give us an error message to
> >> "CONTROL UI not properly installed". So what next?? Desperate
> >> now..
> >>
> >> Jamie
> >>
> >> "Lukas" wrote:
> >>
> >>> Aaaah, Accpac.
> >>>
> >>> We were using Accpac in this manner (Accpac on server, users
> >>> TS into server to run it, all over the LAN), and had all sorts
> >>> of issues. Our Accpac support people eventually declared that
> >>> this was not the preferred way to run Accpac - instead, it
> >>> should be used via its own client-server setup, eg install
> >>> Accpac on a server share, install the Accpac clients on the
> >>> user's workstations.
> >>>
> >>> This setup may not be suitable for you if your users and
> >>> server are geographically remote - the Accpac client-server
> >>> system uses a lot more network space than running it over RDP.
> >>> Have you tried it this way?
> >>>
> >>> Some things to check:
> >>>
> >>> 1) Do the users have Power User level rights on the server (eg
> >>> member of Power Users group)?
> >>>
> >>> 2) Do the users have Full Control rights on the Accpac
> >>> installation directory and all subdirs?
> >>>
> >>> 3) If you are using Accpac user accounts, can the users log in
> >>> using these accounts when the Windows login to the server
> >>> (over RDP or console) is admin?
> >>>
> >>> I don't think this is a TS issue.
> >>>
> >>> Lukas
>
.

Relevant Pages

  • Re: Sharing Application Through Terminal Services
    ... > reveals that the Terminal Service is running on a Domain ... >> and Windows 2003 DOES have a power users group. ... >> Your Terminal Services Security Website ... >>> and everything relating to ACCPAC, and yes too, when in Windows ...
    (microsoft.public.windows.terminal_services)
  • Re: Sharing Application Through Terminal Services
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... > and Windows 2003 DOES have a power users group. ... >> and everything relating to ACCPAC, and yes too, when in Windows ...
    (microsoft.public.windows.terminal_services)
  • Re: Sharing Application Through Terminal Services
    ... Windows Server 2003 does not have a group called Power Users. ... all ACCPAC users can access ACCPAC without any errors. ...
    (microsoft.public.windows.terminal_services)
Loading