Arquivo

Archive for julho \28\UTC 2009

Adicionando SSL FTP Adding a seu website : Editando os arquivos de configuracao do IIS 7

 
Nota: para editar o arquivo applicationHost.config voce precisa ter direitos administrativos
 
1. Recupere o Hash do Certificado SSL:
  1. Em Server Certificates feature, duplo-clique no certificado. 
  2. Clique na aba Details.
  3. Navegue pelos campos ate localizar o valor Thumbprint.
  4. Selecione o valor Thumbprint. Algo como:
    "f0 1e d2 3c b4 5a 96 78 87 69 a5 4b c3 2d e1 0f f0 1e d2 3c"
  5. Copie o hex data para a area de transferencia ( CTRL-C ) e cole no notepad
 
2. Adicione FTP  ao Web Site

  1. Usando o Notepad, abra o arquivo applicationHost.config, localizado em  %SystemRoot%System32inetsrvconfig .
  2. Localize a secao do website que deseja incluir a funcionalidade de FTP. Por exemplo:
    <site name="Default Web Site" id="1">
        <application path="/">
            <virtualDirectory path="/" physicalPath="%SystemDrive%inetpubwwwroot" />
        </application>
        <bindings>
            <binding protocol="http" bindingInformation="*:80:" />
        </bindings>
    </site>
  3. Crie um novo elemento para o Binding, contendo o atributo "ftp", e o valor 21 para o atributo bindingInformation. Como no exemplo abaixo:
    <site name="Default Web Site" id="1">
        <application path="/">
            <virtualDirectory path="/" physicalPath="%SystemDrive%inetpubwwwroot" />
        </application>
        <bindings>
            <binding protocol="http" bindingInformation="*:80:" />
            <binding protocol="ftp" bindingInformation="*:21:" />
        </bindings>
    </site>
  4. Adicione uma secao <ftpServer> que contera’ as configuracoes de autenticacao e SSL. Nota: As configuracoes para os sitres FTP sao configuradas no nivel de SITE. As configuracoes de autenticacao, podem ser configuradas a nivel de URL.
    <ftpServer>
        <security>
            <authentication>
                <anonymousAuthentication enabled="false" userName="IUSR" />
                <basicAuthentication enabled="true" />
            </authentication>
            <ssl serverCertHash="" controlChannelPolicy="SslRequire" dataChannelPolicy="SslRequire" />
        </security>
    </ftpServer>
  5. Copie e Cole o thumbprint data para o atributo serverCertHash do elemento SSL. Remova todos os espacos do thumbprint. (Nota: Se voce nao converter o codigo HEX para maiusculo, ele nao vai ser mostrado no IIS Manager, depois.) . Seu codigo devera agora ser parecido com o codigo abaixo:
    <site name="Default Web Site" id="1">
        <application path="/">
            <virtualDirectory path="/" physicalPath="%SystemDrive%inetpubwwwroot" />
        </application>
        <bindings>
            <binding protocol="http" bindingInformation="*:80:" />
            <binding protocol="ftp" bindingInformation="*:21:" />
        </bindings>
        <ftpServer>
            <security>
                <authentication>
                    <anonymousAuthentication enabled="false" />
                    <basicAuthentication enabled="true" />
                </authentication>
            </security>
            <ssl serverCertHash="F01ED23CB45A96788769A54BC32DE10FF01ED23C" controlChannelPolicy="SslRequire" dataChannelPolicy="SslRequire" />
        </ftpServer>
    </site>
  6. Navegue para o fim do arquivo applicationHost.config e adicione a secao Location para o seu website, que contera’ as configuracoes de autorizacao. Nota: Assim como no exemplo abaixo, as configuracoers de autorizacao para o ftp sao configuradas por URL.
    <location path="Default Web Site">
        <system.ftpServer>
            <security>
                <authorization>
                    <add accessType="Allow" users="administrator" permissions="Read, Write" />
                </authorization>
            </security>
        </system.ftpServer>
    </location>
  7. Salve o arquivo applicationHost.config.

 

Categorias:IIS 7

Windows 7 e Windows 2008 R2 RTM : 6 de agosto

 
O Windows 7 e o Windows 2008 R2 ja estao em RTM. Mas quando voce tera acesso a versao RTM, depende de quem voce e’…..
 
