It sounds like your batch file is the issue, not LANDesk. You should test your batch file while using psexec.exe (-s -i I believe) and make sure it works as you wish. Using psexec with those switches should run it as the local system account, the same that LANDesk uses.
You might need to use MD (make directory) or other commands. Once you get your batch file to work properly in this context, LANDesk should be able to push it out fine.
No no, I'm not talking about batch content...
Try this :
- Make a new batch package
- Target a batch file, whatever
- Add additionnal files structures c:\LD with empty folder in, such as :
* c:\LD\test3\ <<<< empty folder
- Launch the package on a client
- Look in sdmcache, folder c:\test3 is not here
OK, I just never thougth of doing it that way. I would recommend that you have create a batch file that does all that you want, and use that as your package.
These packages are just files deposit, I don't want to batch it (or minimum, batch content : xcopy *.* c:\)
Nobody use LANDesk to update the content of a folder ? You all just deploy softwares or batch actions ?
Imagine, you have a repository master folder containing 100 subfolders with 500 files on it (including empty folders).
You have 400 servers which have exactly the same structure, the same files.
You have to modify 20 files in differents folders.
Now you want to send all my master folder to 400 servers
So you have to make a new batch package (what other option ??)
You put your master folder on additional files option (including empty folders)
Your batch is : xcopy *.* C:\ /E /Y (pretty simple)
Now you start the task, and you verify sdmcache folder on target : empty folder are not included
And my other point : why we don't have a "deposit folder/files package" option in landesk (source : \\nas\xxx ; destination c:\nas, JUST THAT) ? It would be easier than making a batch...