Blade PC/Server: Series of servers added to a chasis and inserted it in a rack in datacenter.
Here in the front view, the green rectangles are single servers. In a single case we can add multiple servers. Small green rectangles are half blade servers(where processor and ram are less) and full rectangles(processor and ram are bit more) are servers. In the right hand side pic, we can see the back side of the blade server.
For desktops to be usable, they must register (that is, establish communication) with the correct controller or with any one of the controllers, if there are more than one.
The default operation, whose configuration is briefly described in this topic, uses information in the desktops’ registries to establish communication. This is referred to as registry-based controller discovery. You can also use an Organizational Unit (OU) in Active Directory (AD). This is referred to as AD-based controller discovery.
Citrix administrators are not set up automatically during XenDesktop installation. After installation, only local administrators on the server running the Controller have full administrative privileges, with authority to manage and administer all areas of the XenDesktop site. Only an administrator with full rights can create additional full or delegated administrators.
Note: Local administrators on the Controller always have full administrative privileges; these privileges always take precedence, regardless of delegated privileges that may later be explicitly assigned by Citrix administrators.
Upon first launch of Desktop Studio just after installation you’ll be presented with error message: “Object reference not set to an instance of an object. reload the snap-in to retry.”
Solution1:
Cause: Because “CitrixConfigurationService” service is NOT running on your system. In the eventvwr you’ll notice that reason why this service failing to startup. The most probable cause is that “This computer is not joined to a domain; these services cannot be run outside of a domain.
The Virtual Desktop Agent has to be present on the virtual machines (VMs) to which your users will be connecting. It enables the machines to register with controllers and manages the HDX connection between the machines and the user devices.
If you are using XenDesktop or Provisioning services to provision VMs, you need to install and configure the Virtual Desktop Agent only once, but if you are using separate stand-alone virtual or physical machines you must install it on each of the machines so they can register with the controller to allow user connections.
You can use multiple policies to customize XenApp to meet users’ needs based on their job functions, geographic locations, or connection types. For example, for security reasons you may need to place restrictions on user groups who regularly work with highly sensitive data. You can create a policy that requires a high level of encryption for sessions and prevents users from saving sensitive files on their local client drives. However, if some people in the user group do need access to their local drives, you can create another policy for only those users.
When installing RHEL 7 in xenserver, most of us might use the RHEL 6(64 bit) template. When creating vm with RHEL6 template, you need to add a word “vnc” at selecting the iso file step. Once the vm is up, you need to use vnc client to access that vm and configure the RHEL 7 OS. But when you follow this process, once the vm is built, you might get some error like:
Desktop groups are sets of virtual machines allocated to users and user groups. Full and assignment administrators can create desktop groups from the catalogs previously generated using the Create Catalog wizard.
Desktop groups are listed in Desktop Studio under the Assignments node. In addition to the total number of machines in each group, the number of available and in-use machines is shown; the number of unavailable and offline machines is not shown.
Client Hypervisor
A client hypervisor is a hypervisor that resides on a laptop, PC or other client device. A hypervisor is a program that allows multiple operating systems to share a single hardware host.
Normally all the Type2 hypervisors come under Client Hypervisor category.
A hypervisor comes in one of two forms: a bare-metal hypervisor, also known as Type 1; or a hosted hypervisor, also known as Type 2. There are important differences between a hosted and bare-metal virtualization hypervisor, and each has pretty specific use cases.
It is also recommended to take a snapshot before you start the below process. If something fails, you can revert to the old vm from the snapshot.
Boot your original master VM up. Install the new application Shut the VM down Take a new snapshot of the VM In DesktopStudio select the catalog in the MAchine node and chose “Update Machine”. Select the new snapshot and the image will be updated.
