I am currently testing, so far it seems to be running as expected, currently I am testing deployment of software. I find the new approach to be much better then SMS, in terms of the pop up notifications SCCM stating that a new program is ready to be installed, the options for the install, and the deadline for the install. The only thing I find lacking is that there does not seem to be a "Advertisement Completed\Program installed"pop up notification. Is there a way to have a pop up stating that it is complete?

Also, another option that I am looking for is the ability to send a command to the client machines to kick off a polling, despite the polling schedule. So if I need to make a change in the advertisement or package, I don't have to wait for the client to poll the server.

Hi

There is no pop up notification after a program has installed.

You can download the right click tool for SCCM and then get the option to update the machine policy on the client or collection from the console. You find the right click tool here:

http://myitforum.com/cs2/blogs/rhouchins/archive/2008/04/09/sccm-right-click-tools.aspx

In general, most companies (and end users) absolutely do not want to be bothered, and the "I'm done" message is bothersome.

If what you are deploying happens to be an MSI, and you happen to be installing "only when a user is logged in", instead of using /qn you could use /qb+! ; if memory serves, that'll pop up a done message. But it's not Configmgr displaying that message, it's msiexec.exe. Personally... I wouldn't do that. I'd keep it quiet, stick with /qn or /qb-! if you want to display something to the user; when the progress bar disappears, the install is done. (again, assuming this is an msi-based install)

A lot of people use the right-click tools, but don't forget to grab Roger Zanders' SCCM Client Center. Lots of great things in there.

This isone time that I have to disagree with Sherry. I actually sent this exact idea in to Microsoft last week as a feature request. I would love to see Microsoft add a featurethat would allow us to give a notification when a program has completed. Today when I deploy using -qn the user has no way to know when the install has completed.

I would agree with Sherry in that case. Either it's completely silent (the end user doesn't see anything so there's no need to pop up a "I'm done" message, because there was nothing visible before) OR it's visible by using /qb-! (which basically provides a progress bar without any cancel buttons. It's done when this progress bar is gone). So *I* don't see the need for another notification. Or am I missing something?

I'd like to add something to this. Some installs run pretty well in the background without any notifications to the user, whereas others don't.

A general rule of thumb I use is if it's a foreground application that an end-user actually launches via a shortcut etc. it may not install very well if that application happens to be open during the install process - hence some notifications to the end user here via a wrapper might be a good idea. e.g.

Office Upgrade (tell them to close their office apps, and warn them that the install may take about 30 minutes)
SAP client upgrade (similar)
Cisco VPN Upgrade (briefly disconnects machine from network)

Ones like background programs that install as services (anti-virus program etc.). or hotfixes etc. are probably better candidates for running without notification, unless a reboot is required at the end. e.g.

OS hotfixes
anti-virus programs
anti-virus definitions
little registry modifications

Dealing with reboots can be interesting as well. But that's a whole subject in its own right.

Hi,

we have used this app to be displayed prior to running some applications - http://blog.coretech.dk/confmgr07/config-mgr-tools/coretech-auto-install-warning-freeware/There is no reason why you can not use it to display a message after a successfull installation of another program. You can customize the message, message title and the logo. It's pretty simple to use.

Hi,

I hope it is OK to reopen this case?

Is there any solution available for SCCM 2012 and x64 installations?

/Cheers