kgsivan's Accepted Solutions

Yes. The settings will be only applied to newly provisioned VMs. If you want to change the existing VM name thn do following: For dedicated pools: Archive first 10 Vm's persistent Disk and recreate. For floating pool: Apply 'delete after logoff' option and ask first 10 users to logout. Once all the Vms are deleted then change back the settings.

While creating Windows XP VM you can create the VM using IDE or SCSI, and even both type of SCSI controllers. You may have to provide necessary driver to proceed with installation, but defenitely changing the default SCSI controller type will not impact any maintenance operations like recompose, rebalance and refresh.

MMR through PCoIP is the one which is not supported on Windows 7, and defenitely you can make use of RDP (in built RDP version 7.0) From your post I understand that you need to support streaming videos on Windows 7. So that means the Virtual Desktops are of Winodows 7. But the above limitation is for Windows 7 as view clients. Please be aware that MMR on PCoIP still supports if you are using Windows XP or Vista as view clients to launch the same desktop.

Hi mittim12, Brokering to existing desktops should happen without much issue. The things need to ensure that accessing pools with certain policies might end up in error like, power policies, spare configuration etc. So before perfoming such maintenance, edit power policy of all pools accrodingly and remove spare configurations, auto scheduled provisioning ops (such as delete after use, refresh after use etc). But defenitely log of policies will not have any impact. I am sure that you would take necessary backup prior to the maintenance. Best Regards Siva

The driver installation happens to the OS disk. So if the new image doesnot contain the same driver system will lose the configuration, and it is expected. Only sytem identities and User profile and data is possible to retain througout the maintenance operations (recompose/Rebalance etc.) Aslo please note that View doesnt maintain the "All User" Profile.

Defenitely.. you can plan and design security server and place appropriate zones to have a secure access externally. You can search for sample designs on vmware website or can contact your local vmware pre-sales team/support for more information. Regards Siva **If you found this or other information useful, please consider awarding points for "Correct" or "Helpful"

Event database holds all historical events of your View Brokers so over time it could get quite large. There are no specific recommendations for the sizing of Event Database in the 4.5 documentation. However it shouldn't grow at a large rate unless there is a problem which causes thousands of events to be raised by the View or if you have a huge floating-pool environment which will result in provisioning and deleting linked clones periodically. In event database, there are two parts, one is historical and other is live. These are in two different tables. Only Live events can see in connection broker and the remaining in an archived form. The amount of live events can be configured (like up to six months). The remaining part in the DB can be controlled by means of any SQL scripts.

If View Composer service is up and running, and port is not blocked by any firewall then ensure following: The account used for VC credenticals configuration in view admin page, has local administrator privilages in Server 2008 SP2 (vCenter Server) The DSN connection used for View Composer successfully able to make database connection (normally if this is not then composer may fail to start. But after the service startedany alteration to the DSN also can cause this isse) Thanks

What is the customization that you have selected during pool creation (Sysprep/QuckPrep) ? Please not that irrespective of the customization type (syspre/quickprep) Linked clone will try to join to the domain that you have chosen in pool creation wizard and *NOT* to the one specified in the VC Custom spec selected. Hence the Domain Account which is configured (vcenter Server properties - Server Configuration page of View administrator ) shoudl be proper, and the DNS server should able to resolve that Domain. So ensure: 1. DNS settings for each client, and Domain connectivity 2. Appropritae Domain Account and OU selected from the Pool creation wizard 3. The added Domain account has enough permissions (Refer to the admin guides) If above settings are proper, then , 4. Verify that the "Connect at power on" is enabled for the Parent VM network card, and the snapshot includs that settings (revert tot eh snapshot and verify network settings)

40-50 View clients could be possible in SQL express without much issues. Going through your reply it is clear that the subnet22 is the network which will have higest network utilization than others w.r.t View Desktops.(and your assumption is right). The network configuration in the ESX for connecting VMs to the Subnet22 is what called VMNetwork Default Username and passoword for the SQLExpress will be the account used to login and install vCenter server in windows machine (this is a windows authentication). You can connect to it as below. Download and install SQL Management Studio from microsoft website in the virtual center host os Open SQL studio, then click on connect , at the server name give 'localhost\SQLEXP_VIM' and select windows authentication This way you can manage the SQL express, and create new database. You can also refer to the DSN for vcenter server which created automatically during installation Most of the VirtualCener servers are VMs I beleive, but as per my understanding both are popular. Defenitly keeping vCenter in VM have lot of advantages and felxibilities. Thanks Siva If you found this or other information useful, please consider awarding points for "Correct" or "Helpful"

View Server will select a datastore based on one of the following methode Maximum Available Space Minimum Population Density The available space is calculated based on below equation: Available Space = Datastore Capacility * Overcommit Factor - Virtual Usage On selecting the datastore for creating new VMs, the datastore selector calculates the "virtual usage". Here, the virtual usage means the maximum possible usage when all VMs on that datastore are powered on: Virtual Usage = usage_by_all_VMs_after_power_on Here, the usage_by_all_VMs_after_power_on = sum of all disk file size and configured memory size of all VMs of the datastore. One thing to note here is that, this calculation may fails to count in those orphan files, such as archived disk files or other user files, that are not belong to any VMs.