Virtual Office CS or Software as a Service set up guide
Set up Virtual Office CS/SaaS by configuring your environment, adding NetStaff CS accounts, adjusting permissions, installing Azure Virtual Desktop, and migrating data.
Use this step-by-step guide to install and customize Virtual Office CS or Software as a Service (SaaS) for your firm's needs.
important
We recommend identifying a
product champion
in your firm to be your go-to person for Virtual Office CS or SaaS.
You'll need administration permissions to do these steps.
Complete the following steps in order:
Required steps
Step 1: Work with your tech to configure your environment
Work with your tech to make sure your environment meets our system requirements.
Set your antivirus and firewall preferences to stay protected without compromising performance, function, or stability.
Step 2: Sign in, add NetStaff CS accounts, and turn on permissions
Sign in to netlinksolution.com as the Firm Administrator using the credentials provided in the welcome email we sent you.
note
The subject line of the email is “Action Required: Welcome to Web Services.”
Select
Admin
, go to the NetStaff CS section, then select
Users
.
Select your name from the list.
Go to the Permissions section and then select
Enable
for Virtual Office CS or SaaS.
Sign out then sign back in.
note
You'll need to do this to view applications.
To add sign-ins for other staff members, go to the Users list and select
Add
.
In the
Add NetStaff CS Users
window, select the method you want to use to create staff.
Once the staff members are added, go to the Permissions section and select
Enable
for Virtual Office CS or SaaS for each member.
If you want to give them administrative permissions, select
Enable
for Administration.
Install Windows App on all computers that need to work in Virtual Office CS or SaaS applications.
On
NetStaff CS
, select
Applications
.
Select
Setup
, then
Windows App
to download the installation file.
Find the installation file and run it, then follow the installation instructions.
Set your default printer
For Windows computers, open your
Start Menu
and find
TerminalWorks
.
Select
TerminalWorks
, then open
Options
.
After the Options window opens, select your preferred printer as the
Default Printer
.
Select
Apply
to save your changes.
When you print, select
TSPrint Default
as the printer if you print with a
Virtual Office CS or SaaS
application powered by Azure Virtual Desktop.
important
If you use FileCabinet CS, you'll need to install the FileCabinet CS Print Driver.
Set your default scanner
For Windows computers, open your
Start Menu
and find
TerminalWorks
.
Select
TerrminalWorks
.
Open
TSScan Client Settings
.
Choose
Select Default Scanner
to set your preferred scanner.
Step 3: Migrate data
It's important to have a plan in place before migrating data to Virtual Office CS or SaaS. Here are a few tips:
FileCabinet CS data usually takes the most planning.
Your local C:\ drive will show as the V:\ drive in the Virtual Office and SaaS environments.
For the complete migrating instructions, refer to Migrating data to Virtual Office CS or SaaS.
Step 4: Use your products
Virtual Office CS or SaaS provides remote access to the applications your firm is licensed for. In the Virtual Office CS or SaaS environment, the applications behave similarly to when they're installed locally, with a few exceptions.
Recommended steps
Set up your email account in Virtual Office or SaaS
Microsoft 365 email and Office sign-in
Virtual Office CS or SaaS supports Microsoft Office applications when your firm maintains a supported Microsoft 365 subscription. Supported licenses are:
Microsoft 365 Business Premium
Microsoft 365 E3
Microsoft 365 E5
Microsoft 365 Apps for enterprise
If your firm uses email in Outlook within Virtual Office CS or SaaS, users should sign in with their firm-issued Microsoft 365 account. Exchange Online mailboxes, aliases, distribution groups, mobile access, and mail-flow settings are administered in your firm's Microsoft 365 tenant.
Your firm or your Microsoft Cloud Solution Provider is responsible for MX, Autodiscover, SPF, DKIM, and DMARC records associated with Microsoft 365 mail flow.