How to replace Dell MD3200 Failed Battery Pack

One of the RAID Controller’s battery on my Dell PowerVault MD3200 has failed today so I got a replacement part to replace it.
Replacing the battery requires detaching the RAID Controller from the MD3200.  However, there was no down time because the other RAID Controller is still functioning.  We just need to make sure all the disk groups have been changed over to the working RAID Controller by using the PowerVault Modular Disk Storage Manager in the Logical View.
Then in the Physical view, select the RAID Controller to be removed.

Click on the Advanced menu and select Recovery –> Place RAID Controller Module –> Offline.  This will place the RAID Controller offline and we are ready to remove it.

This is how the RAID Controller with the battery removed looks like.

The high speed 8GB SDHC card on the RAID Controller.

The battery pack.

After replacing the the battery pack, reinsert the RAID Controller back and place it online.  Wait for a few minutes and everything is back to normal.

explorer.exe error on windows 7

Here's how to fix this issue:
1. CTRL-Alt-Del to bring up Task Manager.
2. Click File | New Task(run).
3. Type regedit in the Run box and click OK.
4. Browse to the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution.options
5. Under this key there will be subkeys named explorer.exe and iexplorer.exe. Delete the explorer and iexplorer keys entirely. They should not be listed under the Image File Execution.Options key.
6. Close the Registry Editor.
7. Restart the computer.
Assuming no other viruses / adware / spyware / malware are interfering, the Windows desktop should load fine now.

OR

hxxp://en.kioskea.net/forum/affich-9082-explorer-exe-corrupted-or-infected
Click Start.
In the Search Bar, type regedit and press Enter.
Locate the following key: HKEY_LOCAL_MACHINE\SOFTWARE\ Microsoft\ SQMClient\Windows\DisabledSessions
In the right pane delete this subkey: MachineThrottling
Turn your computer off and back on for the change to take effect.

OR

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell <- Check "explorer.exe"

OR

1. insert Windows 7 installer DVD
2. Browse DVD -> You find folder name "sources"
3.Then you will find "install.wim"
4. Extract with "7 Zip" software
5. under "Windows" Folder -> explorer.exe -> copy to c:\files
6. under "Windows\system32\" Folder -> shell32.dll -> copy to c:\files
7. On your machine, do the followings

c:\windows>takeown   /f      explorer.exe
c:\windows>icacls      explorer.exe            /grant          zawhtet:F
c:\windows>rename   explorer.exe             explorer.exe_old
c:\windows>move      explorer.exe_old      c:\files
c:\files>copy               explorer.exe             c:\windows\


c:\windows\system32> takeown    /f    shell32.dll
c:\windows\system32>icacls         shell32.dll           /grant         zawhtet:F
c:\windows\system32>rename       shell32.dll           shell32.dll_old
c:\windows\system32>move          shell32.dll             c:\files
c:\files>copy               shell32.dll                c:\windows\system32\


Restart your Windows 7 Computer and check the status. Good Luck !

One more thing, you got to run these commands on "Local Administrator's command prompt"
OR
Start -> Run -> cmd -> right click -> run as administrator
OR
Start -> Run -> cmd -> ctl+shift+Enter

VMWare ESX 4 (Commmands)

Configuring networking from the ESX service console command line

To configure networking from the ESX service console command line:

1. Ensure the network adapter you want to use is currently connected with the command:
   
   [root@server root]# esxcfg-nics –l
   
   The output appears similar to:
   
   Name PCI Driver Link Speed Duplex Description
   vmnic0 06:00.00 tg3 Up 1000Mbps Full Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet
   vmnic1 07:00.00 tg3 Up 1000Mbps Full Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet
   
   In the Link column, Up indicates that the network adapter is available and functioning.

2. List the current virtual switches with the command:
   
   [root@server root]# esxcfg-vswitch –l
   
   The output appears similar to:
   
   Switch Name Num Ports Used Ports Configured Ports Uplinks
   vSwitch0 32 3 32 vmnic0
   
   PortGroup Name Internal ID VLAN ID Used Ports Uplinks
   VM Network portgroup2 0 0 vmnic0
   
   In the example output, there exists a virtual machine network named VM Network with no Service Console portgroup. For illustration, the proceeding steps show you how to create a new virtual switch and place the service console port group on it.
