Upgrade databases, ZyDesk, and Media Server

The ZyDesk.ini file contains information about the SQL server host, port, user name, password, and ZyDB database name. ZyDesk clients require this file to work, and a copy of the file must be placed in C:\Program Files (x86)\Zylinc\ZyDesk\ZyDesk.ini

To create the ZyDesk.ini file:

1. In the Deployment Manager menu, select Database > ZyDB > ZyDesk

2. Make sure that Include tunnel server address is cleared

3. Click Generate encrypted file

4. Save the ZyDesk.ini file in C:\Zylinc install\Release_6.5u4.12\Release_6.5u4.12\4_ZyDesk

If you can't, or don't want to, use the ZyDesk.ini file, you can, alternatively, click Generate registry file, and then use a third-party tool to distribute that registry key to your clients.

If you can't place the ZyDesk.ini file in the C:\Program Files (x86)\Zylinc\ZyDesk folder, or if different users of a shared computer need different ZyDesk.ini files, you can, alternatively, place copies of the file in the following folders in the user profiles for each of the users: C:\Users\%username%\AppData\Roaming\Zylinc\Zydesk\Zydesk.ini. Tip: If you need to do this, the %appdata% environment variable is useful because it takes you directly to the Roaming folder.

Send two files to people who are going to install ZyDesk on Windows client computers.

Different people may manage the installation of clients, terminal servers, or Citrix servers. Remember to send the client software to all of them.

Find the following two files in C:\Zylinc install\Release_6.5u4.12\Release_6.5u4.12\4_ZyDesk, and send them to relevant people:

• ZyDesk_AllUserInstaller.msi

• ZyDesk.ini

You can zip the folder and send it in an e-mail.

Tell the receivers to make sure that .Net Framework on computers running ZyDesk, is updated to at least version 4.7.1.

Then tell the receivers to first install the client software with the .msi installer, and then copy the ZyDesk.ini file to C:\Program Files (x86)\Zylinc\ZyDesk\ZyDesk.ini

If you can't, or don't want to, use the ZyDesk.ini file, you can, alternatively, click Generate registry file, and then use a third-party tool to distribute that registry key to your clients.

If you can't place the ZyDesk.ini file in the C:\Program Files (x86)\Zylinc\ZyDesk folder, or if different users of a shared computer need different ZyDesk.ini files, you can, alternatively, place copies of the file in the following folders in the user profiles for each of the users: C:\Users\%username%\AppData\Roaming\Zylinc\Zydesk\Zydesk.ini. Tip: If you need to do this, the %appdata% environment variable is useful because it takes you directly to the Roaming folder.

1. In the Deployment Manager menu, select Deployment > Installation

2. In Installed Applications, select ZyDesk and click Uninstall Applications

1. Open the folder C:\Zylinc install\Release_6.5u4.12\Release_6.5u4.12\4_ZyDesk

2. Locate ZyDesk_AllUserInstaller.msi

3. Run the installer (it can be quick)

4. Copy ZyDesk.ini to C:\Program Files (x86)\Zylinc\ZyDesk\ZyDesk.ini

Specify the Media Server connection settings and Administration Portal location, because it allows Deployment Manager to connect to Media Server, and then view a list of deployed media server application versions. Via the list, you can also upgrade the software modules, and you can install Administration Portal.

1. In the Deployment Manager menu, select Deployment > Media Server

2. In Address, enter the hostname of Media Server, for example: MediaServer

3. In Port, enter 8080

4. In Media server connection settings > User, enter admin

5. In Media server connection settings > Password, enter the password for Tomcat instance user admin on Media Server

6. In Admin Portal connection settings > URL, enter: http://<MediaServer>:8080/zylinc-admin/

   Example: http://MediaServer:8080/zylinc-admin/

7. In Admin Portal connection settings > User, enter admin

8. In Admin Portal connection settings > Password, enter the password for Tomcat instance user admin on Media Server

9. Click Save

10. Click Refresh

1. In the Deployment Manager menu, select Deployment > Media Server.

2. Click Refresh.

3. In Available Media Server Applications, check if some of the applications indicate new version in the Status column, and appear in blue color.

   If so, use CTRL+click to select all the applications with status new version, and then click Deploy Applications.

   If you see an error message that says Please run a rewrite config manually, you can safely ignore it, because you'll handle it later in the process.

4. Wait until all the applications have successfully been deployed.

5. Click Refresh, and if necessary repeat steps 3 and 4 until no applications indicate new version in the Status column, and appear in blue color.

1. Boot the virtual server for Media Server on the ISO image.

   If you're in doubt about how to do this, search the internet for Boot virtual machine from iso or similar.

2. The ISO installer will run for approximately four minutes.

3. Wait until you see the message: Press <RETURN> to reboot (do not remove your removable medium yet)

4. Use the virtual server console to eject the installation media ISO image from the virtual DVD drive.

5. Press RETURN.

6. If you see the message switch login:

   Log in with user name: admin
   Password: admin

7. In Please enter a value for “Tomcat admin password” (): Enter the password for Tomcat instance user admin on Media Server.

