WEBVTT

1
00:00:00.040 --> 00:00:03.799
<v Speaker 1>Okay, let's unpack this. You know that moment you log

2
00:00:03.839 --> 00:00:08.359
<v Speaker 1>into a new computer or maybe a virtual desktop, and

3
00:00:08.400 --> 00:00:12.199
<v Speaker 1>that sinking feeling hits. Oh yeah, all your personalized settings,

4
00:00:12.519 --> 00:00:16.879
<v Speaker 1>your desktop shortcuts, your app configurations just gone, like your

5
00:00:16.879 --> 00:00:21.160
<v Speaker 1>digital identity completely vanished, totally evaporates. Today we're diving deep

6
00:00:21.199 --> 00:00:24.280
<v Speaker 1>into the magic behind making sure your digital workspace actually

7
00:00:24.280 --> 00:00:26.879
<v Speaker 1>adapts to you no matter where or how you log in.

8
00:00:27.399 --> 00:00:31.920
<v Speaker 1>We're talking about delivering a consistent, personalized and seamless user

9
00:00:31.960 --> 00:00:35.200
<v Speaker 1>experience even in really complex IT setups.

10
00:00:35.240 --> 00:00:37.759
<v Speaker 2>And what's truly fascinating if you think about it, is

11
00:00:37.759 --> 00:00:41.000
<v Speaker 2>how historically managing these user profiles, it's been such a

12
00:00:41.000 --> 00:00:45.560
<v Speaker 2>persistent headache for it, leading to slow logins and let's

13
00:00:45.600 --> 00:00:49.200
<v Speaker 2>be honest, really frustrated users definitely. But solutions like VMware

14
00:00:49.240 --> 00:00:53.479
<v Speaker 2>Dynamic Environment Manager DEM, they're fundamentally changing that whole landscape.

15
00:00:53.560 --> 00:00:57.880
<v Speaker 2>They let it deliver a truly just in time personalized desktop.

16
00:00:57.960 --> 00:01:01.000
<v Speaker 1>And that's exactly our mission today, right to explore User

17
00:01:01.079 --> 00:01:03.960
<v Speaker 1>Environment Management UEM, specifically through DEM.

18
00:01:03.880 --> 00:01:07.319
<v Speaker 2>YEP, trace the evolution of user profiles and really uncover

19
00:01:07.439 --> 00:01:11.519
<v Speaker 2>how this tool streamlines things for admins while making the

20
00:01:11.560 --> 00:01:13.719
<v Speaker 2>experience much better for you, the end user.

21
00:01:14.120 --> 00:01:17.319
<v Speaker 1>Okay, so to really appreciate what DEM does, we probably

22
00:01:17.319 --> 00:01:20.959
<v Speaker 1>need to rewind a bit. Before these modern tools, managing

23
00:01:20.959 --> 00:01:23.480
<v Speaker 1>your digital identity was well a lot more basic.

24
00:01:23.560 --> 00:01:24.439
<v Speaker 2>Oh absolutely.

25
00:01:24.519 --> 00:01:27.120
<v Speaker 1>Can you walk us through how user profiles first really

26
00:01:27.159 --> 00:01:30.000
<v Speaker 1>took shape? Maybe starting with Windows NT.

27
00:01:30.439 --> 00:01:33.599
<v Speaker 2>Sure? Yeah, Back then, your digital footprint on a machine

28
00:01:33.599 --> 00:01:37.439
<v Speaker 2>was pretty limited. Early program stuff was hard to reproduce consistently.

29
00:01:38.000 --> 00:01:40.560
<v Speaker 2>But Windows NT that's where we really saw the birth

30
00:01:40.680 --> 00:01:43.799
<v Speaker 2>of proper user profiles, and it all centered around that

31
00:01:44.000 --> 00:01:45.079
<v Speaker 2>end user dot.

32
00:01:44.959 --> 00:01:48.920
<v Speaker 1>Dat filet user dot dat. I remember that exactly.

33
00:01:48.959 --> 00:01:53.040
<v Speaker 2>It stored all those critical settings, configurations, preferences, everything specific

34
00:01:53.040 --> 00:01:53.599
<v Speaker 2>to your login.

35
00:01:53.719 --> 00:01:56.480
<v Speaker 1>So that single file was basically the heart of your

36
00:01:56.480 --> 00:01:59.280
<v Speaker 1>personalized world on that machine. If it got deleted or corrupted,

37
00:01:59.480 --> 00:02:00.560
<v Speaker 1>puff poof is.

38
00:02:00.599 --> 00:02:03.760
<v Speaker 2>Right back to square one. It's essentially a log file

39
00:02:03.799 --> 00:02:06.840
<v Speaker 2>of all your user specific changes. Delete it and everything

40
00:02:06.879 --> 00:02:10.599
<v Speaker 2>resets to default. It really shows how deep profile management

41
00:02:10.639 --> 00:02:13.840
<v Speaker 2>goes in Windows. And building on that, we then saw

42
00:02:14.080 --> 00:02:16.919
<v Speaker 2>different types of profiles pop up, each trying to follow

43
00:02:16.960 --> 00:02:20.280
<v Speaker 2>a problem, but each with its own set of issues.

44
00:02:20.439 --> 00:02:23.159
<v Speaker 1>And the first simplest ones were just local profiles. Weren't

45
00:02:23.159 --> 00:02:25.599
<v Speaker 1>they your settings? Lived right there and the machine.

46
00:02:25.240 --> 00:02:26.879
<v Speaker 2>You used yep, straightforward.

47
00:02:27.000 --> 00:02:29.599
<v Speaker 1>Great if you only ever use one PC, But if

48
00:02:29.639 --> 00:02:30.879
<v Speaker 1>you move to a different.

