kgsivan's Posts

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 documenta... See more...
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 admin... See more...
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
Yes. GUID's should not be duplicated for linked clones with SCCM agent. Install SCCM agent on parent, take snapshot and start pool provisioning. If you want to avoid SID duplication , the selec... See more...
Yes. GUID's should not be duplicated for linked clones with SCCM agent. Install SCCM agent on parent, take snapshot and start pool provisioning. If you want to avoid SID duplication , the select sysprep provisioning 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... See more...
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)
I hope this is an upgrade from existing View 4.0 to View 4.1. If so the firect component ot upgrade is View Connection server. But the below described problem doesnot seems to because of that. Si... See more...
I hope this is an upgrade from existing View 4.0 to View 4.1. If so the firect component ot upgrade is View Connection server. But the below described problem doesnot seems to because of that. Since the vCenter Server is changed old view composer database may look correcpted for Connection server, becase the entries in composer db refers to the old Center. The best approach to such migration is perform vCenter Server upgrade Was that an VC upgrade or vCenter server change ? Where was the view composer database stored ? Was it along with the SQL Server express ? For upgrade: refer http://www.vmware.com/pdf/view45_upgrade_guide.pdf To change vCenter server, followinf link may help http://communities.vmware.com/blogs/skg/2011/01/01/moving-svi-pool-across-vcenter-server-keeping-user-data-and-ownership
Microsoft SCCM goes well with ViewI Components and Linked lones. WSUS would be a simpler solution than this but do not have much management capabilities like SCCM But it is again OK to use with V... See more...
Microsoft SCCM goes well with ViewI Components and Linked lones. WSUS would be a simpler solution than this but do not have much management capabilities like SCCM But it is again OK to use with View because (and if) receiving Windows updates in a faster and automatic way is the only requirement. Combination of any of this with a periodic recompose (for distributing non microsoft patches and updates) should be the best suitable solution for your requirement
During the installation vCenter server, there is an option two choose a DSN which points to en external database or we can make use of the SQLExpress which is buntled with vCenter Server. This Do... See more...
During the installation vCenter server, there is an option two choose a DSN which points to en external database or we can make use of the SQLExpress which is buntled with vCenter Server. This Document describes installation of View Composer keeping database on the SQLExpress instance which is configured automatically during vCenter installation. Firstly login to the server where VMware vCenter Server is running. Install SQL Server management Studio Express.This software can be downloaded from Microsoft Website. Now open SQL Server Managemet Studio Express (MS SSMSE) login as below. Now object explorer for the database will be opened. Here you can create a new database but however, view composer does not support windows integrated authentication. Hence new user (SQL user ) need to be defined and map with a new database. Typically such SQL express instance should not have a production DB role. So here I am going to explain creating a new DB and mapping it to the inbuilt SQL admin account named "sa". In our case, by default the "sa" account will be in disabled mode. So as the first step we will enable the account and set a password. On the SQL object explorer  - Under 'Security' select the 'Logins'. Right click on 'sa' and go to properties. set password hereand make necessary password enforce policy if required (else uncheck). On the properties window left side click on the status, and grant the permission to connect to database and enable the login. refer below Right click on the server , go to properties and Change the authentication type to Mixed Modeas below. Restart the SQL Service Now the SA account has been enabled for the SQL instance. Disconnect the object explorer and connect to the SQL again using sa account Now the oject explorer is connected to database using sa credentials. as the final step we need to create a new database that need to use with composer. righ click on the database inventory , and select 'New Database' name the database , and click OK This will create new database, and since it si created using 'sa' account 'sa' will have complete permission on this DB. So no need to configure tha database permission and user mapping for this DB. If you are creating a new user other than 'sa' then the User should have the permissions and db ownership to the database. We are now done with the database configuration. the left out part is DSN configuration. From the control panel , open ODBC configuration and select system DSN. One DSN would be already available for virtual center. Click "Add" to create one for View Composer. Select 'SQL Native Client' and click finish. On the next page fill in the DSN name , Decription, and Server. Name can be of any choice. Description is optional and Server should be in the syndax <Hostname>\SQLEXP_VIM Click next, and choose the authentication and SQL authentication and provide sa credentials. In case new user is defined and mapped database , provide that here. Chage the default DB to the newly created database. proceed the wizard through next page with default options and finaly test the data source. The test should give a successful result as below. Click OK and finish teh wizard. This will return to the DSN configuration page of ODBC, and both VC and newly cretaed DSN will be lister here as below Now install View composer, and when it asks for databse, Give the DSN name as 'View Composer' and username as 'sa' and its password. Proceed the wizard and complete the installation
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 othe... See more...
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"
Traffic should be from client to Broker/AgentVM only, and defenitely not to the composer. Only Connection server and vCenter server has communication with View Composer, and used whenever there ... See more...
Traffic should be from client to Broker/AgentVM only, and defenitely not to the composer. Only Connection server and vCenter server has communication with View Composer, and used whenever there is a provisioning or maintenance activity on linked clones. But 100mbps uplink to vCenter server is not advisible specially if the VMnetwork in ESX also has uplink to the same 100mbps network. Because from view client traffic goes to VirtualMachine hosted in ESX servers through these uplinks, and can make network overhead in large number of Desktops are launched It is OK to use same SQL Express instance to create composer database, if it suffice to your deployment size. But need to create separate database for composer. Other thing to notice here is View Composer does not support Windows Integrated authentication so create a user in SQL. Create a DSN to the new database using the SQL username for installing view composer
Please verify the following. Go the the parent VM and revert to the snapshot which is used for linked clone. Edit Vm settings and check whether the network configuration enabled "Connected" and... See more...
Please verify the following. Go the the parent VM and revert to the snapshot which is used for linked clone. Edit Vm settings and check whether the network configuration enabled "Connected" and "Connect when Powering on" Please confirm if it is enabled for the parent VM snapshot state
Each linked clone should get unique ip-address irrespective of whether the the parent VM's ip-address is released or not. This has nothing to do with the issue what you had mentioned in the origi... See more...
Each linked clone should get unique ip-address irrespective of whether the the parent VM's ip-address is released or not. This has nothing to do with the issue what you had mentioned in the original post. Ensure some of the basic requirement by configuring following appropriately in the parent VM before taking the snapshot VM Network settings (in edit VM settings) Network configuration IP set to DHCP Network configuration DNS is set properly so that from clinet, and connection broker can reach fqdn (This can be Static for via DHCP) View agent and VMware tools are installed properly Snapshot taken after a clean shutdown for the Parent VM guest OS If you have the pools defined already which is in error state, you can take a new snapshot with above pre-requesites and perform a recompose to the new snapshot image
You dont need to do this for each linked clone. Instead, edit the parent VM settings and 'check' both the network options "Connected" and "Connect when powering on" Then take a new snapshot. Re... See more...
You dont need to do this for each linked clone. Instead, edit the parent VM settings and 'check' both the network options "Connected" and "Connect when powering on" Then take a new snapshot. Recompose to new snapshot will resolve the issue
A Refresh should not ask for reselecting network location because Refresh and  Recompose/Rebalance of assigned VMs will retain the MAC address. Please confirm "Select network location" is still ... See more...
A Refresh should not ask for reselecting network location because Refresh and  Recompose/Rebalance of assigned VMs will retain the MAC address. Please confirm "Select network location" is still prompts even after refresh
There is a way to do this. The details has been posted in my blog @ http://communities.vmware.com/blogs/skg
This is very much expected behaviour. Since this is a dedicated pool, User 1 will always get Desktop 1 and does not matter whether it is powered on or not. Please note that the 'spare value' is a... See more...
This is very much expected behaviour. Since this is a dedicated pool, User 1 will always get Desktop 1 and does not matter whether it is powered on or not. Please note that the 'spare value' is applicable only for unassigned desktops.
Upgrading existing vCenter is possible, Instead of moving pools across vCenter. Please refer to http://www.vmware.com/pdf/view45_upgrade_guide.pdf I dont think there is a easy way to migrate po... See more...
Upgrading existing vCenter is possible, Instead of moving pools across vCenter. Please refer to http://www.vmware.com/pdf/view45_upgrade_guide.pdf I dont think there is a easy way to migrate pools to a different vCenter in a few clicks (specifically if automated pools are defined at source vcenter server) After upgrading the vCenter Server, new ESX servers can be added and new clusters can be defined. Further existing pools can be edited to select new Cluster and datasore. After this, performing a rebalance will place the pool to the new resource pool/host cluster and datasore.
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: Avail... See more...
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.
Each persistent disk will have user ownership and it is defined in ADAM. If you want to back up entire pool configuration then the answer to Q1 is 'NO' You should have the ADAM and SVI backup fr... See more...
Each persistent disk will have user ownership and it is defined in ADAM. If you want to back up entire pool configuration then the answer to Q1 is 'NO' You should have the ADAM and SVI backup from View Server. If your setup consists SAN storage, which support file level backup then following will be one of the feasible option for backing up all persistent disks without loosing user ownership. Create the linked clone pool as a tiered-persistent-disk. This means, keep the Persistent Disks in a separate datastore. From the storage array take file level backup of that LUN. Each persistent disks will be mapped with the user as defined in ADAM, and persistent disks can be restored to the datastore-lun from storage array. Hope this clarifies Thanks Siva
You can use USB audio devices with the View USB redirection to achive bi-directional audio Regards Siva
Hi, Audio input is supported with dictation only, not VoIP or Voice/Video Chat support for PCoIP Regards Siva