A feature we are realy missing is the ability to let a user reset a VM in case of a crash. A VM can crash for various reasons:
Network / IP problems
Problems with our Novell client
Bluescreen (yes we still use XP)
Memory leak / full
Termserv process hanging
The failover feature will not work for us because it takes a very long time for clients to login on a 'fresh' machine. This is because a lot of software is being installed the first time (Novell Zenworks). We use Windows XP with persistent VDI. I know this is not the best combination, we are working on a better solution, but that is how it is right now.
I hope Quest is working on a reboot feature. VMware view already has this implemented.
Anyway, I was wondering if we could do this with somekind of vWorkspace powecli script?
We could publish an application that runs on a terminalserver, get the user id, find out which VDI machine belongs to that user and then launch a "Invoke-QVWComputerAction" command to reboot the VM.
The biggest challenge would we to find out which user is requesting the reboot, and relating the user to the persistant VM it belongs to.
I'm affraid it's not possible to share this the way it works right now. All kind of things are hardcoded, like paths and sql credentials. It's really not that difficult. I could explain it here if interested.
rene11
1 Rookie
•
74 Posts
158
0
Posted February 14th, 2011 14:00
We've found a nice way to do this:
Works great! Now they don't have to call the supportdesk if their machine crashed.