1 of 1 people found this helpful
Are your Scheduled tasks in "My" or "Public" tasks?
I'm seeing exactly the same thing - but only when they're in public - move them to "my" tasks and it runs perfectly well.
I'm opening a ticket to LANDesk - as I have recreated it on my Test kit too...
Hope this helps
I haven't tried that! Good suggestion though. Can you post what you find from your ticket?
Watch this space
How did the suggestion go for you by the way?
Did it get you going?
Just tried it and I can't authenticate. It won't let me get to provisioning at all from the client.
Did LANDesk every get back to you?
After dragging my Provisioning tasks into "My tasks" rather than public, it worked fine - and I got word from LANDesk that I'm not the only one to report the issue - so it's with Engineering who are looking at a fix.
If this hasn't worked for you, check things like your Com+ objects - make sure they're logging in with a Domain Account (I've found it has to be Admin to ensure it works fully) instead of the local LANDeskComPlus account so that LDProvision is able to figure out if the user has access to use Provisioning...
Otherwise, is there nything in ldprovision.log?