{"id":6843,"date":"2016-08-02T08:45:06","date_gmt":"2016-08-02T08:45:06","guid":{"rendered":"http:\/\/www.highclouder.ninja\/?p=6843"},"modified":"2024-05-21T14:49:54","modified_gmt":"2024-05-21T14:49:54","slug":"exchange-2016-test-farm-azure","status":"publish","type":"post","link":"https:\/\/www.highclouder.com\/?p=6843","title":{"rendered":"Exchange 2016 Test Farm in Azure"},"content":{"rendered":"

If you like me and always want to be at the edge of the technology, you always play with the new version of products. Sometimes having a platform (servers, storage, switches, etc.) to run a product on it is a bit a challenge :). Let’s see how to build VERY simple (1 Domain Controller and 1 Exchange 2016 server) Exchange 2016 environment in Azure Cloud:<\/p>\n

As I already said, this configuration consists of a single Exchange server and a Windows Server Active Directory (AD) domain controller in a subnet of an Azure virtual network, which provides a basis and common starting point from which we can demonstrate Exchange 2016 and develop Exchange Server applications. This configuration is only for internal email and application testing on the Exchange server. No external email flow is configured<\/strong>.<\/p>\n

There are three major phases to setting up this test environment:<\/p>\n

    \n
  1. Set up the virtual network and domain controller (adVM).<\/li>\n
  2. Add the Exchange 2016 server (exVM).<\/li>\n
  3. Configure Exchange 2016.<\/li>\n<\/ol>\n

    Note<\/strong>:\u00a0Because Exchange 2016 makes changes to the schema in Windows Server AD, this configuration cannot use Azure Active Directory Domain Services.<\/em><\/p>\n

    Phase 1: Deploy the virtual network and a domain controller<\/strong><\/p>\n

    We can create a new Azure virtual network with a domain controller with Azure PowerShell. We can run the following PowerShell commands from a Windows PowerShell command prompt or in the PowerShell Integrated Script Environment (ISE).<\/p>\n

    First of all, let’s sign into our Azure account.<\/p>\n

    Login-AzureRMAccount\n<\/pre>\n
    Get our subscription name using the following command.<\/p>\n
    Get-AzureRMSubscription | Sort SubscriptionName | Select SubscriptionName<\/pre>\n
    Set our Azure subscription with the following commands. Set the $subscr<\/strong> variable by replacing everything within the quotes, including the < and > characters, with the correct name.<\/p>\n
    $subscr=\"\"\nGet-AzureRmSubscription -SubscriptionName $subscr | Select-AzureRmSubscription<\/pre>\n
    Next, we have to create a new resource group. To determine a unique resource group name, use this command to list our existing resource groups.<\/p>\n
    Get-AzureRMResourceGroup | Sort ResourceGroupName | Select ResourceGroupName<\/pre>\n
    Create our new resource group with these commands. Set the variables by replacing everything within the quotes, including the < and > characters, with the correct names.<\/p>\n
    $rgName=\"\"\n$locName=\"\"\nNew-AzureRMResourceGroup -Name $rgName -Location $locName<\/pre>\n
    Resource Manager-based virtual machines require a Resource Manager-based storage account. We must pick a globally unique name for our storage account that contains only lowercase letters and numbers. We can use this command to list the existing storage accounts.<\/p>\n
    Get-AzureRMStorageAccount | Sort StorageAccountName | Select StorageAccountName<\/pre>\n
    Create a new storage account for our new test environment with these commands.<\/p>\n
    $rgName=\"\"\n$locName=\"\"\n$saName=\"\"\nNew-AzureRMStorageAccount -Name $saName -ResourceGroupName $rgName -Type Standard_LRS -Location $locName<\/pre>\n
    Next, we create the EX2016Vnet Azure Virtual Network that will host the EX2016Subnet subnet and protect it with a network security group.<\/p>\n
    $rgName=\"\"\n$locName=\"\"\n$locShortName=\"\"\n$exSubnet=New-AzureRMVirtualNetworkSubnetConfig -Name EX2016Subnet -AddressPrefix 10.0.0.0\/24\nNew-AzureRMVirtualNetwork -Name EX2016Vnet -ResourceGroupName $rgName -Location $locName -AddressPrefix 10.0.0.0\/16 -Subnet $exSubnet -DNSServer 10.0.0.4\n$rule1 = New-AzureRMNetworkSecurityRuleConfig -Name \"RDPTraffic\" -Description \"Allow RDP to all VMs on the subnet\" -Access Allow -Protocol Tcp -Direction Inbound -Priority 100 -SourceAddressPrefix Internet -SourcePortRange * -DestinationAddressPrefix * -DestinationPortRange 3389\n$rule2 = New-AzureRMNetworkSecurityRuleConfig -Name \"ExchangeSecureWebTraffic\" -Description \"Allow HTTPS to the Exchange server\" -Access Allow -Protocol Tcp -Direction Inbound -Priority 101 -SourceAddressPrefix Internet -SourcePortRange * -DestinationAddressPrefix \"10.0.0.5\/32\" -DestinationPortRange 443\nNew-AzureRMNetworkSecurityGroup -Name EX2016Subnet -ResourceGroupName $rgName -Location $locShortName -SecurityRules $rule1, $rule2\n$vnet=Get-AzureRMVirtualNetwork -ResourceGroupName $rgName -Name EX2016Vnet\n$nsg=Get-AzureRMNetworkSecurityGroup -Name EX2016Subnet -ResourceGroupName $rgName\nSet-AzureRMVirtualNetworkSubnetConfig -VirtualNetwork $vnet -Name EX2016Subnet -AddressPrefix \"10.0.0.0\/24\" -NetworkSecurityGroup $nsg<\/pre>\n
    Next, we create the adVM virtual machine in Azure. adVM is a domain controller for the corp.contoso.com Windows Server AD domain and a DNS server for the virtual machines of the EX2016Vnet virtual network.
    \nFirst, fill in the name of your resource group, Azure location, and storage account name and run these commands at the Azure PowerShell command prompt on your local computer to create an Azure virtual machine for adVM.<\/p>\n
    $rgName=\"\"\n$locName=\"\"\n\n# Get the Azure storage account name\n$sa=Get-AzureRMStorageaccount | where {$_.ResourceGroupName -eq $rgName}\n$saName=$sa.StorageAccountName\n\n# Create an availability set for domain controller virtual machines\nNew-AzureRMAvailabilitySet -Name dcAvailabilitySet -ResourceGroupName $rgName -Location $locName\n\n# Create the domain controller virtual machine\n$vnet=Get-AzureRMVirtualNetwork -Name EX2016Vnet -ResourceGroupName $rgName\n$pip = New-AzureRMPublicIpAddress -Name adVM-NIC -ResourceGroupName $rgName -Location $locName -AllocationMethod Dynamic\n$nic = New-AzureRMNetworkInterface -Name adVM-NIC -ResourceGroupName $rgName -Location $locName -SubnetId $vnet.Subnets[0].Id -PublicIpAddressId $pip.Id -PrivateIpAddress 10.0.0.4\n\n$avSet=Get-AzureRMAvailabilitySet -Name dcAvailabilitySet -ResourceGroupName $rgName \n$vm=New-AzureRMVMConfig -VMName adVM -VMSize Standard_D1_v2 -AvailabilitySetId $avSet.Id\n\n$storageAcc=Get-AzureRMStorageAccount -ResourceGroupName $rgName -Name $saName\n$vhdURI=$storageAcc.PrimaryEndpoints.Blob.ToString() + \"vhds\/adVM-EX2016Vnet-ADDSDisk.vhd\"\nAdd-AzureRMVMDataDisk -VM $vm -Name ADDS-Data -DiskSizeInGB 20 -VhdUri $vhdURI  -CreateOption empty\n$cred=Get-Credential -Message \"Type the name and password of the local administrator account for adVM.\"\n\n$vm=Set-AzureRMVMOperatingSystem -VM $vm -Windows -ComputerName adVM -Credential $cred -ProvisionVMAgent -EnableAutoUpdate\n$vm=Set-AzureRMVMSourceImage -VM $vm -PublisherName MicrosoftWindowsServer -Offer WindowsServer -Skus 2012-R2-Datacenter -Version \"latest\"\n$vm=Add-AzureRMVMNetworkInterface -VM $vm -Id $nic.Id\n$osDiskUri=$storageAcc.PrimaryEndpoints.Blob.ToString() + \"vhds\/adVM-EX2016Vnet-OSDisk.vhd\"\n$vm=Set-AzureRMVMOSDisk -VM $vm -Name adVM-EX2016Vnet-OSDisk -VhdUri $osDiskUri -CreateOption fromImage\nNew-AzureRMVM -ResourceGroupName $rgName -Location $locName -VM $vm<\/pre>\n
    We will be prompted for a user name and password. This article will refer to this user name as ADMIN_NAME. Use a strong password and record both in a secure location.<\/p>\n
    Note<\/strong>: It can take a few minutes for Azure to build the virtual machine.<\/em><\/p>\n
    Connect to the domain controller virtual machine using local administrator account credentials<\/strong><\/p>\n
      \n
    1. In the Azure portal<\/a>, click Resource Groups ><\/strong> <your resource group name> > adVM > Connect<\/strong>.<\/li>\n
    2. Run the adVM.rdp file that is downloaded, and then click Connect<\/strong>.<\/li>\n
    3. In Windows Security<\/strong>, click Use another account<\/strong>. In User name<\/strong>, type adVM\\<\/strong><ADMIN_NAME>.<\/li>\n
    4. In Password<\/strong>, type the password of the ADMIN_NAME account, and then click OK<\/strong>.<\/li>\n
    5. When prompted, click Yes<\/strong>.<\/li>\n<\/ol>\n
      Add an extra data disk as a new volume with the drive letter F:<\/strong><\/p>\n
        \n
      1. From the adVM desktop, in the left pane of Server Manager, click File and Storage Services<\/strong>, and then click Disks<\/strong>.<\/li>\n
      2. In the contents pane, in the Disks<\/strong> group, click disk 2<\/strong> (with the Partition<\/strong> set to Unknown<\/strong>).<\/li>\n
      3. Click Tasks<\/strong>, and then click New Volume<\/strong>.<\/li>\n
      4. On the Before you begin<\/strong> page of the New Volume Wizard<\/strong>, click Next<\/strong>.<\/li>\n
      5. On the Select the server and disk<\/strong> page, click Disk 2<\/strong>, and then click Next<\/strong>. When prompted, click OK<\/strong>.<\/li>\n
      6. On the Specify the size of the volume<\/strong> page, click Next<\/strong>.<\/li>\n
      7. On the Assign to a drive letter or folder<\/strong> page, click Next<\/strong>.<\/li>\n
      8. On the Select file system settings<\/strong> page, click Next<\/strong>.<\/li>\n
      9. On the Confirm selections<\/strong> page, click Create<\/strong>.<\/li>\n
      10. When complete, click Close<\/strong>.<\/li>\n<\/ol>\n
        Next, configure adVM as a domain controller and DNS server for the corp.contoso.com domain. Run these commands at an administrator-level Windows PowerShell command prompt on adVM.<\/p>\n
        Install-WindowsFeature AD-Domain-Services -IncludeManagementTools\nInstall-ADDSForest -DomainName corp.contoso.com -DatabasePath \"F:\\NTDS\" -SysvolPath \"F:\\SYSVOL\" -LogPath \"F:\\Logs\"<\/pre>\n
        After adVM restarts, reconnect to the adVM virtual machine.<\/p>\n
        Connect to the domain controller virtual machine using domain credentials<\/strong><\/p>\n
          \n
        1. In the Azure portal<\/a>, click Resource Groups ><\/strong> <the name of your new resource group> > adVM > Connect<\/strong>.<\/li>\n
        2. Run the adVM.rdp file that is downloaded, and then click Connect<\/strong>.<\/li>\n
        3. In Windows Security<\/strong>, click Use another account<\/strong>. In User name<\/strong>, type CORP\\<\/strong><ADMIN_NAME>.<\/li>\n
        4. In Password<\/strong>, type the password of the ADMIN_NAME account, and then click OK<\/strong>.<\/li>\n
        5. When prompted, click Yes<\/strong>.<\/li>\n<\/ol>\n
          From the desktop, open an administrator-level Windows PowerShell command prompt and run the following command:<\/p>\n
          Add-WindowsFeature RSAT-ADDS-Tools<\/pre>\n
          Here is the result of Phase 1.
          \n\"result-1\"<\/p>\n
          Phase 2: Create the Exchange 2016 virtual machine<\/strong>
          \nIn this phase, we create an Exchange 2016 virtual machine in the EX2016VNet virtual network and make it a member of the CORP domain.
          \nTo create the Exchange 2016 virtual machine with Azure PowerShell, we need to log in to Azure with your Azure account from the Windows PowerShell command prompt (if needed).<\/p>\n
          Login-AzureRmAccount<\/pre>\n
          We must determine a globally unique DNS name for the exVM virtual machine. We can do this with the following PowerShell commands:<\/p>\n
          $vmDNSName=\"\"\n$locShortName=\"\"\nTest-AzureRmDnsAvailability -DomainQualifiedName $vmDNSName -Location $locShortName<\/pre>\n
          If we see “True”, our proposed name is globally unique.
          \nNext, fill in the variable values and run the resulting block at the PowerShell prompt.<\/p>\n
          # Set up key variables\n$subscrName=\"\"\n$rgName=\"\"\n$locName=\"\"\n$vmDNSName=\"<unique, public DNS name for the Exchange server>\"\n\n# Set the Azure subscription\nGet-AzureRmSubscription -SubscriptionName $subscrName | Select-AzureRmSubscription\n\n# Get the Azure storage account name\n$sa=Get-AzureRMStorageaccount | where {$_.ResourceGroupName -eq $rgName}\n$saName=$sa.StorageAccountName\n\n# Create an availability set for Exchange virtual machines\nNew-AzureRMAvailabilitySet -Name exAvailabilitySet -ResourceGroupName $rgName -Location $locName\n\n# Specify the virtual machine name and size\n$vmName=\"exVM\"\n$vmSize=\"Standard_D3_v2\"\n$vnet=Get-AzureRMVirtualNetwork -Name \"EX2016Vnet\" -ResourceGroupName $rgName\n$avSet=Get-AzureRMAvailabilitySet -Name exAvailabilitySet -ResourceGroupName $rgName \n$vm=New-AzureRMVMConfig -VMName $vmName -VMSize $vmSize -AvailabilitySetId $avSet.Id\n\n# Create the NIC for the virtual machine\n$nicName=$vmName + \"-NIC\"\n$pipName=$vmName + \"-PublicIP\"\n$pip=New-AzureRMPublicIpAddress -Name $pipName -ResourceGroupName $rgName -DomainNameLabel $vmDNSName -Location $locName -AllocationMethod Dynamic\n$nic=New-AzureRMNetworkInterface -Name $nicName -ResourceGroupName $rgName -Location $locName -SubnetId $vnet.Subnets[0].Id -PublicIpAddressId $pip.Id -PrivateIpAddress \"10.0.0.5\"\n\n# Specify the image and local administrator account, and then add the NIC\n$cred=Get-Credential -Message \"Type the name and password of the local administrator account for exVM.\"\n$vm=Set-AzureRMVMOperatingSystem -VM $vm -Windows -ComputerName $vmName -Credential $cred -ProvisionVMAgent -EnableAutoUpdate\n$vm=Set-AzureRMVMSourceImage -VM $vm -PublisherName MicrosoftWindowsServer -Offer WindowsServer -Skus 2012-R2-Datacenter -Version \"latest\"\n$vm=Add-AzureRMVMNetworkInterface -VM $vm -Id $nic.Id\n\n# Specify the OS disk name and create the VM\n$diskName=\"OSDisk\"\n$storageAcc=Get-AzureRMStorageAccount -ResourceGroupName $rgName -Name $saName\n$osDiskUri=$storageAcc.PrimaryEndpoints.Blob.ToString() + \"vhds\/\" + $vmName + $diskName  + \".vhd\"\n$vm=Set-AzureRMVMOSDisk -VM $vm -Name $diskName -VhdUri $osDiskUri -CreateOption fromImage\nNew-AzureRMVM -ResourceGroupName $rgName -Location $locName -VM $vm\n<\/pre>\n
          From the Azure portal, connect to the exVM virtual machine using the credentials of the local administrator account.
          \nNext, join exVM to the Windows AD domain with these commands at a Windows PowerShell prompt.<\/p>\n
          Add-Computer -DomainName \"corp.contoso.com\"\nRestart-Computer\n<\/pre>\n
          Note that we must supply domain account credentials after entering the Add-Computer command. Use the CORP\\ account and password.<\/p>\n
          Here is the result of Phase 2.
          \n\"result-2\"<\/p>\n
          Phase 3: Configure Exchange 2016<\/strong><\/p>\n
          In this phase, you configure Exchange 2016 on exVM and test mail delivery between two mailboxes.<\/p>\n
          Prepare Windows Server AD<\/strong><\/p>\n
            \n
          1. At the PowerShell command prompt on your local computer, run the following commands:\n
            $pip = Get-AzureRMPublicIpaddress -Name \"exVM-PublicIP\" -ResourceGroup $rgName\n$pip.DnsSettings.Fqdn<\/pre>\n<\/li>\n
          2. Note or copy the full DNS name from the display of the last command. This is the Internet DNS name of the exVM virtual machine. You will need this value later.<\/li>\n
          3. If needed, connect to the adVM virtual machine with the Azure portal using the CORP\\<ADMIN_NAME> account and password.<\/li>\n
          4. From the Start screen of adVM, type Active Directory<\/strong>, and then click Active Directory Domains and Trusts<\/strong>.<\/li>\n
          5. Right-click Active Directory Domains and Trusts<\/strong>, and then click Properties<\/strong>.<\/li>\n
          6. In Alternative UPN suffixes<\/strong>, type or copy the Internet DNS name of the exVM virtual machine from step 2, click Add<\/strong>, and then click OK<\/strong>.<\/li>\n
          7. Close the remote desktop session with adVM.<\/li>\n<\/ol>\n
            Install Exchange 2016<\/strong><\/p>\n
              \n
            1. Connect to the exVM virtual machine with the Azure portal using the CORP\\<ADMIN_NAME> account and password.<\/li>\n
            2. From exVM, open an administrator-level Windows PowerShell command prompt and run the following commands.\n
              Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation, RSAT-ADDS-Tools,\nRestart-Computer\n<\/pre>\n<\/li>\n
            3. Connect to the exVM virtual machine with the Azure portal using the CORP\\<ADMIN_NAME> account and password.<\/li>\n
            4. From Server Manager, click Local Server<\/strong>. In the Properties<\/strong> for exVM, click On<\/strong> for IE Enhanced Security Configuration<\/strong>. In Internet Explorer Enhanced Security Configuration<\/strong>, click Off<\/strong> for both Administrators and Users, and then click OK<\/strong>.<\/li>\n
            5. From the Start screen, click Internet Explorer<\/strong>, and then download the Unified Communications Managed API 4.0 Runtime from https:\/\/www.microsoft.com\/download\/details.aspx?id=34992<\/a>. When prompted, click Run<\/strong>.<\/li>\n
            6. When prompted with the Microsoft Unified Communications Managed API 4.0, Runtime Setup, click Next<\/strong>.<\/li>\n
            7. Click I have read and accepts the license terms<\/strong>, and then click Install<\/strong>. On the Installation is Complete<\/strong> page, click Finish<\/strong>.<\/li>\n
            8. From Internet Explorer, download the latest version of Exchange 2016 at http:\/\/go.microsoft.com\/fwlink\/p\/?LinkId=747753<\/a>.<\/li>\n
            9. Click Save<\/strong> to store the ISO file in the Downloads folder.<\/li>\n
            10. Click Open Folder<\/strong>, right-click the Exchange ISO file, and then click Mount<\/strong>.<\/li>\n
            11. From an administrator-level Windows PowerShell command prompt on exVM, run the following:\n
              e:\\setup.exe \/mode:Install \/role:Mailbox \/OrganizationName:Contoso \/IacceptExchangeServerLicenseTerms\nRestart-Computer<\/pre>\n<\/li>\n<\/ol>\n
              Wait until Exchange setup completes, which can take some time, and exVM restarts.<\/p>\n
              Add two mailboxes to the Exchange server<\/strong><\/p>\n
                \n
              1. Connect to the exVM virtual machine with the Azure portal using the CORP\\<ADMIN_NAME> account and password.<\/li>\n
              2. From the Start screen, type Exchange<\/strong>, and then click Exchange Management Shell<\/strong>.<\/li>\n
              3. Copy the following commands to Notepad, insert the Internet DNS name of the exVM virtual machine for the $dnsName<\/strong> variable, and then copy and paste the resulting commands into the Exchange Management Shell.\n
                $dnsName=\"\"\n$user1Name=\"Vasya@\" + $dnsName\n$user2Name=\"janice@\" + $dnsName\n$db=Get-MailboxDatabase\n$dbName=$db.Name\n$password = Read-Host \"Enter password\" -AsSecureString<\/pre>\n<\/li>\n
              4. Record the password specified in a safe place. Next, run these commands to create two mailboxes.\n
                New-Mailbox -UserPrincipalName $user1Name -Alias Vasya -Database $dbName -Name VasyaPupkin -OrganizationalUnit Users -Password $password -FirstName Vasya -LastName Pupkin -DisplayName \"Vasya Pupkin\"\nNew-Mailbox -UserPrincipalName $user2Name -Alias janice -Database $dbName -Name janiceViraide -OrganizationalUnit Users -Password $password -FirstName janice -LastName Viraide -DisplayName \"janice Viraide\"\n<\/pre>\n<\/li>\n<\/ol>\n
                Test email delivery between mailboxes<\/strong><\/p>\n
                  \n
                1. From the browser on our local computer, access the website https:\/\/<\/strong><Internet DNS name of the exVM virtual machine>\/owa<\/strong>. When prompted with an error page for the website\u2019s security certificate, click Continue to this website<\/strong>. On the Outlook sign-in page, use the corp\\vasya account name with its password.<\/li>\n
                2. When prompted to specify the language and time zone, select the appropriate value for each, and then click Save<\/strong>.<\/li>\n
                3. From Vasya Pupkin\u2019s inbox, click New<\/strong>. In To<\/strong>, type janice<\/strong> and then click Search Directory<\/strong>. For Subject<\/strong>, type Test message<\/strong>, and then click Send<\/strong>.<\/li>\n
                4. Click the user icon in the upper right part of the Mail web page, and then click Sign out<\/strong>.<\/li>\n
                5. On the Outlook sign-in page, use the corp\\janice account name with its password. When prompted to specify the language and time zone, select the appropriate value for each, and then click Save<\/strong>.<\/li>\n
                6. Verify that the inbox contains the test message from Vasya Pupkin. Click it, then click Reply all<\/strong>. In the body of the message, type Replied<\/strong>, and then click Send<\/strong>.<\/li>\n
                7. Click the user icon in the upper right part of the Mail web page, and then click Sign out<\/strong>.<\/li>\n
                8. On the Outlook sign-in page, use the corp\\Vasya account name with its password. Verify that the reply email message sent from janice is in the inbox.<\/li>\n<\/ol>\n
                  We are now ready to test Exchange 2016 features or applications!<\/p>\n","protected":false},"excerpt":{"rendered":"
                  If you like me and always want to be at the edge of the technology, you always play with the new version of products. Sometimes having a platform (servers, storage, switches, etc.) to run a product on it is a bit a challenge :). Let’s see how to build VERY simple (1 Domain Controller and […]<\/p>\n","protected":false},"author":1,"featured_media":6845,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[20,4,33],"class_list":["post-6843","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-azure","tag-exchange","tag-private-cloud"],"_links":{"self":[{"href":"https:\/\/www.highclouder.com\/index.php?rest_route=\/wp\/v2\/posts\/6843","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.highclouder.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.highclouder.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.highclouder.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.highclouder.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=6843"}],"version-history":[{"count":1,"href":"https:\/\/www.highclouder.com\/index.php?rest_route=\/wp\/v2\/posts\/6843\/revisions"}],"predecessor-version":[{"id":7250,"href":"https:\/\/www.highclouder.com\/index.php?rest_route=\/wp\/v2\/posts\/6843\/revisions\/7250"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.highclouder.com\/index.php?rest_route=\/wp\/v2\/media\/6845"}],"wp:attachment":[{"href":"https:\/\/www.highclouder.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=6843"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.highclouder.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=6843"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.highclouder.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=6843"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}