Well, I've rebuilt everything - the sever to 2.10, rebuilt the provisioning machine, recreated the provisioning vmdk.....still nothing. Chilli, what do you do to fix the 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 - n...
See more...
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.
Well at least you're getting any signs of life, I get nothing - no Preparing box..... I've tried the log off and a reboot too. Neither seem to kick the agent into provision mode.
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...
See more...
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.