25. March 2013 · Comments Off on How can I stop users from using PST files · Categories: Microsoft · Tags: , , ,

PST files are a burden in many environments. They’re hard to manage, hard to perform discovery on, and prone to loss when stored on local machines. Many companies now use archiving solutions at the mail server, such as the Exchange 2010 archiving functionality, to avoid the need for user PST files.

Briefly, these are some of the problems with PST files:

  • Microsoft does not support using PST files over a LAN or WAN network (KB267019). Using PST files located on network shares can slow down Outlook and can cause corruption of the PST file.
  • Anti-virus countermeasures cannot be implemented on PST files as easily as Exchange Server mailbox databases.
  • It is difficult to accurately report on PST file use, making reporting on organizational mail storage and planning for future growth difficult.
  • Managing content of PST files is difficult.  Exchange Server provides tools to manage the content of mailboxes (such as Messaging Records Management) and to export or remove data from mailboxes (such as the Export-Mailbox cmdlet) but there are no such tools to manage the content of PST files.
  • Local PST files are difficult to back up, making them vulnerable to data loss.

To phase out PST files, take a two phase approach. First, you can stop users from writing to PST files but still allow them to read from then. You can then totally block PST files.
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 »

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 »