Many companies viewed remote working as a short-term fix to the pandemic problem and felt that it would go away after a few months.
However, as the years have passed, most of our clients have recognised that it may be the new norm. In addition, firms have now realised that Remote Desktop Services form a pivotal part of their Disaster Recovery strategy going forward.
Many of our clients are now considering the Tycom Managed Disaster Recovery Service. This allows your Servers to be virtually booted up in the cloud in the event of a localised server failure or localised catastrophic event occurring, such as Ransomware, Virus, Fire, Theft, or Flood.
Typically, emergency server systems can be invoked and started in the Tycom Disaster Recovery Cloud within 180 minutes of the disaster occurring. Whilst this is great and very expedient, it does leave the conundrum of how your users will access the systems in the Tycom DR Cloud from their home or remote offices.
We are pleased to say the solution is simple and provides other advantages too. If an RDS (Remote Desktop Services) server is already deployed onsite and is replicated to the Tycom DR Cloud prior to the disaster occurring, the RDS server is simply started within the Tycom DR Cloud along with the other business servers, thus providing a secure, simple gateway to the business servers which have been recovered in the Tycom DR Cloud, without delays or connection lags.
During normal times the RDS server running locally in the office can be used by employees to facilitate hybrid remote working. It acts as a remote working gateway, providing secure and seamless access to business resources, regardless of the employee location or circumstances, for example, snow day, sick children, personnel illness, isolation, or just hybrid office / home working practices.
We know many of you are considering the Tycom managed Disaster Recovery Service, and hopefully this explains why we are mandating that each DR Cloud subscription must now include an RDS Server.