WEBVTT

1
00:00:00.120 --> 00:00:04.000
<v Speaker 1>Okay, let's unpack this in the well, the ever evolving

2
00:00:04.000 --> 00:00:07.440
<v Speaker 1>world of IT infrastructure, staying current isn't just a recommendation,

3
00:00:07.639 --> 00:00:09.759
<v Speaker 1>is it's pretty much a necessity.

4
00:00:09.839 --> 00:00:10.320
<v Speaker 2>Absolutely.

5
00:00:10.359 --> 00:00:13.320
<v Speaker 1>We're constantly looking for ways to build more resilient, secure,

6
00:00:13.880 --> 00:00:18.320
<v Speaker 1>efficient systems, and today we're diving headfirst into a release

7
00:00:18.320 --> 00:00:20.160
<v Speaker 1>that well promise is exactly that.

8
00:00:20.440 --> 00:00:25.079
<v Speaker 2>Indeed, we're talking about Windows Server twenty twenty five. And yeah,

9
00:00:25.120 --> 00:00:28.440
<v Speaker 2>this isn't just a refresh, not really. It's a platform

10
00:00:28.440 --> 00:00:32.280
<v Speaker 2>engineered for the hybrid reality of modern IT. Okay, it's

11
00:00:32.320 --> 00:00:35.000
<v Speaker 2>really pushing the boundaries of what a server OS can do,

12
00:00:35.200 --> 00:00:39.439
<v Speaker 2>especially especially in how it bridges on premises and cloud environments.

13
00:00:39.560 --> 00:00:42.759
<v Speaker 1>Right, So our mission for you, our curious listener, is

14
00:00:42.799 --> 00:00:46.600
<v Speaker 1>to cut through the noise. We've distilled the absolute most

15
00:00:46.600 --> 00:00:50.439
<v Speaker 1>important insights from a comprehensive guide Windowserver twenty twenty five

16
00:00:50.479 --> 00:00:53.759
<v Speaker 1>at nettrain dot pdf. Think of this as your fast

17
00:00:53.759 --> 00:00:56.759
<v Speaker 1>trick sort of to understanding this strategic advantages the practical

18
00:00:56.759 --> 00:01:00.320
<v Speaker 1>implications of Server twenty twenty five. We're talking everything core

19
00:01:00.359 --> 00:01:04.599
<v Speaker 1>networking installation right through to advanced security, storage and those

20
00:01:05.000 --> 00:01:08.079
<v Speaker 1>those crucial hybrid cloud features. We're giving you the why

21
00:01:08.280 --> 00:01:10.799
<v Speaker 1>behind the what making sure you walk away, you know,

22
00:01:10.840 --> 00:01:11.799
<v Speaker 1>truly well informed.

23
00:01:11.959 --> 00:01:15.879
<v Speaker 2>Exactly, we'll highlight the transformative features, the key differentiators, and

24
00:01:15.920 --> 00:01:19.560
<v Speaker 2>really what these advancements mean for your day to day

25
00:01:19.599 --> 00:01:23.439
<v Speaker 2>operations and your long term infrastructure strategy. Let's make sense

26
00:01:23.480 --> 00:01:24.120
<v Speaker 2>of it all together.

27
00:01:24.519 --> 00:01:29.079
<v Speaker 1>Okay, let's start with the very bedrock networking and server fundamentals.

28
00:01:29.120 --> 00:01:32.040
<v Speaker 1>We're talking about the core architecture, right, how devices communicate,

29
00:01:32.400 --> 00:01:35.359
<v Speaker 1>share resources, all built on reliable hardware. Right.

30
00:01:35.519 --> 00:01:38.799
<v Speaker 2>And while the basics of say a local area network

31
00:01:38.840 --> 00:01:42.840
<v Speaker 2>a land you know, connecting devices locally haven't fundamentally changed,

32
00:01:43.480 --> 00:01:46.000
<v Speaker 2>what's crucial for Server twenty twenty five is how it

33
00:01:46.239 --> 00:01:50.200
<v Speaker 2>optimizes and secures these connections. Okay, so, for instance, addressing,

34
00:01:50.280 --> 00:01:53.120
<v Speaker 2>everyone knows IPv four right, sure, But the real leap

35
00:01:53.159 --> 00:01:56.159
<v Speaker 2>in network scalability and efficiency with Server twenty twenty five

36
00:01:56.200 --> 00:01:59.120
<v Speaker 2>that comes with its deep embrace of IPv six.

37
00:01:59.200 --> 00:02:02.120
<v Speaker 1>So it's more than just like a bigger pool of addresses.

38
00:02:02.120 --> 00:02:05.239
<v Speaker 1>Then where does IPv six truly shine in a twenty

39
00:02:05.280 --> 00:02:06.200
<v Speaker 1>twenty five environment?

40
00:02:06.280 --> 00:02:09.120
<v Speaker 2>Oh? Absolutely, it's much more than just solving address scarcity.

41
00:02:09.159 --> 00:02:13.199
<v Speaker 2>IPv six fundamentally future proofs your network with Server twenty

42
00:02:13.199 --> 00:02:16.879
<v Speaker 2>twenty five. It means inherently more efficient data distribution. Think

43
00:02:16.919 --> 00:02:22.120
<v Speaker 2>about features like multicast addressing, streamlined video streaming, or large

44
00:02:22.240 --> 00:02:26.879
<v Speaker 2>data transfers without taxing the network with duplicate streams. It