49
00:02:30.599 --> 00:02:33.719
<v Speaker 2>Desk, none of your settings followed you. You started completely

50
00:02:33.719 --> 00:02:35.400
<v Speaker 2>from scratch every single time.

51
00:02:35.439 --> 00:02:37.840
<v Speaker 1>A nightmare for anyone who wasn't chained to one desk.

52
00:02:37.919 --> 00:02:41.199
<v Speaker 2>It absolutely was, and that frustration directly led to the

53
00:02:41.240 --> 00:02:42.800
<v Speaker 2>idea of roaming profiles.

54
00:02:42.879 --> 00:02:45.000
<v Speaker 1>Okay, so trying to make the profile roam with the.

55
00:02:45.080 --> 00:02:49.919
<v Speaker 2>User exactly a significant step. Conceptually, your profile was stored

56
00:02:50.039 --> 00:02:53.400
<v Speaker 2>centrally on a server somewhere. It got copied down to

57
00:02:53.439 --> 00:02:55.800
<v Speaker 2>the local machine when you logged in, and then synced

58
00:02:55.840 --> 00:02:58.719
<v Speaker 2>back up when you logged off. The idea was well

59
00:02:58.879 --> 00:02:59.800
<v Speaker 2>brilliant on paper.

60
00:03:00.560 --> 00:03:03.000
<v Speaker 1>I'm sensing a butt here. I can almost hear the

61
00:03:03.039 --> 00:03:06.039
<v Speaker 1>network traffic groaning. Slow logins.

62
00:03:06.400 --> 00:03:09.199
<v Speaker 2>You are absolutely right connect that to the bigger picture. Yes,

63
00:03:09.240 --> 00:03:14.479
<v Speaker 2>they offered portability, but roaming profiles became notorious for slow

64
00:03:14.639 --> 00:03:17.680
<v Speaker 2>logins and logofs.

65
00:03:16.680 --> 00:03:20.080
<v Speaker 1>Just copying huge files back and forth pretty much, especially

66
00:03:20.120 --> 00:03:22.919
<v Speaker 1>as profiles grew and they were often tied.

67
00:03:22.639 --> 00:03:26.800
<v Speaker 2>To specific OS versions, making upgrades of pain. Plus they

68
00:03:26.800 --> 00:03:28.199
<v Speaker 2>were prone to corruption.

69
00:03:28.080 --> 00:03:31.800
<v Speaker 1>Ah, the dreaded profile corruption, often leading to a full

70
00:03:31.840 --> 00:03:32.840
<v Speaker 1>reset right now cutently.

71
00:03:33.039 --> 00:03:35.240
<v Speaker 2>So yeah, it was a step forward, but a pretty

72
00:03:35.319 --> 00:03:36.000
<v Speaker 2>clunky one.

73
00:03:36.039 --> 00:03:39.960
<v Speaker 1>And then there were mandatory profiles, which sound restrictive.

74
00:03:40.120 --> 00:03:43.240
<v Speaker 2>They were admins defined them read only any changes you

75
00:03:43.319 --> 00:03:46.199
<v Speaker 2>made gone when you logged off. Great for control like

76
00:03:46.240 --> 00:03:49.840
<v Speaker 2>for kioks or specific security needs. Okay, they even had regions.

77
00:03:50.199 --> 00:03:52.520
<v Speaker 2>Normal mandatory let you use a cashed copy if the

78
00:03:52.560 --> 00:03:55.719
<v Speaker 2>server was offline. Super mandatory wouldn't even let you log in.

79
00:03:55.919 --> 00:03:59.159
<v Speaker 1>So control over personalization seems like all these early types

80
00:03:59.199 --> 00:04:00.960
<v Speaker 1>involved some kind of tref Definitely.

81
00:04:01.120 --> 00:04:03.159
<v Speaker 2>They were all trying to fit, like you said, a

82
00:04:03.199 --> 00:04:07.319
<v Speaker 2>square peg into the round hole of increasingly dynamic IT environments.

83
00:04:07.680 --> 00:04:11.759
<v Speaker 1>So with all those historical hurdles and compromises, what does

84
00:04:11.800 --> 00:04:16.680
<v Speaker 1>this mean for today for our dynamic, often virtualized desktops.

85
00:04:17.160 --> 00:04:19.040
<v Speaker 1>How do we escape those limitations?

86
00:04:19.160 --> 00:04:22.639
<v Speaker 2>Well, this is exactly where User Environment Management, and specifically

87
00:04:22.720 --> 00:04:26.560
<v Speaker 2>VMware Dynamic Environment Manager DEM, really enters the scene and

88
00:04:26.639 --> 00:04:27.240
<v Speaker 2>changes the game.

89
00:04:27.319 --> 00:04:27.639
<v Speaker 1>Okay.

90
00:04:28.000 --> 00:04:32.240
<v Speaker 2>What DEM does fundamentally is it abstracts your user specific settings,

91
00:04:32.600 --> 00:04:36.160
<v Speaker 2>you know, application settings, OS, preferences, your data, pulls them

92
00:04:36.160 --> 00:04:38.560
<v Speaker 2>away from the underlying operating system itself.

93
00:04:38.600 --> 00:04:40.000
<v Speaker 1>It separates them out precisely.

94
00:04:40.120 --> 00:04:44.079
<v Speaker 2>Yeah, this user personality is then delivered on demand. Just

95
00:04:44.120 --> 00:04:46.399
<v Speaker 2>in time is the term often used right as you

96
00:04:46.439 --> 00:04:46.959
<v Speaker 2>log in.

97
00:04:46.959 --> 00:04:50.920
<v Speaker 1>So it's like your personalized identity is assembled instantly every time,

98
00:04:51.040 --> 00:04:52.240
<v Speaker 1>even on a fresh machine.

99
00:04:52.279 --> 00:04:54.279
<v Speaker 2>That's the core idea. It makes it happen.

