Featured post

Disclaimer

The information contained in this website is for general information purposes only. The information is provided by www.office365support.ca and while we endeavour to keep the information up to date and correct, we make no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability, suitability or availability with respect to the website or the information, products, services, or related graphics contained on the website for any purpose. Any reliance you place on such information is therefore strictly at your own risk.

In no event will we be liable for any loss or damage including without limitation, indirect or consequential loss or damage, or any loss or damage whatsoever arising from loss of data or profits arising out of, or in connection with, the use of this website.

Through this website you are able to link to other websites which are not under the control of www.office365support.ca. We have no control over the nature, content and availability of those sites. The inclusion of any links does not necessarily imply a recommendation or endorse the views expressed within them.

Every effort is made to keep the website up and running smoothly. However, www.office365support.ca takes no responsibility for, and will not be liable for, the website being temporarily unavailable due to technical issues beyond our control.

Finding and Changing the Primary AD FS 2.0 Server in an AD FS 2.0 Farm with PowerShell

PowerShell can be used to quickly identify the primary server in an AD FS 2.0 farm. When you deploy AD FS 2.0 and setup with a default install, it will use Windows Internal Database (WID). In this setup the WID database on the Primary AD FS server is a read/write copy. All the Secondary AD FS server(s), in the farm, have a read only copy that is synchronizes from the Primary.

 

  • Run this command to view the role of the server and see who it’s synchronizing the database changes from.

    Get-ADFSSyncConfiguration

 

Command run on an AD FS Primary Server

 

Command run on an AD FS Secondary Server

 

 

In the event that you lose the Primary AD FS server in the farm, you can move the role to any Secondary Server in the same farm. This again is done through PowerShell with a simple command.

 

  • Run this PowerShell command on the Secondary AD FS server that you want to make Primary AD FS server.

    Set-AdfsSyncProperties -Role PrimaryComputer

And then

  • Run this command to view the current role. It should change to PrimaryComputer

    Get-ADFSSyncConfiguration

 

 

 

Now that the Primary role is moved you must update all the other Secondary servers, if you have more than two Secondary servers in the farm.

 

  • Run this PowerShell command on the other Secondary AD FS servers so that they now sync with the new AD FS Primary server

    Set-AdfsSyncProperties -Role SecondaryComputer -PrimaryComputerName FQDN of ADFS Primary Server

 

Thanks for visiting and reading my posts. I am always looking for more ideas. Please comment or email me with what you would like to see.

Kelsey Epps Office365 MVP

Technical Consultant

Concepps Group

Email Me Follow me on Twitter Connect with me on LinkedIN

 

 

 

 

 

 

No Subscription Found – Office Mobile for iPhone and Android

 

When trying to sign in and activate Office Mobile for iPhone or iPad you may encounter the following error. This error is consistent on the iPhone and Android devices. My post shows screen shots from an iPhone 5, but the same solutions can be applied to Android as well.

 

No Subscription Found We couldn’t find a subscription connected to your account.

 

 

There are a number of reasons why you may encounter this error, so here are the top four fixes.

 

  1. Make sure that your Office365 user account is licensed for Office Professional Plus.

     

  2. If you have a license assigned to your Office 365 user account, give it time to replicate across the Microsoft back end servers. After the license is applied, wait at least 15-30 minutes before trying to activate Office Mobile on iPhone or Android.

     

  3. Verify that you are signing into Office Mobile with the correct account option. Login to Office Mobile with your Organizational Account. If you choose Microsoft Account you will get the error.

     

  4. If the three solutions above, don’t work:
    1. Remove the Office Professional Plus license from the Office 365 user account
    2. Allow for replication/propagation time (30-45 minutes) across the Microsoft back end servers.
    3. Add the Office Professional Plus license back to the Office 365 user account

 

Here is the Microsoft KB that details the issue.

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

 

 

Thanks for visiting and reading my posts. I am always looking for more ideas. Please comment or email me with what you would like to see.

Kelsey Epps Office365 MVP

Technical Consultant

Concepps Group

Email Me Follow me on Twitter Connect with me on LinkedIN

 

Connect to SharePoint Online with the SharePoint Online Management Shell

Most administrators are looking to manage their SharePoint Online service from PowerShell. Here is how you connect to SharePoint online with PowerShell

 

Make sure that the following software is installed

Windows Management Framework 3.0

SharePoint Online Management Shell

 

Connect to SharePoint Online

  1. Open SharePoint Online Management Shella.    Click Startb.    Click All Programs

    c.    Click SharePoint Online Management Shell

       d.    Right Click SharePoint Online Management Shell and run as Administrator

