Backtrack:  
 
showing posts tagged with 'office365'
1 · 2 · 3
by lunarg on October 9th 2015, at 10:06
With the release of Office 2016, Microsoft has also released the Office 2016 Deployment Tool (download here).

New features for Office Deployment Tool:

Specify which update branch to use.

Specify which language accessory packs to install.

The download of Office Deployment Tool contains a sample configuration.xml. Check out the Reference for Click-to-Run configuration.xml file for a complete reference on what can be configured.

Aside of some minor additional options to the configuration XML, using the Office Deployment Tool hasn't change very much, so this article about how to configure and use Office Deployment Tool for Office 365 is still valid.

More information about updating to Offic  ...
by lunarg on August 24th 2015, at 16:20
Occasionally (usually once a year), you may have to renew your SSL certificate of your Active Directory Federation Services server, used for your Office 365 Single Sign-On setup. In past versions, this was done quite easily through IIS. However, since 2012 R2 (a.k.a. ADFS 3.0), ADFS no longer uses IIS and it gets a little bit more complicated.

Outlined in this short article are the steps you need to do in order to renew or replace your SSL certificate on a Windows 2012 R2 server, running ADFS 3.0.

First, renew or request a new SSL certificate through your Certificate Authority (such as GoDaddy, Enom, etc.). How to do this depends greatly on the CA. As ADFS on 2012 R2 no longer uses IIS, yo  ...
by lunarg on August 18th 2015, at 15:07
If you have an Exchange Hybrid Configuration setup, you may have some users that use services of Office365 but still have their mailbox on-premise. These users probably have an Office365 license assigned to them. Selecting these users from the Users list in the Office365 Admin Portal reveals the following message when viewing the primary e-mail address for such a user:

Error
The items you're trying to open couldn't be found.

Additionally, the same error is displayed when attempting to view or edit Exchange Online properties for such a user.

The error is actually a "bug" in the Office365 Admin Portal, caused because the user has an Exchange Online license assigned. Because of thi  ...
by lunarg on August 17th 2015, at 13:25
EDIT: highlight required trailing dots + added CNAME for msoid.

If you're using a hosting provider which uses DirectAdmin for its DNS management, it may be a hassle to correctly configure DNS records for Office 365, mainly because of syntax issues. After some trial-and-error and googling, I finally managed to correctly devise the proper syntax to configure Exchange Online and Lync Online.

The set up of the entries below is a left and right field in the DNS management, safe for MX-records, which are set up elsewhere. For most services, don't forget to add the trailing . at the end of each record pointing to a Microsoft Server. Otherwise, resolving will incorrectly add your own do  ...
by lunarg on August 14th 2015, at 12:29
Setting up a hybrid configuration between Office 365 and on-premise Exchange may seem straight forward, but there are a lot of pitfalls to tackle. One of the more frequent issues is a problem with free/busy information not being visible, or the inability to migrate mailboxes from/to Exchange Online.

Additionally, you may have received this error during the initial configuration of the hybrid setup:

Hybrid Configuration Wizard
Office 365 was unable to communicate with your on-premises Autodiscover endpoint. This is typically due to incorrect DNS or firewall configuration. The Office 365 tenant is currently configured to use the following URL for Autodiscover queries from the Office 365 tena  ...
by lunarg on August 14th 2015, at 09:14

In an Office365 hybrid configuration, you may get the following error after the Sign in to Office 365 prompt in the EAC:

