How to reset trust between parent and child domains

Try this from the parent domain:

NETDOM TRUST parentdomain.com /Domain:child.parentdomain.com /UserD:child\administrator /PasswordD:* /UserO:parent\administrator /PasswordO:* /Reset /TwoWay

VMware: Not using Fault-tolerance? Turn off FT to enable Cluster Compliance

http://kb.vmware.com/kb/1017714

To disable Fault Tolerance compliance checks:

1. Right-click the cluster and click Edit Settings > VMware HA > Advanced Options. 
2. Enter das.includeFTcomplianceChecks in a blank field, and give it a value of false.
   
   When this setting is applied, Fault Tolerance Compliance Checks are removed from the description under theProfile Compliance Tab for the cluster and is no longer a role during a Cluster Compliance check.

Note: To re-enable the checks, remove the das.includeFTcomplianceChecks option.

To remove unused plug-in from vCenter use Managed Object Reference

Found at http://vcenterservername/mob

Logon with vSphere credentials;

1. Click on content, then
2. Extension manager
3. Find the plug-in which needs to be removed; for example, look for extensionList["VirtualCenter"], the parameter you need is just VirtualCenter
4. Click UnregisterExtension, in the VALUE field, enter the name of the plug-in you wish (in this example it's VirtualCenter
5. Click on Invoke Method (to remove plug-in

Upgrading from Lower version of Windows 7 to Enterprise

This steps are for Home Premium to Enterprise. Have not had the opportunity to try from Windows Starter Edition. Will update post once that is successfully tested:-


Upgrading from Home Premium is possible, just make the following registry changes:

Under Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion modify the following keys:

• EditionID from “HomePremium” to “Enterprise”.
• ProductName from “Windows 7 HomePremium” to “Enterprise”.

Default Gateway disappearing after reboot

This is an interesting problem. It's a possible bug after applying Vista SP2.

Symptoms:
Manually added Default Gateway disappears upon reboot.

Cause:
Null or empty line in registry key "DefaultGateway | REG_MULTI_SZ"

Solution:

1. Start Regedit
2. Navigate to  HKLM\System\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\
3. Select CLSID of network adapter (you can identify your adapter by looking at the IPAddress registry Data field). 
4. Doubleclick "DefaultGateway" (You will see a list of all gateways that disappeared, especially if you've tried multiple gateways and rebooted a few times). Very likely the first line will be blank or empty. Remove this first empty line, click OK, exit regedit and reboot.

RSA II Slimline Refresh 1 (Remote Supervisor Adapter II Slimline Refresh 1 - Part number 39Y9566)

This is a real PITA. Nothing like searching/googling, trawling through the net looking for this needle in the haystack.

Especially if your fingers are fast becoming frozen after spending 6 hours in a proper data center...

Adapter ships with old firmware and won't work with newer servers unless firmware is updated.

Firmware is also very difficult to find from IBM's website.

When you try to open a remote console (after installing the adapter) you'll hit this error:
The firmware on this ASM does not include functionality to support this server. You can update its firmware on the next page

In my case, had just added the (P/N 39Y9566 Remote Supervisor Adapter II Slimline refresh 1)


There are two packet files that to be updated in sequence:
1st - PAETBRUS.PKT
2nd - PAETMNUS.PKT


You can find the firmware update files here:
http://www-947.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=MIGR-64575&brandind=5000008

vCenter and SQL 2008 SP1 on Windows 2008 R2

1.  vCenter won't install on the Web Edition.
2. You can install SQL2008 on 2008 R2, just have to disable all services until SP1 has been applied.
3. When creating the ODBC connections, use "%systemdrive%\Windows\SysWoW64\Odbcad32.exe" and not the ODBC from Administrative Tools section.

BEFORE, installing vCenter Server, do:

1.       Start -> Administrative Tools -> Server Manager.

2.       From the left pane, select “Features”

3.       On the right hand pane, click “Add Features”

4.       Expand .NET Framework 3.5.1 Features

5.       Select only .NET Framework 3.5.1 (do not select WCF Activation as it will install IIS which conflicts with Apache Tomcat, which of course vCenter will install).

vCenter Server should now install without any issues.