keropinvestments.blogg.se

1. #Windows cant activate with this product key 0xc004d302 for windows 10#
2. #Windows cant activate with this product key 0xc004d302 windows 10#

We rebooted the targets and once they came back, got the same issue which is not generating the CMID. Now we were able to get unique CMID for each streamed targets. We were not getting the CMID for each streamed targets, so we ran slmgr /ato and cscript ospp.vbs /act in the read only mode on each streamed VMs.

#Windows cant activate with this product key 0xc004d302 windows 10#

In this scenario we rearmed only office 2013 and not windows 10 Ent OS. In test 3 ( In private mode rearmed only office 2013 ) Volume Activation expiration period count – count decrements, after 180 days we may have to rearm In this scenario we were getting same CMID for each streamed targets In test 2 ( In Private mode did not rearm both windows 10 Ent and office 2013) Windows rearm count is decrementing as we have rearmed windows, but the rearm count was increased from 3 to 1000. Volume Activation expiration period count – volume activation period is not decrementing, remains as 180 days. In test 1 ( In private mode rearmed only windows 10 Ent (wasn’t able to rearm office 2013 as previous windows rearm changed the permission in Machine Keys folder )īoth windows 10 Ent and Office 2013 were activated and we were getting unique CMID for each streamed targets Here are the steps (4 different tests) i have tried so far. (c:\ProgramData\Microsoft\Crypto\RSA\MachineKeys )ĭescription: The Security processor reported that the trusted data store was rearmed." On a computer running windows non-core edition, run 'slui.exe 0x2a 0xC004D302' to display the error text Passing the SKU ID is necessary if you are relying on an activation to permit an additional rearm" "There was an error when trying to rearm office, You can try passing the SKU ID as parameter.

#Windows cant activate with this product key 0xc004d302 for windows 10#

But is this the right procedure for windows 10 and office 2013 for prep.KMS for PVS ? without rearming office if i shutdown and promote the vdisk to standard by changing the MIcrosoft volume license to KMS all is working well and getting unique CMID for windows and office. Specifically in this case, if i rearm windows 10 first and then tried to rearm office 2013 its not allowing me to rearm office. CMIDs are unique.But we need to follow CTX128276 for prep office and windows for PVS.