2.1.1 Microsoft Windows

2.1.1.1 Preparation

For Windows platforms, do the following prior to installing SquidNet:

  • Make sure you have admin rights to host.
  • Disable User Account Control (UAC) Settings.
  • Completely disable firewall or enable the following ports:
  • TCP Port 17394
  • UCP Port 17395-17400

Note

The SquidNet service will attempt to create these firewall profiles on startup.

  • Create a dedicated SquidNet Service Account (SSA):
  • Must be an administrator account. It’s ok to use the default “administrator” account.

  • Use administator credentials when installing SquidNet on each Windows computer.

  • Name SquidNet admin account accordingly. Typical account names are “render”, “rendermanager” or “squidnet”

  • Make sure the same SSA account and password is used on all nodes.

  • To create a SquidNet admin account from the command line shell do the following:

    Create user and add to administrators group:
    
        net user /add <username> <password>
        net localgroup administrators <username> /add
    
    To verify account creation:
    
        net localgroup administrators
    
  • If using a domain controller:
  • Make sure to assign network access permissions to SSA account.
  • Make sure to added SSA account to Local Administrators Group on every render node.
  • To test SSA account, log in on to any Windows computer and make sure you can access all network resources (shares, mapped drives, etc…) by creating and deleting some temporary files.
  • If using a cross-platform render farm, update Windows’ hosts file (C:WindowsSystem32driversetchosts) with the IP addresses and node names of Mac OS or Linux nodes.

2.1.1.2 SquidNet Service Account

2.1.1.2.1 Local System Account

On Windows, the SquidNet service runs under a system Admin account. This SSA (SquidNet Service Account) must have full admin permissions and be able to access local and network resources.

To verify SSA access permissions, on each Windows render node, create an administrator account (SSA) named “SquidNet” with a password of your choice. Once the account is created, log out of your current Windows session and log in again using the new SSA account. Make sure you can access any network folders on the network share folders. Try creating and removing some files on the network share while logged in under the SSA account. If you can access the network share without issue, you should be good to go !

If you already have an administrator account that can act as the SSA, you’re free to use that account. Just make sure that the account can access your network share and that you use the same account name and password on all Windows farm nodes.

2.1.1.2.2 Error 1069: The service did not start due to a logon failure

If installing SquidNet on a Windows Server 2xxx product, you might get a Error 1069 when trying to start the SquidNet service.

To resolve, do the following:

  1. Open Local Security Policy manager.
  2. In the console tree, double-click Local Policies, and then click User Rights Assignment.
  3. In the details pane, double-click Log on as a service.
  4. Click Add User or Group, and then add the SquidNet Administrator account to the list of accounts that possess the Log on as a service right.
  5. Open Services management app to restart SquidNet Service.

Note

If using a domain account, make sure to add the account as <domain>/<render_account>.

Source: https://technet.microsoft.com/en-us/library/cc794944(v=ws.10).aspx

2.1.1.2.3 Error 1314: A required privilege is not held by the client

Error 1314 - “A required privilege is not held by the client” may be encountered when an attempt is made to start a service on Microsoft Windows XP, 7, 8.1 or Windows server 2008 or 2012. If you receive this error code, do the following:

  1. Open Local Security Policy manager.

  2. In the console tree, double-click Local Policies, and then click User Rights Assignment.

  3. In the details pane, add the SquidNet Administrator account to the following:

    • Act as part of the operating system
    • Log on as a service
    • Replace process level token
  4. Open Services management app to restart SquidNet Service.

Note

If using a domain account, make sure to add the account as <domain>/<render_account>.

Source: http://www-01.ibm.com/support/docview.wss?uid=nas8N1019929

2.1.1.2.4 Side-by-side Configuration Errors

Side-by-side Configuration errors are caused by missing C++ runtime components or corrupted DLLs on the local host. If you get this error for any SquidNet application, please install the following:

2.1.1.2.5 Windows 10 Render Account

For Windows 10, if not using a domain account, it may be necessary to create a local render account. This local account resides on the local host and is not an Online Microsoft account which requires a valid email address. To create a local render account on Windows 10, please do the following:

  1. Open Windows’ User Account interface.

  2. Create new account.

    _images/create_render_account_add_1.jpg

    Figure 1: Windows Account Manager.

  3. Select “I don’t have this person’s sign-in information”.

    _images/create_render_account_add_2.jpg

    Figure 1: Create Local Account.

  4. Select “Add a user without a Microsoft Account”.

    _images/create_render_account_add_3.jpg

    Figure 1: No Microsoft Account.

  5. Enter account information. Example: “render” account with a private password. Any valid render account name and password will suffice.

    _images/create_render_account_add_4.jpg

    Figure 1: Account Credentials.

  6. Set the render account as an Administrator account.

    _images/create_render_account_add_5.jpg

    Figure 1: Render Farm Administrator Account.

    Important

    Make sure you create the same account and password on all render farm nodes.

2.1.1.2.6 Domain System Account

