Sorry for bothering you, but I think this post is quite useless for the following reasons.
1) As far as I know, OEM SLP activation has nothing to do with retail keys, so it doesn't require an authentication server for which key can be or can't be accepted.
The Lenovo's key is checked by pkeyconfig.xrm-ms and tokens.dat M$ files already installed on OS system dir.
2) If M$ will blacklist this key he will need to update pkeyconfig.xrm-ms or tokens.dat, being an OEM key and a new one will surely comes out (experience should teach us that it's only a matter of time).
3) Some lenovo laptops and notebooks windows 7 certified have already been sold to some users and I can't imagine those people come back to shop for obtain a new one OEM key (which, of course, can be leaked as well as the first one).
4) Did you ever wonder why M$ has never blacklisted the "well-known" Asus SLP 2.0 keys or Dell ones (I'm referring to Windows Vista) when they came out ? Even with SP1 and SP2, those keys are still valid keys.
If Microsoft could blacklist those keys they, surely, have done for a long time, while in 2 years they have never been blacklisted them. I think M$ should spend a lot of his own resources to ban or blacklist any oem leaked code (expecially SLP OEM keys).
Don't forget that OEM SLP activation is a "legit" procedure as M$ can't determine if one user has bought for real his own notebook or laptop, instead of downloading RTM ISO and activating with OEM SLP key. It's very difficult to proof that.
China4Ever/My Digital Life Forums