Applies to: Sage 100, Cloud Workspace customers.
Prerequisites: Admin Access enabled user account.
For Sage 100 Contractor deployments, we have already installed and configured with the sample company deployed. This way, you can immediately move your customers data over and have them set up and working quickly. This Knowledge Base article will simply cover how the program is set up, where the data is stored, what Swizznet is backing up, and what you need to do as the partner (maintenance plans, give yourself System Administrative access to the SQL server).
Cloud Workspace Server
When you log in to the server using the management portal (https://manage.swizznet.com), you are accessing the server as a local administrative user. You will have full admin rights to the server(s) for that customer.
Sage 100 Contractor is installed to the default location on the C:\ drive with all the proper permissions configured as per Sage's system requirements. The Sage100Con folder will exist on the data drive (E:\).
This is where the all of the Sage data will be stored. The scheduled Sage backups, the SQL databases, company files, etc. The proper permissions are also set on this folder.
We map folders out as drive letters for the customers, where as the Admin users (partners) will not see them the same way. Here is a list of our default mapped drives, and what their purpose is.
Z:\ - Within Cloud Workspace, every user will get a personal drive that is only visible to them. This can be used to store private documents, etc. E:\pro\companycode\username
H:\ - This mapped drive is the shared data location for the server. All users will have access to this, and this is a place to store common folders, documents that all of the users must access, etc. The physical location of this share is, E:\data\companycode\
F:\ - This mapped drive is the location where data uploaded via FTP will be stored. Typically this would be used during the migration period. E:\ftp\companycode\
All of the data stored in all of these locations will take up space on the customers billable data drive. Our default Sage 100 Contractor builds have 20GB of disk space, but this can be increased by contacting sales. Please note, that we can expand data drives, but not shrink them.
You can create shares as needed on the server. We understand that customers needs vary and that some of your users may be used to browsing through the company files, where as some may not be technical enough to do so. By default, when adding a new company, Sage will create a Share so that users can access that companies files. Please note, if you create a share, ensure that Everyone is given Full Control on the Share permissions as well as the Security permissions. This is required by Sage.
Working With Sage
We have an SA user created within SQL for you to access the server. The password is in a text file on the server, located in C:\Software\SA Password.txt. This will allow you in as SA.
You can manage the customer using this login, or grant yourself sysadmin rights within SQL Sever Management Studio/Sage Database Administrator.
We already have Knowledge Base Articles for adding admin users, as well as normal Sage users. Those are linked below.
The first step to upgrading Sage 100 to a newer version is to reach out to us and ask us to snapshot the server. This way if at any point during or after the upgrade process there is a failure, we can roll back to the pre-upgrade image.
Once we confirm the snapshot of the server, login to the customers server using administrative access (https://manage.swizznet.com and use the gear icon to connect) and run the software update.
By default, when you add a Sage company, it will set up a maintenance plan to keep two weeks of nightly backups.
We require that Sage maintenance plans be set up on the customers company files, but you do not have to keep it at two weeks.
The only backups that can be used to recover Sage 100 Contractor companies are the ones that Sage creates with its backups through the Database Administration tool/maintenance plans.
We do a full backup nightly. We keep these backups for 30 days. So, if you keep the default maintenance plan, you will effectively have 44 days of nightly backups to revert to. If you keep only a week, you will have 37 days.
View a webinar recording reviewing the items above: