260 likes | 378 Views
Hosting Day Workshop ORK Introduction. Gang Pan Microsoft. Session Overview. Introduction to ORK Build ORK Media Inside ORK Build Your Deployment with ORK. Introduction to ORK. What is the Operational Readiness Kit?.
E N D
Hosting Day WorkshopORK Introduction Gang Pan Microsoft
Session Overview • Introduction to ORK • Build ORK Media • Inside ORK • Build Your Deployment with ORK
What is the Operational Readiness Kit? • The Operational Readiness Kit combines the friendliness of a GUI and the versatility of Windows PowerShell scripting in order to rapidly deploy Microsoft Cloud OS based environment for service providers • ORK is (currently) packaged on a USB storage device with evaluation versions of Microsoft Cloud OS components, such as System Center 2012 R2, Windows Azure Pack, SQL Server 2012 and Windows Server 2012 R2 • Leverages the PowerShell Deployment Toolkit (PDT) 2.6 for System Center Deployment
Partner Cloud OS Deployment Challenges • Challenging Deployment – Knowledge required before even trying to evaluate • Time Consuming – A few days or week(s) could be required to deploy all the necessary products • Costly to deploy – Time, Requirement, and Resources spent on the efforts • Wrong Focus – Too much focus on deploying and too little focus on the actual products • Lack of Guidance – Lack of guidance on how best to deploy the solution
ORK Benefits for Partners • Focused Effort – Allow partners to more quickly deploy Cloud OS environment, therefore able to spend more time on the most valuable tasks. • Consistent Deployment Experience • Speed of Deployment – Bring Cloud OS deployment time down to hours
Operational Readiness Kit – What is it? Deployment Tools Post-Deployment Guidance Pre-deployment Documentation
POC Deployments (Non-Production) • Microsoft System Center Virtualization (5 VMS) • Virtual Machine Manager, Operations Manager, Operations Manager Reporting, SQL Server, Domain Controller • Highly Available Microsoft System Center Virtualization (10 VMS) • Clustered Virtual Machine Manager, Operations Manager, Operations Manager Reporting, Clustered SQL Server, two Domain Controllers • Microsoft Cloud OS (14 VMS) • Virtual Machine Manager, Operations Manager, Operations Manager Reporting, SQL Server, Orchestrator Management Server and Orchestrator Runbook Server, SPF, Configuration Manager, Windows Azure Pack, WSUS, Domain Controller • Highly Available Microsoft Cloud OS (18 VMS) • Clustered Virtual Machine Manager, Operations Manager, Operations Manager Reporting, Clustered SQL Server, Orchestrator Management Server and Orchestrator Runbook Server, SPF, Configuration Manager, Windows Azure Pack, WSUS, Management Console, two Domain Controllers • SQL Server Clustering (4 VMS)
POC Technical Requirements • At least one Microsoft Windows Server 2012 R2 Host • Hyper-V Role Enabled • One virtual switch created • A contiguous range of IP addresses to assign to virtual machines • The following minimum hardware requirements for POC scenarios:
Product Line Architecture (PLA) Deployments • HA Cloud OS +Distributed WAP, Websites, SM, AC, PKI, SMA. SMB (38 VMs) • HA Cloud OS +Websites, SM, AC, PKI, SMA. Shared VHDX (33 VMs) • HA Cloud OS +Distributed WAP, Websites, SM, AC, PKI, SMA. Shared VHDX (38 VMs) • HA Cloud OS +Websites, SM, AC, PKI, SMA. SMB (33 VMs)
PLA Deployment Technical Requirements • At least one Microsoft Windows Server 2012 R2 • Hyper-V Role Enabled • One virtual switch created • A contiguous range of IP addresses to assign to virtual machines • The following minimum hardware requirements for POC scenarios:
Deployment Overview • Deploy one or more hosts with Windows Server 2012 R2 Datacenter and enable Hyper-V. • Prepare the hardware and copy ORK contents to host. • Use ORK to create and execute a customized deployment package. • Complete test scenarios using provided checklists & training.
ORK Media • Contains all of the installation media and Windows Server images required to deploy. • When using a flash drive, place documentation in root. • Installer folder has the remaining content
Build the ORK Media • Prepare Server • Install download prerequisites • Configure Windows PowerShell • Download ORK • Download and extract software and base VHDs • Download System Center, Windows, and SQL media • Create or download base Windows Server VHDX • Download prerequisite software • Create ORK configuration. • Use Downloader.ps1 to obtain remaining software.
Preparing the Server • Download and install 7-Zip or WinRar • Use the x64 version • Be sure to review licensing information for each product • Download and install the Microsoft Web Platform Installer • WebPI can be downloaded: http://www.microsoft.com/web • Do not run WebPI after installation • Set Windows PowerShell execution policy to Unrestricted • Open an administrative Windows PowerShell console • Run Set-ExecutionPolicy Unrestricted • Create a Installer folder to store media. (example: X:\Installer) • Copy ORK.exe to Installer folder
Download and extract software • Extract the System Center components into the following folders: • X:\Installer\SystemCenter2012R2\AppController • X:\Installer\SystemCenter2012R2\ConfigurationManager • X:\Installer\SystemCenter2012R2\DataProtectionManager • X:\Installer\SystemCenter2012R2\OperationsManager.en • X:\Installer\SystemCenter2012R2\Orchestrator • X:\Installer\SystemCenter2012R2\ServiceManager • X:\Installer\SystemCenter2012R2\VirtualMachineManager • Extract the Windows Server 2012 R2 and the Windows Server 2012 source files from the ISO files to the following folders: • X:\Installer\WindowsServer2012R2 • X:\Installer\WindowsServer2012 • Optional: Extract Microsoft SQL Server 2008 R2 and SQL Server 2012 to the following folders: • X:\Installer\SQLServer2008R2 • X:\Installer\SQLServer2012.en
Create base VM images • Create a sysprepped Windows Server 2012 R2 VHDX. • Must create image for correct virtual machine generation. • Options for creating image: • Download from TechNet Evaluation center and convert from VHD to VDX. • Use Convert-WindowsImage.ps1 script available from TechNet Script Center • Create own VM image. • Place VHDX in X:\Installer and name it WIN2012R2RTM.VHDX • Create a sysprepped Windows Server 2008 R2 VHDX. • Options for creating image: • Download from TechNet Evaluation center and convert from VHD to VDX. • Create own VM image. • Place VHDX in X:\Installer and name it WIN2008R2.VHDX
Download Software Prerequisites • Run ORK.EXE from X:\Installer. • Create a new deployment using the (PLA) Highly Available Microsoft Cloud OS Deployment with Distributed WAP and VHDX deployment template. • Use any domain and IP information, this is not used for downloading content. • On the Virtual Machine Information page. Make sure the Installation Source Path matches your media location. Complete the wizard. • Use any password information, this is not used for downloading content. Leave the remaining fields with default values. • Export the deployment package and start an administrative Windows PowerShell session. • Run .\Downloader.ps1 –DeploymentOnly. • This process can take some time to complete.
FAQ • Where can I get ORK? • Request the Hosting Provider Yammer network at: http://aka.ms/JoinHSP • “Build your Own” documentation available in the Yammer group’s file section • Where can I get help with my deployment using ORK? • Use the included troubleshooting documentation, checklists, and training material included with the ORK tool. We also have an external Yammer network at • http://aka.ms/JoinHSP • “Build your Own” documentation available in the Yammer group’s file section
Deployment Package Overview • Deployment package includes: • Deploy.ps1 – Script used to handle entire deployment process • VMCreator.ps1 – Part of PDT used to create VMs • Installer.ps1 – Part of PDT used to install components • Workflow.xml – Part of PDT used to control deployment • Variable.XML Part of PDT customized to define specific deployment. • Folders are created for virtual machines that require additional configuration. The scripts will be copied to the appropriate virtual machine during deployment. These scripts are extensions to PDT.
Greenfield deployment process • Run Deploy.ps1. The script handles all of the required steps. • Deploy verifies that: • all specified hosts are available and Hyper-V is installed • the VM Switch exists • the VHD files are in the correct location • that settings are in place for shared VHDX, if chosen. • Runs VMCreator.ps1 with correct switches to create VMs • VMCreator will start the virtual machines and initiate the deployment from the first domain controller.
Existing domain deployment process • Run Deploy.ps1. The script handles all of the required steps. • Deploy verifies that: • all specified hosts are available and Hyper-V is installed • the VM Switch exists • the VHD files are in the correct location • that settings are in place for shared VHDX, if chosen. • Runs VMCreator.ps1 with correct switches to create VMs • Runs DomainPrep.ps1 to create required accounts in current domain • Makes additional settings based on deployment. • Runs Installer.ps1 to initiate the deployment.