John Yassa's Blog

Home » 2015 (Page 2)

Yearly Archives: 2015

Enable or Disable Clutter for Office 365 Users

After understanding what is Office 365 Clutter , we are going to illustrate how can you enable or disable Clutter for Office 365 user or all users

You have to know that this can be done through PowerShell

Connect to Office 365 using PowerShell

To enable clutter for one user run:

Set-Clutter -Identity user@domain.com -Enable $true

To disable clutter for one user run:

Set-Clutter -Identity user@domain.com -Enable $false

To enable clutter for all users run:

Get-Mailbox | Set-Clutter -Enable $true

To disable clutter for all users run:

Get-Mailbox | Set-Clutter -Enable $false


How to find out who has clutter enabled or disabled

You can use the script attached here to Export all Office 365 users Clutter status to a CSV file

This PowerShell script connects to Office 365 and lists out all mailboxes and shows you if each user has Clutter enabled or disabled for their mailbox.

Sources: Cogmotive Blogs

 

 

What is Office 365 Clutter ?

Clutter is an email filtering option available to Office 365 customers.  It is similar to an anti-spam filter as it moves less important email (based on your reading habits) into a ‘Clutter’ folder where they can be ignored or reviewed later.  Most of the mail going into the folder should be bulk mail (advertisements) and messages from mailing lists.  However, you will want to periodically check the Clutter folder as it may move legitimate email into this folder.

How Clutter filters messages

Clutter and junk email are both filtered out before they reach your Inbox. Junk email is evaluated and filtered first, then Outlook processes the rules (if you have set up any). Next, Clutter analyzes the remaining messages and filters out the types of messages that you usually ignore or don’t respond to, based on your past behavior.

Messages from certain people will never be identified as clutter:

  • You
  • Anyone in your management chain
  • Your direct reports

Clutter looks at various aspects of messages to understand what you don’t typically read, for example:

  • The sender
  • Whether you’ve participated in the conversation
  • If you’re the only recipient
  • The importance

As your reading habits change, Clutter learns and adapts.

How Clutter will look like in Outlook ?

clutter outlook

 

How Clutter will look like in OWA?

clutter OWA

If you are using OWA and need to mark messages as “not clutter”,  either right click on the message and choose ‘Mark as not clutter’ or just drag it to the Inbox. If Exchange is missing messages you want marked as clutter, right click and choose ‘Mark as clutter’ or drag it to the Clutter folder. In Outlook and other clients, you’ll need to drag a message to the clutter folder to mark it as clutter or drag it to the Inbox to mark it not clutter.

Users can drag messages they deem suitable to the Clutter folder to “train” the tool to spot similar email in the future. The tool gets smarter over time, learning from your prior actions with similar messages.

Once Clutter is enabled in OWA, it appears in other clients linked to that Exchange account, including Outlook on both Windows and OS X desktops and notebooks, and the iPhone and Android OWA apps.

Note:  If you have rules moving messages, Clutter is applied after server-side rules are applied and items touched by rules won’t be filtered by clutter.

 

Sources: Article, MS support

New IT management controls added to OneDrive for Business

The OneDrive for Business team has been working to deliver the most commonly requested controls by IT admins. Today, we’ll highlight new management options you have to protect and control the flow of your information using OneDrive for Business.

1- Limiting file sync to domain joined PCs

One of the most common requests from IT admins is to have the ability to block sync on un-managed PCs

Now you can enable file sync to work only on domain-joined PCs (and you can even specify which of your domains you want to allow to sync)

Note that using this setting means that you will disable file sync on all Macs as they cannot be domain-joined and managed like PCs.

The PowerShell cmdlet and syntax you use is: Set-SPOTenantSyncClientRestriction  -Enable -DomainGuids “786548DD-877B-4760-A749-6B1EFBC1190A; 877564FF-877B-4760-A749-6B1EFBC1190A”

The “DomainGuids” value represents the domain you are allowing

2- Auditing all actions taken against OneDrive for Business files

New auditing controls rolling into the Office 365 compliance center allow you to audit all actions taken against files stored in OneDrive for Business. If you want to monitor activities like which PCs or Macs attempted to sync with OneDrive or who viewed and shared files, the auditing controls provide that visibility

3- Managing mobile devices connecting to OneDrive for Business data