100
00:04:54.399 --> 00:04:59.480
<v Speaker 1>That sounds incredibly powerful. It can deploy standard clean desktops.

101
00:04:59.680 --> 00:05:02.600
<v Speaker 1>You the users, still get your familiar setup. That must

102
00:05:02.639 --> 00:05:04.399
<v Speaker 1>simplify things hugely for IT.

103
00:05:04.600 --> 00:05:08.399
<v Speaker 2>Admins immensely for IT. It means centralized management. It means

104
00:05:08.439 --> 00:05:11.600
<v Speaker 2>reduced infrastructure costs because you can use those stateless virtual

105
00:05:11.639 --> 00:05:13.279
<v Speaker 2>desktops h.

106
00:05:13.000 --> 00:05:15.319
<v Speaker 1>Because the personality isn't tied to the machine.

107
00:05:15.000 --> 00:05:19.680
<v Speaker 2>State exactly, simplified deployment, incredibly granular control over what gets

108
00:05:19.720 --> 00:05:22.920
<v Speaker 2>delivered and when, and for you the end user, a

109
00:05:23.000 --> 00:05:29.319
<v Speaker 2>consistent personalized experience any device, physical, virtual cloud, and.

110
00:05:29.279 --> 00:05:34.240
<v Speaker 1>Fast logins, presumably without copying huge roaming profiles.

111
00:05:33.759 --> 00:05:36.839
<v Speaker 2>Fast logins, fast log offs, your setting's actually roam with you,

112
00:05:37.040 --> 00:05:39.360
<v Speaker 2>but without all those traditional headaches we just talked about.

113
00:05:39.600 --> 00:05:41.480
<v Speaker 2>It's consistency without compromise.

114
00:05:41.920 --> 00:05:44.680
<v Speaker 1>That's a compelling vision, but it brings up a really

115
00:05:44.759 --> 00:05:48.199
<v Speaker 1>key question for it. How do you actually guarantee that

116
00:05:48.279 --> 00:05:52.839
<v Speaker 1>consistent personal experience in say a VDI environment where desktops

117
00:05:52.839 --> 00:05:55.360
<v Speaker 1>are built and torn down constantly.

118
00:05:55.000 --> 00:05:58.160
<v Speaker 2>Right, and DEM provides that critical missing piece. It enables

119
00:05:58.199 --> 00:06:01.560
<v Speaker 2>what's often called the composite desktop model. It's built on layers, layers.

120
00:06:01.600 --> 00:06:02.399
<v Speaker 1>Okay, so what are they?

121
00:06:02.439 --> 00:06:05.759
<v Speaker 2>Three distinct layers working together. First the OS layer, that's

122
00:06:05.759 --> 00:06:08.360
<v Speaker 2>your optimized operating system, maybe some core apps everyone needs.

123
00:06:08.360 --> 00:06:09.639
<v Speaker 2>It's like a clean base.

124
00:06:09.519 --> 00:06:11.120
<v Speaker 1>Image, got it, the foundation.

125
00:06:11.279 --> 00:06:14.600
<v Speaker 2>Then you have the applications layer, apps delivered on demand,

126
00:06:14.759 --> 00:06:18.879
<v Speaker 2>maybe through layering tech like app volumes or virtualization added

127
00:06:18.920 --> 00:06:19.439
<v Speaker 2>as needed.

128
00:06:19.600 --> 00:06:21.639
<v Speaker 1>Okay, OS, then apps.

129
00:06:21.519 --> 00:06:25.639
<v Speaker 2>And finally layer three where DEM really does its work,

130
00:06:26.000 --> 00:06:29.759
<v Speaker 2>the user profile layer. This is your abstracted on demand

131
00:06:29.920 --> 00:06:30.879
<v Speaker 2>settings and data.

132
00:06:31.000 --> 00:06:32.360
<v Speaker 1>The user personality layer.

133
00:06:32.519 --> 00:06:36.079
<v Speaker 2>Exactly. It's the magic that makes that generic base OS

134
00:06:36.120 --> 00:06:39.480
<v Speaker 2>and those added apps suddenly feel like your desktop instantly.

135
00:06:39.720 --> 00:06:42.199
<v Speaker 2>It brings your personality to the digital space.

136
00:06:42.319 --> 00:06:45.040
<v Speaker 1>Okay, so how does DEM actually make this happen? What

137
00:06:45.079 --> 00:06:47.600
<v Speaker 1>are the nuts and bolts, the core components.

138
00:06:47.720 --> 00:06:50.480
<v Speaker 2>It boils down to a few key building blocks. First,

139
00:06:50.560 --> 00:06:53.279
<v Speaker 2>there's the flex engine. Think of it as the agent.

140
00:06:53.399 --> 00:06:55.399
<v Speaker 1>The agent so it runs on the user's machine.

141
00:06:55.439 --> 00:06:59.120
<v Speaker 2>Correct, It's a lightweight agent installed on every desktop, physical

142
00:06:59.240 --> 00:07:02.079
<v Speaker 2>or virtual. That dem manages. It's the part that actually

143
00:07:02.120 --> 00:07:05.600
<v Speaker 2>applies the policies and delivers the settings it has configured

144
00:07:05.680 --> 00:07:07.439
<v Speaker 2>the worker be basically.

145
00:07:07.040 --> 00:07:09.720
<v Speaker 1>Okay, flex engine on the endpoint. And for IP to

146
00:07:09.800 --> 00:07:12.439
<v Speaker 1>manage all this, there must be a central control panel,

147
00:07:13.199 --> 00:07:14.199
<v Speaker 1>the management console.

148
00:07:14.480 --> 00:07:17.600
<v Speaker 2>That's right. The management console is the main interface for

