Clean the Taskbar Notification Area Icon Cache in Windows 7
Launch the registry editor
Navigate to the HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\TrayNotify key
Delete the IconsStream and PastIconsStream values in the right pane.
Finally, you’ll have to log out and log back in (or restart Explorer.exe) for your changes to take effect.
Reboot System for changes to take effect if logout/login does not work
# 19042.508.200927-1902.20h2_release_svc_refresh
## CLIENTENTERPRISEEVAL
https://software-download.microsoft.com/download/pr/19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_de-de.iso
https://software-download.microsoft.com/download/pr/19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_en-gb.iso
https://software-download.microsoft.com/download/pr/19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_en-us.iso
https://software-download.microsoft.com/download/pr/19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_es-es.iso
https://software-download.microsoft.com/download/pr/19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_fr-fr.iso
https://software-download.microsoft.com/download/pr/19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_it-it.iso
https://software-download.microsoft.com/download/pr/19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_ja-jp.iso
https://software-download.microsoft.com/download/pr/19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_ko-kr.iso
https://software-download.microsoft.com/download/pr/19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_pt-br.iso
https://software-download.microsoft.com/download/pr/19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_zh-cn.iso
https://software-download.microsoft.com/download/pr/19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_zh-tw.iso
https://software-download.microsoft.com/download/pr/19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_de-de.iso
https://software-download.microsoft.com/download/pr/19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_en-gb.iso
https://software-download.microsoft.com/download/pr/19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_en-us.iso
https://software-download.microsoft.com/download/pr/19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_es-es.iso
https://software-download.microsoft.com/download/pr/19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_fr-fr.iso
https://software-download.microsoft.com/download/pr/19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_it-it.iso
https://software-download.microsoft.com/download/pr/19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_ja-jp.iso
https://software-download.microsoft.com/download/pr/19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_ko-kr.iso
https://software-download.microsoft.com/download/pr/19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_pt-br.iso
https://software-download.microsoft.com/download/pr/19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_zh-cn.iso
https://software-download.microsoft.com/download/pr/19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_zh-tw.iso
e0694676ae6ffadbbcc4ae4c0bf9ef32faa2a5df *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_de-de.iso
11637a2702fb0b417965b00f446d3359ac7cda46 *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_en-gb.iso
2a54d9b98fd5638c6fee7b23383a17e49f6a3118 *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_en-us.iso
56bb3c2423d492ce18c83fbf92a7530727c775bd *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_es-es.iso
29d1bb086d57412fb010864098069266aa9c00f1 *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_fr-fr.iso
561f3a272f7fedacd7a0db47e998d4856da05f7f *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_it-it.iso
1ee3e5eb302beff5f3a90b9711090d6be5c522db *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_ja-jp.iso
6834f87b31614ff3d7d1c8f277de70b657c78cb8 *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_ko-kr.iso
bbce2a75cebfca6dc9a725ab30e66dca0df48094 *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_pt-br.iso
c1f2983af8426781f6d5ed8c59dbaba2a0ddb073 *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_zh-cn.iso
22a8e76095e01e22e5636540e3e058fdf86d9598 *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_zh-tw.iso
3f4b55c851b2255c18679edcb82c05b3d57a2a6c *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_de-de.iso
adbf3dbf4a3414b202c691e0b93cc34df20c40b6 *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_en-gb.iso
c7ba86711d4da4b661c635ddc49f2f63309b56fc *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_en-us.iso
cfe606b08c922bd5488dc7123e71f28a2890132e *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_es-es.iso
3a0096e1bb67e24b93f28677cbf3b269ca617e40 *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_fr-fr.iso
959c96e6e5b94b7866cfe1ba4fdb837525256ae2 *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_it-it.iso
c376b446a2f9ef86087e27e7d178e2ef61909496 *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_ja-jp.iso
9f2e9e8707b32a66a2db341c1cabc3f2a74393f6 *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_ko-kr.iso
05fb2bce4e44e766ae6debcfd10cb90248563101 *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_pt-br.iso
9ceb7c63e60a3d6cb63499ad75a039fa6029bdd0 *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_zh-cn.iso
02220922887acfb97afe7045c619a5a3fc5b01d8 *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_zh-tw.iso
913ff4d4e9a9ca22aa55b1679bfc0a874185495bcac36755046162a4f88e79d9 *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_de-de.iso
bfd47daee5649e8474cd3f4db25925e6821dc09a3cce54c1893d3ccd6632121f *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_en-gb.iso
574f00380ead9e4b53921c33bf348b5a2fa976ffad1d5fa20466ddf7f0258964 *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_en-us.iso
b586edc8388ad439b04d39e66b69937340040733f67c5405e60d4203df610050 *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_es-es.iso
3d877fcc7ea8b440e869144e6b9bfd88ed07bcf7b856be652ef2ec74f62db09a *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_fr-fr.iso
ba169afcb39791a34188ea7ef8650f4579d08cf28760e5f910cb92cda8382b40 *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_it-it.iso
4af2ca54ebbf8d52dca6a397198e8a9b41ff4d6770e3564d8ad095ee1022d970 *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_ja-jp.iso
ce20c034613163bb3269efb1849bc31130f9474b8c7af1f4607cadf24d30bc6e *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_ko-kr.iso
31f07bb764924b231f0d9ab119d76aad9f2c85ff48ab7c69fdbbc16f252aaee5 *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_pt-br.iso
bb271293e0dde3b8f226c702bdabe0da21817d8ebbe3f6fdc3144f741b9e512a *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_zh-cn.iso
3d81e4d6f08cce497bee05d9093fcd6c0abe507295a89d82e6a015eb88c6ba77 *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_zh-tw.iso
81f9e4c4e756b39ee1150f8a48e252b51e38ff5ebcf887740b674f7d5f4ccc09 *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_de-de.iso
5bee75dcff78551a89db01a06244eb41be788b1758b1ee227d0315f2d41b4dc0 *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_en-gb.iso
5f28f9c7bfce3307e8daf5f5a7fbeabb9008776859f828a0348b5f0f46a590d9 *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_en-us.iso
c6a38004e060b0cfb50b8396057b3de688f50fb414b7dde1e77d13f8070465d4 *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_es-es.iso
db7c92d1baeeadd8b7ddca5255dbdeb5966a482f7044715ca5cd1c10cd5fbc6f *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_fr-fr.iso
25664c022805bd0472fd980d5e5b818e43aeca4e40be69ee8391144fad4936f4 *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_it-it.iso
bb447eabadf287e33c1eb51a7684147c48dae8ce3f071ed00fb335f9a85c141e *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_ja-jp.iso
ab6be8a7a31dcb093ce9ec371390a5e35568fdaff6a10d25603e80f8f6ff9630 *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_ko-kr.iso
481e43e4ccb62b4f35543b810a1eee5cc09b1d169bf415aa35f0cef6f64f5f63 *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_pt-br.iso
fe7cae075217c559e3eb25417801a7402dfaa39d93acb29fa9835b8096f74efa *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_zh-cn.iso
4b65c5600907c5ecdc0db0843e36af1bc8be9c52c7b38437dfd9db489f0db60f *19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_zh-tw.iso
Windows 10 Enterprise Evaluation - 2004 build 19041.264
de-de
https://software-download.microsoft.com/download/pr/19041.264.200511-0456.vb_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_de-de.iso
https://software-download.microsoft.com/download/pr/19041.264.200511-0456.vb_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_de-de.iso
en-gb
https://software-download.microsoft.com/download/pr/19041.264.200511-0456.vb_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_en-gb.iso
https://software-download.microsoft.com/download/pr/19041.264.200511-0456.vb_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_en-gb.iso
en-us
https://software-download.microsoft.com/download/pr/19041.264.200511-0456.vb_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_en-us.iso
https://software-download.microsoft.com/download/pr/19041.264.200511-0456.vb_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_en-us.iso
es-es
https://software-download.microsoft.com/download/pr/19041.264.200511-0456.vb_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_es-es.iso
https://software-download.microsoft.com/download/pr/19041.264.200511-0456.vb_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_es-es.iso
fr-fr
https://software-download.microsoft.com/download/pr/19041.264.200511-0456.vb_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_fr-fr.iso
https://software-download.microsoft.com/download/pr/19041.264.200511-0456.vb_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_fr-fr.iso
it-it
https://software-download.microsoft.com/download/pr/19041.264.200511-0456.vb_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_it-it.iso
https://software-download.microsoft.com/download/pr/19041.264.200511-0456.vb_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_it-it.iso
ja-jp
https://software-download.microsoft.com/download/pr/19041.264.200511-0456.vb_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_ja-jp.iso
https://software-download.microsoft.com/download/pr/19041.264.200511-0456.vb_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_ja-jp.iso
ko-kr
https://software-download.microsoft.com/download/pr/19041.264.200511-0456.vb_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_ko-kr.iso
https://software-download.microsoft.com/download/pr/19041.264.200511-0456.vb_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_ko-kr.iso
pt-br
https://software-download.microsoft.com/download/pr/19041.264.200511-0456.vb_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_pt-br.iso
https://software-download.microsoft.com/download/pr/19041.264.200511-0456.vb_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_pt-br.iso
zh-cn
https://software-download.microsoft.com/download/pr/19041.264.200511-0456.vb_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_zh-cn.iso
https://software-download.microsoft.com/download/pr/19041.264.200511-0456.vb_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_zh-cn.iso
zh-tw
https://software-download.microsoft.com/download/pr/19041.264.200511-0456.vb_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_zh-tw.iso
https://software-download.microsoft.com/download/pr/19041.264.200511-0456.vb_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_zh-tw.iso
Windows Server 2003 R2 Generic Product Key.
These Keys cannot be used for License activation. Only helps for default installation of Operating System.
| Windows Server 2003 R2 Standard Edition x86 | PWBJC-22697-D4CVH-FCJWW-DTF9J |
| Windows Server 2003 R2 Standard Edition x64 | XCP6P-7WVXP-F8FQ4-JV6CD-6XV28 |
| Windows Server 2003 R2 Enterprise Edition x86 | XHPV3-PTCWJ-7Y94F-Q6BVH-J849J |
| Windows Server 2003 R2 Enterprise Edition x64 | WQ3GW-Y8GQW-8VJYB-JYM43-D24C8 |
| Windows Server 2003 R2 Datacenter Edition x86 | FXYF6-VTXGX-3JPX9-HJ9K4-6TKTW |
| Windows Server 2003 R2 Datacenter Edition x64 | KDX8X-FYW4T-C6D9J-BKM6M-M89TW |
| Windows Server 2003 R2 Web Edition x86 | GM8KD-GB7JY-QGQYP-XRV74-RT728 |
Generic Product Keys
This Page contains most of the Generic ProductKeys issued by Microsoft. All these keys are blocked on MS Activation Site
Windows XP Pro OEM Edition SP2
From Microsoft Site
To help minimize the potential impact on licensed users, this whitepaper provides steps licensed end users can take to preserve OEM pre-activation when reinstalling the operating system using any of the four scenarios outlined below (sysprep, OOBEinfo, manual and unattended).
The following product keys should be substituted for XXXXX-XXXXX-XXXXX-XXXXX-XXXXX in the solutions discussed below.
Windows XP Professional 32 bit
MVF4D-W774K-MC4VM-QY6XY- R38TB
Windows XP Tablet PC Edition
XT67V-GY7FW-GR6FR-WDK2C-8T97J
Windows XP Professional x64 bit
FM634-HJ3QK-6QVTY-RJY4R-XCR9J
http://www.microsoft.com/technet/prodtechnol/winxppro/deploy/wpadepl.mspx
All of the examples provided above used a beta key for illustration purposes. The product keys listed in this section can be used with any of the answer files and scripted examples. They are blocked at the Microsoft clearinghouse and therefore cannot be used to activate any systems. They provide a number of days (assume 14 days) for you to complete the activation process.
It is absolutely essential that you use the correct type of key, which is a function of the platform type and the media. Choose the key and corresponding sequence number for your scripts from the following table:
Applicability Product Key Whistler Tech Beta Program(All Platforms) PXRQ3-7VPMV-CQWXR-8Y4KX-RD786 Windows XP Home Edition Full product JKTVX-HCRXC-J2YC9-MX3K4-G9X26 Windows XP Home Edition Upgrade C84VB-JYVFD-P7HF4-6KKRJ-7M6XH Windows XP Professional Full product DR8GV-C8V6J-BYXHG-7PYJR-DB66Y Windows XP Professional Upgrade FKTW8-Q7MJ7-JK6GW-9J9RV-HC3C2 Windows XP Home Edition System Builder (Full) KGVXT-F9HVW-XGW9X-QVYVX-HQ9RD Windows XP Professional System Builder (Full) TTGHK-3RC33-BT9DR-3BVYV-BTQ98
Currently no Generic Product Keys are listed for Windows Server 2003 or R2 release
List of Windows Versions for Windows 9x, ME
Released version:
Windows 95: 4.00.950
Windows 95 OSR1: 4.00.950a
Windows 95 OSR2: 4.00.1111
Windows 95 OSR2.1 with update: 4.03.1212
Windows 95 OSR2.1: 4.03.1214
Windows 95 OSR2.5: 4.03.1216
Windows 98 FE: 4.10.1998
Windows 98 SE: 4.10.2222A
Windows Me: 4.90.3000
Windows 95 Retail
CD-ROM Edition
Since I looked at a lot of Windows 95 installation media and
also collected many as well, I'll try to clear things up a little with actual
facts.
First let's clear up what is "retail upgrade" and what is "full
retail": upgrade required the user to own an existing copy of MS-DOS 3.31
or later, Windows 3.0 or later, or OS/2 2.0 or later. If you don't prove your
eligibility to an upgrade, setup would not let you install Windows 95 (but this
can be quite easily bypassed, see below). Full retail, on the other hand, does
not have such restrictions, allowing you to perform a clean install.
The retail part of the name means the product was sold packaged in a box in a
retail store to anyone. This is contrasted by OEM releases, which were licensed
to the hardware manufacturer for inclusion with their hardware, meaning these
copies were not allowed to be sold directly to the end users (althought as you
can imagine, some people broke this rule anyway). This was indicated by the
"For distribution only with a new PC." label on OEM installation
media. As a side note, OEM Service Release 2 and later of Windows 95 were only
available as an OEM release (as the name obviously implies).
The type of installation media is called a product type and there's 9 of them
defined for Windows 95, of which only 7 appear to have actually been used.
The ProductType parameter
is defined in the file SETUPPP.INF inside the PRECOPY*.CAB chain
on the installation media. You can easily override it by placing another
SETUPPP.INF with a different ProductType (or other parameters you want to
change) in the root of the installation source directory. There's also a CCP parameter
in SETUPC.INF, which determines whether or not an upgrade
eligibility check will be performed for upgrade product types. Finally, there's
an OEMUP parameter in SETUPPP.INF, which converts a full OEM
release into an upgrade one, which will still accept OEM keys but can be forced
to perform an eligibility check with CCP=1. Althought OEM upgrade media was
clearly an option, I can't say for certain whether or not this combination was
actually ever used in practice.
Reference - http://www.betaarchive.com
Windows 95 4.00.950 OEM (RTM)
Code:
File: en_win_95_x86_4.00.950_cd_000-04404.iso
CRC-32: 31a787f7
MD4: 70daecae571eeabbce41b4c8e2362202
MD5: 3f7919ceca5f53a08a84c26d692dbb8d
SHA-1: 285298256c8d406a83ff3c45481cbf2099202c46
Windows 95 4.00.950 OEM (OSR1)
Code:
File: en_win_95_x86_4.00.950a_cd_000-27722.iso
CRC-32: 66f7ec0b
MD4: d4de29ac9a560d1b9217c10536794990
MD5: 80dee3cdc0ccb3f4414a1c0c6f45c8b2
SHA-1: 9f28e89aec4dd694f1bb782ca0ec949987902139
Windows Domain Active Directory Schema Version Details
To find the current Active Directory Schema Version, you can use one of the following methods:
Note
The internal root domain that we use in this demo is: "domain.local".
Using "ADSIEdit.msc" or/and "LDP.exe" tools:
Navigate to:
"CN=Schema,CN=Configuration,DC=domain,DC=local"
and review the current "objectVersion" attribute.
Using "DSQuery" command line:
"dsquery * cn=schema,cn=configuration,dc=domainname,dc=local -scope base -attr objectVersion"
The following information provides a mapping between the "objectVersion" attribute value, to
the Active Directory Schema commutability:
13 -> Windows 2000 Server
30 -> Windows Server 2003 RTM, Windows 2003 With Service Pack 1, Windows 2003 With Service Pack 2
31 -> Windows Server 2003 R2
44 -> Windows Server 2008 RTM
47 -> Windows Server 2008 R2 RTM
56 -> Windows Server 2012 RTM
69 -> Windows Server 2012 R2 RTM
87 -> Windows Server 2016 RTM
88 -> Windows Server 2019 RTM
To find the current Exchange Schema Version, you can use one of the following methods:
Note
The internal root domain that we use in this demo is: "domain.local".
Using "ADSIEdit.msc" or/and "LDP.exe" tools:
Navigate to:
"CN=ms-Exch-Schema-Version-Pt, CN=Schema,CN=Configuration,DC=domain,DC=local"
and review the current "rangeUpper" attribute.
Using "DSQuery" command line:
"dsquery * CN=ms-Exch-Schema-Version-Pt,cn=schema,cn=configuration,dc=domain,dc=local -scope base -attr
rangeUpper"
The following information provides a mapping between the "rangeUpper" attribute value, to
the Exchange Schema commutability:
4397 -> Exchange Server 2000 RTM
4406 -> Exchange Server 2000 With Service Pack 3
6870 -> Exchange Server 2003 RTM
6936 -> Exchange Server 2003 With Service Pack 2
10628 -> Exchange Server 2007
11116 -> Exchange 2007 With Service Pack 1
Schema Changes Between Exchange 2000 Server and Exchange Server 2003
Exchange 2007 Schema Changes (SP1)
Microsoft Article Reference - https://social.technet.microsoft.com/wiki/contents/articles/37395.active-directory-schema-versions.aspx
CompactOS
Windows 10 includes tools to help you use less drive space. You can now compress the files for the entire operating system, including your preloaded desktop applications. Compact OS lets you run the operating system from compressed files (similar to WIMBoot in Windows 8.1 Update 1), and single-instancing helps you run your pre-loaded Windows desktop applications in compressed files. The new processes helps maintain a small footprint over time by using individual files, rather than combining them in a WIM file.
You can query whether the operating system is running Compact OS, and change it at any time, using the Compact.exe command.
From Windows PE, determine if the OS is compacted:
Compact.exe /CompactOS:Query /WinDir:E:\Windows
Where E:\Windows is the folder where Windows has been installed.
From an online installation, change from non-compacted to compacted OS:
Compact.exe /CompactOS:always Reference - https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/compact-os
Azure Domain Services
Issue
Our DC was a Windows NT 4.0 Server Single Label Domain that was migrated to Windows Server 2003 as a Single Label Domain, which was eventually migrated to Windows Server 2008 R2 carrying the Single Label Domain. The issues stem from DNS not working well with Single Label Domains and I found a really great article outlining Single Label Domains and we are exhibiting many of the issues outlined in the article.
http://blogs.msmvps.com/acefekay/2009/11/12/active-directory-dns-domain-name-single-label-names/
Resolution -
Work around to our Single Label DNS Domain issue that allows remote computers to join the domain.
In the registry of the client computer you are trying to join to the Single Label Domain add the following registry entry:
Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Netlogon\Parameters
Create a REG_DWORD (32-Bit) Value called AllowSingleLabelDnsDomain
Change the Data Value of the newly created registry entry from 0 to 1
Reboot the computer and you will be able to join your remote computer to the Single Label Domain.
Disk2Vhd does not Support Windows 2000. This tool uses VSS and VSS is not available at Windows 2000.
Only offline conversion is possible with Disk2Vhd
http://www.tekronin.net/2014/01/13/windows-server-2000-p2v-with-disk2vhd/
Make sure that your grandpa server is running on W2K SP4.
Shutdown the server and take off the hard disk.
Install the hard disk on a computer with Windows XP (anything above that is OK too)
Boot up the second computer and make a note of the new volumes.
Download Disk2VHD exe from here
Create VHDs as you want. You can save them to a local drive or if you have a fast network (from my experience 1 Gbps LAN connection would save a 40 GB hard disk in a matter of 15 minutes via network) you can use an existing shared folder. I still prefer to save to VHD format for Windows 2000.
Updated Tool List -
Earlier Tool List - https://nikhilbendre.blogspot.com/2006/01/tools-i-use.html
Will be posting few old documents and articles I had written over the years for trainees.
1. MS-Dos 6.xx Install on Supported Hardware. [Will add Virtual Install Later]
2. Windows 9X installs and tips. [Will add Virtual Install Later]
3. Linux Archives [Old version]
4. Ms SQL Server 6x, 7x, 2000 and later version Install Guides.
5. Ms Exchange Server 5.X 2000 and 2003 evaluation and install steps. [Vintage Tools]
Microsoft Corporation
September 2000
Applies to:
Microsoft Windows NT Embedded 4.0
Summary: This article discusses how Target Designer is used to create Microsoft Windows NT Embedded 4.0 operating system images. (6 printed pages)
Introduction
Hard
Drive
CD-ROM (read-only)
Flash Disk
DiskOnChip
Additional
Information
Target Designer is used to create Microsoft Windows NT Embedded 4.0 operating system (OS) images. Using Target Designer, you configure your operating system image by selecting various components for the OS image. This image is then loaded onto a hardware configuration, creating an embedded system.
Windows NT Embedded 4.0 can be installed and run from the following types of media.
To prep and boot an embedded image for all types of media
The following components can be included in OS images for several types of media:
Using the Write Filter with flash disk media will prevent data from being written to the media, thus ensuring a longer flash disk life. Multiple write operations can degrade the integrity of the media.
The system cloning utility is included on your Windows NT Embedded CD. If the user will install your system from read-only media, you must indicate that you want to clone the target system when you install it to the target media.
To verify that a headless target system is alive, you can include the Serial Console Administration component in your target system, and try connecting to it via serial connection.
The following sections detail how to prepare and boot an embedded OS on several types of media.
Windows NT Embedded 4.0 can be installed and run on embedded systems from both IDE and SCSI hard drives. This section details how to install an embedded OS image on a system with hard drive support.
In order to use a hard disk on your embedded system, the Hard Drive component must be included in your OS image. This component is located in the All Nodes pane under System\Devices\Storage\Fixed Disk. If a SCSI hard disk is to be used instead of the default IDE hard disk, select the SCSI component instead.
To make either a FAT or an NTFS partition bootable, you must copy a Windows NT boot sector to the partition boot sector. You can use the contents of the MungeBoot folder on the Windows NT Embedded 4.0 CD-ROM 1 to create an NT Boot Partition Utility Disk. To create this disk on your development machine, place a blank floppy disk into the A: drive and, with CD 1 in the D: drive, execute the following commands:
C:\> D: D:\> CD MungeBoot D:\MungeBoot\> webimgnt munge622.144
The last command will start the Web Image NT application. Click the A: Drive button to create the utility disk. When the operation is complete, remove the floppy disk from the A: drive and label it, "NT Boot Partition Utility Disk."
After the utility disk has been created, do the following.
To create a bootable Windows NT Embedded 4.0 partition on an embedded system with an attached floppy disk drive
A:\> NTBOOT
This command replaces the boot sector of the hard drive or DiskOnChip partition on the target device with the correct Windows NT boot sector.
Now the partition is configured to boot a Windows NT Embedded 4.0 target image. The next section details how to copy an OS image to a target device.
After the bootable partition has been created, the OS image must be copied to the target device before the embedded system can run. A common method for copying the OS image to the target device is to install the target device's hard drive into the development machine and copy the OS image to that hard drive. When the copy is complete, the target device's hard drive is reinstalled into the target device. When the target device is started, the target device will boot from the OS image on the hard drive.
The following procedure details how to download an OS image to a target device using the network transfer method. In order to use the network transfer method, you must have a network card installed on your target device.
To download an OS image to a target device using the network transfer method
NET USE * //<computername>/embed
This command will map the shared embed folder to a drive on your target device.
FORMAT C: /Q XCOPY D:\*.* . /s/e
The target machine should now boot from the image installed on it when powered on.
For an embedded system to boot from read-only media, it must run from an El Torito format CD-ROM. Using the El Torito CD as Disk component, you can boot and run your system by using a CD-ROM in the El Torito format. If you plan to install your system on a bootable CD-ROM, use the Write Filter and El Torito CD as Disk components together. When the El Torito CD as Disk component is selected, select the FAT file system to reduce interaction with the Write Filter and increase memory for write operations.
Your configuration must include the following components:
When creating an embedded system that runs from a CD-ROM, make sure to consider the following issues. The BIOS for your embedded system must support the El Torito format CD-ROM. A system that boots from a read-only storage device cannot use a page file. The target system must recognize the El Torito CD-ROM as a standard block-mode disk device.
You can use any basic input/output system (BIOS) that boots Windows NT 4.0 to boot your embedded system. However, if your configuration includes an El Torito CD-ROM, BIOS recognizes the CD-ROM as the first drive on the system and Windows NT Embedded supports only the first partition on the CD. Therefore, the Advanced RISC Computing (ARC) name of the bootable El Torito partition is multi(0)disk(0)rdisk(0)partition(1).
To allow the user to choose whether to boot from an El Torito CD-ROM or a regular hard disk partition, you must add the appropriate code to the Boot.ini file. An example of the code follows:
[Boot Loader] timeout=10 Default=multi(0)disk(0)rdisk(0)partition(1)\WINNT [Operating Systems] multi(0)disk(0)rdisk(0)partition(1)\WINNT=''El Torito'' multi(0)disk(0)rdisk(1)partition(1)\WINNT=''1st HDD, 1st partition'' multi(0)disk(0)rdisk(1)partition(2)\WINNT=''1st HDD, 2nd partition'' multi(0)disk(0)rdisk(2)partition(1)\WINNT=''2nd HDD, 1st partition''
The following procedure details how to record an embedded OS image onto an El Torito format CD-ROM.
The target machine should now boot from the image installed on it when powered on with the CD-ROM you created in the CD-ROM drive. When the target system boots from the CD-ROM, the CD tray is locked until you shut down the system.
Using a flash disk, you can boot your embedded system and perform read/write operations. Data written to a flash disk is saved when the power is turned off.
You can include the Write Filter component in your OS image for use with flash disk media. If you use the Write Filter component on read/write media, changes made at run time are not saved. During a write operation to a disk, this component filters data that has been changed and puts it in memory instead of writing it to the disk. During a read operation from a disk, the write filter reads the data from where it is stored in memory, not from the disk. When you shut down the target system, the data written to memory is lost. The target system always boots from the original data. Using the Write Filter with flash disk media will prevent data from being written to the media, thus ensuring a longer flash disk life. Multiple write operations can degrade the integrity of the media.
PCMCIA drivers are required when flash disk media is used with an embedded OS. A general PCMCIA component definition file (.kdf) is required. Including this .kdf file in the build of your OS image will enable your OS to recognize PCMCIA cards and related drivers.
If you have a network adapter attached to your target device, you can download your image to a flash disk using the procedure detailed above. If a network adapter is not installed, detach the storage device form your target machine, attach it to the development machine, and copy the target system to the storage device. When the copy operation is complete, reattach the storage machine to the target device and boot the embedded system. The target machine should now boot from the image installed on it when powered on.
The DiskOnChip is a flash disk device. In an embedded system the DiskOnChip simulates an IDE hard drive. To use the DiskOnChip media, you must include support for IDE and include the driver component for the DiskOnChip in your OS image. The procedure to boot an embedded OS from the DiskOnChip is identical to booting an image from an IDE hard drive.
The Microsoft Knowledge Base article, Q249306: HOWTO: Create a Windows NT-Bootable IDE Partition contains information relevant to this article.
See the Windows lifecycle fact sheet for information about supported versions and end of service dates.