As more people move to OneDrive for Business to store and access their files, email-based mobile device management (MDM) policies may not suffice to protect data. Now using MDM in Office 365, you can ensure that devices connecting to your OneDrive for Business data are managed

4- Setting storage quotas in OneDrive for Business

Several organizations have requested the ability to set smaller quota limits. It could be to limit the amount of data stored, for information protection reasons, or simply to ensure that what people store in OneDrive for Business can sync (and fit) on their PC’s hard drive.

In this case, PowerShell is again used to determine the storage quota.

“SetSPOSiteIdentity https://yourdomain-my.sharepoint.com/personal/username_yourdomain_com StorageQuota 512000″
Sources: Office Blogs

 

 

 

 

 

 

Microsoft Exchange Server 2016 – Preview

Microsoft Exchange Server 2016 brings a new set of technologies, features, and services to Exchange Server. Its goal is to support people and organizations as their work habits evolve from a communication focus to collaboration. Exchange Server 2016 helps lower the total cost of ownership whether you deploy on-premises or provision your mailboxes in the cloud. This release is not approved for production use and should be installed in a lab environment only.

Supported Operating System

Windows Server 2012, Windows Server 2012 R2

.Net Framework: 4.5.2 Internet Explore 11, Microsoft Edge, Apple Safari (Latest), Google Chrome (Latest), Mozilla Firefox          (Latest)

Install Instruction

  1. Click the Download button on this page to start the download.
  2. Do one of the following:
    • To start the installation immediately, click Open or Run this program from its current location.
    • To copy the download to your computer for installation at a later time, click Save or Save this program to disk.

Download: Microsoft Exchange Server 2016 – Preview

More Info: Exchange 2016 (preview) now available for testing

 

Microsoft announces archiving for non-Microsoft data in Office 365

Today, Office 365 helps customers stay compliant with an archiving solution that covers email, documents in SharePoint and OneDrive for Business, and Skype for Business meetings and conversations. But, our customers require and have asked for more—they want Office 365 to provide the same rich archiving capabilities over non-Microsoft data sources, such as social and messaging data, as well.

To accommodate customers who require archiving of non-Microsoft data in Office 365, we are pleased to announce new partnerships with two popular vendors in the archiving space: Actiance and Globanet.

1

Thanks to extensive collaboration and deep integration with Actiance and Globanet, Office 365 extends its rich and comprehensive archiving solution to cover a wide array of third-party data sources:

  • Social — Twitter, Facebook, Yammer, LinkedIn, etc.
  • Instant messaging — Yahoo Messenger, GoogleTalk, Cisco Jabber, etc.
  • Document collaboration — Box, DropBox, etc.
  • Verticals — SalesForce Chatter, Thomson Reuters, Bloomberg, etc.
  • SMS/text messaging — BlackBerry, MobileGuard, etc.

The entire compliance stack in Office 365—eDiscovery, Retention, Hold and Auditing—will have access to these new data sources. Both Microsoft as well as non-Microsoft data will be treated alike throughout the system

Partners are doing work to integrate their products seamlessly with Office 365. By simply indicating Office 365 as an archiving destination in their products, customers will be able to immediately capture data from numerous data sources. There is no need for any additional configuration in Office 365. All captured data flows into Office 365’s auto-expanding archives. Once data is housed in Office 365, it is fully available to the Compliance tools that our customers are familiar with. Using our eDiscovery and Equivio analytics tools, customers will be able to search, preview and conduct extensive reviews on all ingested data and associated properties. Customers will be able to define retention policies for specific data sources—such as “Delete Facebook data after one year” and so on. And finally, every incoming piece of data, regardless of type or source, will be fully tracked and logged by our comprehensive Auditing tools, with full transparency to customers.

An early preview of our upcoming eDiscovery experience in Office 365 with native support for non-Microsoft data:

Announcing-archiving-for-non-Microsoft-data-in-Office-365-1 (1)

Source: Office Blogs

Finally granular administrative roles are now available in Office 365

Since Microsoft lunched Office 365 , granular administrative roles was a request from most of their clients

Lets assume that i have an E3 plan , and i have an outsource company to develop my Intranet based on SharePoint Online , the only way to give them permission to do that is to provide them Global administrator permission , which is impossible.

Now Microsoft has fixed this issue by providing new administrative roles ( Exchange administrator – SharePoint administrator – Skype for business administrator)

