tag:blogger.com,1999:blog-7396481053359703519.post2029327056752937786..comments2024-03-26T04:04:33.060+01:00Comments on Henk's blog: Patch Management in ConfigMgr 2012 Beta 2Henk Hoogendoornhttp://www.blogger.com/profile/01066841733613965112noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-7396481053359703519.post-4236824505219195092012-10-19T09:47:11.966+02:002012-10-19T09:47:11.966+02:00ConfigMgr 2012 is RTM by now! ConfigMgr 2012 SP1 w...ConfigMgr 2012 is RTM by now! ConfigMgr 2012 SP1 will be released in Q1 2013. More functionality to come!Henk Hoogendoornhttps://www.blogger.com/profile/01066841733613965112noreply@blogger.comtag:blogger.com,1999:blog-7396481053359703519.post-77648370722721411212012-10-16T18:37:20.457+02:002012-10-16T18:37:20.457+02:00May I know the advantage of ConfigMgr 2012 Beta 2 ...May I know the advantage of ConfigMgr 2012 Beta 2 update.Patch Managementhttp://www.manageengine.com/products/desktop-central/windows-patch-management.htmlnoreply@blogger.comtag:blogger.com,1999:blog-7396481053359703519.post-20319634380371330802012-03-21T12:56:13.584+01:002012-03-21T12:56:13.584+01:00In ConfigMgr 2012 it's possible to configure S...In ConfigMgr 2012 it's possible to configure Supersedence Rules. <br /><br />You can configure a software update to expire as soon as it is superseded by a more recent software update or to expire after a specified period of time when it is superseded by a more recent software update.<br /><br />Supersedence settings do not apply to Microsoft Forefront definition updates or to software updates that are superseded by Service Packs. There software updates never expire when they are superseded.Henk Hoogendoornhttps://www.blogger.com/profile/01066841733613965112noreply@blogger.comtag:blogger.com,1999:blog-7396481053359703519.post-81067530792864362972012-02-28T11:15:58.820+01:002012-02-28T11:15:58.820+01:00Hi Henk
I test SCCM 2012 RC and have a question a...Hi Henk<br /><br />I test SCCM 2012 RC and have a question about "internal patch maintenance".<br />I made multiple Software Update Groups (patches from each month) and included the updates in the same deployment package.<br />So each month I will get one group more and more patches in the deployment package consuming disk space.<br />What about superseded patches?<br />Is there an automatic way in SCCM to do some "internal maintenance"?<br />I want SCCM to remove superseded patches from groups, deployment packages and file system if I deployed the replacement patches.<br /><br />Thanks for your answer.<br />StefanAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-7396481053359703519.post-58167897620442757492011-04-14T12:36:03.657+02:002011-04-14T12:36:03.657+02:00Hi Henk,
Thanks for your blog. I am concerned jus...Hi Henk,<br /><br />Thanks for your blog. I am concerned just with Beta 2 and Software Updates and I have read your blog. Now I have a few questions:<br />1. I didn't find a way to define Search Folders. I only saw the possibility to save Custom Searches. Any ideas?<br />2. Where can I create and manage Deployment Templates?<br />3. I created a Deployment Rule and I choosed "new Software Update Group". But never asked for the name and after finished the wizard I didn't see any Software Groups.<br />4. I also choosed to create a new Deployment Package and after finished the wizard I see the package. But where can I now start the download for the defined updates?<br /><br />Thank you for your support,<br />DanielAnonymousnoreply@blogger.com