WAAD version 4.3.647.0 seems to have moved the powershell module for manual syncs. To put the shortcut back on the desktop of your WAAD Server. Simply create a new shortcut and paste in the details below and then type start-onlinecoexistencesync to perform a manual sync
powershell.exe -noexit -noprofile -file "C:\Program Files\Windows Azure Active Directory Sync\DirSync\ImportModules.ps1"
It would be great if when you click the Yammer icon in the Office365 services ribbon it actually signs you into Yammer rather than redirecting you to Yammer.com.
This blog will detail how to setup single sign on to Yammer via Microsoft Windows Azure Active Directory. When SSO for Yammer is enabled with Azure AD there is no on premise ADFS requirements.
Every Office365 Subscription also has a Windows Azure tenant in the background.When signed into an Office365 tenant , open a new tab and browse to this URL https://manage.windowsazure.com/ and signup for a free trial.
You will need a credit card when signing up however there will be no charge to the credit card.
Browse to the Active Directory section in the Azure Management Portal and then select "Add Application" and "Add an application my organization is developing" as per the image below.
Name your application as per image below
Then enter your sign-on url & app id uri as per image below
You then select "ENABLE USERS TO SIGN ON" and then browse to the "FEDERATION METADATA DOCUMENT URL" and save the metadata xml file as per image below.
Next we need to connect Windows Azure Active Directory via powershell and run the following commands
The command will output an "AppPrincipalId" take note of this value and save it into a text file.
Then you will need to fill in the Yammer SSO-Checklist.docx which you can download HERE
We now create a Service Request as per image below
We then create a compressed file that contains the FederationMetadata.xml, the AppprincipalId and the SSO Checklist and attach the file to the service request.
Once Yammer Support enable Single Sign On for your Yammer network. When you click on the Yammer link from the Office365 portal it will sign you into Yammer :) Or when you browse to your Yammer SSO URL like https://www.yammer.com/ergogroup.ie
If you sign into Yammer , You can then open a new tab to access portal.microsoftonline.com or a Sharepoint Online site without having to re-authenticate. All this with no - on premise ADFS!
When I first began to work with Office365 ProPlus click to run I couldn't get my head around how to deploy Office in a software as a service model and to deploy it in bulk in Enterprise organisations.
It really is quite simple and I hope this post will help people to deploy Office365 ProPlus and OneDrive for Business with ease.
So to create two distribution points for Office365 Pro Plus and OneDrive for Business we do the following.
Download the Office Deployment tool for Click to Run HERE
We then need to create a configuration file.
#This is the configuration file for OneDrive for Business which will be saved as odfb.xml
#This is the configuration file for Office365 ProPLus which will be saved as office.xml
So we create a folder for each product that contains the Office Deployment tool and run the following command to download the source files.
setup.exe /download office.xml
#OneDrive for Business
setup.exe /download odfb.xml
If you do not have Microsoft System Center Configuration Manager and want to deploy it via a batch file you could use a batch file like this.
echo /* Installing Office 365
net use q: \\fileshare
Setup.exe /CONFIGURE OFFICE.xml
net use q: /delete /yes
For people that are fortunate enough to have Microsoft System Center Configuration Manager. Here is a quick VIDEO on how to add Office365 ProPlus and OneDrive for Business into your Application Catalog.
I recently had a problem with an Exchange Online tenant. There was an external mail contact which was previously synchronised from Active Directory to Exchange Online. So I had deleted the on-premise active directory mail contact but it still existed in Exchange Online. When I tried to delete the contact it gave the following errror message. The action 'Remove-MailContact', 'Identity', can't be performed on the object 'Sean OFarrell ' because the object is being synchronized from your on-premises organization. This action should be performed on the object in your on-premises organization.
To trouble shoot this issue you can do a couple of things to ensure the external contact does not exist in your on premise Active Directory.
Perform a custom search in ADUC: Search Syntax : proxyaddresses=SMTP:email@example.com
Search the WAAD Mettaverse
Run this command on the Exchange Onpremise management shell remove-mailcontact firstname.lastname@example.org
So if after running all of the above steps you cannot find the external contact which is causing the issues. You do the following.
In Exchange Online Run this command : get-mailcontact email@example.com | fl
Take note of the attribute value: ExternalDirectoryObjectId
In this example the externaldirectoryobjectid is 2cb3d9c7-cb29-439f-8174-6c80dd9fe6e8
Then connect to Windows Azure Ad via Powershell and run this command get-msolcontact -objectid2cb3d9c7-cb29-439f-8174-6c80dd9fe6e8| remove-msolcontact
Problem solved. Now run a delta sync on your WAAD server and everything will work fine.
If you you upgraded a Dirsync Server to the newer WAAD sync tool and the original configuration was syncing the full AD forest then when you upgrade to the newer version. You need to perform a full synchronisation with the complete AD Forest.
After the full sync completes , You can then filter the OU's and they will be deleted from Syncing with Office365.
I recently had an issue whereby the objects in the OU's that I had filtered were not getting removed from my Office365 tenant. So to resolve the issue , I performed the steps above.
Once complete , Run the powershell command below to clear out the Office365 recycle bin.
I recently uninstalled DirSync from a customer site where DirSync was installed using SQL Server and not SQL Express. I launched dirsync /fullsql and tried to launch 'DirSyncInstallShell.psc1' and got the error message above. The fix was really simple , Download and install Powershell 3.0 on Windows Server 2008R2