45
00:02:26.919 --> 00:02:31.000
<v Speaker 2>also brings built in quality of service, more robust security features,

46
00:02:31.680 --> 00:02:34.240
<v Speaker 2>which are vital. I mean, look at the explosion of

47
00:02:34.280 --> 00:02:38.000
<v Speaker 2>IoT devices. Yeah, complex network traffic yea, it's everywhere. So

48
00:02:38.039 --> 00:02:40.919
<v Speaker 2>it drastically simplifies network management in the long run.

49
00:02:41.080 --> 00:02:44.680
<v Speaker 1>That sounds like a pretty foundational shift. And speaking of foundations,

50
00:02:44.800 --> 00:02:47.560
<v Speaker 1>what about the physical server itself? I mean, beyond just

51
00:02:47.599 --> 00:02:50.639
<v Speaker 1>being a powerful computer, what does server twenty twenty five

52
00:02:50.759 --> 00:02:53.400
<v Speaker 1>demand from its underlying hardware?

53
00:02:53.560 --> 00:02:56.719
<v Speaker 2>Well, Server twenty twenty five is designed to leverage modern hardware,

54
00:02:56.960 --> 00:03:01.639
<v Speaker 2>really push it. We're talking powerful multi course CPUs, substantial

55
00:03:01.759 --> 00:03:05.199
<v Speaker 2>RAM often hundreds of gigs these days wow, and robust

56
00:03:05.319 --> 00:03:08.560
<v Speaker 2>disc subsystems. Ideally, you know a mix of high speed

57
00:03:08.599 --> 00:03:12.680
<v Speaker 2>SSDs for performance and maybe high capacity HDDs for bulk storage,

58
00:03:12.919 --> 00:03:17.080
<v Speaker 2>and crucially, multiple network interface cards and i sees that's

59
00:03:17.080 --> 00:03:21.879
<v Speaker 2>almost standard now provides a redundancy significantly boosts data throughput,

60
00:03:22.000 --> 00:03:24.840
<v Speaker 2>which is essential for virtualized and hybrid workloads.

61
00:03:24.960 --> 00:03:26.879
<v Speaker 1>So the hardware is the muscle, right, and the network

62
00:03:26.879 --> 00:03:29.599
<v Speaker 1>operating system, the NS, that's the brain coordinating at all.

63
00:03:30.080 --> 00:03:33.120
<v Speaker 1>How has Windows Server twenty twenty five's approach to that

64
00:03:33.199 --> 00:03:37.159
<v Speaker 1>brain power evolved, especially with Microsoft's whole cloud first thing.

65
00:03:37.360 --> 00:03:40.919
<v Speaker 2>Yeah, the evolution is profound. Windows Server twenty twenty five

66
00:03:40.960 --> 00:03:43.520
<v Speaker 2>is really the latest step in Microsoft's Windows Server for

67
00:03:43.560 --> 00:03:46.719
<v Speaker 2>the cloud journey that started way back with Server twenty sixteen.

68
00:03:46.759 --> 00:03:49.039
<v Speaker 2>Really right, This means it's built from the ground up

69
00:03:49.080 --> 00:03:53.360
<v Speaker 2>to integrate seamlessly with cloud services, particularly Azure. It's about

70
00:03:53.439 --> 00:03:56.719
<v Speaker 2>more than just managing local files and users. It's about

71
00:03:56.800 --> 00:04:01.479
<v Speaker 2>providing a unified control plane across on prem edge cloud resources,

72
00:04:02.000 --> 00:04:05.520
<v Speaker 2>emphasizing hybrid deployments intelligent automation. That's the key.

73
00:04:05.599 --> 00:04:08.039
<v Speaker 1>Okay, now that we've covered the groundwork, let's get practical.

74
00:04:08.080 --> 00:04:11.800
<v Speaker 1>For anyone looking to actually deploy Server twenty twenty five.

75
00:04:12.240 --> 00:04:15.879
<v Speaker 1>What are the key requirements and maybe critical installation choices

76
00:04:15.879 --> 00:04:16.720
<v Speaker 1>they need to be aware of.

77
00:04:16.959 --> 00:04:21.439
<v Speaker 2>Okay, requirements, You'll need a sixty four bit processor ideally

78
00:04:21.519 --> 00:04:24.399
<v Speaker 2>two point zero gigahertz or higher. At least thirty two

79
00:04:24.480 --> 00:04:27.439
<v Speaker 2>gigs of RAM, though honestly more is always better for

80
00:04:27.480 --> 00:04:30.959
<v Speaker 2>server roles. Sure storage, you need both really a two

81
00:04:31.079 --> 00:04:34.920
<v Speaker 2>fifty six GB SSD for the OS minimum and at

82
00:04:35.000 --> 00:04:38.560
<v Speaker 2>least a terabyte HDD for data, plus a one gigabit

83
00:04:38.600 --> 00:04:42.560
<v Speaker 2>Ethernet and IC Right. But for modern security, a Trusted

84
00:04:42.600 --> 00:04:46.360
<v Speaker 2>Platform Module a TPM is now practically non negotiable. It's

85
00:04:46.360 --> 00:04:48.399
<v Speaker 2>all about securing the boot process itself.

86
00:04:48.439 --> 00:04:50.879
<v Speaker 1>And speaking of booting, Server TOM twenty five is all

87
00:04:50.920 --> 00:04:54.040
<v Speaker 1>in on UEFI, not the legacy bios. What does that

