Windows Server Configurations

Perform the following Windows Server specific configurations for CampusNexus CRM components.

Configure the Database Component

If Database is installed in a distributed environment, perform the following procedures on all the distributed computers.

Configuring MSDTC Settings

  1. From the Start menu, select Run.

  2. Type dcomcnfg. The Component Services screen is displayed.

  3. Browse to Console Root, Component Services, Computers, My Computer, Distributed Transaction Coordinator, Local DTC.

  4. Right-click Local DTC and select Properties. The Local DTC Properties dialog box is displayed.

  5. Click the Security tab.

  6. Select the Network DTC Access option.

    1. Select Allow Remote Clients.
    2. Select Allow Remote Administration.

  7. In the Transaction Manager Communication area, select the following options:

    • Allow Inbound
    • Allow Outbound
    • No Authentication Required
    • Enable XA Transactions
    • Enable SNA LU 6.2 Transactions

  8. Click OK.

Configure RPC Security for MSDTC

Perform the following steps on Windows computers where CampusNexus CRM databases are hosted.

  1. Open the Registry editor on the computers where CampusNexus CRM databases are hosted.

  2. Navigate to the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC.

  3. On the Edit menu, click New, DWORD Value, and create a new value called TurnOffRpcSecurity, and set its value to 1.

 

Configure Web Components

On the Windows Server computer where any or all the Web Components are installed, perform the following steps:

  1. From the Start menu, select Run.

  2. Type inetmgr. The Internet Information Services (IIS) Manager is displayed.

  3. Ensure that all the virtual roots configured for Web Components are configured with a valid Windows user as the Anonymous User. To do so:

    1. For every virtual root, select Basic Settings from the right pane. The Edit Site dialog box is displayed.

    2. Click Connect as, Specific user, Set and set the domain user credentials in the Set Credentials dialog box.

  4. Configure the identity account for the Application Pool under which the Web Components are running. To do so:

    1. In the right pane, click Advanced Settings. The Advanced Settings dialog box is displayed.

    2. Navigate to the Process Model area and click the ellipsis in the Identity field. The Application Pool Identity dialog box is displayed.

    3. Select the Custom account option and click Set.

    4. In the Set Credentials dialog box, specify the domain user account details.

    5. Click OK.

  5. Ensure that the Allowed option is enabled for all the ISAPI and CGI Extensions. To do so:

    1. Select the Web server node in the IIS Manager.

    2. In the right pane, double-click ISAPI and CGI Restrictions.

    3. Ensure that the Allowed option is enabled for all the ISAPI and CGI Extensions.

    4. For both the ASP.NET v4.0.30319 extensions, click the Edit Feature Settings link.

    5. In the Edit ISAPI and CGI Restrictions dialog box, ensure that the two check boxes are selected and click OK.

 

Configure Job Service Framework and Application Server

Grant remote access permission to Domain Users on Windows computers where Job Services Framework (JSF), and Application Server are installed.

  1. From the Start menu, select Run.

  2. Type dcomcnfg. The Component Services screen is displayed.

  3. Browse to Console Root, Component Services, Computers, My Computer.

  4. Right-click on My Computer, and select Properties. The My Computer Properties dialog box is displayed.

  5. In the COM Security tab, click Edit Limits in the Access Permissions area.

  6. In the Access Permissions dialog box, select the Distributed COM Users group, and select the Allow option for all the permissions.

  7. Click OK.

  8. In the Launch and Activation Permissions area, click Edit Limits.

  9. In the Launch Permission dialog box, select the Distributed COM Users group, and select the Allow option for all the permissions.

  10. Click through OK twice.

  11. For Job Services Framework, browse to the DCOM Config, TLSCMgr node.

    — OR —

    For Application Server, browse to the DCOM Config, Talisma Information Server node

  12. Right-click the node, and select Properties.

  13. In the General tab, select the Authentication Level as Connect.

  14. In the Security tab, select Customize in the Launch and Activation Permissions area, and click Edit.

  15. In the Launch Permission dialog box, click Add.

  16. Type Everyone, and click OK.

  17. Select Allow for all the permissions.

  18. Click OK.

  19. In the Security tab, select Customize in the Access Permissions area, and click Edit.

  20. In the Access Permission dialog box, click Add.

  21. Type Everyone, and click OK.

  22. Select Allow for all the permissions.

  23. Click OK.

  24. In the Identity tab, select This user, and configure a valid Domain User account.

  25. If you have configured the Job Services Framework, restart the Job Services Framework.

    — OR —

    If you have configured the Talisma Application Server, restart Talisma Application Server.

 

Enable Permissions on the Application Server

Domain Users need to be given permissions on the Application Server computer. To do so:

  1. On the Application Server computer, right-click the My Computer icon on the desktop, and select Manage. The Computer Management screen is displayed.

  2. In the left pane, navigate to System Tools, Local Users and Groups, Groups. In the right pane, double-click Distributed COM Users. The Distributed COM Users Properties dialog box is displayed.

  3. Click the Add button, and add the Users, or Groups who will be logging on to CampusNexus CRM.

  4. Click through OK twice.

  5. Close the Computer Management screen.

 

