WEBVTT

1
00:00:00.080 --> 00:00:03.759
<v Speaker 1>Welcome to the deep dive. Today, we're really getting into

2
00:00:03.759 --> 00:00:05.679
<v Speaker 1>the nuts and bolts of our digital world. You know

3
00:00:05.719 --> 00:00:08.359
<v Speaker 1>that feeling you want to understand how the tech around

4
00:00:08.359 --> 00:00:11.039
<v Speaker 1>you works, not just you know that it works. So

5
00:00:11.080 --> 00:00:13.919
<v Speaker 1>we're going on a journey today unlocking some of that

6
00:00:14.000 --> 00:00:15.560
<v Speaker 1>core IT knowledge, Yeah, the.

7
00:00:15.560 --> 00:00:18.399
<v Speaker 2>Stuff that powers everything from your phone to the Internet

8
00:00:18.399 --> 00:00:19.679
<v Speaker 2>itself exactly.

9
00:00:20.280 --> 00:00:24.399
<v Speaker 1>And our guide for this it's this amazing stack of

10
00:00:24.440 --> 00:00:29.079
<v Speaker 1>practice materials for the Comtia A plus exams Core one

11
00:00:29.120 --> 00:00:31.800
<v Speaker 1>and Core two. Think of them as like a decoder

12
00:00:31.879 --> 00:00:33.920
<v Speaker 1>ring for practical, real world IT.

13
00:00:34.200 --> 00:00:37.159
<v Speaker 2>Stuff, right, and our mission here is to pull out

14
00:00:37.200 --> 00:00:40.880
<v Speaker 2>those really crucial relevant bits. We're not just about memorizing facts.

15
00:00:40.880 --> 00:00:43.240
<v Speaker 2>It's more about getting that deeper feel for what something

16
00:00:43.359 --> 00:00:46.439
<v Speaker 2>is and maybe more importantly, why it actually matters. The

17
00:00:46.520 --> 00:00:50.640
<v Speaker 2>sources themselves really push that building real knowledge for practical use,

18
00:00:50.719 --> 00:00:53.159
<v Speaker 2>not just you know, repeating things. That's what we're aiming for.

19
00:00:53.280 --> 00:00:56.600
<v Speaker 1>Couldn't agree more so, whether you're maybe studying for an exam,

20
00:00:56.759 --> 00:00:59.039
<v Speaker 1>or you're just really curious about the hidden workings of

21
00:00:59.039 --> 00:01:02.000
<v Speaker 1>your gadgets, like how does your phone actually know where

22
00:01:02.000 --> 00:01:06.719
<v Speaker 1>you are? Or what makes Wi Fi pick or why

23
00:01:06.799 --> 00:01:10.560
<v Speaker 1>printers can be so temperamental. Sometimes this deep dive is

24
00:01:10.599 --> 00:01:13.280
<v Speaker 1>for you. We want you to walk away feeling genuinely

25
00:01:13.319 --> 00:01:17.239
<v Speaker 1>clued in understanding the tech that's well basically part of

26
00:01:17.239 --> 00:01:17.959
<v Speaker 1>our lives now.

27
00:01:18.000 --> 00:01:20.560
<v Speaker 2>And it's worth saying the expertise behind these source materials

28
00:01:20.640 --> 00:01:23.920
<v Speaker 2>is solid. Audrey, the technical editor and co author, holds

29
00:01:23.920 --> 00:01:26.400
<v Speaker 2>a bunch of Comptier asserts and others, so the foundation

30
00:01:26.519 --> 00:01:27.480
<v Speaker 2>is definitely strong.

31
00:01:27.599 --> 00:01:30.959
<v Speaker 1>Okay, let's start with something we use constantly, mobile devices.

32
00:01:31.200 --> 00:01:33.439
<v Speaker 1>How many times have you wondered how your phone just

33
00:01:33.599 --> 00:01:35.640
<v Speaker 1>knows where you are? It feels like magic, right.

34
00:01:35.599 --> 00:01:37.760
<v Speaker 2>Hah, Yeah, it does seem like it, but it's definitely

35
00:01:37.799 --> 00:01:41.120
<v Speaker 2>more than logic. When we talk location services, yeah, GPS

36
00:01:41.200 --> 00:01:44.560
<v Speaker 2>comes to mind first, Global Positioning System, and sure those

37
00:01:44.599 --> 00:01:47.799
<v Speaker 2>satellites are key. But here's the thing. Your phone hardly ever,

38
00:01:47.840 --> 00:01:51.640
<v Speaker 2>relies just on GPS. It's usually blending things. It uses

39
00:01:51.680 --> 00:01:55.599
<v Speaker 2>cellular location services to signals from cell towers nearby, and

40
00:01:55.640 --> 00:01:59.319
<v Speaker 2>even Wi Fi positioning mapping you against known networks.

41
00:02:00.159 --> 00:02:01.920
<v Speaker 1>Okay, so it's a mix exactly.

42
00:02:02.000 --> 00:02:05.319
<v Speaker 2>It makes it faster, more accurate, especially when you're indoors

43
00:02:05.439 --> 00:02:09.199
<v Speaker 2>where GPS signals can be weak. Think about like a

44
00:02:09.280 --> 00:02:12.879
<v Speaker 2>ride share app it needs to track your driver pretty precisely, right,

45
00:02:13.319 --> 00:02:15.879
<v Speaker 2>or maybe a hiking app showing you exactly where you

46
00:02:15.919 --> 00:02:18.599
<v Speaker 2>are on some trail. That accuracy it comes from these

47
00:02:18.639 --> 00:02:19.680
<v Speaker 2>systems working together.

48
00:02:20.159 --> 00:02:23.800
<v Speaker 1>That makes sense, blending technologies for a better result. Now,

49
00:02:23.840 --> 00:02:28.000
<v Speaker 1>thinking out all these devices, especially for businesses, managing them

50
00:02:28.080 --> 00:02:30.199
<v Speaker 1>must be well a headache.

51
00:02:29.840 --> 00:02:33.240
<v Speaker 2>Sometimes, oh absolutely, And that's precisely where MDM comes in

52
00:02:33.280 --> 00:02:36.680
<v Speaker 2>Mobile device management. Its main job is to centrally manage

53
00:02:36.680 --> 00:02:40.439
<v Speaker 2>and secure all the mobile devices in an organization. Super

54
00:02:40.439 --> 00:02:44.439
<v Speaker 2>important for company owned phones, but also for BYOD scenarios.

55
00:02:44.719 --> 00:02:46.960
<v Speaker 1>Bring your own DIVISCECE is getting more common.

56
00:02:46.719 --> 00:02:50.599
<v Speaker 2>Definitely, so MDM lets it push out security policies, you know,

57
00:02:50.680 --> 00:02:52.960
<v Speaker 2>make sure devices have pass codes, encryption, that sort of thing.

58
00:02:53.400 --> 00:02:55.680
<v Speaker 2>And they can remotely manage corporate apps, make sure they're

59
00:02:55.719 --> 00:02:58.360
<v Speaker 2>installed right, kept up to date. And a really critical

60
00:02:58.400 --> 00:03:01.240
<v Speaker 2>security feature is the remote wipe capability.

61
00:03:01.439 --> 00:03:04.960
<v Speaker 1>Uh yeah, if a phone gets lost or stolen.

62
00:03:04.919 --> 00:03:08.840
<v Speaker 2>Exactly, or if an employee leaves, it can just remotely

63
00:03:08.879 --> 00:03:11.879
<v Speaker 2>erase all the sensitive company data. It's all out control

64
00:03:11.919 --> 00:03:14.639
<v Speaker 2>and security, even when the device isn't physically there.

65
00:03:15.000 --> 00:03:19.360
<v Speaker 1>Okay, So moving away from the corporate side, what does

66
00:03:19.400 --> 00:03:23.080
<v Speaker 1>this mean for our everyday digital lives. How do we

67
00:03:23.159 --> 00:03:27.680
<v Speaker 1>keep our personal stuff flowing between, say, our phone and tablet.

68
00:03:27.960 --> 00:03:31.039
<v Speaker 2>Right, that's where mobile device synchronization comes in. It's basically

69
00:03:31.280 --> 00:03:36.240
<v Speaker 2>essential for keeping everything consistent. Imagine your calendar, contacts, maybe

70
00:03:36.240 --> 00:03:39.960
<v Speaker 2>some work apps, email, cloud storage. Without sync, you'd update

71
00:03:40.000 --> 00:03:41.719
<v Speaker 2>something on your phone and it wouldn't show up on

72
00:03:41.759 --> 00:03:42.360
<v Speaker 2>your laptop.

73
00:03:42.680 --> 00:03:43.919
<v Speaker 1>Chaos, total chaos.

74
00:03:44.000 --> 00:03:47.560
<v Speaker 2>Yeah, so sync is what Let's say parents share appointments easily,

75
00:03:47.680 --> 00:03:50.120
<v Speaker 2>or make sure your contact list is the same everywhere.

76
00:03:50.120 --> 00:03:53.080
<v Speaker 2>It's kind of the invisible glue holding our multi device

77
00:03:53.159 --> 00:03:55.840
<v Speaker 2>lives together makes sense. Just a quick side note, all

78
00:03:55.840 --> 00:03:58.719
<v Speaker 2>the sinking uses data obviously, so knowing your data caps

79
00:03:58.759 --> 00:04:01.400
<v Speaker 2>is sometimes useful to a void surprises.

80
00:04:00.919 --> 00:04:03.439
<v Speaker 1>On your bill. Good point. Okay, so we've talked about

81
00:04:03.479 --> 00:04:05.719
<v Speaker 1>individual devices. Let's zoom out a bit. How do they

82
00:04:05.719 --> 00:04:08.879
<v Speaker 1>actually talk to each other. Let's dig into networking.

83
00:04:08.639 --> 00:04:10.919
<v Speaker 2>Right, the digital backbone, and at the heart of it,

84
00:04:11.000 --> 00:04:15.159
<v Speaker 2>you've got these core protocols, mainly TCP Transmission Control Protocol

85
00:04:15.400 --> 00:04:18.879
<v Speaker 2>and UDP User Data Gram Protocol. Think of it like this.

86
00:04:19.800 --> 00:04:22.439
<v Speaker 2>TCP is like sending a certified letter. It sets up

87
00:04:22.439 --> 00:04:25.199
<v Speaker 2>a connection. Make sure every piece of data gets there

88
00:04:25.319 --> 00:04:26.279
<v Speaker 2>in the right order.

89
00:04:26.279 --> 00:04:29.240
<v Speaker 1>Reliable, okay, but maybe a bit slower.

90
00:04:28.959 --> 00:04:32.519
<v Speaker 2>Exactly because of all the checking and confirming. UDP, on

91
00:04:32.560 --> 00:04:34.959
<v Speaker 2>the other hand, is more like sending a postcard. You

92
00:04:35.079 --> 00:04:37.319
<v Speaker 2>just fire it off. It's faster because it doesn't bother

93
00:04:37.399 --> 00:04:40.839
<v Speaker 2>with all that confirmation stuff. Great for things like live

94
00:04:40.959 --> 00:04:43.759
<v Speaker 2>video or online gaming where a tiny dropped bit of

95
00:04:43.839 --> 00:04:46.759
<v Speaker 2>data isn't the end of the world, but speed is key.

96
00:04:46.879 --> 00:04:50.040
<v Speaker 1>That's a really helpful analogy. And these protocols use specific

97
00:04:50.439 --> 00:04:51.639
<v Speaker 1>like digital doors, right.

98
00:04:51.920 --> 00:04:56.040
<v Speaker 2>Ports precisely. Ports are just standardized numbers that specific services

99
00:04:56.120 --> 00:04:59.240
<v Speaker 2>used to communicate. Keeps everything organized. So for instance, when

100
00:04:59.240 --> 00:05:02.240
<v Speaker 2>you're browsing the web, that's mostly HTTP on Port eighty.

101
00:05:02.399 --> 00:05:05.079
<v Speaker 2>That's how your browser asks for and gets web pages.

102
00:05:05.160 --> 00:05:06.600
<v Speaker 1>Ay, standard web stuff yep.

103
00:05:07.040 --> 00:05:09.600
<v Speaker 2>Then there's a DNS, the domain name system on Court

104
00:05:09.639 --> 00:05:12.879
<v Speaker 2>fifty three. This one's critical. It's like the Internet's phone book.

105
00:05:13.279 --> 00:05:17.000
<v Speaker 2>It turns website names we understand, like Google dot Com

106
00:05:17.040 --> 00:05:20.439
<v Speaker 2>into the numerical IP, addresses computer's need. Without DNS, good

107
00:05:20.519 --> 00:05:22.839
<v Speaker 2>luck finding anything online easily.

108
00:05:22.759 --> 00:05:25.319
<v Speaker 1>Right, that makes sense. What about managing things remotely?

109
00:05:25.600 --> 00:05:30.360
<v Speaker 2>Good question? For secure remote management, you use SSH secure

110
00:05:30.399 --> 00:05:33.319
<v Speaker 2>shell on Port twenty two lets you log in and

111
00:05:33.360 --> 00:05:37.199
<v Speaker 2>control a server securely. Everything's encrypted. Compare that to the

112
00:05:37.199 --> 00:05:41.199
<v Speaker 2>old telnet on port twenty three totally insecure, sends everything

113
00:05:41.240 --> 00:05:43.319
<v Speaker 2>in plaintext. Big no no today.

114
00:05:43.480 --> 00:05:45.079
<v Speaker 1>Definitely avoid that one absolutely.

115
00:05:45.279 --> 00:05:48.279
<v Speaker 2>And if you're doing remote desktop stuff like controlling another

116
00:05:48.319 --> 00:05:51.639
<v Speaker 2>Windows PC over the network, that's often RDP Remote Desktop

117
00:05:51.639 --> 00:05:55.279
<v Speaker 2>Protocol on port three three eighty nine. Understanding these ports

118
00:05:55.319 --> 00:05:57.920
<v Speaker 2>helps you grasp you know, what's happening behind the scenes

119
00:05:57.920 --> 00:05:59.199
<v Speaker 2>with security and services.

120
00:05:59.279 --> 00:06:02.000
<v Speaker 1>It really does put those numbers into context. Yeah, but

121
00:06:02.079 --> 00:06:04.600
<v Speaker 1>networks aren't all the same size, are they not at all?

122
00:06:04.680 --> 00:06:07.560
<v Speaker 2>They very hugely. We usually categorize them. You've got your

123
00:06:07.639 --> 00:06:11.120
<v Speaker 2>land local area network that's typically your home or office network,

124
00:06:11.279 --> 00:06:14.639
<v Speaker 2>small area connect a bunch of lands together, maybe across

125
00:06:14.639 --> 00:06:17.360
<v Speaker 2>cities or countries. And you've got a wand wide area

126
00:06:17.399 --> 00:06:20.439
<v Speaker 2>network think the Internet itself is a giant one. And

127
00:06:20.480 --> 00:06:24.519
<v Speaker 2>then there's the really close range stuff a PAN personal

128
00:06:24.560 --> 00:06:27.720
<v Speaker 2>area network Bluetooth is the classic example, like headphones on

129
00:06:27.759 --> 00:06:31.040
<v Speaker 2>my phone exactly, that's a PAN, usually just around ten

130
00:06:31.120 --> 00:06:34.639
<v Speaker 2>meters range. Knowing these types helps you understand the scale

131
00:06:34.680 --> 00:06:35.959
<v Speaker 2>of the connections you're using.

132
00:06:36.120 --> 00:06:39.240
<v Speaker 1>Okay, so we have all these different networks. But how

133
00:06:39.240 --> 00:06:42.399
<v Speaker 1>do we actually build them fix them when something goes wrong?

134
00:06:42.439 --> 00:06:43.399
<v Speaker 1>You need special tools.

135
00:06:43.560 --> 00:06:46.879
<v Speaker 2>Oh, absolutely, the right tools are essential. Try making a

136
00:06:46.920 --> 00:06:49.600
<v Speaker 2>network cable without a crumper, it's basically impossible to do

137
00:06:49.639 --> 00:06:53.079
<v Speaker 2>it reliably. Or tracing one specific cable in a messy

138
00:06:53.120 --> 00:06:56.439
<v Speaker 2>server RAC without a tone or probe and wand nightmare.

139
00:06:56.519 --> 00:06:57.399
<v Speaker 1>I can imagine.

140
00:06:57.680 --> 00:07:00.959
<v Speaker 2>A really important one is the cable tester. Say you're

141
00:07:01.040 --> 00:07:03.920
<v Speaker 2>running a new fiber optic cable through a wall or conduit.

142
00:07:04.279 --> 00:07:06.480
<v Speaker 2>You definitely want to test it before you pull it through.

143
00:07:06.720 --> 00:07:09.879
<v Speaker 1>Ah yeah, because fixing it later would be awful.

144
00:07:10.160 --> 00:07:13.839
<v Speaker 2>Exactly. The tester confirms it's working, no breaks, and with

145
00:07:13.920 --> 00:07:16.600
<v Speaker 2>Wi Fi being so common, a Wi Fi analyzer is

146
00:07:16.680 --> 00:07:19.879
<v Speaker 2>super useful. It helps you see signal strength, find interference,

147
00:07:19.959 --> 00:07:24.279
<v Speaker 2>choose the best channel, basically troubleshoot and optimize your wireless network.

148
00:07:24.439 --> 00:07:26.199
<v Speaker 2>These tools are the unsung heroes.

149
00:07:26.279 --> 00:07:29.519
<v Speaker 1>Really makes sense, Okay, Let's shift from the invisible signals

150
00:07:29.519 --> 00:07:33.639
<v Speaker 1>and networks to the actual physical stuff, the hardware. Let's

151
00:07:33.639 --> 00:07:34.720
<v Speaker 1>start with screens.

152
00:07:34.959 --> 00:07:38.040
<v Speaker 2>Right displays what you're looking at all day. There's quite

153
00:07:38.079 --> 00:07:41.839
<v Speaker 2>a range now. LCDs liquid crystal displays are still very common,

154
00:07:42.040 --> 00:07:45.399
<v Speaker 2>but within LCDs you have different panel types. IPS panels

155
00:07:45.399 --> 00:07:48.199
<v Speaker 2>are popular because they have great color and wide viewing angles.

156
00:07:48.279 --> 00:07:50.560
<v Speaker 2>Good if you're doing design work or sharing your screen.

157
00:07:51.040 --> 00:07:55.279
<v Speaker 2>Then there's O lead organic light emitting diode, fantastic picture quality,

158
00:07:55.399 --> 00:07:58.279
<v Speaker 2>perfect blacks, and they tend to use less power, which

159
00:07:58.319 --> 00:07:59.759
<v Speaker 2>is why you see them in so many high end

160
00:07:59.800 --> 00:08:00.800
<v Speaker 2>phone and TVs.

161
00:08:00.839 --> 00:08:03.879
<v Speaker 1>Now right, those OLED screens look amazing, they really do.

162
00:08:04.240 --> 00:08:05.920
<v Speaker 2>And of course if it's a touch screen, you've got

163
00:08:05.920 --> 00:08:08.600
<v Speaker 2>the digitizer layer that actually senses your touch. And then

164
00:08:08.600 --> 00:08:11.959
<v Speaker 2>there are attributes like refresh rate. Higher refresh rates means

165
00:08:12.000 --> 00:08:15.839
<v Speaker 2>smoother motion, really important for gaming, and pixel density, which

166
00:08:15.839 --> 00:08:17.600
<v Speaker 2>affects how sharp everything looks.

167
00:08:17.759 --> 00:08:20.959
<v Speaker 1>Okay, so lots of factors in just the display. What

168
00:08:21.040 --> 00:08:24.319
<v Speaker 1>about connecting everything else, all those different cables and plugs.

169
00:08:24.439 --> 00:08:27.199
<v Speaker 2>Yeah, it can feel like spaghetti sometimes, but they each

170
00:08:27.199 --> 00:08:30.839
<v Speaker 2>have a job. For wired networks, it's mostly copper network

171
00:08:30.920 --> 00:08:34.840
<v Speaker 2>cables ethernet cables. They come in categories like PAT five E,

172
00:08:34.960 --> 00:08:37.799
<v Speaker 2>CAT six CAT six A. The main difference is speed

173
00:08:37.879 --> 00:08:40.080
<v Speaker 2>and how far they can carry the signal reliably.

174
00:08:40.200 --> 00:08:41.960
<v Speaker 1>So Cat six A is faster YEP.

175
00:08:42.320 --> 00:08:44.919
<v Speaker 2>CAT six A can handle ten gigabits per second up

176
00:08:44.960 --> 00:08:47.600
<v Speaker 2>to one hundred meters, So if you're wiring a building now,

177
00:08:48.080 --> 00:08:50.240
<v Speaker 2>using CAT six A is kind of future proofing it.

178
00:08:50.679 --> 00:08:53.279
<v Speaker 2>And these cables follow standards T five six eight A

179
00:08:53.480 --> 00:08:55.399
<v Speaker 2>or T five sixty eight B for how the little

180
00:08:55.440 --> 00:09:00.279
<v Speaker 2>wires insider arranged keeps everything compatible. Beyond networking, you've got

181
00:09:00.279 --> 00:09:04.159
<v Speaker 2>cables for removable storage, USB for flash drives, memory cards,

182
00:09:04.519 --> 00:09:07.279
<v Speaker 2>and less common now connections for optical drives.

183
00:09:07.320 --> 00:09:09.720
<v Speaker 1>Okay, let's crack open the computer case itself. What's the

184
00:09:09.720 --> 00:09:10.759
<v Speaker 1>core stuff inside?

185
00:09:10.919 --> 00:09:13.399
<v Speaker 2>Right? The heart of the machine. The motherboard is the

186
00:09:13.399 --> 00:09:16.480
<v Speaker 2>main circuit board connecting everything. They come in different sizes

187
00:09:16.559 --> 00:09:20.399
<v Speaker 2>or form factors ATX, micro, atx, itx.

188
00:09:19.799 --> 00:09:22.039
<v Speaker 1>And that determines if it fits in the case exactly.

189
00:09:22.799 --> 00:09:25.360
<v Speaker 2>You need the right size motherboard for your PC case.

190
00:09:25.440 --> 00:09:29.279
<v Speaker 2>These boards have all sorts of connectors PCIe slots for

191
00:09:29.360 --> 00:09:32.879
<v Speaker 2>graphics cards or other expansion cards, SATA ports for your

192
00:09:32.879 --> 00:09:36.799
<v Speaker 2>hard drives or SSDs, maybe MT two slots for those

193
00:09:36.960 --> 00:09:39.480
<v Speaker 2>super fast gumstick sized SSDs.

194
00:09:39.799 --> 00:09:40.120
<v Speaker 1>Okay.

195
00:09:40.399 --> 00:09:44.440
<v Speaker 2>One key thing to remember, especially for repairs laptop motherboards.

196
00:09:44.480 --> 00:09:47.080
<v Speaker 2>They're almost always proprietary.

197
00:09:46.519 --> 00:09:48.240
<v Speaker 1>Meaning you can't just swap them easily.

198
00:09:48.440 --> 00:09:51.440
<v Speaker 2>Pretty much, you usually can't put a Dell motherboard in

199
00:09:51.440 --> 00:09:54.799
<v Speaker 2>an HP laptop or even sometimes between different Dell models

200
00:09:55.080 --> 00:09:57.799
<v Speaker 2>makes repairs trickier. And of course, the CPU, the central

201
00:09:57.840 --> 00:10:00.360
<v Speaker 2>processing unit, the brain of a whole operation.

202
00:10:00.279 --> 00:10:03.559
<v Speaker 1>Got it? And what about the unsung hero of the office,

203
00:10:03.679 --> 00:10:06.080
<v Speaker 1>the printer. Setting them up and keeping them happy can.

204
00:10:06.000 --> 00:10:09.519
<v Speaker 2>Be tricky, ugh, printers love them, hate them. Setting them

205
00:10:09.559 --> 00:10:11.799
<v Speaker 2>up involves more than just plugging them in. You've got

206
00:10:11.919 --> 00:10:16.000
<v Speaker 2>configuration settings like duplex that's printing on both sides. Also orientation,

207
00:10:16.480 --> 00:10:20.159
<v Speaker 2>which paper tray to use, print quality settings.

208
00:10:19.840 --> 00:10:23.200
<v Speaker 1>Right, and security must be a bigger deal now with networked.

209
00:10:22.759 --> 00:10:27.080
<v Speaker 2>Printers, huge deal features like user authentication, maybe badge readers,

210
00:10:27.519 --> 00:10:30.399
<v Speaker 2>secure print release so documents don't sit out in the open.

211
00:10:30.480 --> 00:10:34.320
<v Speaker 2>It's important. And maintenance is different for laser versus inkjet.

212
00:10:34.559 --> 00:10:38.600
<v Speaker 2>Laser printers use toner. If you see white streaks on

213
00:10:38.639 --> 00:10:41.399
<v Speaker 2>your printouts, probably low toner or a dirty drum.

214
00:10:41.480 --> 00:10:42.600
<v Speaker 1>Okay, that's a common one.

215
00:10:42.639 --> 00:10:45.919
<v Speaker 2>It is for inkjets. If the colors are wrong or faded,

216
00:10:45.960 --> 00:10:49.000
<v Speaker 2>it's often a clogged print head, needing cleaning, or just

217
00:10:49.039 --> 00:10:53.120
<v Speaker 2>a low ink cartridge. Regular cleaning and maintenance definitely help

218
00:10:53.200 --> 00:10:54.840
<v Speaker 2>avoid those frustrating moments.

219
00:10:54.879 --> 00:10:59.039
<v Speaker 1>Good pips Okay, Inevitably things do go wrong. Let's talk troubleshooting.

220
00:10:59.360 --> 00:11:01.279
<v Speaker 1>Knowing the warning signs seems key.

221
00:11:01.559 --> 00:11:05.440
<v Speaker 2>Absolutely. When your computer acts up, especially with core components

222
00:11:05.480 --> 00:11:09.519
<v Speaker 2>like the motherboard, RAM, CPU, or power supply, it often

223
00:11:09.600 --> 00:11:14.720
<v Speaker 2>gives clues. Listen for POSD beeps during startup. Those short

224
00:11:14.720 --> 00:11:17.480
<v Speaker 2>codes can tell you what's wrong before Windows even loads.

225
00:11:17.919 --> 00:11:20.720
<v Speaker 2>A sudden blank screen or the system just being dead

226
00:11:21.080 --> 00:11:23.919
<v Speaker 2>no power could be the power supply, could be the motherboard.

227
00:11:24.080 --> 00:11:25.200
<v Speaker 1>What about overheating?

228
00:11:25.559 --> 00:11:28.480
<v Speaker 2>Classic symptom is the computer randomly shutting down after it's

229
00:11:28.480 --> 00:11:30.799
<v Speaker 2>been running for a bit, say ten to fifteen minutes.

230
00:11:31.200 --> 00:11:34.120
<v Speaker 2>Often means a fan failed or vents are blocked. And

231
00:11:34.200 --> 00:11:37.080
<v Speaker 2>sometimes you can literally see a problem like a bulging

232
00:11:37.159 --> 00:11:40.080
<v Speaker 2>or swollen capacitor on the motherboard. That's a clear sign

233
00:11:40.159 --> 00:11:43.000
<v Speaker 2>something's about to fail badly. These are all symptoms pointing

234
00:11:43.039 --> 00:11:43.759
<v Speaker 2>you in a direction.

235
00:11:44.000 --> 00:11:47.360
<v Speaker 1>Okay, and storage drives losing data is the big fear there.

236
00:11:47.399 --> 00:11:48.360
<v Speaker 1>What are the warning signs?

237
00:11:48.399 --> 00:11:52.159
<v Speaker 2>Yeah, storage issues are scary for traditional spinning hard drives HDDs.

238
00:11:52.360 --> 00:11:55.799
<v Speaker 2>The absolute classic warning sign is that grinding or clicking noise.

239
00:11:56.080 --> 00:11:58.440
<v Speaker 1>Oh that sounds bad. It is bad.

240
00:11:58.600 --> 00:12:02.080
<v Speaker 2>It usually means the physical mechanism inside is failing. Back

241
00:12:02.120 --> 00:12:05.600
<v Speaker 2>up immediately if you hear that. Other signs bootable device

242
00:12:06.039 --> 00:12:10.639
<v Speaker 2>not found, errors, actual data loss or corruption, things taking

243
00:12:10.720 --> 00:12:13.679
<v Speaker 2>forever to read or write. If you're using RAY that's

244
00:12:13.759 --> 00:12:17.399
<v Speaker 2>multiple drives working together. Look at the LED status lights.

245
00:12:17.879 --> 00:12:20.799
<v Speaker 2>An error light or an audible alarm usually means one

246
00:12:20.840 --> 00:12:22.159
<v Speaker 2>of the drives in the set has.

247
00:12:22.039 --> 00:12:25.279
<v Speaker 1>Failed and RAY ten needs four drives right minimum four

248
00:12:25.399 --> 00:12:29.919
<v Speaker 1>Yeah for that combination of mirroring, redundancy and striping speed.

249
00:12:30.240 --> 00:12:33.440
<v Speaker 2>Paying attention to these warnings can save your data definitely.

250
00:12:33.799 --> 00:12:37.720
<v Speaker 1>Lastly, visual problems screens or projectors acting up right.

251
00:12:37.919 --> 00:12:41.360
<v Speaker 2>Display issues can be simple fixes. Sometimes. Always check the

252
00:12:41.360 --> 00:12:43.960
<v Speaker 2>input source setting first and make sure the cables are

253
00:12:44.000 --> 00:12:46.879
<v Speaker 2>plugged in tight. A loose cable is a very common

254
00:12:46.919 --> 00:12:48.679
<v Speaker 2>cause of flickering or no signal.

255
00:12:48.840 --> 00:12:51.240
<v Speaker 1>Good point. Check the simple stuff first always.

256
00:12:51.600 --> 00:12:54.240
<v Speaker 2>For projectors, a burned out ball do is common over time,

257
00:12:54.480 --> 00:12:56.759
<v Speaker 2>or sometimes they just shut down intermnutently because they've hit

258
00:12:56.799 --> 00:13:00.000
<v Speaker 2>their standby timer setting. You might also see a fuzzy image,

259
00:13:00.480 --> 00:13:03.279
<v Speaker 2>maybe dead pixels, those annoying little dots that stay black

260
00:13:03.519 --> 00:13:06.360
<v Speaker 2>or weird colors, and distorted images. Often that's just the

261
00:13:06.360 --> 00:13:09.399
<v Speaker 2>screen resolution being set wrong for the display or maybe

262
00:13:09.440 --> 00:13:13.519
<v Speaker 2>sizing issues. Lots of potential visual glitches, but often traceable.

263
00:13:13.639 --> 00:13:17.440
<v Speaker 1>Okay, let's switch gears to the software side, the operating systems,

264
00:13:17.480 --> 00:13:18.919
<v Speaker 1>the digital brains right.

265
00:13:18.759 --> 00:13:22.960
<v Speaker 2>The operating system or OS. That's the fundamental software managing everything.

266
00:13:23.159 --> 00:13:26.879
<v Speaker 2>We mostly know Windows, Mac, OS, Linux, maybe Chromos. For

267
00:13:26.919 --> 00:13:30.000
<v Speaker 2>desktops and laptops, these are workstation systems, and then for

268
00:13:30.159 --> 00:13:34.559
<v Speaker 2>mobile it's primarily iOS and iPad OS and Android. Each

269
00:13:34.600 --> 00:13:37.399
<v Speaker 2>one provides that core interface and manages the hardware.

270
00:13:37.559 --> 00:13:39.960
<v Speaker 1>And how do they actually store our files? The underlying

271
00:13:39.960 --> 00:13:41.519
<v Speaker 1>file systems are different, aren't they?

272
00:13:41.600 --> 00:13:44.399
<v Speaker 2>They are, and it matters. For example, Fat thirty two

273
00:13:44.559 --> 00:13:47.919
<v Speaker 2>is super compatible, works on Windows, Mac, Linux, great for

274
00:13:48.039 --> 00:13:51.360
<v Speaker 2>USB sticks you move between computers, but the big limitation

275
00:13:51.559 --> 00:13:54.080
<v Speaker 2>is that for gigabyte file size limit, you can't save

276
00:13:54.120 --> 00:13:55.440
<v Speaker 2>a single file bigger than that.

277
00:13:55.919 --> 00:13:59.519
<v Speaker 1>Okay, so not great for large video files.

278
00:13:59.279 --> 00:14:03.000
<v Speaker 2>Or backups exactly. That's why Windows uses NTFS or the

279
00:14:03.000 --> 00:14:07.080
<v Speaker 2>newer efs, macOS uses APFS, and Linux commonly uses XD

280
00:14:07.200 --> 00:14:11.120
<v Speaker 2>four or XFS. These newer ones handle huge files, offer

281
00:14:11.159 --> 00:14:15.679
<v Speaker 2>better security, journaling for reliability, lots of advantages. Knowing the

282
00:14:15.679 --> 00:14:18.720
<v Speaker 2>file system helps if you run into compatibility issues.

283
00:14:18.519 --> 00:14:21.200
<v Speaker 1>Makes sense and for Mac users specifically, what are some

284
00:14:21.320 --> 00:14:24.080
<v Speaker 1>key macOS features and maybe best practices.

285
00:14:24.759 --> 00:14:27.440
<v Speaker 2>macOS has its own way of doing things. Installing apps

286
00:14:27.480 --> 00:14:31.080
<v Speaker 2>often involves dot DMG files, Dot PPG installers or dot

287
00:14:31.159 --> 00:14:34.120
<v Speaker 2>app bundles, plus the app store. Of course, Its system

288
00:14:34.159 --> 00:14:37.840
<v Speaker 2>folder structure is also distinct, with folders like applications, users

289
00:14:37.919 --> 00:14:42.480
<v Speaker 2>library understanding that helps navigate for best practices. Time Machine

290
00:14:42.480 --> 00:14:45.480
<v Speaker 2>for backups is fantastic, really easy to use. Keeping the

291
00:14:45.519 --> 00:14:48.600
<v Speaker 2>OS and apps updated with patches and rapid security responses

292
00:14:48.639 --> 00:14:51.320
<v Speaker 2>is crucial for security and keychain is Its built in

293
00:14:51.320 --> 00:14:54.559
<v Speaker 2>password manager sinks your password securely across your Apple devices,

294
00:14:54.720 --> 00:14:55.399
<v Speaker 2>very landing.

295
00:14:55.279 --> 00:14:58.559
<v Speaker 1>Very integrated. Okay, security, it's everywhere now a constant concern.

296
00:14:58.879 --> 00:15:01.440
<v Speaker 1>How do operating cit stems help us protect ourselves?

297
00:15:01.720 --> 00:15:05.000
<v Speaker 2>OS security is foundational. It starts with basic user and

298
00:15:05.000 --> 00:15:08.240
<v Speaker 2>group management, knowing the difference between a local account versus

299
00:15:08.240 --> 00:15:11.519
<v Speaker 2>a Microsoft account in Windows and the different permission levels

300
00:15:11.879 --> 00:15:14.559
<v Speaker 2>standard user, administrator guests.

301
00:15:14.240 --> 00:15:16.039
<v Speaker 1>Right, don't give everyone admin rights.

302
00:15:15.799 --> 00:15:20.039
<v Speaker 2>Please don't. And login methods have evolved beyond passwords. We

303
00:15:20.120 --> 00:15:24.159
<v Speaker 2>have pins biometrics like fingerprint or facial recognition, though you

304
00:15:24.200 --> 00:15:26.440
<v Speaker 2>need the right hardware for those like a Windows Hello

305
00:15:26.519 --> 00:15:31.320
<v Speaker 2>camera and single sign on sso simplifies logins across multiple services.

306
00:15:31.759 --> 00:15:35.080
<v Speaker 2>Then there's controlling access to files and folders using NTFS

307
00:15:35.080 --> 00:15:40.080
<v Speaker 2>permissions versus share permissions, understanding how inheritance works. Best practices

308
00:15:40.120 --> 00:15:44.480
<v Speaker 2>are vital restrict permissions, disable the guest account, set lockouts

309
00:15:44.480 --> 00:15:48.279
<v Speaker 2>after failed login attempts, use screen locks, change default admin passwords,

310
00:15:48.320 --> 00:15:50.799
<v Speaker 2>disable auto run. The list goes on. It's all about

311
00:15:50.879 --> 00:15:51.639
<v Speaker 2>layers of defense.

312
00:15:51.759 --> 00:15:54.240
<v Speaker 1>That's a lot for desktops, but what about our phones?

313
00:15:54.279 --> 00:15:55.879
<v Speaker 1>We carry our lives on them. How do we lock

314
00:15:55.919 --> 00:15:57.000
<v Speaker 1>those down effectively?

315
00:15:57.279 --> 00:16:00.799
<v Speaker 2>Mobile security is just as critical. Basic hardening includes using

316
00:16:00.799 --> 00:16:04.840
<v Speaker 2>strong screen locks, face ID fingerprint a good pin, not

317
00:16:04.960 --> 00:16:08.720
<v Speaker 2>just a simple swipe pattern, and definitely enable device encryption.

318
00:16:09.360 --> 00:16:12.440
<v Speaker 2>Keeping the OS and your apps updated via patch management

319
00:16:12.519 --> 00:16:15.600
<v Speaker 2>is non negotiable. Security fixes come out all the time.

320
00:16:15.840 --> 00:16:18.480
<v Speaker 2>Endpoint security apps like anti virus aren't as common for

321
00:16:18.519 --> 00:16:20.919
<v Speaker 2>personal phones, but at a layer, and the remote actions

322
00:16:20.960 --> 00:16:23.720
<v Speaker 2>are crucial if your phone is lost or stolen.

323
00:16:23.720 --> 00:16:26.399
<v Speaker 1>Like find my iPhone or the Android equivalent exactly.

324
00:16:26.519 --> 00:16:29.840
<v Speaker 2>Locator apps plus the ability to remotely wipe your data

325
00:16:30.039 --> 00:16:32.960
<v Speaker 2>or trigger a remote backup, and as we mentioned MDM

326
00:16:33.000 --> 00:16:36.159
<v Speaker 2>helps businesses enforce policies be aware of threats too, like

327
00:16:36.279 --> 00:16:39.559
<v Speaker 2>ransomware locking your files, or trojans hiding malware and legit

328
00:16:39.600 --> 00:16:41.919
<v Speaker 2>looking apps. Vigilance is key, okay.

329
00:16:41.960 --> 00:16:43.159
<v Speaker 1>And when it's time to get rid of an old

330
00:16:43.159 --> 00:16:46.080
<v Speaker 1>device or hard drive, just deleting isn't enough.

331
00:16:46.440 --> 00:16:50.399
<v Speaker 2>Absolutely not Deleting files just marks the space as available.

332
00:16:50.759 --> 00:16:54.559
<v Speaker 2>The data is often still recoverable. Proper data destruction is vital.

333
00:16:54.879 --> 00:16:58.039
<v Speaker 2>For old magnetic hard drives, degaussing uses a powerful magnet

334
00:16:58.039 --> 00:17:01.320
<v Speaker 2>to wipe them clean. Very effective, But for any drive

335
00:17:01.440 --> 00:17:04.960
<v Speaker 2>magnetic or SSD physical destruction shredding it is the most

336
00:17:05.000 --> 00:17:05.960
<v Speaker 2>certain method.

337
00:17:05.839 --> 00:17:06.960
<v Speaker 1>So I take a hammer to it.

338
00:17:07.160 --> 00:17:12.440
<v Speaker 2>Huh, Well, maybe professionally shredded is better, Especially for businesses.

339
00:17:12.559 --> 00:17:15.359
<v Speaker 2>Using a certified third party vendor who provides proof of

340
00:17:15.400 --> 00:17:18.200
<v Speaker 2>destruction is often the way to go for compliance reasons.

341
00:17:18.240 --> 00:17:19.640
<v Speaker 2>Don't just throw old tech in the bin.

342
00:17:19.880 --> 00:17:23.559
<v Speaker 1>Good advice, okay. One last area beyond the tech skills,

343
00:17:23.559 --> 00:17:26.599
<v Speaker 1>how we interact with people, especially when providing it support

344
00:17:26.920 --> 00:17:28.079
<v Speaker 1>is super important too.

345
00:17:28.000 --> 00:17:31.720
<v Speaker 2>Isn't it hugely important? Professionalism and communication can make all

346
00:17:31.759 --> 00:17:35.119
<v Speaker 2>the difference. Simple things like appearance, stressing appropriately for the

347
00:17:35.160 --> 00:17:39.440
<v Speaker 2>work environment. But even more critical is language. Avoid technical

348
00:17:39.519 --> 00:17:42.519
<v Speaker 2>jargon and acronyms when talking to non technical users. It

349
00:17:42.640 --> 00:17:44.119
<v Speaker 2>just confuses and intimidates.

350
00:17:44.200 --> 00:17:46.640
<v Speaker 1>Yeah, speak plain English exactly.

351
00:17:46.200 --> 00:17:49.200
<v Speaker 2>Clarify what the user is telling you, ask open ended questions,

352
00:17:49.559 --> 00:17:51.759
<v Speaker 2>restate the problem in your own words to make sure

353
00:17:51.799 --> 00:17:56.799
<v Speaker 2>you understand. Use discretion and managing expectations is key. Give

354
00:17:56.880 --> 00:18:01.480
<v Speaker 2>realistic timelines, keep people updated on progress, offer options, provide

355
00:18:01.559 --> 00:18:04.640
<v Speaker 2>documentation if needed, and always follow up.

356
00:18:04.799 --> 00:18:07.799
<v Speaker 1>So it's not just fixing the problem but managing the whole.

357
00:18:07.599 --> 00:18:11.440
<v Speaker 2>Interaction precisely, and in some cases like security incidents, it

358
00:18:11.480 --> 00:18:16.160
<v Speaker 2>also involves properly identifying and preserving evidence. It's about building

359
00:18:16.200 --> 00:18:19.240
<v Speaker 2>trust and solving the problem effectively and professionally.

360
00:18:19.359 --> 00:18:22.400
<v Speaker 1>Wow. Okay, we've covered a ton of ground today, from

361
00:18:22.440 --> 00:18:24.519
<v Speaker 1>how your phone knows where it is, to the protocols

362
00:18:24.599 --> 00:18:28.559
<v Speaker 1>running the internet, the guts of our computers, printers, troubleshooting

363
00:18:29.200 --> 00:18:32.160
<v Speaker 1>and crucial security. Really peeling back the layers.

364
00:18:32.240 --> 00:18:34.039
<v Speaker 2>Yeah, it's a lot, but hopefully it gives you, the

365
00:18:34.119 --> 00:18:37.799
<v Speaker 2>listener a stronger foundation. Understanding these core ideas really does

366
00:18:37.839 --> 00:18:41.279
<v Speaker 2>empower you. You can navigate your tech better, maybe troubleshoots

367
00:18:41.279 --> 00:18:45.119
<v Speaker 2>simple problems yourself, make smarter decisions about devices and security.

368
00:18:45.319 --> 00:18:47.960
<v Speaker 2>Whether you're in it or just curious, it helps bridge

369
00:18:47.960 --> 00:18:51.240
<v Speaker 2>that gap. Knowledge is power, as they say, especially when

370
00:18:51.279 --> 00:18:52.559
<v Speaker 2>you understand why.

371
00:18:52.559 --> 00:18:55.519
<v Speaker 1>Absolutely, which leads to a final thought for you to

372
00:18:55.599 --> 00:19:00.799
<v Speaker 1>chew on. With technology changing so incredibly fast, what do

373
00:19:00.839 --> 00:19:04.400
<v Speaker 1>you think the next fundamental core IP skill will be.

374
00:19:04.759 --> 00:19:07.640
<v Speaker 1>What's the next essential thing we'll all need to understand

375
00:19:07.920 --> 00:19:09.839
<v Speaker 1>and how might it change how we use our tech

376
00:19:09.920 --> 00:19:10.359
<v Speaker 1>every day.

377
00:19:10.680 --> 00:19:13.000
<v Speaker 2>That's a great question to ponder. It really makes you

378
00:19:13.000 --> 00:19:15.720
<v Speaker 2>think about the future. We encourage you to reflect on

379
00:19:15.839 --> 00:19:17.759
<v Speaker 2>how all this tech stuff plays out in your own life,

380
00:19:17.920 --> 00:19:20.799
<v Speaker 2>maybe dig a little deeper on topics that caught your interest.

381
00:19:21.160 --> 00:19:23.160
<v Speaker 2>The learning never really stops in this field.