Remote Access

If your organization ALREADY has remote access in place, requests for additional users or changes can be made via a Service Desk request.

If your organization needs to setup remote access, you will need to discuss those needs with us so that we can plan and schedule a project to get this in place.

Please review the Remote Access Configuration Options below for more information on your options. They are also ordered from shortest to longest implementation timeline.

REMOTE ACCESS CONFIGURATION OPTIONS

Note all of these configurations are delivered as a project and not via the Service Desk. After reviewing the options below please reach out to us through our contact form if you would like to discuss how one of these configurations may be needed/wanted at your environment.

These are ordered in shortest to longest implementation timeline.

Remote Desktop Gateway / Terminal Server

This provides for a remote desktop with full access to your corporate network, files, and applications. This is often used when server-based applications are in use at the corporate office that are not yet cloud-based. The only disadvantage to this approach is that your physical office must have power/Internet access for it to work.

VPN-based connectivity

This is a legacy method of remote access but still required in certain situations. This is configuring VPN access directly to a Client's corporate network through the firewall. We require SSL VPN licenses for SonicWall devices. Non-corporate workstations should not be configured with this, as it is a security issue. In this case we would recommend a Terminal Server setup.

Azure Server Hosting

Moving your entire server infrastructure to Azure (cloud) is recommended for a Client that utilizes server-based applications that will not have cloud versions in the future. This also is the highest form of disaster recovery protection as all services are run in the cloud.

Microsoft OneDrive / SharePoint

We are putting on all Technology Roadmaps the implementation of moving both user and shared files to these platforms. For those of you with a local server-based "shared drive" moving files to SharePoint/OneDrive will allow for remote access from anywhere on any device. In some cases, this is not possible due to application dependencies, but user files can always be moved to OneDrive. This is also a prerequisite for utilizing Microsoft Teams.

Microsoft Teams

This is a great product and one that we have been discussing with many of you. It allows for collaboration and sharing with chat, files, channels, and online meetings. Teams is typically implemented based on how your organization is structured and included moving your files into OneDrive/SharePoint as well. We have found that Teams can also largely replace (inefficient) internal emails via proper usage of Channels and teams.

Get Started