kgsivan's Posts

> 5. This is a strange one - I didn't decrease the pool size in the steps above (our servers have enough overhead to take the full pool size with one server down). I'm assuming that when desktops on the other datastores are deleted (logged off) > one by one, they will be spun up on this restored datastore (one by one)? Sorry... My bad. You don't need to increase pool size. Instead user "Disable Provisioning" before VM removal and "Enable Provisioning" after patching, and adding the host-back.. (If so, even you don't need to edit the datastore spec.)

Security server is another instance of View Connection server, and therfore its installation should satisfy the same requirements that of a View Connection Server requirements. I would advise to launch the security server installer with the same domain account, that used for installing the Connection server. Else as described in the error, configure 'View Administrator' role to the current user from which Security Server is being installed. <-- This can be done from View Administrator Console. Following Documents will help VMware View 5.2 Documentation Library- Install Security Server VMware Documentation Library - Create an Administrator

I believe, still you need to go for an upgrade. Because Horizon Mirage supports View desktops of version 5.3 onwards. Another way (Which is not officially supported) Create a new pool of windows 7, but ensure same hard-disk hardware controller is used in side the VM (If XP uses buslogic IDE, windows 7 also should be of the same) Now archive old user data disk, (if any) and then edit the last pool info tot he new Win 7 Pool. Select the archived Disk and click "Recreate" -- This can restore entire user data and setting. For application you need to manually prepare the new windows parent image and recompose.

Couple of things to make sure. Check you can add the VC alone without composer enabled. (If this happens, you can remove and re-add it with composer enabled) While configuring composer (while adding or editing VC) check you are using User Principle Name (UPN) or Domain\User format, else local administrator. However, the account should have local administrative privileges Make use you Composer is reachable to entire infra and can resolve FQDN of other components (View / VC/ Domain / ESX etc) If you are using co-installed composer, make sure , proper User credentials are given for VC configuration.

Yes, some what true. But i wouldn't say that is something impossible. If you are keen on bringing them up on demand (for other operations), you can look for leveraging View PowerShell APIs. Again, agree with you that, it will have its own limitations.

This is something very simple and straight forward. View agent (with feature pack) comes with Printer redirection a.k.a Thin print, which enables location based printing as well. You can refer below VMware documentation pages. VMware Documentation - Printing from a View Desktop VMware View 5.0 Documentation - Setting Up Location-Based Printing

>> What is the purpose of the "Remote Desktop Power Policy"? This policy allows administrator to decide to save power, when machines are idle for a specified amount of time. Assume, it is a vSphere cluster, of 4 or 5 hosts. On the weekend, if such policy got applied to mass amount of Virtual desktops, (Suspend or Poweroff) so much power can be saved and , if possible we can automatically put a vSphere host into standby mode. In large enterprises and scale level setup this will be a huge power saving. >>> What advantages are gained by setting to "Suspend" or "Power Off"? Simple... similar advantage gets from Laptop, putting into sleep by closing its lid, instead of shutdown. VMs are bypassed normal boot process, and restored the state from a suspended one.

OK, it looks like, former warning need to be resolved by kernel update. It is failing because SSL/Crypto lib package versions are old (1.0.1) Upgrade the  kernel version, which will automatically fix these dependencies and having recommended versions of lib packages. Please try it on test machine first.

Your understanding is true with 'Disposable Disk". They gets refreshed only while power-down initiated through VMware View. To remove System Disposable Disk from existing disk, first disable it on the pool configuration and then perform a Recompose (to a new image) or simple do a rebalance , so that VMs will get re-provisioned and the new settings will get applied. On a side note, you can make use to "Space Efficient Sparse Disk" enabled for pool, and schedule the wipe and shrink on the disks, to save storage.

Naming conventions does not have any thumb of rule, just need to stick within the 15 letter limit. Couple of things that are following at our end are location /  department / type (but sometime doesn't use VDI at all, as all those goes to a separate OU, instead specify the OS type W7 or W8 for windows) I would suggest to stick on the best and convenient format that your suites your organization needs.

You have mentioned that the 1 minute delay every time user connects. And the desktops are set to refresh after each log-off What about desktops are log-off reconnected *without* being refreshed? Could you please try this? Newly Provisioned (or even refreshed) desktops will definitely take extra time, because it need to create the user profile configuration and prepare the desktop. Such delay will depend on the performance of the VM and Storage IOPS.

For this, my suggestion will be as follows. Create trust relationship between domains. (Two way transitive) Setup new connection server on new domain as replica to the existing View server (And add the new administrator account to the administrator role) Once desktops are migrated, you can decommission the old connection server and you can remove the trust relationship.

You should *not* be doing detach/recreate for migrating Linked clones to new domain . I would suggest to perform "Recompose to new domain" as per below steps (This is officially supported scenario) Recompose to new domain: At server configuration page, edit vCenter configuration, edit View Composer settings and add new the Admin account for new Domain. Edit pool settings, Customization page, and choose (drop-down) new Domain that was added on step-1 Now Perform a rebalance (or recompose) all the clones will be moved to the new domain.