Hi all,

Whenever I create a copy of our OSD task sequence and then deploy it to All Systems as 'Available' and 'Only to PXE and boot media'. It takes over an hour for the task sequence to be available to clients. I should note that applications and packages are very quick, in line with the client polling schedule of 15 minutes.

I would have thought that as the client must speak to the MP to get the list of task sequences this would be almost immediate.

After about half an hour, the 'compliance' changes from 0% to 100% - why is this, what does this represent that it is doing in the background. It makes sense to me for a 'mandatory' deployment, as this is a percentage of the completed task sequences of the targeted collection. But the concept behind 'compliance' for an 'optional' deployment doesn't make sense to me. Can someone explain this to me?

Does anybody know where I can start troubleshooting this on the server, obviously there will be no client logs, and the actual deployment says that it is available and 100.0% compliant.

Kind regards,

Michael

Most likely a known issue: modify the available time of the deployment and set it some hours back. 

The issue Torsten is referring to has to do with DST and basically you need to set the available time of the TS deployment back at least an hour for it to be available on targeted clients.