3. Create a new virtual switch with the command:
   
   [root@server root]# esxcfg-vswitch –a vSwitch1
4. Create the Service Console portgroup on this new virtual switch:
   
   [root@server root]# esxcfg-vswitch –A “Service Console” vSwitch1
   
   Because there is a space in the name (Service Console), you must enclose it in quotation marks.
   
   Note: To create Service Consoles one at time, you may need to delete all previous settings. For more information, see Recreating Service Console Networking from the command line (1000266).
5. Up-link vmnic1 to the new virtual switch with the command:
   
   [root@server root]# esxcfg-vswitch –L vmnic1 vSwitch1
6. If you need to assign a VLAN, use the command:
   
   [root@server root]# esxcfg-vswitch -v -p “Service Console” vSwitch0
   
   where is the VLAN number. A zero here specifies no VLAN.
7. Verify the new virtual switch configuration with the command:
   
   [root@server root]# esxcfg-vswitch –l
   
   The output appears similar to:
   
   Switch Name Num Ports Used Ports Configured Ports Uplinks
   vSwitch0 32 3 32 vmnic0
   
   PortGroup Name Internal ID VLAN ID Used Ports Uplinks
   Service Console portgroup5 0 1 vmnic0
   
   Switch Name Num Ports Used Ports Configured Ports Uplinks
   vSwitch1 64 1 64 vmnic1
   
   PortGroup Name Internal ID VLAN ID Used Ports Uplinks
   Service Console portgroup14 0 1 vmnic1
8. Create the vswif (Service Console) interface. For example, run the command:
   
   [root@server root]# esxcfg-vswif –a vswif0 –i 192.168.1.10 –n 255.255.255.0 –p “Service Console”
   [‘Vnic’ warning] Generated New Mac address, 00:50:xx:xx:xx:xx for vswif0
   
   Nothing to flush.
9. Verify the configuration with the command:
   
   [root@esx]# esxcfg-vswif –l
   Name Port Group IP Address Netmask Broadcast Enabled DHCP
   v swif0 Service Console 192.168.1.10 255.255.255.0 192.168.1.255 true false
10. Verify the networking configuration on the ESX host. See Verifying ESX host networking configuration on the service console (1003796) .

Recreating Service Console networking from the command line

Note: ESX 4.0 Update 2 introduces a new tool that simplifies the process of creating or restoring networking in the ESX service console. For more information, see Configuring or restoring networking from the ESX service console using console-setup (1022078).

To delete and recreate a virtual switch and Service Console from the command line:

Note: On your system the vswif, vmnic, vSwitch numbers and network settings are different. 

1. Run the following command to list the name of the vswif adapter:
   
   # esxcfg-vswif -l
2. Run the following command to delete the vswif adapter:
   
   # esxcfg-vswif --del vswif0
3. Run the following command to list the name of the vSwitch:
   
   # esxcfg-vswitch -l
4. Run the following command to delete the vSwitch:
   
   # esxcfg-vswitch -d vSwitch0
5. Run the following command to create the vSwitch:
   
   # esxcfg-vswitch -a vSwitch0
6. Run the following commands to create default port groups for vSwitch:
   
   # esxcfg-vswitch -A "VM Network" vSwitch0
   # esxcfg-vswitch -A "Service Console" vSwitch0
7. Run the following command to create the vswif adapter:
   
   # esxcfg-vswif --add --portgroup "Service Console" --ip=nnn.nnn.nnn.nnn --netmask=255.255.255.0 vswif0 
8. Run the following command to verify that the settings in the network file are correct:
   
               # cat /etc/sysconfig/network
   
   NETWORKING=yes
   GATEWAYDEV=vswif0
   HOSTNAME=host.domain.com
   GATEWAY=nnn.nnn.nnn.nnn
9. Run the following commands to list all of the network adapters and associate a vmnic which has a link status of up:
   
   # esxcfg-nics -l
   # esxcfg-vswitch -L vmnic1 vSwitch0
10. Run the following command to verify that the vmnic is associated with the vSwitch:
    
    # esxcfg-vswitch -l
11. Ping an IP address to check for network connectivity. If the ping fails, remove the previous vmnic from the vSwitch and try another adapter that has a link status of up.
    
    # esxcfg-vswitch -U vmnic1 vSwitch0
    # esxcfg-vswitch -L vmnic2 vSwitch0
