Is there a way to check which update branch/channel the Office 2016 installation is set to? Some of the local techs in each office I believe installed the wrong version (I have two different .bat files, one for deferred branch and one for first release). I found the GPO to set that at a policy level but I can't seem to find any way to determine (validate) what branch/channel the machines are on. Is that possible? Is there a regkey or .xml file somewhere with that easily distinguishable? One of my managers who has the first release / validation branch enabled received the familiar yellow bar across the top of his Outlook last week that Office needed to be updated and those of us who are also on first release did not get the same prompt - which is what lead me down this path of trying to figure out what update branch everyone is on.
Also, I'm playing around with the update options via GPO and I enabled the "Office 365 Client Management" policy and applied it to a test machine. Is that policy required in order for O365 clients to get updated from ConfigMgr? In other words, if that policy is NOT applied to a machine, it's going to get updates directly from Microsoft? I noticed that when I added Office 2016 updates to my Software Updates component, days later, none of the 2016 updates are showing as Required in the console despite us having close to 40 or so Office 2016 installs (combination of first release and CBB / deferred). I'm wondering if applying this policy is going to change that and I'll start seeing some of those updates listed as Required? [cid:[email protected]] Thanks, James Beardsley | Firm Technology Group Dixon Hughes Goodman LLP [cid:8644FC49-D5C9-45AE-B387-04FAFC0CC7A5]<http://www.dhgllp.com/> ________________________________ Confidentiality Notice: This e-mail is intended only for the addressee named above. It contains information that is privileged, confidential or otherwise protected from use and disclosure. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, or dissemination of this transmission, or taking of any action in reliance on its contents, or other use is strictly prohibited. If you have received this transmission in error, please reply to the sender listed above immediately and permanently delete this message from your inbox. Thank you for your cooperation.
