Can anyone provide any experience on this ?
First of all I would highly suggest upgrading to a newer version, 2.10 is very old and has some bugs in it. Try going for 2.15 first if your reluctant to go to 2.16.
Can i reboot the Windows 2012 box hosting Appvolumes Manager 2.10. ( Standalone). Or do i have to detach all Appstacks first ?
Yes you can reboot Appvolumes manager even if it is a standalone machine, you don't need to detach first although I would not suggest using just a single Appvolumes server. Thing is that users logging in wont get their appstacks attached (not the biggest of your issues, just relog after Appvolumes manager is up) but if a user logs off and your Appvolumes manager is down it wont reconfigure that machine so the appstacks are still attached. You would need to manually reconfigure those machines. If it is just a few it might be an option.
If i do reboot Appvolumes Manager , what is the effect on currently attached appstacks.
They stay attached.
and Lastly when Appvolumes Services start. will it sync and discover all attached Appstacks ?
No, not really. Normally twice a day Appvolumes checks for stale records and will detach the ones it find where a machine has an appstack attached but no user logged in.
Still, I would not suggest rebooting a single Appvolumes server during production..Either create a second one so you do have it load balanced or do this during off hours.
Exactly what i needed. Thanks @Ray_handels