Configure the File Size for Compression

You can configure the file size for compression for Application Server and Client. By default, compression is disabled when connections to Application Server are made over a Local Area Network (LAN). To enable compression, follow these steps:

  1. On the computer where Client is installed, run Regedit from the command prompt. The Registry Editor is displayed.

  2. Browse to the following key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Talisma\Common\ConnectionParameters\LAN

  3. Right-click the DWORD values Request and Response, and select Modify from the shortcut menu. The Edit DWORD Value dialog box is displayed.

  4. Specify the required data size in the Value data field, after selecting Decimal in the Base area. Compression is enabled for DCOM connections. Requests and responses that are greater than or equal to the specified size are compressed.

Notes:

  • By default, the value for the Request and Response DWORDs for the LAN key is 0, indicating that compression is disabled. Setting a value greater than 0 enables compression.

  • Values specified in the Value data field must be in bytes, indicating the file size for which compression must be enabled.

By default, data greater than or equal to 1024 bytes will be compressed when connections to Application Server are made over HTTP. You can modify this value. To do so:

  1. Browse to the following key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Talisma\Common\ConnectionParameters\Internet

  2. Modify the DWORD values Request and Response, and specify the required data size in the Value data field, after selecting Decimal in the Base area.

 

Install ASP.NET on Application Server

  1. From the Start menu, select Settings, Control Panel. The Control Panel is displayed.

  2. Double-click the Add/Remove Programs icon. The Add/Remove Programs wizard is displayed.

  3. Click the Add/Remove Windows Components tab. The Windows Component wizard is displayed.

  4. In the Components list, select Application Server.

  5. Click Details.

  6. Select ASP.NET from the SubComponents of Application Server list, and click Details.

  7. Click OK.

  8. Click Next.

  9. When ASP.NET is installed, click Finish.

 

Configure the Imports on a 64-bit Computer

It is recommended to update the path of the dtexec.exe file to use the MS SQL Server folder for the Jobs created for Import Configurations.

  1. Log on to Microsoft SQL Server as an administrator.

  2. Expand the SQL Server Agent node.

  3. Expand the Jobs node.

  4. Double-click on the Job created for the existing Import Configuration. The Job Properties - <Job name> dialog box is displayed.

  5. Click on the Steps node in the Select a page pane.

  6. Double-click on the first Step in the Job step list: table. The Job Step Properties - <Job name> dialog box is displayed.

  7. In the Select a page pane, click General.

  8. In the Command area, update the path for the dtexec.exe file to the following:

    <System Drive>:\Program Files(x86)\Microsoft Sql Server\110\DTS\Binn

  9. Click the OK button.

  10. Repeat steps 4 through 9 for all the jobs of existing Import Configurations.

 

Log on to Web Components Using Custom Login

When Web Components are installed on a Windows Server computer with IIS, you must carry out the following steps to enable users to log on to Web Components using Custom security:

  1. Create an application pool in IIS Manager. To do so:

    1. From the Start menu, point to Programs, Administrative Tools, and select Internet Information Services (IIS) Manager. The IIS Manager is displayed.

    2. In the left pane of IIS Manager, right-click the Application Pools node, and select Add Application Pool. The Add New Application Pool dialog box is displayed.

    3. In the Application Name field, specify a name for the new application pool. This name will be displayed under the Application Pools node in the IIS Manager.

    4. Click OK. The new application pool is created, and is displayed under the Application Pools node.

  2. Set the security account for the newly created application pool as Local System. To do so:

    1. In the left pane of IIS Manager, expand the Application Pools node, and right-click the newly created application pool.

    2. Click Advanced Settings from the right pane. The Advanced Settings dialog box is displayed.

    3. Navigate to the Process Model area and click the ellipsis in the Identity field. The Application Pool Identity dialog box is displayed.

    4. Select the Custom account option and click Set.

    5. In the Set Credentials dialog box, specify the domain user account details.

    6. Click OK.

  3. Set the newly created application pool in the Properties dialog box for all the virtual roots representing the Web Components. To do so:

    1. In the IIS Manager, expand the Default Web Site node under the Web Sites node in the left pane.

    2. Right-click the required virtual root, and click the Basic Settings link. The Edit Site dialog box is displayed.

    3. Click Connect as and select the Specific user open and specify the Local User credentials in the Set Credentials dialog box.

    4. Click OK twice.

Users will now be able to log on to Web Components using Custom security.

 

Allow Active Server Pages

If Active Server Pages (ASP) are not allowed on the computer where Web Components are installed on a Windows Server computer with IIS, the login page for Business Administrator and other Web Components will not be displayed.

Perform the following steps on the computer where Web Components are installed, to allow ASP pages:

  1. From the Start menu, point to Programs, Administrative Tools, and select Internet Information Services (IIS) Manager. The IIS Manager is displayed.

  2. In the left pane of IIS Manager, select the <Computer name> (local computer) node.

  3. In the right pane of IIS Manager, double-click ISAPI and CGI Restrictions.

  4. Ensure that Active Server Pages is set to Allowed. This operation adds the .asp extension to the list of allowed file extensions.

The login pages for the various Web Components are now displayed.