Setting up TRITON Unified Server Console on a Windows server

In order to get TRITON Unified Server Console installed correctly on a Windows server, you will need to verify that the following configuration setup has been installed:

∗ Verify the server OS is a supported version Select Start > Run and enter winver.exe
∗ All relevant updates are applied. The server must be updated to so the required underlying services are installed - i.e. .NET Go to Start > Control Panel > System and Security > Windows Update
∗ Windows PowerShell Windows PowerShell is required for the TRITON Unified installer. The most convenient method to verify it is installed is to access Server Manager and review the Features Summary.
∗ .Net Framework version 3.5 To validate the version of .Net, go to Start > Administrative Tools > Server Manager. Select to display Features.
∗ Windows Installer 4.5 or greater Open the command prompt and enter: msiexec /? A panel will be displayed showing information regarding the version.
∗ Getting error 1720 or 1722 when installing EIP Infra
  1. Open Services utility and stop and disable the Windows Firewall
  2. Start > Administrative Tools > Local Security Policy > Local Policies and make these changes:

    Security Options section
    • User Account Control: Admin Approval Mode for the Built-in Administrator account - Enabled
    • User Account Control: Allow UIAccess applications to prompt for elevation without using the secure desktop - Enabled
    • User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode - Elevate without prompting
    • User Account Control: Behavior of the elevation prompt for standard users - Prompt for credentials
    • The next 5 UAC entries set to Disabled
    • User Account Control: Virtualize file and registry write failures to per-user locations - Enabled
  3. Start > Control Panel > User Accounts > Change User Account Control Settings > on the User Account Control Settings panel make sure it is set to never notify
  4. Start > Control Panel > User Accounts > Manage User Accounts > select the domain admin account > on the user Properties panel, select Group Membership and ensure the level of access is set to Administrator
Quick Checks to avoid installation pitfalls
  1. First and foremost – make sure you are using the Unified installer and not the individual installers
  2. The server needs to be on the domain – and not a WORKGROUP, you can validate that through the Computer properties panel
  3. If you plan on installing WWS (Filtering) you really need to be logged on the server as a domain admin
  4. Is the domain admin you are logged on as included in the local Administrators group – Server Manager > Configuration > Local Users and Groups > Groups > Administrators
  5. Set User Account Control setting to never notify (from the above table)
  6. Are the permissions correct on the server (this is the stuff from the above table)
  7. Is the firewall disabled – there is a little trick on this – but this is also accessed from the Server Manager panel. On the Windows Firewall with Advanced Security Properties, there are 4 tabs – the first 3 tabs you will need to modify. On each of those tabs you will see a drop-down where you can select Off – before selecting off though, below that are 2 text fields that allow you to select Allow or Block – set both settings to allow then turn the firewall state to Off.
  8. Are the UAC settings correct (from the above table)
  9. If you are installing SQL Express within the Triton Unified installer, you need to perform a step when the Triton Infrastructure installer is finished (the “Finish” button for that installer will be present. At that point, go to the Services utility and check that the services are running (SQL Server, SQL Server Browser). By default the SQL Server Browser service will be disabled, you will need to display the properties, select it to be manual or automatic and then start it. Then proceed with the installation.
  10. If you plan on referencing the SQL Server by IP address (it is the preferred method) instead of the hostname, then you need to enable the TCP/IP protocol. Start > All Programs > Microsoft SQL Server 2008 R2 > Configuration Tools > SQL Configuration Manager – in the left panel select SQL Server Network Configuration > Protocols and enable TCP/IP (you must also restart the SQL Server – select SQL Server Services from the left panel and select the SQL Server option on the right panel and restart it)
  11. If you have all of that – you will most likely not run into any issues.