Adding Citrix XenServer 5.6 SP2 into SCVMM 2012 Beta

a) I’m just got Citrix Certified Administrator (CCA): XenDesktop 5 . (Hooray !) . I took this exam is because of my work related on VDI. However, my VDI deployment is only using Citrix XenDesktop 5 with Hyper V (hypervisor platform) . So no major conflict . Anyway,Citrix and Microsoft is an alliance partner in term of VDI delivery as well.

b) Good to know since SCVMM 2012 has support on additional hypervisor : Citrix XenServer. It will become advantages for me to understand the technologies as well.

c) Pursuing to high level of Citrix certification. One of pre-requisite is i must take the CCA: XenServer.

For the benefit of people who’re interest on Citrix hypervisor, the new version included with

a) Feature Pack 1 +

b) Support for IntelliCache enabling you to use a combination of shared storage and local storage.

c) Local Storage Spans All Physical Volumes.

d) Reset-on-boot VM behaviour.

d) Block SCSI Generic Support added, enabling full compatibility with Emulex and QLogic management functionality.

e) Support for Red Hat Enterprise Linux (RHEL) 6.

Now, before integrate XenServer with SCVMM 2012, i need to install additional SCVMM Supplemental Packs.

The new version of SCVMM 2012 can manage Citrix XenServer without Citrix XenCenter (citrix hypervisor management software).

Xenserver1:-

Xenserver 2:

Integrate with SCVMM 2012:-

a) Computer name and Issue to (view certificate) must be same. If different, then you need to key in computer name according to Issue to . Both must match in order to successful adding Citrix Xenserver into SCVMM 2012.

After adding Citrix XenServer:-

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T Last month I got a call from a customer who was pulling their hair out over a networking issue. They had just deployed VMware Tanzu Kubernetes Grid on their vSphere with Tanzu environment, everything looked good in the dashboards, all pods were running, but their applications inside the pods could not reach external databases running on traditional VMs in the same datacenter. The frustrating part was that some pods could reach external services perfectly fine, while others would just timeout. There was no clear pattern. Let me tell you how we figured this out and fixed it. The Initial Problem Here is what the customer setup looked like: vSphere 8.0 with Tanzu enabled NSX-T 4.1.2 for networking Three Tanzu Kubernetes clusters running different microservices applications External PostgreSQL database running on traditional VMs (non-Kubernetes) External API services running on another se...

AD LDS – Syncronizing AD LDS with Active Directory

First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N...

Troubleshooting vSAN Storage Policy Migration Failures in VMware Cloud Foundation 9.0

Recently I had a customer who migrated their VMware infrastructure from vSphere 7.0 to VMware Cloud Foundation 9.0. After the migration, they wanted to update their vSAN storage policies to take advantage of the new vSAN ESA (Express Storage Architecture) features. However, when they tried to change the storage policy for their production VMs, the operation kept failing with a cryptic error message. The error they were getting was: "Cannot complete operation due to insufficient resources to satisfy current storage policy." This was strange because they had plenty of disk space available. The vSAN cluster was only at 45% capacity, and all the hosts were healthy. Let me walk through how we troubleshooted and fixed this issue. Understanding the Problem First, let's understand what was happening in their environment: They had a 6-node vSAN cluster running VCF 9.0 vSAN was configured with the new ESA architecture They were trying to migrate VMs fro...

My IT Blog

Search This Blog