149
00:07:17.639 --> 00:07:20.839
<v Speaker 2>IT admins. That's where they configure all the personalization, the

150
00:07:20.879 --> 00:07:22.240
<v Speaker 2>application settings, everything.

151
00:07:22.360 --> 00:07:25.079
<v Speaker 1>And it's flexible, like multiple admins can use it.

152
00:07:25.240 --> 00:07:27.920
<v Speaker 2>Yeah, it can be installed on multiple admin machines, so

153
00:07:28.160 --> 00:07:32.000
<v Speaker 2>different team members can manage the environment. Avoids bottlemes.

154
00:07:32.240 --> 00:07:35.720
<v Speaker 1>Okay, so flex Engine on the user side, management console

155
00:07:35.759 --> 00:07:39.399
<v Speaker 1>for it. But where do all these settings, the configurations,

156
00:07:39.439 --> 00:07:43.199
<v Speaker 1>the user's actual data, where does it all live?

157
00:07:43.759 --> 00:07:47.120
<v Speaker 2>Good question. Critical to the whole thing are two central

158
00:07:47.240 --> 00:07:50.279
<v Speaker 2>shared folders, usually on a file server. The first is

159
00:07:50.319 --> 00:07:51.319
<v Speaker 2>the Configuration Share.

160
00:07:51.439 --> 00:07:52.319
<v Speaker 1>Configuration Share.

161
00:07:52.439 --> 00:07:55.040
<v Speaker 2>This is where it stores all the blueprints for your workspace.

162
00:07:55.120 --> 00:07:56.879
<v Speaker 2>We call them flex configuration files.

163
00:07:56.920 --> 00:08:00.519
<v Speaker 1>Blueprints like instruction manuals for apps kind of.

164
00:08:00.720 --> 00:08:03.759
<v Speaker 2>Each one tells them how a specific application or Windows

165
00:08:03.759 --> 00:08:07.199
<v Speaker 2>setting should behave for you. Users just need read access here.

166
00:08:07.319 --> 00:08:10.800
<v Speaker 2>Admin's need full control needs about a gigabyte minimum usually.

167
00:08:10.879 --> 00:08:13.519
<v Speaker 1>Okay, so that's the instructions and the second share, the

168
00:08:13.560 --> 00:08:16.279
<v Speaker 1>profile archive share. That sounds like where my personal stuff goes.

169
00:08:16.480 --> 00:08:21.240
<v Speaker 2>Precisely, This is where your individual customizations, your settings changes

170
00:08:21.360 --> 00:08:24.360
<v Speaker 2>are kept, usually as zip files.

171
00:08:24.920 --> 00:08:25.639
<v Speaker 1>Zip files.

172
00:08:26.000 --> 00:08:28.920
<v Speaker 2>Interesting, Yeah, flex engine reads from here. When you log

173
00:08:28.959 --> 00:08:31.480
<v Speaker 2>in or launch an app, pulls down your settings than

174
00:08:31.639 --> 00:08:33.720
<v Speaker 2>any changes you make get written back here when you

175
00:08:33.759 --> 00:08:35.480
<v Speaker 2>log off or close the app.

176
00:08:35.600 --> 00:08:38.440
<v Speaker 1>And permissions here. Users need to write back right yep.

177
00:08:38.559 --> 00:08:42.679
<v Speaker 2>Users need create folders and a pen data admins need

178
00:08:42.759 --> 00:08:45.960
<v Speaker 2>full control. You should plan for at least one hundred

179
00:08:46.039 --> 00:08:50.080
<v Speaker 2>milibi per user. Here roughly stores unique user data.

180
00:08:50.360 --> 00:08:52.279
<v Speaker 1>Got it? And I think you mentioned a couple of

181
00:08:52.279 --> 00:08:53.879
<v Speaker 1>other tools for specific jobs.

182
00:08:54.120 --> 00:08:57.559
<v Speaker 2>Yes, there's the Application profiler tool. It uses this to

183
00:08:57.559 --> 00:09:01.159
<v Speaker 2>create those flex configuration files. It captures and apps registry settings,

184
00:09:01.200 --> 00:09:05.080
<v Speaker 2>filesystem stuff. Basically, reverse engineer is how an app stores its.

185
00:09:04.840 --> 00:09:07.440
<v Speaker 1>Setting ah okay to build the blueprints exactly.

186
00:09:07.519 --> 00:09:10.000
<v Speaker 2>And then there's the demsync tool. This is handy for

187
00:09:10.159 --> 00:09:12.720
<v Speaker 2>users who might be remote, maybe with body internet or

188
00:09:12.879 --> 00:09:13.559
<v Speaker 2>work offline.

189
00:09:13.559 --> 00:09:15.759
<v Speaker 1>A lot for offline scenarios, right.

190
00:09:15.799 --> 00:09:18.240
<v Speaker 2>It lets them manage their profile settings locally, then sync

191
00:09:18.279 --> 00:09:19.600
<v Speaker 2>everything up when they reconnect.

192
00:09:20.000 --> 00:09:25.200
<v Speaker 1>Makes sense now, deploying this across an organization. How does

193
00:09:25.240 --> 00:09:30.120
<v Speaker 1>it actually plug DEM into everything? Does it need active directory?

194
00:09:30.200 --> 00:09:32.919
<v Speaker 2>It often uses it. The traditional way is via active

195
00:09:32.919 --> 00:09:37.120
<v Speaker 2>directory Group Policy AD GPO. DEM comes with its own

196
00:09:37.159 --> 00:09:38.679
<v Speaker 2>ADMX templates you load.

197
00:09:38.519 --> 00:09:40.399
<v Speaker 1>In so standard GPO management.

198
00:09:40.960 --> 00:09:43.960
<v Speaker 2>But there's also no AD mode. This is great for

