Work Smarter with SharePoint

On-Demand Webinar

Work Smarter with SharePoint

IBM i, Windows, UNIX, Linux, AIX, Mac OSX

 

Many businesses have implemented SharePoint for simple document sharing, but they haven’t maximized its usage to automate their daily processes. If working smarter with SharePoint is your goal, we can help.

Learn how to:

  • Optimize your SharePoint usage for the year ahead
  • Integrate SharePoint with other business-critical applications
  • Plan for the new features and functionality of SharePoint 2016

With our insider tips and first-hand knowledge of Microsoft’s plans for SharePoint 2016, you’ll be well-equipped to transform the way your business collaborates using SharePoint.

 

Richard: All right. Good morning, everyone. Welcome to our live webinar. Today is Thursday, July 30th, and it's another sunny day here in Minnesota, hopefully balmy and mid-80s. My name is Richard Schoen, and I'll be the moderator for our webinar today, entitled Working Smarter with SharePoint, brought to you by HelpSystems and our friends at Avtex.

This webinar will provide some insight into potential features coming up with new SharePoint 2016 version, and we'll also provide some insight into how HelpSystems software can ease your SharePoint operations and help integrate SharePoint with your Windows, Linux, Unix, and IBMI programs and data to maximize productivity. We're excited to have you here, so let's get started.

Here's an over... Oops, next slide, I guess. Got to change slides. There we go. All right, here's the quick overview of today's agenda. First, we'll be providing a quick introduction to your hosts, Don and myself. Next, we'll cover some of the more important 2016 highlights from Microsoft Ignite in Chicago in May, I believe, is when you were there, Don. And Don will also update us on the planned availability dates for the SharePoint 2016 preview version.

Then we'll provide an overview of several ways in which HelpSystems can help you work smarter with SharePoint by automating many of your key SharePoint operations. And lastly, we'll have a short Q&A session. We'll have a little set of polling questions as well. During the webinar, feel free to enter your questions in the chat window or the Q&A window as we go, and we'll address those towards the end of the sessions. If you do it in the chat window, just select all presenters so the questions are directed to both me and Don.

We'll plan to complete our session in about 60 minutes today, but we might spill over a few minutes, since Don and I have a lot of information to share, and we want to make sure we have enough time to address a few questions as well. The webinar is also being recorded, so if you don't have the time or a chance to stay until the end, or if you want to share it with others in your organization, you'll receive a link after the event.

All right. As I mentioned, I'm Richard Schoen. I'm the Director of Document Management here at HelpSystems. My specialty is working with customers to go paperless and streamline their document and other automation processes. I typically work with the sales team and customers to make sure our solutions are a good fit for their needs.

I've been involved in document management since the mid-1990s, and integrating to SharePoint since the 2007 version. So I have a bit of background with SharePoint. I'm also familiar with many of the HelpSystems operations automation products and how they can work together as well, so I can help customers connect the dots between all of our products.

Good morning, Don. Thanks for joining us from sunny Edina, Minnesota. Why don't you tell us a little bit about yourself and your role at Avtex?

Don: Yeah, I've been with Avtex now for almost five years, and during this time, I've been on the consulting team. Right now, I happen to be a senior consultant on the SharePoint team. I also did a stint on the sales side from a pre-sales technical side, so I did a lot of clients and still do a lot of client conversations. But now, I'm doing a lot of that, as well as the implementation at the client level. It doesn't matter what the SharePoint is, we do a lot of work across the board, 2007 all the way through 2013, as well as SharePoint Online, that we also have to include in that.

So that's really my job that I do. So I do a lot of BA work as well as the implementation work on the SharePoint side, as well as other associated applications. And that's one of the things I want to make sure that people understand, it's not just about SharePoint, but it's all of the things that also connect into that as well. That's my background and my position right now.

Richard: Yeah, yeah. And a lot of time, there are people that are using SharePoint to frontend a lot of those other applications that they build as well, too. Good point.

Don: Absolutely.

Richard: Yup. All right, so just a little question and a commentary on how we see people using SharePoint today. What I'm typically seeing is most companies are using SharePoint for internal websites, to post documents to document libraries, possibly to initiate workflows, and in some cases, for public websites. I've talked to many companies using it mainly for this need internally.

However, typically they're looking to expand their needs, and in a lot of cases, looking to move to Office 365 now as that comes online. Don, what's been your experience so far with customers adopting and using SharePoint, and what types of uses typically?

Don: Well, what I've been seeing, especially recently as a lot of organizations want to use it as the main communication platform, so that would be their intranet, and that publishing side of information where you have a few content owners, not many, but you have a couple, and then you have everybody consuming that information.

I also see it as a major platform organizations using from a collaborative perspective. So think about that productivity side of things, and integration with the Office products. And so I literally open up my Word application, I have my recent items, and I can go to that SharePoint site, pull that information in, and maybe I have some templates that are sitting out there. Without even having to hit SharePoint, I can use Word, Excel, PowerPoint to be able to pull those templates in.

And it's because of SharePoint being that shared area that information is going to be, that I can grab and quickly do things with it, as opposing to say, "Hey, where is it?" "Oh, it's in the file sharing, and I have to go through and look for it," those types of things. I'm seeing a lot of work on, not only on premise, but we're seeing a lot of people moving, as Richard was saying, to the online version of SharePoint, and then all the other products that are a part of the Office 365 suite.

Richard: Awesome. All right. So we had this slide, we did an event in May, and I didn't actually update this, but I know that this spec was in 2011. We talked about "Did You Know... Microsoft is adding about 20,000 new SharePoint users each day." And I think we speculated it's probably closer to 50,000 or more nowadays in 2015.

Don: Yeah, I would agree with that.

Richard: Yeah. So we're seeing a lot of SharePoint adoption. I do a lot of customer calls, and in a lot of cases, we ask them, "Are they using SharePoint?" Usually it's, "We have it," or "We're starting to use it," or "We're thinking about using it." So it's definitely part of the talk in most organizations, thinking about things that they're planning to do.

And probably 80% to I'd say almost 100% of the people I talk to are planning on using it for some sort of document management, whether they're posting documents to document libraries, or receiving an uploaded files, or versioning documents, that sort of thing, we see a lot of usage there. And then also probably 80% of the Fortune 500 seems to be using SharePoint as well. Your thought on that, Don, are those pretty accurate specs from what you've heard?

