Client Management Suite

 View Only
  • 1.  Deploy Software Using DS 7.1

    Posted Jun 12, 2010 10:41 AM
    I have a question about deploying Software using DS 7.1.
    I have a DFS share that we use to keep all our apps. In using DS 6.9 we would create jobs and point the to the DFS share for the source files including he MSTs. I would like to do the same in DS 7.1. When trying to create this job I don't clearly see the option to do this. I do see options for package creation and am also not sure what that is about as well. SO my two questions are can I deploy software in DS 7.1 the same as I did in DS 6.9 and how also what is the software package deployment in DS 7.1? Any help is much appreciated.


  • 2.  RE: Deploy Software Using DS 7.1

    Posted Jun 14, 2010 10:27 AM
    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?


  • 3.  RE: Deploy Software Using DS 7.1

    Posted Jun 14, 2010 06:03 PM
    Thanks for the info. To make sure I understand you. I Will need to import my Source Files to the Software Repository on the NS box and not be able to send jobs from my DFS. Also will those Files in the software Repository be pushed down to site servers? I will have 7 Site Servers and wanted to leverage my DFS so I wouldn't have to worry about Disk Space and all these boxes as my Site Servers are work stations with Server OS s on them. Not to speak about Bandwidth. ANy help is much appreciated.


  • 4.  RE: Deploy Software Using DS 7.1

    Posted Jun 14, 2010 06:09 PM

    You can create software resources that use \\UNC, but you cannot apply transforms to \\UNC locations.

    If the packages are needed, site servers will store them.  If they become unneeded, site servers will delete them.  The timing on this is specified in various settings on when to purge unneeded packages.  Check your Settings > Notification Server > Site Server Settings.

    Not sure what you mean about bandwidth.  If you have a single HQ with 10 sites each with 30 nodes, using DFS that's 300 downloads to the site.  If you use software library, the packages replicate to the site servers and you have only 10 downloads, one to each site.