When starting a business or new website project the first step is always picking a relevant yet easy to remember domain name that is easy also good for marketing. One thing that some do not consider is how the search engines delegate certain domain extensions or Top Level Domains(TLDs).
Everyone knows .com, .net, .org and .edu have been around since the start and are widely used, unfortunately it is also hard to find a good domain that is not being help by domain campers, investors or spammers. In order to deal with this the registry has released a number of domains over the years as well as country specific TLDs. However, many of these countries have opened their own TLD for public use, whether for profit or publicity there is quite the list. Some such as .ws and.co have become very popular leaving search giants in the position to treat them like standard TLDs. Here is a list of domains treated like standard TLDs rather than country or regional specific TLDs for SEO purposes by google.
Country domains treated as standard TLDs
Regional domains treated as standard TLDs
It is important to choose a domain treated as a standard domain or all searches will be locked to the country specific search results.
Private memory limit uses your system RAM, where the Virtual Memory limit will use Disk drive space. In most cases it is best to only set a private memory limit to prevent degradation to system performance if an application starts to use excessive amount of memory. Many .Net application will use large amount of virtual memory(Drive Space).
No method via ECP is available for this but a simple powershell command will do the trick:
Set-Mailbox -Identity "User" -DeliverToMailboxAndForward $true -ForwardingSMTPAddress email@example.com
Limiting the use of IPs by each Guest OS is an important step in securing your network from accidental or intentional abuse of IP resources.
You can limit IPs in Hyper-V 2012 using ACL rules much like any router or managed switch would provide via ACLs.
No Gui is currently available to manage ACLs so you will need to open Windows Powershell if you are in GUI mode. Lets assume you have VM named "Poject1" and you would like to limit this client/gues VM so they can only use 10.0.0.75 as an IP address.
Here are the commands:
Add-VMNetworkAdapterAcl -VMName Project1 -LocalIPAddress 10.0.0.75 -Direction Both -Action Allow
Add-VMNetworkAdapterAcl -VMName Project1 -LocalIPAddress any -Direction Both -Action Deny
That is it, your done.
Now you can check the rules with:
Get-VMNetworkAdapterAcl -VMName Project1
or you can remove the rules using:
Remove-VMNetworkAdapterAcl -VMName Project1 -LocalIPAddress 10.0.0.75 -Direction Both -Action Allow
Remove-VMNetworkAdapterAcl -VMName Project1 -LocalIPAddress any -Direction Both -Action Deny
This error occurs when the installer cannot find the install image, this commonly happens when you install f6 drivers but then forget to put the windows install disk back in the drive.
- Verify that you have placed the install disk back in the same drive you had it in to start the install process
- Verify you are using the correct drivers (windows version, 32/64bit)
Problem should be resolved at this point.