![]() ![]() Does this happen to all users that upgraded to. I haven't received any other reports on this. >our users started to report problems with their Outlook Perhaps because the new build was not yet available fot me? The Automatic Update is triggered via a Scheduled Task that executes this command: "C:\Program Files\Common Files\Microsoft Shared\ClickToRun\OfficeC2RClient.exe" /update SCHEDULEDTASK displaylevel=FalseĮxecuting this should also trigger the Automatic Update I think. Normaly when you don't include this parameter it will update to the latest available build. The new build is not available in all areas. In above command I've added the updatetoversion parameter because the Deferred Channel content is still the old version. If you don't want it to be hidden, remove this part: displaylevel=False The update will be performed in the background, completely hidden. You can execute this without local administrator rights. ![]() The easietst way to updated to the new (working) build is executing this command: "C:\Program Files\Common Files\Microsoft Shared\ClickToRun\OfficeC2RClient.exe" /update user updatetoversion=.2092 displaylevel=False ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |