Fix for EUCA-5921: Windows computer rename issue

This fix addresses the use case where users want to rename instances
after they have been launched on Eucalyptus.  After changing the
computer name in a Windows instance, the instance needs to be rebooted
for the rename to take effect.  The fix makes sure that it checks to see
if the instance was just launched or not.  This fix should work with
instances bound to Active Directory as well, since Active Directory
relies on the SID and not the computer name of the computer object.
Special thanks to Deependra Shekhawat for helping with the solution and
testing of this patch.
Merge pull request #5 from hspencer77/computer-rename-fix

Fix for EUCA-5921: Windows computer rename issue