Enter granular administrative roles to provide Office 365 tenants with a method of assigning control over different parts of Office 365 to specific users. Tenant administrators remain all-powerful, but now they have a chance to share their power with others.

The source of authority for granular management roles lies in groups held in Azure Active Directory (AAD). You can’t see these groups through the AAD console and have to work with them using the Office 365 Admin console or PowerShell. You can see the available roles by running the Get-MsOlRole cmdlet. This command lists the available roles – the ObjectId property is important because you will use it to interact with roles in other places.

2

To assign a user account one of these roles, go to the Office 365 Admin Center, select the account in the Users section, and edit it. Go to Roles and select “Limited admin access” as shown in the screen shot below

You can assign Multiple roles to one user

1

You can also use PowerShell to add user accounts to administrative roles. For instance, here’s how t add a new Exchange Online administrator:

Add-MsOlRoleMember –RoleName ‘Exchange Service Administrator’ –RoleMemberEmailAddress ‘John.yassa@johnyassa.com’

After you assign the user the granular permission , allow him a couple of minutes , he should be able to log-on and see the administrative interfaces as below:

3

 

Sources:  Granular administrative roles appear in Office 365

 

 

 

 

Unable to Sync Hash of users’ password with Azure AD using AAD Sync service

After downloading the new Microsoft Azure Active Directory Sync Services (AADSync tool) from the URL Download, i faced a very wired issue, all functions was working properly syncing to the cloud from on premise and also write back password was working fine except the Password synchronization to the cloud , it was not working at all  even after the full initial sync

I found the below event log in the application log

