Client Management Suite

OK - I  posted this here a while ago

https://www-secure.symantec.com/connect/forums/copy-file-job

Now - I would have thought that upgrading to the latest version of CMS - this at least would work.....nope - still the same.

Can anyone confirm if they have this working. I have a file copy job task that works if I run directly against the task. If I create a policy with this single task, it fails.

Can anyone confim if this is a bug or it should work?

Joe.

We actually did have the same issue but after installing Rollup 3 and then actually repairing our Task Server it started working again. It seems the task server was causing us a lot of issues as Patch Management had also been erroring for no reason. Once we removed all of the agents and roles and then added them back in, we had a functioning box and functioning tasks including the copy task.

I'm running the latest version. Other policies work OK. I have  a workaroud. Just sick of stuff not working thats meant to work on this product.

I am seeing this issue as well, just put a ticket in 

I believe I did a while ago, wasn't resolved, just used workaround. didn't have the time to keep chasing it up.

Thanks

Support is telling me doing a file copy as part of a policy is not best practice.  

" I am attaching a KB link that "explains" the copy file task as related to running as or within a policy.

Here's the link: http://www.symantec.com/docs/TECH184268"

I'm still pursuing with support - but for now have done the task via script using xcopy.  

yep - went with xcopy as well. sometimes the oldies are the best :-)

Thanks.

Sooo, uh, yeah, there are some tasks from DS that will not work in a policy because of how they're processed.

When a DS task with an "@" token in it (e.g. @Compname) is run, it is NOT evaluated at the server, and it is NOT evaluated at the client.  It is evaluated by the DS Task Server Handler DLL on the Site Server.

So, when you run these in a policy, sure the SMP sees it, and the client sees it, but since it doesn't go THROUGH the task server, the tokens are not populated and the tasks fail.

<sigh>

Like the KB mentioned indicates, this is, indeed, a rather complex fix to make work and is a feature request.

Why do I sigh?  Because in many cases we would prefer if post deployment tasks were run via policy - OH - but WAIT - you can't.

<double-sigh>

Thanks, Thomas