In Citrix Studio, it is possible to create a new hypervisor connection, and move the VMs to that new connection. The reason new connection be created and we move VMs to that connection can be varies – from commissioning new vCentre server to changing to a new hypervisor platform (from Microsoft Hyper-V to VMware vSphere). This post will explain on how to change the connection from current to a new one. The connection needs to be already established prior to implementation of this steps.  RDP to Citrix Studio server, and launch PowerShell . Add Citrix snap-in by following below command. Command : asnp citrix* Identify current and to be used Broker Connection IDs by using below command. In this example, I want to change  from H ypervisor Connection UID 1 to Hypervisor Connection UID  3 Command : get-BrokerHypervisorConnection

So this is my second PowerShell script created by me. The first one was so simple and I use it in my XenDesktop environment. This script on the other hand, is aprt of my initiative in performing Active Directory clean-up in my environment.  The task of the script is simple - check the IP address of a machine name, then check the hostname of that IP address.  - If the machine name (A host record) and the hostname (PTR record) is similar, we are good.  - If the machine name (A host record) and the hostname (PTR record) is different, error prompted - If the machine name (A host record) is available but the hostname (no PTR record) is not, error prompted - If the machine is not avaiable (no A host record), error prompted. I use  $PSScriptRoot so the location of the script is dynamic, it does not necessarily need to be put at a specific location. This is only part 1. I wish to add more features so it could be better next time. ###################################

Certificate Authority is a server role introduced by Microsoft, to issue digital certificates to target recipients. These digital certificates enable the environment to communicate securely between each other. This post illustrates on how to :- Request certificate from an internal root CA Download the certificate from internal root CA Install the certificate to server Bind the certificate to HTTPS protocol However, this post won't explain on how to install internal CA server. you may refer here for that. So let's get started. Request Certificate From an Internal Root CA  Launch IIS Manager Click at the server name. Inside the working space area, locate Server Certificate feature, and double click at it / right click | open feature Click at Create Certificate Request... Put in all needed info, and click  Next Select crypto service provider and bit length , click Next Specify the location of

Certificate Authority is a server role introduced by Microsoft, to issue digital certificates to target recipients. These digital certificates enable the environment to communicate securely between each other.  Installing an internal CA server is not too hard and pretty much straight forward I believe.  Description : Installing an Internal CA on Server 2012. How To Do :  Launch Server Manager , Go to Manage | Add Roles and Features  Click  Next >  Ensure Role-based or feature-based installation is chosen, and click  Next >      Ensure the target server is selected from the server pool, and click Next >   Check / tick Active Directory Certificate Services role  The Add Roles and Features Wizard appeared. Click at Add Features button.  Click Next >   Select additional features if needed, then click Next >