Cloud Technology & IT Security Specialists Ask a question 01223 921 000 Client Area

Separating a Company’s IT Infrastructure

Over the years Cambridge Support have helped hundreds of businesses overcome many IT challenges. In this article we’ll describe how we helped a construction client of ours separate away from the product side of their business. This caused for the need of splitting the infrastructure of their IT systems.

The Challenge Cambridge Support Faced

One company is now becoming two companies and bought out by a third party. The products section was being split from the main construction side of the business. As both sections of the business grew, they shared the same infrastructure. Therefore, due to the products side being acquired, this necessitated the split in their IT infrastructure.

Their combined infrastructure consisted of servers in Azure, Microsoft 365 for email and Teams, and a SAP instance hosted by a SAP provider in AWS. In addition, a VPN from the SAP Providers AWS infrastructure to the offices allows for printing from SAP. For the initial first six months, both companies shared the same office.

The Solution We Presented

After Cambridge Support’s Technical Consultants met with both companies, a solution was decided. The products side of the business would not use any servers in their new configuration. Their emails would remain in Microsoft 365. Also, their files were moved into SharePoint due to most files being Office documents, which required versioning and collaboration. Both companies were very happy as there were capabilities they did not have before. Devices would continue to use Autopilot & Intune for enrolment, management, and configuration.

To accommodate two companies, the existing on-premises network would need to be split. The main construction company was given a new Microsoft 365 tenant. The tenant was configured, and the prestaging was started. All emails were migrated by using Microsoft’s new ability to perform a tenant-to-tenant migration. The SharePoint Migration Tool was used to copy the files from the server to a new SharePoint library.

The existing Intune and Group Policies were streamlined and reconfigured in the new tenant. The hardware hash for each machine to be migrated was obtained and imported to the new tenant. The existing network in the main office was split into VLANs, then the additional VPN to SAP in AWS was configured.

When a weekend was agreed in which the switchover would take place, final syncs were made for emails and files. The client’s PCs were reset and removed from the product side of the company on AutoPilot and added to the AutoPilot of the construction company. Once completed, the clients PCs were enrolled and configured.  

The Outcome

After all the above, both businesses now have separate IT infrastructures. Both companies are also sharing the same office space without any issue. This construction company was very happy with the Cambridge Support team and how they handled the spit in infrastructures. The speed in which our consultants were able to establish the best practice and ensure a smooth implementation was met with much admiration and appreciation. Both companies could continue working with minimal disruption while their IT infrastructure was split in two.

If you were impressed with how Cambridge Support handled such a complex task, feel free to contact us today and discover how we can help you.