Serializer For Mac

  1. Office Serializer For Mac
  2. Volume License Serializer
  3. Microsoft Office Serializer
  4. Office 2019 Serializer
  5. Adobe Serializer For Mac
  6. Office Serializer For Mac

Soon Microsoft are to release an update to the Office 2016 Volume License installer on VLSC.

The removal and adding of serialization can be combined with a script or task sequence. Applying the license files places the new serial number on the machine and sets it as the active license. Using the licensing files created previously, run the AdobeSerialization application with administrator rights on. This video will show you How to Download and Activate Office 2019 for Macbook permanently 100% in easy and fast way. In my previous video i showed how to to. Once both of these files have been downloaded and installed, your software will be ready to use. There is no need for a product key with Office for Mac. Additional Support. If you installed the Office Suite before installing the serializer package, a message will display when you open your office suite.

This update is 15.17 & is the first that has a few changes that may affect the way you deploy Office 2016.

These changes are going to be later enforced in 15.20 & onwards. Below are some details on the changes, some of the why & how via the power of the Slack & the awesome @pbowden that some of us have had a sneak peek.

Serializer mac office 2019


  • 1 What’s Changing?

When you download the .iso from VLSC you’ll notice two packages within it:

The change is the new second pkg: “Microsoft_Office_2016_VL_Serializer.pkg”

What’s that about?

Well, for a while now it’s been fairly common practice to deploy the Office license to Macs outside of the Office installers or updates.

This came about as on occasion an Office Update or Installer would delete the file.

However, whilst the deletion itself was a bug, the ability to use the license.plist across Macs was also a bug.

What is it & should I use it?

With Office 2016, Microsoft are moving to a device based serialisation method. Which means that deploying the plist /Library/Preferences/ will no longer work.

This device based serialisation is based around the generating a license on the Mac that is to be running Office 2016.

Office Serializer For Mac

So if you employ monolithic imaging or deploy Office 2016 via a Composer snap shot etc, the serialisation will not work. (Please don’t deploy Office 2016 via a Composer snap shot, use the pkg).

Also, if you install Office 2016 whilst booted to another volume (as in when installing via a NetBoot or NetInstall volume or something like Target Mode Imaging), again the serialisation will not work.

To install Office 2016 from another volume & have the serialisation work, cache it locally on the Mac being imaged & install on first boot or if using Casper Imaging check “Install on boot drive after Imaging” for the PKG from within Casper Admin.

However, to enable Office 2016 to be correctly licensed in the multitude of deployment scenarios that we mac admins employ, @pbowden & his team have created the “Microsoft_Office_2016_VL_Serializer.pkg”

Running this will correctly serialise the Office 2016 suite, & should be run from the Mac that’s running the suite. So again, can be added post imaging & then the suite will be correctly serialised.

To be clear, this will only affect you if using the Volume Licensed version of Office 2016 & not the Office365 version.

What happens if I carry on copying the licensing.plist?

For now, not much.

15.17 is the first release with the “Microsoft_Office_2016_VL_Serializer.pkg”, from 15.20 (scheduled for Q1 2016) you will have to use the correct license.

How did people find this out?

Well a little over a month ago a gentleman with the nick @pbowden hopped into the #microsoft-office channel on the Slack, this was awesome as @pbowden is a: Software engineer for Office for Mac/iOS at Microsoft, a fellow Brit & nice guy.

It’s been a great few weeks with the community sharing feedback with @pbowden & some of us being able to test pre-release installers for Office.

I hope this warning has been as helpful to you, as it was when @pbowden shared it with us.


Creative Cloud Packager is no longer in development and no updates will be provided. Also, Creative Cloud Packager cannot be used to create packages that include Creative Cloud 2019 apps or later. Learn More.

We recommend that you use the create package workflows provided in the Adobe Admin Console.

See how to create Named User Licensing packages and Shared Device Licensing packages.

Creative Cloud Enterprise customers can remove old and apply new serialized licensing to end-user machines without reinstalling the software. This article explains how to apply and verify serialized licenses.

