I'm quite sure that such a thing exists, since Microsoft did produce system builder packages of Windows 2000 Professional with SP4 integrated; the CDs in these usually use the xxxxOEM_yy nomenclature. (Do a search on eBay for "Windows 2000 SP4" and you should see some of them.) That said, I don't own such an image, sorry.
At work we have genuine Microsoft Win 2k Pro CD's including SP4 but they are not VLK. I assume they are generic OEM i.e. not Dell / HP etc branded rather than retail. Is this what you want?
If these files are trustworthy, I make it by myself. file: ZRMPOEM_EN.ISO md5: b35277b6304aae7071a928e74c24bfda sha1: d10e69c05258f0f9bac380bc4879fb94c16983ff crc32: ffffffff cdimg247m.exe -lZRMPOEM_EN -t06/20/2003,12:00:00 -g-7 -n -bboot.img -xx -o -m w2pdir en_win2000_pro_sp4_oem.iso
Thanks a lot for your reply. If you can see ZRMPOEM_EN as the volume label when the CD is mounted on a drive, then it is exactly the one I want. They will be generic (non-branded) because ISOs of Dell/HP will not have ZRMPOEM_EN as the volume label.
Unfortunately, that is not the case. In contrast to e.g. Windows XP, you cannot create one variant of Windows 2000 from a different one such that the resulting image is bitwise identical to Microsoft's copy. In this case: Taking e.g. ZRMPFPP_EN, changing the setupp.ini to represent an OEM version and applying the above cdimage command will not give you an authentic Microsoft image. The main source of the problem are the four boot floppy images included on Windows 2000 CD-ROMs: Part of their volume descriptor is a randomized (or possibly time-based) component which can be attributed to the way Windows "stamps" every floppy that is not write-protected while accessed. Every variant of Windows 2000 has its own set of boot floppy images, which differ a) in the volume name (which would be easy to fix, but most people would forget about it) and b) in the above-mentioned randomized bytes, which are impossible to deduce without knowing the target SHA1 or MD5. (And even then, it would mean brute-forcing all possibilities.) I conclusion, "home-brew" images of Windows 2000 usually work as intended, but they are unfortunately useless from a collector's point of view. Your best bet would be to get hold of someone who has access to an official physical medium. Cheers!