Installing Task Server in IIS 7.0 or 7.5

Article:HOWTO47804  |  Created: 2011-03-30  |  Updated: 2015-03-25  |  Article URL http://www.symantec.com/docs/HOWTO47804
Article Type
How To




To install task server on any server operating system, it is required to have following components. If the requirements mentioned below, are not met then task server will not function correctly:

Prerequisites:
1) IIS is Required
- Select "Web Management Tools" with all sub-components (IIS 6 Management Compatibility, IIS Management Console, IIS Management Scripting and Tools, IIS Management Service)
- Select "World Wide Web Services"
- Select "Microsoft .NET Framework 3.0" (If the option is available)
- Make sure that ASP.NET and ASP are selected

2) Application Server is required
- Select "Microsoft .NET Framework 3.5" (If the option is available)
- Select "IIS Support"
- If Site server is also going to be used as Mobile Management server, then enable "Message queuing Activation"

3) Firewall (Windows or any other third-party) needs to have provision for inbound/outbound connection allowed on Port 50120, 50121, 50123, 50124. Please note this ports are specifically used for Task server, Symantec Management Platform uses other ports as well for various purposes. For more information, please refer to product user guide.

Post Configuration:

Pre-SMP 7.5 SP1:
1) Classic App Pool
Task doesn't know how to use the new methodology in IIS 7 for the Default App Pool.  Therefore, you will need to direct Task Server to use the Classic App Pool.  There are a number of ways to do this, but the easiest way is actually after the installation of Task on the server.  Once the product is installed, go into IIS, and under Default Web Site\Altiris, select ClientTaskServer.  Edit the Basic Settings and select the Classic App Pool instead of the Default App Pool.
 

Post-SMP 7.5 SP1:
Starting from SMP 7.5 SP1, Task Server installs its own Application Pool into IIS7. Previously Task Server have using Default Application pool). That pool is configured by the Task Service to have 'Integrated' Managed Pipeline Mode.
Every time Task Service restarts it makes sure the settings of the application pool are correct, if not, the settings are corrected and Managed Pipeline Mode is set to 'Integrated' back.

 

Question:
Is it supported for customer to create a separate application pool for client task server on a site server in 7.1 SP2 MP1.1 with Rollup v10 or v11 (HOWTO81832)? 

Answer:
Yes, that should work correctly assuming app pool is configured correctly.

 

Question:
Pre-SMP 7.5 SP1, can I call the application pool name: 'TaskServer' for example.  I could then assign the Client Task Server to that application pool with .NET Framework 2.0, Managed Pipeline Mode (Classic or Integrated), and the Identity of ApplicationPoolIdentity. Doing that should allow the product to function just fine.  Correct?

Answer:
Correct. But as you know starting from ITMS 7.5 SP1 Task Server creates own application pool. That is introduced in order to have isolated application pool (exclusively for Task Server) what can be configured independently of other pools (what can be used by other applications).
So, You are correct, name of pool does not actually matter, properties of pool do matter. However,  starting from 7.5 SP1 we would recommend to use Task Server’s application pool.


 

See also HOWTO47803 "Installing Package Server in IIS 7"





Article URL http://www.symantec.com/docs/HOWTO47804


Terms of use for this information are found in Legal Notices