88
00:04:54.079 --> 00:04:55.079
<v Speaker 1>mean for us on the ground.

89
00:04:55.199 --> 00:04:58.279
<v Speaker 2>Yeah. UFI offers faster, much more secure boots. It supports

90
00:04:58.319 --> 00:05:02.079
<v Speaker 2>critical features like secure boot locker for encryption. More importantly,

91
00:05:02.120 --> 00:05:05.800
<v Speaker 2>it supports the GID partition Table GPT partitioning scheme. This

92
00:05:05.920 --> 00:05:09.360
<v Speaker 2>is essential, absolutely essential for discs larger than two terabytes.

93
00:05:09.399 --> 00:05:11.879
<v Speaker 2>Ah Okay, and yeah, it's a non negotiable requirement for

94
00:05:11.920 --> 00:05:15.680
<v Speaker 2>Server twenty twenty five installations. Ensures better performance reliability for

95
00:05:15.759 --> 00:05:16.680
<v Speaker 2>modern storage.

96
00:05:16.839 --> 00:05:20.319
<v Speaker 1>Gotcha. So, once you're past the initial setup, you've got

97
00:05:20.439 --> 00:05:23.839
<v Speaker 1>choices and how Server twenty twenty five presents itself? Right?

98
00:05:23.879 --> 00:05:25.879
<v Speaker 1>You can go with the full desktop experience or the

99
00:05:26.000 --> 00:05:29.319
<v Speaker 1>leaner server Core or even nanoserver. How do these options

100
00:05:29.360 --> 00:05:31.399
<v Speaker 1>impact deployment strategy?

101
00:05:31.680 --> 00:05:36.879
<v Speaker 2>These choices are strategic definitely not trivial. The desktop experience

102
00:05:36.920 --> 00:05:40.360
<v Speaker 2>gives you that familiar graphical interface you know. Great for

103
00:05:40.439 --> 00:05:43.759
<v Speaker 2>smaller setups or maybe folks new to server okay. Server

104
00:05:43.839 --> 00:05:47.639
<v Speaker 2>Core is the lean headless option. Reduces the attack surface,

105
00:05:47.720 --> 00:05:51.560
<v Speaker 2>memory footprint, patching requirements, ideal for infrastructure roles like domain

106
00:05:51.600 --> 00:05:52.199
<v Speaker 2>controllers or.

107
00:05:52.199 --> 00:05:54.160
<v Speaker 1>File servers, right less to go wrong.

108
00:05:54.120 --> 00:05:57.920
<v Speaker 2>Exactly, and nanoserver even lighter is purpose built for cloud

109
00:05:58.000 --> 00:06:02.680
<v Speaker 2>native apps and containers for minimal reboots, high density. So

110
00:06:02.959 --> 00:06:06.959
<v Speaker 2>your choice directly impacts resource use, security and importantly how

111
00:06:06.959 --> 00:06:08.720
<v Speaker 2>you manage the server going forward, and.

112
00:06:08.639 --> 00:06:12.240
<v Speaker 1>For streamlined management across all these, especially in hybrid setups.

113
00:06:12.360 --> 00:06:14.759
<v Speaker 1>Windows admin Center seems to have become a crucial tool,

114
00:06:14.800 --> 00:06:15.199
<v Speaker 1>hasn't it?

115
00:06:15.360 --> 00:06:18.319
<v Speaker 2>Oh, it absolutely has. Windows admin Center. It's that modern

116
00:06:18.560 --> 00:06:23.000
<v Speaker 2>web based tool. It consolidates server cluster, even client device

117
00:06:23.040 --> 00:06:27.240
<v Speaker 2>management into one intuitive interface. It goes way beyond older

118
00:06:27.240 --> 00:06:31.480
<v Speaker 2>tools like RSAT. But what's truly powerful here, particularly for

119
00:06:31.560 --> 00:06:35.120
<v Speaker 2>Server twenty twenty five, is its integration with PowerShell Desired

120
00:06:35.160 --> 00:06:40.600
<v Speaker 2>State Configuration DSc oh DSc. This helps you manage configuration drift,

121
00:06:40.839 --> 00:06:44.480
<v Speaker 2>basically making sure your servers automatically stay compliant with your

122
00:06:44.560 --> 00:06:48.839
<v Speaker 2>organizational standards. That's a massive win for consistency security, especially

123
00:06:48.839 --> 00:06:50.040
<v Speaker 2>in dynamic environments.

124
00:06:50.160 --> 00:06:53.879
<v Speaker 1>Okay, so if the server is the engine, then actor, directory,

125
00:06:53.879 --> 00:06:57.800
<v Speaker 1>domain services adds. Yeah, like the master key in central directory,

126
00:06:57.800 --> 00:07:01.120
<v Speaker 1>isn't it. It's the backbone for identity and access in

127
00:07:01.360 --> 00:07:03.079
<v Speaker 1>well almost every Windows environment.

128
00:07:03.120 --> 00:07:06.720
<v Speaker 2>That's exactly right, Adds is that centralized repository for everything

129
00:07:07.040 --> 00:07:10.920
<v Speaker 2>user accounts, computers, printers, network services, and each has its

130
00:07:10.959 --> 00:07:12.639
<v Speaker 2>own specific security.

131
00:07:12.199 --> 00:07:13.920
<v Speaker 1>Settings, granular control.

