What does this DWORD Value: 30000 represent in time?

For my use case I decided to use MaxRegistrationDelayMin anyway. I set it to 40 minutes.

I guess I owe you an answer, because I don't think that's ridiculous. At least from my perspective, because I had to build this, did I? :-D

The 40 minutes is not exactly necessary, it's just that it sometimes needs more than 20, and I wouldn't want to do further tricks, so I just doubled the time.

Then there are 3 scrips and the BIS-F delay

1. Installs the customers ERP software. Why during logon? Because the software isn't exactly installed, but copied over from a share. And the vendor changes stuff all the time. So with BIS-F during each reboot, the software get's reinstalled. Only that the software is big and consists of thousands of little files. That simple robocopy command can take about 10 minutes.

2. Defender onboarding. Shouldn't take too long.

3. Monitoring agent onboarding. As this are MCS clones, I found to install monitoring agents after the cloneing a lot easier, then getting this puzzle solved in the master image. Takes max 1 minute.

4. The BIS-F delay. I mostly set it to 10 minutes, so Defender can do it's stuff after onboarding, like getting signatures right etc. At least I imagine that this is necessary. And as servers reboot during the night, nobody cares the delay.

And well, there is the time for the reboot itself, so we get:

1. Reboot Time ~2 minutes 2. ERP software ~10 minutes 3. Defender onboarding ~1 minute 4. Monitoring agent (Zabbix) ~1 minute 5. BIS-F delay ~10 minutes Summarized: ~24 minutes Could always cut the 10 minutes from BIS-F, but I like it that way, let's the machine settle down after the reboot and maybe VMware DRS also want's to have some fun, who knows?

ping @Nick Panaccio @Ray Davis @James Terrell

But thanks for the explanation though.