Deployment Solution

I am using DS 6.9 SP4.  We recently started using a new server and I decided to move completely to WinPE from our Linux initial deployment.  The reason for this was we are deploying Windows 7 using imageX which requires WinPE.  When I was using the Linux PXE it would boot to PXE and quickly prompt for which initial deploy I wanted to run.  Now in WinPE it will occasionally not prompt for which job to run.  The only fix is to delete the computer from the DS and have it report in again and then it will prompt for which initial deployment job to run.  Before deleting it, it says it is waiting for a user selection but on the computer there is no prompt, until the computer is deleted and it tries to run the initial deploy again. 

The second problem with using only is that when it does give you the option to make the image selection, is that it will some times take a while before it will actually use that selection.  For example if I select Windows 7 as my initial deploy option it might take another minute or two before it will actually start that job.  This isn't as big of an issue as the first problem since as long as the job does actually run it is all automated and you can't really do anything for at least an hour while it installs the OS and our software, but it is still annoying.

Any help is much appreciated.

No one is have any problems with WinPE in intial deploy?  great, guess I will be contacting support....

So I was doing some testing and found that the delay in the job start is because it actually schedules the job for 5 minutes in the future.  So if you select to do the Windows 7 initial deploy, it will schedule the job to start in 5 minutes.  I checked everything and couldn't find a reason that it would schedule it for that amount of time in the future.

Regarding the first issue, I found this occuring in our environment, usually when a technician would leave the computer.  The initial deployment has a timeout, if you miss that timeout the menu will dissappear, leaving you in a state like you mentioned where you would have to delete the computer.  I had to keep yelling at the techs to at least get it to the point where it was deploying before they walked away.

Issue 2, I'm not sure why it would schedule 5 minutes in the future.

Problem #1:

For this problem you can try your luck by increasing the defualt timeout in which is by defualt 60 Seconds

1. click on Initial deployment

2. "Properties of initial deployment" Window is opened.

3  Change timeout to say 180

Problem #2:

"The second problem with using only is that when it does give you the option to make the image selection, is that it will some times take a while before it will actually use that selection.  For example if I select Windows 7 as my initial deploy option it might take another minute or two before it will actually start that job. " 

Answer:

Please follow the below steps and check whether it works

1. click on Initial deployment

2. "Properties of initial deployment" Window is opened

3 .Go to Configuration tab.

4.Click on Advanced button

5. Change default timeout to "0" instead of 5 minutes.

The job get schedule on client immediately once it gets connected to server.

I have not tested the solution for this problem but i am damp sure  that it works perfectly.

"IF YOU FIND THIS INFORMATION SUITABLE PEASE MARK IT AS SOLUTION  TO AVOID FURTHER DISCUSSION ON THIS TOPIC"

Bhawyer: I checked with a user that was experiencing this problem and found that the initial deploy never popped up. 

Symdon: So I always skipped over the configuration tab as I figured it was only for the configuration jobs for initial deploy.  So I think your solution for my second problem is the correct one.  I have tried adjusting the timeout for the jobs, but no effect on my problem 1.  I am wondering if the advanced configuration, just changing it to "Process this job as each client becomes active" will fix both the issues.