Unable to Register with Task Server
search cancel

Unable to Register with Task Server


Article ID: 176992


Updated On:


IT Management Suite Task Server


Client Machines are unable to register with Task Servers.

Symptoms include:

  • Unable to run tasks/jobs
  • Various error messages in the NS Agent log files
  • Task Server Management Page on NS shows 0 client registered


For proper functionality, Task Server depends on the local computer account for Microsoft's ASP.NET to have sufficient NTFS permissions to work with the Task Server program files. In this case, the problem was caused by insufficient NTFS permissions on the
"Program Files\Altiris\Altiris Agent\Client Task Server" directory.


Begin by confirming there is indeed a NTFS permissions issue by performing the following test on the Task Server:

  1. Open IIS Admin
  2. Browse to Default Web Site > Altiris > Client Task > Server > Right-click on Authenticate.aspx and choose Browse.
  3. If a NTFS permission error occurs, make note of the path specified and continue to the next step.

After verifying there is a problem with NTFS permissions complete the following:

  1. In Windows Explorer, open "Program Files\Altiris\Altiris Agent\"
  2. Right-click on the "Client Task Server" folder and choose Properties
  3. Select the "Security Tab"
  4. Ensure that the local "Users" group has Read & Execute, List Folder Contents and Read permissions. The typical format of this account is COMPUTERNAME\Users.
    The reason this is required is that by default the ASP.NET computer account used by Task Server is a member of the Local Users Group. Without permission to this directory Task Server will fail to operate.
  5. If "Users" is not listed, add it and then click on the "Advanced Button" and choose the option to "Replace permission entries on all child objects with entries shown here that apply to child objects" then click OK.
  6. This should resolve the problem. If not, take a look at Altiris KB 32117 or Altiris KB 43668 or Altiris KB 46962 for additional troubleshooting steps.

Applies To
Task Server 6.0.1505 (SP2)