Nutanix Xi Frame – Part1

Nutanix Xi Frame Deployment Series: Part 1

Nutanix Frame:

Nutanix Xi Frame Desktop as A Service Platform Build for Cloud Deployments, having integration ith Azure, AWA, GOOGLE Cloud. But we can deploy Frame on-Prem on Nutanix AHV. In this Series I show the Nutanix Xi Frame Deployment on on-Prem Nutanix AHV.

Requirements:

  1. Nutanix Cluster Running with Acropolis Hypervisor with Prism Central 5.10 or newer
  2. Frame Agent and Cloud Connector Appliance (Download from here)
    Cloud Connector Appliance can be downloaded automatically during deployment also
  3. Xi Frame Subscription

STEPS:

  1. Create Golden Image
  2. Prepare Nutanix Cluster
  3. Connect to Xi Frame

Create Golden Image:

Now I will Install windows 10 & install Frame agent on it and then Sysprep the image.

Create VM on AHV:

Open Prim Element & Navigate to VM

Click Create VM to Create Virtual Machine

Assign VM Name, VCPU, RAM, Storage, Network and mount Windows 10 ISO , VertIO

Note: VertIO Is required to Install Window on AHV Hypervisor as Window 10 does have Nutanix ISCSI pass through Drivers

Click Save to Create the VM.

Power-On the Created VM.

Click Install to Proceed with installation

Click Install Now

Select Desire Language and keyboard options and Click Next

Select Operating System Version and Click Next

Accept the Agreement and Click Next

As Disk is not discovered, click load driver.

Browse Nutanix VertiIO ISO & Select the Driver as per Operating System Type. And click Ok

Select Nutanix VertiO SCSI Pass-through Controller and click next

Create Partition and click next to proceed with Windows Installation.

Once Windows Installation completed. Install VertiO Drivers.

Browse Mounted VertIO ISO and Run Setup.

 

Click Finish

Enable Remote Desktop and RDP to Virtual Machine for Frame Agent Installation.

Note: RDP to VM is requried, as once you install Frame Agent, VNC Console connection will be disconnected

Copy Downloaded Frame Agent Installer to Virtual machines and Run it.

 

Click Restart to Restart the VM.

Once You done with Image configration, run the below Command from PowerShell as Administator

Start-Process -FilePath “C:WindowsSystem32SysprepSysprep.exe” -ArgumentList “/oobe /shutdown /generalize /unattend:C:ProgramDataFrameSysprepUnattend.xml” -Wait -NoNewWindow

Virtual machine will be powered-off once Sysprep done.

Step 2: Prepare Nutanix Cluster

Open Nutanix Prism Central, open settings

Local user Management

Create new User: with prism Central admin & user admin permission.

Save your user name and password – you will need these later on in the process.

Click on the hamburger menu icon in the upper left portion of your Prism Central interface.

Expand the “Virtual Infrastructure” menu item and select “Categories.”

Click on the “New Category” button.

Fill in the form with the following values:

Name: FrameRole

Purpose: Create and Manage Frame Instances

Values: Instance, Template, and MasterTemplate (Add each value on separate lines using the plus symbol.)

Click “Save.”

From your home drop-down menu on the left, click “Settings.”

Under the “Setup” section of the “Settings” menu, click “Connect to Frame.”

 

On this page, specify the following:

 

Select Frame Service: This is your Frame Service deployment type. Most organizations should select “Commercial” unless using a Frame GovCloud deployment.

Dedicated AHV cluster: Select the cluster where the CCA would be deployed from the drop-down menu.

Network connected to Prism Central: Specify the VLAN that will be used by this CCA from the drop-down menu.

Click “Next.” The current image for CCA will be downloaded from Nutanix portal and deployed on the Nutanix cluster specified in the previous step. The progress can be monitored in the status bar. Once complete, click “Configure.”

 

Connect your AHV Cluster to Frame

Connecting your AHV cluster to Frame is the final task required to get Frame running on AHV.

NOTE: DHCP Is requried otherwise wizard will be stuck on 50% stage

Access the Frame Cloud Connector wizard by navigating to the CCA’s IP. For example https://192.168.2.X.

