Email sent from a shared mailbox are not saved to the Sent Items

 Issue :

When a user sends an Email from his delegated (shared) mailbox the Email which sent from the delegated mailbox are stored in user's (who sent mail) sent item instead of the shared mailbox's sent item.

Cause :

When user send a new message from the shared mailbox, Outlook automatically sends from the sender's account. Therefore, messages are stored in the Sent Items folder of the sender's mailbox.

Solution :

Note : Outlook must be configured to run in cached mode for this option to work correctly. This will not work in NEW OUTLOOK mode which does not support cached mode.

1. Click Start, click Run, type regedit, and then click OK.

2. Locate and then click the following registry subkey:

   HKEY_CURRENT_USER\Software\Microsoft\Office\x.0\Outlook\Preferences

    Note :

   The x.0 placeholder represents your version of Office (16.0 = Office 2016, Office 2019, or Office LTSC 2021, 15.0 = Office 2013, 14.0 = Office 2010).

3. On the Edit menu, point to New, and then click DWORD Value.

4. Type DelegateSentItemsStyle, and then press Enter.

5. Right-click DelegateSentItemsStyle, and then click Modify.

6. In the Value data box, type 1, and then click OK.

7. Exit Registry Editor.

8. Close and open the outlook and try to send EMail again.

Source : https://learn.microsoft.com/en-us/exchange/troubleshoot/user-and-shared-mailboxes/sent-mail-is-not-saved

https://learn.microsoft.com/en-us/outlook/troubleshoot/email-management/email-remains-in-the-outbox-when-you-use-the-deleg

The specified user logon name already exists in the enterprise

 I have a Azure sync issue for a user due to it has other language character (for examplw German's ü) we tried to change character to u instead of ü, however we got an below error,

The specified user logon name already exists in the enterprise. Specify a new one, either by changing the prefix or slecting a different suffix from the list.

 

Tried find the user with character u (we thought there is another user with this name already) and ensured that, there is no such user(s). 

Seems the Windows OS settings could not identify the both characters are different and it always says above error.

Also tried customer LDAP query and result display only affected the user. 

(&(objectCategory=person)(objectClass=user)(sAMAccountName=logumm))

So, we tried to rename the user with random number, like  logümm121 and renamed to logumm. It works fine and AAD synced the user to Azure portal.

A contact's presence status is unknown in MSTeams

    Recently one of our newly joined user had issue that presence status is unknown in Teams. He gets "Unknown status" in MSTeams. He also cannot see the status of others, however all the other applications that use the Microsoft 365 account work properly.

    He was not able to access the status for MSTeams through web, desktop app, mobile and all other ways. Found some articles,  for recommendations to fix this by apply coexsistance change Teams, however, coexsistance change might force reoccurrence meetings to be resend.

   The issue might be related to license assigned to MSTeams, so removed the license for the user from on-prem AD and waited to sync with AAD, once it synced again issued license to the user. 

Note: Through conditional access, we are assigning license for particular security group users, so removed him from that security group and again added.

    We waited for some time till re-assigned license to be take affect. The license is reissued to the user the MSTeams started to work properly.

Note: This may affect the functionality of user's other services like Email and all, so plan accordingly.

Veeam Explorer for SharePoint shows as empty while restore

We are unable to view any site/content in Veeam Explorer for SharePoint when I initiate restore, it looks empty under content DB path. We kept the screen more than an hour but no use. 

Here is the solution:

1.Please make sure there is no backup job running or wait for some time to complete all the backup jobs.
2.Stop Veeam console and Veeam services (also from the remote proxies):

• Veeam Backup for Microsoft Office 365 service (Veeam server)
• Veeam Backup Proxy for Microsoft Office 365 services. (Veeam server & remote proxies)

3.Go to Veeam Backup for Office 365 - %programdata%\Veeam\Backup365\config.xml and proxy.xml
4.Edit the config.xml in a text editor.
5.Edit the proxy.xml in a text editor.
 
Add the bold text as per examples below:
 
The config.xml for Backup365 should be like this:
<Veeam>
  <Archiver OperationTimeout="1200">
   ….
    <WCF OperationTimeout="1200" />
   ….
  </Archiver>
</Veeam>
 
The proxy.xml from Veeam server should be like this:
<Veeam>
    <Archiver OperationTimeout="1200">
      <RemoteConnection Timeout="10:00:00" />
      <WCF OperationTimeout="1200" />
       ….
  </Archiver>
</Veeam>
 
We`ll need to increase the timeout for the SharePoint explorer in order to have time to load all the items in the GUI. To do this we`ll need to modify the config.xml.
 
In order to view to config.xml, we need to enable extended logging in the SharePoint explorer. To enable extended logging, please do the following:
 
1)Open the Sharepoint explorer
2)Go to General Options -> Advanced
3)Click on "Enable extended logging"
 
After this go to C:\ProgramData\Veeam\Backup\SharePointExplorer and you`ll have the config.xml. Before we edit it please stop both VBO365 services:

• Veeam Backup for Microsoft Office 365 Service
• Veeam Backup Proxy for Microsoft Office 365 Service

 
Add the bold text as per examples below:
 
The SharePoint Explorer config.xml should look like this:
<Veeam>
<Archiver OperationTimeout="1200">
    <RemoteConnection Timeout="10:00:00" />
    <WCF OperationTimeout="1200" />        
….
 </Archiver>
</Veeam>
 
 
The proxy.xml from the remote proxy, should be like this:
<Veeam>
  <Archiver OperationTimeout="1200>
      <RemoteConnection Timeout="10:00:00" />
      <WCF OperationTimeout="1200" />
   ….
  </Archiver>
</Veeam>
 
The issue should fix now. If the issue persists, please change the value "1200" to "2400" and check again.

Office can't be activated because it doesn't meet the requirements for running on remote

 Error :

When user tries to open office applications and gets the error,

 

Office can't be activated because it doesn't meet the requirements for running on remote

 

in Terminal/RDS server the following error may occur:

This copy of Microsoft Office 2016 cannot be used on a computer running Terminal Services. To use Office 2016 on a computer running Terminal Services, you must use a Volume License of Office.

 

Troubleshoot:

Please confirm whether the office product installed as Office 365 ProPlus on a remote desktop server through ODT deployment.

 

Fix/Solution:

If it is not installed by ODT then try to install using ODT installation method.

 

If yes,

Open the registry editor (Win+R > regedit) and go to this path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration

Add the SharedComputerLicensing (Reg_SZ) key and set its value to 1.

(or)

Press Win+R and run gpedit.msc to open the local group policy editor.

Edit the policy or create this policy if it doesn’t exist:

Computer Configuration\Policies\Administrative Templates\Microsoft Office 2016 (Machine)\Licensing Settings

Enable the 'Use shared computer activation'.