Yes, that really was a thing.Īfter having to deal with those issues for 15 years, CBS promised much goodness. The act of re-applying the service pack would over write the older file from the CD with the new file from the service pack. After installing an OS component you had to reapply the service pack. NT had its own quirk where there was no chaining. Windows knew it needed particular files from a particular source and would prompt as needed. inf files were chained as the OS was updated over time with service packs and hotfixes. For example if you wanted to install an OS feature on a Windows Server 2003 SP2 machine, potentially you needed to provide RTM, SP1 and SP2 source files. For those who worked on NT or Windows 2000/2003 servers there are always some funny stories around managing the OS over time. The Windows Component Store was introduced in Windows XP to support side by side assemblies and enhanced in Vista track all the OS components. Note that Windows 7 and Windows Server 2008 R2 changed their update methodology in October 2016 to mirror the update distribution behaviour in newer versions of Windows. When we looked into the details, the monthly Windows Server 2012 R2 updates had been failing to install for the last 18 months. The customer's security team were slightly upset as they believed (mistakenly) that all assets were properly updated. The below post initially stemmed from an Exchange Risk Assessment which noted that all of the customer's Exchange servers were missing critical Windows updates.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |