the script needs to be run from an elevated command prompt with these files in the same folder: tokens.dat; pkeyconfig-office.xrm-ms. It will set the permissions and replace the MS installed files with the ones in the folder.
In the folder that I downloaded from the hotfile link, there is a, "activate" file, "tokens.dat" file, & a "pkeyconfig-office" file. Are these the files you are referring to? If not, where can I find these files?
this happens if you have "hide file extensions for known file types" enabled. yes, same files that I listed above.
It says "Your installation cannot be activated because you have activated up to the limit of your Multiple Activation Key. Contact your administrator for further help." Is there another method to activate it?
You need to change the key in the script to another key from the public beta. Maybe it's still possible to register for the public beta and get a key.
PLEASE HELP ... i can not activate office 2010 Build 4734.1000 with ActivateOffice2010beta >activate.cmd. I got error message " microsoft office professional Plus 2010 cannot verify the license for this product." I tried to change key in activate.cmd with another beta key. still got the message error. and i tried to copy "tokens.dat" file, & a "pkeyconfig-office" file to each folder manually and still got error. Or maybe because i got Update for Microsoft Office 2010 File Validation - Beta (KB976133), 32-Bit Edition.. so i cannot activate office 2010 with ActivateOffice2010beta. when i tried to uninstall this update, there is no KB976133 in uninstall update.
as soloar pointed out in another thread, there is something else going on with some people's activation files that screws up activation. I was successfully applying this to one system, no luck on another. the thing is that I uninstalled everything, installed public beta, obtained a NEW key and didn't even work for the public beta with a legit key! some of the activation files from the new installation were still there even after uninstalling it. files from the working system did not work on the non-working system... cleaning registry keys from office14 or files on the PC beforehand didn't work either. after several trials, I finally got it to work with a months old public beta key I had still lying around, but only after two or three trials. the public beta first complained about wrong key, then accepted it and finally installed something before it said it finished. Only after that I was able to copy the token files and uninstall and install rtm and use the copied token files. now it's working. beyond me, only suspicion is that there are some activation files I missed the first time or screwed them up. good luck
With a June date for retail availability and some reports of April for RTM (couple months before retail is typical), it's probably a good month, month and a half, before they'd bother to finalize anything. Better to spend the time swatting bugs in these endlessly complex programs. Question for anyone: Has anyone tried using the two files in the ZIP file with the script rather than using your OWN files generated from a successful Beta 2 activation? I seem to recall from the last thread that this worked, but I took the smoother route of using my own files and the same key I used for activation (a well-known public one). Just curious in case I need to recommend this to someone. It would be a lot easier if they could skip Beta 2, and only bother with it as a last resort.
i didnt want to do it but im redownloading beta 2 and i have my product keys and i will give the token.dat trick a try. uninstalling rtm 2010 now ill let you know if it works later on when its done.