Thanks for the reply. I have been working the issues with the MS support team. I have been told that my issue related to Outlook search as well as the Excel error when sending to email is a bug in the 1709 Fall Creators update. It appears the Windows upgrade is removing Office registry keys, he could not provide any further information than that as the information is very new and nothing has been officially confirmed as of yet.
I was told the issue was not present in the 1703 build, because we got such a late start we decided to go to 1709 instead of 1703...maybe we should re-think our decision. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of ODONNELL Aaron M Sent: Friday, January 19, 2018 4:54 PM To: mssms@lists.myitforum.com Subject: [mssms] RE: 1709 Issues We've seen both those two issues in our 1709 testing as well, and both those fixes worked for us in most cases. A few computers are still having the outlook search issue even after a repair + cleaning up the OSTs and creating a new Outlook profile. We haven't gotten very far in pursuing it since 1709 is still in testing and we are still working through a host of 1703 upgrade issues that have a much bigger priority. Thanks, Aaron O'Donnell From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Enley, Carl Sent: Friday, January 19, 2018 5:53 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] 1709 Issues We are currently starting to pilot the 1709 update to our users and have started to notice a few issues, I am curious if anyone else is seeing the same problems we are. We are using 1709 Enterprise and SCCM 1706 task sequence to deploy, we have Office 2016 .msi version installed. 1 - After upgrading to 1709 our users are having search issues with Outlook 2016, very similar to the issues last June when the security patch broke the search function. Basically when they search they have a message saying "Something went wrong and your search couldn't be completed", results are retuned but they appear to be missing some items. I was able to fix the issue by deleting the users .OST file and performing an Office repair, neither one by itself would fix the issue. This is really not a great solution as our users have pretty large .OST files and some of them are connected via slow WAN links. Seems I may not be alone - https://social.technet.microsoft.com/Forums/ie/en-US/c9673cdc-0fa9-4126-9acc-b9ec42222ae3/after-windows-10-fall-update-1709-outlook-search-error?forum=outlook 2 - After upgrading to 1709 when a user is in Excel 2016 and they use the File > Share > Email to send the workbook via email they receive the following error " General mail failure. Quit Excel, restart the mail system and try again". The only way to fic this is to delete the MAPI32.DLL file from C:\Program Files (x86)\Common Files\system\MSMAPI\1033\ directory. Again it doesn't look like I am alone - https://social.technet.microsoft.com/Forums/office/en-US/4ca08c76-5252-40a2-88bb-dd430d637c2b/general-mail-failure-quit-microsoft-excel-restart-the-mail-system-and-try-again?forum=Office2016ITPro https://answers.microsoft.com/en-us/windows/forum/windows_10-windows_install/creator-update-excel-2016-general-mail-failure/07c820b6-3f5c-4a2d-bc2c-a051ec1effbf?auth=1 3 - My last issue is more of a product issue / feature request. While performing the 1709 upgrade over a VPN when the first reboot occurs the client loses contact with the MGT point, the task sequence continues to run and because I have the content downloaded before running the install succeeds and life is good. The problem with this is that the client does not queue up the status messages to be sent upon next connection to the network so our reporting is not reliable, we have no idea if the user is up to date via the monitoring tab...it gets messy as the systems stay in the "In progress" state. I guess in an ideal world every user would be in an office somewhere connected to the corporate LAN while performing the feature updates but that is just not feasible in our environment as we have many road warriors and sales folks. I suppose some type of cloud / DMZ / IBCM type solution would help the situation but ideally I would expect the status messages to remain client side until the next time it connects to the MGT point and then send them up. Does anyone know of a script or something that could be run to re-send the task sequence status messages? *Rant on/ - I have premiere support so I opened a ticket regarding the issues I am having, still waiting on response from MS but what I find ridiculous is that I have to open up 3 different tickets. So rather than working with one support rep I now have to mage 3 different support reps wanting to setup time to trouble shoot etc...all of the issues were caused by a simple 1709 feature update, there should be someone who can take the lead and get the right people in the loop to help, why should I have to open and manage 3 different support cases because they broke core functionality in the product with the upgrade. I guess I understand the VPN status message thing should be a separate ticket but come on Office is Office and whether it is Outlook or Excel you would think the same guy could help me. *Rant off/
