We all know that SharePoint is a mighty powerful platform, right? It's no surprise that its 2013 installment (including Office 365) is filled with cool and useful new features making upgrading a must. But for that choice to be obvious, you obviously need to know what these features are and how they will drastically help you build what might very well be one of the Greatest SharePoint of all time!
So here it is, the recording of our "111 Hot New Features in SharePoint 2013" webinar, hosted by SharePoint MVP Benjamin Niaulin. He'll take you over all SharePoint 2013 has to offer, the just damn simple way. That is what this webinar is all about! So sit tight, buckle up and enjoy the guided tour!
Here's a quick recap of what Ben covers in there for you!
How is the social factor integrated in 2013 and what place has Yammer in it? Lots of changes and improvements done here. Functionalities like easily referencing other users, hashtags, Community Sites and Portals are just a few of the many new things here.
Today, SharePoint is all about making collaboration on documents easy. Therefore, it's pretty logical to find tons of new features there. The new version of SharePoint and its Office 365 counterpart gets super intuitive Collaboration wise. Drag&Drops, Geolocalisation, External Sharing… You name it! And that's not considering all the improvement made to existing features.
Without the ability to Search through Sites and Libraries, SharePoint would be missing the point… So Ben popped the hood and took a look at the new Engine and other features that came along. A prancing horse right there, let me tell you! New Web Parts, new Crawling options and features, Query Suggestions, etc.
This right there would be reason enough to upgrade!
Branding, here's what makes the difference between your grand-dad's SharePoint and yours! This new version allows you to do so much more to build beautiful Master Pages.
Web Content Management
Anything related to web pages in SharePoint 2013 is now as simple as ABC. This will make managing these pages super easy, and super intuitive for your end users to provide a great experience. It's so easy, your five years old could do it! (Please note: We do not encourage child labor of any kind.)
That is just a fraction of what's cover in this webinar recording. We'll keep a little suspense! But think Apps, Migration, New Interface, Records Management, Power BI, Visio Services and much more.
By the way, we also released an eBook these 111 Hot New Features in SharePoint 2013! It's worth checking out.
** Our video transcripts are generated automatically. So, while we meticulously review them, some typos fall through the cracks. Please excuse any errors, and feel free to let us know if any pop up. **
Benjamin Niaulin, and we'll be looking at Discover SharePoint 2013. This session is about looking at everything going on, new features, and then towards the end, we'll look at the different migration scenarios that are possible. We’ll look at actually what works and what doesn't.
So there's a lot of content to be looking at Discover today, so I hope you brought your notepad. We will be recording this entire session so that you can view it afterwards if you need to. We will send all of the information tomorrow.
If you have questions, I have two great friends, three great friends, colleagues of mine, that are helping me out today so that if you have questions throughout the session, you won't see me or hear me answering but ask for your question. However, Jean-Luc, Sebastian and Yohan will.
So good evening, and thank you for joining if you're joining us so late today. So thank you very much. Let's discover SharePoint 2013 together. So here, the first thing, obviously-- hi, my name is Benjamin Niaulin. We'll be doing this today.
After the session, visit the blog. That's what I am here for. This is provided by Sharegate. Sharegate is a SharePoint migration tool and a SharePoint governance tool that's going to be out of beta today and released for you to be able to govern your SharePoint. So if you have any migration, don't worry. I will not be doing any advertisement or any sales pitch of the product today. this will be strictly about SharePoint, of course.
Looks like my colleagues have muted themselves.
And here the user first is going to be looking at SharePoint 2013 arrive. What are the first experience that the user has? Well, initially, the user will be thinking, wow, cool. Look at all the changes. Look at everything happening inside of the application. SharePoint has changed. The interface has changed.
And then after a few seconds, or a few days, I should say, of using SharePoint, the users say, hold on a second. Before I could access anything that I wanted straight from the Site Actions menu. Then, certain options are simply no longer there. So they'll go into the Site Actions menu, and you'll see that Create Site is no longer in the Site Actions menu. Then they'll notice that switching language, if you have multiple languages, simply is not possible either. So it's a very tough experience if you don't have good communication or good training towards the beginning.
The IT pro. So what's changed for the IT pro? You'll see that straight away, he's not happy about it. He's not happy because it requires more server. Everything that he used to be able to do using the interface, using the actual SharePoint Central Administration, a lot of it is simply not available anymore because they want you to use PowerShell.
And I'll be honest with you. I am an IT pro, as well, as well as I'm an architect. And I'll use SharePoint any way that I can to make it work without doing development, but it's not always easy for everyone to start using PowerShell command. So it is a little bit tough to get into. And the way I'm sounding, you'll probably think that he's going to tell us not to use SharePoint 2013, but don't worry. We'll get to all of that. It's not necessarily the case. It's just important for us to understand everything that is happening and all the changes.
Then we have the developer. Now, this is a tough one, because as a developer, you probably just finished learning how to develop for SharePoint 2010. It's a long process. We finished the internet. We finished the portal. And just now, we're saying, well, you know, everything that you've learned for SharePoint 2010, yeah, we don't want you to do it that way anymore.
So if you were using SandBox Solutions to code custom solutions for your customers or for yourself, well, we don't really want you to use that anymore. Obviously, there are certain things that require you to be using SandBox Solutions, but essentially what they're saying is not to use them as much as possible. What they do want you to use now is to develop apps, apps that will be available in either the Microsoft SharePoint app store, or in an enterprise-provided app store, for your users, the end user, to be able to just plug into your environment.
However, the development process and some of the limitations that come with building apps are completely different than what we are used to when we're developing. Then you've got to learn things like Display Templates. You've got to learn HTML5, CCS3 if you're not comfortable. I'm running out of breath just thinking about all the things that a developer has to think about.
So when we're thinking about those three things-- the end user who's very excited to see the new changes. It's a lot easier for him to use, but then after a few seconds, can't find himself within the application. Then we have the IT pro, who, it's just more work basically, because now it's PowerShell commands. And it's also, what we said, more server, more power.
And then we have, of course, the developer, who needs to basically not forget everything he's learned. Obviously, there's a lot of the core of SharePoint that stays the same. He'll have to know what a SP web is, and the list of libraries, and all that. But the concept of development is definitely changing, and we will need to adapt for it, as well.
All right, I hope everybody's doing well today. The last thing that, obviously, we have to think about is, yes, I'm learning about all these new things for SharePoint 2013, but what about Office 365? Instead of migrating to SharePoint 2013, should I be starting to look at the clouds? What are the limitations? Do I get the same features?
I don't want to say that they do updates without telling you, but there's definitely changes that arrive, and you're not always able to adapt quickly to them. So it's very, very difficult, and you have to find out what is the best and right for you. Will it be On-Premises SharePoint 2013? Will it be Office 365 that you want to look into? Or is it even OneDrive for Business?
And the only reason I've added it recently is because I've been getting so many questions, which is why I wrote a blog post yesterday or the day before on the subject. And we'll talk about OneDrive for Business in this session today, absolutely, because it is a big piece of SharePoint 2013. The issue is that everyone is a little confused with what this actually is. And of course, the marketing on the Microsoft side makes it look to be a SharePoint in itself when it's not really SharePoint. But you can subscribe to OneDrive for Business as a standalone subscription, which is like a small Office 365 in a certain way.
So you definitely have to be looking at all the possibilities. Who are you? What do you need as a business? Would do you need to do? And will it be looking at migrating to SharePoint? Will it be looking at migrating to Office 365? Or will it be looking at migrating to OneDrive for Business? And what do you plan to do with it? So this is what I try and I hope to cover here today.
I know. I know, guys. I'm the same way. I'm confused. There's a lot going on. So what's happening? And on the other hand-- and I thought this image was very, very appropriate-- is it worth the switch? Because we've spent quite a bit of money implementing the previous SharePoint that we have.
And we have end users. We have our, not the administrators, but we have the owners of the business, the CEOs, CIOs, that are wondering, well, Ben, that's nice. Is it worth the switch? Because I'm ready to release the dragon in this scenario and eat you alive if this is not going to work or if what we're going to upgrade is for a true business value. We're not going to just upgrade because we're geeks and we want the latest and greatest.
So, basically, what I want to be able to do at the end is hopefully answer the question, is it worth the switch, and what's new? And to be honest, I can't even answer the question myself. I will tell you my personal opinion, but it will definitely depend on what it is that you plan to do. What are your business needs? What do you plan to do with SharePoint? And do you think that's going to help you save on terms of cost and make sure productivity goes up, and whatever is the case in your situation?
So let's discover SharePoint together. I know, guys. I do have a French accent, but that's what it is. Unfortunately, we're all based in Montreal. That's where I'm from. We will have a little French accent.
So, let's discover SharePoint, guys. What exactly is happening in there? Well, we'll look at the new interface. We'll look at what's changed, very quickly. I'm definitely not going to spend 20 minutes on the interface itself, but I think it's important to look at what's changed and how it's changed.
We'll look at the social aspect of it. Because I'm obviously working very often with Angelina Jolie and Brad Pitt, so I want to make sure that our conversations are-- I'm joking. I'm not actually working with Angelina. I wish. And would I be doing this webinar today? I don't know.
But we'll be looking at the social, what's changed with SharePoint 2013. We'll talk a little bit about Yammer, as well, because obviously this is a big piece of the social insider of SharePoint 2013. We'll be looking at collaboration, what's changed in terms of our document libraries and how we work with others with SharePoint 2013. And I'll always mention Office 365 versus SharePoint, obviously, and if I can, versus the OneDrive for Business subscription that's available.
This is a big piece. And I know. I've seen the attendee list so far. I know that some of you, we've met at a SharePoint Saturday or at a SharePoint conference. And thank you for joining here again today. And you probably know that I'm a big fan of what's changed in SharePoint Search. In fact, this is one of the number one reasons that drives me to upgrade to SharePoint 2013, to be very, very frank with you. If it wasn't for search, I'd probably be looking a lot closer at SharePoint 2013 to make sure for each scenario that I do want to upgrade, but search really makes it worth it for me.
Branding. And of course, classic Ferrari.com. You can also look at Volvo.com. You can be looking at one of the pages, one of the sites, of Best Buy. There's a lot of websites today. One that we've even built ourselves, www.laval.com, that is also built on SharePoint 2013 combining the search engine to build this very, very dynamic and not-static website that will adjust based on what the user is asking for and what he's looking for.
But what's changed in terms of branding? It is also a factor when we're looking at migrating because, believe it or not, user adoption is closely attached to how the experience of SharePoint is and how it looks. It's not true that you can leave out-of-the-box SharePoint for an intranet and hope that every one's gong to appropriate and start using it. It needs to have some kind of feel. It has to feel like your brand, very, very important.
We'll look at web content-- wow, are we going to be looking at all of this in one hour? I better start talking a little faster. We're going to be looking at web content management, as well. So how does SharePoint 2013 make anything related to the intranet, extranets, or public-- for anything where you want to manage web pages with SharePoint, how easy does it get? How do I make a refinement panel that allows me to filter the screen size with a little icon like this to make it a lot easier to use? And again, when we're talking about branding, we're talking about user adoption, of course. The price like this is a lot better than a bunch of bullets that come down in the price box.
We'll talk about apps a little bit. There's nothing really to it. We'll obviously talk about it, but as an end user or architecture perspective as a reason to migrate, basically you have a SharePoint store where you can look for apps and add them to your pages. As a developer, it's definitely a whole other story.
We'll look at the migration scenarios. I think Microsoft did something really, really well with the migration path. However, it is only available when you're on SharePoint 2010 and going to 2013. And that's not including Office 365. So we'll look at the different migration scenarios. I want to talk to you about the real implementations, what happens exactly when you do migrate. But there is definitely some good to it.
And obviously there's tons of other things. We're talking Performance Points, Records Management, Power BI, Visio Services, Office Web Apps, Shredded Storage for performance. There's tons of changes in SharePoint 2013, and unfortunately, I only have an hour so I can't focus on all of them at the same time. But I've selected a few that I find were what made me want to migrate to the next one, so we'll be definitely looking at that.
So first, the interface. And what better way to look at the interface than walking-- aw, that's a nice picture, isn't it? So let's take a walk through it together and see what's changed in the interface. So what I've done is I've created a SharePoint. So you'll notice that my SharePoint is quite fast. A lot of people always make fun that I'm using a Mac, but my SharePoint is running on a virtual machine. And I know my colleagues here answering your questions are probably laughing right now, but it's running.
So what's changed in the interface? So of course, the first thing that we're going to see is this Site Actions is now a gear. And if you're using Internet Explorer, what do you have right above this gear here? Another gear for Internet Explorer options. So it's not ideal, but I think, it's what it is.
The Site's Actions is essentially moved back to the right side. So if your users came from SharePoint 2007 and are going to 2013, they won't have too much trouble because that's where it was in 2007. And in 2010, they put it on the left side, and in 2013 they put it back on the right side. So SharePoint 2015 might be back on the left side. Who knows?
What else has changed? Well, you'll notice that there's a Suite Bar. They call this the Suit Bar or the Suite Bar. Essentially, this is controlled by SharePoint. You can add links to it using, generally, PowerShell to add whatever links that you may want at the top. Usually, if you're on Office 365, it will come with Outlook, Calendar, and all of these other exchange-related links. And then you'll have the news feed and everything else that you may want.
You may notice that now there's a new button, that I cannot see because of my bar here, to remove the quick launch on the left side quickly. So when you want to go full screen, especially useful if you're using your calendar view in SharePoint, this is great.
One thing that I absolutely like is that, if you have the power to manage the navigation here on the sides, you can do it directly here. You can click the new link and it will be available directly below or wherever you want. And if you're not-- so this is the downside of using a Mac, you can actually drag and drop them, but using a Mac, you cannot drag and drop your links from top to bottom. So drag and drop link here does not work unless you're using a Windows PC with Internet Explorer. I do believe it works with Chrome.
We do have the same edit links here at the top. And essentially, this is what's changed with interface. There's nothing really to it more than that. I definitely want to remove those pop-ups here. There we go.
But what we're going to be looking at is all the other changes, so don't worry. The whole session is not about these new clicks and this new interface, but this is where I want to start before we head in. The rest we'll see as we go, but this is what SharePoint 2013 looks like. If you go to Site Contents, you'll also notice-- and this took some time for me to get used to because it's not so easy to get used to the new way of presenting the All Site Content.
This is also where you'll find the Create a New Sub Site. Before we'd go to Site Action, Create a New Sub Site. Not available anymore. You've got to go to the Site Contents and then click on New Sub Site, and from here, you'll be able to create the sites that you may want.
The last thing I want to add before we continue on with the session, and this was a big one for me. Why? Because we're here in Montreal, and in Quebec, Canada, it is very bilingual. It's very much French and English. There's actual laws that require us, or for many companies based here, to have the environment available in French, as well, for anyone that requires it or requests it in the company.
The problem is that, even if I install the language pack, which I have in this scenario, it is not easy as a regular end user to just go on his name like he used to and just change the language. You just can't. Now, you'll have to go to your My Site, or your About Me. You'll have to click on Edit Your Profile. You'll have to know to click on the ellipsis, the three dots here. Click on Language and Region, and then choose the language preference that you want for your site. And it will be global. That means it will affect all of your team sites.
Of course, the team sites, if I go back to my Tour site here-- I first have to go to Site Settings, and I have to make sure that in the language setting, I told this site that it is also available in French. Otherwise it will only be available in English. But you can see how it can be very difficult, not only for the end user that wants to be able to switch between French and English quickly, but also for the administrator that's building a bilingual site and needs to test with his account how it will look like in French, how does it look like in English. The title's a little bit longer in French, so I want to adjust a little bit the size. No, you can't do that easily. So it's definitely something to take into consideration before you do the migration.
Let's continue. So what else? What about social, social in the enterprise? What's changed? Well, of course, I've got to talk to you about the social in SharePoint 2013, and I've got to talk to you about Yammer.
So SharePoint 2013. You've noticed in this Suite Bar at the top that I can click on Newsfeed. And once I click on Newsfeed, I will arrive on this Newsfeed-- let's go back. I will arrive on this Newsfeed page where I'll be able to do some micro blogging. And what does that mean? That means I can use mentions with an at sign.
I can use hashtags, just like on Twitter, just like on Facebook, where I can categorize my conversations so I can find them easier later on, find everything related to a specific hashtag, as long as, just like our taxonomy, just like our metadata on our library, people are using the same hashtag. And very organically, usually people tend to follow the same thing.
In this case, this is a French conversation that we've had at work, so I can say that I was about to go to the SharePoint Summit in Quebec. This is the hashtag that we started using, and we started conversation always having that hashtag so that later on, I can find all the documents, all the conversation, related to this hashtag specifically.
And I can follow conversations, or I can stop following conversations so they don't appear on my newsfeed. And I can say "like" again to approve. Sometimes it's nice. Somebody says something, and a very just "like" from your superior, your manager, can always encourage everyone to do more, whatever it is that they were doing.
The thing about the conversation, guys, the newsfeed, is that, they've been trying since 2007, 2010, and 2013. And to be very honest with you, it just doesn't pick up, and it has not picked up. People that are using SharePoint 2013, they have never started using it. It has never become viral within the organization. What happens is it just doesn't feel natural. When you want to add photos, you can only add one photo at a time. And it just hasn't-- a lot of people would add or add-ons from third-party vendors to make it what they wanted to do.
So what Microsoft has done is it bought one of those third parties that was available on top of SharePoint. And that's Yammer, which is obviously very well known today. The thing about Yammer is that it's cloud only, and it will never, never be On-Premises. Now, of course, never say never, right?
But there are no plans of ever bringing this on an On-Premise scenario. They want to keep this on the cloud. You subscribe, and you get your Yammer network where your company and groups and teams can have conversations. However, the integrations that are available as of today with your SharePoint On-Premises, not so much. It's really more, I've got a SharePoint here and I've got a Yammer over there, and we can look at it together.
The integrations that you can see is you can show the feed on your team site. So it can be a group feed for a specific group. You know what? Let's go look at the differences. If I click on Newsfeed here, I'm going to go to the Newsfeed page. And as you can see, not a lot of things happening here. You'll get some notifications from community sites.
I can start a conversation. I can definitely mention someone. Hi, Brett. I have a question about Outlook. Can you help? And he'll get a notification. And it does the job, obviously, but this will only show me the conversations I'm following. There's a little dashboard. It's simple, but it does work.
And I do have a little Yammer that we can quickly jump into, a community Yammer where a lot of people are having different conversations. And there's a lot more things happening. People are having conversations. You can reply to them straight there. Links, pictures, videos. And just kind of praise somebody for doing something, have polls, events. There are actually no longer going to be events very soon. But have my inbox, go into a specific group, and have a conversation. And then what I can do is I can take a specific-- say, I going into the migration group. And I can take this group and put it into a team site and see everything happening there very, very quickly.
So that's essentially the differences. I do want to talk to you about one thing, though. This is really some insight from the Microsoft headquarters in Seattle. The team that was in charge of the SharePoint social, so the team that was in charge of the social features, has now changed their name at Microsoft. The team that used to take care of this is now called Yammer North.
So that definitely gives you a heads-up that if you're planning to use this, there's a good chance that you won't see it in the next version of SharePoint. Microsoft definitely wants to invest in Yammer, so you should if possible start looking into Yammer if you do want to use Enterprise Social.
However, if cloud is not an option, then I probably recommend looking more at third-party tools that can install on top of SharePoint unless what you saw here today is fine with you, obviously. But there will not be any future upgrades to these features. This is what you're going to get, and that's it.
All right, let's continue, because we've got a lot of things to cover. There are other integrations that are available with SharePoint and Yammer. So basically, straight from SharePoint, you can publish to Yammer. You can replace the Newsfeed here with a Yammer link. So people, instead of going to the Newsfeed, they'll jump into the Yammer portal. And it'll be seamless, especially if you have Office 365. There will now be single sign on between the two, but otherwise they'll have to make sure they're logged into Yammer to jump into that Yammer a group. But other than that, there's no integration.
What will be coming very shortly is that in Yammer, whenever you'll be creating a new group, Yammer's going to create a sort of team site template in your SharePoint automatically for that Yammer group. So whenever you have conversations, whenever you have documents that are added into Yammer, it will actually go into your SharePoint team site so that you can manage your document with security, with metadata, with retention rules, with anything over there. And we're expecting that to be coming very shortly actually. So definitely an awesome feature.
Oh, this one. This is a good one. To OneDrive link here at the top. So if you're familiar with OneDrive, the public offering by Microsoft where you can drop your files and get them later, this has nothing to do with it. Very simple.
When you see OneDrive here at the top, this is actually the new name to go to your My Sites. So when I click on OneDrive, I actually go to my My Site, and that's it. So if I go back on my SharePoint, I click on OneDrive here, and I'm on my My Site. That's it. I can here look at the Site Contents. I will see my task list. I will see my blog site. I will see my document library. I can share files. OneDrive means My Site. So that is definitely confusing for end users. Make sure you have a communication plan for that if you plan to roll that out.
The other thing that's cool about your My Site-- or I guess we should call it OneDrive. You get the idea-- is the aggregation of your tasks from all of your sites, so all of the SharePoint sites where you're using a task list where there are tasks assigned to you. So you'll have the name of the site followed by the name of the list and the task that is assigned to you that is not yet completed. But you can click on Completed Tasks and you'll see them there.
But what's cool is that if you have Exchange 2013-- that's what the stars are for. If you have Exchange 2013, it will also merge your Outlook tasks directly here. So with one glance, you can actually see all of the tasks that are assigned to you in one page.
So we have already established that the link for OneDrive here is actually a link to your My Site, but it's not the only thing-- that's why I strongly recommend you go check out the Sharegate website blog. The last post that I wrote is about, what exactly is OneDrive for Business? Because when we're talking about OneDrive for Business, it's actually a synchronization tool. It used to be called Groove. It used to be called SharePoint Workspace in 2010.
And what it allows you to do is to synchronize a document library into your desktop under Favorites. So before it was called SkyDrive Pro. Now it's just renamed to OneDrive for Business. And you'll see your documentary library straight here. This is what OneDrive for Business is, and that is the only thing that is.
The link at the top is to go to your My Site. And whenever you click on the button to sync on any document library, any document library, it will launch the OneDrive for Business application that you have installed on your computer, and it will start synchronizing so that you have access to them on your computer.
So the details of the installation for OneDrive for Business, because you have to install it, is either available with Office 2013, or if you don't have Office 2013, you can install a standalone application, which is OneDrive for Business. If you have neither installed and you click on the button to sync, it will want to launch SharePoint Workspace from Office 2010.
So this is what I'm talking about. I'm in any document library, and I decide to click on sync. It will want to launch the application, but I'm on a Mac. So guess what, guys? There is no client application for the Mac. So unfortunately if you are using a Mac, you will not be able to synchronize offline, at least for now.
You will have to be in a Windows environment. Go to your SharePoint site on any SharePoint site. This one. Go to a document library. You'll have a sync button, and it will launch your Microsoft OneDrive for Business install. And it will synchronize it, just like that, and show you the files in your favorites under OneDrive for Business or under SharePoint for regular team sites. All right, I hope that clears it up. Took me some time, as well. Don't worry about it.
OK, this, I love. It is some feature that every single customer has asked us when we were in SharePoint 2007 or in SharePoint 2010. Hey, Benjamin, Benjamin, I know I'm a member of all and many SharePoint sites. Is there a place where I can see all of the sites that I'm a member of or that I'm working on so that I can quickly jump into them? And I've saved them in my favorites, but the hyperlink has changed. Now I have to go through all of my favorites to change it.
Well, good news. You probably saw me use it a couple of times. You can click on Sites here at the top, and you can see all the sites you're following, and sometimes even some that SharePoint will suggest for you, so you can jump directly to it. You can also say that you want to stop following certain ones so that they don't appear there anymore.
OK, so this is really more for the interface and the things that have changed. The next thing I want to talk about it is a little about security. First, nothing has changed about security. Permissions work the same way. You can do the same permission levels, the same everything. However, from deep end user perspective, it is now called sharing.
So you will share a folder. You will share a document library. You will share a site. And you'll always see these buttons to share, but that's what it's for. It's for your permissions. You simply enter their name or their email address, and then you say with a simple method of security, do you want them to be able to edit? Do you want them to be able to view? And that will assign them the same permission levels that used to exist and that still exist, which is contribute, full control, or read only.
So we've already done the social tour, I think. We've looked at Yammer a little bit. We've looked at social. And we've looked at everything that we've mentioned. In terms of your IT pro perspective, one of the biggest problems that we've had was with the User Profile Synchronization Service. Lucky for us, no more problems with that. You can simply do an Active Directory import. You don't even need to configure the User Profile Synchronization Service if you don't need it. You can simply do an Active Directory import. This will import your basic users properties, and you could have user profiles, no problem.
However, there's a new little service causing problems. We'll never get away from all of them. And that's the Distributed Cache service. Now, of course, if you're doing a single-server Distributed Cache service, it's not going to be a problem. It'll work just fine. However, the Distributed Cache service is required by many services, like the social features, and also, of course, every single search Web Parts, because that's where the cache is going to be stored.
It's also required for other services, not all necessarily a required service. But if you want to create a redundancy for your Distributed Cache service, you'll need to create a cache cluster that's only using PowerShell. And it's quite fun setting it up, believe me. Right, Sebastian?
All right, new site templates, guys. There's two new sites templates. One is called the Community Portal, and one is called Community Sites. The Community Portal is very, very straightforward. What the Community Portal does is it shows you all of the Community Sites that you have created. So the Community Site are a place where you can have discussion, badges, reputations, and people answering questions. So it'll be managing discussions, organize them by categories.
Let me show you quickly. Let's go to my Community Portal. Straight from my Community Portal, I can see that there's a few communities. There's one about SharePoint. There's one about Outlook. And there's one about me, or people, being able to ask questions to the executives.
So I'll go straight to the SharePoint Community Site, and there I'll see that there's contributors. Wow, looks like Angelina has got a little bit more points than I do for now. And I've asked the question. I can create new discussions. I can say whether this discussion is a question. I can put them in categories. The categories, I can browse them through straight over here. I can create new categories.
But if I create or ask a question, somebody can create a reply. And then as the original person that created the question, I can mark one of the replies as the best reply. So very form like, very typical form. You can create badges-- expert, professional-- and then you can assign your badges to certain members. So for example, I can say that, Angelina Jolie's been answering a lot of questions. So what I'll do is I'll give the badge called expert. Save. And then I can go back to my home site, and now I'll see that Angelina has a badge.
So creating this community, you'll have these experts come out out of nowhere. So even if somebody's in marketing, they could be answering a lot of questions about using Word, and using Mail Merge, and other features of Word that could be helping out other people, or just answering questions.
Of course, I do recommend that you have a community manager that's going to make sure that nothing bad is happening. You can actually manage the community so that you can enable reporting of offensive content if you think that it's going to be a problem. But to be honest, I haven't seen any of that problem in the past. So that's the Community Site and the Community Portal.
So we've done the demo. This is us at work. Every Monday, everybody has to wear a T-shirt with an animal. I know.
All right, what else has changed in terms of the Team Sites? Well, you'll see that your Team Sites-- and this is only if you've enabled Office Web Apps. Office Web Apps is technically free. You will need your users to have user licenses to be able to use this. But Office Web Apps is an extra server that will allow you to review documents and edit documents that are office documents-- Word, Excel, PowerPoint, and so on-- directly in the web browser without installing anything extra. It will also work on your iPads, your Surfaces, your devices.
Very, very practical for those on the road that don't necessarily have Office installed everywhere. And I've been using it quite a bit, to be honest, because once I'm on a Mac. And the Office for Mac isn't as awesome as the one that is available directly on the web browser. So very, very cool.
Now, If you do have Office Web Apps installed, then you'll also be able to integrate them with your Team Site. So whenever you create a new Team Site, you'll see that there's a workbook that comes with it. If you do not have Office Web Apps installed, when you create Team Sites, workbook's not going to be available. And even if you add Office Web Apps feature in the future, all of your previously created Team Sites simply will not have this.
And what this is a workbook that does not belong to a particular person. It's a OneNote workbook that belongs to the actual site. So very practical, very, very practical for people to share notes. The benefits, well, it's going to create the OneNote for the site or for the team. And that means that it's going to inherit the permissions of the site automatically, meaning if somebody is no longer in the team, they will no longer have access to the OneNote workbook. And somebody that's going to join later on will automatically have access to all the notes that people have taken.
So you can put notes that will help people, new employees, on things to get started quickly rather than starting to build wikis necessarily. A lot of people are a lot more comfortable with OneNote. And it is a great tool, to be honest. So definitely check it out. And there is OneNote for Mac.
All right, guys, collaboration. Collaboration is a big piece. It's one of the main reasons why SharePoint is actually sold in businesses. There's two reasons I would say that SharePoint 2013 is usually sold. One, intranet. We want to replace or we want to build an intranet. We want it to be easy to use, easy to create. We want it to be nicely designed. And we want it to be integrated to our business solutions or our business information.
And the other reason is file sharers simply don't work. We're in 2014. We're going to 2015. The principle of file sharers and having documents in one folder or one other folder, not finding it, having documents that have underscore final version, underscore Eric, underscore V7, is simply not acceptable anymore.
We need to have one document in one place. We want multiple people to be working on the document at the same time, so co authoring. And we want to tag the document with the right metadata, so that however you're looking for your document, you'll be able to find it regardless of where it is stored. You need to find it based on what it contains. This is one of the biggest problems we're facing in the IT world is always, how do we find our content?
So there's lots of small upgrades that make the collaboration a lot better. There isn't a kapow feature that's going to be, that's the reason we're upgrading. It's a lot of small add-ons that just make it that much better.
So the first one is obviously the drag and drop. Users can simply take your files and folders, move them into the document library, or the Web Part of the document library, wherever you have it, and the documents will be uploaded instantly.
Let me show you. I'll go to a document library. Let's go back to our demo today, or wherever we're planning to go. I'll go into document library. And say I have some things on documents. We can look at my invoices if you want. And we'll take all of this here and just drag and drop it here. And it's done. Wow, that was definitely very, very fast.
So the only problem with that-- what do you see happened? Well, I have three columns, and I was really hoping to enter that metadata. The whole point of a document library is to tag my documents. So it didn't even bother telling me or asking me or doing anything regardless.
So you really need to be able to communicate with your end users or make sure that somebody is looking at making sure that metadata is entered. The other thing is you can make the columns required columns, and in this case the documents will stay checked out and not available for viewing by anyone else except the administrators.
All right, what else has changed? Well, there's no more Edit in DataSheet View. It's now called Quick Edit. It's been definitely upgraded. You can now even create columns. So you can go into the little plus sign when you're in edit mode. You can create columns straight from here. You can copy paste into it. You can drag and drop. You can use it like Excel basically. Very, very, very interesting.
There is also, I forgot to mention, a little search box within every document library that will search as you type. Very, very practical to find your documents within a document library very, very quickly. So this is one of my favorite add-ons. As you can see, there's no big feature for collaboration, but all of these little things really make it interesting.
Now, did you guys know there's a new column for geolocation inside of SharePoint for Bing Maps? Let me show you. And it's really, really hidden. So first and foremost, your administrator will have to register with Bing Maps, something that I have not done. So you will see that my maps will have a big warning message that says I have not activated an account.
But I have to create a PowerShell, because obviously everything is in PowerShell now. And I've created a script that basically says, go into this specific site, find a list called Partners, and then I want you to add a geolocation-type of column named Location. This is going to become a site column, so I can reuse it within my site collection. There are other ways of deploying this column.
But let's look at what's the difference now. Let's go into my Partners list. And now there's the location column that has been added. So whenever I create a new item, I can say, well, one of my partners is Sharegate. And it's a type of partner-- I have no idea, so we're going to say, awesome. The account manager is Brad Pitt. And if I want to add a location-- my laptop doesn't have GPS so I can't use my location, but I can definitely specify location.
Yeah, I know. Latitude, longitude. Well, of course, it's a 45.67999. Unfortunately, you have to go to Bing Maps-- nice picture-- and then you'll have to do your search here. And then once you find your search, you'll have everything directly here, the latitude and longitude. Come back here. And I usually just cut and paste it. Remove the comma. Very user friendly. Everybody knows how to use that, no?
You can obviously develop some things so that people can use it a lot easier. But I'll click on OK, and there's the Bing Map, straight there, right in the center of Montreal. Well, not really, but there's Montreal. And you can see that the specified credentials for my SharePoint form are invalid.
So unfortunately I will always have this mess that's on top, but when users come, they can quickly click on geolocation. Wow, that is pretty cool. It's out of the box. It'll work. You can replace it with custom development to get Google if you prefer Google, but it does the job and it's very easy to use. A lot of people don't even know that it exists, unfortunately.
All right. Wow, look at the time. Look at the time. So Office Web Apps if it's installed allows you to preview the document directly from within your ellipsis. So if you're looking in your document library, you click on the ellipsis, and you'll have a preview of the document that you can actually scroll. You can scroll through the Word document, through the PowerPoint, through the Excel, and see and make sure that it is the document you're looking for.
If you click here, you'll be able to print to PDF. You'll be able to embed the document itself in an Office Web Apps coding so people can view the document directly on the web by pasting the code that that will generate. You have the hyperlink directly here, so you can copy paste it. So basically, this little pop-up makes it that much more usable inside a document library. See? All of these little add-ons just make it that much friendlier for people to adopt your document libraries and start using them.
Copy pasting from Word to SharePoint now maintains 100% of the styles. So that's awesome, because a lot of my content editors and my content authors tend to create it in Word and then copy paste it into SharePoint, but that usually would add all of that weird HTML. Now it really keeps it clean. But it's still not going to automatically upload your picture for you when you copy paste. That means you're going to have a zone for your picture. It will be empty, and then you'll have to upload your picture manually to a SharePoint image library or an assets library if you wish.
It's made for that rather than the content. Because the problem with the Content Editor Web Part is people are adding it everywhere on all these pages. And then it comes down to do a migration, and then everybody's complaining that their custom code or their page doesn't work correctly anymore. Well, that's because you had no idea that they had all this custom code running in a Content Editor Web Part, which was not meant for that. So encourage people to be using this.
SharePoint also allows you to play videos straight with a video player. You can also upload videos. I have an entire session on that if you like. I do not recommend that you upload large videos into SharePoint. There is a trick. Bing it or Google it. Uploading your videos into SharePoint without actually uploading them to SharePoint.
The trick is to create an ISS website. And what you do is you store your videos on a regular file sharer for performance reasons, and then you have SharePoint upload the URLs and pretend that those are actual videos inside of SharePoint. It's a very easy trick. It doesn't require any special servers or anything of the sort, but it makes the performance of video playing a lot better than uploading your videos into a document library and thinking that 10,000 users are going to be able to run that straight from SharePoint.
The default video player is still going to be Silverlight, but it will shift into HTML5 so that all devices will be able to play it. But to be honest with you, I've had a little bit of issues running even with the HTML5 player.
Storing your videos using the document set video that comes with SharePoint, whether they're stored in SharePoint or, like I recommend, in an IES server. However, try to see if there isn't a custom video player that you can get online, or even pay for, like Brightcove, if it is something that you think is going to be valuable for you to create a online learning center, for example. Because my personal experience with the video player is it's good for basic needs. Let's just put it that way.
There's also the Site Mailbox. So this allows you to connect a site as a mailbox in your Outlook, and look at it, and navigate through it. However, you still can't drag and drop documents directly in there. It'll just make sure that you can see the documents and maybe bring them from attachments into a document library, but not necessarily vice versa. It will do hyperlinks, though, so definitely very practical for that.
How are you guys doing? Let me just grab some water here. Much better. I hope everybody's doing OK and we're learning some new things. I bet you didn't know for the geolocation column. Or maybe you did, but a lot of time, people get surprised, even in my own team sometimes.
What about what's changed for discovering our content? All these other things are nice. The interface changed. That's cute, Ben. What about the rest? What about finding my content? Well, one of the biggest problems that we've had was impossible to see content from other lists and other libraries.
Even worse for another Site Collection, we had to learn how to code in XSLT. We had to know how to change the way the results are shown, were very difficult. Contextual results were nearly impossible. So that means showing things in the context of the user. Hi, my name is Benjamin. And I'm in IT and I'm currently visiting this site. Can you show me results for me and not for a generic audience? Having to ask the admins to add extra managed properties, very, very difficult.
So obviously a lot has changed for search, a lot. I think it is the biggest change in SharePoint 2013 is search. Obviously, FAST Search, which was a third-party product, has been integrated for free into SharePoint 2013, making the algorithm for search, adding continuous crawl, adding new Web Parts, modifying the existing Web Parts, and allowing us to do many, many other things that just make it worth it.
Yes, continuous crawl. I usually have very, very good examples, and I do encourage you to check out my other video recordings on our website, specifically for search and how it works. But continuous crawl not continuously crawling, guys. Continuous crawl is still every 15 minutes, just like before. However, it's capable of running parallel processes.
So you'll have multiple processes of search running on your box. This will definitely cost a lot in terms of RAM, in terms of CPU on your server, so don't necessarily activate to everywhere. Activate it only in places where you do need it. And you can also change the schedule, but the purpose of continuous crawl is to make sure that you search index is very fresh with the content that you need.
So for an intranet or for a public-facing website, this is going to be a requirement, but you'll need to do a content source for that because if you activate continuous crawl for your entire form, prepare to pay, guys. Prepare to pay.
Before you do anything with search, I strongly recommend you understand the difference between crawl properties and managed properties. I've also recently wrote a blog post on it, so check it out, Share-gate.com/blog, and you'll have, what is the Difference Between Crawl Properties and Managed Properties?
Because whenever you create columns in your document libraries, it does not mean it's going to be available in your search results or in your search Web Parts. In fact, it won't be unless you created a side column or you created a manage metadata column. Because all of the search Web Parts, all of the search Web Parts without any exception, will only work by displaying, or filtering, or sorting on managed properties. And unless it's a site column or a manage metadata column, you'll have to create them manually.
So pop quiz, guys. If I'm planning to use a search-related Web Part to show my content, what kind of property am I using? Exactly.
So now that we've got this out of the way, let's talk about the new administration possibilities with search. One of the big pluses for me is that now I can actually manage search as a site collection administrator. I can create my own scopes that are called result sources. I can create my result types, which is me being able to change how certain types of results are being displayed. I can create query rules to change the ranking of search results, or to change how certain results will be in the position of my search results Web Part.
So essentially, let's say you say, if somebody uses the word "deck" in his search box, what he really means is PowerPoint presentation, so take all of the PowerPoints and put them at the top. That's what query rules essentially will do.
And the search schema allows you to create and manage your managed properties, as well as looking at your crawl properties that are available. This is extremely useful for a site collection administrator because before we'd have to ask the form administrator. And we'd have to wait for him to be able to do it and do a full crawl.
The other advantage is that if you want for a specific document library to run a full crawl, you can simply go as a library administrator to Library Settings, Advanced Settings, and then you can scroll down and ask the SharePoint search to re-index your document library. And what will happen is that when the search crawler will arrive on this library, it will mark it and see that it will need to do a full crawl for that library and for that site collection to make sure that it has all of the managed properties available.
A lot of information today. So as you can see, I can look at all of the managed properties straight from my site collection. So I can see my managed properties, and I can see the mapped crawl properties that are used within it. If you do not understand this piece, don't worry. Go check out the blog post. But it's very, very important that you do understand if you're planning to use search.
So as I mentioned, there's no more search scopes. They are now called result sources. They do a lot more. They even allow you to combine with federated search. And it allows you to build them with a wizard.
So if I go to a site, say my Tour site, and go to Site Settings. Go to Result Sources. And I can say that whenever people are going to search something, it's going to filter and look only through document, or only through conversations, or only through pictures, pages, wikis. But there's one missing, searching only inside sites. So I want people to use a search box, and whatever they type, all the results that are going to come are only and strictly sites in the results.
So I click on New Results Source. We'll call it Sites. It's going to be Local SharePoint. It's going to be SharePoint Search Results. The search term that the person is going to query is going to type in a search box, and then we'll launch the Query Builder. And we'll say, make sure that you only return sites at keyword test. Yes, these are only sites that are being returned in my results. OK. And save. Wow, that was difficult.
And now when people are going to be searching and they'll use one of the result sources if I make it available here at the drop down, they'll be able to filter. And whatever they type in the box here will only bring back sites. Simple as that.
All right, let's continue here. Wow, four minutes. Let's continue fast. Result Types. With Result Types, what you're able to do is say, if one of the results that comes back is an access document, use the specific template that's going to render them differently.
So even if you have a bunch of documents being returned in your Search Results web part, you can say, hey, these are invoices because content type equals invoice. Make them look very differently, and put a picture of the customer logo on the right so I know exactly who this invoice is for. And that is awesome if you take the time to build your result types. And I encourage you to do it.
The Query Rules, we talked about it. You can promote your results at the top, or you can completely create a blog for them or change the ranking of them in the search. You do have suggested queries, or query suggestions, so that as you type SharePoint is going to suggest the result for you so that you can click on it.
When you start installing SharePoint, you'll see that it will never give you good results in the suggestions because it will learn as you start using SharePoint Search a lot more. If you want you can upload a dictionary app so that day one when you start SharePoint, it will already have many suggestions so that if people type "deck" it will replace it with PowerPoint or whatever you want.
There's obviously the Content Search web part. It's a brand new web part. It is now available in Office 365, as well. So what you can do is you can build a query, like I just showed you, only return sites that equal community, and then you can choose which display template you're going to display them in.
I'm not going to do a full demo, but I'm going to show you some that I have already done. Johan, who's answering your questions right now, he actually built a slider. So he has his images in a document library, and then he can show them to you with this display template. This is the Content Search web part, for example.
Another one that I have done is the menu that is animated. So you have an animated menu that returns the list items that are in this list. And another one is a circular navigation that pops up at the bottom that shows you the same images that Johan had uploaded to his image library.
So there's tons of ways to use the Content Search Web Part, or the Search Results Web Part, with the combination of the new branding features, like display templates, to make them appear in the way that you want. Display templates are how things are rendered in SharePoint, and they are used everywhere.
This is a perfect example of a combination of display templates and the result types. The result type said these are PowerPoints so we're going to show them with the thumbnail here. What display templates will do is they will take your managed properties and make them show in any design that you want.
Don't worry, guys. I know we're closing to the end. I just have maybe five extra minutes. Otherwise, everything is recorded, so we'll make sure we send them to you if you have to leave. I do apologize. I just have tons of information to share with you.
So it will allow you to do an image library into a slider. And by the way, all of these animated menus I showed you-- the slider, the animated menu, the pop-up-- these are all available on our blog for you to download for free for your Search 2013 Web Part. So by all means, go check it out.
What this does mean, however, it means that from now on, we'll be able to create search-driven pages. That means this entire page that you're seeing is actually the result of one search. It's a display design, a display template, that says, go and search something and put the title here, the description column here, and the image or hyperlink picture column on the right. And instead of having static pages, you will have search-driven pages. I do have a recording step-by-step that shows you how to do that step by step so you can practice it on our website, as well.
In terms of branding, this is Sayid on Lost, very, very pissed because he had to use XSLT before. So we definitely want him to stop doing that. And we won't let him get too angry here.
So what's changed in SharePoint 2013? Well, SharePoint Designer no longer has the Design View. So that's going to be a problem. What can we do? Well, there is HTML5, and SharePoint does not use tables anymore in HTML. It uses regular DIVs. So that's a big plus.
But if the Design View is gone, what exactly are we going to do? The Design Manager. It's a new tool. It's not an actual tool you download or an actual tool that you have. It's a way of working with SharePoint 2013 Design. It allows you to, even with a Mac and even with a Windows computer, connect your site master page folder directly into you're connected drive.
So you can have a Z drive, a Y drive, an M drive, or whatever you want, that's going to be available on your computer so that you can easily upload your pictures, your files, your CSS, your master pages, and work with them straight from your computer. This also means that you can use things like Dreamweaver, Notepad++ if you want, to build those HTML pages, to build those display templates, as well.
And just like magic, what SharePoint can do-- and there's a link to show you step by step how to do it-- it'll convert a regular HTML page into a master page. So now when you're doing branding, you can actually build a regular HTML page, completely non-SharePoint-related, just build an HTML design, or have a company do it for you. And then you plug it into SharePoint and it'll turn into a master page.
And all you'll have to do is go into the Code Snippets gallery, ask which snippet of code you want, like the site navigation, the sign-in button, the site logo, the top navigation, the bread crumbs. It'll generate the code for you, and you paste it into your regular HTML at the location that you want it with the CSS classes that you want. Very, very useful.
Obviously, there's device channels. To be very frank with you, nobody uses them. Device channels allow you to say, for this particular device, load a different master page with different CSS. And though this is a lot easier for download sizes so that people on iPhone only download the display for iPhone and not the entire thing and then, like CSS-responsive design, readjust. Unfortunately, the device channel requires you to maintain multiple master pages for your organization. And that's a lot of work. So check it out, but in unusual cases, people are still doing responsive design or adaptive design if they really need to.
SharePoint allows you to create Design Packages. So after you've done your display templates, after you've done your master page, after you've done your page layouts, there's a magic button that will create a WSP package for you to deploy. Unfortunately, it hasn't worked amazingly every single time. It does the work, but then when you come to deactivate the WSP package, that's when things happen, where it removes columns that it's not supposed. So be careful when using the Design Package. I still recommend having somebody that knows Visual Studio that can create your solutions for you for your design for you to deploy. But it is there if you need to.
There's also Composed Looks, which is kind of like the WordPress gallery of themes. So you can create your own themes, and then people can change the colors, can change the master page, and they can change the fonts if you have made it available for that theme. You can check that out, as well.
And finally, finishing quickly with Web Content Management, there is something called the Product Catalog List, which is allowing you to connect a list of SharePoint into the navigation here and here, as well as building search-driven pages. Cross-Site Publishing-- essentially, you have your catalog in one place, it goes into the search, and then you create your publishing sites that will show you what's available in the search engine.
There's a lot and a lot to cover in SharePoint 2013, and I think you guys can see that right now. So what I'm going to do, because I really want us to talk about the migration piece-- actually we can finish quickly. There's only two slides.
So now you can do friendly URLs, as well. There are going to be managed metadata navigation, this is called. And what you can do is you can create a navigation that when you click, it'll go to a link but without the slash pages, slash all, dot aspx. And this is very important for you guys that are doing public-facing website, because for SEO, for search engine optimization, it's the best, or it's much, much, much recommended to have friendly names like this that have terms and keywords.
Workflows. Not much has changed. You get better integration with Visio to import and export. You can start another workflow now. You can call an HTTP Web Service. You can do count. Wait for an event on a list item and then continue. But you do require to install something on the server, which is Workflow Manager, to install and work with Workflow's 2013 workflows.
Migration, to finish up, guys. There's only one migration or upgrade scenario, and this is the Database-Attach upgrade. And this is from your SharePoint 2010 to SharePoint 2013 On-Premises only. That is the only way to do it. You take your database from one SharePoint. You plug it into the new SharePoint.
The benefit and the fun thing about SharePoint 2013 and what Microsoft has done very well is that when you install SharePoint 2013, it actually installs SharePoint 2010 as well on the same box. So even if you do a database-attach upgrade, it will stay in 2010 mode using the files of 2010 so that you can decommission your old SharePoint 2010 farm and continue having things run in SharePoint 2010, and just start creating new site collections in 2013 to benefit from the search engine, to benefit from the new collaboration features, the Office Web Apps, the Search Web Parts, and everything that we've seen, leaving the old in 2010 mode. And then if you want, selectively migrate the sites that you want. You can preview the upgrade in 2013. They've done a really good job.
However, if you're in 2007 or you're planning to go to Office 365, unfortunately you'll have to use third-party tools. You're lucky because we are definitely giving 10% off for Sharegate for those of you that attended today if you want to check it out. But in terms of, is it worth the switch? Let's talk about that for a few seconds.
Honestly, guys, look at what you need to do. SharePoint 2013 will do everything that SharePoint 2010 does better, as one of my friends from the community Dan Holmes has mentioned this. And I completely agree. However, it doesn't mean that because SharePoint 2013 is available that you should just upgrade to SharePoint 2013.
You have to look at what you're doing, what you plan on doing. What are the business needs? What is the requirement for you to have SharePoint? Is it for collaboration? Is it for creating an intranet? And then look at the SharePoint that you have right now. And look at the features that are in 2013. And look at the effort that migration will be, because your customs solutions that you've built in the past won't easily migrate to 2013 or to Office 365, especially on Office 365.
So you got to look at the different impacts and whether or not it's worth to migrate. You've seen all of the features, the main features, that we've mentioned here in this session. I hope it's been useful. Do I think it's worth the switch? I think that there's one way that makes it very well worth it.
The one way that I'm talking about is to do the database-attach upgrade but leaving everything in 2010 mode, or leaving your 2010 environment as is and create a SharePoint 2013 farm on the side with only the search engine. Because the SharePoint 2013 search engine allows you to index your old SharePoint 2010 farm even though it's a separate farm.
This means that people can slowly start using the SharePoint 2013 sites and the search engine to find things, even the old things that are in the 2010. And then as you continue, you create site collections in the 2013 environment, doing an easy roll out. Because between you and me, Microsoft is doing very, very fast releases now, especially with Office 365, especially with Yammer, and those are coming only for those are going to be on 2013. And it's going to be coming very, very fast.
So if you think you're going to be requiring things like Enterprise Social with Yammer, if you want to be up to date with the Office Web Apps, the previews, and the things that they've announced at the SBC, it's definitely a good idea to have this solution.
So is it worth it? I personally think so. I'm not trying to tell you to migrate. I'm telling you, look at what you need. Look at the features that are available. Does it make sense? And that's it.
Thank you very much for your time. I do apologize. I hope it was worth it to stay an extra 11 minutes. We will send this recording tomorrow for you guys. And if you have any questions, we'll stick around for another good 10 minutes. And that's it. Have an awesome day. Thank you very much.
Thank you very much for all the amazing feedback. I really appreciate it. And I enjoy that. I'm glad that it was helpful and useful, because there's so many things in 2013 that are important. And don't hesitate to go on the Sharegate.com/blog. I try to do a lot of sharing of everything that I've done to give you an idea. Let's go on it quickly here. Let me share my screen again. Show my screen. Here, let's go on the Sharegate blog website quickly.
One of them that I would recommend looking at is I have in the past-- so there's the OneDrive for Business that explains everything about OneDrive for Business. And there's a beginner series that Natasha is doing. What are sites? What are columns? What are views? Check it out. The difference between crawl properties and managed properties.
But there's one that is particularly helpful. And there's other recordings, but the one that I'm looking for-- I think it's on this page. Sorry about the wait here. And I will send it afterwards. But there's one that will show you-- there it is.
How do I learn more about different SharePoint topics? And I'll send you the link. Contact us. There's the Twitter handle, @bniaulin. Ask me. And I show you by categories all of my blog posts, all of my video recordings, all of my blog series, if it is mine, for the SharePoint basics, for the Search in SharePoint. You have videos. You have articles.
Display templates. This is where you can download them and see step by step with videos. Cross-site publishing, branding, migration. Multiple series on migration. Governance. So this is definitely a helpful blog that you can check out. Actually let me put it straight in the chat right now so that everyone can benefit from it as of this moment. Let me go in chat. There we go. Send. So you can definitely check this out. I do recommend it.
I did see a question about whether or not I'm doing a bilingual webinar. I'll check it out. We haven't done one in the past. And we've had a lot of issues we've worked around a lot here, because we are in Montreal, Quebec. You can check out-- let me put the link up again, www.laval.ca.
This is a public-facing, multilingual site that we've created with the combination of our own features that we've developed, because to be honest with you, the variations haven't changed that much between 2010 and 2013. And unfortunately, our needs have definitely grown, and our requirements for this to work well and effectively are not at the same standard that the [? version ?] feature allows it to be. So we can talk, but we definitely have some custom development there for that.
So, I see a question. How do you maintain the SharePoint 2007 look for SharePoint 2013? You can't. It's a very simple, straightforward answer, unfortunately. You can keep the look when going from 2007 to 2010 temporarily. It's the worst upgrade scenario that I've ever seen, because it actually upgrades your 2007 to 2010. Even though it shows you a preview of what it's going to look like, it already migrated your site. So if it stopped working, it stopped working.
So they've done a much better job from 2010 to 2013 because they actually installed the SharePoint 2010 binary files on the SharePoint 2013 server so that when you upgrade it stays in 2010 mode, and it actually stays in 2010 mode. But from 2007 to 2013, unfortunately there's not even an upgrade scenario. You have to either purchase a tool-- hopefully Sharegate. But if you're doing a 2007 to 2010 to 2013, there's no way. You would have to recreate the entire master page. You might as well not.
Is the recording a read only? To be honest, I do not know if the recording will be available for download, but even if it's not available, just ask and we'll definitely allow you to download the file. Usually we do allow to download, but it's going to be a very large file. But yeah, absolutely we'll make it available for download. Usually we only put it for streaming. If you want to download, just send us a little email and we'll make sure that's possible.
Best recommendation for someone just embarking on SharePoint. Start by learning the basics. Learn how to use the site. Learn how to use a list and library. Become a power user. Even if you're going to be a developer, even if you're going to be an administrator, no matter what you plan to do in the SharePoint world, start by understanding how to use the end user side.
Know what lists and libraries are, what columns are, what site columns are, what content types are. Focus on that. Go on the URL that I've mentioned. There's the section for the basics. Go through all of that, the series by my colleague Natasha. I'm training her and at the same time she's sharing everything through her blog. Go through that. Start there. And ask me questions on Twitter or on the blogs directly, and I'll try to help you. But make sure you start with the basics before you go straight to, how do I become an administrator, for example.
That's a good suggestion for the app model. I'll definitely look into if one of our developers will be able to do an app model presentation to understand the differences. They've just abolished the auto-hosted apps actually, so it's definitely a good moment to look at what's possible using and building apps for SharePoint and Office 365. So good recommendation. I'll check it out.
In terms of learning SharePoint in a contained environment, you can either go to MicrosoftOfficeDemos.com, and you can download official virtual hard drives to practice SharePoint. But otherwise, I would say just do a trial for Office 365 and just create multiple trials every time you're done learning.
All right, guys, we're running a little bit extra on time. I do apologize. It is my fault. I'm going to save all of the questions. I'll leave you time to answer to ask all of the questions that you want. We won't answer them right now. What I'm going to do is I'm going to export them. I'm going to take the time to answer them. And then we'll post them in a blog post for tomorrow or Friday. Just let me digest this a little bit, and I'll answer.
So ask all of your questions right now, and within a minute or two I'll close the session. I'll take the time to answer all of your questions as best as I can and publish them with a blog post with the recording. But you will get the recording tomorrow.
So thank you very, very much for attending. I'm glad that it's been helpful. Ask your questions in the list here and I'll answer them as fast as I can and send you the information. Thank you.