Parceiros e OEM
  • ISV (Independent software vendor) e IHV (Independent hardware vendor) Partners vao poder fazer o download do Windows 7 RTM usando o Microsoft Connect ou MSDN em 6 de Agosto
  • Microsoft Partner Program Gold/Certified Members em 16 de Agosto
  • Microsoft Action Pack Subscribers em 23 de Agosto

Business Customers

  • Volume License (VL) customer com Software Assurance (SA) em 7 de Agosto
  • Volume License customers sem SA license vao poder comprar o  Windows 7 pelo  Volume Licensing em 1º de  Setembro

 IT Professionals e Developers

  • IT Professionals com TechNet Subscriptions em 6 de Agosto

Consumidores

  • Nas lojas e em novos PC’s a partir de 22 de Outubro

Nota: Postei somente as datas para as versoes em ingles. As demais versoes, tem datas

 
 
Categorias:Microsoft

Exportando / Importando maquinas virtuais usando o Hyper-V Manager

A maneira correta e’ usar o Hyper-V manager para exportar as maquinas virtuais e entao, importa-las novamente.

No menu Acao, selecione a opcao Exportar. Indique o caminho ( por exemplo um disco externo, USB ).

Esta opcao faz com que o Hyper-V copie todas as informacoes e dados necessarios para que a maquina virtual possa ser importada com seguranca em outro servidor hyper-v. Dentro desta pasta que voce especificou tera o seguinte conteudo:

  • Virtual Machines folder
    • contem um arquivo  .exp. Por  exemplo : "6D59FE56-6D20-4129-9BF3-2457DDB58A9A.exp".  Este arquivo contem a configuracao da maquina virtual. 
    • Tambem tera uma outra sub pasta com o nome do ID da maquina virtual. Se a maquina virtual estava em " saved state"  ela vai conter dois aquivos ( .vsv e .bin), senao vai estar em branco.
  • Virtual Hard Disks folder
    • Esta pastas contem a copia de cada VHD associado a maquina virtual.
  • Snapshots folder
    • Esta pasta contem:
      • Um .exp file para cada snapshot que a maquina virtual tiver. 
      • Uma pastas com o nome do snapshot ID que contem os arquivos "saved state" .
      • Uma pasta que ira conter os discos difereciais usados por todos os snapshots da maquina virtual (.avhd).
  • config.xml
  •  

    Se voce preferir tambem pode usar script :

    /* Copyright – Taylor Brown   Hyper-V Test Team  */

    param
    (
        [
    string]$MasterVM = $(Throw "MasterVM required"),
        [
    string]$Path = $(Throw "Path required"),
        [
    string]$NewName = "VMCopy",
        [
    string]$HyperVHost = "localhost"
    )

    function ProcessWMIJob
    {
        param
        (
            [
    System.Management.ManagementBaseObject]$Result
        )

        if ($Result.ReturnValue -eq 4096)
        {
            $Job = [WMI]$Result.Job

            while ($Job.JobState -eq 4)
            {
                Write-Progress -Id 2 -ParentId 1 $Job.Caption -Status "Executing" -PercentComplete $Job.PercentComplete
                Start-Sleep 1
                $Job.PSBase.Get()
            }
            if ($Job.JobState -ne 7)
            {
                Write-Error $Job.ErrorDescription
                Throw $Job.ErrorDescription
            }
        }
        elseif ($Result.ReturnValue -ne 0)
        {
            Throw $Result.ReturnValue
        }
        Write-Progress $Job.Caption -Status "Completed" -PercentComplete 100 -Id 2 -ParentId 1
    }

    #Main Script Body
    $VMManagementService = Get-WmiObject -Namespace rootvirtualization -Class Msvm_VirtualSystemManagementService -ComputerName $HyperVHost
    $SourceVm = Get-WmiObject -Namespace rootvirtualization -Query "Select * From Msvm_ComputerSystem Where ElementName=’$MasterVM’" -ComputerName $HyperVHost
    $a = 0


    while ($a -lt 10) {
        write-progress -Id 1 "Cloning Vm’s" -Status "Executing" -percentcomplete (($a / 10)*100)
        $tempVMName = "$NewName – $a"
        $VMSettingData = Get-WmiObject -Namespace rootvirtualization -Query "Associators of {$SourceVm} Where ResultClass=Msvm_VirtualSystemSettingData AssocClass=Msvm_SettingsDefineState" -ComputerName $HyperVHost
        $VMSettingData.ElementName = $tempVMName

        $Result = $VMManagementService.ModifyVirtualSystem($SourceVm, $VMSettingData.PSBase.GetText(1))
        ProcessWMIJob $Result

        $Result = $VMManagementService.ExportVirtualSystem($SourceVm, $TRUE, "$Path")
        ProcessWMIJob $Result

        $Result = $VMManagementService.ImportVirtualSystem("$Path$tempVMName", $TRUE)
        ProcessWMIJob $Result

        $a ++
    }


    write-progress -Id 1 -Completed $TRUE -Activity "Cloning Vm’s"
    $VMSettingData = Get-WmiObject -Namespace rootvirtualization -Query "Associators of {$SourceVm} Where ResultClass=Msvm_VirtualSystemSettingData AssocClass=Msvm_SettingsDefineState" -ComputerName $HyperVHost
    $VMSettingData.ElementName = $MasterVM

    $Result = $VMManagementService.ModifyVirtualSystem($SourceVm, $VMSettingData.PSBase.GetText(1))
    ProcessWMIJob $Result

     

    SCVMM R2 : Novo tipo de migracao : Quick Storage Migration

     

    QSM Is One of Many Migration Technologies Supported in Virtual Machine Manager’s Portfolio

    VM Migration Type

    Platforms available on

    Technology used for transfer

    Expected downtime for VM

    Live Migration

    • Hyper-V
      (2008 R2)
    • ESX 3.0, 3.5
    • Windows Server 2008 Failover Cluster
    • Hyper-V
    • vMotion for ESX

    None

    • No service interruption while virtual machine is moved

    Quick Migration

    • Hyper-V
    • Windows Server 2008 Failover Cluster
    • Hyper-V

    Under 1 minute in most cases

    • VM is put into save-state while it is moved from one cluster node to another using the cluster failover mechanism

    SAN Migration

    • Virtual Server
    • Hyper-V
    • Windows Server 2008 Hyper-V and Virtual Disk Service (VDS) Hardware Providers
    • N-Port Identification Virtualization (NPIV) on Emulex and QLogic Fibre Channel HBAs
    • iSCSI on EMC, HP, Hitachi, NetApp, EquiLogic arrays

    Under 1 minute in most cases

    • VM is put into save-state while it is moved from one virtual machine host to another using unmasking and masking operations at the SAN level

    Network based migration

    (aka LAN migration)

    • Virtual Server
    • Hyper-V
    • ESX
    • BITS for Virtual Server and Hyper-V
    • sFTP for ESX

    Minutes to hours (W2K8, W2K3 hosts)

    • VM needs to be stopped or in saved state for the entire duration of transfer

    Under 1 minute in most cases (W2K8 R2)

    • VM can remain running for the almost entire duration of the transfer of its virtual disks from once storage location to another
    • VM is put into save-state for a brief interval to migrate its memory state and associated differencing disks.

    Storage Migration Type

    Platforms available on

    Technology used for transfer

    Expected downtime

    Storage vMotion

    • ESX 3.5
    • Storage vMotion

    None

    • No perceived service interruption while the virtual disks associated with a virtual machine are moved from storage location to another

    Quick Storage Migration

    • Hyper-V
      (2008 R2)
    • BITS and Hyper-V

    Under 1 minute in most cases (W2K8 R2)

    • VM can remain running for the almost the entire duration of the transfer of its virtual disks from once storage location to another
    • VM is put into save-state for a brief interval to migrate its memory state and associated differencing disks.

     

     

    How QSM Compares To VMware Storage VMotion

     

    VMM 2008 R2 + Windows Server 2008 R2 Hyper-V

    VMware (vCenter 2.5 + ESX 3.5)

    Migration of virtual machines across two hosts with independent storage

    Supported

    Not Supported

    Migration of virtual machines with snapshots

    Supported

    Not Supported

    Migration of Virtual machine with Virtual Disks

    Supported

    Supported (persistent mode)

    Requires sufficient resources to support two instances of the virtual machines running concurrently

    Not Required

    Required

    Additional Licensed Required

    None

    VMotion License

    Number of concurrent storage Migrations allowed

    10

    4

    Storage Migrations supported in the Administrator Console

    Yes (QSM and Storage vMotion)

    No

    Storage Migrations supported in the CLI

    Yes (QSM and Storage vMotion)

    Yes

    Protocol agnostic

    Yes

    Yes

    Support for migrations of VMs and storage between hosts with different processors versions (same manufacturer)

    Yes (use Hyper-V R2 Processor Compatibility Mode to increase the number of compatible hosts )

    Not Applicable