1
00:00:00,340 --> 00:00:01,230
[Autogenerated] So what's the difference

2
00:00:01,230 --> 00:00:03,900
between using the session approach versus

3
00:00:03,900 --> 00:00:07,140
just passing the computer name? Well, if

4
00:00:07,140 --> 00:00:09,590
we use the same computer name, it creates

5
00:00:09,590 --> 00:00:12,560
a single connection to the target client

6
00:00:12,560 --> 00:00:15,990
or the server. You can start and stop the

7
00:00:15,990 --> 00:00:18,210
session automatically, so you just connect

8
00:00:18,210 --> 00:00:19,970
in, and then when you finished, it will

9
00:00:19,970 --> 00:00:22,710
disconnect. And you would usually use this

10
00:00:22,710 --> 00:00:26,260
for execute in single commands against the

11
00:00:26,260 --> 00:00:30,010
client or the server. On the flip side of

12
00:00:30,010 --> 00:00:32,800
this, If I'm using the session command,

13
00:00:32,800 --> 00:00:35,640
then I'm looking at controlling sessions,

14
00:00:35,640 --> 00:00:38,780
either temp recessions or permanent until

15
00:00:38,780 --> 00:00:41,890
I closed them down. These are normally

16
00:00:41,890 --> 00:00:43,850
used when you need to run multiple

17
00:00:43,850 --> 00:00:46,760
commands against the remote targets. So

18
00:00:46,760 --> 00:00:49,030
instead of just connect, retrieve and

19
00:00:49,030 --> 00:00:51,080
that's it. I maybe want to connect,

20
00:00:51,080 --> 00:00:53,480
retrieve, then execute, then retrieve,

21
00:00:53,480 --> 00:00:55,720
then execute, then retrieve. And then, of

22
00:00:55,720 --> 00:00:57,820
course, there is faster performance for

23
00:00:57,820 --> 00:00:59,770
execution of commands. Because you've

24
00:00:59,770 --> 00:01:01,630
opened the session, we're not having to re

25
00:01:01,630 --> 00:01:03,910
initialize a session every time we want to

26
00:01:03,910 --> 00:01:08,000
grab information or do something because the session already exists