As I said, it could be that your client is outdated in the GPO. I would start by updating the GPO using the method described here:
http://blogs.technet.com/b/smartinez/archive/2013/09/27/top-3-configmgr-2012-client-installation-methods.aspx On Wed, Mar 11, 2015 at 4:29 PM, Stefanie Burton <[email protected] > wrote: > Yes client push is all ready in play. This would be an additional effort. > > SB > On Mar 11, 2015 3:50 PM, ccollins9 <[email protected]> wrote: > > Just curious, have you thought about setting the SCCM AD discovery for the > OUs you are targeting and allow SCCM to install the client automatically to > the systems discovered by that process? The reason I suggest this is > because SCCM will always install the correct client. When using GPO, if > you make any upgrades to SCCM and have a new client version due to that, > you need to go update the GPO with the correct client AND install > switches/parameters. From the error you posted, it seems that the GPO is > trying to install an outdated version to the computer. > > On Wed, Mar 11, 2015 at 3:43 PM, <[email protected]> wrote: > > Hello Folks, > > Application Event log error Product: SMS Client Setup Bootstrap -- A newer > version of the SMS Client Setup Bootstrap is already installed > > Need to determine exactly where the process is failing. What component or > executable is the MSI looking for that's flagging this. The SCCM client > push install seems to have no problem installing whereas the GPO push > results in this error. Any assistance is greatly appreciated. Thanks. > > > > >
