none
Question about VPN Configuration in Azure. RRS feed

  • 질문

  • While I have been setting VPN configuration from this url, I have a some question.

    A. Ref.URL : http://www.windowsazure.com/en-us/manage/services/networking/active-directory-forest/

    1. following this url, Step 4 is not found.
    What need task for Step 4?

    2. Step 6 show script, do I this script deploy to Azure use by PowerShell ?
    If this script is not provisioning, VM cann't join domain on Boot step?

    ----------------------

    B. Ref.URL : http://www.windowsazure.com/en-us/manage/services/networking/cross-premises-connectivity/

    3. what is this Address space information ?
    is this address space means private address in on-premises ?
    or it means virtual ip address ?

    4. is this Subnets means client ip address in on-premises that is join vpn?
    or is this have a the other means ?

    5. I have been set DNS to vm in azure virtual machine And i can write DNS information use this information ? or need the other DNS information ?

    6. finally, if i finish VPN configuration , how can i checked it?
    if client on on-premises can access this VM in azure, that is check it?

    Regards,

    2012년 9월 14일 금요일 오전 8:42

답변

  • Hello, MahoMay.

    1. I think this is a documentation miss. I'll spread this problem to MSFT forum. :-)

    2. Yes. That script can be used with your local PowerShell console to deploy new virtual machine as member of specified AD controller. But without that PowerShell script, you can create your pre-configured VM images. If you want to create pre-configured image, consider these steps.

      • Create a virtual machine then install and configure your server operating system.
      • Create a sysprep answer file to automate initialize process. http://technet.microsoft.com/en-us/library/hh824849.aspx
      • Generalize and seal the virtual machine with sysprep.
      • Detach VHD file and upload to Azure with CSUPLOAD.

    Alternatively, you can use Windows AIK and WIM2VHD tool. WIM2VHD tool provides direct translation from WIM to VHD.

    3. The term "Address space" means its own virtual area, not physical/on-premise area. Virtual network is perfectly isolated from your existing virtual network, so you don't need to consider collision between on-premise network and virtual network.

    4. Subnet is also secluded from existing network. Site-to-site VPN join will not affect existing subnet configuration.

    5. Basically, you can manage your own DNS server in connected virtual network. But if you need spread DNS configuration for public web service, there are some sort of limitations due to NAT-like environment.

    6. If you want to configure site-to-site VPN, Azure Virtual Network will provide real-time dashboard to administrator, but it is currently available for some known high level routers. Alternatively, you can use OpenVPN or built-in Windows or linux VPN host service.

    Thank you.

    Windows Azure MVP, Nam Jung Hyun


    남정현 (rkttu@rkttu.com) - Windows Azure Cafe SYSOP - http://cafe.naver.com/wazure | DEVPIA C# Forum SYSOP - http://www.devpia.com/CSharp.MAEUL | ContentStory (http://www.ineat.co.kr)

    • 답변으로 표시됨 MahoMay 2012년 9월 18일 화요일 오전 5:29
    2012년 9월 14일 금요일 오후 4:13
    중재자

모든 응답

  • Hello, MahoMay.

    1. I think this is a documentation miss. I'll spread this problem to MSFT forum. :-)

    2. Yes. That script can be used with your local PowerShell console to deploy new virtual machine as member of specified AD controller. But without that PowerShell script, you can create your pre-configured VM images. If you want to create pre-configured image, consider these steps.

      • Create a virtual machine then install and configure your server operating system.
      • Create a sysprep answer file to automate initialize process. http://technet.microsoft.com/en-us/library/hh824849.aspx
      • Generalize and seal the virtual machine with sysprep.
      • Detach VHD file and upload to Azure with CSUPLOAD.

    Alternatively, you can use Windows AIK and WIM2VHD tool. WIM2VHD tool provides direct translation from WIM to VHD.

    3. The term "Address space" means its own virtual area, not physical/on-premise area. Virtual network is perfectly isolated from your existing virtual network, so you don't need to consider collision between on-premise network and virtual network.

    4. Subnet is also secluded from existing network. Site-to-site VPN join will not affect existing subnet configuration.

    5. Basically, you can manage your own DNS server in connected virtual network. But if you need spread DNS configuration for public web service, there are some sort of limitations due to NAT-like environment.

    6. If you want to configure site-to-site VPN, Azure Virtual Network will provide real-time dashboard to administrator, but it is currently available for some known high level routers. Alternatively, you can use OpenVPN or built-in Windows or linux VPN host service.

    Thank you.

    Windows Azure MVP, Nam Jung Hyun


    남정현 (rkttu@rkttu.com) - Windows Azure Cafe SYSOP - http://cafe.naver.com/wazure | DEVPIA C# Forum SYSOP - http://www.devpia.com/CSharp.MAEUL | ContentStory (http://www.ineat.co.kr)

    • 답변으로 표시됨 MahoMay 2012년 9월 18일 화요일 오전 5:29
    2012년 9월 14일 금요일 오후 4:13
    중재자
  • Dear Nam,

    Thanks for your answer,

    I will retry this situation.

    I think, i will deploy script use powshell, because i must use os image from gallery.

    if i have get a more issue, i will re-posting to forum.

    Regards,

    2012년 9월 18일 화요일 오전 5:38