I have a problem I've never seen before. When I go to provision an AppStack, I assign my clean machine as the provisioning machine. It attaches the drive but the agent never comes up telling me I'm in provisioning mode..... It's all very strange. I'm running 2.10, and the provisioning machine is windows 7 x64 sp1. I've put the clean machine in the same network and cluster as my server just to make sure there's no firewall in the way. Also, I've uninstalled and reinstalled the AppVolumes server.
Any ideas are welcome.
I have seen something similar to this, in that the first 'preparing to provision' box appears, but not the 'You are now provisioning' box.
I log off and back on to the machine when this happens and I see the 'You are provisioning' box as normal.
And the appstack is attached to the packaging machine?? What happens if you do a net stop svservice and net stop svdriver and start the services again after that?
And is this a newly created appstack or an updated one?
Try shutting down your provisioning box, and trying to provision a stack to it.
If the app volumes manager doesn't report the machine unavailable then you've found your issue 🙂
I can confirm that the AppStack is attaching to the vm - I see that in vCenter and I also see it in disk management. I've tried stopping and starting the service after attaching the AppStack - nothin'. It's a new AppStack. I'll try to create a new vmdk in the template directory and see what happens. And I know I'm not confused as to what my provisioning machine is - when it's off, it's unavailable, when it's on it is.
Provision a virtual machine that has never had any AppStacks assigned to it. If AppStacks are assigned to the virtual machine, or the virtual machine has been used for provisioning before, the virtual machine should be set back to the clean snapshot before provisioning a new AppStack.