Hello, we have software assurance, so MAK and KMS are available for O2013. I cannot use KMS server (there are reasons for now). So I have to use MAK. I know that it is possible later on to convert MAK to KMS. I found topic about ADBA. But missing few points from the description after my 2 questions. Can I use KMS key for use with Volume Activation Tool without actually having KMS installed? At the end it says just 180 days activation. What will happen then? From: -------Prior to Office 2013, IT had to rely on Multiple Activation Key (MAK) or Key Management Service (KMS) activation. These processes were generally more complex than ADBA. Little has changed with either MAK or KMS in Office 2013. With ADBA, however, IT can easily through their connections to the domain. To implement ADBA, administrators must use the Volume Activation Tools utility, which walks them through the setup process. After admins supply the KMS host key, the setup process adds an activation object to the Services. The activation object uses the same Generic Volume Licenses Key (GVLK) and KMS host pair as that for regular KMS activation. When the client joins the domain, the activation object automatically activates the Office installation, granting a license to the client for 180 days. -------------- --- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis. Hello, we have software assurance, so MAK and KMS are available for O2013. I cannot use KMS server (there are reasons for now). So I have to use MAK. ![]() I know that it is possible later on to convert MAK to KMS. I found topic about ADBA. But missing few points from the description after my 2 questions. Can I use KMS key for use with Volume Activation Tool without actually having KMS installed? At the end it says just 180 days activation. What will happen then? From: -------Prior to Office 2013, IT had to rely on Multiple Activation Key (MAK) or Key Management Service (KMS) activation. These processes were generally more complex than ADBA. Little has changed with either MAK or KMS in Office 2013. With ADBA, however, IT can easily through their connections to the domain. To implement ADBA, administrators must use the Volume Activation Tools utility, which walks them through the setup process. After admins supply the KMS host key, the setup process adds an activation object to the Services. The activation object uses the same Generic Volume Licenses Key (GVLK) and KMS host pair as that for regular KMS activation. When the client joins the domain, the activation object automatically activates the Office installation, granting a license to the client for 180 days. -------------- --- When you hit a wrong note its the next note that makes it good or bad. ![]() ![]() Open LicenseThis is the most common of the licensing programs, as only 5 CALs are required to enroll.All license information can be managed through Microsoft's Volume Licensing Service Center website.An authorization number and a license number are required for installation. This article describes how to use the Sysprep deployment preparation tool in conjunction with Windows Product Activation or Volume License Media. Nov 20, 2008. Executive Summary: Use Slmgr to change a Windows Vista or Windows Server 2008 product key or activate a system, extend your product-activation grace period, and determine whether your computer's license is a volume, retail, or OEM license. --- Miles Davis Q1) there is a KMShost product key, and there is a KMSclient product key. The KMShost product key, you install this in your KMShost machine, and the client machines which have the KMSclient product key will contact your KMShost machine for activation. Volume Licensed products are provided by MSFT with the KMSclient product key already installed. The KMSclient product keys are also publically available in the TechNet library documentation. VAMT can be used, with or without KMS installed. VAMT is not part of KMS, and, KMS is not part of VAMT. ADBA is not part of VAMT and VAMT is not part of ADBA. ADBA can only be used if your AD is at the later version, and, ADBA only works for the latest products like Windows8 and Office2013. If you have older AD or older products you will still need to have KMS or MAK. Q2) after 180days, it's the same as KMS - the KMSclient (or ADBA client) will enter 'non-genuine' mode if the client has not contacted ADBA object (or KMShost) to renew the activation status. This wiki article I put together, includes a few helpful links about ADBA and KMS: Don (Please take a moment to 'Vote as Helpful' and/or 'Mark as Answer', where applicable. This helps the community, keeps the forums tidy, and recognises useful contributions. I have no problem with O2013 activation with MDT2012 deployment. I need to activate my APPV O2013 deployment that works fine. I didn't use userconfig.xml that comes with O2013 Appv package at all. I use Office admx for config. Is there an option in O2013 GPO for entering MAK? Is it correct syntax for O2013 MAK activation through userconfig.xml?: Q1) No, you cannot configure a pkey via GPO. Q2) You mention APPV O2013? Have you sequenced this yourself? Or are you using O365ProPlus ODT to create the App-V packages? Don (Please take a moment to 'Vote as Helpful' and/or 'Mark as Answer', where applicable. This helps the community, keeps the forums tidy, and recognises useful contributions. Hello, we have software assurance, so MAK and KMS are available for O2013. I cannot use KMS server (there are reasons for now). So I have to use MAK. I know that it is possible later on to convert MAK to KMS. I found topic about ADBA. But missing few points from the description after my 2 questions. Can I use KMS key for use with Volume Activation Tool without actually having KMS installed? At the end it says just 180 days activation. What will happen then? From: -------Prior to Office 2013, IT had to rely on Multiple Activation Key (MAK) or Key Management Service (KMS) activation. These processes were generally more complex than ADBA. Little has changed with either MAK or KMS in Office 2013. With ADBA, however, IT can easily through their connections to the domain. To implement ADBA, administrators must use the Volume Activation Tools utility, which walks them through the setup process. After admins supply the KMS host key, the setup process adds an activation object to the Services. The activation object uses the same Generic Volume Licenses Key (GVLK) and KMS host pair as that for regular KMS activation. When the client joins the domain, the activation object automatically activates the Office installation, granting a license to the client for 180 days. -------------- --- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis Q1) there is a KMShost product key, and there is a KMSclient product key. The KMShost product key, you install this in your KMShost machine, and the client machines which have the KMSclient product key will contact your KMShost machine for activation. Volume Licensed products are provided by MSFT with the KMSclient product key already installed. The KMSclient product keys are also publically available in the TechNet library documentation. VAMT can be used, with or without KMS installed. VAMT is not part of KMS, and, KMS is not part of VAMT. ADBA is not part of VAMT and VAMT is not part of ADBA. ADBA can only be used if your AD is at the later version, and, ADBA only works for the latest products like Windows8 and Office2013. If you have older AD or older products you will still need to have KMS or MAK. Q2) after 180days, it's the same as KMS - the KMSclient (or ADBA client) will enter 'non-genuine' mode if the client has not contacted ADBA object (or KMShost) to renew the activation status. This wiki article I put together, includes a few helpful links about ADBA and KMS: Don (Please take a moment to 'Vote as Helpful' and/or 'Mark as Answer', where applicable. This helps the community, keeps the forums tidy, and recognises useful contributions. I have no problem with O2013 activation with MDT2012 deployment. I need to activate my APPV O2013 deployment that works fine. I didn't use userconfig.xml that comes with O2013 Appv package at all. I use Office admx for config. Is there an option in O2013 GPO for entering MAK? Is it correct syntax for O2013 MAK activation through userconfig.xml?: --- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis. I have no problem with O2013 activation with MDT2012 deployment. I need to activate my APPV O2013 deployment that works fine. I didn't use userconfig.xml that comes with O2013 Appv package at all. I use Office admx for config. Is there an option in O2013 GPO for entering MAK? Is it correct syntax for O2013 MAK activation through userconfig.xml?: Q1) No, you cannot configure a pkey via GPO. Q2) You mention APPV O2013? Have you sequenced this yourself? Or are you using O365ProPlus ODT to create the App-V packages? Don (Please take a moment to 'Vote as Helpful' and/or 'Mark as Answer', where applicable. This helps the community, keeps the forums tidy, and recognises useful contributions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
February 2018
Categories |