Don: Yeah, I think they're close. I think they've probably gone up since then, but I know as far as from an enterprise content management side of things, if you take a look at the Gartner Quadrants, that is the upper right-hand quadrant for ECM, it's the upper right-hand quadrant for many of the collaborative side of things, and the portals and collaboration space in general.

So you're finding that organizations, yes, a lot of the Fortune 500, but even small- and medium-sized organizations are falling back onto SharePoint. Number one because it may be a part of their agreement with Microsoft, and they just never had an opportunity to do it. Or maybe you happened to be in the government, or even nonprofit space, and there's incredible pricing for those people, incentives, to be able to get into SharePoint as that collaboration platform for your organization.

Richard: Yeah, and I even think about with Office 365, when people want to do departmental things, too, sometimes they can deploy a site without necessarily having to bring IT into the mix. They can set it up as an expense item, and very quickly roll the site live. Although IT usually gets involved a little bit, it's nice to be able to be able to deploy stuff quickly in the cloud.

Don: Well, and I think you hit on a point, is that's really what the bread and butter of what SharePoint is about. In the past, when organizations have done intranet, it's a homegrown intranet. It may be PHP, It may be homegrown HTML, but the fact is that IT would have to go and update that. And a lot of times, the business side of the organization were saying, "Yeah, it takes forever to get that updated."

Whereas now, on the SharePoint platform, configured correctly, it allows you to be able to then post it or put it in one location and display it in all the places that you need to, whether it be a news article, or if it needs to be just a Word document. I can naturally just upload that document without having to go to IT to be able to upload the document, create the link, and then publish that out.

Richard: Yup, absolutely. All right. So quick introduction to HelpSystems. HelpSystems has been around since 1982 as an AS/400 operations automation company, started out with our Robot job scheduling and operations automation products. Since then, the company has grown via organic product enhancements and acquisitions. You can see a few of our brands on the slide there.

Our product coverage now span the Windows, Linux, AIX, and IBMI, and other business computing platforms to provide a full suite of automation solutions for system and network management, including job scheduling, business process automation, and network monitoring. Also, we have business intelligence and reporting offerings. Systems security and compliance is big in environments - especially the environments with SharePoint, or any system that's being exposed to the outside world - and then also document management as well for managing paperless process.

This slide shows a visual timeline of our growth over the past 32 years. Our most recent acquisition was SkyView Partners in June of this year, which will help us to continue to expand our security offerings as systems security continues to be one of the biggest priorities in many organizations.

This is a brief but impressive list of some of our customers who use HelpSystems products. We're in over 350 of the Forbes Global 2,000, and we have over 9,000 total customers worldwide today. I think that's grown actually even more. This slide is a little bit dated. So a lot of various customers helping drive our product growth, and we're also very focused on customer support, and making sure people get the most usage of our products.

All right, enough of the commercial introduction. Now, we're going to let Don take over and enlighten us on what he knows about SharePoint, and what's up and coming.

Don: Perfect. Thanks, Richard. Yeah, so I'll go ahead and get to the next slide. So I happened to go along with some of my colleagues to the Microsoft Ignite conference in May. And specifically, at that point, it was more theoretical than anything else. So SharePoint 2016 is what they're calling the next version of it. At the time, there was no technical preview. Now, they're saying August of this year, there will be a technical preview available for organizations to start playing with.

The only way that anybody has access to the bits at this point for 2016 is through different partner programs, one of them being a technical advisory program, or a TAP program. There's another one that's also available for some organizations, but those are mainly around partners of Microsoft being able to have access to that. A lot of it is based off of the 2013 platform. So go ahead and next one.

Again, the other thing, too, I want to mention is the fact that these things that I will be quickly talking about today may change because of feedback through those types of programs. And as we know with Microsoft recently, they do a lot of feedback, in general, when they're starting to go into preview.

As we saw with the Windows 10, if you did the technical preview side of things, there was a lot of changes that happened between things, based off of what people were requesting, different things that they saw. So it's a possibility that this is now the new Microsoft, and how they're approaching the preview program. So we'll see. Things may change as we move forward.

But I actually was in three different sessions at Ignite, and this was down in Chicago in May. They're a large conference, specifically across all the different platforms, from an IT pro perspective, from a Microsoft side of things. And we were at three different sessions that were actually talking about the 2016 platform.

One of them was with Bill Baer, who is the actual owner of the SharePoint platform from Microsoft, so very well-known on the SharePoint side, in the community as well as in general about what's happening. He really understands, and he's really one of those people that you can go actually just have a general conversation with. Very knowledgeable. So his session really hit the bullet points of what we're talking about here.

So the first thing is that everything that we're talking about from a 2016 platform actually started from SharePoint Online. If you're not familiar with SharePoint Online, it's part of the Office 365 suite. And they literally said, "At this point, we're going to take the code base from SharePoint Online, and we're going to branch that."

And so they started taking a look at the different feature sets that were in there, and if they could be duplicated on-prem, they were going to duplicate that on-prem. However, if there were some feature sets that could not be duplicated, specifically some of the things we're going to talk about from the NextGen Portal side of things, then they would stay in the cloud, and they would hybrid that.

And that's, I think, the biggest thing that you're going to find is that is going to make it a lot easier, the 2016 platform, for you to be able to connect to online services. And there's going to be rationale for you to do that just because of what they're doing on the high end, the search side of things, and the video portal, as well as some of the things that are coming down the pipeline. So that's the biggest thing from the code base side of things. Go ahead.

As far as your resources on how we're doing things, there are some changes. Part of it is just the fact that the server base is changing. Back in 2010, SharePoint, if you were doing an on-premise type situation, you were concentrating on 2008 servers, 2008 R2, maybe some of you guys started having server 2012. So literally what they do is they go back one version of the OS plus the current version of the OS, and it's supported at that point. So now, we can't do this on a 2003 server is really what it is, especially since that's end of life, as we speak.

So hardware requirements are very similar to the 2013 platform - single server, multiple servers. Still you have your 12 to 24, or 12 to 16, 16 to 24 gigs of RAM, 64 bit processor, that's not going to change, and a minimum of four processors, 80 gigs of space. Other things again - server 2012 R2, and then Windows server 10 comes out - then that'll be available. Your database servers - SQL server 2014 SP1 and SQL 20 - whatever they come up with and when that happens.

The one thing that it will not be supported at all was, in the previous versions, you had this ability to be able to just install SharePoint on a server, period, and let it do its bidding or do its own thing, and it would install SQL Express. That's not going to happen anymore.

Additionally, you're not going to be able to do a standalone server anymore, so you can't just install SQL on that box and then SharePoint on top of it. It won't let you do that at this point again. That may change, but realistically, you'd have to have a minimum of two servers if you have a small environment. And yes, those servers can be virtualized, so that's not a major issue from there.

Richard: Yeah. And one of the notes on SQL Express, I know I've done a lot of test versions with that, too, and you ultimately end up going beyond the 10-gig boundary just because there's a lot of data capturing in that database. So that's probably a smart move for them to move that along.

Don: Yeah, absolutely. The other thing about the migration path way early on when 2016 was talked about, they did say that, "Yeah, we'll be able to bring you from 2010 to 2016 without any problems." Well, now that has changed, as we expected. You do need to upgrade from 2010 to 2013, and then 2013 to 2016, if you're doing the content database migration side of things.

The other thing, too, is there are no changes in the service applications. The service applications are going to be very similar from a 2013 perspective. That's not a major issue. So you have the option of using tools, as always, to be able to do those types of things.

They are, especially from a SharePoint on-prem to an online, if you're doing a Hybrid, and you want to have some of your content on SharePoint on-prem and some of it online, they have new APIs that have been released, and those APIs are actually utilizing, in the back end, Azure Services to be able to actually cache that information up in Azure in the meantime, and then be able to actually take that and then move it in. Migration is probably going to be cut in half, just because of those types of integrations with the Azure Services.

Other things, if there is, like I mentioned before, if there's not a service in SharePoint Online, they're going to port that service over into SharePoint 2016. For example, what they did talk about is still supporting PerformancePoint services, which a lot of organizations are using for a BI dashboard component. They will still be available within 2016, but if it's something that's online or available online, that they would make sure that that Hybrid scenario's available. Okay?

And then, again, this is what I was talking about before with the new migration API. My fault - five times faster, not just twice. So there's a lot of those happening. There's already four vendors, at Ignite, there were four vendors that came out and said, "We're already working on this. So when 2016 is available, we've already got the APIs. We've got access to it, and we're already starting to do our own betas of our software to be able to actually take advantage of this new API from a migration perspective."

And this is primarily going from on-prem to SharePoint Online, which is a big to-do. It's a big thing going on, and there's a lot of money. Just the fact that you have to sit there and wait for a lot of that to happen, it does take a lot of time and energy.

We're just doing that with one of our clients right now. And I'm trying to remember, I think we had somewhere in the neighborhood of 5 to 10 gigabytes of content, and the structure of it was interesting. But it literally took about 14 hours to migrate that up, just because of the structure that they had the information in. But it takes a long time to be able to do that from an on-prem to an online scenario. All right?

Some of the other things, and I think there might be another image on that slide... There we go. So the other thing that they're doing is that from a performance and reliability side of things, they're now having these things called roles, or MinRoles.

Now, within SharePoint 2013, we really did not have a definition of a role. We would say by the server name or whatever we want to designate that, and by turning on and flipping on services, that this is a web frontend, versus this is an app server. And then we may say, well, this server, which is an app server, deals with our search. And so it's a search server, specifically. But there is no designation within SharePoint that says that.

In 2016, they're actually coming up with these pre-defined roles around user services, around Robot services, as well as caching, that then allow us to be able to say, okay, this does this. And it minimizes that footprint of SharePoint on that particular box, if need be. So your options, and they literally have in the configuration wizard at this point, again, this is where we don't know what they're going to do with this, is they have a specialized load, and that special load would be like how we did 2013.

So we then could say, okay, these services go here, these services go there, so it's customized at that point. Otherwise, we can go in and say this is the application server, or this is the distributed cache, or this is the frontend server, this is the search server. And by doing that, it's actually allowing you to be able to better use, and those services that are on there, minimize the service footprint, and so that you can be able to have a much better performing and more reliable system overall. Go ahead and flip on to the next one.

So based off of that, then you have the Health Analyzer. And one of the nice things about the Health Analyzer is this is based off of your MinRoles that you have already setup on this. So what it will do is if I said that I want to have an application server and that's the MinRole that I did for that particular server, then it allows me to be able to check against those health rules for that particular role that we have set up.

Additionally, if it seems to be out of compliance with what those parameters were for that particular role, it will actually bring it back into compliance, utilizing scripts to be able to get that back to what it was supposed to be. So then your system is clean, it works efficiently, and we don't have any other issues with that.

What we don't know is if the Health Analyzer will work in the specialized load. At this point, we're hearing that it's supposed to be specifically around the MinRoles, but we don't know if that's being expanded outside of that, to be able to accommodate the specialized load feature when you're actually doing the install and configure for SharePoint 2016.

So we're not sure where that is at right now. There's some hubbub out on the interwebs about that right now. Bill Baer's actually been weighing in on this, and at this point, they're not changing, but we'll see. That may change in the future.

All right. So then the other thing that's been a major nightmare for SharePoint in general was the whole patching side of things. I'll focus on 2013 first for a couple of minutes here. In 2013, we had a lot of cumulative updates that came out, and a lot of those cumulative updates, and we would have up to 37 different MSI packages in there, and then if you had different languages, then you'd have additional MSIs for those languages.

And the biggest thing about that is, is that if I were to update, maybe throw a CU on a particular server, I literally had to bring that server down. I couldn't do anything else with that particular server. It had to be off hours when I was doing the patching. It was very difficult to do it. Sometimes it would take hours, depending upon how much I have to actually update that particular server to get it up to date, and with all the security components that need to be a part of that. Okay? So that's an issue.

Right now, again, not sure 100%, but what they're doing is they're going to reduce the footprint of these. So we're talking about maybe two MSIs, as opposed to 37 MSIs. Additionally, they are claiming at this point that it will be zero downtime patching. So literally, you would be able to do it during the day, not off hours.

And what they're trying to do is they're just trying to cut it down, by that, 37 to 2, you're not having as many things that are going to get hit. You're not going to have to restart IIS basically or reset that, and literally then maybe reboot the computer, or maybe use the reconfiguration wizard after you get done with that. That's not going to happen anymore.

And realistically, they're doing that right now. SharePoint Online is already utilizing these types of things. We don't see downtime patching happening and preventing our service from running. That's part of the SLA, that they have, I think it was the four nines - the 99.99% uptime associated to SharePoint Online. So keep that in mind is that it's literally going to be no patching or no downtime with your patching.

