1
00:00:02,888 --> 00:00:04,754
Now that we have seen the theory, let's go

2
00:00:04,754 --> 00:00:07,075
in the lab and check out the SharePoint

3
00:00:07,075 --> 00:00:10,670
usage reports, as well as the SharePoint

4
00:00:10,670 --> 00:00:13,186
crawl log. We're now in the live

5
00:00:13,186 --> 00:00:15,833
environment so let me open up this Search

6
00:00:15,833 --> 00:00:19,133
admin center, and we'll already go to the

7
00:00:19,133 --> 00:00:21,984
View Usage Reports where we have all of

8
00:00:21,984 --> 00:00:25,088
the different reports on Search. Let's

9
00:00:25,088 --> 00:00:27,555
take a look at some of them. Let's first

10
00:00:27,555 --> 00:00:30,141
of all take a look at the top queries by

11
00:00:30,141 --> 00:00:33,592
month so we can see what were the top

12
00:00:33,592 --> 00:00:36,029
queries every month in the organization.

13
00:00:36,029 --> 00:00:38,384
It will take a few seconds, and then it

14
00:00:38,384 --> 00:00:42,115
will start the download. Let's open it up,

15
00:00:42,115 --> 00:00:45,965
and as you can see, I can go through every

16
00:00:45,965 --> 00:00:49,390
month and see what were the top queries.

17
00:00:49,390 --> 00:00:52,075
This is a dev tenant so it doesn't have a

18
00:00:52,075 --> 00:00:56,456
lot of content, but you can see inside

19
00:00:56,456 --> 00:00:59,030
August 2019, I have searched for test

20
00:00:59,030 --> 00:01:02,037
three different times, and it's most of

21
00:01:02,037 --> 00:01:05,080
the queries. I can also go and download,

22
00:01:05,080 --> 00:01:08,232
for example, the number of queries so we

23
00:01:08,232 --> 00:01:10,779
can determine how many queries to we get

24
00:01:10,779 --> 00:01:13,061
per month, and when are people searching

25
00:01:13,061 --> 00:01:16,360
for stuff? What is the high season and the

26
00:01:16,360 --> 00:01:18,775
low season when people do searches inside

27
00:01:18,775 --> 00:01:21,903
our SharePoint Online tenant? Let's open

28
00:01:21,903 --> 00:01:25,223
up and let's go to Monthly, which has a

29
00:01:25,223 --> 00:01:27,775
lot more information, and here you can

30
00:01:27,775 --> 00:01:30,710
really see how many queries I had per

31
00:01:30,710 --> 00:01:33,340
month in the last three years. So it

32
00:01:33,340 --> 00:01:35,687
really keeps a lot of information, as well

33
00:01:35,687 --> 00:01:39,166
as the daily report for this month where I

34
00:01:39,166 --> 00:01:41,642
do not have lots of information since

35
00:01:41,642 --> 00:01:45,878
again this is a pretty static dev tenant.

36
00:01:45,878 --> 00:01:49,042
Now let's talk about the crawl Log. Before

37
00:01:49,042 --> 00:01:52,800
being able to look at the crawl log, we

38
00:01:52,800 --> 00:01:56,307
need to add the permissions. So I need to

39
00:01:56,307 --> 00:01:58,884
go into Crawl Log Permissions and then we

40
00:01:58,884 --> 00:02:02,054
need to add the users that are allowed to

41
00:02:02,054 --> 00:02:04,624
access the crawl log for this tenant.

42
00:02:04,624 --> 00:02:08,029
Again, even if you're a global admin, a

43
00:02:08,029 --> 00:02:10,374
SharePoint Online admin, it doesn't

44
00:02:10,374 --> 00:02:13,084
automatically add you in here. So you need

45
00:02:13,084 --> 00:02:14,986
to make sure that you've been added and

46
00:02:14,986 --> 00:02:17,376
then you're able to use the PowerShell

47
00:02:17,376 --> 00:02:20,682
cmdlets that we have looked at in the

48
00:02:20,682 --> 00:02:24,841
slides in order to get that log. So if I

49
00:02:24,841 --> 00:02:27,745
run it now, I'm actually going to get an

50
00:02:27,745 --> 00:02:31,395
error. What normally happens is that you

51
00:02:31,395 --> 00:02:34,966
get the crawl logs; however, there is

52
00:02:34,966 --> 00:02:38,152
actually a known issue with SharePoint

53
00:02:38,152 --> 00:02:40,535
right now that has been reported. I know

54
00:02:40,535 --> 00:02:43,966
that Microsoft has fixed the error and it

55
00:02:43,966 --> 00:02:46,312
will take another month until the fix

56
00:02:46,312 --> 00:02:48,928
comes to all of the tenants worldwide so

57
00:02:48,928 --> 00:02:51,890
until October 2019, you might not be able

58
00:02:51,890 --> 00:02:55,321
to run this cmdlet, but it's unfortunately

59
00:02:55,321 --> 00:02:58,815
a known error. I've tried waiting as much

60
00:02:58,815 --> 00:03:00,955
as possible before recording this part,

61
00:03:00,955 --> 00:03:03,400
that maybe the fix would come to my

62
00:03:03,400 --> 00:03:06,589
tenant, but unfortunately it didn't. I'll

63
00:03:06,589 --> 00:03:08,789
make sure that I add that link to the

64
00:03:08,789 --> 00:03:11,497
known issue inside the exercise files so

65
00:03:11,497 --> 00:03:14,057
if you get the error as well, you can go

66
00:03:14,057 --> 00:03:18,172
and take a look if it has been resolved.

67
00:03:18,172 --> 00:03:20,279
However, this is the right cmdlet, those

68
00:03:20,279 --> 00:03:23,282
are the right filters, it's just a known

69
00:03:23,282 --> 00:03:26,642
issue why we cannot run it right now. This

70
00:03:26,642 --> 00:03:29,033
is it for this demo. We have looked at how

71
00:03:29,033 --> 00:03:31,626
to download the usage reports, as well as

72
00:03:31,626 --> 00:03:35,040
how we would try to go to the SharePoint

73
00:03:35,040 --> 00:03:37,671
crawl log. Unfortunately, the reality of

74
00:03:37,671 --> 00:03:40,809
the cloud is that sometimes some things do

75
00:03:40,809 --> 00:03:44,001
not work for a short period of time, and

76
00:03:44,001 --> 00:03:47,542
because we're only clients of that cloud

77
00:03:47,542 --> 00:03:49,804
provider, we cannot do anything as long as

78
00:03:49,804 --> 00:03:52,220
they're working on it. So I was not able

79
00:03:52,220 --> 00:03:55,308
to show you this specific cmdlet. I'm

80
00:03:55,308 --> 00:03:58,057
really sorry about it; however, it also

81
00:03:58,057 --> 00:04:01,818
teaches you a bit on where to look at and

82
00:04:01,818 --> 00:04:05,024
that sometimes things go wrong with Office

83
00:04:05,024 --> 00:04:08,928
365 and with any cloud provider, and all

84
00:04:08,928 --> 00:04:11,531
that you can do is wait for them to fix

85
00:04:11,531 --> 00:04:14,303
it, but at least you know in theory how it

86
00:04:14,303 --> 00:04:20,000
would work. Now let's go back to the slides and finish this module.

