VDI in a box Sent from my slightly schizophrenic, but rather cool, BlackBerry Android From: [email protected] Sent: 8 June 2017 8:58 p.m. To: [email protected] Reply to: [email protected] Subject: [NTSysADM] RE: VMware to Hyper-V transition
You left out Emergent Online, then Provision Networks, then Quest, then Dell and Wyse is in there somewhere. Webster From: [email protected] [mailto:[email protected]] On Behalf Of Melvin Backus Sent: Thursday, June 8, 2017 12:01 PM To: [email protected] Subject: [NTSysADM] RE: VMware to Hyper-V transition vWorkspace, formerly Quest, then Dell, and now Quest again. :) -- There are 10 kinds of people in the world... those who understand binary and those who don't. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Webster Sent: Thursday, June 8, 2017 11:56 AM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] RE: VMware to Hyper-V transition What is your VDI solution? Webster From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Melvin Backus Sent: Thursday, June 8, 2017 10:48 AM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] VMware to Hyper-V transition Anyone out there proficient in both VMware and Hyper-V who can point me at any good docs on doing a migration? I’ve got a specific application I’m considering moving to Hyper-V to help stretch the life of our VDI solution. We will eventually have to change I’m sure, but migrating it may be a stopgap and I’ve got the extra hardware at the moment. In particular I’m weak on the networking aspects of Hyper-V. -------------------- Service Desk | 404-497-1599 | https://servicedesk.byers.com<https://servicedesk.byers.com/> Melvin Backus | Sr. Systems Engineer | Byers Engineering Company | 404.497.1565 -- There are 10 kinds of people in the world... those who understand binary and those who don't.