199
00:09:44.279 --> 00:09:47.559
<v Speaker 2>environments without AD which you see sometimes with cloud desktops

200
00:09:47.639 --> 00:09:48.799
<v Speaker 2>or specific setups.

201
00:09:49.159 --> 00:09:50.720
<v Speaker 1>No AD how does that work?

202
00:09:50.759 --> 00:09:54.600
<v Speaker 2>Then it uses a noad dot xml file for configuration instead,

203
00:09:54.879 --> 00:09:58.360
<v Speaker 2>bypasses GPOs login scripts entirely. You just have to make

204
00:09:58.360 --> 00:10:00.480
<v Speaker 2>sure the flex engine agent is installed and no AD

205
00:10:00.519 --> 00:10:02.120
<v Speaker 2>mode offers good flexibility.

206
00:10:02.200 --> 00:10:04.639
<v Speaker 1>That flexibility is good, but it does raise a big question,

207
00:10:04.679 --> 00:10:07.200
<v Speaker 1>especially for larger companies, how do you make sure these

208
00:10:07.240 --> 00:10:10.480
<v Speaker 1>profiles are always available consistent across different sites. What if

209
00:10:10.480 --> 00:10:11.559
<v Speaker 1>a file server goes down.

210
00:10:11.679 --> 00:10:15.840
<v Speaker 2>Reliability is key, absolutely critical point, and DEM's architecture is

211
00:10:15.879 --> 00:10:19.240
<v Speaker 2>designed with this in mind. It supports multiple configuration shares,

212
00:10:19.320 --> 00:10:21.440
<v Speaker 2>multiple profile archive shares, so you can.

213
00:10:21.360 --> 00:10:24.320
<v Speaker 1>Have different ones for different locations or departments exactly.

214
00:10:24.399 --> 00:10:27.159
<v Speaker 2>And then you use replication. That's the key. Maybe software

215
00:10:27.159 --> 00:10:31.559
<v Speaker 2>replication like DFSN for the configuration files, or hardware sand

216
00:10:31.759 --> 00:10:33.840
<v Speaker 2>replication for the user profile data.

217
00:10:34.000 --> 00:10:36.600
<v Speaker 1>Ah so standard high availability techniques right.

218
00:10:36.960 --> 00:10:41.320
<v Speaker 2>That ensures scalability, high availability and lets users roams seamlessly

219
00:10:41.360 --> 00:10:44.759
<v Speaker 2>between sites. Your profile's there even if one server has

220
00:10:44.799 --> 00:10:47.840
<v Speaker 2>an issue business continuity okay, And.

221
00:10:47.799 --> 00:10:50.080
<v Speaker 1>What about the management console server itself? The one it

222
00:10:50.480 --> 00:10:52.799
<v Speaker 1>uses is that a single point of failure.

223
00:10:53.279 --> 00:10:55.799
<v Speaker 2>No, not really. If a management server fails, you can

224
00:10:55.840 --> 00:10:57.840
<v Speaker 2>just reinstall it quickly and point it back to those

225
00:10:57.879 --> 00:11:01.679
<v Speaker 2>replicated shares. All the critical and FIG and user data

226
00:11:01.799 --> 00:11:05.320
<v Speaker 2>lives on those shares, safe and sound. The system's pretty resilient.

227
00:11:05.360 --> 00:11:09.159
<v Speaker 1>Okay. Understanding the pieces is one thing, but the real power,

228
00:11:09.200 --> 00:11:12.519
<v Speaker 1>what it gets creative is on the configuration, right, putting

229
00:11:12.559 --> 00:11:14.759
<v Speaker 1>it all together to shape that dynamic environment.

230
00:11:14.879 --> 00:11:19.399
<v Speaker 2>Absolutely. The initial setup is pretty standard GPO stuff copy

231
00:11:19.480 --> 00:11:23.240
<v Speaker 2>the ADMX ADML templates, create a link of GPO. Then

232
00:11:23.399 --> 00:11:26.519
<v Speaker 2>in that GPO you set the core paths, can fig

233
00:11:26.559 --> 00:11:30.000
<v Speaker 2>share profile, archive, share where backups go, log file locations,

234
00:11:30.399 --> 00:11:33.320
<v Speaker 2>and you enable the Flex Engine, logan and log off scripts.

235
00:11:33.559 --> 00:11:36.039
<v Speaker 1>The flex engine, dot ex e I R and a

236
00:11:36.120 --> 00:11:37.399
<v Speaker 1>less commands.

237
00:11:36.919 --> 00:11:39.879
<v Speaker 2>Exactly coe er for refreshed logan, a lag us for

238
00:11:39.960 --> 00:11:43.279
<v Speaker 2>stable golf. And the first time you launched a management console,

239
00:11:43.320 --> 00:11:47.279
<v Speaker 2>it asks you about enabling personalization, maybe extra features like

240
00:11:47.320 --> 00:11:50.919
<v Speaker 2>app V support. It's about getting the basic plumbing in place.

241
00:11:51.159 --> 00:11:54.360
<v Speaker 1>So beyond that initial setup, where does the really fine

242
00:11:54.399 --> 00:11:57.440
<v Speaker 1>grained control come in tailoring the experience.

243
00:11:57.600 --> 00:12:01.559
<v Speaker 2>That's where dem gets really powerful with advance personalization. The

244
00:12:01.559 --> 00:12:02.679
<v Speaker 2>core of it is the flex.

245
00:12:02.840 --> 00:12:05.200
<v Speaker 1>Now, the thing that sounds really cool for the user

246
00:12:05.240 --> 00:12:08.720
<v Speaker 1>experience is directflex. Can you explain that again? How does

247
00:12:08.759 --> 00:12:09.960
<v Speaker 1>it speed things up so much?

248
00:12:10.039 --> 00:12:13.600
<v Speaker 2>Right? Directflex it's a massive optimization. Instead of loading all

