by
Brian Madden
Peter Ghostine is one of my favorite guys in the desktop virtualization industry. Most recently he founded Provision Networks (which was bought a few years ago by Quest Software), and now he's the CTO of Quest's desktop virtualization division. Peter was the first guy who really pushed the combination of VDI and TS, and Provision Virtual Access Suite (now Quest vWorkspace) was the first product that seamlessly combined single app publishing from VDI and TS.
I've spent a lot of evenings with Peter, and I'm continuously blown away by how deep this dude understands the technology and how he can explain how stuff REALLY works. (Look how he influenced this protocol article I wrote in 2007.)
A few months ago, Peter approached me to be the independent expert for a webcast they're doing about their Quest vWorkspace product, and I gladly accepted. Our topic for today's webcast is "Simplifying Desktop Management - Merging the Physical and Virtual." We have an hour scheduled. I'll talk for the first 15 minutes about the whole physical versus virtual thing, and then Peter will talk for 15 minutes about vWorkspace. But the best part will be the final 30 minutes, where Peter and I will jointly answer your questions and/or discuss the topics and the industry-at-large. We're actually purposefully keeping our content short so we can have plenty of time for the discussion.
In the spirit of full disclosure, I'd like to point out that Quest is paying TechTarget (my employer) to host and promote this webcast. But I'm blogging about it here because I'm always excited about anything I do with Peter, and I think it will be a good time.
If you can't attend the webcast live, we'll forward the link to the archived recording (although that might take until tomorrow to be ready).
Register for the webcast here. It starts at 9:00 PDT, 12:00 noon EDT, and 16:00 GMT.
(Note: You must be logged in to post a comment.)
If you log in and nothing happens, delete your cookies from BrianMadden.com and try again. Sorry about that, but we had to make a one-time change to the cookie path when we migrated web servers.