However, the thing that we don't know yet if that's specific to the MinRole, and if we have specialized loads, what's going to be the difference. Are we going to see the zero downtime patching if we use specialized load? That we don't know yet. And so again, that's something that we're waiting for as we come down to August, as well as a countdown to next year. At this point, they are saying second quarter next year, but we'll see. That may change. All right, Richard.

Richard: Thank you, Don. I have a question for you, just in terms of that whole MinRole thing. Do you see most of your customers that are using SharePoint, are they using it on virtual machines so that they can do snapshots and then do patches and rollback and that sort of thing, rather than putting it on the bare metal nowadays?

Don: Oh, absolutely. I think that's the majority of our customers are doing that. I mean to say, that's not even just SharePoint, but that's even SQL for that matter. A lot of organizations are going to that. And we know that SQL can be virtualized. It doesn't have the same performance hit as it used to, and that a lot of organizations did that as the bare metal. Now, I think that we're fine from a virtualization perspective. And you can actually use those features to be able to bring it back up, and use your snapshots, and restore it from that perspective.

Richard: Cool. Nice.

Don: Yeah. The other thing, too, is that Microsoft is really changing the software limits and the boundaries that were in the SharePoint platforms in the previous. And it just makes sense to do it, just because the fact that file sizes have gotten very large, but SharePoint hasn't literally followed along. So other things like content databases, we do suggest, it can take up to 300 GB, but we suggest 200 gigabytes. Now, it's going to be able to support terabytes of data in your particular content databases, and it will support that without any problems. And migration shouldn't be as much of an issue as we had in the past.

The other thing, too, site collections per content database. Now, it allows us to go up to 100,000, which I believe, and that's going to be for larger organizations anyway, but I believe it was 10,000 limited at that point.

List threshold, this has been a bane in a lot organizations' existence with SharePoint. It will be, and they didn't say anything as far as an upper limit, but it will be over 5,000, which is the default limit in there, and then causes performance issues after that. They're saying that 2016, we're not going to have those performance issues, and they're going to not have that 5,000 limit, it's going to be higher than that.

The other thing is they're going from 2 gigabytes file size to 10 gigabytes file size. And this is one thing that, just as a consultant, that we talk about with companies is that, yeah, they have a lot of files that are going to be bigger than 2 gigs. And what are they going to do with them? Well, then they're still regulated to file shares, and how they have to deal with them, or they may have to chunk it up into smaller file sizes so that they can actually throw it into SharePoint.

The other thing is the indexed list items. You're going to have to do 5 million. Again, maybe not most organizations are dealing with this, but the larger organizations are going to have to deal with that many objects that are within their SharePoint environment. But really, search is the biggest thing now that Microsoft is putting a lot of attention into, and that's been since 2010, but now I think it's been going into high gear. And I think that a lot of organizations can take advantage of it to find what they're really literally looking for. All right, Richard. Perfect.

Other things that they're actually taking advantage of are things like BITS, so background intelligence transfer protocol. So basically what it does is it takes a look at the files that you have locally, and then the files that are up in SharePoint, and now it uses this protocol to be able to say what the difference is, and be able to transfer the difference. So your network load balance is going to be less because it's not taking that whole entire document and updating it into SharePoint environment.

The other thing, what they're doing is they're adding more from a fast site creation side of things, and we're already seeing this in SharePoint Online, where they have a master copy of a site collection already in place. And before, they literally had to take each of the individual components as they were creating it.

It would take a fair amount of time in SharePoint on-prem to be able to actually create a site collection; this is going to be a lot easier. Plus the fact that that site collection template already has all the features enabled. In the past, they would take the template, throw it down, and then go in and individually set up each one of those particular features. Now, it's already done.

The other thing, too, is starting in 2010, they started adding a feature called Document ID, which is really cool, especially within the site collection. But the problem is if I have multiple site collections and I want to move a document between site collections, then the Document ID broke. Think of the Document ID as the capability that anytime I move a document within a site collection, it gets a unique ID within that site collection. So no matter where it moves, it always has that same ID, and then I can hard-code it if I want to, if I need to make it someplace else in another system, that link doesn't change, except if I go into another site collection, that's the issue.

Now, they're doing something called a Durable link, so that it does not matter what site collection you happen to be in, it's always going to get that ID, no matter where it's at within the SharePoint farm. So it's a really, really nice little feature that will help out with the nightmare of moving content sometimes.

Richard: Well, I think especially in the web today, I still access things back from the '90s periodically and they're still linked out there. So I think having a permalink that doesn't change is huge if people are going to publish articles that are going to live on the web for long periods of time, or they want to bookmark things.

Don: Agreed. And I've seen this with other systems that you maybe need to have a link of a document that's in a third party or another system outside of SharePoint, that you have that link. Well, now that changes, and now not only in SharePoint you have to change it, but also over here in that document or that other application you have to change. Now, this is durable. No matter what, it's always going to be there.

Richard: Yeah, I can't count the number of blog posts I've done where my links are old, and they're 2005, 2006, and they're gone because the sites are gone.

Don: Yeah. Exactly. The other thing, too, is they're making some changes in user profile service. So this has been going back and forth since 2007. In 2007, we had the capability of doing directly to AD and just do a one-way direction import and get that information up and running.

In 2010, they got rid of that and started going more of the Forefront Identity Manager, or FIM. In 2013, they brought back that feature from 2007 and 2010, or should I say, and the Forefront Identity Manager. What they're doing now is they're forking that where you now have that 2007 feature out of the box with SharePoint.

Think of it as just one way, you just get your information from Active Directory into 2016. Then, if you want to use FIM, so the Forefront Identity Manager sync capability, then you have to stand up a FIM server to be able to use that. And that way, you can use that bi-directional.

Like, say for instance, you have user profiles that have extra fields in them that you want your end users to be able to fill out, and then it pushes to AD. Then you can do that. Or in general, some of the information you want, they want to be able to update it from the user profile, they push that to AD. That's where you would have to use the Forefront Identity Manager to be able to do that.

But it is going to be a separate server that does that, or you may have a FIM farm specifically for those types of things. So they're putting a lot more of their resources, especially on the user profile services in the Forefront Identity Manager component. Big change on that.

 

All right, the other thing, too, and I apologize for this screenshot, this was literally, they don't have any documentation on this, but this is actually a screenshot of what they're doing, and they have, they being Microsoft, internal IT has for monitoring their current SharePoint online environment.

 

And so what they're going to be doing is giving a lot more analytics from the backend perspective around the services, about actions that are happening inside there - usage, engagement, information about how people are engaging within the platform, as well as diagnostic stuff. But in general, we are going to see a lot more of that admin features.

 

Again, don't know yet until we actually see that from the preview side of things, so I'll be very interested in what we get from that. But I know there are a lot of organizations that literally threw their hands up in disgust when 2013 came around, and there was hardly anything from a real-time telemetry side of things that we have any issues with. So right now, I'm hoping that this will really bring that out for them to be able to do more with.

 

All right. Then search. Search is a huge thing. Organizations that have been able to actually utilize search within the SharePoint 2010 or even 2013 have found that it's so much better than previous versions. Part of that is the fact that back in 2010, Microsoft bought a high-end search application called FAST Search, and in 2013, they integrated it fully into the search platform.

A lot of times now though, it's all about performance at this point, especially for some organizations. So one of the things Microsoft is making available, and this is the first thing from a Hybrid side of things that you can do, is you can actually offload your search to Online SharePoint, if you choose to do so.

So Microsoft has put a lot of energy into that online search side of things, specifically, if you've heard something called Office Graph and then the application that rides on top of that called Delve. Office Graph is really that search backend, and that's a next-generation component from that FAST Search purchase way back in 2010. So really, this is going to be helping overall with that.

Now, they're not necessarily going to allow you to be able to have Office Graph on-prem, so that's where you make that connection online. They also said that this ability to be able to utilize online search for your on-prem content will be also available to 2013 clients as well. So if you want to literally take your search and move it on there, that's literally allowing you to be able to index it, and then from there, you'd be able to search against that from an online perspective, so you'll have that Hybrid search at this point.

But the biggest thing is it doesn't matter where it's at. It doesn't matter if the content's online or on-prem, they're going to allow you to be able to search either side. And so you'll have one search capability across all of it. So if I'm on on-prem, and I want to be able to have my search look at my online, they'll allow you to do that. If I'm online and I want to be able to see search information from on-prem, you can do that too. Which right now, we can't necessarily do that both directions; we can only do it one direction.

The other thing that's going to be nice, and I've done a little bit of work on the eDiscovery side from the SharePoint side, so SharePoint one drive, those types of things. If you've not worked with the eDiscovery site, the electronic discovery site, this is a really cool little feature. But right now, you can only have an eDiscovery site on-prem, and it won't look online, and then vice versa.

Now, the other thing is the integration into Exchange, and that's part of that whole thing that you want to have from an eDiscovery side of things. So it's hard to be able to do an Exchange online from an on-prem situation. So the proper way of doing it right now is you need to have an eDiscovery on-prem and an eDiscovery online.

So part of the next version is, they're actually starting to roll this out online right now, is the Compliance Center. And what they're trying to do is they're including not only the eDiscovery, but all those other features like data loss prevention and some of those things, into one area. Well, DLP, your data loss prevention, is going to be available on-premise in Exchange 2016, as well as, I believe it's actually in Exchange 2013 right now, but also in SharePoint 2016.

And so now, you could have a Compliance Center on-prem that will encompass both on-prem and online. Same thing for online - it will allow you to be able to do both. So again, it's that one location, one place, one Compliance Center, to be able to go against everything.

All right. As I mentioned, the biggest thing is about Hybrid, and I've said that a few times during this session. It's about me, if I'm in SharePoint - and especially in 2013, we started seeing features like following sites and people and documents - being able to have that now go across both environments. Right now, I can only do it on-prem or I can do it online. That's it. I can't do across both. Being able to be able to follow a site online and being able to see it when I'm on-premise is going to be huge, especially for user adoption.

Managed metadata service is a feature that's been around for a couple different iterations of SharePoint. It's this corporate taxonomy, or tagging capability. Again, online only or on-premise only. Now we're going to be able to share that across, so that's not just going to be two different set prints, it's going to be one. Things like promoted sites, I can promote a site within the online, and it shows up when I go into the sites area. Now I can do online and I can do on-prem without any problems.

As well as the whole self-service site creation side of things. Some organizations use this as basically, you go in, you request the site, and it automatically provisions it for you. Well, now it's connected, so if I'm on-prem, I can have my self-site creation side of things here, but it's going to create it for me online. It doesn't matter anymore. To the end user, it's seamless, and that's what they want to try to do.

Additionally, to be able to have all this happen, they are going to start doing what they have done with Exchange since 2010, is they're going to start doing configuration wizards. And literally, it will run the PowerShell scripts behind the scenes. If I'll say I want this, boom, boom, boom, boom, boom, and then it will do it for me without having to do those configurations. Plus on top of that, it'll give me the script if I want to do that myself later on if I'm into that PowerShell thing. So some nice features from that perspective.

The other thing I want to mention is not a 2016 component yet, but these are some of the things that I've been hinting at, that you have that Hybrid scenario, but you may not have that Office Graph side of things, or Delve side of things - availability on-premise -but you want it and would like to use it, but it's an online service. Okay?

Well, what are the other online services that are coming up or what they have? So to just quickly mention, the Office 365 Video Portal - it is a video portal that allows you to be able to upload up to 10 gigabytes of video content into... it literally is a SharePoint site. All of these have SharePoint underpinnings to it.

So you have a SharePoint site, then you can actually create channels. It even has this capability, which is nice that it will automatically, by using as your media services, configure five or six different resolution versions of that particular video. That gives me this capability of, so if I am watching a video, and by the way, there's an app for your videos too that you can connect in, if I'm on a mobile device, and I have a really good connection, I'll get the higher resolution, and it will stream down to my device pretty easily.

But if I go into an area that doesn't have as good of reception, then it will go to a lower version resolution of that particular video automatically, without having to worry about that backend side of things. And it's doing that automatically as you upload that content. So think of it as enterprise YouTube or enterprise Vimeo, literally for your organization.

Delve is that, I was mentioning, is that way that information is being surfaced up as part of the Office Graph. Think of it as a proactive search. So you don't even know that it's out there. You didn't even know you needed it, but based off of your activities and the people that you're connected to - this is what Bob's working with, and Bob happens to be on my team - it will surface that information relevant to my permission set.

So if I don't have permissions for it, then I won't see it. But if I do have permissions in that area, if it's a collaboration area, then I can see that Bob's working on something that I actually may be interested in. So I actually equate it to Pinterest for my Office 365 content. And that could be Yammer, that could be OneDrive, that could be SharePoint Online that even could be emails that have attachments associated to it.

Infopedia is this new knowledge base system that is not rolled out yet. They're looking at it, and either at the end of this year or the beginning of next year they'll make available. But think of this as, maybe I'm a product owner, and I wanted people to understand about my products, and so it makes it easier for them to be able to put the information in there very quickly without having to worry about the configuration of it. I want to upload a photo here, and I want to put text here, and very quickly do that.

Additionally, they're also going to be coming out with where you can come up with your own custom portal based off of your needs. And they didn't talk much about that at Ignite, they concentrated on those other three components. But realistically that's the NextGen of the NextGens. Really, the next version of the NextGens that are coming up.

But the biggest thing is you have to understand that these all are happening in Office 365, and they're all utilizing SharePoint as the underpinning, but they're connecting to all those other apps. They're connecting to OneDrive for Business, they're connecting to Skype for Business, they're connecting to Outlook, and those types of things to be able to get more out of what you're doing. So, all right?

Richard: All right, yeah. And I think you mentioned this early on, but I think right now we're looking at August as our first release on the preview version. So I'm hoping to get my hands on that when it comes out. And then if any of you weren't here right at the beginning, Don and I were talking a little bit about a couple of things that have happened in the last couple of weeks that aren't necessarily SharePoint-related, but obviously Windows 10 was released yesterday. I got my key.

We were reminiscing about how back in '95, when Windows 95 came out; I went to the store and actually purchased it at midnight to get my DVD. And it's pretty uneventful. Now, you just download and, as Don said, you have to get in queue to get your copy of the software and you just download it from the Internet.

And then on the development side, Visual Studios 2015 is out too, so there's lots of cool things there for multi-platform development and just in general, the product's been enhanced a lot for mobile development and that sort of stuff as well. So obviously those are some immediate highlights. Obviously we're not covering today, but good for people to hear about that.

All right, so we're going to do a little introduction now into the HelpSystems product, and some of the ways that we can automate our SharePoint environment. Thanks, Don, for all that info on SharePoint 2016. Hopefully the group finds that useful.

So just a quick introduction to some of the SharePoint monitoring and automation software. So we offer several multi-platform offerings, including our Skybot software, which is an automated job scheduling tool, and we'll talk a little bit more about some use case scenarios.

We also have network monitoring, notification, visual network mapping with our InterMapper software. We'll talk a little bit about that and go through a couple of use cases. And then we also have document and forms management and report management with our WebDocs software, and then business process automation via our AutoMate software. So we'll walk through some specific scenarios on how you might utilize each of these particular products in your SharePoint environments.

So first, we'll talk about a little bit of Windows process automation. This is our AutoMate software. But SharePoint specifically, well, actually from a top level, it's cool because we can automate 600 different Windows processes, so there's functionality built in for several different things like reading and writing databases, and sending and receiving emails.

And then central to this discussion is the SharePoint integration, so we can read and write and sync information into SharePoint lists whether they're in the cloud or whether they're on-premise. So those are typically mini databases where you might want to capture information or send it out to your SharePoint server to be consumed.

We can also upload and download documents to SharePoint libraries, which the use case, we'll talk about in a moment, but a lot of times sending out reports or other documents, or pulling documents in from people. We can also version-control documents, trigger workflows, move folders around, trigger backups, and there's about 50 or 60 different actions that we can do against the SharePoint server with our AutoMate product.

So here's one use case that might be interesting for people. So this example is used to push order data to a SharePoint list. So this could be from a SQL server, it could be from an IBMI DB2 database or Oracle. It really doesn't matter. Because wherever your order entry system is, you might have a scenario where there's order data entered or changed in the ERP system, and then basically there might be some sort of database flag or a change date in the database or something like that, that triggers the system to push information out.

So AutoMate can be monitoring for those changes, and send them out to a SharePoint list, or grabbing a document and sending it out to a document library as well. So that order data then is updated in the SharePoint list, and then notifications can be sent out through SharePoint, or you might trigger some workflows in that environment as well. So what's nice is you can do both inbound and outbound processing in a lot of cases with SharePoint.

So an example here. You might have vendor and trading partner documents or maybe an employee portal or something like that that are stored in a centralized document library. And you might also have uploads that happen from the field, or you might need to upload documents where you send out notifications.

So being able to capture those documents, get notifications from the SharePoint server when the documents change, or when they're uploaded to the system, and being able to grab those and pull them out, maybe store them in a central filing system, they might stay in SharePoint, they might go into another ECM system, such as our WebDocs software, or something else that you might have as well. So that's a use case that can be used to be able to capture, upload the documents with AutoMate.

So like I was talking about, whether you're using database input/output, whether you're triggering off of email notifications, or other sort of network notifications, or other business scenarios, there's about 600 different ways that we can trigger off business processes that tie into SharePoint with the AutoMate software.

Here's a quick look at what a sample SharePoint list might look like that was populated from a database. This one actually happens to be from an IBMI. It's the standard customer database that we typically see out on an IBMI. So obviously IBMI, Windows, Linux - any platform can participate in sending and receiving data in and out of SharePoint. So it's a nice way, especially since a lot of our customer base is IBMI-driven, it's nice to be able to read and write databases and also send documents in and out of SharePoint.

Okay, on the job scheduling front, so we have a product called Skybot. Typically, Skybot is used to run daily business processing jobs - Oracle, SAP, JD Edwards, Infor, any of the large ERPs or homegrown software that you might have - you might want to send daily documents to SharePoint. They can generate it out of the software, maybe there's audit logs, those sorts of documents that you need to send out. So we've got event-driven scheduling, automated notifications, audits, reporting, all the good stuff that you have in scheduling interfaces.

And so in a lot of cases, I know a lot of people use SharePoint timer jobs, if they're using SharePoint, and run PowerShell scripts and things like that. So we can certainly run PowerShell scripts, but a lot of times, between Skybot and between AutoMate, a lot of those PowerShell scripts can be eliminated with all the built-in functionality in those tools for scheduling.

So an example here is scheduled file sync of system data. So they might have a SharePoint-based website hosted in-house or an Office 365, and let's say there's an e-commerce site, and you need to shoot the customer and item master over to that site, either on a daily, or an hourly, or an up-to-the-minute basis, you could use Skybot and AutoMate to actually set up a task where it watches for either database changes or runs regular data extract.

Skybot then runs the task to synchronize the data to SharePoint using AutoMate, and then that automates that whole process. It could be Office 365, as we said, or it could be an in-house SharePoint server, or another website, too. So good example of doing SharePoint data-sharing.

On the scheduled end-of-day processing, everybody typically has end-of-day processes that need to run that get scheduled on a regular basis. And a lot of that may need to integrate with SharePoint. It might just be regular jobs as well, but a lot of times, people use our Skybot software for their standard end-of-day jobs. They'll set up their nightly processing, and then they might schedule documents to be pushed over into SharePoint or delivered via email or something like that, either using WebDocs or AutoMate software as well. So the use case there is just being able to use for your daily processing the Skybot software.

On the network monitoring side, our InterMapper software is a great way… A lot of companies I talk to are either using something homegrown, or they're not using something at all, and in some cases, they're using another product, which our InterMapper software can integrate to other products as well, but the use case for SharePoint users is typically you want to know that your SQL server is running. You want to know that your SharePoint servers are available. If you're out at Office 365, you may want to know that those sites are available as well.

So being able to know that your servers are up, everything performance-wise is running in spec, maintaining your service levels if you've got SLA agreements, and getting notified of issues via email or text or SNMP, is usually important when you start doing network monitoring, rather than just guessing that the sites stay up.

So in this case, the example here is we can monitor the SharePoint servers, the SQL server, and actually get a visual map. So you can actually build visual maps of your internal network and your extranet as well, and be able to see if devices go down. So maybe you have a data center map setup that's monitoring devices, and things flash, people get notifications when something fails. And then you can also trigger tasks to restart VM, and things like that.

So let's say you noticed that one of your servers was down, and so you wanted to actually reboot it. Or you notice that, for some reason, it was pinging really slowly, or something like that, and you wanted to restart it. You could actually trigger the VM restart or another server restart as well. So that might be one use case. But monitoring all things SharePoint is pretty straightforward with InterMapper.

Also, you may want to watch traffic flow too. Find out who your high-bandwidth users are, and being able to see who's sucking up bandwidth, who's streaming data that they're not supposed to. I know in SharePoint, as they start adding the video services and things like that, that'll definitely take its toll on the networks. And although internal networks usually have high-speed access, a lot of times there's still limited bandwidth to the outside world. So being able to monitor that traffic, see how things are flowing, and find out who our bandwidth hogs are is a good way to keep our eye on our network, and keep things flowing very well.

Also, we talked about visually mapping your network. So you can draw network maps, see devices that are flashing if they go offline. You can also access via mobile devices. We use responsive web design so it's very easy to be able to access our console using a mobile device or a web browser, or a tablet, or something like that.

So being able to visually map the network, you can drill down into network segments so you're not always looking at the large picture of everything. And then being able to access all those maps from any device is a nice feature of network monitoring. Also very important in keeping our SharePoint farms in check.

On the document management side, we support the capturing of scanned documents to SharePoint, and also to our WebDocs software. Storing signed documents, we can capture electronic signatures on PDF and TIFF documents, and actually store those in SharePoint document libraries, or store them on the network, or store them in our WebDocs software. We have components that can burst and distribute reports out to SharePoint.

So an example here might be that you've got different departments that get their daily reports, or weekly or monthly reports, and you want to be able to send those to a SharePoint document library, and maybe version-control some of that information. It's one of the uses of using document management there.

Also collecting data entry into SharePoint, we have a component called WebForms that can be used to take any paper-based form, turn it into an online form, and capture data from that. Also, you might want to send those documents coming in from SharePoint to WebDocs or another ECM system for long-term storage. Sometimes SharePoint is the storage mechanism. Sometimes it's used as the collaboration vehicle, and then the documents get moved to a long-term storage mechanism after the fact.

And then you can also use custom web parts. I'll show you an example of one we did for our WebDocs software. But another way to surface data, like we were talking about using SharePoint as your one frontend, is you can create web parts to actually view documents. We have a sample that I'll show you for WebDocs, but it can be done pretty much for any application.

So this use case is, and I started doing this back in the '90s and it's still very important today, is that customers have the need to burst and deliver reports. So we can actually support bursting and delivering stuff coming out from an IBMI, or from PDF-based documents as well because not everybody uses IBMI. They might have any other system that generates PDFs, and might generate a large PDF for an invoice or for a sales report or something like that, and need to be able to slice and dice it, and send it out to various different areas.

So typically this scenario there is a report generated and placed in a folder or a print queue. The document gets bursted on a zone such as department or rep or something like that, and then we email it or store it in SharePoint or WebDocs, or maybe we fax it out. In some cases, some people still use fax machines. So that's one nice way to be able to burst and deliver a single report in various segments that people need.

We also have some components for taking invoices and statements, proofs of delivery, and being able to take, if you're using pre-printed forms today, being able to turn those into online versions, and then be able to send them out to customers electronically. And then also being able to archive them as well, if you need to keep an archive for compliance or for other historical reasons as well.

So our DeliverNow and our iForms component can be combined with SharePoint or with our WebDocs software for a document distribution system for electronic form documents. So it's a nice way to be able to create high-quality business output, and only generate paper when you need to print it. A lot of times, 90% of the documents that you generate as a company could be sent out electronically, or stored in SharePoint and let the customers login and access them as well, so another interesting use case for recreating business output.

Also scan documents. We support capturing scanned documents and storing them in SharePoint, or storing them in our WebDocs software, or simply storing them on a network if people want to do that as well. So in RJS solutions with WebDocs, we have several components for scanning or capturing by drag and dropping the files, and storing them into our document management software, or storing them into SharePoint. So it's a nice way to allow the desktop users to participate easily in capturing documents for storage and retrieval.

Also, another quick scenario here, we see this a lot. Actually, with the AutoMate software and with WebDocs, we see a lot of customers that want to do employee onboarding or offboarding in that case, as well. So being able to onboard users quickly, be able to capture all their information electronically, or maybe even have them fill out documents at home with their spouse, such as insurance information and that, and be able to sign those documents electronically, and then generate pixel-perfect versions of all the government forms, like the W-4, the I-9, that sort of stuff, and also be able to tie into Active Directory, to create them as a user, maybe create them in the business systems as well, and also be able to store those final documents for archival purposes.

In a large company, especially with a lot of turnover, with a lot of employee count, it's nice to be able to automate partitioning users, and then turning them on and turning them off, and also generating all that documentation as well. So typically, a lot of that W-4 and I-9 processing is done manually, and so being able to automate that can really help the HR department.

Okay, and on the document management side. So this is just an example of business implements an ECM system such as WebDocs, and that becomes the central repository, but there's a need to access documents within SharePoint for collaboration, or maybe just for inquiry, or they want to be able to check a document out, work on it in a SharePoint document library, and then check it back in to WebDocs. So being able to store documents, and electronic document repository access, documents via SharePoint webpart, or check them out and keep the final copies in one place.

We see a lot of times people have various systems of record, such as the network SharePoint, in some cases, Exchange mailboxes, file systems, that sort of thing. So moving into the paradigm of keeping all of our core business documents in a secure central location is becoming very popular with more and more customers. So trying to have that one system of record where all of our documents sit, and when they need to expire out of the system, and also be secured by department, have all that in one place, but be able to use that information from other systems such as SharePoint.

So here's a quick example. This is our WebDocs user interface, which happens to be a browser user interface, and this is just an example. I did a SharePoint part for tha, so basically where you can do a basic search, search for the documents, and retrieve them right outside of WebDocs. So this was done in VisualStudio.net  and you can do that very quickly, especially if you're using SharePoint 2013. And I'm sure 2016 will make it even easier, but it makes it very easy to surface data such as documents. Also, from your databases on IBMI, or on SQL server, you can easily write web parts to do inquiries into your real-time data as well. So you don't always have to be syncing data, you can use it in real-time.

Okay, so that was kind of a quick spin through some of the HelpSystems methods for automating SharePoint. So now we're going to take time for a little Q&A. So if you have the Q&A window or the chat window, I have both of them up, you can enter a few questions. I've got a couple that have come in already. Again, if you select the chat window, make sure to select all presenters.

And then I'm also going to display a short poll for the next couple minutes while we're actually doing that. So we'll give you two minutes, and if you wouldn't mind answering some of these questions I threw up a little poll on how people might be using SharePoint, and then I'll share the results with you in just a moment.

While we're waiting, I'll go through a couple of questions I have. It looks like one here that probably Don can answer, and a couple that I can take on. A couple people emailed me privately, or chatted me privately, and said, "When are we going to talk about IBMI?" Obviously you can tell that HelpSystems is an IBMI-centric company.

So we did talk about several of our scenarios already for reading and writing SharePoint lists, reading documents and putting them out into SharePoint. It could be out on the IFS, on the IBMI, it could be out of the Windows shared file systems. Also, downloading and bursting reports and sending them to SharePoint electronically.

So I think of IBMI as a database. I think of SQL server as a database nowadays. So being able to call programs and use the database, use print queue information, that sort of stuff, I look at IBMI as a full participant. And with all the HelpSystems technology we have nowadays, it's very easy to build workflows around integrating IBMI data directly into SharePoint.

You don't see a lot of that advertised, but I know within our realm, I've done paper-less for the last twenty years and worked with SharePoint since 2007. And then with our AutoMate product and some of the products from RJS, we've got some nice natural integration into SharePoint. So that's pretty nice.

The other one was, "We're moving from SharePoint to Office 365, or SharePoint internal. Can the HelpSystems software push and pull documents to lists and document libraries?" I think the question here is can I push in documents in and out of on-premise or Office 365?

I think I mentioned earlier that we really don't care what version of SharePoint that you're using. It's just that it uses a different authentication mechanism, but it's typically as long as we have a valid user ID and password, we can actually build business processes for sending information in and out of SharePoint, directly to an on-premise server from 2010 and above, and also out to SharePoint in the cloud - so through Office 365 as well. So any of those can be a full participant in that process as well.

And then I have one here for Don as well. "Is it hard to migrate from on-premise to cloud-hosted versions of SharePoint? I know you guys have been doing a little bit of that"

Don: Yeah, it is, because you need a tool. Unless you're willing to do the hand migration, and that would be you open up Windows Explorer and you literally move it from one area to the other. Lists become difficult. I've had some organizations that have used Access and Excel to be able to do the migration, but really if you have too much content to be able to migrate, then I would highly suggest a tool. I know Quest has a tool, Metalogix, ShareGate, and I think there's one more tool out there like MetaVis, I think is the other tool that you can use to be able to migrate from your on-prem to online. There's just no other way to do it. So I won't say it's easy just because of that.

Richard: Yup, that makes sense. It looks like our poll results just got done here, so I'm going to take a look at that real quick. So it looks like we had probably the top question on the question number one, which is, "What are typical uses for SharePoint?" Sharing and collaborating on documents got about a third of the site information. The website content management got about 20%. So I think that jibes with what we were thinking about at the top - 10% distributing documents, lower percentage on capturing upload and collecting information. So it's probably pretty standard from what we've seen so far.

About 22% say they're moving to Office 365, so that probably jibes with what I've been seeing in customer demos lately because is I ask that question often, and they're saying, yeah, probably in the next year or so, once we know where it's at, we'll probably be migrating into the cloud. So I think that sort of fits.

"Does your organization plan to move to SharePoint 2016?" Twenty-two percent said no, 13% yes, and we had a 67% no answer on that, so a lot of indecision on that side of the fence.

Don: Which makes sense, at this point.

Richard: Yeah, exactly. We don't even know what it is yet. Until we know, then maybe we'll have to do another one of these later in the year, once we have some more specifics on what's going on. "Do you need to automate SharePoint-related resources?" So we had 18% say yes, 16% no, and 67% no answer, because that probably jibes with our "Do we plan to move?"

And then, "Which of the following areas could most benefit your organization?" So it looks like top was document management, file management - which fits - business process management, and then job scheduling, and network monitoring came in fourth place on that one. So pretty good.

So I have another question that somebody asked, "Are we talking about SharePoint 2013 or 2016?" Well, the earlier portion, and everybody will get a replay link on this, in the earlier portion, we were talking about the potential features coming out in SharePoint 2016. What I was talking about in the back half of the scenario really applies to SharePoint 2010 all the way up to once 2016, once we know what materializes and comes out. But we were talking about some of the ways that HelpSystems can integrate into SharePoint.

So everybody will get a replay link of this. So if you want to go back and listen to any of the parts that Don covered or that I covered, you're more than welcome to do that. And that's why we record these because you can't always catch everything on the first round, especially when we have to move relatively fast.

So we do appreciate everybody joining us today. I think we're at the tail end of our questions here. If you have SharePoint automation needs and would like to learn more about any of the HelpSystems offerings around SharePoint, feel free to reach out to me, or any of the members of the HelpSystems sales team, and we can talk about your needs. If you have any SharePoint or Office 365 implementation needs, or other needs around SharePoint, make sure to reach out to Don or the sales team at Avtex, and they can help you out.

So I think that brings us to the tail end of our webinar. We only went five minutes over, that wasn't too bad. So we appreciate your attendance today, and we hope you have a great day, and enjoy the rest of your week.