Locking a client device binds that client to the current model number. Meaning that if something unexpected should happen during a migration or update, a connecting client ignores the new manifests from the server.
Mobile devices (iOS and ChromeOS) can not be locked to a model number as they have no client running on them.
The right-click > Lock option for iOS is for locking the screen of the device
See: Locking Devices
2. Backup your FileWave server for the migration
If you are wanting to Migrate to a Linux Virtual Server we offer a pre-built appliance that you are able to bring up in your Virtual Environment. You would go to FileWave website → Support → Software Downloads → FileWave Management Suite → select "Release notes and Download" → Scroll Management Suite Downloads Page. Scroll to the bottom of the software downloads page and you will see the option below to download a Virtual Server appliance. FileWave Management Suite Downloads Page
When you are migrating your FileWave server you need to migrate the server to the same version of FileWave that you are currently running. For example if you are running FileWave 12.1 you must migrate to a FileWave 12.1 server. If you try to migrate from a FileWave 12.1 server to FileWave 12.3 the migration will fail.
|title||3.1 macOS or Linux server → macOS Server|
3.1 macOS or Linux server → macOS Server
- Install the same FileWave server version that you are currently running on to your new Server.
- On your macOS server go to the FileWave website → Support → Software Downloads → FileWave Management Suite → select "Release notes and Download". (You will select the same release that you are running on your current server. For the screen shots I am migrating to a FileWave 12.3 server) FileWave Management Suite Downloads Page
- You will then scroll down on the page until you see "macOS Installers" and select it. This will download the FileWave Installers for the version of FileWave you are migrating to in a .dmg file.
- Next you will find the FileWave dmg file that was downloaded in step "b" and double click on the file to open it.
- You will be presented with a similar window on the server and will be looking for the "FileWave Server.pkg" in the top right above "Server Installer"
- To run the install you just need to double click on the "FileWave Server.pkg" and go through the steps as prompted on the machine.
- The installer can take a few mins to run but when it is finished you will be presented with the window below and you are finished with upgrading the server.
- The server is now installed and you can continue with the migration.
Once the server is installed you will open Terminal and Stop the FileWave server services that are running on the new server.
sudo fwcontrol server stop
- Next step is to Move the FileWave backup that you created previously on your old server to the new server. You are able to do this how ever you would like. Two ways that are most common is by moving the backup to a network share or using scp command on the server. You will need to move all of the files created in the "fw-backups" folder including the zipped folder, Data Folder, and ipa folder. We would suggest moving it to the /tmp directory of your FileWave server. For all example commands we will show from that directory.
- Once the backup is moved to the new server the next step is to unzip the Zip folder that is inside of the "fw-backups" folder. This zip file contains the configuration and Database files that you will be using for the migration. Screenshots below show the files that will be in your backup.
- The next step is to start moving files from your backup to locations on your new FileWave server. You will need to replace the files already in the location. For the commands below we will move the file that is at the location of the new server so that you are available to replace it from your backup. For the commands below the backup is located in the "/tmp" directory of the new server. The commands will be slightly different on your server depending on your file path and name of the backup folder since it is named by default with the day and time the backup was taken.
- Open Terminal on your server and type the below command to receive root access
- Certs folder of your backup to /usr/local/filewave/certs/
- Move the "certs" folder from the new server
mv /usr/local/filewave/certs /usr/local/filewave/certs.bak
- Copy the "certs" folder from your backup
cp -r /tmp/fw-backups/fwxserver-Config-DB-Jan-12-18--10-34/certs /usr/local/filewave/
- Media folder from backup to /usr/local/filewave/
- Move the "media" folder from the new server
mv /usr/local/filewave/media /usr/local/filewave/media.bak
- Copy the "media" folder from your backup
cp -r /tmp/fw-backups/media /usr/local/filewave/
- ipa folder from backup to /usr/local/filewave/ipa/
- Move the "ipa" folder from the new server
mv /usr/local/filewave/ipa /usr/local/filewave/ipa.bak
- Copy the "ipa" folder from your backup
cp -r /tmp/fw-backups/ipa /usr/local/filewave/
- Data Folder from backup to /fwxserver/Data Folder/
- Move the "Data Folder" folder from the new server
mv /fwxserver/Data\ Folder /fwxserver/Data\ Folder.bak
- Copy the "Data Folder" folder from your backup
cp -r /tmp/fw-backups/Data\ Folder /fwxserver/
- Move the below two files to /usr/local/filewave/apache/conf/
- Move the "httpd_custom.conf" file from the new server
mv /usr/local/filewave/apache/conf/httpd_custom.conf /usr/local/filewave/apache/conf/httpd_custom.conf.bak
- Copy the "httpd_custom.conf" file from your backup
cp -r /tmp/fw-backups/fwxserver-Config-DB-Jan-12-18--10-34/httpd_custom.conf /usr/local/filewave/apache/conf/
- Move the "mdm_auth.conf" file from the new server
mv /usr/local/filewave/apache/conf/mdm_auth.conf /usr/local/filewave/apache/conf/mdm_auth.conf.bak
- Copy the "mdm_auth.conf" file from your backup
cp -r /tmp/fw-backups/fwxserver-Config-DB-Jan-12-18--10-34/mdm_auth.conf /usr/local/filewave/apache/conf/
- Move the passwd files from the backup to the new server
- Move the "passwords" and "passwords.digest" file from the new server. (You may not have a passwords.digest file. If so you can skip without any issues)
mv /usr/local/filewave/apache/passwd/passwords /usr/local/filewave/apache/passwd/passwords.bak
mv /usr/local/filewave/apache/passwd/passwords.digest /usr/local/filewave/apache/passwd/passwords.digest.bak
- Copy the "passwords" and "passwords.digest" file from the new server. (You may not have a passwords.digest file. If so you can skip without any issues)
cp -r /tmp/fw-backups/fwxserver-Config-DB-Jan-12-18--10-34/passwd/passwords /usr/local/filewave/apache/passwd/
cp -r /tmp/fw-backups/fwxserver-Config-DB-Jan-12-18--10-34/passwd/passwords.digest /usr/local/filewave/apache/passwd/
- Next step is to run the below commands on your new servers database.
- Open terminal and give yourself root access for the next commands. After entering the command you will need to type in the admin credentials for the new server.
- First you need to start the postgres process on your new FileWave server. You can do so with the below command.
sudo -u postgres /usr/local/filewave/postgresql/bin/pg_ctl start -w -D /fwxserver/DB/pg_data -m fast
- Once postgres has been started you will now need to access the Database on the server using the below command.
/usr/local/filewave/postgresql/bin/psql postgres postgres
- Then you will need to drop the MDM table of the database
drop database mdm;
- Create a table you are then able to restore your mdm-dump.sql file to
create database mdm OWNER postgres ENCODING 'UTF8' TEMPLATE template0;
- Quit out of the Database with the below command
- Now you need to run the restore on the mdm-dump.sql file on your new server. You can do so with the below command. For my command the "mdm-dump.sql" file is located in the "/tmp" directory but the command you run will match the location of your backup. This command can take a little while to run. If you see any errors at the end of the output there is most likely an issue with the migration and please contact our FileWave support team for assistants.
/usr/local/filewave/postgresql/bin/psql -U postgres mdm < /tmp/fw-backups/fwxserver-Config-DB-Jan-12-18--10-34/DB/mdm-dump.sql
- Once the command finishes we will now need to start running the migration for the Database manually. First migration you will run with the below command.
/usr/local/filewave/python/bin/python /usr/local/filewave/django/manage.pyc migrate --no-input --fake-initial
- Then we will need to do a server migration which can be done with the command below.
- Run the script attached below with sudo to fix the server's folder permissions and ownerships.
- You will need to give the script 755 permissions first. You will run the command to the path to the script. For the example it is in the /tmp folder.
chmod 755 /tmp/fixfwxserverPermissions5.X-1.sh
- Then you will need to run the script.
- After this command finishes you are almost done with migrating the information for the server. Next step is to restart the FileWave services to start checking if the migration has completed successfully. This can be done with the below commands to stop and start the services.
- Stop the FileWave services
sudo fwcontrol server stop
- Start the FileWave services
sudo fwcontrol server start
- With the FileWave server services started you are now done with migrating the Data on the FileWave server and Move on to Checking the migration in the FileWave Admin. Do not change your IP or DNS to match that of the old server yet. This will be one of the last things you do so you can make sure everything is correct before having your devices connect to the new server.