Home › Knowledgebase › KB-1465

Cafe Pub Server Replacement Brisbane Gold Coast

Summary

This guide helps you troubleshoot and resolve: Cafe Pub Server Replacement Brisbane Gold Coast. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

Cloud Migration for Hospitality Operations: Brisbane and Gold Coast

Cafés, pubs, and restaurants across Brisbane and the Gold Coast frequently rely on a single on-premise server to manage bookings, staff rostering, and financial records. While this setup is familiar, it creates significant operational risk. A hardware failure, power surge, or theft can halt service entirely, and remote access is often limited or insecure. This article outlines migrating these workloads to Microsoft 365 and Azure cloud services so your team can manage operations from any device while reducing the cost and complexity of maintaining physical hardware.

Critical Warning: Do not migrate live POS databases during trading hours. Payment processing dependencies, including EFTPOS integration and offline trading capabilities, must be fully tested before you decommission any on-premise hardware. Ensure you can process payments and print receipts during an internet outage before removing the old server.

Why Replace Your On-Premise Server

Keeping a server on-site means paying for more than just the hardware. You are also responsible for:

Moving to Microsoft 365 and Azure shifts these costs into a predictable monthly subscription. Your data is stored in secure Australian data centres, and your staff can access bookings, rosters, and financial records from any device with an internet connection.

Quick Fix Steps

  1. Audit your current server and identify all critical data, including booking databases, staff rosters, financial records, and shared files.
  2. Document all hospitality hardware dependencies, including POS terminals, kitchen printers, receipt printers, barcode scanners, and EFTPOS terminals.
  3. Check your internet connection at the venue to ensure it can support cloud-based access for multiple devices.
  4. Provision Microsoft 365 licences for each staff member who needs access to email, files, and collaboration tools.
  5. Set up Azure storage or Azure Virtual Desktop for applications that must remain in a server environment.
  6. Migrate files and databases from the on-premise server to the cloud using the appropriate migration tools.
  7. Configure user identities and access permissions in Microsoft Entra ID (formerly Azure Active Directory).
  8. Test remote access from a tablet, laptop, or mobile device before decommissioning the old server.
  9. Verify payment processing and offline trading capabilities before removing on-premise hardware.

Detailed Instructions

Step 1: Assess Your Current Environment

Before making changes, document what is running on your existing server. Common hospitality workloads include:

Record the file path locations for shared data and make a list of which staff members need access to which folders.

\\SERVERNAME\SharedData\Menus

Step 2: Prepare Your Internet Connection

Cloud access depends on a stable business-grade internet connection. If your venue relies on a basic residential plan, consider upgrading to a business fibre or fixed wireless service before migrating. Multiple staff accessing bookings and rosters simultaneously will require sufficient upload and download speeds. Confirm your connection can support EFTPOS terminals and cloud POS applications during peak trading periods.

Step 3: Set Up Microsoft 365

  1. Purchase Microsoft 365 Business Premium licences for your organisation. This tier includes email, file storage, and advanced security features.
  2. Sign in to the Microsoft 365 admin centre and add your business domain.
  3. Navigate to Users > Active users and create user accounts for each staff member.
  4. Assign licences to each user so they can access Outlook, OneDrive, Teams, and SharePoint.
  5. Set up multi-factor authentication (MFA) for every account to protect against unauthorised access.

Step 4: Migrate Files to SharePoint and OneDrive

  1. Create a SharePoint site for your venue to act as the central location for shared documents, such as menus, supplier contracts, and staff policies.
  2. Use OneDrive for individual staff files that do not need to be shared across the organisation.
  3. Copy data from the on-premise server to SharePoint using the SharePoint Migration Tool. Do not copy live database files by dragging and dropping through a web browser.
  4. Set folder permissions so only relevant staff can view sensitive financial or HR documents.
Tip: Schedule the migration during quiet trading hours, such as early morning or late evening, to avoid disrupting bookings and service.

Step 5: Move Server-Based Applications to Azure

If your booking or rostering software requires a server environment, consider Azure Virtual Desktop or Azure cloud tiers. This allows staff to run the application from a tablet or laptop without needing a physical server in the office.

  1. Sign in to the Azure portal at portal.azure.com.
  2. Create an Azure subscription if your organisation does not already have one.
  3. Navigate to Azure Virtual Desktop > Host pools > Create.
  4. Configure the host pool with a virtual machine size suited to your application requirements.
  5. Select the operating system image and configure virtual machine settings, including network and storage.
  6. Install the hospitality application on the Azure environment and configure it to connect to your cloud database.
  7. Navigate to Application groups > Add users to assign staff to the virtual desktop group.
  8. Staff can log in remotely using the Remote Desktop app or a web browser.

Step 6: Manage Identity and Access

Use Microsoft Entra ID to control who can access your cloud resources. Create groups for different roles, such as Managers, Floor Staff, and Kitchen, and assign folder and application permissions based on those groups. When a staff member leaves the organisation, disable their account immediately to revoke access to all systems.

Step 7: Decommission the Old Server

Only switch off the physical server after you have:

Caution: Do not dispose of the old server until you are certain no critical data remains on local drives. Keep the hardware in storage for at least 30 days after migration as a precaution.

Troubleshooting

POS Terminal Cannot Connect to Cloud Application

Verify that the POS terminal is connected to the correct local network and that the venue's internet connection is active. Check that the Azure Virtual Desktop host pool is running and that the user has been assigned to the correct application group. Confirm that firewall rules allow outbound traffic to the required Azure endpoints.

EFTPOS or Payment Terminal Issues

Ensure the payment terminal is connected to the correct network port and that it can reach the payment processor. Test a transaction before opening for trade. If the terminal relies on the on-premise server for connectivity, reconfigure it to connect directly to the internet or through your router.

Kitchen or Receipt Printer Not Working

Confirm that the printer is connected to the local network via Ethernet or Wi-Fi. Check that the printer's IP address has not changed and that the POS workstation is sending print jobs to the correct IP address. Verify that the printer is online and has paper and ink or thermal rolls loaded.

Barcode Scanner Not Recognised

Ensure the scanner is plugged into the correct USB port or paired via Bluetooth. Test the scanner in a text document to confirm it is inputting data. If the scanner requires a server-based driver, reinstall the driver on the local workstation or Azure Virtual Desktop session.

Staff Cannot Access Shared Folders

Check that the user has been assigned a Microsoft 365 licence and that their account is a member of the correct SharePoint site or security group. Verify that folder inheritance is not blocking access.

Slow Performance When Accessing Cloud Applications

Test your venue's internet speed. If upload speeds are low, contact your internet service provider about upgrading to a business-grade plan. Also, ensure staff are not downloading large files over mobile data while on-site.

Multi-Factor Authentication Prompting Too Often

Review conditional access policies in Microsoft Entra ID. You can mark the venue's public IP address as a trusted location so staff are not prompted for MFA every time they log in from inside the business.

If you need assistance with this migration, just Open a Ticket and our team will get it sorted.

Still Having Issues?

Need more help? If the issue persists after trying these steps, please open a support ticket and our team will assist you.

💻 Open a Ticket