Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

SWD Tasks and SEP

Created: 23 Jun 2011 | 1 comment
jpn010@tower's picture
0 0 Votes
Login to vote

Trying to work through the "SEP Integration" for NS7.1, which seems significantly scaled down from previous versions.  The trouble I am having is that it seems that the process is to simply upload the packages and this will allow you to create install tasks (the SEP Integration installation adds some additional canned tasks as well that are fairly uneventful).  Well, these SEP install tasks can be scheduled to run, but the target remains static, so this is essential only useful for one-off installations.  Which leads me to the thought that the only way to ensure that the SEP client gets rolled out properly to all computers is to throw the package in a standard SW package and create a managed delivery policy.  Is this the case?  There seems to be very little use to the SEP Integration component unless I'm missing the boat completely on this (which I hope I am).  Any insight is appreciated.

Another item I'm thinking I have to be just stupid on... how do a setup a managed delivery policy or task to "Run Once ASAP" like you could do by checking the box in NS6?  Driving me nuts that I can't figure this out.  I looked back at the CMS 7.x training manual and I see in the labs they just had you schedule policy to run "2-3 minutes from now."  I hope this functionality wasn't pulled?!

Thanks in advance for any and all guidence.

Joe

Comments

jharings's picture
27
Jun
2011
0 Votes 0
Login to vote

I agree with your perception

The SEP Integration component has lost some of it's value from 6.x to 7.x. The main benefit I see is being able to schedule inventory to client systems, but there is no direct tie-in to the database like in 6.x.

The IT Analytics component provides more value for reporting purposes, and does allow connections to the SEPM databases.

You can schedule the managed policies to run within certain windows, check for compliance, and then remediate if necessary. You can't do the run once ASAP with managed policies like you can do with tasks in 6.x.

Have you tried creating a filter on version which should help avoid the static target issue? The migration jobs may already take that into account.

Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.