Skip to content
English
More support Sign in
Contact us
  • There are no suggestions because the search field is empty.

Swap Guide

Search

Swap Guide

Overview:

 

This guide will walk you through the steps necessary to ensure a server swap goes as smoothly as possible. Each section will directly correspond to the section that is listed on the Swap Checklist form, which must be filled out for every swap. You can find the swap at the below link. Please copy this form (DO NOT EDIT THE BASE), then rename it to the track you are swapping. Create a new folder within that Gdrive and name it the tracks license name. Move the new sheet to this folder and rename it. 

If you have any questions during a swap or run into any complications, please seek out a Level 2 or Management personnel. 

Link to server swap sheets


Section 1) Server Prep:


Summary: This section can be done prior to the server swap day. It should be done in full prior to the swap if possible to help eliminate the time needed to complete the swap. 

  • Setup Receipt Printers
    1. On the Old server and the New one, Open OPOS
    2. Copy (Manually set up) the receipt printers on the New server exactly the same as the old one
    3. Be sure to set up each printer with the exact same Printer Name and IP address
    4. Right Click and press communication settings to see the IP it is set at.
  • Setup Cash Drawer
    1. On the Old Server and the New Server, Open OPOS
    2. Copy (Manually set up) the receipt printers on the New server exactly the same as the old one. 
    3. Be sure to set up each Cash Drawer with the exact same Printer Name and IP address
    4. Right Click and press communication settings to see the IP it is set at.
  • Setup Result Printers
    1. On the Old server and the New one, Open Devices and Printers
    2. Look at the printer that is set up on the old server
    3. Set up the same model printer on the new server
  • Setup Waiver Printers
    1. On the Old server and the New one, Open Devices and Printers
    2. Look at the printer that is set up on the old server
    3. Set up the same model printer on the new server
  • Check Paper Orientation
    1. Right Click on each Printer, go to printer properties
    2. Click on printer defaults
    3. Ensure the Orientation is set correctly on the New server when compared to the old. 
  • Set up SCR users in AD
    1. On the to-be-old server, open Active Directory Users and Computers
    2. Go to the ClubSpeed OU
    3. Double click on each SCR user, go the the Environment tab.
    4. If the executable is one of the new speed screens, on the new server create a new speed screen executable for the same channel and place it in the assets folder of the new server.
    5. Open Active Directory on the new server.
    6. Go to the ClubSpeed OU
    7. For the SCR users that had Environment settings pointed towards a new speed screen executable on the old server, point their environment settings towards the correct executable that you created in the assets folder on the new server.
  • Set up Reg Users in AD
    1. On the to-be-old server, open Active Directory Users and Computers
    2. Go to the ClubSpeed OU
    3. Double click on each REG user, go the the Environment tab.
    4. If the executable is one of the new registration apps, on the new server create a new registration executable for the same registration type (mind cameras, etc.) and place it in the assets folder of the new server.
    5. Open Active Directory on the new server.
    6. Go to the ClubSpeed OU
    7. For the REG users that had Environment settings pointed towards a new registration executable on the old server, point their environment settings towards the correct executable that you created in the assets folder on the new server.
  • Configure DHCP
    • Creating Scopes 
      1. On the to-be-old server, open DHCP
      2. Expand IPV4
      3. Expand Scope
      4. Select Address Pool. Note the start and end IP addresses ranges. There may be multiple along with exclusions
      5. On the new server, open DHCP
      6. Expand IPV4
      7. Right-click on IPV4 and select New Scope...
      8. Press Next and on the second-page name the scope Club Speed and in the description, enter the IP range from above. Press Next
      9. Enter the Start and End IP addresses noted above from the old server. Subnet mask should match that of the server. Press Next
      10. If there is an exclusion noted from the old server, enter it here. If not, Press Next
      11. Set the lease duration to 1 day. Press Next
      12. Ensure Yes, I want to configure these options now is selected and press Next
      13. Enter the default gateway of the server and press add. Press Next when complete
      14. If during the swap we are going to be migrating the new server onto the old server's IP address, ensure that the old server's IP address is listed under the IP address field. If not, enter it in and press add. Unless for a special case, remove all other IP addresses by highlighting them and pressing Remove. Press Next when you are complete.
      15. Press Next
      16. Ensure No, I will activate this scope later is selected and press Next
      17. Press Finish
    • Creating Reservations
      1. On the to-be-old server, open DHCP
      2. Expand IPV4
      3. Expand Reservations. If there is nothing listed, congrats! you're done. If there are IP addresses listed, continue on!
      4. Right-click on one of the reservations and select Properties
      5. On the new server, open DHCP
      6. Expand IPV4
      7. Right-click on Reservations and select New Reservation...
      8. Enter a friendly name into the Reservation name field. Enter the IP address for the reservation. Enter the MAC address of the hardware getting the reservation. (This information should be in the Properties window of the reservation on the old server).
      9. Continue until all of the reservations have been copied over to the new server
  • Setup Replication
  • Copy Clubspeedapps configs
    • Copy the files located below to the same directories on the new server (maybe unique per server):
      • [Drive letter]\clubspeedapps\api\config.php
      • [Drive letter]\clubspeedapps\admin\laravel\app\config\config.php
      • [Drive letter]\clubspeedapps\booking\laravel\app\config\config.php
      • [Drive letter]\clubspeedapps\cs-registration\laravel\app\config\config.php
      • [Drive letter]\clubspeedapps\cs-printer\config.js
  • Setup FD services
    • Check FireDaemon services on the old server and see if there are any custom services that are needing to be moved over.
      • Edit the FireDaemon service and in the general tab there should be a working directory. Find that folder in the file explorer and move it over to the same directory on the new server. (create a ClubSpeedCustomApps folder if needed)
      • Create new FireDaemon services on the new server copying those on the old server
  • Setup Task Scheduler
    • On the old server, check to see if there are any custom/needed tasks
    • Recreate these on the new server
    • Once the tasks are created, SET THEM TO DISABLED
    • If you have any questions or concerns about these, ask level two or leadership
  • Download latest Upgrade
    • Get with Support leadership to get the version that they want the new server to be upgraded to.
    • Download the files on to the new server and extract them to the C Drive
  • Copy Asset images
    • Copy the entire [Drive letter]/clubspeedapps/assets folder from the old server to the new. Do not overwrite.
  • Check Regional Settings
    1. Ensure the DB users are set to use the right language.
      • Open SQL on the old and new servers
      • Expand Security > Logins on both
      • For the users, root, network service, system, and mssqlserver logins do the following:
        • Double click on the login on both servers
        • check the old server's Default language for the login and make sure the new server's login matches the old server
    2. Ensure each Clubspeed user has the correct regional settings
      • Open Control Panel and got to Region
      • Under the Formats tab, ensure the correct Format is selected in the Format dropdown
      • Under the Location tab, ensure the correct location is selected in the Home location dropdown
      • Under the Administrative tab, ensure the correct Current language is showing under the Language for non-Unicode programs 
  • K1 Corporate Location Specific Set Up
  • Create terminal folders
    • Log in to the current live server
    • Open SSMS
    • Expand ClubspeeV8
    • Expand Tables
    • Right-click on dbo.controlpanel and select edit top ...
    • Note the amount of OFF, PIT, POS and REG terminal names are listed
    • On the new server, ensure that there are the following in the Clubspeed folder:
      • a sp_intake# folder with the correct number for every POS terminal name
      • a sp_office# folder with the correct number for every OFF terminal name
      • a sp_browser# folder with the correct number for every REG terminal name
      • a sp_pit# folder with the correct number for every PIT terminal name
  • Create terminal users
    • On the new and old server open active directory users and computers
    • expand the Clubspeed OU
    • Double click on each user to edit the properties of the user and go to the environment tab
    • Ensure the environment settings match. If there is a reg or scr user that has a different app for the environment settings, ensure the app is located on the new server and the environment settings a pointing towards it
  • Check/Configure DNS and SMTP
  • Copy over custom images
    • Also, check for any custom registration images, score sheet templates, etc. and copy them over to the new server
    • From the current server, copy over the files from this directory ...\clubspeed\wwwroot\csregistration\images :
      • adult.bmp
      • cs_reg.png
      • minor.bmp
      • reg_footer.png
      • register-kiosk.jpeg
      • thankyou.bmp
  • Check customer terminal compatibility
    • If the operating system of the current server is Windows Server 2008 R2 or earlier we need to get in touch with the customer and check to see if they have any Wyse terminals with a firmware version of 6.5 or higher or if they are using Windows machines to connect that they are windows 7 or higher and have the service pack to update the RDP client on those machines.
  • Inform customer of password change if applicable
    • If the customer already had a password that was not the speedsheet password on their old controller, make sure we still use that same password for the new controller. You will need to go into Active Directory and reset the passwords for all the Clubspeed OU users
