This type of RAID array requires a partition using a GUID (Globally Unique Identifier) Partition Table (GPT) to work properly for Windows in UEFI BIOS mode. Windows Setup, however, does not support making a GPT partition in the standard setup dialogue. Diskpart from the Command Prompt must be used to create a GPT partition to allow setup to see the RAID partition and continue setup.
Start the install, and load the PERC H310 drivers via the OS “Load Diver” function. After the driver is loaded the RAID volume will appear in the install to device list (Figure 1).
Press Shift+F10 to bring up a Command Prompt window.
Type DISKPART and press Enter to enter the DISKPART tool. Enter the commands in the following steps as shown in bold and press enter.
DETAIL DISK – This shows a list of volumes seen by the system. Make note of the Volume number for the RAID array.
SELECT DISK=X – X will be the Volume number of the RAID shown in the detail disk report.
CLEAN – Clears the partition information.
CONVERT GPT – Sets the partition to GPT.
EXIT – Exits DISKPART.
Exit the Command Prompt window.
The full RAID volume should show in the device list.
Complete the remainder of the installation process normally. The RAID volume should show as “Windows Boot Manager” in UEFI.
If this was completed correctly, the system should boot normally in UEFI BIOS mode, and allow Windows to install.
By default IIS will listen for connections on port 80 for any IP
bound to the server. This happens even if there are no host headers or
bindings set for a specific IP. This can be a problem when trying to run
multiple web servers on port 80.
To set IIS to listen on specific IPs follow the instructions below.
Windows Server 2003/IIS 6:
1. This requires the Server 2003 support tools. If this is not already installed it can be downloaded here.
2. Once installed open a command prompt and navigate to the support
tools installation folder (default is C:\Program Files\Support Tools). cd C:\Program Files\Support Tools
3. Stop http. net stop http /y
4. Use this command to display the current list of IPs: httpcfg query iplisten
5. By default it will listen on all IPs (0.0.0.0) so we can remove this. httpcfg delete iplisten -i 0.0.0.0
6. Specify the IP(s) that IIS should listen on. Make sure to update
127.0.0.1 to the desired IP and run the command for each IP IIS should
listen on. httpcfg set iplisten -i 127.0.0.1
7. Start http and test out your sites. net start http
Windows Server 2008/IIS 7:
1. Open a command prompt and type “netsh”. netsh
2. Type “http”. http
3. Enter the following command to display the current list of IPs to
listen on. Note if no IPs are displayed like in the below image, IIS
will listen on all IPs (default). show iplisten
4. Use the command below to set IIS to listen on a specific IP. Make
sure to replace 127.0.0.1 with the correct IP and run the command again
for any additional addresses. add iplisten ipaddress=127.0.0.1
5. In case you need to delete an IP from this list, use the following command. delete iplisten ipaddress=127.0.0.1
“I have two sites (siteV1.mysite.com and sitev2.mysite.com). They
listen on the same IP address and port. We generated a certificate for
siteV1.mysite.com and SSL is working properly. The problem is that some
of our customers use siteV2.mysite.com and they are getting certificate
errors. What’s the problem?”
Here is the issue:
There are three pieces of data to uniquely identify an IIS site:
The IP address
The Host name which HTTP 1.1 clients send as an HTTP request header.
This IP:Port:Hostname triplet is called a binding. The binding “192.168.1.192:80:myserver” for example represents a site that listens on IP address 192.168.1.192, port 80, host-header myserver.
The very first things IIS (HTTP.SYS to be more precise) does when a
request comes in is to read the site’s configuration. Connection limits
and timeouts are examples of site configuration. The site binding is
used to find the right site configuration. The SSL certificate seems to
be another great example of site configuration – the SSL certificate is
needed to decrypt the encrypted SSL data coming from the client.
And the IIS User Interface certainly makes it appear as if the SSL
certificate would be site configuration, too – doesn’t it? In reality
however you can’t bind a SSL certificate to a site. The IIS UI is
fooling you. But why?
It’s a chicken and egg problem: The host name is encrypted in the SSL
blob that the client sends. Because the host name is part of the
binding IIS needs the host name to lookup the right certificate. Without
the host name IIS can’t lookup the right site because the binding is
incomplete. Without the certificate IIS can’t decrypt the SSL blob that
contains the host name. Game over – we are turning in circles.
What IIS does under the covers is to ignore the host name. IIS binds
the certificate to IP:Port and warns you when you try to bind a
certificate to the same IP:Port combo with different host names.
But there is a way if you need two different sites on the same
IP:Port. You can accomplish this by getting a certificate that contains
both common names, i.e. sitev1.mysite.com and sitev2.mysitem.com. Cert
Authorities usually allow more than one so called “common names” in a
certificate. By binding the certificate to one of the two sites you
won’t not get certificate errors anymore. The client is happy if one of
the names in the certificate matches.
But there is another caveat: you can’t use the IIS7 User Interface to
add a host header to an SSL site binding. You have to use command-line
tools, do it programmatically or edit applicationhost.config directly.
Here is an example and a link how you can it via command-line:
appcmd set site /site.name:”MySite V2″ /+bindings.[protocol=’https’,bindingInformation=’*:443:sitev2.mysite.com’]
And last but not least: with IIS7 you can use the following command
to figure out what certificate is bound to a particular IP:Port
combination: netsh http show sslcert
This command will show the IP:Port binding but also some other SSL settings.
(2)SmokePing的特点 SmokePing keeps track of your network latency: Best of breed latency visualisation.（最佳图形展示功能，延时丢包等可以很直观的可视化展现） Interactive graph explorer.（交互式浏览器图表） Wide range of latency measurement plugins.（丰富的网络状况测量插件） Master/Slave System for distributed measurement.（支持主从的分布式部署模式） Highly configurable alerting system.（自定义报警功能） Live Latency Charts with the most ‘interesting’ graphs.（漂亮、免费、开源） Free and OpenSource Software written in Perl written by Tobi Oetiker, the creator of MRTG and RRDtool