Skip to content

Snelson EA frequency ideas #1

Description

@da4ftso

What if we set some EAs to only update X often, but then need to touch that plist to catch a change in the env?

Can we measure change in recon time to justify this effort? Is it much worse once we go to cloud?

--

UPN - in some cases, never changes; what if we look for new Users?

daily: (not really if recon runs that often anyway)

weekly:
Battery Health
Location Services
AD Binding?

monthly:
SWU History (or write plist so it only runs after change detected? Do we need to do this if JSS has accurate history, or does this catch other updates?)

quarterly:
Tanium, Nexthink versions

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions