We have hundreds of applications currently rolled out via GPO objects. I am going to begin the task of migrating all of these to SCCM, with the end goal of having little or no software deployed by GPO software installation options.
I've been trying to find some best practice on this, the thing I need to understand is how to time it so that software is removed by the existing GPO before being applied by SCCM but with minimum disruption to users. I don't know if it is smart enough to realise that the application is already installed and not try to install it again when it is already present thanks to GPO or conversely if I deploy again with SCCM then remove the GPO object will that cause an uninstall?
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
Hi,
We have hundreds of applications currently rolled out via GPO objects. I am going to begin the task of migrating all of these to SCCM, with the end goal of having little or no software deployed by GPO software installation options.
I've been trying to find some best practice on this, the thing I need to understand is how to time it so that software is removed by the existing GPO before being applied by SCCM but with minimum disruption to users. I don't know if it is smart enough to realise that the application is already installed and not try to install it again when it is already present thanks to GPO or conversely if I deploy again with SCCM then remove the GPO object will that cause an uninstall?
Thanks for any advice
Share this post
Link to post
Share on other sites