You're not likely going to be able to deploy this to a *DESKTOP*, because the Windows Update Agent runs in the SYSTEM context, and as such does not have access to user folders. At best, you could use WSUS/WUA/PatchManager to deliver the installer to a SYSTEM location and then complete the process using a LOGON script that runs in the user's context.
But... why not just RUN the installer and install the product?
Ehhh.. I overread the statement. You simply meant that you're trying to deploy it to every computer.
I read "Desktop" a bit too literally... but the rest of the post still applies.
Applicability Rules: when either ProcArch=x86 or ProcArch=x64
Installed Rules: when either ProcArch=x86 or ProcArch=x64
These are not really appropriate Applicability Rules (and they're redundant with the Prerequisite Rules, which is the proper place to define them),
and they're totally useless as Installed Rules -- in this package the Installed Ruleset always returns TRUE so nothing is going to happen.
My suggestion would be to build the correct rules and test with that.
Or is there a tutorial on how to create a third-party package
There are these and I would highly encourage you to watch both of these webcasts
Package Creation Using Patch Manager
Additional webcast, video, and training resources are available on the Patch Manager Library and Support page in Thwack.
