ymagalif's Posts

Liora, Best practice with VDI is to try to use E-mail archiving solutions for your older email (like Symantec Enterprise Vault), so that the size of your mailbox is smaller and therefore searching is faster. Older email can be searched from the archiving solution's online interface, which is always centrally available outside of the virtual desktop. Also best practice is to urge web based email adoption (OWA). However, if that is not possible, here is something you could try: If using a replication based profile solution like VMware's Persona Management or other third-party solutions, you can set the Windows search index location to be replicated to the user's profile. Thus, the user will always get the correct profile, even in a floating/non-persistent scenario. Windows search index location: http://www.edbsearch.com/location.html I have not personally tried doing it this way for Windows Search index, but I believe it should work. Sincerely, Yury Magalif

Mr. Beatnick, I always disable "Stop Provisioning on Error." Like you said, you don't want the whole provisioning run to stop just because of 1 error. Most of the time if there are errors, they exist in some desktops, but not all. Thus, enough good desktops get generated to get going. You do have to be aware that it wastes resources if there are many faulty desktops. But the benefits of disabling outweigh the disadvantages. Sincerely, Yury Magalif

vcpguy, Here is a standard on SQL (Page 3): http://www.isbe.state.il.us/ILDS/pdf/SQL_server_standards.pdf "it is sometimes a good idea to prefix your table names with some characters that group your tables together. For example, for a healthcare application you might give your tables an "Hc" prefix so that all of the tables for that application would appear in alphabetized lists together. The last kind of prefix that is  acceptable is one that allows you to group logical units of tables. A plausible example could entail a large application (30 to 40+ tables) that handled both Payroll and Benefits data. You could prefix the tables dealing with payroll with a "Pay" or "Prl" prefix and give the tables dealing with benefits data a "Ben" or "Bfts" prefix. The goal of both this prefix and the aforementioned shared schema/database prefix is to allow you to group specific tables together alphabetically in lists and distinguish them from unrelated tables." My theory was just a theory, but due to the above there is some concrete usage of SQL table prefixes in the real world. Sincerely, Yury Magalif

vcpguy, I believe we create a table prefix because if you were to use SQL queries and search the actual database, you would be able to search for the prefix and find all Event Log entries. However, most people won't search the database by using SQL queries. So an alternate reason could exist. Sincerely, Yury Magalif

David, VMware View does not support a Linux agent inside your desktop, only Windows. There is a discussion about it here, and you can sign a petition to make it happen: vmware view 5 support for linux/Debian guest? Sincerely, Yury Magalif