249
00:12:13.639 --> 00:12:15.559
<v Speaker 2>the settings for all your applications when.

250
00:12:15.440 --> 00:12:17.399
<v Speaker 1>You log in, which could take ages.

251
00:12:17.240 --> 00:12:21.240
<v Speaker 2>Exactly, directflex only processes and applications settings when you actually

252
00:12:21.320 --> 00:12:23.159
<v Speaker 2>launch that specific application.

253
00:12:23.399 --> 00:12:25.840
<v Speaker 1>Ah, just in time for apps too, not just.

254
00:12:25.879 --> 00:12:29.919
<v Speaker 2>Log in precisely. It makes logins way faster because it's

255
00:12:30.200 --> 00:12:33.039
<v Speaker 2>not doing all that work up front. It delivers just

256
00:12:33.120 --> 00:12:36.519
<v Speaker 2>what's needed right when it's needed. Big performance boost makes

257
00:12:36.519 --> 00:12:39.480
<v Speaker 2>total sense. Plus you can set up robust backups for

258
00:12:39.519 --> 00:12:44.600
<v Speaker 2>the profile archives, define specific conditions based on OSIP range

259
00:12:44.679 --> 00:12:47.720
<v Speaker 2>ad group, even time of day for when certain setting

260
00:12:47.720 --> 00:12:50.720
<v Speaker 2>should apply. Context is everything, so it's really.

261
00:12:50.519 --> 00:12:53.840
<v Speaker 1>About managing the whole user environment, not just profiles and isolation.

262
00:12:54.200 --> 00:12:55.240
<v Speaker 1>What else falls under that on.

263
00:12:55.279 --> 00:12:59.039
<v Speaker 2>Broad Oh, it's incredibly comprehensive. You can pull in traditional

264
00:12:59.120 --> 00:13:03.720
<v Speaker 2>ADMX based settings, group policy settings, but apply them contextually

265
00:13:03.840 --> 00:13:05.960
<v Speaker 2>through DEM, making them dynamic.

266
00:13:05.639 --> 00:13:08.200
<v Speaker 1>So more targeted than regular GPOs much more.

267
00:13:08.600 --> 00:13:12.440
<v Speaker 2>There's app of volumes integration to optimize things like outlook

268
00:13:12.480 --> 00:13:16.360
<v Speaker 2>ost files on writable volumes. You can do application blocking,

269
00:13:16.440 --> 00:13:20.240
<v Speaker 2>stop specific apps from running globally or based on conditions

270
00:13:20.519 --> 00:13:21.600
<v Speaker 2>with custom messages.

271
00:13:21.960 --> 00:13:25.039
<v Speaker 1>And the one I really like the sound of privileged elevation.

272
00:13:25.320 --> 00:13:29.559
<v Speaker 2>Yes, huge security win grant elevated rights for just one

273
00:13:29.799 --> 00:13:33.159
<v Speaker 2>specific app or installer without making the user a full

274
00:13:33.240 --> 00:13:34.120
<v Speaker 2>local admin.

275
00:13:34.360 --> 00:13:37.559
<v Speaker 1>That's fantastic. No more over privileged users just for one

276
00:13:37.679 --> 00:13:39.279
<v Speaker 1>annoying app exactly.

277
00:13:39.440 --> 00:13:43.600
<v Speaker 2>And think about all the routine stuff, drive mappings, environment variables,

278
00:13:43.639 --> 00:13:47.799
<v Speaker 2>file type associations, folder redirection, running log on, log off tasks,

279
00:13:47.840 --> 00:13:51.759
<v Speaker 2>mapping printers, creating shortcuts, even Windows settings like display language

280
00:13:51.799 --> 00:13:52.720
<v Speaker 2>or hiding drive.

281
00:13:52.600 --> 00:13:55.120
<v Speaker 1>All managed centrally and contextually.

282
00:13:54.519 --> 00:13:57.519
<v Speaker 2>All centrally defined, managed and applied based on those conditions.

283
00:13:57.519 --> 00:13:59.919
<v Speaker 2>Through DEM. It turns what used to be manual SS

284
00:14:00.000 --> 00:14:03.480
<v Speaker 2>scripting or static GPOs into an automated, dynamic process.

285
00:14:03.679 --> 00:14:06.159
<v Speaker 1>Okay, one really powerful thing we haven't dug into yet

286
00:14:06.240 --> 00:14:10.360
<v Speaker 1>is application upgrades. I mean, everyone dreads migrating user settings

287
00:14:10.399 --> 00:14:13.039
<v Speaker 1>from say Office twenty ten to Office three sixty five.

288
00:14:13.519 --> 00:14:15.279
<v Speaker 1>How does DEM handle that pain point?

289
00:14:15.600 --> 00:14:19.000
<v Speaker 2>Ah? Yes, that's a classic challenge, right, making sure all

290
00:14:19.000 --> 00:14:22.159
<v Speaker 2>the users' personal tweaks and settings move smoothly from the

291
00:14:22.200 --> 00:14:24.759
<v Speaker 2>old version to the new one without breaking anything.

292
00:14:24.840 --> 00:14:27.480
<v Speaker 1>Yeah, you don't want users complaining their customizations are gone

293
00:14:27.559 --> 00:14:28.320
<v Speaker 1>after an upgrade.

294
00:14:28.440 --> 00:14:32.080
<v Speaker 2>Exactly. Dem has a dedicated application migration feature for this.

295
00:14:32.559 --> 00:14:37.240
<v Speaker 2>It lets it define a very precise automated process to handle.

296
00:14:36.960 --> 00:14:40.000
<v Speaker 1>That transition automated. How does that work? Is it complex

297
00:14:40.080 --> 00:14:40.600
<v Speaker 1>to set up?

