joeman1881 Posted February 5, 2014 Report post Posted February 5, 2014 In my environment, we previously had 2 WSUS Servers, Forefront Boxes, and SCCM servers at each site. We were able to replace this with 1 SCCM 2012 box, and it has been great. I have never worked with this product prior because I am new in my career, but I have learned in the last few months just how powerful of a tool it is! My latest struggle has me changing my software update plan daily. I created a collection for my W8, W7, and XP machines, that auto populate based on OS and OU, Auto Deployment Rules are pushing out correctly to these machines and they are all happy. Servers are where my issue lies. Prior to implementing this new SUP, we had servers reach out to the WSUS for servers UP, download updates, and await approval/install. This means once a month we log onto all of our 150ish servers and click install, reboot our VM's, update our hosts, and reboot them. I was hoping to set something up similar to this with SCCM by pushing updates via Software Center, like I do with my client machines, but instead of silently auto-installing, I just want them to be available? I can't seem to get this functional in a test enviornment. My next thought was, maybe I can just push the updates to install, and then when we are ready to finalize, just reboot the servers after hours, so we could skip the "wait for install and then reboot" process we currently go through. My only concern is that with my current deployments to clients, we have reboots suppressed, we aren't using a maintenance window, but after updates, the machines still say they need to be rebooted within 7 days. This seems like a lot of time, but in my environment we only have 3 network/server techs for all 20 sites, so sometimes we are late on our updates due to other pressing issues. I can not have Sharepoint, Exchange, or our main DC's go down unexpectedly. Anyone have any insight on how I can achieve one of those two scenario's? I would also like to hear if anyone has a better way of managing this. Thanks! Quote Share this post Link to post Share on other sites More sharing options...
willisj318 Posted February 5, 2014 Report post Posted February 5, 2014 It sounds to me like you simply need a separate collection and deployment going to servers that you have set as available instead of required? Unless I am not understanding what you want exactly. Quote Share this post Link to post Share on other sites More sharing options...
joeman1881 Posted February 5, 2014 Report post Posted February 5, 2014 It sounds to me like you simply need a separate collection and deployment going to servers that you have set as available instead of required? Unless I am not understanding what you want exactly. That is exactly what I need, but when I am running through the steps to create my ADR's I am not seeing this option like I do with software deployments. Am I missing something? Quote Share this post Link to post Share on other sites More sharing options...
joeman1881 Posted February 6, 2014 Report post Posted February 6, 2014 If anyone has insight on this is would be great. I ran through the ADR Wizard again, and I'm not finding the section to make the deployment Available/Required. I also checked the Deployment Package to verify that this didn't need to be configured after the ADR was configured. Has anyone else run into this? Quote Share this post Link to post Share on other sites More sharing options...
Peter33 Posted February 7, 2014 Report post Posted February 7, 2014 Just define a deadline far far far far far .... far in the future. Like 2050 or something. Edit: My fault, you can only define 12 month. But this should be good enough, because the deadline will be set again as soon as the ADR runs. Quote Share this post Link to post Share on other sites More sharing options...
joeman1881 Posted February 7, 2014 Report post Posted February 7, 2014 Just define a deadline far far far far far .... far in the future. Like 2050 or something. Edit: My fault, you can only define 12 month. But this should be good enough, because the deadline will be set again as soon as the ADR runs. Ok...Thats was I was thinking of doing, just didn't know if there was for sure a setting that I missed. Thanks for the insight! Quote Share this post Link to post Share on other sites More sharing options...