You can rerun the installation wizard if you previously exited the wizard before completing all the steps, or you entered the wrong hostname/addressing information (for server-based deployments) during the initial configuration.
Re-running the installation wizard will overwrite any existing Management Node configuration and lose all connections to existing Conferencing Nodes. Therefore, if you re-run the installation wizard after deploying any Conferencing Nodes, you must delete any existing Conferencing Nodes and then redeploy them from the updated Management Node.
If you want to change the IP address of the Management Node you must first return your licenses from your current Management Node. If you do not return your licenses before re-running the installation wizard you will lose your licenses from your new Management Node (with the new IP address) and you will not be able to add them back to that new Management Node.
Do not re-run the installation wizard on cloud-based deployments (Azure, AWS or GCP) in order to change Management Node configuration data such as its IP address or hostname. To change such data you must terminate the existing instance and deploy a new Management Node instance. You should only re-run the installation wizard on cloud-based deployments if you need to reset the web administration password (and then you should not change any of the other configuration data).
If you re-run the installation wizard to only reset the web administration password then you will not lose your configuration data and you will not need to delete and redeploy your Conferencing Nodes, providing you re-enter exactly the same hostname/addressing information as before. However, after completing the wizard you must then edit every system location ( ) and reselect the DNS and NTP servers for that location.
To re-run the installation wizard:
Open a console window on the Management Node VM.
If your Management Node is deployed on Azure, AWS or GCP, use an SSH client to access the Management Node, supplying your private key file if appropriate.
- At the login prompt, log in as admin.
- If requested, enter the operating system password created when the installation wizard was run. If you did not get as far as creating a new password, you will be asked to create one now.
If your Management Node is deployed on Azure, AWS or GCP, you will be prompted again for the admin password.
The Pexip installation wizard will begin.
(Note that the steps described above can vary slightly depending on whether it is a cloud or server-based deployment, and whether you previously completed all of the installation wizard steps.)
Follow the prompts to set the following configuration for the Management Node.
If you press enter, the default value will be applied:
|Setting||Default value||Multiple entries allowed?||Can be changed via Pexip Infinity Administrator interface?|
|Hostname||<no default>||No||No ‡|
|Domain suffix||<no default>||No||No ‡|
|DNS servers||188.8.131.52||Yes, if separated by a space||Yes|
|NTP servers †||
Two of the following:
|Yes, if separated by a space||Yes|
|Web administration username||admin||No||No ‡|
|Web administration password||<no default>||No||Yes|
|Enable incident reporting (yes/no)||<no default>||Yes|
|Send deployment and usage statistics to Pexip (yes/no)||<no default>||Yes|
* These defaults apply only if your network does not have DHCP enabled. If DHCP is enabled, the defaults will be those allocated by the DHCP server. The addresses you enter using this wizard will be assigned as static IP addresses.
* When deploying on Microsoft Azure, Amazon Web Services (AWS) or Google Cloud Platform (GCP), these values are replaced with the IP address and network settings for your instance.
† The NTP server must be accessible by the Management Node at the time the startup wizard is run. Installation will fail if the Management Node is unable to synchronize its time with an NTP server.
‡ After they have been configured, do not attempt to change these settings by any other means.