Our organization sets up "shared" mailboxes by just creating a regular mailbox and then giving people Full Access in the ecp/exchange admin. It then automaps to their Outlook client. But we are running into the bug where emails sent to that address marked as private, will be invisible. Users can see the count ("Inbox 6"), but not the actual email in Outlook client (only in OWA). The only "fixes" I can find involve a system using Delegate settings. We do not do delegates. No one in our company is a listed delegate nor are these "shared" mailboxes even attached to a client as a standalone where Delegate settings could be managed. Any other resolutions for this?
Vermont1981's questions
Is there a way to restrict an exchange distribution list email address to Allow All external, but only "A", "B", and "C" internal?
Scenario: Office 2016 Enterprise Plus (volume license version) is installed on a base image of Windows 10, then when cloned onto workstations, they report that Office is missing its license and needs to be repaired (repair fails. requires full uninstall, reinstall)
Does anyone know why Office 2016 volume license edition is corrupted when cloned? It should work fine.
ETA: Application logs show an event ID 1000, faulting application MsiExec.exe, faulting module KERNELBASE.dll, exception code 0xc06d007e.
Also event 11729, Product: Microsoft Office 64-bit components 2016 - configuration failed.
When I change directory to the x86 Office16 path and run cscript ospp.vbs /dstatus, is reports "no installed product keys detected"
ETA2: When a newly-imaged workstation first opens an Office product, a "Configuration" wizard begins to run automatically but then fails, leaving Office without a product key. The base image (before sysprep generalize) does not have this problem though. Office works fine on it before sysprep and cloning.
At some point in 2019 Windows 10 updated to where PowerShell is the default in the WinX menu. I'm looking for a solution to change this that can be syspreped and cloned. So a registry modification or non-user specific settings change. Note: There are plenty of explanations out there for changing this in the File Explorer context menu (registry>shell>cmd), but that does not change the WinX menu.