132
00:07:13.759 --> 00:07:18.519
<v Speaker 2>Precisely, granular control over all your network resources. It's supported

133
00:07:18.519 --> 00:07:23.519
<v Speaker 2>by core protocols know ldapp for directory access, curbaros for authentication,

134
00:07:24.120 --> 00:07:28.000
<v Speaker 2>DNS for name resolution standard. Yeah, standard, but critical. And

135
00:07:28.040 --> 00:07:31.040
<v Speaker 2>for administrators you're looking at tools ranging from the familiar

136
00:07:31.079 --> 00:07:35.920
<v Speaker 2>graphical consoles, active directory users and computers to powerful PowerShell

137
00:07:35.959 --> 00:07:40.000
<v Speaker 2>modules for scripting and automating complex tasks at scale.

138
00:07:39.639 --> 00:07:44.920
<v Speaker 1>And within eightyds. There's that clear hierarchy domains, trees, forests.

139
00:07:45.839 --> 00:07:50.000
<v Speaker 1>This structure dictates how resources are shared managed. But for

140
00:07:50.040 --> 00:07:53.720
<v Speaker 1>those managing existing environments, what's the crucial difference between a

141
00:07:53.759 --> 00:07:56.560
<v Speaker 1>domain and just a simple work group, Especially when thinking

142
00:07:56.600 --> 00:07:58.839
<v Speaker 1>about scaling with Server twenty twenty five.

143
00:07:59.000 --> 00:08:02.480
<v Speaker 2>That distinction is absolutely fundamental for securing and scaling your

144
00:08:02.519 --> 00:08:06.680
<v Speaker 2>IT environment efficiently. Domains use dedicated servers domain controllers. For

145
00:08:06.759 --> 00:08:10.759
<v Speaker 2>centralized services, it's a client server model, right, Authentication policy enforcement,

146
00:08:10.759 --> 00:08:13.319
<v Speaker 2>all managed centrally work groups. On the other hand, they're

147
00:08:13.360 --> 00:08:16.639
<v Speaker 2>peer to peer. Each computer manages its own local security,

148
00:08:16.759 --> 00:08:19.600
<v Speaker 2>shares resources, no central authority.

149
00:08:19.720 --> 00:08:20.720
<v Speaker 1>Right. Much simpler, but.

150
00:08:21.160 --> 00:08:24.439
<v Speaker 2>Doesn't scale securely for any enterprise or even a growing

151
00:08:24.480 --> 00:08:28.240
<v Speaker 2>small business. A domain infrastructure is well, it's non negotiable

152
00:08:28.279 --> 00:08:30.399
<v Speaker 2>for security, manageability and scale.

153
00:08:30.639 --> 00:08:34.399
<v Speaker 1>Speaking of scale, Windows Server twenty twenty five introduces some

154
00:08:34.440 --> 00:08:40.080
<v Speaker 1>significant enhancements to ADDS focus on scalability, performance, manageability. What

155
00:08:40.120 --> 00:08:41.440
<v Speaker 1>are the headline features for us here?

156
00:08:41.480 --> 00:08:43.919
<v Speaker 2>Okay, A key one is the new domain and forced

157
00:08:44.000 --> 00:08:46.639
<v Speaker 2>functional level ten. Now this isn't just a version number bump.

158
00:08:47.080 --> 00:08:50.080
<v Speaker 2>It means ADDS and Server twenty twenty five can now

159
00:08:50.120 --> 00:08:55.279
<v Speaker 2>comfortably manage significantly larger user bases, more complex organizational structures.

160
00:08:55.759 --> 00:08:59.840
<v Speaker 2>It really pushes previous scalability limits might even delay costly

161
00:08:59.879 --> 00:09:03.840
<v Speaker 2>re designs for rapidly growing enterprises. That's big it is.

162
00:09:04.320 --> 00:09:08.000
<v Speaker 2>We're also seeing optimized replication for large scale environments using

163
00:09:08.000 --> 00:09:12.120
<v Speaker 2>advanced algorithms to reduce latency bandwidth usage, which is crucial

164
00:09:12.240 --> 00:09:15.799
<v Speaker 2>for widely distributed locations, hybrid setups.

165
00:09:15.360 --> 00:09:18.120
<v Speaker 1>And for peace of mind. What's new in backup and

166
00:09:18.159 --> 00:09:19.960
<v Speaker 1>recovery mechanisms? Anything stand out?

167
00:09:20.120 --> 00:09:23.480
<v Speaker 2>Yeah? Server twenty twenty five brings enhanced backup and recovery,

168
00:09:23.879 --> 00:09:28.919
<v Speaker 2>more efficient incremental backups, improved restoration processes. The active directory

169
00:09:28.960 --> 00:09:31.879
<v Speaker 2>recycle bin for example, it's been further refined. It preserves

170
00:09:31.879 --> 00:09:36.519
<v Speaker 2>more attributes relationships of deleted objects, making recovery easier oh useful.

171
00:09:36.759 --> 00:09:41.240
<v Speaker 2>Very Plus, leveraging the Volume Shadow Copy Service VSS ensures

172
00:09:41.279 --> 00:09:44.360
<v Speaker 2>consistent data protection for adds during backups.

173
00:09:44.480 --> 00:09:48.799
<v Speaker 1>Good stuff. Now, security paramount in today's threat landscape, obviously,

174
00:09:49.000 --> 00:09:50.799
<v Speaker 1>and when do. Server twenty twenty five seems to have