Log Name: Application
Source: Directory Synchronization
Date: 5/5/2015 12:50:50 PM
Event ID: 611
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: AADsyncserver1.xxxxxxx.com
Description:
Password synchronization failed for domain: xxxxxxx.com. Details:
Microsoft.Online.PasswordSynchronization.SynchronizationManagerException: Unable to open connection to domain: xxxxxxx.com. Error: There was an error creating the connection context. —> Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsException: There was an error creating the connection context. —> System.MissingMethodException: Method not found: ‘IntPtr System.Runtime.InteropServices.Marshal.GetFunctionPointerForDelegate(!!0)’.
at Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsRpcConnectionContext.CreateDrsHandle(Void* rpcBindingHandle, SafePointer<_SEC_WINNT_AUTH_IDENTITY_W> authHandle)
at Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsRpcConnection.CreateConnectionContext(SourceDomainController sourceDomain)
— End of inner exception stack trace —
at Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsRpcConnection.CreateConnectionContext(SourceDomainController sourceDomain)
at Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsConnection.EstablishConnection()
at Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsConnection.Connect()
at Microsoft.Online.PasswordSynchronization.RetryUtility.<>c__DisplayClass1.<ExecuteWithRetry>b__0()
at Microsoft.Online.PasswordSynchronization.RetryUtility.ExecuteWithRetry[T](Func`1 operation, Func`1 shouldAbort, RetryPolicyHandler retryPolicy)
at Microsoft.Online.PasswordSynchronization.PasswordSynchronizationTask.OpenConnection(IDrsConnection connection)
— End of inner exception stack trace —
at Microsoft.Online.PasswordSynchronization.PasswordSynchronizationTask.OpenConnection(IDrsConnection connection)
at Microsoft.Online.PasswordSynchronization.PasswordSynchronizationTask.CreateConnection()
at Microsoft.Online.PasswordSynchronization.RecoveryTask.SynchronizeCredentialsToCloud()
at Microsoft.Online.PasswordSynchronization.PasswordSynchronizationTask.SynchronizeSecrets()
at Microsoft.Online.PasswordSynchronization.SynchronizationExecutionContext.SynchronizeDomain()
at Microsoft.Online.PasswordSynchronization.SynchronizationManager.SynchronizeDomain(SynchronizationExecutionContext syncExecutionContext)
Microsoft.Online.PasswordSynchronization.SynchronizationManagerException: Unable to open connection to domain: xxxxxxx.com. Error: There was an error creating the connection context. —> Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsException: There was an error creating the connection context. —> System.MissingMethodException: Method not found: ‘IntPtr System.Runtime.InteropServices.Marshal.GetFunctionPointerForDelegate(!!0)’.
at Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsRpcConnectionContext.CreateDrsHandle(Void* rpcBindingHandle, SafePointer<_SEC_WINNT_AUTH_IDENTITY_W> authHandle)
at Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsRpcConnection.CreateConnectionContext(SourceDomainController sourceDomain)
— End of inner exception stack trace —
at Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsRpcConnection.CreateConnectionContext(SourceDomainController sourceDomain)
at Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsConnection.EstablishConnection()
at Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsConnection.Connect()
at Microsoft.Online.PasswordSynchronization.RetryUtility.<>c__DisplayClass1.<ExecuteWithRetry>b__0()
at Microsoft.Online.PasswordSynchronization.RetryUtility.ExecuteWithRetry[T](Func`1 operation, Func`1 shouldAbort, RetryPolicyHandler retryPolicy)
at Microsoft.Online.PasswordSynchronization.PasswordSynchronizationTask.OpenConnection(IDrsConnection connection)
— End of inner exception stack trace —
at Microsoft.Online.PasswordSynchronization.PasswordSynchronizationTask.OpenConnection(IDrsConnection connection)
at Microsoft.Online.PasswordSynchronization.PasswordSynchronizationTask.CreateConnection()
at Microsoft.Online.PasswordSynchronization.RecoveryTask.SynchronizeCredentialsToCloud()
at Microsoft.Online.PasswordSynchronization.PasswordSynchronizationTask.SynchronizeSecrets()
at Microsoft.Online.PasswordSynchronization.SynchronizationExecutionContext.SynchronizeDomain()
at Microsoft.Online.PasswordSynchronization.SynchronizationManager.SynchronizeDomain(SynchronizationExecutionContext syncExecutionContext)
Microsoft.Online.PasswordSynchronization.SynchronizationManagerException: Unable to open connection to domain: xxxxxxx.com. Error: There was an error creating the connection context. —> Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsException: There was an error creating the connection context. —> System.MissingMethodException: Method not found: ‘IntPtr System.Runtime.InteropServices.Marshal.GetFunctionPointerForDelegate(!!0)’.
at Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsRpcConnectionContext.CreateDrsHandle(Void* rpcBindingHandle, SafePointer<_SEC_WINNT_AUTH_IDENTITY_W> authHandle)
at Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsRpcConnection.CreateConnectionContext(SourceDomainController sourceDomain)
— End of inner exception stack trace —
at Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsRpcConnection.CreateConnectionContext(SourceDomainController sourceDomain)
at Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsConnection.EstablishConnection()
at Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsConnection.Connect()
at Microsoft.Online.PasswordSynchronization.RetryUtility.<>c__DisplayClass1.<ExecuteWithRetry>b__0()
at Microsoft.Online.PasswordSynchronization.RetryUtility.ExecuteWithRetry[T](Func`1 operation, Func`1 shouldAbort, RetryPolicyHandler retryPolicy)
at Microsoft.Online.PasswordSynchronization.PasswordSynchronizationTask.OpenConnection(IDrsConnection connection)
— End of inner exception stack trace —
at Microsoft.Online.PasswordSynchronization.PasswordSynchronizationTask.OpenConnection(IDrsConnection connection)
at Microsoft.Online.PasswordSynchronization.PasswordSynchronizationTask.CreateConnection()
at Microsoft.Online.PasswordSynchronization.RecoveryTask.SynchronizeCredentialsToCloud()
at Microsoft.Online.PasswordSynchronization.PasswordSynchronizationTask.SynchronizeSecrets()
at Microsoft.Online.PasswordSynchronization.SynchronizationExecutionContext.SynchronizeDomain()
at Microsoft.Online.PasswordSynchronization.SynchronizationManager.SynchronizeDomain(SynchronizationExecutionContext syncExecutionContext)
.

