Windows sid updating
That followed two and a half years at the company as a Solutions Engineer working directly with many organizations of all sizes.
Prior to that Paul worked at Microsoft for 12 years, eight of which were as a senior Config Mgr Engineer for the teams serving Microsoft IT (300,000 clients) and others.
That included “dogfooding” many versions of Config Mgr.
For his first few years at Microsoft, Paul was a technical writer on the Config Mgr (SCCM) product team.
Have you heard anything along those lines in all the discussions of Windows 10? With a little digging, however, you will find that Microsoft has actually been conscious of the pain of reboots for a long time, having invested very aggressively over the years to mitigate them.
Our “Improve Security by Optimizing Your Reboot Strategy” whitepaper goes into details about those efforts, but today we’ll focus on Restart Manager.
Microsoft surely knows that, so you would think that in this new world they would work to reduce the pain of restarts.Restart Manager tries to avoid the computer restart by only restarting the software that is sharing the resources.This all sounds great, but today’s reality is that it is still very common for installations or upgrades to require restarts.I took my conclusion to the Windows security and deployment teams and no one could come up with a scenario where two systems with the same machine SID, whether in a Workgroup or a Domain, would cause an issue.At that point the decision to retire New SID became obvious.' He concludes: 'It's a little surprising that the SID duplication issue has gone unquestioned for so long, but everyone has assumed that someone else knew exactly why it was a problem.
As early as 2005, Microsoft described Restart Manager as: “If a part of an application, or the operating system itself, needs to updated, the installer will call the Restart Manager, which looks to see if it can clear that part of the system so that it can be updated.