You can either apply new serialized licensing or see Solutions, if you are experiencing the following error:

Volume License Serializer

'Your license is expiring'


Contact your Account Representative or Adobe, if you are unaware about the changes in serialized licensing.

Use the Creative Cloud Packager to generate new license files and apply the licenses to your existing user base. The AdobeSerialization and RemoveVolumeSerial application provided must be run with administrative rights. System management tools can be used to deploy these files. No command-line arguments are required. These tools are designed to run silently in the background.


Before applying licensing, exit all Adobe applications. They use the licensing files and can damage your licensing if running during this process.

  1. Using a valid Creative Cloud ENT serial number, create a set of license files in the Creative Cloud Packager.

    Use the one year expiring serial number you were provided by your Account Representative, if issued. Otherwise, the Adobe Licensing website contains the most updated Creative Cloud ENT serial numbers. Contact Adobe for assistance locating the correct serial number.

  2. Uninstall the Creative Cloud desktop app, if installed.

    The Creative Cloud desktop app is not recommended on serialized machines. Any users that login with a named user license can disrupt serialized licensing.

    Administrative users can run a utility to uninstall the Creative Cloud desktop app. IT Administrators can silently run a command against machines to remove the application using system management software such as SCCM or Casper. For instructions, see uninstall the Creative Cloud desktop app.

  3. Remove existing serialization from end-user machines.

    Removing your existing expiring serial number prevents future installations using the incorrect licensing. This step removes all Creative Cloud ENT licenses from the machine. Although a serial number was used to generate the files, it is not required to remove serialization.

    Using the licensing files created previously, run the RemoveVolumeSerial application with administrator rights on the machine. Alternatively, run he application silently with a system management application, such as SCCM or Casper.

  4. The removal and adding of serialization can be combined with a script or task sequence. Applying the license files places the new serial number on the machine and sets it as the active license.

    Using the licensing files created previously, run the AdobeSerialization application with administrator rights on the machine. Alternatively, run the application silently with system management application, such as SCCM or Casper.


    More command-line parameters are not necessary for removing existing serialization or applying new one. The application is designed to run silently. Most users so not even see the command window. The success or failure is recorded in the oobelib.log. For more information, see verify serialized license.

There are two methods to verify that your licensing has been applied. The licensing tool logs success and failure in the oobelib.log file. Furthermore, during installation and launch, the products write an ISO file that contains the type of licensing.

The RemoveVolumeSerial and AdobeSerialization application write success/failure in the oobelib.log file. If run from a user account, it appears in the user temporary folder. System management tools typically run in System or Root access. These tools place the log in the system log location.

  • User Log Location
    • Windows
    • Mac
  • System and Root Log Locations
    • Windows
    • Mac

For information on reading the log, see Logging.

During installation and launch of the Creative Cloud products a software ISO tag is written to the operating system. These can also be used to determine the actual license being used by the product. You can use management systems to scan for the Return codes or software tags to verify the licensing status.

ISO tags are stored in the following location.


Microsoft Office Serializer

Serializer For Mac
  • Windows
  • Mac
    /Library/Application Support/

Important information for license verification

  • These files are typically generated on installation and product launch. Running the license files does not generate these files.
  • The Creative Cloud Enterprise file resembles{}CreativeCloudEnt-1.0-{Win Mac}-GM-MUL.
  • The license being applied to the machine is encoded and near the bottom of the ISO file in a field called <swid:serial_number>.
  • The encoded version is used by all machines.

To decode the serial number

Office 2019 Serializer

Office serializer for mac

Adobe Serializer For Mac


  1. Use the Create License File mentioned option above to generate license files using your serial number.
  2. Apply your new serial number to a machine.
  3. Open the OOBELib.log file and scroll to the bottom. Your encoded serial number appears after LEIDLocForType2A entry written for SN.

Office Serializer For Mac

Adobe Customer Care

  1. Open a support case through your One Console and include the encoded serial number.
  2. Adobe representatives can provide you with the last four digits of the decoded serial number.
  3. You can then match these four digits to the serial number on the Adobe Licensing Website.