Server/POS Pre-update Checklist

Here are some questions that should be answered before deciding if we are ready to update the client's unit. 

• Client Should be informed and agree to the following:
  • branches updated and others that are not will not be syncing with each other. This goes with the POS too
  • the client should not turn off the computer while patching, this will cause issues in the data. We will leave a note on the desktop of the server once the update is done. 

• does the client have any customized software or any AV branch?
  
  • Web system
  • POS
  • Autosync
  • Database
  • Data collector
    
    • C500
    • Android
• Is the client using the data collector? Does their customization require additional changes before being updated?
• How can we move the settings for their current system to the new and updated one?
• Are all the POS computer names updated already?
• Are there any special cases that the devs should be aware of when updating the client? e.g. The manual sync of unirich's main branch is installed in a separate office computer because there is an issue with the server.
• is the client going to be updated as GIT or not?
• Clients should be informed that all POS whether for peak season or regularly used should be updated on their schedule and can't be accommodated in december. 
• should we install both the V4 and the v5 autosync at the same time?
• Documentation:
  • are all the POS and servers in the teamviewer and logmein list?
  • are already non-existing hardware removed from the list?
  • are the list of branches and terminals in port 82 complete and accurate?