I'm still confused with OA3. When I 1st start up a new notebook most of them reported as being not activated. If I then activate - it does. No internet connection...
Has anyone logged the address that is used to report keys and activate keys to microsoft I think this should be included in the specifics of your post .... If anyone is going to be successful at OEM activation the complete understanding and make a proof of concept like DAZ did it sounds like this is a must. You will need to point these servers to localhost and respond in the same fashion that m$ does. Obviously OEM activation tools of the trade would be needed but I am sure there is someone out there who would be willing to drop that bomb. As far as romholes and the bios being locked I am not afraid to solder a new bios on a motherboard even though I think it may be possible to unlock the "lock" via another method or maybe even a modchip solution for windows activation if needed people don't mind paying for windows activation the real issue is not the cost as the cost is fair but if someone wants to lets say change hardware in their PC they do not want to be subjected to extra activation headaches by windows they just want what they paid for to work and work without hassle. How do I know this you ask.... As a person who has repaired and built somewhere in the range of a hundred PC's and laptops I've talked to people and this is what there concerns are constantly and I tell them all they have to do is call and reactivate and majority of them would rather not deal with it to my amazement call it being lazy or whatever you would like I call it a customer wanting their product to work as advertised plain and simple nothing more or less.
Yes, despite the common belief, OA3 doesn't need to contact MS' server to activate on the first boot. OEM-DM key, injected in MSDM ACPI table, is hardware-specific by it's internal structure, thus when sppsvc detects the match between hardware hash and decoded info inside the key, it activates the OS off-line. The only way i can think of how it can be implemented is that the so-called secret number (see Windows 8 Product Key Decoding thread) in case of OEM-DM keys is generated out of hw-hash or something like that.
Not necessarily avoid - it's just that SLIC modification will be irrelevant for Windows 8. (SLIC will still be relevant for Windows 7.)
I did read this part. What I was asking is, if someone flashes a BIOS modded with SLIC to downgrade the OS, will the OA3 activation module be destroyed. For example, MSDM table or whatever. For me, it was not so clear.
Since this is so new, I think it is best if someone who has tried it, or is a technical expert, can clarify the issue.
As far as I know, the new Windows Server 2012 R2 aka Windows 8.1 Server will have the OA 2.3 by using the new ACPI SLIC table. However the Windows 8.1 client will still use the OA 3.0 and cannot perform the offline activation as the MSDM table will be used instead.
Hi there, I'm quite new here. This message is dedicated to all good and experienced guys, maybe also m$in$iders. I found something on a new notebook and I would like to know what it really is. With a Ggl help I was able to tell that the files are not publicly known, so I will not tell their names here. But it has definitely to do something with 0A3.0 activation. Looks like one manufacturer (the real one which manufactures the notebooks for their big customers which then sells them to retail) forgot to clean the Win8 installation and left some interesting files here (including some less interesting - some files can contain persnl info about some employees and I don't really want to hurt anyone). Since I still don't know who is here the master boss I would like to ask you who can I send those files to (for inspection). It can be nothing, maybe it's all well-known for you, or it can be something better than nothing, just for educational purposes or similar. I don't think it's usefull for mimicking the 0A3 activation, but I'm not really expert on this.