Set the SA password to: sauser (step 13) - optional
2. Configure SQL Server Configuration Manager to allow TCP and Enable SQL Server Browser
Start SQL Server Configuration Manager by searching for it and starting or edit in local Computer Management under MMC
Open SQL Native Client Configuration - Open Client Protocols - Verify TCP/IP Says Enabled - If it does not right click on TCP/IP and press enable
Open SQL Server Network Configuration - Open Protocols - Verify TCP/IP Says Enabled - If it does not right click on TCP/IP and press enable
Open SQL Native Client Configuration (32bit) - Open Client Protocols - Verify TCP/IP Says Enabled - If it does not right click on TCP/IP and press enable
Open SQL Server Services - Right Click on SQL Server Browser - Go to Service Tab - Click on start mode and switch to automatic - Click Apply
Right Click on SQL Server - Click Restart
Right Click on SQL Server Browser - Click Start
3. Import NTL Studio Database into SQL Server
New Database
Follow the steps from step 4(Install iConnect Studio), sub-step 4
Start iConnect Studio - It will give you an error the first time because it is not connected to any DB
Select the SQL Server you just installed along with the database name - if it does not show up most likely there is a problem with the SQL Server setup
If you are starting with a fresh database, Click 'Generate Database' then open the "SQL Database Name" drop down and look for 'NTLStudioDatabase'
Press Ok when the settings are correct and Restart NTL Studio
5. Change Router and Firewall Settings (Required For Connect-Backs)
Forward port 3002 on your router to the IP address of your NTL Studio computer on port 3002 (Can be done under port forwarding on most routers)
Permit TCP Port 3002 on the Computers Firewall
Add a Static Reservation on the router for your NTL Studio Computers IP Address
6. Verify iConnect Studio works by connecting a unit
Open iConnect Studio Management & Distribution - you shouldn't get any errors when opening
Try connecting directly to a unit and doing a connect back to verify that everything works - in order for a connect back to work you have to have distribution open as well
If you have any problems try troubleshooting with the articles in this knowledge base