175
00:09:50.840 --> 00:09:53.799
<v Speaker 1>really stepped up its game here. What's fascinating I think

176
00:09:53.879 --> 00:09:56.440
<v Speaker 1>is the focus on advanced authentication mechanisms.

177
00:09:56.559 --> 00:10:01.080
<v Speaker 2>Yes, definitely. This includes significant enhancements to Kurber authentication, more

178
00:10:01.159 --> 00:10:05.960
<v Speaker 2>robust encryption algorithms, bolster defenses against common vulnerabilities like past

179
00:10:05.960 --> 00:10:08.600
<v Speaker 2>the ticket attack. Right, those are nasty, they are beyond that.

180
00:10:08.639 --> 00:10:12.879
<v Speaker 2>Server twenty twenty five deeply embraces multi factor authentication MFA,

181
00:10:13.200 --> 00:10:15.399
<v Speaker 2>particularly with conditional access policies.

182
00:10:15.440 --> 00:10:16.399
<v Speaker 1>Conditional access.

183
00:10:16.639 --> 00:10:20.399
<v Speaker 2>Yeah, this lets you dynamically enforce MFA based on context

184
00:10:20.720 --> 00:10:25.039
<v Speaker 2>things like resource sensitivity, the user's role, maybe even their location.

185
00:10:25.519 --> 00:10:30.159
<v Speaker 2>It aligns perfectly with zero trust principles. Verify every access

186
00:10:30.159 --> 00:10:31.559
<v Speaker 2>request basically.

187
00:10:31.320 --> 00:10:34.279
<v Speaker 1>So it's not just about stopping threats, but detecting them quickly,

188
00:10:34.519 --> 00:10:35.840
<v Speaker 1>intelligently exactly.

189
00:10:36.279 --> 00:10:40.080
<v Speaker 2>Automated threat detection is key, real time tracking of access attempts,

190
00:10:40.159 --> 00:10:45.240
<v Speaker 2>immediately flagging irregular or suspicious behavior. Microsoft Defender Anti Virus

191
00:10:45.279 --> 00:10:49.080
<v Speaker 2>for Windows Server twenty twenty five offers comprehensive protection, real

192
00:10:49.120 --> 00:10:54.080
<v Speaker 2>time defense, advanced threat detection using machine learning, automated response capabilities,

193
00:10:54.279 --> 00:10:57.080
<v Speaker 2>ensuring the integrity of your server environment against these constantly

194
00:10:57.159 --> 00:10:58.639
<v Speaker 2>evolving threats and for.

195
00:10:58.559 --> 00:11:01.159
<v Speaker 1>You, the admin on the ground. What does implementing these

196
00:11:01.159 --> 00:11:04.000
<v Speaker 1>security best practices look like day to day with Server

197
00:11:04.080 --> 00:11:04.840
<v Speaker 1>twenty twenty five.

198
00:11:05.000 --> 00:11:08.879
<v Speaker 2>Well, it means consistent patch management right often via WSUS

199
00:11:08.960 --> 00:11:12.879
<v Speaker 2>or even hot patching, which we should definitely talk more about. Crucially,

200
00:11:12.960 --> 00:11:17.519
<v Speaker 2>it involves rigorous audit logging. The system records everything user login,

201
00:11:17.679 --> 00:11:20.840
<v Speaker 2>system changes, providing that historical record you need for forensic

202
00:11:20.879 --> 00:11:22.200
<v Speaker 2>analysis if something happens.

203
00:11:22.480 --> 00:11:26.320
<v Speaker 1>Treatsability exactly. There's even a PowerShell script available to check

204
00:11:26.320 --> 00:11:30.279
<v Speaker 1>for security baseline drift, making sure your configurations stay robust

205
00:11:30.600 --> 00:11:34.679
<v Speaker 1>against new threats and comply with your established security policies. Okay,

206
00:11:34.720 --> 00:11:37.879
<v Speaker 1>let's shift gear slightly. How does server twenty twenty five

207
00:11:37.960 --> 00:11:40.759
<v Speaker 1>handle your data? Storage is always a challenge, isn't it.

208
00:11:41.000 --> 00:11:44.159
<v Speaker 1>Server twenty twenty five offers some powerful modern solutions here.

209
00:11:44.240 --> 00:11:48.279
<v Speaker 2>Oh yeah, this brings us to storage spaces direct or

210
00:11:48.440 --> 00:11:51.200
<v Speaker 2>S two D. This is a core component of software

211
00:11:51.240 --> 00:11:55.600
<v Speaker 2>defined storage SDS in Server twenty twenty five SDS. Right, so,

212
00:11:55.639 --> 00:11:58.840
<v Speaker 2>instead of relying on traditional hardware rad controllers, s to

213
00:11:58.840 --> 00:12:01.960
<v Speaker 2>two D provides fault tolerance by creating shared storage pools

214
00:12:01.960 --> 00:12:04.679
<v Speaker 2>from local disks across servers in a cluster.

215
00:12:04.639 --> 00:12:06.919
<v Speaker 1>Using local discs. Interesting it is?

216
00:12:07.000 --> 00:12:10.879
<v Speaker 2>It delivers amazing flexibility and scalability by abstracting the hardware,

217
00:12:11.120 --> 00:12:14.159
<v Speaker 2>lets you build highly available, high performance storage using standard

218
00:12:14.159 --> 00:12:17.480
<v Speaker 2>server hardware. It's a true game changer for modern data centers.

