1
00:00:02,710 --> 00:00:08,370
In this demo, we will see how some PS drive adds custom parameter

2
00:00:08,370 --> 00:00:12,900
based on the type of data that is being accessed in that drive.

3
00:00:12,900 --> 00:00:17,740
We'll then see how some PowerShell module or snap‑in adds an

4
00:00:17,740 --> 00:00:21,940
additional PS drive automatically.

5
00:00:21,940 --> 00:00:25,620
We earlier talked about CodeSigningCert parameter that shows

6
00:00:25,620 --> 00:00:29,740
up only while we are in cert PS drive.

7
00:00:29,740 --> 00:00:35,680
Currently, I'm in C drive, which is a file system drive. I'll now enter

8
00:00:35,680 --> 00:00:42,040
Get‑Item command and switch through available parameters.

9
00:00:42,040 --> 00:00:49,120
As I keep switching, we can see that the CodeSigningCert has still not appeared.

10
00:00:49,120 --> 00:00:55,880
I'll now change the PS drive to cert using Set‑Location command and then enter

11
00:00:55,880 --> 00:01:01,930
cert: PS drive. Now I'll again enter same command,

12
00:01:01,930 --> 00:01:07,540
Get‑Item, and switch through available parameters.

13
00:01:07,540 --> 00:01:13,540
We can now see that the CodeSigningCert parameter is now available.

14
00:01:13,540 --> 00:01:17,320
This is an example of how the set of available parameters

15
00:01:17,320 --> 00:01:20,910
for a command may get changed depending on the drive in

16
00:01:20,910 --> 00:01:24,240
which the command is being executed.

17
00:01:24,240 --> 00:01:29,230
We will now see how an additional Active Directory PS provider gets added when

18
00:01:29,230 --> 00:01:35,080
we install RSAT module for Active Directory. RSAT is the abbreviation of Remote

19
00:01:35,080 --> 00:01:38,510
Server Administration Tools. From the name itself,

20
00:01:38,510 --> 00:01:41,790
you can guess that it's a collection of tools that are used to

21
00:01:41,790 --> 00:01:47,140
administer remote computers. Installing RSAT will install required

22
00:01:47,140 --> 00:01:51,220
snap‑ins and PowerShell modules which are required to manage roles

23
00:01:51,220 --> 00:01:53,940
and features of remote computers.

24
00:01:53,940 --> 00:01:57,580
I'll quickly show you how we can install RSAT tool for Active

25
00:01:57,580 --> 00:02:02,140
Directory on Windows 10. I'll first go to Settings,

26
00:02:02,140 --> 00:02:06,640
click on Apps, go to Optional features,

27
00:02:06,640 --> 00:02:12,920
click on Add feature, and in the search box, I'll type RSAT. This will list

28
00:02:12,920 --> 00:02:18,490
RSAT tool for different server roles. For this demo, we are interested in RSAT

29
00:02:18,490 --> 00:02:24,380
tool for Active Directory. I'll select it and click on Install. The RSAT tool

30
00:02:24,380 --> 00:02:28,980
will install Active Directory PowerShell module which will enable us to connect

31
00:02:28,980 --> 00:02:30,960
to Active Directory PS drive.

32
00:02:30,960 --> 00:02:35,720
Remember that your machine needs to be a member of Active Directory domain to

33
00:02:35,720 --> 00:02:44,270
connect to ADPS drive. So we are back in our demo, and now I have installed

34
00:02:44,270 --> 00:02:50,860
RSAT tool for Active Directory on this system. First, I'll run Get‑PSProvider

35
00:02:50,860 --> 00:02:55,740
command and we can see that the default providers that were available earlier

36
00:02:55,740 --> 00:03:02,980
is displayed on the screen. Since I now have RSAT tool installed, I can

37
00:03:02,980 --> 00:03:10,020
import Active Directory module. Once I do that, I'll again run Get‑PSProvider

38
00:03:10,020 --> 00:03:16,100
command, and now we can see that Active Directory PS provider got added and

39
00:03:16,100 --> 00:03:24,170
its associated AD drive is also listed in drive's column. I'll now enter into

40
00:03:24,170 --> 00:03:32,500
AD drive using Set‑Location command and run Get‑ChildItem command. This will

41
00:03:32,500 --> 00:03:39,580
list AD partitions. I can enter any of this AD partition and get details of

42
00:03:39,580 --> 00:03:46,540
AD objects present in that partition. I'll use Set‑Location command and enter

43
00:03:46,540 --> 00:03:48,940
domain partition.

44
00:03:48,940 --> 00:03:59,000
Once I'm in, I'll run Get‑ChildItem command and the list of immediate OUs present in that domain will get listed.