Login with the Prism Central account you have designated for Xi Frame and enter the Prism Central URL.

Provide the Service Account(you created eariler in Pirsm Central) information and Prism Central IP Address and click Login.

Select your cluster and network VLAN to host desktops and enter your desired cloud account name.

Note: To ensure a smooth setup, please make sure you are logged into your “My Nutanix” account in a separate tab in your browser window.

Define and add the VM instance types to use for your AHV-hosted Xi Frame account.

Check the box next to your golden master image VM template for the Sandbox template.

Click on the “OS” field listed next to your Sandbox template. Select your desired operating system. Click “Next” when you’re ready.

Select the Customer entity or Organization you created earlier in the Xi Frame account setup. Click “Finish.”

The wizard should inform you that your cluster has been connected successfully.

Note: Currently Configuration changes to cloud Connector appliance after its connects to Cluster is not possible, for changes need to contact Nutanix Support.

Log in to your Xi Frame account to check the cloud account creation status. The “C” status indicates that the account is still being created.

Note: If your account status hasn’t changed after an hour, please create a ticket through your MyNutanix support portal and provide your cloud account’s display name. You can locate the cloud account’s display name by navigating to the Organization or Customer entity’s “Cloud Accounts” tab.

The account status should change from “C” (Creating) to “R” (Ready).

Once the cloud account is ready, you can use your AHV infrastructure to create an account.

Ref: docs.frame.nutanix.com

Rubrik BMR Restore for Windows Physical/Virtual Server (Basic Disk Volume)

Hi,

Below is the procedure to perform Rubrik BMR (Volume Restore) on Physical / Virtual. Before starting the restore details please upgrade the CDM 4.2 to latest available as from CDM5.0 there major changes and enhancements related to Windows Volume backup / BMR Restore.

Supported Operating System:

  • Windows Server 2012
  • Windows Server 2012 R2
  • Windows Server 2016
  • Windows Server 2019

Requirements:

  • Microsoft Windows PE Bootable CD required to initiate the Restore Process

I have created the WINPE ISO which can be used to initiate restore on VMware/Hyper-V VM, you can download it from below link.

https://access.jouddrive.com/portal/s/0202101780743208790

Incase if you want to create WINPE ISO for Physical Server with Custom Raid Storage Drivers, Please use the below link

https://support.rubrik.com/s/article/000001905

Restore Procedure:

Step 1: Mount the Windows Volume you want to restore

Step 2: Initiate the Restore from WinPE

STEP 1: Mount Windows Volume for Restore:

  1. Browse the Windows Host for Select the Snapshot to restore

  1. Select Mount the Volume
  2. Select the Volume to Restore and click next
  3. Select no host and click next
  4. Specify Domain, username used during setting up SMB Security and Client IP Address you will be using in Restore Client during Boot. And click Finish.
  5. Mounted Volume will be available in live Mount à Windows Volume
  6. Move the mouse pointer on Mounted Volume and copied the SMB path, required during restore process. In our case below is the SMB path.
    \192.168.194.50uktucarubrik-ca6de0d9-5d29-4900-8c85-23a291ab4e30.vhdx

Step 2: Initiate the Restore from WinPE

  1. Boot from WinPE ISO
  2. Set IP Address on booted VM incase if DHCP is not available , if DHCP is available please skip to next step.
    List all interface names
    netsh interface show interface
    Set Static IP
    netsh int ip set address “Ethernet0” static 192.168.194.65 255.255.255.0 192.168.194.1
    Set DNS
    netsh interface ip add dns “Ethernet0” 192.168.194.10
  3. Browse to X:Utilities and run below command to start the BMR Restore script from Powershell and follow the Script steps.
    .RubrikBMR.ps1 -Operation bmr
  4. Wait for restore finish, once 100% restore done. Press Y to reboot the PC
  5. Once system is boot confirm, restored disks and reip the Server

Notes:

  • Local Admin Account password is required to logon on the restored System as you may not be able to use Domain Account for login
  • Customer WinPE may need to be created in case of Physical Restore with Proper RAID Controller Drivers.

Any Suggestions and Comments are Welcome, please share the feedback or comment if any.

Best Regards,
Qamar Abbas