Here's what happened to me. Was happily running VMWare 3.0.2 on Macbook Pro. Had Win7 Enterprise installed as a bootcamp partition and would open that up on the Mac using Fusion - basically allowed me to use Win7 for Outlook and MS Project while doing everything else on the Mac.
Saw an enticing notice that Fusion 3.1 was now available. Downloaded, installed and updated VMWare tools on the bootcamp partition. All of a sudden Win7 started telling me that the activation was no longer valid and that I needed to reactivate. Tried everything under the sun in order to try and get it activated to no avail (restarts, going to microsoft.com/genuine, using slmgr.vbs, grabbing the key using Produkey, etc.). The weird/good thing was that whenever I booted natively into Win7 it was fine. It was whenever I booted into Win7 using fusion on the Mac side that it wasn't valid.
Finally had to call in the IT guy at work and he figured it out (go Mike!). Basically two combined fixes:
a) VMWare networking sometimes gets confused (tell me about it). He ran the following in the terminal to reset it:
sudo /Library/Application\ Support/VMware\ Fusion/boot.sh --restart
b) This was probably the key - he changed the perferences in VMWare such that before the Fusion image loaded that it was set to use Bridged networking from the beginning. I had it set to NAT and then tried switching it to Bridged after launch, but that probably wasn't good enough. Once he did that the Fusion Win7 instance was able to find the KMS server inside the firewall and all was well.
Glad that only burned a whole day from my life...arg...
No comments:
Post a Comment