I don't have the activate.cmd file, since I've been running the lines manually with various keys. I did backup those two files before uninstalling B2, so I did do essentially the same as you describe, but they fared no better than the ones from the RAR. That makes sense, since people have been getting the ones in the RAR to work. Does your /dstatus output differ from mine? Apart from the key anyway? I'm not sure what a working system is supposed to look like. It would help to know which key was in effect when the two files were created. That might work.
I can try that script, but it's all the stuff I did manually. I can also try uninstalling the new build and putting on the old one, but by backing up my working files before installing, I've effectively already done it. Besides, we don't need to be using the key which matches the one used when the files were created. He said any old public key would do (i.e. one that's already been used). I think as far as /dstatus is concerned, I'm already activated by virtue of /act (you can confirm that by comparing your /dstatus against mine). The trick is in getting the apps to stop asking me for the key and let me actually use them. That's proven incredibly difficult.
I tried using the script. It works and says that product was successfully activated at the end, but when I then run any office application it asks for a key. It won't take neither the key that was in the activate.cmd nor the official key from Beta 1 I also tried placing my 2 files (tokens and the other one) from my Beta 1 installation into the activate.cmd dir, but that did not work as well. AND replacing the key in activate.cmd with my Beta 1 key, that did not help too. Any ideas? P.S. I haven't tried the original manual method, but I will today in the evening. P.P.S. And yes, I did run it as administrator.
I have sth to ask, does it work permanently? Is it still having an expiry day? Is it the same with activating by using the license MAK given by MS? I think it's better to wait for the OEM edition, as it must be fully activated...
ofc it gives you expiry date. Even if this build is so close to RTM that they actualy are using license files from RTM, overwriting those files with public beta license files gives you public beta expiry date. But not like it matters, that date is sometimes in october, final version will be released long before... This activation is just so you dont need to rearm every 25 days (or maybe its 30 here as well as with windows, but i think its 25 since its volume license).
its still beta, but i think they are kinda on same level of development that they where with windows 7 with 72xx builds.
Unfortunately, that's not the problem. All commands show perfect success (product key installation successful, product activation successful, licensed), the two files are in place and the cache deleted, but then any Office app demands a key. There's another aspect to this for some systems.
Worked flawlessly here. I just had to change the directory of the scrip, since my office folder is "Microsoft Office 2010". Office is activated. Thanks SoLoR!
I had Office 2010 Tech Preview, uninstalled and installed Beta. Uninstalled Beta, installed build 4730, ran script. Besides, I've had Office 2007 also installed during all this.