Task Server 7.0 SP5
| Article:DOC2154 | | | Created: 2010-05-17 | | | Updated: 2010-10-15 | | | Article URL http://www.symantec.com/docs/DOC2154 |
Description
Build number 7.0.8641
Task Server is an infrastructure component of Symantec Management Platform that provides task sequencing and automation for solutions that integrate with the platform. The functionality is similar to what Deployement Solution provides with its Job engine, but it is built on the Notification Server piece of the platform. This allows all integrated solutions to take advantage of its powerful features.
This component is part of Symantec Management Platform 7.0. For all platform release notes, see knowledgebase article 49812.
This document contains the following topics:
Installation and upgrade
Prerequisites
Task Server computer requirements are as follows:
- Microsoft .NET Framework versions 2.0
- Windows Server 2003 or Windows Server 2008 32-bit or 64-bit.
- Symantec Management Agent
For desktops, Windows XP SP3 32-bit is required.
Task Server minimum hardware recommendations are as follows:
- Intel Pentium 4 processor or equivalent
- 1 GB RAM
- 1 GB disk space
Before installing Task Server on any version of Windows 2008, you must do the following:
- In Server Manager, ensure that the web services role is selected. This installs IIS 7.
- Enable the following options when installing the web services role:
- IIS6 compatibility tools
- (Under Application Development) ASP.NET
- Windows Authentication
- After installing the web services role, run the following command.
Warning! You must run this command before installing Task Server, not after; otherwise, the Task Server will not function:
%systemroot%\system32\inetsrv\appcmd set app "Default Web Site/" /applicationPool:"Classic .NET AppPool"
New installation
You can install this product by using the Symantec Installation Manager. You can download the installation files directly to your server or you can create offline installation packages.
For more information, see the Symantec Management Platform Installation Guide (knowlegebase article 45732).
Upgrade
You can upgrade this product from 6x versions if you run the Symantec Installation Manager on a Notification Server 6x computer. To upgrade from the 6x version, you must first upgrade your 6x Notification Server to Symantec Management Platform 7.0 or later.
For more information, see the Symantec Management Platform Installation Guide (knowlegebase article 45732).
Ports used by Task Server
Task Server uses ports 50120-50124.
Installation and upgrade issues
There are no known installation or upgrade issues for this release.
Fixed issues in this release
The following are previous issues that were fixed in this release. If additional information about an issue is available, you can read it by clicking the Article ID link.
| Issue | Article ID | Internal ID |
Sample Task "Turns on Altiris Agent Upgrade" points to deleted policy.Even though the sample task pointed to a deleted policy, the agent upgrade policy could still be used to perform the upgrade. |
N/A | 1862465 |
Script task doesn't work on Windows Server 2008 x64If a script requiring user input is run on Windows Vista/2008 or later, you must run it as locally logged-on user. This is by Microsoft Windows design. |
N/A | 2115526 |
Things to know
The following are things to know about in this release. If additional information about an issue is available, you can read it by clicking the Article ID link.
| Issue | Article ID | Internal ID |
Pop-up dialog box is blank when selecting Edit/New icon on "Update summary data" dialog.For Notification Server to run properly, you must be able to install (or be prompted to install) ActiveX objects. If your IE settings prevent the ActiveX control from running, you will see errors when working with jobs and tasks. This is by design. |
53191 | 1850633 |
Known issues in this release
The following are known issues for this release. If additional information about an issue is available, you can read it by clicking the Article ID link.
| Issue | Article ID | Internal ID |
System.Net.Sockets.SocketException observed while trying to restart the Task server services (Altiris Object Host service)In some cases the agent cannot register with task server, preventing users from running tasks on agent computers. This is a known issue for this release and is under investigation. |
N/A | 2111808 |
Initial use of ‘.\username’ causes any script tasks specified as Machinename\username) to fail with error ‘Unable to open the file’ because of Profile loading problem.This issue applies only to some operating systems, such as Window XP SP2 and Windows 2003. It does not apply to pre-Vista versions such as Windows 7 or Windows Vista Ultimate SP2. |
N/A | 2069614 |
Task Server Task runs even though "Allow other tasks to run while running this task" is checked.
|
53009 | 1809168 |
Error when stopping a running task.
|
53035 | 1837026 |
Error when deleting a running task.
|
53036 | 1839882 |
A window is not displayed when cmd.exe is running in Task Manager as System even though the Show Script in a Normal Window option is selectedA new Windows 2008 security feature called "Session isolation" most likely causes this error. Related to incident 2115526, which was fixed. |
54050 | 2068705, 2115526 |
|
Changing the tickle port in config and UI does not cause the tickle port to actually change. If you change the tickle port under Site Server settings, or in the config from the default of 50123, the change is not made. The server will continue trying to open 50123 which causes 'unable to connect to tickle server' errors in the log. |
1932572 281-899-606 |
|
The information contained in the Altiris Knowledgebase is subject to the Terms of Use as outlined at http://www.altiris.com/legal/termsofuse.asp.
|
|
Legacy ID
52918
Article URL http://www.symantec.com/docs/DOC2154
Terms of use for this information are found in Legal Notices
Thank you.