Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

R

rene11

1 Rookie

 • 

74 Posts

38430

January 18th, 2011 06:00

Script to let user reboot VDI machine?

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.

Any help would be appreciated!

rene11

1 Rookie

 • 

74 Posts

February 14th, 2011 14:00

We've found a nice way to do this:

  • We published a special 'reset' application on a terminalserver.
  • Users have access to this application.
  • This application gets the current user that is logged in and searches the vWorkspace DB for the corresponding persistant machine.
  • Using powershell it resets the machine. The user can only reset his own machine.

Works great! Now they don't have to call the supportdesk if their machine crashed.

reset.png

rmack1

1 Rookie

 • 

48 Posts

February 15th, 2011 02:00

Nice.

Any chance of getting you to share it with the community. I could offer some good Australian beer or wine :-)

regards,

Rick

rene11

1 Rookie

 • 

74 Posts

February 15th, 2011 18:00

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.

However, I just saw another post that explains how to make a self service web interface. Might be interesting.
http://en.community.dell.com/techcenter/virtualization/vworkspace/b/vworkspace-blog/archive/2011/02/14/39-vworkspace-self-service-39-using-a-simple-asp-net-web-portal-with-quest-vworkspace-powershell-module

Was this post helpful?

View All

No Events found!

Top