IT can be easy
Xangati is the newest sponsor for this blog. I thank them for giving me the cash to purchase Layer 3 switches that have support sFlow so I can do futher testing with ThinApp streaming and load testing. They’re great community supporters and fans of independent blogging. Once I get my NetApp storage up and running I hope to get down to business.
Check them out for yourself:
Tech Field Day – Virtualization Field Day
If you have to run persistent desktops and your user base is transient or not needing access to their desktops all the time, 5.0.1 was a good release for you. You now have option to let them start where there they left off and potentially squeeze some more users onto your infrastructure. Below is taken from the release notes for View 5.0.1.
Previously, you could configure dedicated View desktops to be suspended if users had logged out but not if they had disconnected without logging out. This issue has been resolved so that you can now configure dedicated View desktops to be suspended when users disconnect. This functionality helps to conserve resources. To enable “Suspend on disconnect”:
Open ADSI Edit.
In the console tree, click ADSI Edit.
From the Action menu, select “Connect to.”
In the “Select or type a domain or server ” field, specify the server name as localhost:389.
Under “Connection point,” click “Select or type a distinguished name or naming context “, and then specify the distinguished name as DC=vdi,DC=vmware,DC=int and click OK.
The ADAM ADSI Edit main window appears.
Expand the ADAM ADSI tree, and expand OU=Properties.
Select OU=Global and select CN=Common in the right pane.
Select Action > Properties, and under the pae-NameValuePair attribute, add new entry suspendOnDisconnect=1.
Restart View Connection Server.
NOTE: Beware of your storage footprint with VMSS file. VDI Host Memory will equal the same size of VMSS file.
I will be giving up my role as VMware User Group Leader for Saskatoon. I am going to try a vBeers in Lloydminster and see what the interest would be to have a User Group here in Lloydminster. I would like to move it a closer to home and do more networking in my local area. I am thinking starting something in Lloydmisnter will allow for more focus on local industries in the area like Oil and Gas. I hope that there will be enough interest in Lloydminster to get one off the ground. I may have to broaden the appeal of it but I am thinking it should pan out.
I’ve had to drive 2.5 hours there and back for meetings and usually take a whole or part day off work to attend plus hotel costs. It wasn’t a problem in the past but a new job and twin girls make it a little harder to do. The holiday season has reinstated the importance of family and spending the most time you can with them.
I still hope to be involved with the user groups because they do provide a lot of value to the community. Let me know in the mean time if I can help out with anything else for my lair in Lloydminster. I would still be willing to speak if you have a topic that I can address.
It was great to meet and talk to all the people in the Saskatoon User Group. I hope we can stay in touch.
Thanks for the great experience.
Mid September Teradici released new firmware for their zero clients and on October 1st released an update to their free management console.
Teradici Firmware 3.4.1
Biggest New Feature:
Added Support for pre-session user authentication using .NET smart cards
Biggest fix: Fixed a memory leak from 3.4 that caused the network card to become non-responsive.
PCoIP Management Console 1.6
Biggest New Feature: The management console using the hostname instead of the default name is the biggest one for me. Teradici introduced Remote Power Down feature but I think this will confuse more users than it’s worth.
Biggest Fix: Fixed an issue where AutoConfig could not find a correct rule when multiple IP matches found
PCoIP_Management_Console_Release_Notes
NOTE: You can support up to 2000 devices per management console
Disable build to lossless for WAN or heavy contrainsted wireless areas. This can be done via GPO’s that are placed on the connection server.
More information: http://blogs.vmware.com/euc/2011/09/vmware-view-5-pcoip-build-to-lossless-.html
