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 AD FS for Office 365 – Simplified Installation Guide · Categories: Office365 · Tags: , , ,

Step 1. Prepare Your Active Directory Domain

Office 365 SSO requires an Internet-resolvable domain name to use as the suffix in each user’s username. Don’t worry, though, if your Active Directory domain name doesn’t meet this requirement. Most of them don’t. You can make things work by giving users an alternate User Principal Name (UPN) that matches any public domain name you own.

Let’s assume your public domain name is contoso.com, but your inside-the-firewall Active Directory domain is contoso.local. You can’t resolve contoso.local via Internet servers, therefore you won’t be able to with Office 365 DNS servers. That said, you can use federation to set each user’s UPN to a publicly resolvable domain name and let them log in as username@contoso.com.

While each user’s UPN might look like an e-mail address, it has nothing to do with SMTP or Session Initiation Protocol. This change merely maps your users’ Active Directory accounts with an external address that Office 365 can understand.

Launch Active Directory Domains and Trusts and view the Properties of its top-level node. In the box titled Alternative UPN suffixes, enter your publicly resolvable domain name and click Add. Then launch Active Directory Users and Computers and view the Properties of a user account. Under its Account tab, you can now set the User logon name to that publicly resolvable domain name. Do this for each Office 365-enabled user. They’ll be using this as their Office 365 username in a minute.

Step 2. Prepare Your Server and Install ADFS

You can install ADFS on a domain controller or another server. You’ll first need to configure a few prerequisites. The following steps assume you’re installing to Windows Server 2008 R2.

Using Server Manager, install the IIS role and the Microsoft .NET Framework 3.5.1. Then purchase and install a server-authentication certificate from a public certificate authority. Make sure you match the certificate’s subject name with the Fully Qualified Domain Name of the server. Launch IIS Manager and import that certificate to the default Web site.
More »

27. October 2012 · Comments Off on Configure user passwords to never expire on Office 365 · Categories: Office365 · Tags: , ,

Prerequisites

Microsoft Online Services Module for Windows PowerShell must be installed

http://onlinehelp.microsoft.com/en-us/office365-enterprises/hh124998.aspx

1. Install Single Sign-on
2. Install PowerShell Add-on

Procedure

Open “Microsoft Online Services Module for Windows Powershell”

Connect to the account by typing

Connect-MSOLService 
 (You will get a username and password Prompt)

[[Authenticate]]

Check whether a password is set to never expire

To check whether a password is set to never expire, determine whether the More »

23. October 2012 · Comments Off on WinMail.dat on Office365 Fix · Categories: Office365 · Tags: , ,

 

After Migrating users to Office365 users will make an issue of other external people or organizations getting a Winmail.dat file as an attachment instead of actual files or attachments.   Below are the commands you how to fix this, so that Office365 doesn’t send in this format to people who are outside your organization.

More »