12. Run the following command to change the vlan ID of a vSwitch:
    
    # esxcfg-vswitch -p "VM Network 1" -v 10 vSwitch0
13. If you make any manual changes to /etc/sysconfig/network, run the following command to restart the network service:
    
    # service network restart

For more information, see Configuring a VLAN on a portgroup (1003825).

For information on vNetwork Distributed Switches, see Configuring vSwitch or vNetwork Distributed Switch from the command line in ESX 4.0 (1008127).

Check All your VMs and ID

vim-cmd    vmsvc/getallvms  

Start The VM
vim-cmd    vmsvc/power.on   48

Stop The VM
vim-cmd    vmsvc/power.off   48

Restart The VM
vim-cmd    vmsvc/power.restart  48

If you need to restart your VM on a daily basis I would edit and add the cron job in:
vi   var/spool/cron/crontabs/root

List all the commands under 
vim-cmd vmsvc

List the vms & file path
vmware-cmd -l

Start the VM Machine
vmware-cmd "/vmfs/volumes/4c16a0ec-2c7ebe2a-6ad5-0011s8azz71c/OpenSolaris 2009.06/OpenSolaris 2009.06.vmx" start

Power-On or Off Status
vmware-cmd -l | sed '/^$/d' |  while read VMX ; do STATE=$(vmware-cmd  "${VMX}" getstate | awk ' { print $3 } ') ;  echo "${VMX}" = "${STATE}" ; done


Check Available Network Cards

esxcfg-nics -l

vm-support -x 

vm-support  -X   100 

vmware-cmd.pl   -H 192.168.1.1 -l zawhtet

Ref:hxxp://benincosa.org/blog/?p=266

ps -auxwww | grep 100

kill  -9  100

Workaround for Dell OpenManage Server Administrator installation fails prerequisite checks

When trying to install Dell OpenManage Server Administrator (OMSA) on a PowerEdge R610 server running Windows Server 2003 R2,  I received the following error from the prerequisite checker:
 ”This is not a supported server. Server Administrator software can only be installed on supported servers.”
I recevied this error when trying to install OMSA 5.4, 5.5, and 6.0.1. To get around the error you can run the installer with the option to bypass the prerequsite checker. To do so, from command prompt, run the following:
C:\OpenManage\windows\SystemsManagement\msiexec /i SysMgmt.msi SYSTEMCHECK=NO
Dell’s official documentation says version 5.4 and 5.5 of OMSA are not supported on the R610, but it runs great on many systems in my environment.

hxxp://support.dell.com/support/edocs/software/smsom/5.4/en/qig/html/index.htm#wp1130494

Network Connectivity Status Indicator

Windows Server 2008 includes a feature called Network Connectivity Status Indicator (NCSI), which is part of a broader feature called Network Awareness. Network Awareness collects network connectivity information and makes it available through an application programming interface (API) to services and applications on a computer running Windows Server 2008. With this information, services and applications can filter networks (based on attributes and signatures) and choose the networks best suited to their tasks. Network Awareness notifies services and applications of changes in the network environment, thus enabling applications to dynamically update network connections.
Network Awareness collects network connectivity information such as the Domain Name System (DNS) suffix of the computer and the forest name and gateway address of networks that the computer connects to. When called on by Network Awareness, NCSI can add information about the following capabilities for a given network:

• Connectivity to an intranet
• Connectivity to the Internet (possibly including the ability to send a DNS query and obtain the correct resolution of a DNS name)

NCSI is designed to be responsive to network conditions, so it examines the connectivity of a network in a variety of ways. For example, NCSI tests connectivity by trying to connect to http://www.msftncsi.com, a simple Web site that exists only to support the functionality of NCSI.

Overview: Using NCSI in a Managed Environment

In a managed environment, you might choose to use NCSI because of the way it supports services and applications that require network connectivity. However, you can disable NCSI through Group Policy.

How NCSI Communicates with a Site on the Internet

The following list describes how NCSI might communicate with a Web site to determine whether a network has Internet connectivity:
Specific information sent or received:

