1
00:00:00,540 --> 00:00:03,540
[Autogenerated] So first off, what is SIM?

2
00:00:03,540 --> 00:00:06,230
While SIM stands for common information

3
00:00:06,230 --> 00:00:08,660
model, it is a set of standards that

4
00:00:08,660 --> 00:00:12,120
describe how information is structured and

5
00:00:12,120 --> 00:00:15,470
represented within a specific system, such

6
00:00:15,470 --> 00:00:19,450
as a Windows device. So let's go a little

7
00:00:19,450 --> 00:00:22,280
bit further. What is Sim then? We know

8
00:00:22,280 --> 00:00:24,210
it's a common information model, but what

9
00:00:24,210 --> 00:00:26,610
does? What does that mean? Well, first

10
00:00:26,610 --> 00:00:28,850
off, it was introduced into PowerShell

11
00:00:28,850 --> 00:00:31,570
version three. It's been available from

12
00:00:31,570 --> 00:00:34,080
Windows Server 2012 and Windows eight

13
00:00:34,080 --> 00:00:36,480
onwards, and really, the most important

14
00:00:36,480 --> 00:00:39,160
thing here is it's a replacement for any

15
00:00:39,160 --> 00:00:42,640
existing W. M I or Windows management

16
00:00:42,640 --> 00:00:46,360
instrumentation commands. So what does it

17
00:00:46,360 --> 00:00:47,910
look like? And how does this all tie

18
00:00:47,910 --> 00:00:49,890
together? Well, first off we have the

19
00:00:49,890 --> 00:00:52,300
Windows Management API, which obviously

20
00:00:52,300 --> 00:00:55,790
controls the windows interface itself.

21
00:00:55,790 --> 00:00:58,160
Then we have the .NET Framework that sits

22
00:00:58,160 --> 00:01:00,500
over that. Then, of course, that splits

23
00:01:00,500 --> 00:01:03,870
into two objects. We have win RM, which is

24
00:01:03,870 --> 00:01:06,250
obviously part of Sim, and then we have D

25
00:01:06,250 --> 00:01:09,730
com, which is W. M. I on Sim and then

26
00:01:09,730 --> 00:01:11,860
really our last two objects here are the

27
00:01:11,860 --> 00:01:14,880
SIM object manager and then the same

28
00:01:14,880 --> 00:01:17,530
database. I wanted to imagine the same

29
00:01:17,530 --> 00:01:20,890
database as really the listing of the

30
00:01:20,890 --> 00:01:22,700
values and the properties that you would

31
00:01:22,700 --> 00:01:25,030
want to retrieve. So, for example, a list

32
00:01:25,030 --> 00:01:27,740
of processes on the machine, for example,

33
00:01:27,740 --> 00:01:29,610
the object manager is the piece that

34
00:01:29,610 --> 00:01:32,660
interacts directly to that database by

35
00:01:32,660 --> 00:01:37,000
using whichever mechanism, whether it's to be m I or Sim.