If using a domain account, the domain controller determines which service accounts can register a process as a service. This user right is defined in the Default Domain Controller Group Policy object (GPO) and in the local security policy of workstations and servers. By default, no accounts have the privilege to log on as a service.

To add the “Log on as a service” right to an account for a Group Policy object, when you are on a server that is joined to a domain or a domain controller:

  1. Click Start, point to Run, type mmc, and then click OK.

  2. On the File menu, click Add/Remove Snap-in.

  3. In Add/Remove Snap-in, click Add, and then, in Add Standalone Snap-in, double-click Group Policy Object Editor.

  4. In Group Policy Object, click Browse, browse to the Group Policy object (GPO) that you want to modify, click OK, and then click Finish.

  5. Click Close, and then click OK.

  6. In the console tree, click User Rights Assignment.

    Where?

    GroupPolicyObject [ComputerName] Policy

    Computer Configuration

    Windows Settings

    Security Settings

    Local Policies

    User Rights Assignment

  7. In the details pane, double-click Log on as a service.

  8. If the security setting has not yet been defined, select the Define these policy settings check box.

  9. Click Add User or Group, and then add the appropriate account to the list of accounts that possess the Log on as a service right.

If the above settings are not set on the domain controller, you can apply the same settings on each render node by doing the following:

  1. Open Local Security Policy manager.

  2. In the console tree, double-click Local Policies, and then click User Rights Assignment.

  3. In the details pane, add the domain account (ex: domain\administrator) to the following:

    • Act as part of the operating system
    • Log on as a service
    • Replace process level token
  4. Open Services management app to restart SquidNet Service.

Source: https://technet.microsoft.com/en-us/library/cc794944(v=ws.10).aspx

2.1.1.2.7 Windows 10 Render Account

Because of Microsoft’s new user accout security measures for Windows 10, it may be necessary to create a unique “render” account on each render farm node. To create an account, please follow these instructions:

2.1.1.3 Basic installer

To install SquidNet using the WINDOWS installer, execute the following instructions:

  1. Make sure you have the latest version of the SquidNet installer available. Always check website for the latest updates.

  2. Run installer then select “Next” on first window.

    _images/install_01.png

    Figure 1: SquidNet Installer.

  3. Please read and accept the license agreement (ULA) then select “Next”.

    _images/install_02.png

    Figure 2: User License Agreement.

  4. Set your installation directory. The default path is recommended.

    _images/install_03.png

    Figure 3: Install directory.

  5. Enter Windows Admin account information. Select “Install” and wait for the installation to complete.

    _images/install_04.png

    Figure 4: Service Account Information.

    Hint

    • To be consistent, use the same account name and password for all installations (Example: user: render/pass: xxxxx)
    • For SquidNet to work correctly, you must install the software under an Administrator account with full network access privileges. The username format must be in “DOMAINaccount” for domain accounts or “HOSTNAMEaccount” format for non-domain accounts. For domain accounts, please make sure that your domain controller is reachable on the network. If it’s not reachable, you will not be able to install the software. Please consult your domain administrator for specific account information.
    • Important: Make sure that network File Sharing is enabled. If it isn’t, the following step will not work; you’ll get a “server not found” error message.
  6. When completed, select “Close”.

    _images/install_05.png

    Figure 5: Service Account Information.

  7. By default, the installer will automatically start the SquidServer service. However, in some rare situations this may not be the case (due to service pack incompatibilities). To verify that the installation succeeded, start the SquidNet user interface console. If the user interface console starts up, you’re all set. If not, either start the service with the services manager or reboot your computer.

    _images/serviceman.jpg

    Figure 6: Windows Service Manager.

    Hint

    You can start the Windows Service Manager from the “run” prompt. Just type in “services”

  8. Use Windows’ Task Manager to make sure that the SquidServer.exe service is running.

    _images/taskman.png

    Figure 7: Windows Task Manager.

2.1.1.4 Upgrading to a newer version of SquidNet

_images/net_install.png

Figure 8: Network installer.

Once you have all your nodes installed, you can update all the nodes on your farm at one time with a few steps:

  1. Download new SquidNet installer (example: squidnet-x.xx.exe ).

  2. Update your local node (preferably the master node).

  3. Start the SquidNet User Interface.

  4. Open up a network view window.

  5. Make sure that all your nodes are running then select all nodes that you’d like to update, right-click and select “Upgrade software version…” (see pic above)

  6. When prompted, select the UNC path to the new SquidNet installer.

    Important

    The SquidNet installer must reside on a network share path (mapped drive or UNC path).

  7. That’s it!!

Warning

Although all SquidNet operations will function with UAC enabled, remote SquidNet updates will not function because WINDOWS UAC requires user consent for all software installations. Therefore, to ensure that remote upgrade operations will work, it’s recommended that WINDOWS UAC be disabled.

2.1.1.5 Uninstall

Use the standard WINDOWS uninstaller to uninstall SquidNet