If you are using ADBA or KMS activation methods, two activation transactions are still required, but ADBA/KMS activation is typically automatic and transparent to the end-user while connected to your on-premises ADBA/KMS infrastructure. If you are using MAK activation methods, this requires two activation transactions.
In such a situation, the physical Windows installation and the virtual Windows installation are regarded as completely different machines, therefore two activations must occur. So, if I understand correctly, you are effectively installing Windows twice upon each Mac?Įach installation (once via bootcamp, installed on the Mac hardware, and, again via parallels on the virtual hardware), is independent of the other, and each has a different hardware identity. Set up parallels on Mac and then it requests for product key again. Help will be greatly appreciated since we are currently stuck in this situation. Kindly advise the method of using parallel such that we are not required to enter product key twice or at least our VLSC seat count does not increase. I have read multiple posts about this but couldn't find one recommended solution for this. Set up parallel on Mac and then it requests for parallel key again. Set up bootcamp partition and install windows. Wanted to know what is the best way to apply the windows license key when there parallels in the scenario. This number goes up when the user is switching between parallels and the bootcamp.
It is using more than one VLSC seat forĮach mac. We have been experiencing issues with windows licensing. We are a software services firm and am the IT manager managing our infrastructure.We have recently switched to Mac and been using windows with parallels on them.
0 kommentar(er)
