User Profile
DaveGuenthner
MicrosoftJoined Oct 03, 2018
User Widgets
Recent Discussions
Re: Office 365 Pro Plus - Closes All Office apps when updates are deployed
Rob Fuller FORCEAPPSHUTDOWN is used only during install scenario to close legacy click-to-run applications. Remember, there was an older version of C2R based on Office 2013.. since deprecated and gone. This parameter is not relevant to Update scenario.Re: Office 365 Pro Plus - Closes All Office apps when updates are deployed
DBarnhart Thanks for the suggestion. My take is to never use a on-premises file share because it has so many pitfalls. (IT Pro has to download all content and mirror CDN and when you consider all the different channels and architecture combinations cost of ownership is too high in my opinion) Also, for customers who use SCCM, this breaks it due to UpdatePath having priority. When possible use CDN or SCCM only.Re: Office 365 Pro Plus - Closes All Office apps when updates are deployed
Rob Fuller Modification of the trigger of Office Automatic Updates is not supported, so I can't support that suggestion. For example, there is a feature to apply updates in CDN scenario which computer is detected to be IDLE which would no longer function. My suggestion is setup a few test VMs and evaluate GPOs in thread mentioned earlier to get a sense of the normal notification workflow. Additionally, if it wasn't mentioned earlier.. if a new Office build is staged but cannot be installed because Office program is open, by default Office registers a service called "Microsoft Office Click-to-Run Service" that will apply the update on any computer startup. The idea is to apply the update prior to CTRL + ALT + DEL because we know the first thing user will do is launch Office once they reach desktop. You may be able to also resolve through combination of deadline + computer restart during agreed upon maintenance window. (This is what SCCM does in effect)Re: Office 365 Pro Plus - Closes All Office apps when updates are deployed
Rob Fuller A few suggestions: 1. If you suspect there is a custom script calling officec2rclient.exe out of band then use process monitor with filter for process name officec2rclient.exe + drop filtered events to monitor and trap the event to understand who the caller is and turn off the script. Download latest ADMX 2. You can turn on "Delay downloading and installing updates for Office". This is basically N+Days from Patch Tuesday, for example 5. Roughly five days after build is released updates will be installed. Make the difference in days end up on a weekend. 3. You can turn on Update Deadline. Get buy in from customer on a maintenance window like weekend where installation will take place and users get series of notifications prior to change. 4. Integrate with SCCM with standard Software Update Workflow with restart notifications and so forth. Most customers I speak with include Windows and Office Updates in the same software deployment so there is a single reboot for maintenance window. 5. Make sure this is set or not present, can't be 1. This suppresses the bizbar notifying the user of pending change HKLM\SOFTWARE\Policies\Microsoft\office\16.0\common\officeupdate "hideupdatenotifications"=dword:00000000Re: Office 365 Pro Plus - Closes All Office apps when updates are deployed
Christopher Hadwin and community, I recently blogged on this topic. It discusses end user behavior and workflow.. just scroll down to the SCCM section. If there is something you would like to see added, let me know and I'll update in FAQ Understanding Office 365 ProPlus Updates for IT Pros (CDN vs SCCM)Re: Initiating Office Updates Without User Intervention
drawson Couple of key decisions IT Pro needs to take: 1. What channel? (determines the rate of change in terms of feature\fixes) If you don't declare a channel, Semi-Annual Channel is used. Basically you get a build every month for security. Two special months of January\July you get security+feature+fixes 2. Where from? (CDN which is default or SCCM) By default, the Automatic Updates scheduled task updates client on behalf of user without any intervention. If you disabled Automatic Updates this would explain why updates are not happening. Can you take a look at my two blog articles which I hope will address concerns in detail? Understanding Office 365 ProPlus Updates for IT Pros (CDN vs SCCM) How to manage Office 365 ProPlus Channels for IT ProsRe: Automate Office 365 Outlook profile creation - can it be done?
Damon Weelros Sorry you're running into trouble. I've tested and re-validated this twice and it does work for me, no prompts whatsoever. Using process monitor would be a good place to start troubleshooting to inspect whether Outlook process on launch is checking for the registry key or any others with similar name etc. (Make sure you're using recent version of Office 365 ProPlus and have reviewed external links I shared in case I missed something in my explanation) Worst case, reach out to MS Support and get another set of eyes on it but from my tests it did work.Re: Updates Issue
CookieW great question. I recently wrote a post on how things are *supposed* to work, can you review it and take a look at the FAQ section under SCCM scenario? The post is here: Understanding Office 365 ProPlus Updates for IT Pros (CDN vs SCCM). There have been a few bugs in the past but to my knowledge those have all been fixed, even in latest Semi-Annual Channel version. Do you have any software packages in Software Center which change channels, call OfficeC2rClient.exe (not supported) or add\remove Visio or Project? The reason I ask is anytime you request a change, by default Office Client will always pull the latest build for respective channel from CDN. Due to customer feedback we recently added a feature called "MatchInstalled" which basically says, just do it but keep the same version of everything even if newer build is available. Is it possible these few machines are getting a configuration change we call "2nd Install" and MatchInstalled is not being used? This would explain observation. One additional thought, "Monthly Channel release is supported only until the next Monthly Channel release is available." We think about Monthly in terms of customers using CDN with Delivery Optimization for this scenario because the number of builds released are very frequent. So while this has nothing to do with your question I wanted to make sure you knew support statement for Monthly. Customers who need more time\predictability tend to use Semi-Annual or Semi-Annual (Targeted). Let us know if these are plausible explanations. If not, get in touch with MS Support who can gather logs and have in depth review.Re: Understanding Office 365 ProPlus Updates for IT Pros (CDN vs SCCM)
lforbes This blog scope does not include Windows only Office 365 ProPlus. You're right in that monthly cumulative build (irrespective of Channel) of Office is around 2GB. However, the exact sizes for updates each month are quite small and are documented here. In basic SCCM scenario, IT Pro downloads 2GB one time from internet and then distributes content to all DPs. The Office Clients then use COM application referenced in blog above to guarantee Office Client pulls update content only from DP and is not permitted to use CDN. (it's not the entire build but subset of files) I've used Wireshark extensively and can confirm this is how Office 365 ProPlus update process works and aligns with documentation.Re: Is there a way to disable second screen via GP or Reg after Outlook auto add's your account?
Heather_Kuhn Here are my notes which worked for multiple customers on this.. HKCU\Software\Microsoft\Office\16.0\Outlook\AutoDiscover ZeroConfigExchange = 1 (DWORD) How to manually create additional Outlook 2016 profiles with ZeroConfigExchange in place https://support.microsoft.com/en-us/help/4046818/zeroconfigexchange-outlook-manually-create-additional-profile ZeroConfigExchange - Automating the Creation of an Outlook Profile for Exchange Accounts https://techcommunity.microsoft.com/t5/Outlook-Global-Customer-Service/ZeroConfigExchange-Automating-the-Creation-of-an-Outlook-Profile/ba-p/389691 When I performed this prior to profile being present on machine, Outlook was 100% silent. This worked on first launch.. if I already had a profile on the machine it didn't work, I got Outlook profile prompt. To troubleshoot I recommend you logon with another profile, use the "Advanced System Settings" feature from My computer to access User Profiles button and ensure the test account profile your using doesn't exist or delete it prior to test. I also used process monitor to "trust and verify" that Outlook process checked and found this key on launch. Finally, make sure you're following this process when creating a Windows "image" including Office 365 ProPlus. Deploy Office 365 ProPlus as part of an operating system image
