29. October 2015 · Comments Off on How to Add an SMTP address in Office365 with DirSync & ADFS enabled · Categories: Office365, Windows

If you are synchronizing an Office 365 account with an on-premises Active Directory, you know that you cannot edit exchange user properties using the Office 365 administrator portal.  In this article, I will show you how to add e-mail aliases using the Active Directory Service Interfaces Editor (adsiedit).

  1. Go to Start > Run and type adsiedit.msc
  2. Now, find the unit where your AD user’s reside
  3. Right click the user you want to edit and click Properties.
  4. Find the variable proxyAddresses – this is the one you want to edit.
    When you add new e-mail aliases, you want to make sure that your primary e-mail address will start with upper-case SMTP. Your aliases, aka, secondary addresses should be lower-case smtp.For example, I want my primary e-mail address to be firstnamelastname@example.com
    In the proxyAddresses attribute, I would put:
    SMTP:firstnamelastname@example.com
    As my alias, I want firstname.lastname@example.com… to do this, I will use lower case smtp:
    smtp:firstname.lastname@example.com

Apply the new settings and wait for your active directory to be synchronised with Office 365 (by default this happens every 3 hours)

17. April 2014 · Comments Off on OpenSSL Heartbeat (Heartbleed) Vulnerability (CVE-2014-0160) and its High-Level Mechanics · Categories: Cisco, Linux, Microsoft, Office365, VMWARE, Windows · Tags: , , , , , , ,

Cisco Devices are not effected as they are running OpenSSL version 0.9.8 on the newest 9.01 IOS Software. Most Cisco Firewalls have Older IOS versions and therefore have older versions of OpenSSL.

The heartbleed bug was introduced in OpenSSL 1.0.1 and is present in
• 1.0.1
• 1.0.1a
• 1.0.1b
• 1.0.1c
• 1.0.1d
• 1.0.1e
• 1.0.1f
The bug is not present in 1.0.1g, nor is it present in the 1.0.0 branch nor the 0.9.8 branch of OpenSSL.

22. August 2013 · Comments Off on Check mailbox size and usage with Office 365 · Categories: Office365 · Tags: , ,
  1. First of all, you need to use the regular version of PowerShell.  NOT the “Online Services Module” for PowerShell version
  2. Make sure you run PowerShell as an administrator. (Right-click the icon and select “Run as Administrator”)
  3. The first time I ever tried to run these type of scripts, I got an error about running remote signed scripts or something like that. So you need to run this command the very first time you try any operations like this:
    • Set-ExecutionPolicy RemoteSigned
      More »
22. April 2013 · Comments Off on The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process · Categories: Office365 · Tags: , , , ,

I”m working on a Office365 Migration for a client that has an Excahange 2010.  Encountered some some migration issues.  I ran the testexchangeconnectivity.com test for RPC over HTTP, and everything was just fine, excpet for the last test, which returned the dreaded:

“The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.”

===================================================================
More »

22. March 2013 · Comments Off on [Office365] Disable the requirement for strong password using PowerShell · Categories: Office365 · Tags: , ,

images

 

To disable the requirement for strong password for users via Windows PowerShell, would you please take the following steps:

Step 1. Install the Office 365 cmdlets.

Step 2. Connect Windows PowerShell to Microsoft Online Service.

Step 3. Start Microsoft Online Services Module for Windows PowerShell as an administrator and connect to Microsoft Online Service with a global administrator account by running the following command:

Connect-MsolService.
More »

19. March 2013 · Comments Off on Potential Autodiscover Issue During E-Mail Coexistence · Categories: Office365 · Tags: , ,

 

Under some conditions your organization may experience Autodiscover issues while testing Microsoft Online or when establishing e-mail coexistence between your local Microsoft Exchange Server environment and Exchange Online Services.

Scenario

If your company is an Exchange Online customer and your e-mail environment meets the following conditions, you may encounter Autodiscover issues.

  1. 1.       Your organization is using Microsoft Exchange Server 2007.
  2. 2.       Your users are using Microsoft Outlook 2007.
  3. 3.       Your users with Exchange Online mailboxes also have mailboxes on your on-premise Exchange Server, AND your Exchange Online user accounts have identical primary SMTP e-mail address in both systems.

More »

17. March 2013 · Comments Off on Exchange 2007 to Office 365 mailbox migration: Autodiscover connects Outlook to the Exchange Server instead of O365 mailbox · Categories: Office365 · Tags: , , , ,

 

While migrating an Exchange 2007 (or 2010) mailbox into Office 365 (O365), autodiscover connects Outlook to the Exchange Server rather than connecting to the O365 mailbox.  Although you can’t connect via Outlook, Outlook Web Apps (OWA) and mobile devices might correctly connect to the O365 mailbox.

Reason:

This issue occurs because you have an on-premise Exchange Server. Autodiscover for Outlook will always point to the on-premise environment.

When you install an Exchange 2007 or 2010 Client Access Server (CAS) role, a number of service-related configurations are applied. What is causing the issue is the service connection point (SCP). This is an Active Directory (AD) object that gets created on the server that the CAS role gets installed on. The SCP object contains the authoritative list of autodiscover service URLs for the forest. To see this list, you can run the following command in the Exchange Management Shell (EMS):
More »

17. March 2013 · Comments Off on How to enable archive mailboxes in Office 365 GUI/portal & PowerShell · Categories: Office365 · Tags: , ,

Configure/Enable Archive Mailbox with Office 365 GUI (Single-User)

  1. Select “Manage My Organization” > “Users & Groups” > “Mailboxes”.
  2. Select the mailbox you want to enable the archive mailbox for and click Details.
  3. Under Mailbox Features, select Archive and click Enable.
  4. In the Archive Mailbox window, accept the default archive name (Archive Mailbox – ) or type a new name.
  5. Click Save.
  6. Note that the status for Archive is now Enabled.

NOTE: = The display name of the user as it is listed within Office 365, thus if the user’s name is Jane Doe, the default name will be Archive Mailbox – Jane Doe.

Configure/Enable Archive Mailbox with PowerShell (Single-User)
More »

19. January 2013 · Comments Off on Setup Windows Server 2008 SMTP Relay for Office 365 · Categories: Office365 · Tags: , ,

Many small businesses have printers that scan to e-mail, phone systems that send e-mail status updates, and a number of other e-mail enabled applications and devices.  When converting to a cloud based e-mail system, like Office 365, sometimes these devices cannot be configured to send e-mail over encrypted links to the cloud.  Office 365 required an SMTP connection that supports TLS encryption and many legacy devices or applications don’t support this.

The solution is to install an onsite SMTP relay that supports an encrypted connection.  Fortuneately, Windows Server supports an SMTP relay for Office 365.

This how-to guide assumes you have an operational Windows Server 2008 server within your company / organization.  It will work through adding the correct roles and features to Windows Server 2008, and then configuring them for communicating with Online Exchange within Office 365.

Determine Office 365 SMTP Server Settings

Before you can configure the relay, you must know the exact mail server addresses to use in Office 365.  To determine those, follow these steps:
More »

02. January 2013 · Comments Off on How to convert an Office365 federated domain back to a managed domain · Categories: Office365

Use these methods only if all the following conditions are true:

Reverse the domain federated authentication settings for the Office 365 account domain
– if the AD FS 2.0 server is available

Use this method only if all the following conditions are true:

  • The problem is caused by a service outage that requires immediately restoring user access, or the account is an Office 365 for professionals and small businesses account.
  • The Active Directory Federation Services (AD FS) 2.0 server is available.
    More »