2.    Run the following command, modified for your own tenant

 Connect-SPOService -Url https://customerdomain-admin.sharepoint.com -credential admin@customerdomain.com

-Url is the URL of the SharePoint Online Admin Centre

-Credential is the user that has admin access to the SharePoint Online service

 

Check out the following link for all the wonderful things that you can do with SharePoint online and PowerShell.

Introduction to the SharePoint Online management shell

 

Thanks for visiting and reading my posts. I am always looking for more ideas. Please comment or email me with what you would like to see.

Kelsey Epps

Office 365 MVP

Email Me Follow me on Twitter Connect with me on LinkedIN Facebook Me

 

How Office 365 Saves me Time and my Marriage

Working full time (at HP), caring for a family (including 3 kids under 5 years old) and running my own side business; I don’t have the time to manage my own IT. That doesn’t mean that I have to settle for sub par email, no IM and no collaboration tool. Office 365 affords me the freedom to have enterprise class services on a shoe string budget. I am a company of one, but that doesn’t mean I don’t require enterprise class services. Since I am the whole company, my requirements are more than a normal person.

My favorite Office 365 feature is Exchange Online. I need to stay on top of my email and without Office 365 I don’t think that I would be able to do that. I can access my email from everywhere and have one mailbox that is always up to date no matter what device I choose to access it from. A typical day for me includes checking and replying to my emails from Outlook, smartphone, OWA and tablet. I can be in my Office, meeting a client for coffee or relaxing in bed and I am always up to date.

Being a user of Office 365 and a Microsoft Partner, I can speak from experience when I speak nothing but good words about Office 365. The many clients that I consult for love Office 365 as it’s a great balance of services provided and money spent.

Thanks for visiting and reading my posts. I am always looking for more ideas. Please comment or email me with what you would like to see.

Kelsey Epps

Office 365 MVP

Email Me Follow me on Twitter Connect with me on LinkedIN Facebook Me

 

Making AD FS Highly Available for the NEW Office 365

Since we configured AD FS into a farm configuration, making the solution highly available, is relatively straight forward. We essentially add another server to the farm, then load balance through hardware or software. This will be a two part post; the first part will cover adding another server to the AD FS farm and the second part will detail how to load balance those servers.

 

Prepare the Server for AD FS

 

We are going to jump between a few of my other posts, to prepare the server. Sorry, but I am too lazy to re-write the content.

  1. Domain join the new AD FS server
  2. Use, Prepare the Local AD FS Server, and complete the following sections
    1. Install AD FS Server Role
    2. Install Sign-in Assistant
    3. Install the Windows Azure Active Directory Module for Windows PowerShell
    1. Follow the instructions and import and assign the certificate on the new AD FS server

This will get us to the point where we can add the AD FS server to the existing AD FS Farm

 

Method 1 – Adding a Server to an AD FS farm with the AD FS Configuration Wizard

 

  1. Login to the server that you just prepared for AD FS, with an administrative account
  2. Open Server Manager
  3. Click Tools
  4. Click AD FS Management
  5. Click AD FS Federation Server Configuration Wizard

  6. Walk through the wizard and the second server is added.

 

Method 2 – Adding a Server to an AD FS Farm from the Command Prompt

 

  1. Login to the server that you just prepared for AD FS, with an administrative account
  2. Get the Thumbprint from the certificate that you imported on the AD FS server. This is located on the certificate.

  3. Open a Command Window as an Administrator
  4. Change the directory to the path where AD FS 2.0 was installed.
    1. Windows Server 2008 C:\Program Files\Active Directory Federation Services 2.0
    2. Windows Server 2012 C:\Windows\ADFS
  5. Add the server with FsConfig.exe

FsConfig.exe JoinFarm /PrimaryComputerName PRIMARY AD FS SERVER /ServiceAccount DOMAIN\SERVICE ACCOUNT /ServiceAccountPassword PASSWORD /CertThumbprint “ff eb 43 bb 8b f9 34 56 4b 45 ec 6f 53 bb 99 7f bf 48 7e”

Now we have the second AD FS server added to the AD FS farm.

 

 

Network Load Balance the AD FS Servers in the Farm

Now that we have two servers in the AD FS Farm, we still have to load balance them. In an Enterprise production environment, I always recommend that you use a hardware based load balancing solution. In non-production and small to medium organizations you can use Windows Network Load Balancing. Regardless of the load balancing solution, you need to make sure that you are load balancing TCP 443 to the AD FS Farm name.

NLB Cluster Name – sts.office365supportlab.com

Nodes –

FS01.office365supportlab.com

FS02.office365supportlab.com

 

If you need help configuring Windows NLB, please use Configuring Windows NLB for AD FS 2.0

 

