- Office 2016 For Mac Support
- Office 2016 Mac Update
- Office 2016 Mac Update Manually
- Update Office For Mac
Hollywood.com, LLC Digital Millennium Copyright Act (“DMCA”) Policy
Hi Peter, Thanks for posting on our forum. First, I want to say that Office 16.22 is include in Office 365 or Office 2019, as you purchased a license for Microsoft Office 2016 for Mac Home and Business, I suggest you uninstall the Office 2019 and reinstall Office 2016. Microsoft issued another update, so I have now installed the Office 2016 updates and they were successful so far. But still missing a bunch of features from Office 2011. Beats me how Apple let them get away with doing that. Thanks for your reply. Office for Mac that comes with a Microsoft 365 subscription is updated on a regular basis to provide new features, security updates, and non-security updates. The following information is primarily intended for IT professionals who are deploying Office for Mac to the users in their organizations. Office 2016 is a much welcome upgrade for any existing Office installation, particularly for Mac users who’ve been suffering under the rather awful Office 2011 with its ugly, clunky interface. Office 2016 brings welcome uniformity by making the Mac version nearly identical to the Windows version. The identifiers for the Office apps, such as Word and Outlook, can be used for Office for Mac (from an Office 365 or Microsoft 365 subscription plan) or for Office 2019 for Mac (either a retail or a volume licensed version). If an update is pending for MAU itself, that update must be applied before any applications can be updated.
Introduction
This policy implements the procedures set forth in 17 U.S.C. §512 and the Digital Millennium Copyright Act (“DMCA”) for the reporting of alleged copyright infringement. It is the policy of the Company to respect the legitimate rights of copyright owners, their agents, and representatives. Users of any part of the Company computing system are required to respect the legal protections provided by applicable copyright law.
Designated Agent
The Company’s Designated Agent to receive notification of alleged infringement under the DMCA is:
Greg Sica
2255 Glades Road, Suite 221A
Boca Raton, FL 33431
Email: violations contact form (this email address is only for copyright infringement claims – you will not receive a reply if the matter is not a copyright issue): legal@hollywood.com
When we receive proper notification of claimed infringement, the Company will follow the procedures outlined herein and in the DMCA.
Complaint Notice Procedures for Copyright Owners
The following elements must be included in your copyright infringement complaint notice:
1. An electronic or physical signature of the copyright owner or a person authorized to act on behalf of the owner of an exclusive right that is allegedly infringed.
2. Identification of the copyrighted work or works claimed to have been infringed.
3. Identification of the material that is claimed to be infringing or to be the subject of infringing activity and that is to be removed or access to which is to be disabled, and information reasonably sufficient to permit the Company to locate the material.
4. Information reasonably sufficient to permit the Company to contact the complaining party, including an address, telephone number, and, if available, an email address at which the complaining party may be contacted.
5. A statement that the information in the notice is accurate, and under penalty of perjury, that the complaining party is authorized to act on behalf of the owner of an exclusive right that is allegedly infringed.
If you do not include all of the above information, it may invalidate your notification or cause a delay of the processing of the DMCA notification.
Please note that, under Section 512(f) of the Copyright Act, any person who knowingly materially misrepresents that material or activity is infringing may be subject to liability.
Please also note that the information provided in your notification to us may be forwarded to the person who provided the allegedly infringing content.
Company reserves the right to publish Claimant information on the site in place of disabled content.
Notice and Take down Procedure
Procedure: It is expected that all users of any part of the Company system will comply with applicable copyright laws. However, if the Company receives proper notification of claimed copyright infringement, it will respond expeditiously by removing, or disabling access to, the material that is claimed to be infringing or to be the subject of infringing activity provided all such claims have been investigated and determined to be valid by the Company in the Company’s sole and absolute discretion.
The Company will comply with the appropriate provisions of the DMCA in the event a counter notification is received.
Office 2016 For Mac Support
Please note that under Section 512(f) of the Copyright Act, any person who knowingly materially misrepresents that material or activity was removed or disabled by mistake or misidentification may be subject to liability.
Repeat Infringers
It is Company’s policy to permanently cancel the privileges and authorizations, in appropriate circumstances, of repeat copyright infringers.
Accommodation of Standard Technical Measures
It is Company policy to accommodate, and not interfere with, standard technical measures it determines are reasonable under the circumstances, i.e., technical measures that are used by copyright owners to identify or protect copyrighted works.
Soon Microsoft are to release an update to the Office 2016 Volume License installer on VLSC.
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 MacAdmins.org Slack & the awesome @pbowden that some of us have had a sneak peek.
Contents
- 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/com.microsoft.office.licensingv2.plist 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.
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?
Office 2016 Mac Update
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 MacAdmins.org Slack, this was awesome as @pbowden is a: Software engineer for Office for Mac/iOS at Microsoft, a fellow Brit & nice guy.
Office 2016 Mac Update Manually
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.
Update Office For Mac
I hope this warning has been as helpful to you, as it was when @pbowden shared it with us.