I've read this a few times and I'm not seeing it.
Is your problem that:
- They put a shortcut on the desktop?
- It's not the right desktop?
- They don't put a shortcut on any desktop?
I think that you're only seeing whichever problem with SWD? That in itself could be the problem... it's in the zombie-like state of advanced decay that we software vendors like to call "deprecated". There are still some valid use cases, but there are also known problems without planned solutions. Personally, I only use it for things without user interaction (including shortcuts).
Just to Clarify
The SWD packages are doing the following when installed individually
(1) Install the software and place a shortcut on the C:\Documents and settings\allusers\desktop
When they are installed in the template
(1) Package 1 installs as above i.e creates an application shortcut in C:\Documents and settings\allusers\desktop (which is what I would expect)
(2) all other swd packages in the template install the shortcut to D:\userdata\username\Desktop even though the short is set for all users
Example of the shortcut from the builder
SHORTCUT: "$DEFAULTDIR$\ARDINTF.EXE",AI_6.0,dir="$DEFAULTDIR$", allusers
seems like the variable is being replaced?? Try hardcoding it...
I find spotty results at best when deploying distribution packages using provisioning. I get around it by using the execute command option in the template and calling the exe, msi, or bat file. Then I use use the command line options to set the installation defaults by either calling a answer file or using switches.