Thanks for the reply!
Were just figuring that out! Makes sense now.
We had it set to 0, can't recall if that's the default. We deploy a lot of software after initial imaging depending on the use of the computer/student lab. We have a base image and deploy software separately based on group membership. We image 5 machines at once via smb which has helped the cpu load compared to http. Once they're finished imaging they move onto the software install phase and another 5 start imaging via smb.
We've been observing large CPU spikes on check-ins, hopefully that can be randomized in a future release.
Thanks again!
Luc