Good afternoon,
I am wondering if anyone has run into this behavior before. For a certain part of our environment we are using Maintenence Windows to trigger executions of Managed Software Delivery. Today we discovered that an MSD got out with a flawed Compliance Rule. We saw that it was trying to run every night for the past few days on the targeted machines. However we also noticed a few other MSD's that were staged/downloaded on the machine were not firing their policies as one would expect.
One specific thing about these machines is that they are all machines that were just imaged so they are getting a number of policies at once. Most are running well however a few of our recent file copy MSD's are not running.
We have fixed the one MSD with the bad rule and will review that in a couple of days to ensure it cleans up as expected. I am wondering if there are any known issues when using Maintenence Windows to execute MSDs? Wondering if having this broken rule might have triggered a scenerio where anything ready to execute behind just never gets the chance.
Any ideas would be appreciated. We'll know more at the beginning of the week.
Thanks
DCHAD