Connecting to MAS200

  • Thread starter Thread starter j.t.w
  • Start date Start date
J

j.t.w

Guest
Hello,

We're wanting to connect a sales office to the main office to use
MAS200.

I've seen some posts about connecting to MAS200 via terminal services.
Does anyone know what is the user's experience like? Is it acceptable
or is there a lag like when using gotomypc?

Does anyone have any other sugestions we should look into with using
the MAS product?

Thanks,
j.t.w
 
RE: Connecting to MAS200

We run MAS500 on a Terminal Server in my office and the performance is
acceptable, as long as you have it running on a decent enough box. The only
downside is that in order to get it to work correctly (Spent hours on the
line with Sage support) you have to give the users Admin rights to the box.

"j.t.w" wrote:

> Hello,
>
> We're wanting to connect a sales office to the main office to use
> MAS200.
>
> I've seen some posts about connecting to MAS200 via terminal services.
> Does anyone know what is the user's experience like? Is it acceptable
> or is there a lag like when using gotomypc?
>
> Does anyone have any other sugestions we should look into with using
> the MAS product?
>
> Thanks,
> j.t.w
>
>
 
Re: Connecting to MAS200

Jeff,

Thanks for the quick reply.

Can you clarify what you mean by giving "users admin rights to the
box"? Do you mean the terminal server box or the MAS200 server box? If
it's the terminal server box, what kind of damage can the users do to
it? And have you personally had any problems with your users?

Again, thanks for replying. Much appreciated.

j.t.w
 
Re: Connecting to MAS200

I mean the Terminal Server box. As for what damage they can do, pretty much
anything anyone with Admin rights could do... I would suggest going to the
Local Security policy on that machine and locking down permissions for what
Administrators can do and replace those rights with Domain Admin, Ie ability
to shut down the computer....


"j.t.w" wrote:

> Jeff,
>
> Thanks for the quick reply.
>
> Can you clarify what you mean by giving "users admin rights to the
> box"? Do you mean the terminal server box or the MAS200 server box? If
> it's the terminal server box, what kind of damage can the users do to
> it? And have you personally had any problems with your users?
>
> Again, thanks for replying. Much appreciated.
>
> j.t.w
>
 
Re: Connecting to MAS200

Never make users Administrators just to fix a permission problem
with an application! It's just a matter of time before they screw
up your server beyond repair.

Check this out:

My application runs fine for Administrators, but not for normal
users
http://ts.veranoest.net/ts_faq_applications.htm#FileRegMon

_________________________________________________________
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?SmVmZg==?= <Jeff@discussions.microsoft.com> wrote on 14
feb 2008 in microsoft.public.windows.terminal_services:

> I mean the Terminal Server box. As for what damage they can do,
> pretty much anything anyone with Admin rights could do... I
> would suggest going to the Local Security policy on that machine
> and locking down permissions for what Administrators can do and
> replace those rights with Domain Admin, Ie ability to shut down
> the computer....
>
>
> "j.t.w" wrote:
>
>> Jeff,
>>
>> Thanks for the quick reply.
>>
>> Can you clarify what you mean by giving "users admin rights to
>> the box"? Do you mean the terminal server box or the MAS200
>> server box? If it's the terminal server box, what kind of
>> damage can the users do to it? And have you personally had any
>> problems with your users?
>>
>> Again, thanks for replying. Much appreciated.
>>
>> j.t.w
 
Back
Top