Our images come pre-applied from the manufacturer with the SCCM client installed. Upon receipt the PCs are joined to the domain and then applications are installed manually. 

I am doing a proof of concept that deploys applications based on the AD OU in which the computer object resides. It works well except for the fact that you have to wait 15-30 minutes between the computer being joined to the domain and applications being installed. Even after forcing a "Machine Policy Retrieval & Evaluation Cycle." Is there a way to force the client to install required applications immediately? 

Is the client already member of the appropriate collections then? How are they set up?

Well it`s more than just the computer policy. You need to wait for the computer to be in AD once it`s in AD you need to wait for device to talk to the MP after that the collection that as the query to put the computer in as to run (if you use increment that 5 min default).

In this case i don't think you could do a lot faster. 15 min to start to get all the application after getting the PC i think it`s pretty good since you have all the piece that need to be in place.

Join the PC to the domain and make sure all the application you need to deploy are done automatically wait 1 hour and when you come back should be all set.

Quick recap of step for computer to get application.

1.join to domain

2. Wait for the client to find the MP and start talking together.

3. Wait for SCCM to get the OU the computer belong to (AD system discovery if memory server me right) 5 min refresh delta

4. wait for the collection to refresh that as the query 5 min refresh if incremental as been selected

5. Need to get machine policy

• Edited by Frederick Dicaire 15 hours 16 minutes ago

The computer object is added to the OU before the computer is joined to the domain. The collection is based on the OU using a dynamic query. The computer already has the client installed but the certs and smscfg.ini are removed in the image. Did I address your question?

3. Wait for SCCM to get the OU the computer belong to (AD system discovery if memory server me right) 5 min refresh delt

Heartbeat.

Thanks Torsten

It is pretty quick in terms of SCCM. But from the POV of the tech the computer is sitting doing nothing when she could be performing the installation of software. That is also additional 15-30 minutes that the user is prevented from working. I was hoping there was a way to put new computers in a "fast lane" to receive applications or perhaps a TS that could speed things up. 

So at first heartbeat the computer should show up in the collection? It does seem to happen rather quickly after joining the domain.

Well you could look into the Prestaged media

http://sccmguy.com/2014/08/15/creating-prestaged-image-using-configuration-manager-2012-r2/

This would mean that the OEM re-seller would image the computer with your image and when they power on they look for SCCM right away to complete the task sequence.

This would be what you are looking for.

• Edited by Frederick Dicaire 15 hours 5 minutes ago

A great suggestion but in our agreement we supply one image for all models and that image is refreshed every 3 months. The manufacturer adds the drivers and tests the image for us which removes us from the liability of having a deployment that doesn't boot or is missing drivers. 

It seems like it should be possible to call a TS from inside windows (like MDT litetouch) that will do that software evaluation and kick off the installation but I cannot find any information supporting that concept.

Well to start a task sequence from inside windows you would have the same issue you would need to wait for the computer to receive the task sequence before running it.

You simply create the task sequence you want and deploy it to a collection (making sure it can run from config manager client).

Well it`s more than just the computer policy. You need to wait for the computer to be in AD once it`s in AD you need to wait for device to talk to the MP after that the collection that as the query to put the computer in as to run (if you use increment that 5 min default).

In this case i don't think you could do a lot faster. 15 min to start to get all the application after getting the PC i think it`s pretty good since you have all the piece that need to be in place.

Join the PC to the domain and make sure all the application you need to deploy are done automatically wait 1 hour and when you come back should be all set.

Quick recap of step for computer to get application.

1.join to domain

2. Wait for the client to find the MP and start talking together.

3. Wait for SCCM to get the OU the computer belong to (AD system discovery if memory server me right) 5 min refresh delta

4. wait for the collection to refresh that as the query 5 min refresh if incremental as been selected

5. Need to get machine policy

• Edited by Frederick Dicaire Thursday, August 20, 2015 4:35 PM
• Proposed as answer by Joyce LMicrosoft contingent staff, Moderator Tuesday, August 25, 2015 6:57 AM
• Marked as answer by Beanska Tuesday, August 25, 2015 12:25 PM

Well you could look into the Prestaged media

http://sccmguy.com/2014/08/15/creating-prestaged-image-using-configuration-manager-2012-r2/

This would mean that the OEM re-seller would image the computer with your image and when they power on they look for SCCM right away to complete the task sequence.

This would be what you are looking for.

• Edited by Frederick Dicaire Thursday, August 20, 2015 4:46 PM

Well to start a task sequence from inside windows you would have the same issue you would need to wait for the computer to receive the task sequence before running it.

You simply create the task sequence you want and deploy it to a collection (making sure it can run from config manager client).

• Proposed as answer by Joyce LMicrosoft contingent staff, Moderator Tuesday, August 25, 2015 6:56 AM

I have not implemented this yet but the Technet article below advises creating a collection for new computers and then applying a more aggressive client policy to that collection. 

http://blogs.technet.com/b/michaelgriswold/archive/2012/08/02/fast-policy-evaluation-only-for-new-machines.aspx

• Edited by Beanska 14 hours 58 minutes ago client -> client policy

I have not implemented this yet but the Technet article below advises creating a collection for new computers and then applying a more aggressive client policy to that collection. 

http://blogs.technet.com/b/michaelgriswold/archive/2012/08/02/fast-policy-evaluation-only-for-new-machines.aspx

• Edited by Beanska Friday, September 04, 2015 4:55 PM client -> client policy