How to change the account that runs ZyNET

SYMPTOMS

By default ZyNET will run under the application pool of the ‘Root’ however this can be configured.

ZyNET is associated to an application pool. It is possible to configure a different location, you can convert the source folder/executable in Internet Information Services to an application, create a new application pool and assign the new exe application to be run under this application pool. In addition you can change the identity of the application pool to the service account that you want to use for ZyNET.exe.

According to Microsoft:
Whenever a new application pool is created, the Internet Information Management process creates a security identifier (SID) that represents the name of the application pool itself.

For example: if you create an application pool with the name "MyNewAppPool," a security identifier with the name "MyNewAppPool" is created in the Windows Security system.
From this point on, resources can be secured by using this identity. However, the identity is not a real user account; it will not show up as a user in the Windows User Management Console.

The ZyLAB Information Management installer will apply an account during the installation phase however this account association can be changed later on.
Concerning the Managed Pipeline Mode, when the value is set to Integrated, Internet Information Services uses the integrated Internet Information Services request-processing pipeline to process requests in the application pool. This is recommend however you can modify this option.

CAUSE

Not applicable.

RESOLUTION

• From the Computer Management console you can open the Internet Information Services (IIS) Manager.
• Select the applicable computer node.
• Open the Application Pools section.
• Open 'Advanced Settings' of the ZyNET_FCGI application pool.
• Navigate to the Process Model section
• Go to the ‘Identity’ section of the 'Application Pool Identity' window and double-click to change.
• Click on Set and enter the credentials of the Service Account.
• Make sure that this account is part of a group that has sufficient privileges to run within the application pool.

APPLIES TO

6.3; 6.4; 6.4 SP1