219
00:12:17.480 --> 00:12:22.360
<v Speaker 1>Honestly, virtualization another cornerstone of modern it maximizing hardware efficiency.

220
00:12:22.759 --> 00:12:24.879
<v Speaker 1>HYPERV has been around for a while, but how to

221
00:12:25.000 --> 00:12:27.919
<v Speaker 1>Server twenty twenty five enhance this capability well?

222
00:12:28.039 --> 00:12:31.039
<v Speaker 2>HYPERV and Server twenty twenty five continues to provide that

223
00:12:31.159 --> 00:12:35.840
<v Speaker 2>robust hardware level virtualization. What's important for you here are

224
00:12:35.840 --> 00:12:40.000
<v Speaker 2>the ongoing performance improvements, obviously, and the ability to configure

225
00:12:40.080 --> 00:12:44.679
<v Speaker 2>virtual switches flexibly external for physical network access, internal for

226
00:12:44.759 --> 00:12:49.559
<v Speaker 2>host only communication, private for just VMDVM chatter okay, and

227
00:12:49.639 --> 00:12:53.799
<v Speaker 2>for quick recovery VM checkpoints. Those snapshots are still invaluable

228
00:12:53.799 --> 00:12:57.759
<v Speaker 2>for easy rollbacks. What's also fascinating is the continued refinement

229
00:12:57.799 --> 00:13:01.000
<v Speaker 2>of tools like DISC to VHD makes it easier than

230
00:13:01.039 --> 00:13:04.120
<v Speaker 2>ever to convert physical servers to virtual machines p too,

231
00:13:04.159 --> 00:13:08.159
<v Speaker 2>v which is a key step in modernizing your IT infrastructure.

232
00:13:08.720 --> 00:13:10.960
<v Speaker 1>So you've got all this power and your physical servers

233
00:13:11.039 --> 00:13:14.399
<v Speaker 1>running vms. Yeah, but the challenge often becomes managing at all,

234
00:13:14.440 --> 00:13:17.159
<v Speaker 1>doesn't it, especially as your infrastructure stretches beyond your data

235
00:13:17.159 --> 00:13:21.000
<v Speaker 1>center walls. That's where Server twenty twenty five hybrid capabilities

236
00:13:21.200 --> 00:13:24.559
<v Speaker 1>powered by tools like Azure Arc become truly transformative.

237
00:13:24.600 --> 00:13:26.759
<v Speaker 2>I think you've hit on a critical point there. Azure

238
00:13:26.879 --> 00:13:30.720
<v Speaker 2>Arc essentially extends Azure's management capabilities right down to your

239
00:13:30.759 --> 00:13:32.679
<v Speaker 2>on premises and edge resource.

240
00:13:32.360 --> 00:13:34.240
<v Speaker 1>Right into your data center exactly.

241
00:13:34.320 --> 00:13:37.000
<v Speaker 2>It means you can manage your Windows server instances using

242
00:13:37.039 --> 00:13:40.399
<v Speaker 2>familiar Azure tools, Azure Portal, Azuro policy or whatever, regardless

243
00:13:40.399 --> 00:13:43.320
<v Speaker 2>of where they actually physically reside. Okay, this provides that

244
00:13:43.440 --> 00:13:47.679
<v Speaker 2>unified control plane we talked about, simplifies administration, ensure consistent

245
00:13:47.759 --> 00:13:51.679
<v Speaker 2>policy enforcement across your entire hybrid estate. It's really powerful.

246
00:13:51.840 --> 00:13:55.639
<v Speaker 1>That's a powerful claim unified management. But a crucial point

247
00:13:55.639 --> 00:13:58.919
<v Speaker 1>to consider major bain point usually is how do you

248
00:13:59.200 --> 00:14:01.840
<v Speaker 1>update critical servers without downtime?

249
00:14:01.919 --> 00:14:05.519
<v Speaker 2>Ah? Yes, that's where hot patching comes in. Specifically for

250
00:14:05.639 --> 00:14:09.440
<v Speaker 2>Windows Server twenty twenty five Azure edition, this is a

251
00:14:09.600 --> 00:14:13.120
<v Speaker 2>crucial innovation hot patching. It allows you to apply certain

252
00:14:13.159 --> 00:14:16.799
<v Speaker 2>security updates without rebooting your server. You reboot, no reboot

253
00:14:16.840 --> 00:14:22.120
<v Speaker 2>for many critical updates. This ensures operational continarity significantly reduces

254
00:14:22.159 --> 00:14:26.159
<v Speaker 2>planned downtime, a massive benefit for those critical workloads where

255
00:14:26.200 --> 00:14:29.960
<v Speaker 2>every minute of availability is essential. It's a fundamental shift

256
00:14:29.960 --> 00:14:32.639
<v Speaker 2>in update management for those high availability environments.

257
00:14:32.960 --> 00:14:36.879
<v Speaker 1>Okay, maintaining an efficient server environment means staying rigorously on

258
00:14:36.960 --> 00:14:40.759
<v Speaker 1>top of updates Beyond the OS patches handled by Windows Update,

259
00:14:41.120 --> 00:14:42.840
<v Speaker 1>what about all those third party apps?

260
00:14:43.000 --> 00:14:46.919
<v Speaker 2>Right? For centralized OS patch management, especially in larger setups,

261
00:14:47.200 --> 00:14:51.480
<v Speaker 2>Windows Server Update Services WSUS is still a vital tool

