- Initial Deployment may display the menu, allow you to select it and then not execute.
- Computers may be assigned a job in production (i.e. sysprep), reboot and then do nothing in Automation even though you verify network connectivity.
- Computers in automation may be assigned a task and not run it even though they show active in the console. You may be able to assign a command script but all DS tasks fail.
These symptoms may occur for other reasons, there is a sure-fire way to diagnose this particular problem.
- Verify that the PECTAgent has launched.
- Once it has run for a few minutes, read the pectagent.log file looking for "Tickle". This is the line where the pectagent establishes its connection with the Task Server for receipt of tasks.
- On this line you should see the name of the Task Server. Go to the task server and verify it has a Deployment share on it (that is, the Deployment Task Handlers are installed). If not, this is the problem.
Note: If you establish the tickle connection, you obviously have network connectivity.
This happens because we have connected to a Task Server that doesn't have the Deployment Server plug-ins installed (including the Deployment Share). We tell the agent what NS to communicate with but do not have any way of verifying that the task server assigned also has the appropriate Deployment services or files. Deployment Tasks assume they will run from the Task Server for source locations.
Thus, if we connect, to one of these servers, we may receive the tasks, and we may even run certain types of tasks, but any task that requires the Deployment Share to run will fail because they can not connect to or receive the appropriate files.
The resolution to this is to be sure all your Task Servers also have the Deployment Plugins.
You should ensure they are Package Servers to be sure that images captured on other Deployment site servers get replicated to this one since that replication process uses the built-in replication of Package Servers.
Imported Document Id