Groups-Yammer-team-planner

Leave a comment

Last night at the SharePoint Québec Usergroup meeting we had a great discussion about the collaboration tools that are available with Office 365. SharePoint, Groups, teams, Yammer, Onedrive for Business and all.

Here a few links that were shared in order to help understand better the different tools.

Microsoft Teams, groups and Yammer general information

Groups

Deploying and governing groups

Get the Latest on Office 365 Groups – Overview, What’s New and Roadmap

Yammer

Planner

Team

 

 

 

Yammer connected to Office 365 Groups

Leave a comment

Microsoft is rolling out a new feature on Office 365 that will connect Yammer groups to Office 365.

They should be done rolling out to all tenants by March 31st 2017.

It is already enabled on my tenant.

In order to use the connected Yammer groups you will need to Enforce Office 365 Identity on your Yammer Network.

In Network Admin, select Security Settings, then Enforce Office 365 Identity.

Once it will be enabled, you will get a new Office 365 group when you create a Yammer group. This Office 365 Group will be connected to your Yammer group.

You will see Office 365 resources in your new Yammer groups.

From your Yammer group you will have access to

  • In the coming months, Microsoft will replace the Yammer notes with the group OneNote Notebook.
  • When the group is created from Yammer, it will use the Yammer conversations.
  • The Yammer connected group makes it easier to share files from Onedrive to your Yammer group conversations
  • Since the group email address is part of the Exchange global address list, it will be easier to send email to the Yammer conversation.

More information on what you will get with Yammer Connected Groups.

https://blogs.office.com/2016/09/26/yammer-strengthens-team-collaboration-through-integration-with-office-365-groups/

SharePoint Online Public Web sites

Leave a comment

Public Web Site has not been available to new Office 365 tennant for a while.

Existing tenant that had a public web site could still use it.

Beginnig May 1 2017 you will not be able to use your SharePoint Online Public Web site… Unless you required to keep your site until March 31 2018.

Steps to request to keep your site until March 31 2018.

1. Log in to the SharePoint Admin Center.
2. Click Settings.
3. Select the I’d like to keep my public website until March 31, 2018 option.

Act now if you have a SharePoint Online Public Web site.

More information

 

SharePoint Online Site Mailbox

Leave a comment

Microsoft has announced that SharePoint Online site mailbox are going away.

If you were not using them, it is not an issue. However, you will not be able to create new site mailbox stating in March 2017.

Your existing site mailboxes will continue to work for a while, but you should plan to transition to Office 365 groups.

Here is the message received in the message center:

 

Restrict access to SharePoint Online from network location

Leave a comment

Office 365 now offers an option to allow access to SharePoint Online site from only specific IP addresses.

To allow access to your SharePoint Online sites from specific IP address locations:

  • Sign in to your Office 365 administration center
  • Go to the SharePoint administration center
  • On the left navigation bar click on Device Access
  • Specify the IP addresses that you want to allow

Important: Make sure you enter your external (internet IP address). If you enter the wrong IP address you will not have access to all SharePoint Online sites including the SharePoint Administration center. In this case, you will need to open a ticket with the Office 365 support team to remove the restriction for you.

If you try to access a SharePoint Online site from an IP address that is not in the allow list, you will receive this message:

access-restricted

Note: At the time of writing this article, in order to allow access to SharePoint Online from only specific IP addresses, you might have to activate first release

See this article to activate first release: https://tremblayse.wordpress.com/2017/02/09/office-365-first-release/

Office 365 first release

Leave a comment

Microsoft makes frequent updates to Office 365.

In order to prepare and test these updates, an Office 365 tenant administrator can allow everyone or specific users to have access to these features before they are publicly available.

This gives you time to test and prepare the documentation to train/notify your users about the changes the upcoming changes in Office 365

It is very simple to activate.

  • Logon to your Office 365 Admin center with your tenant administration account.
  • Go to Settings/Organisations profile
  • Edit the release preferences to allow access to the first release

Note: It might take up to 24 hours to be activated.

 

More information about first release: https://support.office.com/en-us/article/Set-up-the-Standard-or-First-Release-options-in-Office-365-3b3adfa4-1777-4ff0-b606-fb8732101f47

Working with SharePoint ULS Logs

Leave a comment

Microsoft SharePoint Unified Logging System (ULS) is great to help you troubleshoot issues in your SharePoint Farm.

The ULS logs are storing information about events (Errors, Warnings, Information) and activities that are running on your SharePoint Server.

By default, SharePoint log files are saved to the following location: C:\Program files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS.

Note: You should change the location of the log files to another drive.

In the Microsoft SharePoint Central Administration site, you can set Logging level for different categories and change the log file location.

Logging level can be set to:

  • None
  • Critical
  • Error
  • Warning
  • Information
  • Verbose

When setting the log level you can choose all categories or a specific category.

Set-Sploglevel

You can also use the Set-sploglevel PowerShell cmdlet to set the logging level.

Ex: Set-SPLogLevel -TraceSeverity verbose -EventSeverity verbose will set logging level to verbose for all categories.

Once you are done with your troubleshooting, you can use the Clear-Sploglevel cmdlet to reset all categories to the default value.

New-Splogfile

When configuring the log level to verbose, the log file can become very big. One way of working a smaller log file while troubleshooting is to use the New-Splogfile PowerShell cmdlet.

The New-Splogfile PowerShell cmdlet will create a new log file.

You can use the command before trying to reproduce your problem, and run it again when you are done. Then you will have a log file for only the time that you worked on your issue.

Note: If you have multiple servers in your farm, you will need to run this on every servers.

Merge-Splogfile

You can also use the Merge-Splogfile PowerShell cmdlet to create a smaller log file.

Using the following command will create a log file with the information from 11:00 to 11:30 on October 27th 2016, and will merge the information from all the servers in your farm into a single log file.

Merge-SPLogFile -Path “D:\Temp\MergedLog-20161027-1100-1130.log” -StartTime “27/10/2016 11:00:00” -EndTime “27/10/2016 11:30:00”

If you know the Correlation Id you can use the following command to create a log file with only the information about the correlation id.

Merge-SPLogFile -Path “D:\Temp\MergedLog.log –Correlation YourCorrelationID

See more examples of Merge-Splogfile
https://technet.microsoft.com/en-us/library/ff607721.aspx

ULS Log viewer

There are ULS log viewers that will help you reading the log files instead of trying to use Notepad or Notepad ++. These tool are pretty handy, you will be able to filter logs and it will be much easier to read than trying to read from Notepad.

https://www.microsoft.com/en-us/download/details.aspx?id=44020

https://sharepointlogviewer.codeplex.com/


Happy troubleshooting!

Older Entries Newer Entries