As you already know, Microsoft updates frequently the DirSync tool used to synchronize your on premises directory with Office 365.
Also, as Microsoft has announced the availability of the S/MIME feature on Exchange 2013 SP1 – and so also for Exchange Online on Office 365, you will have to update your DirSync currently installed.
Download the new version here http://go.microsoft.com/fwlink/?LinkID=278924 – version involved for this post is 1.0.6635.43
Then you have the choice to upgrade the existing installation or uninstalling the installed version one before installing the new one.
NOTE if you uninstall the installed version, you user will continue to be present on Office 365, only updates (new users, details updates) will be synchronize once the new version will be installed.
Then, once the new version has been installed (whatever the process used), open the MIIS client console; run the miisclient.exe file available within C:\Program Files\Windows Azure Active Directory Sync\SYNCBUS\Synchronization Service\UIShell directory.
to confirm/reconfigure your synchronization filtering.
Then check if the userSMIMECertificate attribute is present and enabled; if not present you are not using the correct version of DirSync, if not enabled just enable it.
To check this, go through the MIIS console to the Select Attributes section of the Active Directory management agent (Active Directory Connector)
Microsoft has published some sample PowerShell scripts to help you managing Office 365 and Lync.
These scripts will connect to your Office 365 tenant, display your users list, manage user settings or manage domains and more.
As prerequisite, you must have installed Microsoft Online Sign In Assistant, PowerShell Module for Windows Azure Active Directory, Lync PowerShell and the Framework 4.5
Go to http://www.microsoft.com/en-us/download/details.aspx?id=41953 for download the scripts
With the February 2014 updates, Microsoft has improved a little bit the SkyDrive experience.
As you already know, SkyDrive is now fully integrated within Windows client and this integration has introduced some bad experience.
With the KB 2923768, Microsoft has started to improve this user experience. As part of this KB, a new icon will be displayed in the systray to display current state of the SkyDrive – as we had with the previous SkyDrive client.
Unfortunately, it is still required to logon on Windows 8 with a Microsoft account to be able to use SkyDrive…
Microsoft has released a new version of the Lync Connectivity Analyzer, a tool which helps to determine if the deployment and the configuration of Office 365 (Lync Online) and Lync On Premises match the prerequisites to support connectivity.
Go to http://go.microsoft.com/fwlink/?LinkId=277056 to download the tool.
As part of the improvements:
More details available here http://blogs.technet.com/b/nexthop/archive/2014/01/21/announcing-the-release-of-the-updated-lync-connectivity-analyzer.aspx
Recently, I went to an error when moving online mailboxes from Office 365 – Exchange Online – to on premises – Exchange 2013.
Strangely, these mailboxes have been moved multiple times in both direction – on premises to online and online to on premises – without any issue.
The migration batch starts and content is being synchronized between Exchange Online and Exchange On Premises and finally the job failed with the error
Error: MigrationPermanentException: Error: Resource 'CiAgeOfLastNotification(System)' is unhealthy and shouldn't be accessed
After some digging, the issue was due to a corrupted index on Exchange On Premises.
If you are using Office 365 and have implemented ADFS to manage the authentication to Office 365 services, this post is for you
You may get the following error code – 8004789A – when logging on to Office 365 with web browser (Exchange Online OWA or SharePoint Online), while Outlook or any ActiveSync device is working fine
The solution is simple:
check if the Issuer (URI) URL is set to HTTPS; if the answer is yes, you have to change the configuration to use HTTP only
run the following command from a PowerShell window on the ADFS server
Add-PSSnapin Microsoft.Adfs.PowerShell Set-ADFSProperties -Identifier "http://<your ADFS URL>/adfs/services/trust" Restart-Service adfssrv
Also on the TMG side, check if the following settings are correctly set:
Today, Microsoft has announced an update regarding the ForeFront product line.
After announcing the end of ForeFront TMG and ForeFront Protection – see http://blog.hametbenoit.info/Lists/Posts/Post.aspx?ID=422, Microsoft is now ending ForeFront UAG too.
ForeFront UAG will be removed from the catalog in July 2014; as for ForeFront TMG, support will be maintained until the end of his lifecycle – until April 2015 for standard support and April 2020 for extended support.
Customer will have rights to upgrade to Windows Server 2012 R2 to replace ForeFront UAG by using publication features introduced with 2012 R2.
See all the details here http://blogs.technet.com/b/server-cloud/archive/2013/12/17/important-changes-to-the-forefront-product-line.aspx
A new administration option is available for SharePoint Online administrators to manage SkyDrive Pro storage allocation
Go to your SharePoint Online administration portal using the Admin menu from the Office 365 portal or use the direct URL https://<your tenant>-admin.sharepoint.com
Then, on the left side, go to the new SkyDrive Pro section
Then you will be able to change the storage allocation – from 25 Gb to 100 Gb – by entering the email address(es) of the user(s) to be impacted by this storage allocation change
On the top right, you will also be able to see the global storage allocation for your tenant and the storage currently consumed
Following the announcement and then the availability for Office 365 Enterprise plan of Yammer (see http://blog.hametbenoit.info/Lists/Posts/Post.aspx?ID=571 to activate Yammer on your Office 365 subscription), you may want to add Yammer on the top navigation bar
To do so, it’s really simple.
Just logon to your Office 365 administration portal and go to the SharePoint administration from the Admin menu or use the direct URL https://<your tenant>-admin.sharepoint.com
Then go to the Settings section from the left side and switch from the SharePoint Newsfeed to Yammer as Enterprise Social Collaboration
Wait a little et voilà Yammer is now displayed on the top navigation bar
If you click on this link, you will be redirected to your enterprise Yammer network
Recently, I tried to deployed the latest cumulative update release for Exchange 2013 as well as implement hybrid configuration with my Office 365 which was finally fully upgraded – I say fully upgraded because even after receiving the notification of my tenant has been upgraded to latest version there was still a component running on older version, I mean FOPE.
After raising a service request to Office 365 support and fight a lot, I finally get FOPE upgraded; but this is not the point of this post.
Just after that I wanted to implement hybrid configuration between my Exchange 2013 On Premises and my Office 365 tenant. Off course I had prepare everything to get smooth implementation (I mean a public certificate for my on premises).
Unfortunately, when I tried to implement this hybrid configuration I quickly ran to a strange issue: hybrid configuration wizard quickly failed after starting the implementation with the following error Property Enabled can't be set on this object because it requires the object to have version 0.10 (126.96.36.199) or later. The object's current version is 0.0 (6.5.6500.0).
The wizard did not complete successfully. Please see the list below for error details.
Updating hybrid configuration failed with error 'Subtask Configure execution failed: Configure Organization Relationship Execution of the Set-FederatedOrganizationIdentifier cmdlet has thrown an exception. This may indicate invalid parameters in your hybrid configuration settings. Property Enabled can't be set on this object because it requires the object to have version 0.10 (188.8.131.52) or later. The object's current version is 0.0 (6.5.6500.0). at Microsoft.Exchange.Management.Hybrid.RemotePowershellSession.RunCommand(String cmdlet, SessionParameters parameters, Boolean ignoreNotFoundErrors) '. Additional troubleshooting information is available in the Update-HybridConfiguration log file on server
At the same time, the Exchange Product Group released the latest cumulative update – CU 3 – which also failed to install with the same error.
Strangely, CU 2 has been installed successfully.
Luckily, I had my service request to Office 365 support was still open and they were able to assist me by involving the Exchange support.
Microsoft Exchange support engineer asked me to check the value of the msExchVersion attribute for the Federation container
In my case, this attribute had no value. So, I have been asked to enter the following value 44220983382016.
After setting the value, I have been able to complete the hybrid configuration as well as the installation of the CU 3.