As a function of our IEM implementation, we are going to move PCs in and out of sites for both patch and software deployment. So once the device is completed within that site, it is moved into production patch/software deployment sites.
Question is, how do I test relevance for all the baselines? we are planning on a numbering system based on a registry key value. 0 post imaging software deploy / setup tasks, and 1 being normal software deploy based on it’s usage. I need to be able to flip it from 0 to 1 once it’s done with post imaging software deploy. I would assume a task would do that, but how would the relevance be set up?
Ideas? I know they were talking about a similar concept at Interconnect for patching (one site for your current 1 year back patches, and one site for things older), and I wasn’t sure how to accomplish this.
If you have a baseline in any actionsite, the origin site where the fixlets came from has to be subscribed to by the client to have the baseline relevant. Before anyone says anything I know in old agents this was broken sometimes so often the outer wrapper needed an extra exists site "blah" but that was addressed in most recent clients.
This would enable you to essentially unsubscribe the “prep” site from the agents. You could do this by having your clients be part of a manual group of “Preproduction” and “Production” and having sites subscribe based off this group.
I’m sure there are many other ways of doing this, this is just one suggestion if I’m understanding the issues.
I guess what I’m trying to accomplish is within the relevance loop of the baseline (and correct me if I’m going down the wrong path here), have some trigger (like in this screen shot) to decrement or just change some setting to move it to the next old patch site.
However unlike in this screen shot, the decrements should no be relevant until all the other patches are no longer applicable. Any ideas on how to write that relevance statement?
Or maybe I don’t need the “Post Imaging - …” task in the baseline components. Just a task in the site with the appropriate relevance. I just don’t want to go down the list of updates without looping a few times.
I often have a case where a Fixlet won’t properly apply. Instead of looking at Relevant Fixlets, I check for Pending Actions, so the machine has a chance to give up eventually.
To exit my patching site, I check for a combination of “evaluated of site”, pending actions, system uptime, and pending restarts
Please forgive my n00b-ness, but I see that “evaluated of site” comes back in the QA tool at “true”, but I’m not sure what it’s returning. This doesn’t work:
valuated of site whose (it as name contains "Patch Remediation")
So Alan, that’s only supposed to give you the SITES your relevant to right? How do I evaluate IF I’m no longer relevant a set of baselines in a site? If I’m no longer relevant to those baselines, I want to run an action that will change a reg key, and that will them remove me from the patch remediation site.
That gives you if you have evaluated everything in sites. Anything that is “false” means the agent hasn’t yet completed evaluation of new content at least once
