Scheduled OSD deployment available before start time

Hi there,

i was wondering if somebody could help me resolve a issue i am having. 

I am trying to prepare several deployments to make them available after a specific time period. The problem is when i select a start time, the deployment already becomes available to devices.

I already tried to check en uncheck the UTC option, this makes no difference.

Anyone has some suggestions for me?

Thanks in advance

August 15th, 2015 4:20am

During the deployment you can use the Scheduling part of the deployment also to configure when the deployment will be available. This can be configured by selecting the box with Schedule when this deployment will become available.
Free Windows Admin Tool Kit Click here and download it now
August 15th, 2015 4:36am

Hi Peter,

that is the odd thing. When i create the deployment i use the option Schedule when this deployment will become available. But it still is available before this time.

August 15th, 2015 4:39am

Are you talking about PXE boot? 
Free Windows Admin Tool Kit Click here and download it now
August 15th, 2015 4:40am

At this point i am testing it in a virtual environment with a bootable iso.
August 15th, 2015 4:41am

Hi,

How do you set the available time and start time?

If you schedule a start time for a required task sequence that is earlier than the date and time when the task sequence is available, the Configuration Manager client downloads the task sequence at the scheduled start time.

Free Windows Admin Tool Kit Click here and download it now
August 19th, 2015 3:59am

We found out that this is not going to work. As the schedule is a SCCM policy and the machine is in WINPE and does not receive a SCCM policy at this point. 

When the SCCM agent is installed during the task sequence and gets initialized the task sequence failes because the deployment is expired. So the schedule works only when the machine is getting SCCM policies.

September 9th, 2015 3:13am

We found out that this is not going to work. As the schedule is a SCCM policy and the machine is in WINPE and does not receive a SCCM policy at this point. 

When the SCCM agent is installed during the task sequence and gets initialized the task sequence failes because the deployment is expired. So the schedule works only when the machine is getting SCCM policies.

Free Windows Admin Tool Kit Click here and download it now
September 9th, 2015 3:14am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics