After you Synchronize users from Local Active Directory to Office 365 Directory using dirsync and try to enable users licenses on Office 365 portal you get the following error.
Error:
Exchange: Cannot process command because of one or more missing mandatory parameters: ArchiveGuid.Exchange: An unknown error has occurred. Refer to correlation ID: dfd8cc2d-e6a4-4b47-8e1e-2059031893c1
According to the error message, it indicates that parameter ArchiveGuid is missed, please refer to the following steps to narrow down this issue:
Apparently the commands above didn’t work. And so I had to check something else.!
In order to solve the problem first
I had to assign License to the user synced on O365.
Check User’s Proxy target attribute using ADSI. (Which was correct)
Checking Archiving Attributes since the error is mentioning the Archiving option.
After checking the Archiving attributes it turns that the admin of Exchange has changed the below attributes before he assign user the license on o365 and migrate the user.
5. So deleting the value below msExchArchiveName and setting up msExchRemoteReceipeintType back to 4 have solved the problem 6. Of course DirSync needs to be applied in order to sync changes to AD on O365.
Note:
The migration for the User should be “continued” from previous migration batch in the portal otherwise if you start any new batch for the same user the result will be completed but migration won’t take place.
If you used DirSync to sync users from local to online, please try to restart the DirSync to check whether this issue persists or not.
Before Starting the process of implementing the integration, you must consider using some tools to see if your environment has no issues.
First you must use this tool IdFix check the active directory for any possible issues when installing Dirsync and synchronizing users and their objects to the cloud.
IdFix is used to perform discovery and remediation of identity objects and their attributes in an on-premises Active Directory environment in preparation for migration to Office 365. IdFix is intended for the Active Directory administrators responsible for DirSync with the Office 365 service.
Install ADFS (Optional) for SSO (To authenticate users from Local AD)
Note about ADFS:
ADFS can be the reason of so much headache and it’s always better to avoid installing it, instead of using ADFS to use the same password for users on a large scale deployments, the Dirsync can Synchronize local Passwords to Azure AD and same password can be used for both users local and online.
Create an enterprise admin user account on the domain for DirSync service
Installation of Dirsync with Password synchronization: We prepare a separate server for the DirSync tool that is windows 2008 R2 SP1 or 2012 R2 installed and the server
should be domain joined in order to reach Active Directory.
The account used with Dirsync should be member of the domain admin. Also you need to have the admin credentials for the tenant that you signed up to on O365.
While installing I had an error saying that current user was not member of the Synchronization Engine FIMSyncAdmins group.
I tried uninstall DirSync but it it gives the same error message
The FIMSyncAdmins group is a local group on the server. Your user is not a member of that group locally. Try adding your user to the group.. after adding the user to the required group the installation were completed successfully.
First you need to make sure that your customized (personal) domain is active.
Now we need to enable Dirsync from the portal, next to Active Directory ® Synchronization Click on Set up and activate DirSync.
Now click on Activate
Now after we made sure that our domain is active and we activated Dirsync on Office 365 portal let’s Go back to DirSync server to complete the steps and check if we can start syncing your Active Directory.
Type your enterprise admin user which you have prepared for Dirsync, for my case I’m just going to use the domain admin user since it’s a Lab.
Make sure you Enable Hybrid Deployment since Azure active directory will modify objects in your on-premises AD.
In case you would want to have your On-premises AD password for users synchronized with users on Office 365
then you must tick the option as in the below snapshot.
Here, When I click next I get an error as following:
Error:
The new version of Dirsync doesn’t accept the domain admin account.
Solution:
In order to resolve the problem you have to create a new user account with enterprise admin privileges
Use this account to connect to AD during config.
Here I created the new user and added the required groups.
After using the new account there was no issue with the setup and I could complete the configuration successfully.
Once the configuration finished you will be able to find event ID 611 in the logs.
Now checking Office 365 portal, I can see that users have been synced to the Office 365 portal:
Now let’s go to the Exchange On-Premises server, and before starting the HCW on Exchange on-premises you will have to do three main steps:
Make sure Autodiscover is set
Make sure WSSecurity is set to true.
Make sure that’s MSProxy is set to True.
You need to make sure that Autodiscover URL on autodiscover virtual directory is set for internal and External. To do so first check the current configuration by using the following commands.
Get-autodiscovervirtualdirectory | fl
If the Internal and external Autodiscover urls are not set then set them using the following command line.
Now to enable the WebServices use the following cmdlet on Exchange Management shell
To enable the WSSecurity use the following CMDlet
Then use the command “Get-WebServicesVirtualDirectory -Server ExchangeHostName | fl” to see if the values have changed
I need to go to my Local exchange server and start the Hybrid process.
From Under MS Exchange on-premises we click on Organization Configuration after we add our trusted tenant domain to the Exchange server.
Click Next, and enter the credentials for your domain admin and tenant admin.
Click Next, Add enter the verified domain.
Click next, here you will need to press ctrl + C to copy the value and create this value as txt in your public DNS.
Click next once you verified that the value has been published and available on
Select the Mailbox, Client Access, Hub transport.
Here click Next again, below you will need to create a new A Name record in your public DNS that directs to your Inbound connector’s IP under ForeFront Online Protection and the FQDN e.g. “Mail.domain.com” under the outbound connector or place the SMTP gateway’s Public IP if you have it and create an A name in your public DNS that has the same IP .
In the following step, the snapshot shows the certificate which I have associated with my hub transport server however, this certificate is public certificate that’s brought from 3rd party.
Select the certificate and choose how you want to route your mail.
Click Manage, When clicking manage you might get the following error message
Updating hybrid configuration failed with error ‘Subtask Configure execution failed: Configure Mail Flow Execution of the Set-HybridMailflow cmdlet had thrown an exception. This may indicate invalid parameters in your Hybrid Configuration settings.
Connector validation failed: RouteAllMessagesViaOnPremises can be set to true only when there is at least one inbound connector of type OnPremises with AssociatedAcceptedDomains set to empty.
at Microsoft.Exchange.Management.Hybrid.RemotePowershellSession.RunCommand(String cmdlet, Dictionary`2 parameters, Boolean ignoreNotFoundErrors)
‘.
Additional troubleshooting information is available in the Update-HybridConfiguration log file located at C:\Program Files\Microsoft\Exchange Server\V14\Logging\Update-HybridConfiguration\HybridConfiguration_2_11_2014_15_9_37_635277281771541111.log.
As Microsoft Employee advises it’s better to use the internet instead. So we will go with this option and see what happens.
The general recommendation and default setting is not do this, but to deliver e-mail from Exchange Online to external recipients directly to the Internet instaed.
If it is no requirement, I advise you to skip that option.
After migrating a user from on-premises exchange to O365 and try to move it back from O365 to On-premises the user will not move and you will see a message similar to the one below.
Resolution :
To resolve this issue, you will have to disable the ESMTP Inspection rule on your Cisco firewall.
4/4/2014 7:27:34 PM – Remote Server at emea01-internal.map.protection.outlook.com (10.47.216.25) returned ‘450 4.7.0 Proxy session setup failed on Frontend with ‘451 4.4.0 Primary target IP address responded with: “451 5.7.3 STARTTLS is required to send mail.” Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was 210.179.31.5:25”
4/4/2014 7:27:34 PM – Remote Server at emea01-internal.map.protection.outlook.com (10.47.216.25) returned ‘450 4.7.0 Proxy session setup failed on Frontend with ‘451 4.4.0 Primary target IP address responded with: “451 5.7.3 STARTTLS is required to send mail.” Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was 210.179.31.5:25”
Original message headers:
Received: from DB4PR03MB610.eurprd03.prod.outlook.com (10.141.234.156) by DB4PR03MB532.eurprd03.prod.outlook.com (10.141.235.143) with Microsoft SMTP Server (TLS) id 15.0.908.10; Wed, 2 Apr 2014 19:31:29 +0000 Received:
from DB4PR03MB610.eurprd03.prod.outlook.com (10.141.233.156) by DB4PR03MB610.eurprd03.prod.outlook.com
(10.141.234.156) with Microsoft SMTP Server (TLS) id 15.0.898.11; Wed, 2 Apr 2014 12:49:18 +0000 Received: from DB4PR03MB610.eurprd03.prod.outlook.com ([10.141.233.156]) by DB4PR03MB620.eurprd03.prod.outlook.com
([10.141.233.156]) with mapi id 15.00.0913.002; Wed, 2 Apr 2014 12:49:17 +0000 Content-Type: multipart/mixed; boundary=”_000_2c4cf07ee43e4faab98dc52f068a566fDB4PR03MB620eurprd03pro_”
When you try to telnet the Office 365 hub transport from Exchange on-premises server it won’t recognize the telnet commands on the SMTP server.
Resolution:
451 4.4.0 Primary target IP address responded with: “451 5.7.3 Must issue a STARTTLS commnd first” Office 365 Hybrid
If you have an Office 365 hybrid configuration you may experience issues sending emails between on premise and cloud users (in either direction).
The Exchange 2013 (or 2010) on premises queue viewer may show:
‘451 4.4.0 Primary target IP address responded with: “451 5.7.3 STARTTLS is required to send mail.” Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was xxx.xxx.xxx.xxx’
The Office 365 Message Trace Console shows the delivery status of ‘None’
Office 365 Message Trace
The errors suggest the TLS connection cannot be made but a TLS certificate IS present and during the Hybrid Connection Wizard the required connectors are automatically created so should not require an additional configuration.
When an email is sent between on premise & cloud (Office 365) users of your SSO domain it is sent across one of the automatically created send connectors. These connectors are secured using TLS.
So, assuming you have ruled out all the normal stuff its now time to get baffled. We know the on premise server can send and receive external email. We also know that the Office 365 service can send and receive email. It is just the email between the two services that does not work.
I was banging my head against a wall for ages until I used Telnet to connect from my on premise Exchange server to Microsoft cloud gateway.
What I got is shown below:
This is not correct. As you can see the server has not recognised the “ehlo” statement and the banner does not “look right”…
A bit of digging around the firewall I noticed that packets were being dropped when TLS was attempted.
The firewall is a Cisco PIX 515. I disabled ESMTP inspection but that made no difference so I discounted this as the cause.
After a lot more digging around and raging I remembered that the PIX was behind another Cisco firewall – this time an ASA 5510. So I accessed this device and sure enough this edge firewall was also inspecting and dropping TLS over SMTP.
Once both firewall were configured not to inspect ESMTP the default configuration that was set by the Hybrid Configuration Wizard started working straight away.
The commands to disable ESMTP inspection are:
pix(config)#policy-map global_policy pix(config-pmap)#class inspection_default pix(config-pmap-c)#no inspect esmtp pix(config-pmap-c)#exit pix(config-pmap)#exit Now telnet the cloud server and you should see a correct banner:
Before Starting the process of Deploying Dirsync, you must consider using some tools to see if your environment has no issues.
First you must use this tool IdFix check the active directory for any possible issues when installing Dirsync and synchronizing users and their objects to the cloud.
IdFix is used to perform discovery and remediation of identity objects and their attributes in an on-premises Active Directory environment in preparation for migration to Office 365. IdFix is intended for the Active Directory administrators responsible for DirSync with the Office 365 service.
Install ADFS (Optional) for SSO (To authenticate users from Local AD)
Note about ADFS:
ADFS can be the reason of so much headache and it’s always better to avoid installing it, instead of using ADFS to use the same password for users on a large scale deployments, the Dirsync can Synchronize local Passwords to Azure AD and same password can be used for both users local and online.
Create an enterprise admin user account on the domain for DirSync service
Installation of Dirsync with Password synchronization: We prepare a separate server for the DirSync tool that is windows 2008 R2 SP1 or 2012 R2 installed and the server
should be domain joined in order to reach Active Directory.
The account used with Dirsync should be member of the domain admin. Also you need to have the admin credentials for the tenant that you signed up to on O365.
While installing I had an error saying that current user was not member of the Synchronization Engine FIMSyncAdmins group.
I tried uninstall DirSync but it it gives the same error message
The FIMSyncAdmins group is a local group on the server. Your user is not a member of that group locally. Try adding your user to the group.. after adding the user to the required group the installation were completed successfully.
First you need to make sure that your customized (personal) domain is active.
Now we need to enable Dirsync from the portal, next to Active Directory ® Synchronization Click on Set up and activate DirSync.
Now click on Activate
Now after we made sure that our domain is active and we activated Dirsync on Office 365 portal let’s Go back to DirSync server to complete the steps and check if we can start syncing your Active Directory.
Type your enterprise admin user which you have prepared for Dirsync, for my case I’m just going to use the domain admin user since it’s a Lab.
Make sure you Enable Hybrid Deployment since Azure active directory will modify objects in your on-premises AD.
In case you would want to have your On-premises AD password for users synchronized with users on Office 365
then you must tick the option as in the below snapshot.
Here, When I click next I get an error as following:
Error:
The new version of Dirsync doesn’t accept the domain admin account.
Solution:
In order to resolve the problem you have to create a new user account with enterprise admin privileges
Use this account to connect to AD during config.
Here I created the new user and added the required groups.
After using the new account there was no issue with the setup and I could complete the configuration successfully.
Once the configuration finished you will be able to find event ID 611 in the logs.
Now checking Office 365 portal, I can see that users have been synced to the Office 365 portal:
Creating Custom Attributes on On-Premises AD for Exchange Online Users
I have came across some interesting scenario where Exchange Server doesn’t exist however some attributes might be still required or used on Office 365 for Exchange online users which are Synced with Azure Active Directory Sync tool.
The attributes might be used for different purposes but sometimes it’s very necessary so I will go ahead and demonstrate how to create a custom attribute which is normally created by default with Exchange servers deployed on-prem.
First I will run the Schema console
On one of the DC servers which are synced with Office 365 Launch CMD as Administrator
Run the following Command
regsvr32 schmMgmt.dll
Run MMC
Click on File -> ADD /Remove Snap in
Right Click on Attributes -> Create Attribute…
Click on Continue
Click OK
Go to Attributes, Navigate to Custom attributes and double click on it and tick the boxes below then click apply
Now go to Classes
Find and double click on User
Now go to Attributes tab
Click on Add and add the Custom Attribute
Click Apply
Now go back to CMD on DC Server and replicate changes across all DC servers
Matching Users after migrating to new Active Directory Forest
Installing ADConnect in a new forest for the same users which have been migrated to a new Active Directory forest
In order to do so you will have to launch Azure powershell in admin mode and connect to MSOL service as in the following snapshot
$cred = get-credential After connecting then type/copy the following Get-MsolUser -ReturnDeletedUsers -All | Out-GridView
Once you type enter a GUI will come up showing you all the deleted users list, you should delete any old non-usable account that has similar attributes to the ones that you’re about to Sync from the AD to O365.
Once you’re sure about what do you want to delete you can go ahead with the following Command to delete the users
Note: You must be sure that when you run this command, you will no longer be able to restore any deleted item or object later on.
To prepare Azure Active Directory Sync Server, you will need to download the following tools to check for users attributes on your local AD:
Mirosoft Windows Server 2008R2/2012R2
NetFramework 4 (For IDFIX tool to work)
IDFIX (to Check if there’s any issue on AD with DirSync)
Note:
One of the new features that came with AADSync is that it can be installed on the DC server as well. but some may choose to have it on a separate server to avoid any risk.
Software Prerequisites
Install required tools for Azure Active Directory Connector (Dirsync)
NOTE: Effective October 20, 2014, the 32-bit version of Azure Active Directory Module for Windows PowerShell is discontinued. Support for the 32-bit version will no longer occur, and future updates to the Azure Active Directory Module will be released only for the 64-bit version. We strongly recommend you install the 64-bit version to ensure future support and compatibility. Refer to “Install the Azure AD Module” in Manage Azure AD using Windows PowerShell.
If DirSync is to be installed on a server with Windows 2008 R2, beginning with version 1.0.6765.0006, PowerShell 3.0 is required and can be installed from Windows Management Framework 3.0; AND beginning with version 1.0.6985.000, .NET Framework 4.5.1 is a prerequisite.
Once you download IDFIX, you have to unzip and run the exe tool
Right click on Idfix and run it as administrator to give it the required privileges to access AD users and groups.
After you run it, it must look like the following
After running the tool you will have to click on Query to get the problematic users/groups and solve the ones that you want them to be synced to Office 365 Azure AD.
Top Level Domain:
The most common issue that occurs when preparing for AADSYNC is the Top Level domain users related errors (If .local is used)
To Fix this issue for all the users/groups which will be synced to O365 you will have to open Active Directory Domains and Trusts:
Right click on Active directory domains and trusts and click properties then add your public domain to the Alternative UPN Suffixes:
Next open Active directory users and computers to change the UPN to the correct one that matches your public domain.
Note:
Changing the domain suffix for your users suffixes won’t affect their login to their machines or any other application server.
Select the users in which OU that you want it to be synced and right click and choose Properties.
Proxy Address:
You might as well face another issue with users that you intend to sync to Office 365 which is the SMTP proxy address. in some Exchange Organizations the e-mail policy might be set wrong and therefore the user might have an invalid domain value in his proxyaddress attribute e.g. user@domain.local
To solve this, there are 3 ways to solve it. First would be to use Exchange on-premises Email policy to delete the .local SMTP proxy and set the public domain one.
The other two ways would be that you delete the proxyaddress manually or with a powershell script . I personally prefer to do this manually due to avoid any risk that it may impose on the users objects.
Another method would be the IDFIX it self or Admodify.
In the below snapshot I used IDFIX to fix the proxyaddress of the problematic users.
Installation of ADDSYNC
First we’ll install Microsoft Online Services Sign-In Assistant for IT Professionals RTW…
Next Windows Azure AD powershell module
Installing AADirsync
In the next step you will have to enter an Office 365 Global administrator user (preferably not onmicrosoft.com user) and I would recommend that you create a cloud user on Office 365 with global admin privileges to use with AADSYNC.
Next before you continue, you should open your O365 portal and Enable ADSync there.
When you click on Set up the following page should come to you. you should click on Activate AD Sync.
Now you may continue to config AADSYNC, below I am going to use a different user that’s dedicated only to “AADSYNC” tool. I will calll it Dirsynccloud@domain.com
Next On Active directory on-premises I will configure a new user called (Dirsync) that’s member of enterprise admins. this user will have access to all the OUs that will be synced in order to sync their attributes and passwords..etc
Once you enter your Enterprise domain account below and click add forest, it will be enlisted below and you can add additional number of forests if you have more.
Next you may choose to have Hybrid deployment if you have Exchange on-premises (At least Exchange 2010 SP3) but if not then no need to tick the box. The password write-back is a feature that requires an Azure premium AD subscription so if you don’t have this subscription then you don’t really need to tick this box.
The Azure AD app and attribute filtering is a feature that allows you to pick a certain application attribute you want to sync back and forth to Azure AD e.g. (Exchange, SharePoint..etc). If you don’t tick this box the normal standard attributes will be synced which will include (Exchange and user’s basic info) you can find it as soon as the setup finished and you open ADDSync UI.
Password writeback is an Azure Active Directory Sync component that can be enabled and used by the current subscribers of Azure Active Directory Premium. For more information, see Azure Active Directory Editions. It allows you to configure your cloud tenant to write passwords back to you on-premises Active Directory. It obviates you from having to set up and manage a complicated on-premises self-service password reset solution, and it provides a convenient cloud-based way for your users to reset their on-premises passwords wherever they are. Read on for some of the key features of password writeback:
You can enable filtering in AADSync at any time. If you have already run the default configurations of directory synchronization and then configured the filtering, the objects that are filtered out are no longer synchronized to Azure AD. As a result, any objects in Azure AD that were previously synchronized but were then filtered are deleted in Azure AD. If objects were inadvertently deleted because of a filtering error, you can re-create the objects in Azure AD by removing your filtering configurations, and then synchronize your directories again.
Next I will not tick Synchronize now because this will sync All local AD objects and OUs to the cloud, in my case I just want to choose particular OUs to sync to the cloud.
In order to configure AADSYNC to choose which on-premises Active directory Organization Unit you want to change you will have to navigate to the following path on the server which you installed AADSYNC.
PATH:
C:\Program Files\Microsoft Azure AD Sync\UIShell\miisclient.exe
Right click on domain.local and click properties
Next Click on “Configure Directory Partitions” and Under “Credentials” Click on Containers and enter your new on-premises enterprise admin account.
Next select the OU you want to sync to the cloud and click OK
Next you will want to open “Task Scheduler” on the server and Enable the task that was created by AADSYNC installation to enable every 3 hours sync..
In order to Force the sync you will have to run a separate command that Microsoft has brought along with AADSYNC called “DirectorySyncClientCmd” the command can be run from Powershell or made a shortcut on a desktop and directly run.
Path:
c:\Program Files\Microsoft Azure AD Sync\Bin\DirectorySyncClientCmd
These are instructions that demonstrate how to change WordPress to match your replaced or changed Public domain. as this occurs in case if you are already using WordPress and have it published on let’s say Domain1.com and then you transferred this domain to Domain2.com.
When you try to reach wordpress website from your new public domain. you might not reach it or wordpress might try to redirect you to your old domain1.com instead.
In order to fix this, we’ll have to use a tool called wp-cli which fixes this configuration problem. to do so please open your SSH shell or get in your UBuntu server and do the following.
(Automatic desktop wallpaper downloader and customizer), Variety also displays quotes on your desktop along with wallpapers.
2- Cairo dock (shortcut bar to Applications)
3- Shutter (Graphic tool)
Shutter is a graphic tool that can take snapshots, desktop screenshots and edit them or send them to your e-mail.
it’s very powerful and every button on it can be customized with a shortcut by the keyboard. for example if you want to create a shortcut for screen selection (Like the OneNote on Windows) you can simply open the keyboard shortcuts app (mate-keybinding-properties)
Once you have launched the keyboard shortcuts utility, you can customize a new shortcut to take a screenshot for you with Shutter by selection.
You will have to click on Add and create a new shortcut as following
Once you click apply, you can assign the shortcut for this command.
For example, I am using the shortcut CTRL + SHIFT + S
4- Remote Desktop tools
A- NoMachine
NoMachine is a free and very powerful remote desktop utility that works on all Operating systems and supports all kinds of features that are available in other remote desktop utlities like (Radmin, Teamviewer, RDP).
After installation, you need to go through one-time configuration which involves granting onedrive-d read/write access to your OneDrive account.
First, create a local folder which will be used to sync against a remote OneDrive account.
$ mkdir ~/onedrive
Then run the following command to start the first-time configuration.
$ onedrive-d
It will pop up a onedrive-d’s Settings window as shown below. In “Location” option, choose the local folder you created earlier. In “Authentication” option, you will see “You have not authenticated OneDrive-d yet” message. Now click on “Connect to OneDrive.com” box.
It will pop up a new window asking you to sign in to OneDrive.com.
After logging in to OneDrive.com, you will be asked to grant access to onedrive-d. Choose “Yes”.
Coming back to the Settings window, you will see that the previous status has changed to “You have connected to OneDrive.com”. Click on “OK” to finish.
Sync a Local Folder with OneDrive
There are two ways to sync a local folder with your OneDrive storage by using onedrive-d.
One way is to sync with OneDrive manually from the command line. That is, whenever you want to sync a local folder against your OneDrive account, simply run:
$ onedrive-d
onedrive-d will then scan the content of both a local folder and a OneDrive account, and make the two in sync. This means either uploading newly added files in a local folder, or downloading newly found files from a remote OneDrive account. If you remove any file from a local folder, the corresponding file will automatically be deleted from a OneDrive account after sync. The same thing will happen in the reverse direction as well.
Once sync is completed, you can kill the foreground-running onedrive-d process by pressing Ctrl+C.
Another way is to run onedrive-d as an always-on daemon which launches automatically upon start. In that case, the background daemon will monitor both the local folder and OneDrive account, to keep them in sync. For that, simply add onedrive-d to the auto-start program list of your desktop.
When onedrive-d daemon is running in the background, you will see OneDrive icon in the desktop status bar as shown below. Whenever sync update is triggered, you will see a desktop notification.
6- Evolution Email Client for Exchange accounts.
If you ever thought of using an e-mail client that supports your account on Microsoft Exchange Email server’s protocol which is known as (RPC over HTTP) then you have probably used Mozilla thunderbird or kmail, geary..etc but all those clients don’t support Exchange’s most flexible connectivity which is RPC over HTTP that will sync all your emails, contacts, tasks, calendars ..etc
To Install evolution, all you have to do is open Linux Terminal and type the following
Sudo apt-get install evolution
Since I already have Evolution installed it won’t proceed and will tell me that it’s already installed. but that’s not all!
In order to setup an Exchange account on Evolution you will have to install an Evolution plugin that will support the web services for the RPC over http connectivity which is known as (EWS = Exchange Web Services).
In order to install this plugin you will have to type the following command
Sudo apt-get install Evolution-ews
Once you install the plugin, you can launch the program and setup your account as following.
Click on Add as in the picture
When you click add you should be welcomed by a message saying “Welcome to Evolution wizard ..etd”
Click Continue and then type in your name and email address in the next window
You can skip the automatic configuration as Evolution still doesn’t support Exchange Autodiscover mechanism for auto configuration of the account. so you must manually provide all the configuration of your exchange as following
In the host URL you will have to provide your Exchange server’s EWS URL which usually looks like this
For the OAB (Offline Address Book) you also need to provide the configured URL of the OAB on your Exchange Server. which in my case again it’s Microsoft Office 365.
you will need to make sure that the correct authentication method is set (NTLM) in my case, this can vary though on Exchange server’s Outlook Anywhere configuration. it can be Basic as well. so it’s up to your configuration to choose but for Office 365 it’s NTLM.
Once you finish the configuration you can continue and you’ll get prompted to enter your Credentials. as soon as you finish typing your Password hit enter and your e-mails will start syncing. as in the following snapshot
That’s it, you’re setup here either if it’s an exchange on-premises or Office 365 for Linux desktop client.
Here’s another guide for the new mapi connectivity for Evolution, probably the same steps
7- For Office (Word, Powerpoint ..etc) I prefer to use Kingsoft’s community version along with LibreOffice
Since Libre office provide more tools or the full package I still use it on Linux but Kingsoft’s WPS tools have a user friendly and rich of tools GUI.
In order to download WPS software you will have to navigate to the link below and download the suitable version with your Linux OS. or use the terminal to download latest available version with the following command
8- For media there are various available software and tools that you can use on Linux to either listen to music or edit mp3s or convert media types.
A- Audacity (Convert and Edit audio files).
B- Spotify (listen to music online)
C- Clementine (Listen to Music on your computer)
D- VLC (Watch Videos on your PC) or use it as a streaming server.
There are other useful tools and things to do on Linux OS as it’s a very flexible and customizable OS but I’ll end this article here and write a new one about how to decorate your welcome screen and your desktop with beautiful pictures and tools.
![clip_image001[5]](http://lh6.ggpht.com/-bTsYbCoyBDE/VSe6tby9vwI/AAAAAAAAORQ/7oMFwn6XVWs/clip_image001%25255B5%25255D_thumb.png?imgmax=800)
![clip_image002[4]](http://lh4.ggpht.com/-Tc_IjdCkie4/VSe6vTh70nI/AAAAAAAAORg/DaVeYIKS1F4/clip_image002%25255B4%25255D_thumb.png?imgmax=800)
![clip_image003[4]](http://lh4.ggpht.com/-5paj8WsOWZs/VSe6xkWuhKI/AAAAAAAAORw/ZkFYGWVxNeM/clip_image003%25255B4%25255D_thumb.png?imgmax=800)
![clip_image004[4]](http://lh4.ggpht.com/-dn2f9cdUKEo/VSe60bcnjYI/AAAAAAAAOSA/du-W37Jv-jM/clip_image004%25255B4%25255D_thumb.png?imgmax=800)
![clip_image005[4]](http://lh6.ggpht.com/-pnvgRPt6_n4/VSe62yUPVgI/AAAAAAAAOSQ/P5WUuU98X90/clip_image005%25255B4%25255D_thumb.jpg?imgmax=800)
![clip_image006[4]](http://lh5.ggpht.com/-lg6fVFgFc8o/VSe65oCP2kI/AAAAAAAAOSg/8ouI0xFaxPY/clip_image006%25255B4%25255D_thumb.jpg?imgmax=800)
