Fixlet to unsubscribe workstations from site

Content Authoring
1

(imported topic written by murtasma91)

I had to rename several sites in our BigFix deployment. Since you are unable to rename a site once it’s created I had to create a new site and remove the old one. What I have noticed is workstations are still subscribed to the old site. I would be really nice if BigFix would automaticlly create an action to unsubscribe workstations subsribed to a site if you remove the site but this doesn’t appear to be the case.

Now I am sitting with a few unknown sites. I would like to unsubscribe these workstations from these sites. Normally this would be a simple task of right clicking a computer and opening the edit properties window to generate an action to unsubscribe machines. The problem is once a site is removed it no longer shows up in the drop down list.

After doing some investigating when you create an action like this it makes an action with the following relevance and associated action script.

Relevance

((exists custom site subscription effective date “CustomSite_OldSite”) AND (custom site subscription effective date “CustomSite_OldSite” < universal time “Wed, 04 Aug 2010 15:54:01 +0000”))

Action Script

custom site unsubscribe CustomSite_OldSite on “Wed, 04 Aug 2010 15:54:01 +0000”))

I can probably create a custom fixlet to perform the same task on the old deleted sites but I have a few questions

Why are dates used in the relevance and action script?

What does custom site subscription effective date translate to in english terms? Why is this being compared against universal time?

Is there some relevance and action script that can unsubscribe workstations from any sites that no longer exist in BigFix? this would be ideal since I could just have a standing action opened to perform this clean up on any workstations that need it for any future sites that get removed or renamed?

In the future it would be a best practice to unsubscribe machines from a site before you delete the site. If BigFix is unable to do this automatically it would be nice to be presented with a warning before deleting a site about possible orphaned machines subscribed to a non existant site.

2

(imported comment written by cstoneba)

bump. I’m having a similar problem. I have a fixlet within a baseline policy running to unsubscribe a client from a custom site. However, it always keeps running. Is my relevance unsubscribe relvance missing something? Is a date needed like murtasma is using??

(exists custom site subscription effective date “CustomSite_TR-2dServerBuilds”)

3

(imported comment written by cstoneba)

I think I narrowed my problem down. Even though I give the client the following unsubscribe command, the “value” value within the site under HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\Settings\CustomSites goes away, but the “effective date” value stays there. That is why my relevance of (exists custom site subscription effective date sitename) keeps report back as true. Can someone confirm that I am removing the client from the custom site with the correct command?

custom site unsubscribe CustomSite_TR-2dServerBuilds on “{now}”