298
00:14:40.720 --> 00:14:44.279
<v Speaker 2>It uses a special XML file, you tell dem okay,

299
00:14:44.360 --> 00:14:47.799
<v Speaker 2>here's the flexiconfig file for the old app version, the source,

300
00:14:47.840 --> 00:14:49.600
<v Speaker 2>and here's the one for the new version, the target,

301
00:14:49.679 --> 00:14:53.039
<v Speaker 2>tours and target. Then the migration XML file itself contains

302
00:14:53.039 --> 00:14:56.879
<v Speaker 2>the detailed instructions. You define granular actions for the registry

303
00:14:56.879 --> 00:15:00.879
<v Speaker 2>and file system, things like create this registry key, rename

304
00:15:00.960 --> 00:15:04.039
<v Speaker 2>that value, delete this old file, copy these settings files,

305
00:15:04.080 --> 00:15:05.039
<v Speaker 2>move this directory.

306
00:15:05.200 --> 00:15:07.840
<v Speaker 1>So it's like a step by step script for transforming

307
00:15:07.879 --> 00:15:08.840
<v Speaker 1>the settings very much.

308
00:15:08.840 --> 00:15:10.000
<v Speaker 2>It's a transformation map.

309
00:15:10.039 --> 00:15:12.519
<v Speaker 1>And I guess the order you define those steps in

310
00:15:12.559 --> 00:15:15.879
<v Speaker 1>the XML is crucial. Get it wrong and you could

311
00:15:15.879 --> 00:15:16.600
<v Speaker 1>mess things up.

312
00:15:16.879 --> 00:15:20.639
<v Speaker 2>Absolutely critical thinking is needed there. The order of operations

313
00:15:20.639 --> 00:15:24.240
<v Speaker 2>can definitely make or break the migration. You're effectively scripting

314
00:15:24.279 --> 00:15:27.480
<v Speaker 2>the update of the user's digital footprint for that app.

315
00:15:27.840 --> 00:15:31.039
<v Speaker 1>But done right, it means a seamless transition for the user.

316
00:15:31.159 --> 00:15:34.279
<v Speaker 1>They just launched the new version and their settings are there.

317
00:15:34.399 --> 00:15:39.360
<v Speaker 2>That's the goal, completely automated maintaining user productivity, avoiding manual

318
00:15:39.360 --> 00:15:44.600
<v Speaker 2>reconfiguration or data loss. Very powerful for application life cycle management.

319
00:15:44.759 --> 00:15:48.279
<v Speaker 1>Now, even with the best planning, things inevitably go sideways.

320
00:15:48.320 --> 00:15:53.360
<v Speaker 1>Sometimes support and troubleshooting are always necessary. What tools does

321
00:15:53.440 --> 00:15:55.600
<v Speaker 1>DEM offer for it when issues pop up?

322
00:15:55.799 --> 00:15:58.600
<v Speaker 2>For that frontline support? There's the help Desk Support tool.

323
00:15:58.720 --> 00:16:00.960
<v Speaker 2>It's an optional component but really useful.

324
00:16:01.039 --> 00:16:02.360
<v Speaker 1>What does it let support staff do?

325
00:16:02.759 --> 00:16:06.360
<v Speaker 2>It allows authorized IT admins or help desk operators to

326
00:16:06.519 --> 00:16:10.720
<v Speaker 2>view user profile archives, look at backups, edit settings if needed,

327
00:16:11.039 --> 00:16:13.200
<v Speaker 2>reset profiles or restore them from backup.

328
00:16:13.240 --> 00:16:15.919
<v Speaker 1>Okay, direct access to the user's profile data exactly.

329
00:16:16.279 --> 00:16:17.960
<v Speaker 2>And it has a built in viewer for the Flex

330
00:16:18.000 --> 00:16:21.000
<v Speaker 2>Engine log files, which makes analyzing those logs much much

331
00:16:21.039 --> 00:16:22.799
<v Speaker 2>easier than digging through text files.

332
00:16:23.120 --> 00:16:24.960
<v Speaker 1>Nice log viewing built.

333
00:16:24.679 --> 00:16:27.080
<v Speaker 2>In Yeah, and you can configure it with paths and

334
00:16:27.200 --> 00:16:30.320
<v Speaker 2>labels for different environments too, which helps streamline support in

335
00:16:30.360 --> 00:16:31.600
<v Speaker 2>bigger organizations.

336
00:16:31.639 --> 00:16:34.200
<v Speaker 1>And when things do go wrong, what are some common

337
00:16:34.240 --> 00:16:37.960
<v Speaker 1>scenarios it might run into when troubleshooting DEM.

338
00:16:38.320 --> 00:16:41.720
<v Speaker 2>Well, one you might see is direct flex conflicts. An

339
00:16:41.759 --> 00:16:45.080
<v Speaker 2>application won't launch or it fails because its hooks are

340
00:16:45.159 --> 00:16:48.879
<v Speaker 2>interfering with another app hooks. Yeah, how it integrates. The

341
00:16:48.919 --> 00:16:52.559
<v Speaker 2>fix often involves blacklisting certain apps from direct Flex or

342
00:16:52.720 --> 00:16:58.360
<v Speaker 2>using some advanced config settings. Another huge one anti virus exclusions.

343
00:16:57.840 --> 00:16:59.360
<v Speaker 1>Ah AV getting in the way.

344
00:16:59.559 --> 00:17:03.759
<v Speaker 2>Always classic, Always, you absolutely must exclude the dems, shared

345
00:17:03.799 --> 00:17:07.599
<v Speaker 2>folders and the local paths and executables like flexengine dot

346
00:17:07.640 --> 00:17:11.720
<v Speaker 2>ex and Flexservice dot ex from eighty scans, otherwise you

347
00:17:11.799 --> 00:17:14.599
<v Speaker 2>risk major performance hits or even profile corruption.

