Application deployment clarification - automatic silent installs to computers?

[nry]

Hi all,

 

We started to look at application deployment within our SCCM 2012 RC trials today.

 

We have some test clients, built from the Win7 x64 image created and deployed using the guides on here.

 

We did a quick application for Adobe Flash Player 11 from the official MSI via the Adobe Licencing scheme.

 

The package was automatically set with the /q flag by SCCM as expected for a silent install, We then deployed it to our test device collection of built computers - those having completed Win7 installs, on the domain and with the SCCM client installed during the deployment. They also picked up Forefront soon after they finished building.

 

According to our understanding, Flash Player should have just automatically been installed to the computers in the device collection we assigned it to. We waited a good while and then as if by magic, one PC did begin the install - however it popped up the full install interface needing the user to click through it. It first complained of no Internet connection to download the package, we clicked retry and it worked. We expected this to be silent though, no user interaction?

 

The other PC did nothing - no Flash Player install etc.

 

So, first off is this something that should work? We were assuming we can create and then deploy an application and have it automatically installed, silently, at the login screen (or during a logon session if applicable).

 

We then tried another simple MSI based application - we created the application within SCCM and then deployed it to the same device collection as Flash Player. After a good hour or so it still hadn't been installed.

 

Are we missing something with SCCM Application Deployment or should it work the way we are expecting it to?

 

Do the clients check for new applications on a fixed schedule and if so, are we able to configure this check frequency? Perhaps the clients just didn't do a check in the timeframe we were waiting.

 

Thanks for any reply.

 

Chris

[nry]

I suspect we're being impatient as the app had installed to one PC by this morning, however we're curious how we go about troubleshooting an app which hasn't deployed successfully to all assigned computers?

 

I have a feeling that the process went like this:

 

Build Win7 PC

SCCM picks it up, we move it to a device collection

We then renamed the PC and rebooted it

Allocate application

It installs to the PC that SCCM had got the right name for but not to the renamed PC

 

The renamed PC now shows by the correct name in SCCM but is not picking up any deployed applications. I cannot find a way to refresh or redeploy the application to the failed machines unless I'm missing something?

[airnooch]

Nry

 

Any luck on this. I'm having a similar issue.

[nry]

Kind of, I'm still unsure if or how you can control more closely when a newly deployed software application gets deployed.

 

There seems to be a setting in the SCCM Client Settings to make the computer client check for new deployments every 5 minutes, however this still doesn't appear to trigger newly deployed applications to be installed.