If you setup the task to run from source, the installation takes place as the Local System account, so it won't have access to a share that only domain users has access to. You'll need to setup a null session share or use an http share.
Nulls may not be necessary depending on your infrastructure. Review pages 136-138 of the 8.7 manual. I believe you indicated you are using preferred server. Are you distributing Autoit via UNC or HTTP? I believe Paul indicated that if you use run from source that the credentials it uses to obtain the package and run it on the client is what is in preferred server credentials. So as long as your credentials you are using from preferred server have access to the package share and you are using UNC you should be good to go. Also, post some of the distro logs.
This doc also has some good stuff about share rights http://community.landesk.com/support/docs/DOC-1081
I created a null share according to http://support.microsoft.com/default.aspx?scid=kb;en-us;q289655. I also changed the group policy settings for the preferred server "network: restrict anonymous access to named pipes and shares" to disabled and added the share to "Network: shares that can be accessed anonymously." I tested the the null share using - net use
servername\sharename "" /user:"" . It said the task completed successfully which means the null share is working. I ran the scheduled task and received the message that additional files could not be downloaded. I also gave full control rights for the share to the domain account I used for the preferred. I am still not able to complete a SWD. As for the log files, there are none. The log file icon in the scheduled task window is grayed out.
To avoid problems of authentication, use http share and enable the anonymous access on the IIS.
You can also use the http share created in the Core Server (http://coreservername/ldhm-packages). The default path is: "Program Files\LANDesk\ManagementSuite\ldhm\packages\". This web site is already configured to use anonymous access.
If you need null session shares in the future just run c:\program files\landesk\managementsuite\utilities\SysShrs.exe
Log filesC:\Program Files\LANDesk\LDClient\Data\sdclient_taskXXX.log on the target machine.
I would review the documents listed above and post the log files. Also is the job that you are distributing unc or http?
Try using HTTP - if HTTP works, you have UNC access problems. That happens pretty easily - especially with 2003.
Now - regarding Null-session shares, they need some extra work in 2003 ...
(1) Run Sysshr.exe to create the null session share
(2) At the Start | Run line, run "gpedit.msc"
(3) Under Local Computer Policy | Computer Configuration | Windows Settings | Security Settings | Local Policies | Security Options, change the following:
A - Network Access: Let Everyone permissions apply to anonymous users - Enabled
B - Network Access: Restrict anonymous access to Named Pipes and Shares – Disabled
LANDesk EMEA Technical Lead