xxxxxxx.com
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”&gt;
<System>
<Provider Name=”Directory Synchronization” />
<EventID Qualifiers=”0″>611</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime=”2015-05-05T09:50:50.000000000Z” />
<EventRecordID>15413</EventRecordID>
<Channel>Application</Channel>
<Computer>QinvestADSYNC01.xxxxxxx.com</Computer>
<Security />
</System>
<EventData>
<Data>Password synchronization failed for domain: xxxxxxx.com. Details:
Microsoft.Online.PasswordSynchronization.SynchronizationManagerException: Unable to open connection to domain: xxxxxxx.com. Error: There was an error creating the connection context. —&gt; Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsException: There was an error creating the connection context. —&gt; System.MissingMethodException: Method not found: ‘IntPtr System.Runtime.InteropServices.Marshal.GetFunctionPointerForDelegate(!!0)’.
at Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsRpcConnectionContext.CreateDrsHandle(Void* rpcBindingHandle, SafePointer&lt;_SEC_WINNT_AUTH_IDENTITY_W&gt; authHandle)
at Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsRpcConnection.CreateConnectionContext(SourceDomainController sourceDomain)
— End of inner exception stack trace —
at Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsRpcConnection.CreateConnectionContext(SourceDomainController sourceDomain)
at Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsConnection.EstablishConnection()
at Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsConnection.Connect()
at Microsoft.Online.PasswordSynchronization.RetryUtility.&lt;&gt;c__DisplayClass1.&lt;ExecuteWithRetry&gt;b__0()
at Microsoft.Online.PasswordSynchronization.RetryUtility.ExecuteWithRetry[T](Func`1 operation, Func`1 shouldAbort, RetryPolicyHandler retryPolicy)
at Microsoft.Online.PasswordSynchronization.PasswordSynchronizationTask.OpenConnection(IDrsConnection connection)
— End of inner exception stack trace —
at Microsoft.Online.PasswordSynchronization.PasswordSynchronizationTask.OpenConnection(IDrsConnection connection)
at Microsoft.Online.PasswordSynchronization.PasswordSynchronizationTask.CreateConnection()
at Microsoft.Online.PasswordSynchronization.RecoveryTask.SynchronizeCredentialsToCloud()
at Microsoft.Online.PasswordSynchronization.PasswordSynchronizationTask.SynchronizeSecrets()
at Microsoft.Online.PasswordSynchronization.SynchronizationExecutionContext.SynchronizeDomain()
at Microsoft.Online.PasswordSynchronization.SynchronizationManager.SynchronizeDomain(SynchronizationExecutionContext syncExecutionContext)
Microsoft.Online.PasswordSynchronization.SynchronizationManagerException: Unable to open connection to domain: xxxxxxx.com. Error: There was an error creating the connection context. —&gt; Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsException: There was an error creating the connection context. —&gt; System.MissingMethodException: Method not found: ‘IntPtr System.Runtime.InteropServices.Marshal.GetFunctionPointerForDelegate(!!0)’.
at Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsRpcConnectionContext.CreateDrsHandle(Void* rpcBindingHandle, SafePointer&lt;_SEC_WINNT_AUTH_IDENTITY_W&gt; authHandle)
at Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsRpcConnection.CreateConnectionContext(SourceDomainController sourceDomain)
— End of inner exception stack trace —
at Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsRpcConnection.CreateConnectionContext(SourceDomainController sourceDomain)
at Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsConnection.EstablishConnection()
at Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsConnection.Connect()
at Microsoft.Online.PasswordSynchronization.RetryUtility.&lt;&gt;c__DisplayClass1.&lt;ExecuteWithRetry&gt;b__0()
at Microsoft.Online.PasswordSynchronization.RetryUtility.ExecuteWithRetry[T](Func`1 operation, Func`1 shouldAbort, RetryPolicyHandler retryPolicy)
at Microsoft.Online.PasswordSynchronization.PasswordSynchronizationTask.OpenConnection(IDrsConnection connection)
— End of inner exception stack trace —
at Microsoft.Online.PasswordSynchronization.PasswordSynchronizationTask.OpenConnection(IDrsConnection connection)
at Microsoft.Online.PasswordSynchronization.PasswordSynchronizationTask.CreateConnection()
at Microsoft.Online.PasswordSynchronization.RecoveryTask.SynchronizeCredentialsToCloud()
at Microsoft.Online.PasswordSynchronization.PasswordSynchronizationTask.SynchronizeSecrets()
at Microsoft.Online.PasswordSynchronization.SynchronizationExecutionContext.SynchronizeDomain()
at Microsoft.Online.PasswordSynchronization.SynchronizationManager.SynchronizeDomain(SynchronizationExecutionContext syncExecutionContext)
Microsoft.Online.PasswordSynchronization.SynchronizationManagerException: Unable to open connection to domain: xxxxxxx.com. Error: There was an error creating the connection context. —&gt; Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsException: There was an error creating the connection context. —&gt; System.MissingMethodException: Method not found: ‘IntPtr System.Runtime.InteropServices.Marshal.GetFunctionPointerForDelegate(!!0)’.
at Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsRpcConnectionContext.CreateDrsHandle(Void* rpcBindingHandle, SafePointer&lt;_SEC_WINNT_AUTH_IDENTITY_W&gt; authHandle)
at Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsRpcConnection.CreateConnectionContext(SourceDomainController sourceDomain)
— End of inner exception stack trace —
at Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsRpcConnection.CreateConnectionContext(SourceDomainController sourceDomain)
at Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsConnection.EstablishConnection()
at Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsConnection.Connect()
at Microsoft.Online.PasswordSynchronization.RetryUtility.&lt;&gt;c__DisplayClass1.&lt;ExecuteWithRetry&gt;b__0()
at Microsoft.Online.PasswordSynchronization.RetryUtility.ExecuteWithRetry[T](Func`1 operation, Func`1 shouldAbort, RetryPolicyHandler retryPolicy)
at Microsoft.Online.PasswordSynchronization.PasswordSynchronizationTask.OpenConnection(IDrsConnection connection)
— End of inner exception stack trace —
at Microsoft.Online.PasswordSynchronization.PasswordSynchronizationTask.OpenConnection(IDrsConnection connection)
at Microsoft.Online.PasswordSynchronization.PasswordSynchronizationTask.CreateConnection()
at Microsoft.Online.PasswordSynchronization.RecoveryTask.SynchronizeCredentialsToCloud()
at Microsoft.Online.PasswordSynchronization.PasswordSynchronizationTask.SynchronizeSecrets()
at Microsoft.Online.PasswordSynchronization.SynchronizationExecutionContext.SynchronizeDomain()
at Microsoft.Online.PasswordSynchronization.SynchronizationManager.SynchronizeDomain(SynchronizationExecutionContext syncExecutionContext)
.

