How does the randomize parameter work?
Here's an example of an excerpt from a snowagent.config file:
<Schedule>
<Task>
<Occurance>
<Daily>true</Daily>
<AtLogOn>false</AtLogOn>
<AtStart>false</AtStart>
</Occurance>
<Action>scan</Action>
<TimeOfDay>PT09H00M</TimeOfDay>
<Randomize>60</Randomize>
</Task>
</Schedule>
Look at the latest snowagent.log from C:\Program Files\Snow Software\Inventory\Agent\data.
Then search within it for the keyword scheduling item and locate the latest date and time.
In this example, I have the below excerpt (your timestamps will differ):
2022-01-28T12:16:29+11:00; Verbose; snowagent; win32\serviceprocess.cpp; snow::win32::ServiceProcessBase::main; Service is running.
2022-01-28T12:16:29+11:00; Verbose; snowagent; win32\bootconfig.cpp; snow::BootConfig::parse_scheduled_tasks; Scheduling daily item.
2022-01-28T12:16:29+11:00; Info; snowagent; win32\bootconfig.cpp; snow::BootConfig::schedule; Scheduling item at 2022-Jan-29 09:13:00
2022-01-28T12:16:29+11:00; Verbose; snowagent; process\processmanager.cpp; snow::win32::ProcessManager::handle; Process 0 started.
From the snowagent.config file we can see that our setting is defined to perform a scan every day at 0900 hours:
<TimeOfDay>PT09H00M</TimeOfDay>
<Randomize>60</Randomize>
From the log extract, you can then confirm that the exact schedule is at 09:13
2022-01-28T12:16:29+11:00; Info; snowagent; win32\bootconfig.cpp; snow::BootConfig::schedule; Scheduling item at 2022-Jan-29 09:13:00
In the config we had specified it at 0900 hours but the randomize parameter has adjusted this.
The randomize setting allows users to define values for Snow to pick a random number within the range define in your configuration, in this example, its 60. The random number will then be for the minutes.
In our log file we can see that in our example 13 (minutes) has been randomly selected thus from the log we able to see it is set to schedule the next scan at 09:13 am
You can simulate the random picking of numbers if you restart the Snow Agent service and check the logs again.
After the restart, a new schedule was selected. By looking at my log file I can see this is now at 09:16 hours instead of the previous 09:13 hours:
2022-01-28T12:29:35+11:00; Info; snowagent; win32\bootconfig.cpp; snow::BootConfig::schedule; Scheduling item at 2022-Jan-29 09:16:00
Why is the random selection of schedule helpful?
One reason for picking the right balance on what value to set for the randomize is to consider the number of devices that may overwhelm your platform. This particularly important to the Snow Inventory Server on processing multiple snowpacks at once.
Imagine if you set below snowagent configuration to scan as follows:
<TimeOfDay>PT09H00M</TimeOfDay>
<Randomize>2</Randomize>
If you have, for example, 100,000 devices that are online and expected to send snowpacks everyday. Setting that as your configuration would mean, all of those 100,000 devices will have to scan and send snowpacks between 09:00 and 09:02 hours. The Snow Inventory Server will have to receive and process them.
However, if we set the randomize value to for example 60, this would mean, we are giving more time for our Snow Inventory Server and also for our network too. Giving too much randomize value is not a good practice though, if we put higher value the machine might have already turned off before it performs the scan for the day.
Depending on your circumstances and business needs finding the right balance is always the key.
Was this helpful?
Related Articles
Release Notes Index: Snow Inventory Agent 688Number of Views How to configure Snow Agent configuration or ps1 files on different drive letter 7Number of Views Request or download a Snow Inventory Agent 199Number of Views Fix API endpoint configuration issues between Snow Inventory Server and Snow License Manager 349Number of Views Release Notes Index: Snow Agent Script 323Number of Views
Revenera Assistant - Beta
Online
Hi, I am Reva - Ask me anything.
Updates
No new updates
Chat
Home
Updates
/**/
Thanks for the feedback!
Your feedback has been saved.Rate this response:
1
2
3
4
5
Add Additional feedback ( Optional )
0/240
English
English
Language changed successfully
Something went wrong
Email sent successfully
Something went wrong
Case create successfully
Are you sure you want to cancel
the case creation?
Please select a product to submit the case.
Please select a product version to submit the case.
0/255
Upload Attachment
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to cancel the case creation?
Case closed successfully
File Upload
Maximum file size allowed is 3 MB.
File type not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
© 2026 Flexera Software. All Rights Reserved.
Case id: 00001065
Activity: Status change: 2 hours ago