Hello,

I'm trying to redundantly to configure the Snow Inventory Agent to send the .snowpack forcibly.

My environment of close to 8000 desktops is heavily uncertain under the aspect of usage. By this I mean that we have departments where computers stays turned off for long time and usually support technicians have to turn on computers spread over several locations. Even though the retention policy configured at SLM (45 days) avoid them to be wrongly archived, I have outdated data about those computers.

This is my current snowagent.config:

<Span>

   <StarTime>PT00H00M</StarTime>

   <EndTime>PT23H59M</EndTime>

  </Span>

<Occurance>

   <Weekday>monday</Weekday>

   <Weekday>tuesday</Weekday>

   <Weekday>wednesday</Weekday>

   <Weekday>thursday</Weekday>

   <Weekday>friday</Weekday>

   <Weekday>saturday</Weekday>

   <Weekday>sunday</Weekday>

  </Occurance>

...

<Schedule>

  <Task>

   <Occurance>

    <AtLogOn>false</AtLogOn>

    <AtStart>false</AtStart>

    <Daily>true</Daily>

   </Occurance>

   <Action>scan</Action>

   <TimeOfDay>PT09H00M</TimeOfDay>

   <Randomize>90</Randomize>

  </Task>

 </Schedule>

 <SystemSettings>

The following changes are being evaluated:

   <Occurance>

    <AtLogOn>true</AtLogOn>

    <AtStart>true</AtStart>

    <Daily>true</Daily>

   </Occurance>

   <Randomize>60</Randomize>

1. Is occurrence parameters exclusive? Or Could I enable all three possibilities? (Once that a scheduled scan will never be performed more frequently than once a day, I'll be sure that under some of the possibilities the scan/send will be executed)
2. Randomize time reduction, narrowing the range of possible scan/send times.

I'll appreciate suggestions of other actions that we could take.

Reference:

https://docs.snowsoftware.com/documentation-resources/snow-inventory/configuration-doc.html#Configuration_Schedule

https://docs.snowsoftware.com/snow-inventory/en/UUID-e3347090-a773-a05d-2e2c-ce197cd00a26.html