Hello Denmyos,
I have set up a lot of SCCM for clients using the User-centric concept. This was introduced with SCCM 2012. Great stuff! So, What I usually do, I built my Devices and Users collections based on the same Active Directory group referencing the application. Help desk personnel can add either Users or Workstations in those groups, so it saves a lot of time for the SCCM guy responsible for deploying the application to the device or user. Customer satisfaction and waiting time improve too. Delta Discovery and collection updates take about just 5 minutes, when the limiting collection is, either All Users or All Systems depending on the type of collection. Some people prefer to use direct membership, but I think that this is a bad use of a great tool.
By default, SCCM clients, will take up to an hour to retrieve their policies. The technician can now easily trigger the policies himself via the SCCM console on the device itself. But you can tell the users how to do it on their computer via the control panel applet for the SCCM client.
If you are the Mcgiver type of person. I would suggest creating a script to specifically help the users refresh their policies themselves when you tell them they can to trigger the installation.
Hope you stick to SCCM, it is consistently improved by Microsoft Engineers. You have to think on the Macro deployment benefits, rather than just on the single deployment.
Best regards,