262
00:14:51.600 --> 00:14:56.159
<v Speaker 2>lets you manage distribute updates efficiently. But for third party applications,

263
00:14:56.200 --> 00:15:00.120
<v Speaker 2>thank Oracle databases, patchy web servers, things like that, you

264
00:15:00.200 --> 00:15:00.759
<v Speaker 2>might turn.

265
00:15:00.600 --> 00:15:02.159
<v Speaker 1>To wing it now wing it on server.

266
00:15:02.399 --> 00:15:05.440
<v Speaker 2>Yeah, a simple wing it upgrade all command can scan

267
00:15:05.720 --> 00:15:11.360
<v Speaker 2>download install updates for many installed applications, reinforces security stability

268
00:15:11.399 --> 00:15:14.279
<v Speaker 2>across your entire software stack, and of course don't forget

269
00:15:14.320 --> 00:15:17.240
<v Speaker 2>the strategic advantage of hot patching for those critical security

270
00:15:17.279 --> 00:15:19.279
<v Speaker 2>updates on Azure edition VMS.

271
00:15:19.039 --> 00:15:23.559
<v Speaker 1>Right now when things inevitably go wrong. Effective troubleshooting is

272
00:15:23.559 --> 00:15:27.000
<v Speaker 1>obviously an essential skill. What are the key diagnostic tools

273
00:15:27.039 --> 00:15:29.679
<v Speaker 1>and maybe approaches to master in a Server twenty twenty

274
00:15:29.720 --> 00:15:30.440
<v Speaker 1>five environment.

275
00:15:30.720 --> 00:15:33.960
<v Speaker 2>Well, you'll always want to approach problems systematically follow your process,

276
00:15:34.279 --> 00:15:37.279
<v Speaker 2>but the core tools for you include Event Viewer, of course,

277
00:15:37.399 --> 00:15:43.039
<v Speaker 2>logging critical activities, Performance Monitor, Resource Monitor, Task Manager. They

278
00:15:43.039 --> 00:15:46.679
<v Speaker 2>give you those real time insights into CPU memory, disc

279
00:15:47.279 --> 00:15:52.879
<v Speaker 2>network usage, helping you pinpoint bottlenecks ideally proactively. And Server

280
00:15:52.960 --> 00:15:56.120
<v Speaker 2>twenty twenty five also integrates tightly with Azure Monitor when

281
00:15:56.159 --> 00:15:59.600
<v Speaker 2>it's ARC enabled, extending your diagnostic capabilities right into the

282
00:15:59.600 --> 00:16:02.759
<v Speaker 2>cloud for a unified view across hybrid resources.

283
00:16:02.960 --> 00:16:06.399
<v Speaker 1>Beyond just fixing immediate problems, the big picture is business

284
00:16:06.440 --> 00:16:09.840
<v Speaker 1>continuity and disaster recovery. Yeah, what's the server twenty twenty

285
00:16:09.840 --> 00:16:12.840
<v Speaker 1>five perspective on keeping everything running smoothly? Come what may?

286
00:16:13.080 --> 00:16:17.120
<v Speaker 2>Absolutely? A disaster recovery plan a DRP is that detailed

287
00:16:17.120 --> 00:16:20.840
<v Speaker 2>document outlining how you resume operations after a significant disruption.

288
00:16:21.039 --> 00:16:21.679
<v Speaker 1>Right the plan?

289
00:16:21.840 --> 00:16:25.480
<v Speaker 2>Yeah, it includes inventoring assets, assessing risks, defining your recovery

290
00:16:25.480 --> 00:16:28.840
<v Speaker 2>time objectives rtos, and recover point objectives RPOs. Essentially how

291
00:16:28.919 --> 00:16:31.240
<v Speaker 2>much downtime and data loss your business can tolerate.

292
00:16:31.279 --> 00:16:32.080
<v Speaker 1>Crucial numbers.

293
00:16:32.200 --> 00:16:37.960
<v Speaker 2>Crucial numbers. Business continuity BC focuses on maintaining essential operations

294
00:16:38.039 --> 00:16:41.879
<v Speaker 2>during a disruption, while dr focuses on restoring systems after one.

295
00:16:42.000 --> 00:16:43.639
<v Speaker 2>They really work hand in hand.

296
00:16:43.720 --> 00:16:46.120
<v Speaker 1>And what are the key strategies for BC and DR

297
00:16:46.240 --> 00:16:49.519
<v Speaker 1>in this modern server landscape? Maybe using server twenty twenty

298
00:16:49.519 --> 00:16:50.159
<v Speaker 1>five features.

299
00:16:50.480 --> 00:16:54.200
<v Speaker 2>Key strategies include robust data redundancy. Obviously, multiple copies of

300
00:16:54.240 --> 00:16:58.240
<v Speaker 2>data in different locations. Clustering is still huge. Using multiple

301
00:16:58.279 --> 00:17:02.080
<v Speaker 2>servers for continuous service through failover one takes over, one

302
00:17:02.080 --> 00:17:05.319
<v Speaker 2>takes over if another fails, or load balancing sharing the workload.

303
00:17:05.839 --> 00:17:09.400
<v Speaker 2>Robust backups are foundational using tools like Windows Server Backup

304
00:17:09.759 --> 00:17:14.359
<v Speaker 2>and importantly, knowing your Directory Services Restore Mode DSRM password

305
00:17:14.359 --> 00:17:16.440
<v Speaker 2>for active directory restores is critical.

