Installing MAS200 at the main office and branch office

Hello,

We're looking into purchasing MAS200 but have a couple of general
questions...

After installing MAS200 at the main office, can we install a copy of
MAS200 at a branch office (a sales department) without having to
purchase the complete ERP software and database for that location? We
will have enough client licenses for all users.

I've seen some posts about connecting to MAS via terminal services.
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

 

Technically it would be against the MAS 200 Sage Software license to
install the software in multiple locations like you suggest. The best
implementation of MAS 200 for multiple locations is using terminal
services. Provided there is a reasonable DSL internet speed at both
offices there should be no lag or delay. The user experience is so
similar to a live session that most users will not even know they are
on terminal server. In addition, all the accounting is in one
location on one system. if you implement two different installs, you
will have problems with multiple data sets in different locations -
usually not a good idea.

A properly implemented Terminal solution for MAS 200 is a solid and
cost effective way to use MAS from multiple locations.

 

Roy,

Thanks for your quick response.

I've read in some posts that in order for MAS to work with Terminal
Service (TS), the users need admin rights on the TS box. Do you know
if this is true? Or do you know of a work around that works (something
like setting full control permissions only on specified folders)?

Again, thanks for your help and insight.
j.t.w

P.S. Does anyone know how much TS with a 5 user license costs and TS
with a 15 user license?

 

JTW,

What kind of company will be using MAS200?

Thanks,

A

 

Hi J.T.W.,

What type of business are you running? There are a lot of solutions
out there that would not require terminal services to connect over the
internet, although terminal services would certainly work. Have you
looked into programs built in the Microsoft .NET framework with the
ability to utilize Web services rather than requiring terminal
services?

Good luck with your decision!

Rebecca

Comtech Solutions
Accounting & ERP Made Easy

 

Howdy,

Terminal Services is built into the latest versions of Windows. I use it
regularly.

The server receiving the connections should be configured with specific
login accounts. Remote connections should never be logging in with the
server's Administative account. You will want an experienced and very
trustworthy consultant to set it up while you watch and learn how to change
the passwords.

The connection accounts can be set to access the server with limited
privileges. Should be able to restrict it to only open and use MAS.

I know you do not want to use Windows Vista for the main machine. Its
security will drive you crazy, while at the same time is not completely safe
for this type of networking. Windows 2003 Server will work very nicely for
you.

Thanks, Chris www.bizynet.com and www.bizycart.com
BIZynet Coordinator - (575) 586-1225
Moderator of biz.ecommerce, biz.general, biz.marketplace.discussion,
biz.marketplace.web-design, biz.marketplace.international & others

 

The best way to address common network security concerns with MAS200
is actually to use TS. Just setup the Remote Desktop User profile to
launch MAS 200 at user login, or modify the RDP shorcut on the desktop
to launch MAS200 at login, then TS only allows MAS to be run. This is
a good way to avoid security problems and in my opinion TS is actually
more secure than most MAS 200 configs.

That said, MAS200 does require full admin rights to function
properly. Even if MAS 200 is installed on the local desktop it is
best if the local user has full rights to the local machine and of
course full rights to the directory above the ../MAS90 directory.

Printing to non-network local printers is a little bit of a hassel
with TS, so consider making all printers network printers when you
roll out TS.

Shoot me an email if you need any help.

Cheers.

Roy Hobbs
http://www.alxerp.com