8. In Please enter a value for “confirm the new tomcat password” (): enter the same password again.

9. Wait until you see the message: (network main) Enter option [h for help].

   1. Type 0, for eth0.

   2. Type m, to set DHCP/Static mode to STATIC.

   3. Type ip, and enter the IP4 address that you plan to use.

   4. Type mask, and enter the subnet mask that you plan to use.

   5. Type gw, and enter the IP4 address of the default gateway that you plan to use.

   6. Type da, and enter the IP4 address of DNS server 1 that you plan to use.

   7. Type da, and enter the IP4 address of DNS server 2, or skip this step if you only use one DNS server.

   8. Type b, to return to previous menu.

   9. Type a, to save and apply all changes

   10. Type 0, for eth0

   11. Type t, to toggle state from down to up

   12. Type b, to return to previous menu.

   13. Type a, to save and apply all changes.

   14. Verify that eth0 is shown in green, and that is displays a MAC address and an IP4 address. If that's not the case, go through network configuration again.

   15. Type q, to quit the (network main) Enter option [h for help] menu.

10. Enter the hostname that you plan to use.

    Example of a hostname: MediaServer

    We use hostnames to refer to servers, but you can also use IP4 addresses, if your network requires it.

11. Type n, to keep the selected time zone, or type y and specify another time zone.

12. Wait until you see -- (action) --> under NTP configuration: Select Action menu.

13. Type a, to save and apply all changes, and use the default time servers.

14. In Enter new UNIX password: Enter the password for Unix user admin for AdminCLI.

15. In Retype new UNIX password, enter the same password again.

16. Wait until you see a menu: select(1-4):

    • If you use a physical server, enter 1

    • If you use a VMWare host, enter 2

    • If you use a Hyper-V host, enter 3

    • If you don’t use any of the above, enter 4

17. In Do you wish to disable IPv6 [y/*], type y, to disable IPv6.

18. In Choice: type 2 for ZyCall Switch Backend.

19. Wait approximately six minutes until you see a message that says:

    Finished Setup.
    Enter any key to continue.

20. Press ENTER, to reboot Media Server.

21. Wait until you can see a text-based login prompt in the console window.

Specify the Media Server connection settings and Administration Portal location, because it allows Deployment Manager to connect to Media Server, and then view a list of deployed media server application versions. Via the list, you can also upgrade the software modules, and you can install Administration Portal.

1. In the Deployment Manager menu, select Deployment > Media Server

2. In Address, enter the hostname of Media Server, for example: MediaServer

3. In Port, enter 8080

4. In Media server connection settings > User, enter admin

5. In Media server connection settings > Password, enter the password for Tomcat instance user admin on Media Server

6. In Admin Portal connection settings > URL, enter: http://<MediaServer>:8080/zylinc-admin/

   Example: http://MediaServer:8080/zylinc-admin/

7. In Admin Portal connection settings > User, enter admin

8. In Admin Portal connection settings > Password, enter the password for Tomcat instance user admin on Media Server

9. Click Save

10. Click Refresh

1. In the Deployment Manager menu, select Deployment > Media Server.

2. Click Refresh.

3. In Available Media Server Applications, check if some of the applications indicate new version in the Status column, and appear in blue color.

   If so, use CTRL+click to select all the applications with status new version, and then click Deploy Applications.

   If you see an error message that says Please run a rewrite config manually, you can safely ignore it, because you'll handle it later in the process.

4. Wait until all the applications have successfully been deployed.

5. Click Refresh, and if necessary repeat steps 3 and 4 until no applications indicate new version in the Status column, and appear in blue color.

1. In the Deployment Manager menu, select Deployment > Media Server

2. Click Refresh

3. In Available Media Server Application, select ZylincAdminPortal

4. Click Deploy Applications

1. In a browser, go to the Administration Portal URL that you entered in a previous step (the setting was called Admin Portal connection settings)

   Example: URL: http://MediaServer:8080/zylinc-admin/

2. Click Admin

3. Log in with the user name and password you also entered in a previous step.

   Username: admin

   Password: Enter the password for Tomcat instance user admin on Media Server

4. Next to Host, click

   If you can see a help message, your browser supports scripting, and you can continue.

   If you can't see a help message, you'll need to add your Media server and Zylinc Windows application server to trusted sites in Internet Explorer, or use an alternative browser. For more information, see Set up Internet Explorer on Windows Application Server.

5. In Host, enter the hostname for the SQL server that hosts ZyDB, for example, WinAppServer

6. In Port, enter 1433

7. In Instance, leave the field blank

8. In Username, enter ZyUser

   For security reasons, don’t use the sa account (user name: sa).

9. In Password, enter the password for MSSQL user ZyUser

10. In DB Name, enter ZyDB

11. Click Save

12. Click Apply

13. Click Test.

14. You should see this message: Connection successfully established to Singletenant Database: <WinAppServer> / zydb

    You should also see the ZyDB Database Version. The version should not be 0.0.0.0

You're going to use Administration Portal again later, so make a note of the procedure in step 1.