New install / help on setting up multi-user Sage drive, basic process

SUGGESTED

Morning all, after a discussion with sales and telling them what we wanted, they said we should go with Sage 50 / Quantum / Multi-user.    There is a single person office, 2 other users and some mobile use needed.  I am an AWS architect so figured a cloud solution was correct and they said yes, with a cloud server users at different places can access real time.   So we made the purchase, and here is where all my issues started.

I setup a Windows 2019 AWS server, downloaded direct from the link and the installer just crashes.  After some reading, I was able to finish the install from the /sage/peachw folder which left me at a question of where is the data located, local or windows share.  I was under the impression it would be local and other clients would connect via CNAME or direct, but again not the case.  So I chatted and told none of that will work, to get a ticket and call today.  A little more help but I am still confused so figured forums are always great.   I was given some KB pages which of course led to more questions;

What is Sage Drive and does my subscription plan include it 

Will Sage Drive allow a remote user to access the company at the same time as users in the office?

  • No, Sage Drive can be used in a multi-user environment; however, it will require you to access the company in a single-user mode while it is being shared on Sage Drive. Note: In 2017 version and higher, you can select Pause Sharing.

Getting started with Sage Drive Multi-User

Seems to be more of what I want.

So ... here is the recap and questions.   I don't have an "office" but 2 full time employees that will be home/remote with local SAGE 50 installed and needing to access the data almost real time.  Knowing if someone opens, adds something there is upload / download time.  That's it!   So the questions; 

1.  Is Sage Drive Multi-User what I need to setup?

2.  It says that the data is stored in Amazon (but not told where), so is this being stored on S3 and do I even need a server running in AWS if that server is not actively using it?


Sorry for the long thread, but I want to make sure everything is understood so I don't waste time as I am 2 days in and even Sage developers really tip-toe around things vs just helping sometimes.

  • 0
    SUGGESTED

    1. Maybe. I think that a server set up to host Remote Desktop sessions from outside users is a better solution. But if that's not feasible for you then Sage Drive Mutli-User may be a good option.

    2. You do not need an AWS server to use Sage Drive.

    I've never worked with AWS but let I'll try to explain how Sage Drive works. First, it's important to understand that Sage 50cloud is NOT a cloud application. It is a desktop application that integrates with certain cloud applications. One of those cloud applications is Sage Drive.

    Sage 50cloud gets installed on your local PC. In most instances it is installed on a local server, and then the installation on the workstation is pointed to the data on the server. Since you are in a single user office it would most likely be installed (program and data) to your C drive. Here's my "nutshell" version of how the Sage Drive portion works. When you share your data using Sage Drive, your data is copied up to the Sage Drive servers. The users that you have invited to share your Sage 50 data must also have Sage 50cloud installed on their PCs. Then they can open your data from Sage Drive. The data is copied down to their local drive where it is accessed the same way a locally created company file would be accessed except that the changes they make will get synchronized back up to Sage Drive and then down to your original database. None of that requires you to have an AWS server. To the end user, the fact that Sage Drive resides on AWS matters only for the sake of transparency, and has nothing to do with how you implement Sage 50cloud or Sage Drive.

    If you still have questions, don't hesitate to post a follow-up.

  • 0 in reply to StephenC

    Thanks for that update.   I spent some time over the weekend and spoke with Sage directly to get the server installed, sage drive installed and the company moved.

    We do have 3 users, so user one did the local install, was able to setup sage drive and download the company (so things are looking good).  Waiting on users 2 and 3 this week, and still trying to fully understand if a "server" is even needed if the data is residing on the sage drive and if so, does it need to be running 24/7.

    If user 1 and 2 have local copies, make a change and that get's updated to that sage drive, what reason is there to have a dedicated server sitting there (unless that sage drive has to talk to the main server which has the data on the local C drive) which I am not sure.

  • 0 in reply to lraymond

    Call me at 918-851-9713. I would be happy to share my knowledge of Sage 50 and Sage Drive in exchange for a little enlightenment about AWS.

  • 0 in reply to StephenC

    Absolutely.  Im in EST so will give you a call around 12:30est if that works for you.