DNS Configuration

Since we are now using network load balancing, we need to make sure that our A record for sts.office365supportlab.comis updated with the IP address that you assigned as the VIP to the NLB cluster.

Type Name IP
A sts.office365supportlab.com 10.0.0.20
A fs01. office365supportlab.com 10.0.0.14
A fs02. office365supportlab.com 10.0.0.17

 

Getting to know the NEW Office 365

  1. Does Microsoft have FREE training for the NEW Office 365?
  2. Signing up for the NEW Office 365
  3. Adding and Verifying a Domain for the NEW Office 365
  4. Creating Cloud Users for the NEW Office 365
  5. Configuring Desktops for the NEW Office 365
  6. Exchange 2003 Cutover Migration to the NEW Office 365
  7. Exchange 2007 Cutover Migration to the NEW Office 365
  8. Setting up AD FS and Enabling Single Sign-On to the NEW Office 365
  9. Setting up AD FS Proxy Servers for Single Sign-On to the NEW Office 365
  10. Setting up Directory Synchronization with the NEW Office 365
  11. Activating and Licensing a Synchronized User in the NEW Office 365
  12. Testing Single Sign-on to the NEW Office 365
  13. Making the Single Sign-On Solution Highly Available
  14. Exchange Hybrid Deployment with the NEW Office 365

Thanks for visiting and reading my posts. I am always looking for more ideas. Please comment or email me with what you would like to see.

Kelsey Epps

Office 365 MVP

Email Me Follow me on Twitter Connect with me on LinkedIN Facebook Me

 

Configuring Windows NLB for AD FS 2.0

When we have two or more AD FS and AD FS Proxy servers we install them into a farm configuration. Even though the AD FS servers are installed in a farm configuration, we still need to network load balance them. This can be done with hardware (recommended for large Enterprise deployments) or with software (recommended for small to medium deployments). This post will cover installing Windows Network Load Balancing on Windows Server 2012.

 

Installing Windows Network Load Balancing Feature

  1. Login to the AD FS server with an Administrative account
  2. Open Server Manager
  3. Click Manage
  4. Click Add Roles and Features
  5. Click Next

  6. Select Role-based or feature based installation
  7. Click Next

  8. Select the AD FS server from the server pool
  9. Click Next

  10. Click Next, not adding any server roles

  11. Select Network Load Balancing from Features

  12. Add the required features by clicking Add Features

  13. Click Next
  14. Click Install

  15. Let the install finish and reboot the server when completed. While you are waiting, complete the same steps on the second AD FS Server

 

Configure Windows Network Load Balancing

Once the feature has been installed on both nodes, make sure that they are both rebooted.

  1. Login to the primary AD FS server with an administrative account
  2. Open Server Manager
  3. Click Tools
  4. Click Network Load Balancing Manager

  5. Click Cluster
  6. Click New

  7. Add the primary AD FS server name
  8. Click Connect

  9. Click Next
  10. Verify that the Priority is set to 1 for the first node and verify the IP address
  11. Click Next

  12. Add and IP address (VIP) for Windows NLB to use
  13. Click Next

  14. Add the Cluster Name – Full Internet Name (matches the AD FS Farm Name)
  15. Change to Multicast
  16. Click Next

  17. Click Edit (we need to limit what we are load balancing to TCP 443)

  18. Change the port range to 443 – 443
  19. Change the protocol to TCP
  20. Click OK

  21. Click Finish

  22. The primary AD FS server is added and the NLB cluster is converged (green is good)

 

Adding the Second AD FS Server to the NLB Cluster

 

  1. While still working on the Primary AD FS server, open Network Load Balancing Manager
  2. Right click the cluster name
  3. Click Add host to cluster

  4. Enter the name for the second AD FS server
  5. Click Connect
  6. Click Next

  7. Verify the priority is set to 2
  8. Verify the IP address matches the second AD FS server
  9. Click Next

  10. Verify the port and protocol match the cluster (TCP 443)
  11. Click Finish

  12. Second AD FS Server is added and converged

 

Update DNS

Now that the AD FS Servers are load balanced, we have to update DNS. Make sure that the A record for the AD FS Farm Name is updated to match the NLB Cluster IP. This will allow for NLB to direct AD FS traffic to the two AD FS Servers.

Type Name IP
A sts.office365supportlab.com 10.0.0.20
A fs01. office365supportlab.com 10.0.0.14
A fs02. office365supportlab.com 10.0.0.17

 

Thanks for visiting and reading my posts. I am always looking for more ideas. Please comment or email me with what you would like to see.

Kelsey Epps

Office 365 MVP

Email Me Follow me on Twitter Connect with me on LinkedIN Facebook Me