Microsoft Office 365 makes available the most recent version of the Office software for licensed users to download. In this case that would be Office 2016.
But for any number of reasons, there are still cases where someone may need Office 2013. Up until March 1, 2017, Office 2013 was easily available through O365.
Now that we are pass that deadline, the question is: Can we still download Office 2013 for our O365 account users. And the answer is: YES!!!!
My good MVP buddy, Boon Tee, recently posted directions (click here) on where one can still download Office 2013 from Office 365.
Customer had Office 2010 on his computer, and was upgrading to Office 2016 via his GoDaddy Office 365 account. But the installation would fail half way through with error code 30143-37
GoDaddy support said it was because anti-virus was running. We stopped A/V but still encountered the error. I then right clicked on the downloaded setup executable, selected Properties, and clicked to “unblock” the file. That did not help either.
I found a couple of web sites that suggested deleting (or at least renaming) the folder “C:\Program Files\Microsoft Office 15”.
That seemed to do the trick, as I was able to then install Office 365. Note: I did NOT reboot the computer after deleting the folder.
I recently migrated a customer from SBS 2008/Exchange 2007 to Office 365 with AppRiver and BitTitan’s MigrationWiz tool.
Migration went like a charm … that is, until one of the employees tried to “scan to email” a document from their Ricoh Aficio MP C2500.
A quick search of forums suggested that a lot of people had been down this road before, and with a myriad of possible ways to configure or fix it. Quite often, the suggestion was to use a 3rd party SMTP service.
I submitted a ticket to AppRiver’s support at 11:57am this morning and received a phone call from their tech support within 15 minutes. A quick remote connect session, and we had everything working within minutes.
Here are my notes for future reference:
First, the solution we followed
- We used information from this Microsoft TechNet Article
Second, gather the following information
- Your public IP address to your office. You can use WhatIsMyIp.com if you don’t know it)
- Your Office 365 MX record. It should look something like this: Contoso-com.mail.protection.outlook.com
Next, setup the Exchange connector within Office 365
- Login to your O365 Admin Center portal (http://portal.office.com)
- Click Exchange –> Mail Flow –> Connectors
- Create a new connector with this information
- Enter a name for your connector, such as “Ricoh Copier On Prem”
- From: select Your Organization’s Email Server
- To: select Office 365
- Description: enter something like this: This is the connector that will allow traffic from the SMTP services for Ricoh
- Enable the option Retain Internal Exchange Email Headers
- IP Address: enter your public IP address
Next, let’s go to the Ricoh web portal to finish things up:
- Go to your Ricoh’s web portal (local IP address, such as 192.168.1.xxx)
- Click to login as the administrator.
If you don’t know the login/password, here’s a web site that may help you:
- Click Configuration => E-mail (under Device Settings)
- Enter the following information as appropriate:
- Your Admin O365 email address
- Protocol: SMTP
- SMTP Server Name: your O365 MX name you looked up previously
(such as Contoso-com.mail.protection.outlook.com)
- Port: 25
- SMTP Authentication: OFF
- SMTP Authentication Email/Username/Password: your O365 Admin email address
- SMTP Authentication Encryption: DISABLE
That’s all we did. Hope it works for you!
Microsoft released an update (KB 2974308) today to address the issue where integrating Windows Server Essentials 2012 R2 with Microsoft Office 365 or Windows Azure Active Directory is blocked when you are in a multiple domain controller environment.
Until now, you could only integrate Windows Server Essentials with O365/Azure AD in a single domain controller environment.
Attempting to run the integration in a multiple DC environment would fail:
I’m proud of the work that our MVP group did in identifying this issue soon after the release of Essentials 2012 R2 last year.
The 12th annual SMB Nation Fall conference is set for September 26-28, 2014, and will focus entirely on Office 365. The conference will be held at the Microsoft Redmond campus in Redmond, WA.
Harry Brelsford announced today that they are now taking reservations.
I recall the excitement that surrounded his very first SMB Nation conference, which was held in Indianapolis, IN back in 2003.
If you have not attended an SMB Nation conference before, I would highly recommend it.
The folks at apress have made available as a free download the eBook titled “Office 365: Migrating and Managing Your Business in the Cloud”. The book is jammed-pack with information, including a hands-on tutorial of Office 365, and covers in-depth what you need to do to migrate to Office 365/
This 680 page book is available in EPUB, MOBI and PDF format.
Here is a partial list of chapter titles:
Microsoft announced this week that their “multi-factor” authentication is now available for the majority of Office 365 plans – midsize, enterprise, academic, non-profit and even standalone plans for Exchange Online and SharePoint Online. I guess that just leaves out the “P” plans.
More importantly, there will be no extra charge for this new feature, and it is purely optional whether you implement it at all.
Microsoft is calling it “multi-factor” instead of “two factor” authentication because you have multiple options for getting that second authentication.
Check out the Microsoft Office Blog for details and screen shots!
Most businesses, large or small, use alias emails, such at firstname.lastname@example.org or email@example.com. If some cases, the alias is only managed by a single person (e.g. firstname.lastname@example.org).
But what if you want to assign the alias email address to a group of users, that is, a distribution group?
The simple answer is ‘Yes, it can be done’. However, there is no wizard to do this from the Office 365 Admin portal page. So, you will be required to define the shared mailbox using PowerShell commands.
There are three basic steps required:
- Create a distribution group, and assign users
- Create a shared mailbox using PowerShell commands
- Have each user add the shared mailbox to their Outlook 2010/OWA app
Rather than describing each of these steps, Microsoft provides a very clear, step by step, set of instructional videos for each of these steps:
Create a public email alias in Office 365
Microsoft makes available a list of “service description” documents related to Office 365. The list addresses everything from Exchange Online to Office Web Apps, from Apple Mac/IOS support to SharePoint Online.
Here is the link: