WEBVTT 00:06.400 --> 00:14.770 Windass Management Instrumentation WMI and Common Information Model theme are related technologies. 00:14.980 --> 00:24.250 Both are based on industry standards defined by the Distributed Management Task Force or the MTA, which 00:24.250 --> 00:32.530 defines independent management standards that can be implemented across different platforms or vendor 00:32.530 --> 00:34.190 enterprise environments. 00:34.390 --> 00:45.430 WMI is Microsoft's implementation of the Web based enterprise management or the IBM standard, and is 00:45.430 --> 00:53.050 an early technology that is based on preliminary standards and proprietary technology. 00:53.290 --> 00:58.800 SYM is a newer technology and is based on open source platform standards. 00:58.990 --> 01:05.000 WMI has been available on Windows operating system since Windows 24. 01:05.290 --> 01:13.390 Most technologies provide a way to connect to common information repository, also known as the WMI 01:13.390 --> 01:14.310 repository. 01:14.560 --> 01:20.980 This repository holds management information that can be queried and manipulated. 01:21.250 --> 01:24.610 Windows Power Shell supports both technologies. 01:24.760 --> 01:33.160 Earlier versions of Windows Power shall support it on the WMI and Windows Power Shell of later than 01:33.160 --> 01:37.520 3.0 version two parallel sets of commands. 01:37.560 --> 01:42.850 Slatyer perform tasks by using either WMI or SIM. 01:43.120 --> 01:50.410 SIM commands provide many different colours, cross platform and cross version capabilities that support 01:50.410 --> 01:58.990 three kinds of connections connections to the local computer, which has always use decon ad hoc connections 01:58.990 --> 02:07.960 to a remote computer which oversees the Web services for management or W.S. Man protocol. 02:08.350 --> 02:16.240 This protocol is based on HTP and session based connections to remote computer, which can use either 02:16.550 --> 02:19.690 discom or double YES-MAN protocol. 02:19.990 --> 02:27.250 Dukedom connections are typically made to the Windows Management Instrumentation Service that is part 02:27.250 --> 02:30.370 of the Windows operating system with Assman. 02:30.370 --> 02:37.120 Connections are made to Windows Remote Management, or Winogrand Service, which is the same server 02:37.130 --> 02:39.760 that enables Windows Power Scheller remote. 02:39.790 --> 02:46.660 And we'll talk about remote a bit later in some other course in more detail. 02:46.870 --> 02:54.460 In the room is part of the Windows management framework and is included in Windows Management Framework 02:54.670 --> 02:57.100 Version two and newer versions. 02:57.250 --> 03:04.510 Then Arima is installed by default on computers that are running Windows seven, Windows eight and so 03:04.510 --> 03:09.430 on, although installed by default on all those operating systems. 03:09.580 --> 03:12.220 You can assume commands in two ways. 03:12.460 --> 03:18.220 The first Guerra's the remote computer to have the interim installed and enabled. 03:18.430 --> 03:25.600 That will typically require the Windows management framework version three be installed and that Windows 03:25.600 --> 03:27.670 power Scheller Motin is enabled. 03:27.880 --> 03:35.410 The second way to use same commands is to tell the command to use the earlier WMI technology. 03:35.650 --> 03:43.630 That is the same technology used by WMI commands, and it does not require that Windows management framework 03:43.900 --> 03:46.270 be installed on the remote computer. 03:46.480 --> 03:48.520 No to WMI commands. 03:48.520 --> 03:53.050 WMI commands use the same repositories, same commands. 03:53.200 --> 03:59.080 The only difference is in how the WMI commands connect to a remote computer. 03:59.320 --> 04:03.400 WMI commands do not support assertion based connections. 04:03.550 --> 04:12.430 The commands support only ad hoc connections over DECL, whether used by WMI or Assume Command. 04:12.550 --> 04:16.980 Dickon can be difficult to use on some networks. 04:17.200 --> 04:22.000 The com uses the remote procedure call or RBOC protocol. 04:22.210 --> 04:30.420 That protocol requires specific firewall exceptions to work correctly, WMI commands communicate with 04:30.420 --> 04:32.500 the WMI service. 04:32.710 --> 04:40.180 They do not require an version of Windows management framework on a remote computer and they do not 04:40.180 --> 04:47.800 require that Windows Power Scheller Motin be enabled is a remote computer, has a Windows firewall feature 04:47.800 --> 04:56.410 enabled WMI commands require that the remote administration exception be enabled on the remote computer. 04:56.650 --> 05:04.120 If the remote computer has a different local firewall enabled, an equivalent exception must be created 05:04.120 --> 05:05.830 and enabled because. 05:06.230 --> 05:15.390 Commands can also use the eCom WMI commands are typically necessary only when you have to make an ad 05:15.390 --> 05:21.300 hoc connection to a computer that does not have Windows power Scheller remote and enabled. 05:21.540 --> 05:29.340 So should you use WMI or assume most of the time you should use seem command LEDs instead of the older 05:29.370 --> 05:30.500 WMI command? 05:30.510 --> 05:31.770 Let's assume command. 05:31.770 --> 05:36.290 Let's use the Comm One Cuarón, the local computer system command. 05:36.300 --> 05:45.660 Let's use W Earthman for ad hoc connections to remote computers and same command that can use the command 05:45.930 --> 05:50.640 W Earthman for session based connections to remote computer. 05:50.970 --> 05:58.080 They are WMI commands that can be used when you must make an ad hoc connection to a computer that does 05:58.080 --> 06:05.640 not have Windows management framework version to a newer version installed or to a computer that has 06:05.640 --> 06:13.190 Windows management framework installed, but that does not have Windows power Scheller remote and enabled. 06:13.320 --> 06:20.790 However, the same command that can connect to a computer that does not have Windows management framework 06:21.000 --> 06:25.520 installed and two computers that do not have Windows power. 06:25.530 --> 06:27.120 So the remote and enabled. 06:27.360 --> 06:31.920 You must use the same session to connect to those computers. 06:32.010 --> 06:35.910 You learn about six sessions a bit later in this course. 06:36.030 --> 06:43.650 Please note Microsoft considers the WMI commands within Windows Power Shell to be deprecated. 06:43.860 --> 06:52.170 Although the underlying WMI repository is still a current technology, you should rely primarily on 06:52.170 --> 06:55.290 Simca commands and to use WMI commands. 06:55.290 --> 06:58.500 Only one SIM commands are not practical. 06:58.710 --> 07:06.270 The repository is not well documented and discover the classes that you might need to perform. 07:06.510 --> 07:10.890 A specific task can be difficult and impractical. 07:11.130 --> 07:18.450 The solution is to provide Windows Power Shell commands that behave like any other shell command, but 07:18.720 --> 07:22.230 that internally use WMI or oracy. 07:22.680 --> 07:30.840 The approach gives you the advantages of Windows power shell commands such as discoverability and in 07:30.840 --> 07:37.080 documentation, while also giving you the existing functionality of the repository. 07:37.290 --> 07:46.350 In Windows eight and Windows 2012, Microsoft introduced hundreds of new commands and Windows Paracel. 07:46.590 --> 07:51.360 Many of the commands internally use WMI or Seyoum. 07:51.630 --> 08:00.630 These commands provide better access to the functionality of WMI and SIM so that you can use the functionality 08:00.630 --> 08:04.040 without having to deal with their complexity.