Welcome < Installation < Preparing to Install Zetta
Before installing Zetta®, some configuration must be done. This section will outline the following pre-install tasks required to install Zetta and Zetta2GO for the first time.
In this Topic: show/hideshow/hide
Install Required Device Drivers
Configuring Windows to Run Zetta
Before installing Zetta for the first time on a new PC, ensure the latest device drivers are installed for the following components:
Audio Device Drivers/Software – Obtain the latest approved drivers and software from the vendor for the audio solution used. To obtain a list of supported and approved audio devices and drivers, contact RCS Support. If Windows 10 or higher is used, ensure Zetta has access to the Microphone for recording. Go to Setting | Privacy | Microphone and set the Allow apps to access your Microphone to On.
Video Device Drivers/Software – In addition to the latest audio drivers, it is important to have the latest stable drivers and software installed for the video solution used. Contact the vendor or manufacturer of the video device for the latest software and drivers.
Network Adapter Drivers/Software – Having current Network Adapter drivers will help to prevent any connectivity issues due to corrupt or outdated network device drivers. Contact the vendor or manufacturer of the network adapter for the latest driver.
Zetta will run with User Account Control on or off. If user account control is turned on additional security prompts may be displayed upon installation of the software. In a network environment, Network Discovery and File Sharing will need to be enabled on Windows 7 and Windows 8 to allow the computers to communicate with each other. Contact the system administrator for assistance.
If running a Windows Server environment Zetta requires Desktop Experience and Media Foundation windows features be installed.
The following are the ports used by Zetta and the Services that use these ports. Most of these ports are automatically opened on the firewall of the computer when Zetta is installed, however they may need to be opened on the Internet firewall for the site if the services are used.
|
Protocol |
Port |
Service |
|
RPC |
135 |
Microsoft Message Queuing - http://support.microsoft.com/kb/178517 |
|
TCP |
443 |
Zetta2GO SSL and HTTPS connections |
|
TCP |
445 |
SQL Port used is for Named Pipes Protocol and File Sharing. |
|
UDP |
1434 |
SQL Port used for SQL Browser Service. The SQL Server Browser service listens for incoming connections to a named instance and provides the client the TCP port number that corresponds to that named instance. |
|
TCP |
1433, 1434 |
SQL listener ports. The default instance will listen on TCP port 1433. |
|
TCP |
1801 |
Message Queuing (including HTTP messaging) message traffic and internal session management traffic between Queue Managers. |
|
RPC |
2101 |
Microsoft Message Queuing - http://support.microsoft.com/kb/178517 |
|
RPC |
2103 |
Microsoft Message Queuing - http://support.microsoft.com/kb/178517 |
|
RPC |
2105 |
Microsoft Message Queuing - http://support.microsoft.com/kb/178517 |
|
TCP |
3131 |
GSelector® Integration |
|
TCP |
3132 |
Status Feed Service (For HTTP Bindings) |
|
TCP |
3133 |
Status Feed Service |
|
TCP |
3134 |
Status Feed Service (For TCP Bindings) |
|
TCP |
3135 |
ZCast Service |
|
TCP |
3136 |
Zetta2GO and RCSAPI (For HTTP Bindings) |
|
TCP |
3137 |
Zetta2GO and RCSAPI (For TCP Binding). Also used for Site Replication connection to API |
|
TCP |
3138 |
Zetta Integration API used with GSelector® Integration |
|
TCP |
3139 |
Zetta Simple API (For HTTP Bindings) |
|
TCP |
3140 |
Database Watcher Service (For HTTP Bindings) |
|
TCP |
3141 |
Database Watcher Service |
|
TCP |
3150 |
RCS Updater. RCS Updater application is installed with the Zetta Client and can be used to update multiple computers on the same network. |
|
UDP |
3527 |
Microsoft Message Queuing - http://support.microsoft.com/kb/178517 |
|
TCP/UDP |
4060 |
The default port for Live Metadata send, but can be changed. See the Live Metadata tab in the System Configuration window for the protocol and port being used. |
|
TCP |
42381 |
DBMS Service |
|
TCP |
42384 |
DBMS Streaming Service (2.7 and above) |
|
TCP |
42385 |
Local DBMS Service (2.7 and above) |
|
TCP |
42388 |
Local DBMS Streaming Service (2.7 and above) |
|
UDP |
49520 |
Site Map Synchronization Version 2 (3.5 and above) - This port needs opened on all machines running Zetta. |
|
TCP/UDP |
49521 |
RCS License Manager |
|
TCP/UDP |
49999-65535 |
Range for XMOM Agents |
|
|
55776 |
Default port used for the WheatNet UIO GPIO Device. See the Computer Configuration GPIO/Routes tab for the actual port number. |
|
|
64333 |
Default port used for DASDEC configuration. See the DASDEC configuration for the actual port used. |
|
TCP/UDP |
? |
GPIO devices using TCP or UDP connection requiring port configuration. See the Computer Configuration GPIO/Routes tab for the actual port number. |
Zetta runs the following commands during the installation to allow Zetta to run under a non-administrator account. If the netsh.exe is blocked or disabled, it will need to be enabled for these commands to run.
Command to register the web service address we use to talk to GSelector, UAC requires this command:
netsh http add urlacl url=http://+:3131/Zetta user=Users
Command to register the status feed address:
netsh http add urlacl url=http://+:3132/StatusFeed user=Users
Command to register ZCast address:
netsh http add urlacl url=http://{computername}:3135/ user=Users
Command to register Zetta api http address:
netsh http add urlacl url=http://+:3136/ user=Users
Command to register Zetta api tcp address:
netsh http add urlacl url=http://+:3137/ user=Users
Command to register Zetta GS integration api tcp address:
netsh http add urlacl url=http://+:3138/ user=Users
While RCS in general recommends keeping the operating system up-to-date with the latest updates from Microsoft, we also want to ensure these updates are not downloaded and installed uncontrollably. Therefore, RCS recommends disabling automatic updates for Windows. Having a system set to automatically update and reboot could take a station of the air. Windows Updates and reboots should be handled manually on Zetta computers for best results. If the computer is on a Domain contact the system Administrator for assistance. The Windows Update Settings for Windows 7 and 8.1 can be changed in the Changes Settings window of the Windows Update Control Panel.
In Windows 10 there is not a Windows Update Control Panel. Therefore the Configuration of Automatic updates will need to be done in the Domain or Local Group Policy Editor. If the computer is on a Domain contact the system Administrator for assistance. If the computer is not on a domain, right-click the Start button and select Run from the resulting menu. Enter gpedit.msc into the Run command and press enter to open the Local Group Policy Editor.
In the left pane navigate to Computer Configuration\Administrative Templates\Windows Components\Windows Update then in the right pane locate Configure Automatic Updates and double-click it. Set it to Enabled and then select the preferred setting in the options pane on the left. In the right pane of the Configure Automatic Updates window is some Help information for each setting. RCS recommends option 2 – Notify for download and notify for install.
Once Zetta is installed, always take a Backup of Zetta before installing windows updates.
Windows IIS will be enabled with the Zetta Installation package, when Zetta2GO or GSelector Integration is selected, if not previously installed. Contact the site system administrator for assistance.
|
|
To enable Internet Information Services (IIS), WCF and ASP.NET, perform the following steps: |
Welcome < Installation < Preparing to Install Zetta
© 2007-2024 RCS. All Rights Reserved.
