Score:0

Proper way to rollout GPO that requires restart of current and future machines?

jp flag

Let's say I have a policy that sets specific encryption settings for our servers. We don't want SSL 3.0, insecure, ciphers, etc for example. After this change machines must be restarted for the changes to take affect.

  1. existing machines should be restarted at specific time off hours
  2. future machines will need to be restarted after policy is applied

What is the ideal approach for handling this situation where there is a set time that needs to be scheduled now, but also a restart that needs to occur for future machines (edit: and administrator won't know that is the case for the new machine)?

Score:1
ru flag

GPOs don't reboot a system, so you need something else e.g. based on shutdown -r.

Future machines don't need that as they pull GPOs as soon as they've joined the domain (and were possibly moved to the appropriate OU). Usually, that's part of plattform installation where a machine is restarted a few times anyway.

cn flag
Yes I would separate this from Group Policy. There either needs to be a Config Management or RMM tool. Or if all the hosts are local, just script it.
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.