306
00:17:16.480 --> 00:17:17.359
<v Speaker 1>Don't forget that password.

307
00:17:17.400 --> 00:17:20.720
<v Speaker 2>We'll never forget that password, and you know. Server twenty

308
00:17:20.759 --> 00:17:24.880
<v Speaker 2>twenty five's enhancements to features like storage spaces direct also

309
00:17:24.960 --> 00:17:28.440
<v Speaker 2>provide inherent fault tolerance for your data storage layer itself.

310
00:17:29.519 --> 00:17:33.039
<v Speaker 2>Now just switching gears slightly for anyone serious about a

311
00:17:33.079 --> 00:17:37.079
<v Speaker 2>career in it. The value of Microsoft Role based certifications,

312
00:17:37.079 --> 00:17:39.759
<v Speaker 2>while it really can't be overstated ken it. They validate

313
00:17:39.799 --> 00:17:43.279
<v Speaker 2>your expertise in modern tech, provide a competitive edge, helps

314
00:17:43.279 --> 00:17:43.839
<v Speaker 2>you stand out.

315
00:17:43.920 --> 00:17:46.599
<v Speaker 1>Yeah, definitely. Take the eighty eight hundred exam for instance.

316
00:17:47.000 --> 00:17:50.200
<v Speaker 1>It measures your skills in deploying and managing adds both

317
00:17:50.200 --> 00:17:53.480
<v Speaker 1>on prem and in the cloud, managing VMS and containers,

318
00:17:53.720 --> 00:17:57.680
<v Speaker 1>implementing hybrid networking, handling storage and file services. It's a

319
00:17:57.720 --> 00:18:01.400
<v Speaker 1>comprehensive benchmark for a Windows server, pro ensuring you cover

320
00:18:01.480 --> 00:18:04.799
<v Speaker 1>critical modern skills, aligning perfectly with pretty much everything we've

321
00:18:04.799 --> 00:18:06.039
<v Speaker 1>discussed today exactly.

322
00:18:06.079 --> 00:18:09.839
<v Speaker 2>And Microsoft has also implemented revised validity periods and renewal

323
00:18:09.839 --> 00:18:12.680
<v Speaker 2>processes for these certifications. You can renew them at no

324
00:18:12.799 --> 00:18:15.720
<v Speaker 2>cost now through Microsoft Learn. It is it ensures your

325
00:18:15.720 --> 00:18:20.200
<v Speaker 2>skills stay current and competitive in this rapidly evolving landscape

326
00:18:20.519 --> 00:18:24.400
<v Speaker 2>without the pain and cost of recertifying from scratch every

327
00:18:24.400 --> 00:18:25.079
<v Speaker 2>couple of years.

328
00:18:25.400 --> 00:18:27.599
<v Speaker 1>So wrapping this up, then, what does this all mean

329
00:18:27.640 --> 00:18:30.359
<v Speaker 1>for you the listener? Yeah, we've taken it well. A

330
00:18:30.400 --> 00:18:33.720
<v Speaker 1>pretty deep dive into Windows Server twenty twenty five explored

331
00:18:33.720 --> 00:18:39.400
<v Speaker 1>its foundations, cutting edge security, modern storage, virtualization, those crucial

332
00:18:39.480 --> 00:18:43.240
<v Speaker 1>hybrid cloud integrations. It's clear this isn't just another server

333
00:18:43.400 --> 00:18:47.799
<v Speaker 1>OS update. It feels like a strategic platform for building resilient, secure,

334
00:18:48.160 --> 00:18:52.960
<v Speaker 1>scalable IT environments really designed for today's complex and distributed world.

335
00:18:53.039 --> 00:18:56.240
<v Speaker 2>I think the overarching themes for you are seamless integration

336
00:18:56.599 --> 00:19:01.000
<v Speaker 2>really blending on premises with cloud services, enhanced proactive security

337
00:19:01.000 --> 00:19:04.599
<v Speaker 2>through things like advanced authentication and intelligent threat detection, and

338
00:19:05.000 --> 00:19:08.559
<v Speaker 2>a significant leap in operational efficiency driven by innovations like

339
00:19:08.599 --> 00:19:11.920
<v Speaker 2>hot patching and software defined storage. These really feel like

340
00:19:11.960 --> 00:19:14.279
<v Speaker 2>the pillars of modern IT infrastructure management.

341
00:19:14.599 --> 00:19:18.319
<v Speaker 1>So here's a final thought. As IT environments become inevitably

342
00:19:18.400 --> 00:19:23.000
<v Speaker 1>more distributed, more complex, how will mastering platforms like Windows

343
00:19:23.000 --> 00:19:26.720
<v Speaker 1>Server twenty twenty five reshape the role of the system administrator,

344
00:19:27.559 --> 00:19:30.599
<v Speaker 1>moving perhaps from a reactive troubleshooter to more of a

345
00:19:30.640 --> 00:19:34.799
<v Speaker 1>proactive architect of resilient digital infrastructure. Something for you to mull.

346
00:19:34.640 --> 00:19:36.279
<v Speaker 2>Over, definitely something to think about.

347
00:19:36.319 --> 00:19:38.359
<v Speaker 1>We hope this deep dive has given you plenty to

348
00:19:38.400 --> 00:19:41.200
<v Speaker 1>consider and maybe a clearer path forward for your own

349
00:19:41.240 --> 00:19:41.960
<v Speaker 1>learning journey.