xxxxxxx.com</Data>
</EventData>
</Event>

 

ِAfter a long time of troubleshooting and contacting Microsoft support here is what we got

Cause: Essential component required by the password sync engine was not installed; The generic version of “GetFunctionPointerForDelegate” only exists in .Net 4.5.1 and later

Resolution: Installing .net 4.5.2 and latest .net live updates.

 

Overview on Exchange 2016

The below is preliminary information and subject to change before the first release of Exchange server 2016

1- The Block Architecture:

In Exchange 2013 , there were 2 blocks (CAS – MBX) , these both blocks has been merged in Exchange 2016 , there is a single building block that provides the client access services and the high availability architecture necessary for any enterprise messaging environment.

1

The Mailbox server role now:

  1. Houses the logic to route protocol requests to the correct destination endpoint.
  2. Hosts all of the components and/or protocols that process, render and store the data.

No clients connect directly to the back-end endpoints on the Mailbox server; instead, clients connect client access services and are routed (via local or remote proxy) to the Mailbox server that hosts the active database that contains the user’s mailbox.

DAGs in Exchange Server 2016 do have a few specific enhancements:

  1. DatabaseAvailabilityGroupIpAddresses is no longer required when creating a DAG. By default, the failover cluster will be created without an administrative access point, as this is the recommended best practice.
  2. Replay Lag Manager is enabled by default.
  3. Lagged database copy play down can be delayed based on disk latency, thereby ensuring active users are not impacted.
  4. Database failovers times are reduced by 33% when compared to Exchange Server 2013.

Communication between servers still occurs at the protocol layer, effectively ensuring that every server is an island. For a given mailbox’s connectivity, the protocol being used is always served by the protocol instance that is local to the active database copy.

2

 

The load balancer configuration is also not affected by this architectural change. From a protocol perspective, the following will happen:

  1. A client resolves the namespace to a load balanced virtual IP address.
  2. The load balancer assigns the session to a Mailbox server in the load balanced pool.
  3. The Mailbox server authenticates the request and performs a service discovery by accessing Active Directory to retrieve the following information:
    1. Mailbox version (for this discussion, we will assume an Exchange 2016 mailbox)
    2. Mailbox location information (e.g., database information, ExternalURL values, etc.)
  4. The Mailbox server makes the decision to proxy the request or redirect the request to another Mailbox server in the infrastructure (within the same forest).
  5. The Mailbox server queries an Active Manager instance that is responsible for the database to determine which Mailbox server is hosting the active copy.
  6. The Mailbox server proxies the request to the Mailbox server hosting the active copy

3

 2- Search Improvements

