And one more thing: NO! Rearming do not change your Installation ID. If you don't know how to find your Installation ID, use the following command: Code: cscript //nologo "%programfiles%\Microsoft Office\Office14\ospp.vbs" /dinstid
Hehe you guys are awesome. I just bought a Dell laptop that comes with 2010 Starter. Can I use this Toolkit to unlock Office 2010 Pro?
My Dell laptop is being built should have it in a week or two at the latest. Has this worked for others with Starter on the disk?
Yeah, destroying License Config (where CMID is stored) forces it to make a new one. As far as I am aware that OID is for phone activation. Oddly enough, I was adding that to Check Activation Status before you mentioned it. I believe it is the ID you see when you do phone activation, and I believe the /actcid: command lets you enter a phone confirmation. I'll test that with a legit MSDN key.
letsgoawayhell this is for my second pc: with zwt keygen - persistent 0x8000700D error (does not work for 20 tries) modded keygen - worked on first try. CMID: Code: Microsoft (R) Windows Script Host Version 5.8 Copyright (C) Microsoft Corporation. All rights reserved. ---Processing-------------------------- --------------------------------------- Client Machine ID (CMID): 0b67d4d5-21e7-44fe-817b-e412a3d61304 --------------------------------------- ---Exiting----------------------------- actually I can rearm eachtime and give you another CMID.. but the CMID I posted so far are from different machines that has the persistent 0x8000700D error (both machines installed with x64 windows 7 + x64 office).
Yes, this is the ID that is used for phone activation. Do you know the exact location where CMID is stored?
Working on a phone activator that will save your results. As long as your Install ID remains the same, you can reuse that phone activation.
CODYQX4 for phone activation users need a Retail key (MAK key also work) and it's not something new, I wrote a guide on another forum. but it's a nice addition to your toolkit. (/dinstid to show the user the INID to type on the given phone number (base on his country), then give the user option to type the confirmationid, and use /actcid:confirmationid to activate, also offer the user option to backup the activation- tokens.dat+reg keys).
Well yeah I know it's Retail/MAK, and the way you describe is very similar to how it works. It's just a new means to save activation that I find nicer than a Backup, and it means keys that are dead online but still work over the phone come back into play. I wish we could keygen the CID, as I can do everything full-auto and activate anything if we could.
Can someone willing to do a reformat twice check something for me? Nuke your PC, install Office 2010 Pro Plus Retail, using the key you see in the toolkit by choosing Pro Plus Retail check (It ends in BBKQ8). Then run the command cscript ospp.vbs /dinstid and save the results somewhere safe. Reformat your PC and install the same copy of Office 2010 Pro Plus Retail with the same key, and run cscript ospp.vbs /dinstid again, saving its results. Does the Installation ID change? Show me both command's results. Don't use a VM because VM's seem to be more tolerant sometimes. The reason for this is I want to know if this ID changes after a reformat. I am pretty sure a reinstall of just office retains it, though I went through hell reinstalling so who knows if I messed things up. I basically want to see if this ID changes, because if it doesn't, then your Phone Activation ID persists across OS Reinstalls, meaning you can reactivate with it. If it does change, then whatever is resposible for the change is probably why normal backups don't work after a OS reinstall.
KMS CMID Explained - Part 1 Hey guys, I said that I'll post some info about KMS CMID before. Here it is the first part: When Office wants to use KMS activation it needs an ID called KMS CMID(Clien Machine IDentifier) to contact KMS Host and request for activation with it. But KMS CMID is not being generated during Office installation, that means if you install an Office on you PC and you use: Code: cscript //nologo "%ProgramFiles%\Microsoft Office\Office14\OSPP.VBS" /dcmid right after its installation, you'll get: Code: C:\>cscript //nologo "%ProgramFiles%\Microsoft Office\Office14\OSPP.VBS" /dcmid ---Processing-------------------------- --------------------------------------- Client Machine ID (CMID): Not found. --------------------------------------- ---Exiting----------------------------- Instead, it is generated when necessary. That is, when you try to activate your office using KMSCLIENT channel and that CMID is retained in your office licensing store thereafter. But the good thing is that CMID is not generated based on your hardware and seems to be - to some degree - random. This is very very good news because we can use this feature to change our CMID without a rearm. The procedure is as follows: right after you istalled you Office, backup office licensing store. Then issue an activation command, Office will generate a CMID for you. If you like this CMID keep it otherwise restore office licensing store to its previous state and issue another activation request, you'll get a NEW CMID. In order to further clarify the procedure I put up two simple batch file that do the job for you. Stay tuned as more info on CMID is gonna get revealed. *** Note: Office licensing store = Office tokens and OSPP registry keys Note 2: These are 2 simple batch files to help better understand the above mentioned procedure. DO NOT RELY ON THEM. Just use them to clarify things for yourself. THEY ARE NOT MEANT FOR EXTENSIVE USAGE.
i'm due for a reformat possibly in a few days or so, because i have a trojan that keeps maifesting itself again like a poltergeist