1
00:00:02,440 --> 00:00:03,800
[Autogenerated] Now that we have seen the

2
00:00:03,800 --> 00:00:06,740
Tillery, let's go to the lab environment

3
00:00:06,740 --> 00:00:09,740
and see how we can lock and unlock

4
00:00:09,740 --> 00:00:13,550
SharePoint sites. We are now in the demo

5
00:00:13,550 --> 00:00:16,160
environment. And let me open up the

6
00:00:16,160 --> 00:00:19,950
PowerShell. I see where I have already

7
00:00:19,950 --> 00:00:23,040
locked in to SharePoint online by using

8
00:00:23,040 --> 00:00:26,250
the SharePoint online management shell. In

9
00:00:26,250 --> 00:00:29,000
this demo, we're going to play with a few

10
00:00:29,000 --> 00:00:33,070
sites that we have created and modified in

11
00:00:33,070 --> 00:00:38,240
previous demos Tim Bravo and Alfa Team.

12
00:00:38,240 --> 00:00:41,440
Let's start first of all, by changing a

13
00:00:41,440 --> 00:00:45,810
site to read only. So in order to lock a

14
00:00:45,810 --> 00:00:48,760
site to read only we will use the set.

15
00:00:48,760 --> 00:00:52,340
Spock, IT partial cmdlet specified

16
00:00:52,340 --> 00:00:55,120
identity of the site. We want to do the

17
00:00:55,120 --> 00:00:58,630
change on in this case Alphatec, Eem. And

18
00:00:58,630 --> 00:01:01,530
then we will use the lock state parameter,

19
00:01:01,530 --> 00:01:05,210
which we will set to read only. So let me

20
00:01:05,210 --> 00:01:07,940
run this. It should only take a few

21
00:01:07,940 --> 00:01:10,890
seconds. And there we do. NICs already

22
00:01:10,890 --> 00:01:15,500
done. Now, if I go to the browser and I

23
00:01:15,500 --> 00:01:19,170
refresh the Alfa team site, I should have

24
00:01:19,170 --> 00:01:22,250
a warning that says this share prints. IT

25
00:01:22,250 --> 00:01:25,370
is read only right now. So if I go to

26
00:01:25,370 --> 00:01:27,890
documents for example. You see, I do not

27
00:01:27,890 --> 00:01:31,820
have the plus, but I cannot add any

28
00:01:31,820 --> 00:01:34,850
documents. I cannot modify the page or

29
00:01:34,850 --> 00:01:39,530
anything. This site is now unread only. So

30
00:01:39,530 --> 00:01:42,120
this is the read only mode. Now, if we go

31
00:01:42,120 --> 00:01:44,760
back to the PowerShell, let me scroll down

32
00:01:44,760 --> 00:01:48,100
a bit. Let's take a look at the no access

33
00:01:48,100 --> 00:01:51,220
mode. So in this case I will run again.

34
00:01:51,220 --> 00:01:54,500
The set, Spock, IT provide identity, which

35
00:01:54,500 --> 00:01:58,250
is Team Bravo and then the lock state,

36
00:01:58,250 --> 00:02:02,130
which is no access. If I leave it like

37
00:02:02,130 --> 00:02:04,750
that right now, what will happen is that

38
00:02:04,750 --> 00:02:07,560
users will get and not founder of four or

39
00:02:07,560 --> 00:02:11,230
three forbidden error. But in order to

40
00:02:11,230 --> 00:02:14,080
make this more user friendly, I have

41
00:02:14,080 --> 00:02:17,630
actually created a page on the Internet

42
00:02:17,630 --> 00:02:20,660
that says the site you attempted to visit

43
00:02:20,660 --> 00:02:23,450
has been locked and then a bit of

44
00:02:23,450 --> 00:02:26,700
information on what users should do if

45
00:02:26,700 --> 00:02:30,930
they need to get access to the site. And I

46
00:02:30,930 --> 00:02:34,800
can use the set Spoto tenant and provide

47
00:02:34,800 --> 00:02:37,510
that you are well in the no access

48
00:02:37,510 --> 00:02:41,240
redirect. You are well, so if any user

49
00:02:41,240 --> 00:02:44,900
goes on a site that is in the no access

50
00:02:44,900 --> 00:02:48,010
log state, they will be automatically

51
00:02:48,010 --> 00:02:51,860
read, directed to that specific page part

52
00:02:51,860 --> 00:02:55,770
of the internet so looks run that it's

53
00:02:55,770 --> 00:02:59,380
already done. However, it might take a few

54
00:02:59,380 --> 00:03:02,520
seconds until we see the experience in the

55
00:03:02,520 --> 00:03:05,370
actual browser. So let's try to do a

56
00:03:05,370 --> 00:03:08,770
refresh here. Great. It actually worked

57
00:03:08,770 --> 00:03:11,850
right away. You can see that I was not

58
00:03:11,850 --> 00:03:15,740
able to refresh the Dream Bravo site, but

59
00:03:15,740 --> 00:03:18,900
it has actually read directed me to the

60
00:03:18,900 --> 00:03:21,880
page that we specified in the tenant

61
00:03:21,880 --> 00:03:25,630
properties. So now any user that goes

62
00:03:25,630 --> 00:03:28,460
there, either by a bookmark a link from an

63
00:03:28,460 --> 00:03:32,140
old email they will get some information

64
00:03:32,140 --> 00:03:34,560
that the site is still there. But it's

65
00:03:34,560 --> 00:03:37,390
locked and a way for them to contact

66
00:03:37,390 --> 00:03:41,390
somebody in order to get it unlocked. Now,

67
00:03:41,390 --> 00:03:44,030
the last thing I want to show you is how

68
00:03:44,030 --> 00:03:47,880
do we unlock Sykes? Procedure is very

69
00:03:47,880 --> 00:03:52,500
similar. Set, Spock IT give it identity

70
00:03:52,500 --> 00:03:56,240
and the lock state should be unlock. So if

71
00:03:56,240 --> 00:04:00,450
I run this now under Alfa team site, if I

72
00:04:00,450 --> 00:04:03,860
go back here, click on refresh. My warning

73
00:04:03,860 --> 00:04:06,910
should be gone. And now I am able to

74
00:04:06,910 --> 00:04:09,480
actually create things, and again it might

75
00:04:09,480 --> 00:04:12,060
take a few minutes before the user

76
00:04:12,060 --> 00:04:14,570
interface experience is completely

77
00:04:14,570 --> 00:04:18,540
refreshed or a few refreshes if you do it

78
00:04:18,540 --> 00:04:21,140
right away. But as you can see now, I have

79
00:04:21,140 --> 00:04:24,230
my new button and I'm ready to collaborate

80
00:04:24,230 --> 00:04:28,100
in this site again. This is it for this

81
00:04:28,100 --> 00:04:30,970
demo in which we have seen how to set a

82
00:04:30,970 --> 00:04:34,950
site to read only to no access. How to

83
00:04:34,950 --> 00:04:37,870
redirect all of the request to a locked

84
00:04:37,870 --> 00:04:40,900
site in no access mode to a nice page in

85
00:04:40,900 --> 00:04:44,380
the internet that tells people what to do.

86
00:04:44,380 --> 00:04:48,600
And finally, how to unlock sites. This is

87
00:04:48,600 --> 00:04:58,000
it for this demo, and now let's go back in the slides and finish off this module.