One of the challenging areas for on-premises environment was the amount of data that was replicated with each database copy in previous releases. In Exchange Server 2016, we have reduced bandwidth requirements between the active copy and a passive copy by 40%. This was accomplished by enabling the local search instance to read data from its local database copy. As a result of this change, passive search instances no longer need to coordinate with their active counterparts in order to perform index updates.

Another area of investment in search has been around decreasing the length of time to return search results, especially in online mode clients like OWA. This is accomplished by performing multiple asynchronous disk reads prior to the user completing the search term, which populates the cache with the relevant information, providing sub-second search query latency for online mode clients.

 

3- Document Colloboration

In previous releases of Exchange, OWA included document preview for Office and PDF documents, reducing the need to have a full fidelity client. SharePoint had a similar feature, however it used the Office Web Apps Server to accomplish this capability. Within Office 365, we also leverage Office Web Apps Server to provide this capability, ensuring uniform document preview and editing capability across the suite.

In Exchange Server 2016, we leverage Office Web Apps Server to provide the rich document preview and editing capabilities for OWA. While this was a necessary change to ensure a homogenous experience across the Office Server suite, this does introduce additional complexity for environments that don’t have Office Web Apps Server.

 

4- Outlook Connectivity

Introduced in Exchange Server 2013 Service Pack 1, MAPI/HTTP is the new standard in connectivity for Outlook. In Exchange Server 2016, MAPI/HTTP is enabled by default. In addition, Exchange Server 2016 introduces per-user control over this connectivity model, as well as, the ability to control whether the protocol (and Outlook Anywhere) is advertised to external clients.

 

Topology Requirements

Exchange Server 2016 will only be supported on Windows Server 2012 R2 and Windows Server “10” operating systems.

From an Active Directory perspective, Exchange Server 2016 will require:

  • Windows Server 2008 R2 or later Active Directory servers.
  • Windows Server 2008 R2 or higher Forest Functional Mode and Domain Functional Mode.

Exchange Server 2016 will only support coexistence with Exchange Server 2010 SP3 RU11* and Exchange Server 2013 CU11* (*subject to change).

These are the main improvements and enhancements that exist in the new version of Exchange

Resources and more Information at : Exchange Team Blog & Exchange 2016 Ignite Video

How to monitor availability of your Azure datacenter

It is one of those days when you face connectivity issue with your Azure Virtual machines,  and you don’t know what is the problem

Now you can use the URL : http://azure.microsoft.com/en-in/status/#current

As per the below , you will find :

1- Refresh interval

2- Types of information (Good – Warning – Error – ………)

3- Location of the Datacenter (West Europe – East US – ……………)

4- The service (Storage – VM – …………..)

1

 

 

If you want to check the incident history , just go to History tab

You can check the old incidents related to any service , any data center or any time interval

2

 

Configure Auditing & Reporting for one drive for business

First thing you need to know that the Auditing and Reporting is not enabled by default

The below article will help you to enable both features on your One drive for business

What we will gain from Auditing and Reporting:

1- Shows all events where a user viewed content in this site

2- Shows all events that caused content in this site to be deleted or restored from the Recycle Bin

3- Shows all events that modified content types and lists in this site

 

Now lets see how can we enable these features:

1- Log in to your Office 365 Portal

2- Click One Drive as below

0

3- Now navigate to the gear icon and choose “Site Settings” as below

1

4- After the “Site Settings” page open , click on “Site Collection Features” under “Site Collection Administration” as below

2

 

5- Once the “Site Collection Features” page opened , scroll down to “Reporting” and then click “Activate” as below

3

6- Now got Back to the “Site Settings”  page as step 4 , you will find 2 new options appeared under “Site Collection Administration” which are “Site collection audit settings” and “Audit Log Reports” , now choose “Site collection audit settings” as below

Note: it is prefer to crate a folder under your one drive for business for the reports only

5

 

7- Now go back to “Site Settings” step 4 , and choose “Audit Log Reports” , the below page will open to you

6

8- Now you can choose any report you want to generate and press on it and the below page will appear to you

7

9- Press on OK , the below page will appear

8

10- Now press on “Click Here to view the report”, the report will be as below

9

11- Press on the “Report Data” tab , in the bottom of the Excel sheet to know more information (like who delete the file or folder)

10

 

Now if you share any file or folder with internal or external users , you will be able to know who deleted or modified your files and what actions has been taken on you shares

 

Sources: office 365 advisors

 

 

%d bloggers like this: