After Powering up the servers even couples of times. You might have a strange boot up issue with your Hypervisor and and IBM XSeries with an EFI Firmware.

During the last stage of the Boot Sequence you might received :

Hypervisor : Boot Failed or the system loop and restart.

To avoid this behavior, Go to your System Boot Sequence and ADD : Legacy Only as the first Boot Device.

This will force the EFI to turn off and boot as a Normal “Legacy” Bios and Power up again your Hypervisor !

Thanks to the IBM Technical support for this one.

For more information read page 5 (or the whole document): introducing_uefi-compliant_firmware_on_ibm_system_x.1.0

For everyone you have a Sonicwall with enhanced OS and you want to forward a services but the WAN port need to be different from the LAN port. This one is a bit tricky.

Scenario Terminal Services Session

external IP : Port 3387 to Internal IP Port 3389

Create your WAN port Services (if it’s not Standard based on our scenario : 3387)

In the Sonicwall Management :

Go to :

Network -> Services -> Add Service *** Do not add a Services Group ! ***

Name : Custom RDP
Protocol : TCP(6)
Port Range : 3387 – 3387

Create you port forwarding with the Public Server Wizard as usual. (This is more simple all the rules will be created including the NAT)

Go to: Firewall, On the Top, Select Wizards
Select Public Server Wizard, Next
Select the services Type Created previously : Custom RDP, Next
Enter your internal server IP, Next
Enter your Public server IP, Next

Apply, Close

After we will modify the Translation Port manually.

Go To :

Network, Interface, NAT Policies.

Choose you NAT policy :

• Original Source: Any
• Translated Source: Original
• Original Destination: rdp_publicIP
• Translated Destination: rdp_privateIP
• Original Service: Custom RDP
• Translated Service: Terminal Services RDP
• Inbound Interface: WAN
• Outbound Interface: Any
• Comment: Enter a short description
• Enable NAT Policy: Checked
• Create a reflective policy: Unchecked

The Translated Service must be change from Original to The internal Server port

Click OK

Test your RDP with you RDP client :

Address : PublicIP:3387

This should be good !

This is from Quest technical support :

if you want to improve the speed of vreplicator :

Upgrade the HW for the Virtual Appliance from v4 to v7.

Upgrade the VA to 2 Gig Ram

Upgrade the VA 2 CPU

Remove and re-add nic from Flexible to E1000 on the VA

This should improve the replication speed.

If you have any issue with VMware Tools after a P2V convertion, you need to verify if the folder redirection is enable, if yes update all those registry key if they have a UNC path :

HKEY_CURRENT_USEREnvironnement
TEMP AND TMP

HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionExplorerUser Shell Folder
Check all the key and update all.

Start, Run, cmd

Type
set devmgr_show_nonpresent_devices=1
hit Enter
type devmgmt.msc hit enter

In the Device Manager window

Click on View/Show hidden devices/
Remove everything that is not useful

**Useful after a P2V in Vmware

Click “Start,” then “Control Panel.”

Double-click the “Network Connections” icon. Right-click any one of the Local Area Connection (LAN) icons in the Network Connections window.

Select “Properties” in the menu that pops up. Locate the “HP Network Configuration Utility” option in the list of services and left-click it.

Click the “Uninstall” button that pops up in the Properties window. The HP Teaming Software will begin to remove itself from your system.

Click “Yes” when prompted to restart your computer after the uninstallation has completed.

To reset a domain controller recovery console password.

http://www.pogostick.net/~pnh/ntpasswd/