[sccm 2012] Software not deploying to re-imaged machine

[nicholab]

Anyone got any suggestion why SCCM is not deploying software to a machine if I re-image it?

[DalekSec]

Have you checked the new machine is in all the right collections? and that the software is being deployed to them.

 

Also run the software inventory cycle, along with some of the others

[Annabelle]

It could just be a timing issue. Deployment of software doesn't happen right after re-imaging.

 

If you go to the Control Panel - Configuration Manager and force it to grab the latest machine policy, does it recognize that it has applications available to be installed?

Check the three logs that begin with App* on the client machines.

[mullet_man]

How are you installing the SCCM client after you've reimaged? Is it actually installed?

[sparkeh]

Also check that the machine doesn't think that installation is barred by being In working hours.

 

I've had a bit of an issue with this recently after an update to sccm. Working hours are different to maintenance windows.

[mullet_man]

Did you get to the bottom of this?

 

I ran the latest Hotfix on our SCCM and now machines am re-imaging are not picking up deployments. Hmmmm once I get a few mins I'll check some logs and take a closer look.

[mullet_man]

It seems I wasn't waiting long enough, the re-imaged machines seem to have picked up the applications now. Just seemed to have taken a lot longer than normal.

[Annabelle]

If you don't want to wait and want to test that the deployment is working, you can go to the Control Panel -> Configuration Manger and grab the latest machine policy.

Then see if the app shows up "quicker". If the application is still not deployed in 5 minutes then it is time to troubleshoot.

[mullet_man]

If you don't want to wait and want to test that the deployment is working, you can go to the Control Panel -> Configuration Manger and grab the latest machine policy.

Then see if the app shows up "quicker". If the application is still not deployed in 5 minutes then it is time to troubleshoot.

 

I did run that but it still took a lot longer than 5 mins. It all seems fine now, not sure if the latest update had caused the issue or not.

[ReadTheNetwork]

Could I ask why you don't install the packages/applications during the task sequences rather than after?

[nicholab]

They are part of the task sequence and the have not applied also not all application deployments have been added to the task senescence.

[mullet_man]

Could I ask why you don't install the packages/applications during the task sequences rather than after?

 

It's a good question, am not sure I guess a lot of our apps have been added on since imaging so get added to SCCM.

 

Am still not sure what the best method of imaging is.

 

Thin/Fat?

Apps during deployment?

Apps via SCCM?

 

Who knows, mine is a mix of fat and apps via SCCM. We have CS6 full suite which takes an age to install so it's part of our image rather than it getting installed each time.

[sparkeh]

It's a good question, am not sure I guess a lot of our apps have been added on since imaging so get added to SCCM.

 

Am still not sure what the best method of imaging is.

 

Thin/Fat?

Apps during deployment?

Apps via SCCM?

 

Who knows, mine is a mix of fat and apps via SCCM. We have CS6 full suite which takes an age to install so it's part of our image rather than it getting installed each time.

Yeah its tricky, I guess its personal preference and there's no 'right way' (though some people will tell you otherwise )

I like to keep things as separate as possible as, in my opinion, it makes troubleshooting easier. So I do the following:

1. Apply image from source wim, only alteration is to strip Windows 10 modern apps out
   
2. Apply updates (though with Windows 10 and cumulative updates its easy to keep the image up to date)
   
3. Install all applicable software
   
4. Reboot so GPOs apply.
   

[ReadTheNetwork]

I personally like to keep my image light, it's a Windows OS and updates are applied automatically offline.

 

I then deploy software during the task sequence pending on the groups they are in. Obviously everyone gets Office, Adobe Reader etc.

I cut down CS6 to just photoshop as our school doesn't use any other part of it. But yes, if it does take a long time to install then I'd be tempted to put it on the image .

 

So my deployment looks a bit like the following:

(Device Collections)

All Unknown Machines have Collection Variables such as Teaching_PC, Student_PC, Software_Maths, Software_Computing etc. (new builds)

I then have Device Collections with the same names which gets the computers from an AD group with same name again. The collection variables for these are set with it's name to true or yes. Example Software_Computing collection will have variable collection called Software_Computing set to true. (rebuilds)

 

(Task Sequence)

Adds the machine to the AD groups pending on the collection variables (if it's a student_pc set to yes or true then it'll add all the software subject software in anyway such as maths computing, otherwise if it's staff_pc then it'll check which additional software would be required.)

Finally the applications are deployed if the collection variable for that software is set to yes/true.

[Annabelle]

I prefer hybrid approach: base image = Windows 10 + visual C++ + .NET Framework + MS Office + Windows updates.

We also build the image using MDT.

 

Then the WIM created by MDT is imported to SCCM.

Within SCCM, there are several task sequence based with variations of applications that need to be installed usually differed by user type: students, teachers, admins, BitLocker.

 

Computers are grouped by the room in the OU.

Any specialty software such as Photoshop, Autodesk, etc will be pushed out imaging to a specific OU/Room.