iis 10 달라진 점

출처 : http://www.iis.net/learn/get-started/whats-new-in-iis-10/wildcard-host-header-support

Wildcard Host Header Support

By Andrew Westgarth

July 1, 2015

Level 200 : Novice

COMPATIBILITY

Version Notes
IIS 10.0 Wildcard Host Header Support was introduced in IIS 10.0
IIS 8.5 Wildcard Host Header was not supported in IIS 8.5
IIS 8.0 Wildcard Host Header was not supported in IIS 8.0.
IIS 7.5 Wildcard Host Header was not supported in IIS 7.5.
IIS 7.0 Wildcard Host Header was not supported in IIS 7.0.

CONTENTS

Problem

For quite some time, customers have requested that we support Wildcard Host Headers in IIS. IIS 10 now supports Wildcard Host Headers.

Solution

Wildcard Host Headers enable admins to setup a webserver for a domain, e.g. contoso.com and then have the webserver serve requests for any subdomain. For example the following would all be valid hosts:

  • intranet.contoso.com
  • private.contoso.com
  • blogs.contoso.com

Step by Step Instructions

ADDING A NEW SITE WITH A WILDCARD HOST HEADER

To add a new site with a Wildcard Host Header in IIS you need to follow these simple steps:

  1. Open Internet Information Services Manager on the server your site is hosted on:
      1. If you are using Windows Server Technical Preview:
        1. On the taskbar, click Server Manager, click Tools, and then click Internet Information Services (IIS) Manager.
      2. If you are using Windows Technical Preview
        1. Hold down the Windows Key, press the letter X and then click Control Panel.
        2. Click Administrative Tools, and then double-click Internet Information Services (IIS) Manager.
      3. Select the server on which you wish to create your site, from the list in connections.
      4. Click the “Add Website..” option in the Actions PaneNew Site in IIS Manager
  2. Enter configuration for your site, in the text box for Host name enter your Wildcard Host Header e.g. *.contoso.com and click OK.New Site Details
  3. Your new site has been configured with a Wildcard Host Header
  4. ADDING A WILDCARD HOST HEADER TO AN EXISTING SITE

    To configure and existing site to make use of a Wildcard Host Header in IIS you need to follow these simple steps:

    1. Open Internet Information Services Manager on the server your site is hosted on:
        1. If you are using Windows Server Technical Preview:
          1. On the taskbar, click Server Manager, click Tools, and then click Internet Information Services (IIS) Manager.
        2. If you are using Windows Technical Preview
          1. Hold down the Windows Key, press the letter X and then click Control Panel.
          2. Click Administrative Tools, and then double-click Internet Information Services (IIS) Manager.
        3. Select the server on which your site is deployed, from the list in connections.
        4. Select the website (.e.g. Default Web Site) you wish to configure from the list of sites.
        5. In the Actions pane select Bindings:Edit existing site in IIS Manager
    2. Select the binding you would like to edit (e.g. http) and click Edit…Site Bindings
    3. In the text box for Host name enter your Wildcard Host Header e.g. *.contoso.com and click OKAdd/Edit Site Binding
    4. Now you can see the Wildcard Host Header value in the list of bindings:Updated Site Bindings
    5. Click close to return to IIS Manager.
    6. TESTING A WILDCARD HOST HEADER

      Once you have configured a Wildcard Host Header you will need to configure DNS for the domain and then you can test traffic to your website. In the below screenshots we have used three different subdomains to route to the site which we configured with a Wildcard Host Header (*.contoso.com). The demonstration asp.net application we deployed to this site renders the host name requested on the home page.

      intranet.contoso.comprivate.contoso.comblogs.contoso.com

      Issues

      Summary

      IIS 10.0 has added support for Wildcard Host Headers in bindings.

Telerik Ad

번역 보기

 

vmware의 가상머신에서 hyper-v 사용하기

VMWare 설정에서 Processors 항목에서

Virtualize Intel VT-x/EPT or AMD-V/RVI 항목이 체크되어 있는 지 확인(Default는 언체크) 체크 해준다.

채크 후 바로 VM을 실행하지 말고

해당 VMWare 가상머신이 설치된 폴더를 열어서

가상머신명.vmx 파일을 에디터로(ex) notepad) 등으로 열어서

hypervisor.cpuid.v0 = “FALSE” 항목을 추가한다.(기존에 있다면 값이 false 인지 확인)

 

그 후 다시 VMWare 실행 하면 정상적으로 hyper-v가 동작함.

32비트 운영체제에서 128G 램 사용하기

원문 출처 : http://wj32.org/wp/2013/10/25/pae-patch-updated-for-windows-8-1/

 

직접 다운로드 : PatchPae2

 

이 파일의 압축을 해제하여 나오는 파일들을 가지고 이용함.

  1. 다운받은 툴의 PatchPae2.exe를 Windows/System32 폴더에 복사를 한다.
  2. cmd를 관리자 권한으로 실행한다.
  3. 128 GB 까지 메모리를 인식할 수 있도록 커널을 패치한다.
    3.1 윈도 8/8.1 : c:\Windows\System32>PatchPae2.exe -type kernel -o ntoskrnx.exe ntoskrnl.exe
    3.2 윈도 Vista/7 : c:\Windows\System32>PatchPae2.exe -type kernel -o ntkrnlpx.exe ntkrnlpa.exe
  4. c:\Windows\System32>PatchPae2.exe -type loader -o winloadp.exe winload.exe
    – 로더의 사인 검증 로직을 제거한다.
  5. bcdedit /copy {current} /d “Windows (PAE Patched)”
    – 부트 항목을 추가한다.
    – 이 명령을 실행하면, {8bfc9ccb-7075-11e4-8f2b-9980ef68eed0}와 같은 UUID를 확인할 수 있다.
  6. 패치된 커널의 추가한 부트 항목으로 로딩하기 위해서 아래의 명령을 실행한다.
    6.1 윈도 8/8.1 : c:\Windows\System32>bcdedit /set {8bfc9ccb-7075-11e4-8f2b-9980ef68eed0} kernel ntoskrnx.exe
    6.2 윈도 Vista/7 : c:\Windows\System32>bcdedit /set {8bfc9ccb-7075-11e4-8f2b-9980ef68eed0} kernel ntkrnlpx.exe
  7. c:\Windows\System32>bcdedit /set {8bfc9ccb-7075-11e4-8f2b-9980ef68eed0} path \Windows\system32\winloadp.exe
    – 패치된 로더로 변경한다.
  8. c:\Windows\System32>bcdedit /set {8bfc9ccb-7075-11e4-8f2b-9980ef68eed0} nointegritychecks 1
    – 로더 검증 로직을 제거한다.

 

이후 msconfig 또는 고급 시스템 설정에서 부팅 설정을 하면 됨.