The System File Checker utility allowed users to preform a manual scan of protected system files (and optionally repair them). Windows File Protection also arrived with 2000 which protected critical system files by not allowing anything other than Microsoft's Windows Installer or Windows Update package installer modify system files. One noticeable fact right off the bat is that features from have made it into the Windows NT line, like the Active Desktop update, Internet Explorer 5, Windows Driver Model, Internet Connection Sharing, Windows Media Player and WebDAV support. ![]() I'm curious about the need to install a new Windows 2000 SP4 instance in order to P-to-V an existing Windows 2000 Server? The Windows 2000 binaries, along with several other products, were unilaterally pulled from all Microsoft properties many years ago after Microsoft lost the Java lawsuit to Sun - because those products contained the Java-products built by Microsoft and subject to that lawsuit. ![]() Lawrence (SolarWinds) wrote: Just an FYI on the trivia side of things. In addition to installing a Win2000SP4 system, you'll also have seven years of patches to install (June 2003 - July 2010), and the ONLY way to get those installed onto a Windows 2000 system today (other than one-at-a-time manually) is by using a downlevel (not patched current) instance of WSUS v.226 (or WSUS v2 if you can find those bits). If so, the P-to-V process should be functionally the same on Win2000 or Win2003 testing on Win2003 may be a functional compromise if it's just about vetting the procedure.
0 Comments
Leave a Reply. |