Error
412
Cookies Are Disabled :(
Please make sure that you enabled cookies in your browser settings and that your Exchange Admininstration Center domain has been added to trusted sites or local intranet zones.

To resolve, you need to do just that:

  1. Go to Internet Options, tab Security.
  2. Click the Intranet zone, then click the Websites button, then the Advanced button.
  3. Add your EAC FQDN to the list (e.g. https://exchange01.contoso.com/).
  4. Completely close the browser, then log back in.
by lunarg on August 13th 2015, at 15:55

There's no direct installer available for Skype for Business, as it is part of Office Pro Plus, but if you have enough with the basic version (i.e. you're missing a couple of enterprise grade features), you can get Skype for Business by first installing Lync Basic, then install the required updates to turn Lync into Skype for Business.

  1. Microsoft Lync Basic 2013
  2. Install these two patches:
by lunarg on June 26th 2015, at 14:50

Microsoft has released the Azure Active Directory Connect to the general public. Azure AD Connect replaces (although "incorporates" is a better word) DirSync as the new tool to set up synchronization between your on-premise Active Directory and Azure Active Directory, including Office 365.

The current version of Azure AD Connect is only the beginning. Microsoft has announced a lot more features, which will be made available in the next versions.

More information and installation resources: https://azure.microsoft.com/nl-nl/documentation/articles/active-directory-aadconnect/

by lunarg on June 5th 2015, at 15:04

Office365 Outlook Web Access (OWA) has been updated with a new look. Most notable is the presence of Gmail-style avatars for the contacts:

by lunarg on May 29th 2015, at 14:43
You can set up an e-mail signature in Office365's OWA (also works with on-premise Exchange 2013 OWA) quite easily. While it's no problem to apply any kind of formatting to your signature, you'll find out that adding images is not as straight forward.

To set up an e-mail signature, follow the steps below.

For best results, use either Internet Explorer or Firefox. Google Chrome has some (minor) issues with OWA.

Log onto OWA. For Office365, this is https://outlook.office365.com/.

Click on the gear icon in the upper-right corner, and choose Options.

In the left tree, follow Mail > Layout > Email signature.

Edit your signature, or copy/paste it from another source (e.g. Word).
If you   ...
by lunarg on April 22nd 2015, at 12:25
There are limitations to using OneDrive for Business to synchronize items.

Maximum items* for OneDrive for Business20 000Maximum items* per Sharepoint document library5 000*** Files and folders.
** You can synchronize more than one library.

Maximum size per item2 GBMaximum name length for files and foldersSharepoint Server 2013: max. 128 chars
Sharepoint Online: max. 256 chars
Folder names: max. 250 chars
Maximum combined names (files and folders, aka "path": max. 250 charsInvalid characters:\ / : * ? " < > | &hash;
spaces are not supported
files starting with a ~Invalid chars (Sharepoint Server 2013):All of the above +
{ } % ~
names starting with a .Unsupported folder  ...
by lunarg on March 24th 2015, at 12:12

As you probably already have noticed, does Outlook prompt for credentials when configuring Outlook for use with a federated Office 365 account, regardless of whether you've set up your intranet zoning for your ADFS server in Internet Explorer options.

Apparently, this is unresolveable as Outlook (2013 and earlier) simply does not support SSO. It is currently unknown whether a subsequent version of Outlook will have this feature.

Source: https://support.microsoft.com/kb/2535227

Oddly enough, Lync does support SSO.

by lunarg on March 18th 2015, at 13:38
When implementing AD/Dirsync to synchronize your on-premise AD with Office365, you may have to change the UPN-suffix to match the (e-mail) domain name used in your Office365 tenant. Most often, the local UPN-suffix would be something like domain.local, and would then have to be changed to domain.com. With a lot of users, it can quickly become tedious to change this manually. Along came Powershell...

The attached script is an easy way to quickly change the UPN-suffix for all users in a particular OU. Simply adjust the parameters to match your configuration, and let it run. Note that the script runs recursively, so be careful when running this on a top-level OU, as it will cascade through a  ...
by lunarg on March 4th 2015, at 15:09
By default, when a user first logs on to Outlook Web App, they are prompted to choose their language and time zone. Sometimes, it's required to change these settings for a certain user, or even, for all users. This can be done by an administrative user through Exchange Management Shell (EMS), and works for both Exchange 2010/2013 and Office365, with the cmdlet Set-MailboxRegionalConfiguration.

First, open EMS for your on-premise Exchange, or for Office365, connect to Exchange Online using Powershell.

You can then set/change the language and time zone for a user like so:

Set-MailboxRegionalConfiguration -Identity -Language -TimeZone

identity speaks for itself: it can be an alia  ...
by lunarg on February 13th 2015, at 11:05

If OneDrive for Business stays stuck at "We're getting things ready to sync..." when syncing a new library, or re-syncing an existing one, try resetting OneDrive for Business.

by lunarg on February 13th 2015, at 11:02
If for some reason (e.g. when synchronization no longer works properly), you can completely clear and reset OneDrive for Business in a few easy steps.

First, close down all Office programs (such as Word, Excel, Outlook, etc.). Next, open Windows Task Manager, look for and kill these processes:

MSOSYNC.EXE

GROOVE.EXE

MSOUC.EXE

I've noticed that sometimes, these processes get restarted automatically, so be sure they are gone before performing the next step.

Next, locate and delete these folders and their contents:

%LOCALAPPDATA%\Microsoft\Office\Spw

%LOCALAPPDATA%\Microsoft\Office\15.0\OfficeFileCache

If needed, also delete the local copy of all synced libraries. The location depends   ...
by lunarg on November 12th 2014, at 16:45

Technically, you can't set up out-of-office for shared mailboxes through a normal way, because you can't log in with Outlook on those accounts. A workaround would be to temporarily convert it to a regular mailbox, grant a license to it, and then log in with Outlook, but this is not always possible or desired.

Fortunately, you can also enable out-of-office through Powershell on any mailbox, including shared and resource mailboxes.

http://support.microsoft.com/kb/2667296

by lunarg on October 21st 2014, at 11:14
You can easily get a list of users and their assigned Office365 licenses through the Windows Azure Active Directory Module for PowerShell.

Connect to your Office365 tenant through a user with Administrator permissions:

Connect-MsolService

Then, enter this command:

Get-MsolUser | Select DisplayName,Licenses | FT

You can also append the following to export it to a CSV-file.

... | Export-CSV -Delimiter ";" ~Desktopmy-export.csv

The Licenses column tells which license is assigned, but it uses different names than what is visible at the WebPortal.

These are the ones that I know of:

STANDARDPACK Office365 Enterprise E1 ENTERPRISEPACK Office  ...
by lunarg on August 28th 2014, at 13:11
For migrations from other e-mail platforms to Exchange, you probably want to have full access enabled for a certain Exchange-account to facilitate the migration without having to set up complex access rights. Exchange has something called application impersonation, which allows a user to impersonate other users to access individual mailboxes, which comes in very handy during a migration.

In order to set up application impersonation, you need access to the Exchange Management Shell (EMS), with an account which has permissions to set up access rights.

Exchange 2007 does not support application impersonation as in Exchange 2010 and up. Impersonation does exist but has to be set on each indivi  ...
by lunarg on March 4th 2014, at 13:03
In normal circumstances, Outlook would configure itself using a procedure called Autodiscovery: all server settings and logon names would be configured by downloading configuration settings from a certain site, eliminating the requirement to know any server settings. Office 365 also makes extensive use of Autodiscovery for this and other purposes. In case of migrations, or when Autodiscovery is not available or does not apply (e.g. Outlook 2007), you can also manually configure your Office 365 account. Although this used to be pretty straight-forward, since they moved to Exchange 2013, manual configuration of Outlook has become a bit more complex.

Since its upgrade to Exchange 2013, Office   ...
1 · 2 · 3
showing posts tagged with 'office365'