Comments on: How Hyper-V can seem to lose your data http://www.itwriting.com/blog/1227-how-hyper-v-can-seem-to-lose-your-data.html Tech writing blog Sun, 12 Feb 2012 21:04:12 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Glen http://www.itwriting.com/blog/1227-how-hyper-v-can-seem-to-lose-your-data.html/comment-page-1#comment-209967 Glen Thu, 01 Jul 2010 21:58:20 +0000 http://www.itwriting.com/blog/1227-how-hyper-v-can-seem-to-lose-your-data.html#comment-209967 For the broken trust issue, you don't need to drop it from the domain and re-join it, you can simply run this command at the command prompt of the now untrusted workstation: netdom resetpwd /server:YourDcName /userd:YourDomainName\administrator /passwordd:* For the broken trust issue, you don’t need to drop it from the domain and re-join it, you can simply run this command at the command prompt of the now untrusted workstation: netdom resetpwd /server:YourDcName /userd:YourDomainName\administrator /passwordd:*

]]> By: E http://www.itwriting.com/blog/1227-how-hyper-v-can-seem-to-lose-your-data.html/comment-page-1#comment-168251 E Wed, 03 Mar 2010 01:23:51 +0000 http://www.itwriting.com/blog/1227-how-hyper-v-can-seem-to-lose-your-data.html#comment-168251 Applied a 3 month old VM snapshot today, resulting in broken domain trust. Disabling the machine account in ADS & rejoining the VM worked as advertised. Amateurs such as myself may find that coercing the OK button of the VM's Computer Name dialog into an enabled state when "joining the same domain" will seem impossible until one remembers the FQN & NETBIOS domain names are different strings. Applied a 3 month old VM snapshot today, resulting in broken domain trust. Disabling the machine account in ADS & rejoining the VM worked as advertised.

Amateurs such as myself may find that coercing the OK button of the VM’s Computer Name dialog into an enabled state when “joining the same domain” will seem impossible until one remembers the FQN & NETBIOS domain names are different strings.

]]> By: Tim Anderson http://www.itwriting.com/blog/1227-how-hyper-v-can-seem-to-lose-your-data.html/comment-page-1#comment-156852 Tim Anderson Fri, 08 Jan 2010 08:33:32 +0000 http://www.itwriting.com/blog/1227-how-hyper-v-can-seem-to-lose-your-data.html#comment-156852 Thanks for the tip; I wonder if this generally works when the trust relationship breaks. Tim Thanks for the tip; I wonder if this generally works when the trust relationship breaks.

Tim

]]> By: Art Vandelay http://www.itwriting.com/blog/1227-how-hyper-v-can-seem-to-lose-your-data.html/comment-page-1#comment-156834 Art Vandelay Fri, 08 Jan 2010 02:32:25 +0000 http://www.itwriting.com/blog/1227-how-hyper-v-can-seem-to-lose-your-data.html#comment-156834 I had a standalone SQL/MOSS VM running Server 2008 (lets call it the Test1 VM) that had snapshots I would roll back to occasionally (used for testing). After a month or so, the rollback was too old for my DC and the trust relationship broke. I resolved it by going to the DC (Windows Server 2008-based) and under AD Users and Computers saying "Disable Account" for the Test1 machine on the domain. With the Test1 machine still on the network (and logged into it as local admin) I went to join it to the same domain it was already joined to (when challenged - I provided my domain admin creds). This "rejoined" the VM to the domain and flipped the "disabled" bit for the machine account to "enabled". I did NOT unjoin the machine or place it in workgroup. I believe this approach saved me from pulling down new SIDs and royally screwing up SharePoint. With the trust re-established I took a new baseline VM snapshot which should be good for another few months... I had a standalone SQL/MOSS VM running Server 2008 (lets call it the Test1 VM) that had snapshots I would roll back to occasionally (used for testing). After a month or so, the rollback was too old for my DC and the trust relationship broke. I resolved it by going to the DC (Windows Server 2008-based) and under AD Users and Computers saying “Disable Account” for the Test1 machine on the domain. With the Test1 machine still on the network (and logged into it as local admin) I went to join it to the same domain it was already joined to (when challenged – I provided my domain admin creds). This “rejoined” the VM to the domain and flipped the “disabled” bit for the machine account to “enabled”. I did NOT unjoin the machine or place it in workgroup. I believe this approach saved me from pulling down new SIDs and royally screwing up SharePoint. With the trust re-established I took a new baseline VM snapshot which should be good for another few months…

]]> By: tim http://www.itwriting.com/blog/1227-how-hyper-v-can-seem-to-lose-your-data.html/comment-page-1#comment-122068 tim Thu, 26 Feb 2009 15:42:21 +0000 http://www.itwriting.com/blog/1227-how-hyper-v-can-seem-to-lose-your-data.html#comment-122068 Hi Greg I'm saying that I needn't have deleted the computer account. If I'd realised what had happened, I could just have merged the differencing files and it would have been fine. This is not normal though. So your second statement is true as well. There wasn't really a problem with SQL and SharePoint - the VM had just reverted to its state at an earlier date, without being asked. Tim Hi Greg

I’m saying that I needn’t have deleted the computer account. If I’d realised what had happened, I could just have merged the differencing files and it would have been fine.

This is not normal though. So your second statement is true as well.

There wasn’t really a problem with SQL and SharePoint – the VM had just reverted to its state at an earlier date, without being asked.

Tim

]]> By: Greg http://www.itwriting.com/blog/1227-how-hyper-v-can-seem-to-lose-your-data.html/comment-page-1#comment-122066 Greg Thu, 26 Feb 2009 15:35:46 +0000 http://www.itwriting.com/blog/1227-how-hyper-v-can-seem-to-lose-your-data.html#comment-122066 Tim, I'm having a discussion with a colleague and we are wondering... Are you saying that "in doing the wrong thing" that you should have first merged the differencing files and therefore you would not have needed to rejoin the domain and also SharePoint and SQL would've been intact and that this is normal? Or, are you saying "what had really happened" is that Hyper V truly forgot about the differencing files upon the initial boot which produced the "The trust relationship between this workstation and the primary domain failed" and the problems with SQL and SharePoint? Tim,

I’m having a discussion with a colleague and we are wondering…

Are you saying that “in doing the wrong thing” that you should have first merged the differencing files and therefore you would not have needed to rejoin the domain and also SharePoint and SQL would’ve been intact and that this is normal?

Or, are you saying “what had really happened” is that Hyper V truly forgot about the differencing files upon the initial boot which produced the “The trust relationship between this workstation and the primary domain failed” and the problems with SQL and SharePoint?

]]>