After completing switching process, DUA agent is not removing existing Outlook *.OST file from workstation filesystem.
When launching Outlook thick client, your existing mail profile is also getting errors concerning :
1) Mailbox temporarily moved.
2) Might not have all of your previous data.
3) Connect to temporary mailbox.
4) Work offline with all of your old data.
5) Cannot send or receive email messages.
DUA is designed to switch your Outlook profile from a source email address to another different target email address, however both your source & target email addresses are the same : abc@xyz.com
When you are having the same source & target email addresses, your scenario is unfortunately not supported, since there is nothing new for DUA to switch to, because DUA is designed to switch to another different target email address.
From your DUA log :
Both source & target email addresses are the same :
"SourceEmail": "abc@xyz.com",
"TargetEmail": "abc@xyz.com",
New Outlook profile is created but duplicated :
19:36:22 [Info] Adding Profile name 'abc@xyz.com'
19:36:23 [Info] Successfully created profile 'abc@xyz.com'
19:36:23 [Info] Setting default profile to 'abc@xyz.com'
Old Outlook profile is forbidden to be removed :
19:37:31 [Info] Removing profile with email address: 'abc@xyz.com'
19:37:31 [Info] Removing Outlook profile 'outlook'
19:37:31 [Info] Removing 1 orphaned .OST files
19:37:31 [Error] Exception in DeleteFiles()
System.IO.IOException: The process cannot access the file 'C:\Users\decoration.india\AppData\Local\Microsoft\Outlook\abc@xyz.com - outlook.ost' because it is being used by another process.
DUA has created a new Outlook profile which may have duplicated or overwritten your old Outlook profile with the same email address.
When trying to remove your old Outlook profile with the same email address, DUA may actually be looking at your newly created Outlook profile, so of course it is unable to proceed to remove, because this Outlook profile is still in use with the same email address.
Since old Outlook profile & *.ost file are still in active usage by Outlook Client, an unexpected conflict may have resulted here, DUA is unable to remove them, because they are already being locked up by Outlook Client, so that no other program is allowed to get access to them, hence your scenario for Outlook profile switch is reasonably not supported by DUA.