348
00:17:14.759 --> 00:17:17.079
<v Speaker 1>Right critical configuration. What else you might see?

349
00:17:17.119 --> 00:17:20.880
<v Speaker 2>Folder redirection loops That happens if you accidentally redirect files

350
00:17:20.920 --> 00:17:23.880
<v Speaker 2>inside a folder that's already redirected. The log files are

351
00:17:23.920 --> 00:17:26.000
<v Speaker 2>key here check the redirected folders section.

352
00:17:26.119 --> 00:17:27.000
<v Speaker 1>Okay, logs are your.

353
00:17:26.880 --> 00:17:29.880
<v Speaker 2>Friend there Always if the configuration share is unavailable when

354
00:17:29.880 --> 00:17:32.039
<v Speaker 2>a user logs in, they might just get logged right

355
00:17:32.079 --> 00:17:34.960
<v Speaker 2>back out could be network problems or maybe a GPO setting.

356
00:17:35.599 --> 00:17:38.839
<v Speaker 2>There's a policy paths unavailable at logga that you can

357
00:17:38.880 --> 00:17:42.599
<v Speaker 2>set to skip import instead of logoff, which can sometimes.

358
00:17:42.160 --> 00:17:44.559
<v Speaker 1>Help at least lets them get to a desktop, maybe

359
00:17:44.599 --> 00:17:46.480
<v Speaker 1>without full personalization exactly.

360
00:17:46.640 --> 00:17:49.200
<v Speaker 2>And if a user logs off and finds their Windows

361
00:17:49.240 --> 00:17:50.319
<v Speaker 2>settings didn't.

362
00:17:50.039 --> 00:17:52.480
<v Speaker 1>Save, oh, what's usually the cause there?

363
00:17:52.599 --> 00:17:56.279
<v Speaker 2>Typically it means the logoff commands aren't running. You need

364
00:17:56.319 --> 00:17:59.519
<v Speaker 2>to double check that the Flexengine dot ex s command

365
00:17:59.640 --> 00:18:03.079
<v Speaker 2>is correctly set up in a log off script or policy. Gotcha,

366
00:18:03.160 --> 00:18:06.000
<v Speaker 2>And this really highlights a core belief. You know, knowledge

367
00:18:06.039 --> 00:18:08.359
<v Speaker 2>is great, but it's most valuable when you can actually

368
00:18:08.400 --> 00:18:11.640
<v Speaker 2>apply it. Learning to read those Flex Engine log files,

369
00:18:11.680 --> 00:18:14.720
<v Speaker 2>Theflex Engine dot log it's like having a direct line

370
00:18:14.720 --> 00:18:15.920
<v Speaker 2>into what dem is doing.

371
00:18:16.000 --> 00:18:17.680
<v Speaker 1>What kind of details can you see in there?

372
00:18:17.920 --> 00:18:22.359
<v Speaker 2>Oh? Everything successful logins, user and computer details, the state

373
00:18:22.400 --> 00:18:25.480
<v Speaker 2>of the profile, which config files got processed, which direct

374
00:18:25.519 --> 00:18:29.119
<v Speaker 2>Flex apps launched, how long things took, GPO processing times,

375
00:18:29.119 --> 00:18:32.720
<v Speaker 2>compression status, how it handled unavailable shares. It's your number

376
00:18:32.799 --> 00:18:33.839
<v Speaker 2>one tool for debugging.

377
00:18:33.920 --> 00:18:37.240
<v Speaker 1>Wow. Okay, we have certainly covered a lot of ground

378
00:18:37.240 --> 00:18:42.000
<v Speaker 1>today from the history and the headaches of old school user.

379
00:18:41.759 --> 00:18:43.799
<v Speaker 2>Profiles the battle days.

380
00:18:43.640 --> 00:18:47.759
<v Speaker 1>To the really sophisticated capabilities of VMware Dynamic Environment Manager.

381
00:18:48.119 --> 00:18:51.400
<v Speaker 1>I think anyone listening now has a really solid grasp

382
00:18:51.720 --> 00:18:56.200
<v Speaker 1>on how DEM tackles the complexity of managing personalized digital workspaces.

383
00:18:56.400 --> 00:18:58.839
<v Speaker 2>Absolutely, and it's important to see DEM as more than

384
00:18:58.880 --> 00:19:01.640
<v Speaker 2>just a profile tool, really a strategic piece for any

385
00:19:01.720 --> 00:19:06.440
<v Speaker 2>organization moving towards dynamic, virtualized or cloud based desktops. It

386
00:19:06.559 --> 00:19:11.039
<v Speaker 2>ensures that end user experience stays consistent, secure, and importantly productive.

387
00:19:11.200 --> 00:19:14.119
<v Speaker 1>Yeah, it's about making sure your digital workspace actually works

388
00:19:14.160 --> 00:19:16.960
<v Speaker 1>for you, not against you, every single time you log in,

389
00:19:17.039 --> 00:19:23.319
<v Speaker 1>precisely so. Looking ahead, as digital workspaces keep evolving, blending physical,

390
00:19:23.400 --> 00:19:27.000
<v Speaker 1>virtual cloud maybe even more, what new challenges do you

391
00:19:27.000 --> 00:19:30.559
<v Speaker 1>see coming up for maintaining that truly personal, agile user

392
00:19:30.640 --> 00:19:34.640
<v Speaker 1>experience and how might tools like DAM need to keep adapting.

393
00:19:34.759 --> 00:19:35.599
<v Speaker 2>That's the big question.

394
00:19:35.680 --> 00:19:37.640
<v Speaker 1>Isn't it something for you to think about? Is you

395
00:19:37.680 --> 00:19:40.519
<v Speaker 1>consider how these ideas might apply in your own digital environment,