I explained a little bit of the process for creating a software package in your other thread, but you'll want to go to Manage > Software and then Add a software resource into the software library. This involves importing files (might just be an .msi, might be a folder's worth of files, might be an .exe and a transform) and defining command lines. There's an option for 'Add transforms to be applied to the MSI at run-time.' This is under Transform Options when you are editing the command line. The transform must already be uploaded as part of the Package Folder.
Make sure you're using the Software Library and uploading the transforms when you create the resource. You cannnot apply MSTs if the packages exist on a UNC source. You get some leverage by using the Software Library because there is more information stored in the database on manufacturer, version, etc -- even MSI Product Codes.
So rather than write a script that you tell the clients to run against the DFS share, you import the files from the DFS share into the Software Library (a storage repository the NS can access) as part of a package. The command lines are all defined there, so there's no scripting involved -- just send the package to a computer. It doesn't need access to the DFS share or the Software Library; the NS will grab the files and deliver them to the client. The client then runs the commands you've specified against the package.
Another benefit to defining software packages is that you can have a single package with multiple command lines (Uninstall, Install, Repair, Install - no UI, etc), so there's a little less clutter in your "job" listing.
Jobs exist in SMP7, but primarily for the purpose of adding logic or nested scenarios: e.g. do this, then do this, then do this, then reboot, then do this. In SMP7, software installs like you describe will be sent via policies (check for compliance on a schedule or run on a schedule) or tasks (run now!). So your jobs from DS 6.9 will either be jobs in SMP7 (if they require logic or nested actions with predecessors) or tasks (if you want to send it now).
Does this answer your question?