• Type of Request that NCSI Sends	What NCSI Expects to Receive if Connectivity Exists
  A request for http://www.msftncsi.com/ncsi.txt	A page called ncsi.txt containing the following line of text with no terminating new line or other non-printing characters: Microsoft NCSI (Page headers disable caching.)
  A request for DNS name resolution of dns.msftncsi.com	The resolution of the DNS name to: 131.107.255.255

• Default setting and ability to disable: By default, Network Awareness (which includes NCSI) is enabled. NCSI can be disabled by using Group Policy.
• Triggers: Network Awareness and its subfeatures gather information flexibly—that is, by using complex algorithms that respond to changing network conditions. This means that triggers can vary, but the following are examples of typical triggers that can cause NCSI to communicate across the Internet:
  
  
  • Someone first logs on after the computer has been restarted
  • The computer connects to a different network
  • The computer is brought into a hot spot (public wireless access area) that requires sign-in
• User notification: NCSI does not notify the user before attempting to collect information. It does notify the user or the application when there are changes in connectivity (for example, loss of Internet connectivity). Note that an application that uses NCSI can be written to include user notifications if appropriate to the design and function of the application.
• Logging: NCSI does not log events in Event Viewer.
• Privacy, encryption and storage: NCSI does not use encryption (both the requests it sends and the responses it receives are standardized, as shown in the table earlier in this subsection). Internet Information System (IIS) logs are stored on the server at www.msftncsi.com. These logs contain the time of each access and the IP address recorded for that access. These IP addresses are not used to identify users, and in many cases, they are the address of a network address translation (NAT) computer or proxy server, not a specific client behind that NAT computer or proxy server.
• Transmission protocol and port: NCSI uses HTTP over port 80. For DNS requests, NCSI uses the DNS port, which by default is port 53.

Controlling Communication Between NCSI and a Site on the Internet

You can prevent NCSI from connecting to http://www.msftncsi.com by using Group Policy. The following subsections provide more information.

How Preventing NCSI from Communicating Across the Internet Can Affect Users and Applications

If you use Group Policy to prevent NCSI from connecting to http://www.msftncsi.com, applications that perform checks for the existence of Internet connectivity might work more slowly. Also, if a computer running Windows Server 2008 is brought into a hot spot that requires sign-in, the computer might not detect the hot spot.

Procedures for Controlling Communication Between NCSI and a Site on the Internet

The following procedure describes how to use Group Policy to prevent NCSI from communicating across the Internet.

To Prevent NCSI from Communicating Across the Internet by Using Group Policy

1. See Appendix B: Resources for Learning About Group Policy for Windows Server 2008 for information about using Group Policy. Using an account with domain administrative credentials, log on to a computer running Windows Server 2008 (with the Group Policy Management feature installed) or running Windows Vista with SP1 and containing the Group Policy Management Console (GPMC) that is included in Remote Server Administration Tools for Windows Server 2008. Open GPMC by running gpmc.msc, and then edit an appropriate Group Policy object (GPO).
   

   You must perform this procedure on a computer running the software described in this step.

2. Expand Computer Configuration, expand Policies, expand Administrative Templates, expand System, expand Internet Communication Management, and then click Internet Communication settings.
3. In the details pane, double-click Turn off Windows Network Connectivity Status Indicator active tests, and then click Enabled.

   You can also restrict Internet access for this and a number of other features by applying the Restrict Internet communication policy setting. This setting is located in either Computer Configuration or User Configuration, in Policies\Administrative Templates\System\Internet Communication Management. For more information about this Group Policy and the policies that it controls, see Appendix C: Group Policy Settings Listed Under the Internet Communication Management Category in Windows Server 2008.

Additional References

For more information about how applications can use Network Awareness in Windows Server 2008, see the MSDN Web site at:
http://go.microsoft.com/fwlink/?LinkId=108692

Active Directory CMD

Active Directory Group Name Query and Export List

dsquery group -name "My Group A" | DSGET group -members  > Group-A-members.txt

Organization ADD

dsadd ou "ou=Development, ou=NY-OFFICE, dc=mmx, dc=com"

Group ADD

dsadd group "cn=Development Team, ou=Groups, ou=NY-OFFICE, dc=mmx, dc=com" -secgrp yes -scope g

User ADD

dsadd user "cn=zawhtet, ou=Development Team, ou=NY-OFFICE, dc=mmx, dc=com" -fn Zaw -ln Htet -pwd hateUnow99 -memberof "cn=Development Team, ou=Groups, ou=NY-OFFICE, dc=mmx, dc=com"  -mustchpwd yes

