This post is more than 5 years old
6 Posts
0
5532
December 7th, 2010 13:00
Reprovisioning at log-off fails with ‘No action required’ message
Hi all,
My company is still in the process of deploying a vWorkspace (7.1) VDI solution in combination with Hyper-V R2 and SCVMM. We have come a long way and almost all functionality seems to be working fine however reprovisioning of a VDI desktop fails with the message: ‘No action required’.
Our setup: we have created a Windows 7 desktop group within vWorkspace. The Windows 7 VDI desktops are deployed using rapid provisioning and depend on Hyper-V differencing disks. We have configured the log-off action on the computer group to reprovision the computer after the user logs off. When we test this behavior the VDI desktop logs off successfully and vWorkspace intiates a reprovision action. This takes about a minute or so after which the reprovision action gives a task failure with the message ‘No action required’.
The strange thing is: if we manually reprovision a single VDI desktop within the same computer group reprovisioning works just fine and reprovisions the VDI desktop as expected! The only difference here is that we are able to specify the existing parent VHD disk as source for the differencing disk clone. This should however, according to the vWorkspace console, also be the default behavior if you configure reprovisioning as the default log-off action on the computer group level.
Has anyone seen similar behavior using vWorkspace and SCVMM/Hyper-V R2? Are we missing an additional configuration step? Or should the current configuration be sufficient?
Any thoughts on this one would be greatly appreciated!
Tom
No Events found!
duijstto
6 Posts
1
March 17th, 2011 12:00
This problem has been resolved by a hotfix available for vWorkspace 7.2. We had to upgrade our environment to vWorkspace 7.2 in order to be able to apply the hotfix. After installing the hotfix, reprovisioning at logoff works succesfully with SCVMM and Hyper-V R2.
dbolton
180 Posts
0
December 7th, 2010 14:00
Hi Tom,
I can confirm that I can also see this... With 7.1 and the 7.1MR1 update.
Can't say for sure if this will be sorted in 7.2 it was on my list of things to test.
I've been meaning to contact support about for a while now.
Cheers,
Dan.
duijstto
6 Posts
0
December 10th, 2010 09:00
Hi Dan,
Thanks for confirming this behaviour in your environment. I am currently talking to Quest support to solve this issue. If we manage to figure this one out, I will post the solution here.
Regards,
Tom