Search the Community
Showing results for tags 'push'.
Good Morning Guys / Niall - A couple of months ago, I applied CU4 to our SCCM 2012 R2 environment and this past weekend, CU5 mostly due to the IsCacheCopyNeeded issue. When applying the CUs, I'm extremely thorough in my procedure and remediate to ensure that every single of our ~1000 clients receives the update if at all possible. There's only one part of the process I don't fully understand - the best method to apply the CU's MSP for future console pushes and OSD. I did some research and below are the three most common (individual) solutions I've found: 1. Copy MSP into a subfolder for each client source (\x64 & \i386). I've found posts where the folder should be named "hotfix", posts where it should be named "ClientPatch", and one post saying to create and copy it into both folders. The theory is that similar to the Office installation, once the primary installer completes, it searches pre-defined paths for MSP patches and applies them. I currently have both folders in my source and only have the latest CU MSP in them. Supposedly, this should ensure that all OSD deployments and console pushes will install the latest client by default so there's no need for a 2nd advertisement Example of where to place CU MSPs: - \\SCCMPrimaryServert\SMS_ABC\Client\i386\ClientPatch\configmgr2012ac-r2-kb3054451-i386.msp - \\SCCMPrimaryServert\SMS_ABC\Client\i386\hotfix\configmgr2012ac-r2-kb3054451-i386.msp - \\SCCMPrimaryServert\SMS_ABC\Client\x64\ClientPatch\configmgr2012ac-r2-kb3054451-i386.msp - \\SCCMPrimaryServert\SMS_ABC\Client\x64\hotfix\configmgr2012ac-r2-kb3054451-i386.msp 2. For OSD: Add step in OSD TS for client update package. This one is pretty straight forward. Never update the default client package and simply add a step in OSD for the update package which the CU creates 3. For Console Pushes & everything else - Maintain a query-based collection for all clients which are out of date. For it, always have an open advertisement for each of the latest (x64 & x86) client upgrade packages So - which of the above (if any) are the best solution? There are countless guides online for applying CUs for SCCM, but I haven't found any which discuss how to apply the CU to future client installs once the site has been completely updated. Any comments, suggestions, or anything else would be much appreciated - Thanks!
Greetings: I'm rolling out a new SCCM 2012 environment. I have 81 clients that I'm trying to bring into my environment from an existing 2007 environment. I configured discovery so they were identified by configuration manager, and then pushed the client to all of them. About 20% of the machines are failing to install the client, and they're all getting the same error: c:\windows\ccmsetup\logs\ccmsetup.log: Couldn't verify 'C:\Windows\ccmsetup\MicrosoftPolicyPlatformSetup.msi' authenticode signature. Return code 0x800b0101 It appears that the installation isn't liking the MicorsoftPolicyPlatformSetup.msi authenticode signature, and I'm not quite sure what to do about it. Since the majority of my clients installed without problems, I'm pretty sure the problem isn't with the source files. To make sure something wasn't getting corrupt data copied over, I did a file compare (fc <file1> <file2>) from a command prompt. The files are identical. I thought maybe an error message might be getting hidden during the install, so I decided to run the microsoftPolicyPlatformSetup.msi manually and see what happened. No errors were generated. However, after installing this manually, I was able to push the client successfully from the console. Any ideas?
Hello! Befor the New year we intalled SCCM 2012 SP1 and import some preferences. But now we find one very strange problem. When we install OS TS in ccm.log we find a lot of errors that push intalletion accont can't connct to the ...\admin$ share. Add this account manually to the administration group on test computer. Then we go to push account and check password - it was wrong. Ok, we changed it and complite verification. But it doesn't help. We saw similar errors. Ok, we check AD account - it was unblocked. After than we go to the preferences of push account and find, than password is wrong. So now we change password, test connection and press 'ok' and nothing has been changed We try reboot server and make new AD accont for push account.
Hello all i have setup SCCM 2007 r3 in my Lab enviroment. I can get the software Deployment Working. I have Enabled Software Distrobution point, made the package and created the advertisement .. I have also made a small video of my Setup for show you where the problem is... My windows 7 client just sits there does nothing. Which logs can I check.to help me fin the problem... VIDEO http://youtu.be/WCpYlKntSvI