Open two excel sheets at the same time

I tried the solution above for the Win7 Excel 2010 environment and was unsuccessful (using the same guide lines for Office14). I tried the following change and was able to open the two Excel windows properly.

Works for
Excel 2010 & Win7 (could work for 07 not tested)
------------------------------------------------------------------------
Open Registry Editor ver6.1

-Go to Branch:
HKEY_CLASSES_ROOT\Excel.Sheet.12\shell\Open\command

(Note: it doesn't matter what is listed under default)

-Change the value command and under data remove /dde (above listed /e) and add after existing string the following code below

/p "C:Program Files (x86)Microsoft OfficeOffice14EXCEL.EXE" /e "%1"

(Note: /p switch will ignore the (default) open settings)

-Go to Branch:
HKEY_CLASSES_ROOT\ExcelSheet.12\shell\Open\ddeexec

-Rename ddeexec2

Configure Protocol Logging in Exchange Server 2010

Get-ReceiveConnector 
Set-ReceiveConnector -Default Receive Connector -ProtocolLoggingLevel Verbose

Get-SendConnector 
Set-SendConnector -Default Send Connector -ProtocolLoggingLevel Verbose

[PS] C:\>Set-TransportServer NY-CAS-2K8 -ReceiveProtocolLogPath  "D:\Message-Log"
[PS] C:\>Set-TransportServer NY-CAS-2K8 -SendProtocolLogPath "D:\Message-Log"
[PS] C:\>Set-TransportServer NY-CAS-2K8 -ReceiveProtocolLogMaxFileSize 30MB
[PS] C:\>Set-TransportServer NY-CAS-2K8 -SendProtocolLogMaxFileSize 30MB
[PS] C:\>Set-TransportServer NY-CAS-2K8 -ReceiveProtocolLogMaxDirectorySize 400MB
[PS] C:\>Set-TransportServer NY-CAS-2K8 -SendProtocolLogMaxDirectorySize 400MB
[PS] C:\>Set-TransportServer NY-CAS-2K8 -ReceiveProtocolLogMaxAge 180.00:00:00
[PS] C:\>Set-TransportServer NY-CAS-2K8 -SendProtocolLogMaxAge 180.00:00:00

Protocol Logging logs all the SMTP conversation occurring between Exchange Server 2010 as part of message delivery. These conversations occur on Send or Receive Connectors that are configured on Exchange Server 2010 Hub Transport or the Edge Transport servers. These log files are helpful for administrators to troubleshoot mail flow problems. By default, protocol logging is disabled on all Send or Receive Connectors. Exchange Server 2010 uses Circular logging to restrict the log file size and file age to help control the hard disk space.

All the Receive Connectors configured on Hub Transport or Edge Transport share the same protocol log files and protocol log options. These log files and log options are different from the Send Connector configured on Hub Transport and the Edge Transport on the same servers.

Enable or disable protocol logging on connectors

You need to be assigned permissions before you can perform this procedure.

  How to configure Protocol Logging on Connectors from the EMC

1. Perform one of the following steps:
   • On an Edge Transport server, in the EMC, select Edge Transport and then click the Receive Connectors tab in the work pane.
   • On a Hub Transport server, expand Server Configuration and then select Hub Transport. In the result pane, select the server that has the Receive connector you want to modify and then open its Properties.
2. Click Properties under the name of the Receive Connector.
3. Click the General tab and use the drop-down box next to Protocol logging level to enable or disable protocol logging. None disables protocol logging, and Verbose enables protocol logging.
4. Click Ok to save the settings.

The above procedure is similar for Send connectors. To access Send connectors, you will have navigate to Organization Configuration > Hub Transport.

How to Use Shell to Enable or Disable Protocol Logging on Receive Connector

In the below example, we have enabled protocol logging level for the Receive connector "Connection from Techpeoples.net".

Get-ReceiveConnector

Set-ReceiveConnector -Connection from Techpeoples.net -ProtocolLoggingLevel Verbose

How to Use Shell to Enable or Disable Protocol Logging on Send Connector

In the below example, we have enabled protocol logging level for the Send connector "Connection from Techpeoples.net".

Get-SendConnector

Set-SendConnector -Connection from Techpeoples.net -ProtocolLoggingLevel Verbose

How to Configure the Location of the Protocol Log Files

The default location of Receive connector log files are at C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\ProtocolLog\SmtpReceive, and the Send connector protocol log files location is C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\ProtocolLog\SmtpSend.

How to change the location of Receive Connector log files:

Get- TransportServer

Set-TransportServer PC01 -ReceiveProtocolLogPath "C:\Receive SMTP Logs"

How to change the location of Send Connector log files:

Get-TransportServer

Set-TransportServer PC01 -SendProtocolLogPath "C:\Send SMTP Logs"

Log file location can also be changed from the Exchange Console.

How to Configure the Maximum Size of each Protocol Log File

The default size of each protocol log file is 10MB. All Receive connectors on the server share the same protocol log files and all Send connectors on the same server share the same protocol log files. When this limit is reached, a new protocol log file is created until the protocol log directory reaches its specified maximum size or a protocol log file reaches its specified maximum age. Circular logging deletes the oldest log file after the maximum size or maximum age limit is reached.

We cannot use the Exchange Console to change the maximum size of each protocol log file:

Below we have used to syntax to change the maximum file size of Send and Receive connector from the Shell:-

Set-TransportServer PC01 -ReceiveProtocolLogMaxFileSize 30MB

Set-TransportServer PC01 -SendProtocolLogMaxFileSize 30MB

How to Configure the Maximum Size of each Protocol Log Directory

The default size of each protocol log directory is 250MB. All Receive connectors on the server share the same protocol log files and all Send connectors on the same server share the same protocol log files. When this limit is reached, a new protocol log file is created until the protocol log directory reaches its specified maximum size or a protocol log file reaches its specified maximum age. Circular logging deletes the oldest log file after the maximum size or maximum age limit is reached.

We cannot use the Exchange Console to change the maximum size of each protocol log file:

Below we have used to syntax to change the maximum directory size of Send and Receive connector from the Shell:-

Set-TransportServer PC01 -ReceiveProtocolLogMaxDirectorySize 400MB

Set-TransportServer PC01 -SendProtocolLogMaxDirectorySize 400MB

How to Configure the Maximum Age of Protocol Log Files

The default age of each protocol log file is 30 days. All Receive connectors on the server share the same protocol log files and all Send connectors on the same server share the same protocol log files. When this limit is reached, a new protocol log file is created until the protocol log directory reaches its specified maximum size or a protocol log file reaches its specified maximum age. Circular logging deletes the oldest log file after the maximum size or maximum age limit is reached.

We cannot use the Exchange Console to change the maximum size of each protocol log file:

Below we have used to syntax to change the maximum directory size of Send and Receive connector from the Shell:-

Below we are configuring the age limit on Send and Receive connector to 60 days.

Set-TransportServer PC01 -ReceiveProtocolLogMaxAge 60.00:00:00

Set-TransportServer PC01 -SendProtocolLogMaxAge 60.00:00:00

Downgrade: Change Windows 7 Ultimate to Premium or Professional (Step by Step)

  A Windows 7 Ultimate Installation can normally not change into a minor version of "Windows 7 Home Premium" or "Professional". If you have installed a preview version of Windows 7 Ultimate (e.g. beta, release candidate build 7100 or RTM build 7600) and want to install a cheaper version Windows 7 Home Premium or Professional the installation is refused:

 But with a change of a registry key whilst installation you can fake a minor version - so you can install the minor version

Change these registry keys

A re-boot after change of these registry keys is not necessary.

he version name to be entered must be identical to the version name on the installation DVD. See here the differences of an English and a German installation

All data, documents, music and movie files, installed driver and programs, shortcuts, program and user settings are retained. Only in a few Windows 7 programs some settings are reset to the initial settings; e.g. in the "services". After the downgrade the Windows 7 installation, of course, must be re-activated.

Attention: In Windows 7 Ultimate Build 7100 (Release Candidate) the effort is greater. First the entire DVD content must be copied to a folder to the hard drive. Then open in subfolder "sources" the file "cversion.ini" and change the entry "MinClient=7233.0" to "MinClient=7077.0". Then you can start the installation with "Setup.exe" (one folders hierarchy up). After the installation the entire folder can be deleted.