How Route between two different virtual networks in Hyper-V

When new internal network is created from “Virtual Network Manager”, new virtual “Local Area Connection X” is automatically created under “Control Panel > Network Connections”. We can use RRAS (routing and remote access) to route between virtual “Local Area Connection”.

1. Open Hyper-V console
2. Click on “Virtual Network Manager” under “Actions” Pane
3. Enter Name, choose “Internal”, click “Add”, click “OK”
4. You will noticed that new Local Area Connection is created under “Control Panel > Network Connections”
5. Right click on the newly created Local Area Connection, choose properties.
6. On TCP/IPv4 screen, enter IP: 10.1.0.1 , Subnet: 255.255.255.0 and no gateway. ( Repeat step 2 to 6 if you would like to create multiple networks )

7. Open “Routing and Remote Access” console. ( Server Manager > Network Policy and Access > Routing and Remote Access)

8. Right click on “Routing and Remote Access” and choose “Configure and Enable Routing and Remote Access”

9. Choose “Custom Configuration”

10. Choose “NAT” and “LAN routing”, click Next
    NAT allows your VMs to access the internet without exposing them.
    LAN routing allows you route between Local Area Connections

11. Click Finish and Start the service.

12. Browse to “NAT” under IPv4, Right click and choose “New Interface”, choose the interface that you use to connect to the internet.

13. Choose “Public interface connected to the internet”, check “Enable NAT on this interface”, click OK

Now use 10.1.0.1 as the gateway on Hyper-V guest VM and you will be able to access the internet and to other subnets.
SCREENSHOTS

VSS Snapshot warning. File %BeBootDrive%\bootmgr is not present on the snapshot.

Exclude the ASR writer from the list of approved writers

ASR writer id is '{BE000CBE-11FE-4426-9C58-531AA6355FC4}'.

1. Go to: Start  --> Run, key in regedt32, press Enter.
2. Then go to the HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec for Windows Servers \Engine\Shadow Copy Components\
3. Then create a new Additional Not Authorized Writers key.
4. Then, in the Additional Not Authorized Writers key, create a new String value under that key named ASR, with a value of {BE000CBE-11FE-4426-9C58-531AA6355FC4} Completing these steps causes Backup Exec to ignore the ASR components.

Exchange Server 2010 & Event ID 106

There is nothing to worry about this error. Microsoft published article KB982679 - Event ID 106 is logged when you start the RPC Client Access service on Exchange Server 2010.
This problem occurs because the performance counters of the RPC Client Access service are not installed when you install only the Mailbox role on an Exchange Server 2010 server. However, this does not affect the functionality of the Exchange Server 2010 server.
It’s not so pretty to see many errors in Event Viewer after restarting Microsoft Exchange RPC Client Access service. Let’s try to manually add RPC Client Access performance counters.
Manually add RPC Client Access performance counters

• Start Exchange Management Shell
• Add-PSSnapin Microsoft.Exchange.Management.PowerShell.Setup
• New-PerfCounters -DefinitionFileName "C:\Program Files\Microsoft\Exchange Server\V14\Setup\Perf\RpcClientAccessPerformanceCounters.xml"
  
  
• Restart server or Microsoft Exchange RPC Client Access service.

Diable USB stroage with allow mouse and keyboard

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\USBSTOR --> Start --> 4

Add Full Access Right to Exchange 2010 user's mailbox

Get-MailboxDatabase -identity “Mailbox Database” | Add-ADPermission -user “Domain Admins” -AccessRights GenericAll

Rebuilding Foreign Disk manually in LSI RAID

1. Download "MegaCli64" from LSI and store on c:\temp
2. Open Command Prompt
3. In command prompt, run "C:\temp\MegaCli64 -CfgForeign -Scan -a0"
4. If the result show "There are 1 foreign configuration(s) on controller 0", go to step 5
5. In Command prompt, run "C:\temp\MegaCli64 -CfgForeign -Clear -a0"

Change Remote Desktop Listening Port

1. Open Regedit
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp

2.Locate the port number

3. Change from 3389 to 6389

4. Access the server with special RDP port, e.g. 192.168.0.11:6389