Environment settings pointed towards a new speed screen executable on the old server, point their environment settings towards the correct executable that you created in the assets folder on the new server.Environment settings pointed towards a new registration executable on the old server, point their environment settings towards the correct executable that you created in the assets folder on the new server.SET THEM TO DISABLEDIf you have any questions or concerns about these, ask level two or leadership

 

 

Section 2)  Server Swap:

  • Copy Over Latest Database
    • Use the following article to take a backup of the databases:
    • Copy over the databases to the new server over the network
      • Open up a file explorer
      • in the address bar, type in \\{new server's ip address}\c$
        • This allows you access to the file system of the new server
      • Browse to somewhere safe and copy and paste all the database backups to the new server.
  • Attach Latest Database
  • Copy waiver, signature, and picture files
    • After the last business day before the swap, start transferring over image folders (customer pictures, waivers, signatures, and payment signatures).
      • You will want to map a network drive and copy over the files that way. If you have questions on how to do this, ask a level 2 or management.
  • Migrate DHCP 
    • Disable DHCP on old server:
      • Open DHCP on the old server
      • Ensure the server and IPv4 directories are expanded
      • Right-click on the scope and select deactivate
      • Right-click on the server and select deauthorize
      • Open up services and disable the DHCP SERVER service
    • Activate/Authorize DHCP on new server:
      • Open DHCP on the new server
      • Right-click on the server and select authorize
      • Ensure the server and IPv4 directories are expanded
      • Right-click on the scope and select activate
  • Swap IP Addresses
    • Change the old server to an available IP and give the new server the old server's IP and set DNS IP to new server's IP. Make sure Forwarders are set up.
  • Disable FD on Old Server
    • On the old server, open FireDaemon and select all services and edit the services. Set all services to disabled.
  • Disable ST on old server
    • On the old server, open up task scheduler and stop and disable all tasks
  • Enable Scheduled Tasks
    • On the new server, open scheduled tasks and make sure all scheduled tasks are enabled
  • Start FD services
    • On the new server, open FD and ensure all services are enabled and started
  • Enable Replication (if applicable) 
    • If the location replicates, on the new server, ensure that there is a CS_Replication task in task scheduler is enabled
  • Disable DB on old server
    • On the old server, open services and disable the SQL Server service
  • Export Duplicati on old server
    • On the old server:
      • Open Duplicati in Chrome by navigating to localhost:8200
      • Click the v next to one of the tasks
      • Click Export
      • Ensure To File is selected, and click Export
      • Repeat for the other Task
      • Transfer to the new server
  • DIsable Dulicati on old server
    • On the old server, open services and disable the Duplicati service
  • Import Duplicati tasks
    • On the new server:
      • Open Duplicati in Chrome by navigating to localhost:8200
      • Click Add Backup
      • Select Import from a file, and click Next
      • Choose File, navigate to the new file and then click Import
    • Make a new url for send-http-url (check the Duplicati setup guide for how to do this).

Section 3)  Post-Swap/Upgrade checklist:


Follow the below article for upgrade steps:


https://support.clubspeed.com/a/solutions/articles/47001188171


Ensure to use the upgrade doc and swap doc to document the post swap and upgrade 




Resources: 

LogMeIn link to send to customer: https://secure.logmein.com/pullinstall_go.asp?page=addacomputer3_pull&lang=en&c=00%5Fbrkpgwx110h9yo6cf7nct7xwpdnxk5khibg8j&bnf=undefined




Related Articles