Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated:
1
00:00:01,389 --> 00:00:05,758
[Music]
2
00:00:04,960 --> 00:00:08,240
hi
3
00:00:05,759 --> 00:00:10,160
my name is christine ruana and i'm here
4
00:00:08,240 --> 00:00:12,080
today to talk to you about all the
5
00:00:10,160 --> 00:00:15,280
improvements we've been making to the
6
00:00:12,080 --> 00:00:17,519
visual studio administrator experience
7
00:00:15,279 --> 00:00:20,239
over the last several decades
8
00:00:17,519 --> 00:00:23,359
visual studio has provided world-class
9
00:00:20,239 --> 00:00:25,839
productivity tools for developers
10
00:00:23,359 --> 00:00:28,400
we've also realized
11
00:00:25,839 --> 00:00:30,800
how important it is to provide the same
12
00:00:28,399 --> 00:00:32,719
level of functionality and support to
13
00:00:30,800 --> 00:00:34,719
i.t administrators
14
00:00:32,719 --> 00:00:37,840
those people who have the important
15
00:00:34,719 --> 00:00:40,399
responsibility for maintaining their
16
00:00:37,840 --> 00:00:42,960
organization's software infrastructure
17
00:00:40,399 --> 00:00:45,039
and keeping it secure
18
00:00:42,960 --> 00:00:45,840
the developer tools that we provide to
19
00:00:45,039 --> 00:00:48,559
you
20
00:00:45,840 --> 00:00:51,359
must be easy to update and easy to
21
00:00:48,558 --> 00:00:54,558
manage so that your organization can be
22
00:00:51,359 --> 00:00:57,600
resilient to security threats
23
00:00:54,558 --> 00:00:58,479
we want you to always have
24
00:00:57,600 --> 00:01:00,719
the
25
00:00:58,479 --> 00:01:02,718
most current and best defenses at your
26
00:01:00,719 --> 00:01:05,118
disposal
27
00:01:02,719 --> 00:01:07,760
in this talk i'll be describing the
28
00:01:05,118 --> 00:01:10,319
recent improvements we've made to help
29
00:01:07,760 --> 00:01:11,439
administrators deploy and manage visual
30
00:01:10,319 --> 00:01:14,798
studio
31
00:01:11,438 --> 00:01:17,519
as many of you are aware visual studio
32
00:01:14,799 --> 00:01:20,240
has a concept of servicing baselines
33
00:01:17,519 --> 00:01:22,879
which are distinct future version levels
34
00:01:20,239 --> 00:01:25,118
that are supported and that enterprises
35
00:01:22,879 --> 00:01:27,280
can park on
36
00:01:25,118 --> 00:01:29,920
we are now referring to servicing
37
00:01:27,280 --> 00:01:32,799
baselines as long-term servicing
38
00:01:29,920 --> 00:01:36,478
channels or ltscs
39
00:01:32,799 --> 00:01:39,040
ltscs provide flexibility and control
40
00:01:36,478 --> 00:01:41,280
for when you accept and deploy
41
00:01:39,040 --> 00:01:42,960
feature or security updates across your
42
00:01:41,280 --> 00:01:45,840
organization
43
00:01:42,959 --> 00:01:47,919
with visual studio 2022 there are a few
44
00:01:45,840 --> 00:01:51,680
significant improvements i'd like to
45
00:01:47,920 --> 00:01:55,040
call your attention to regarding ltscs
46
00:01:51,680 --> 00:01:58,240
we are now declaring in advance
47
00:01:55,040 --> 00:02:00,000
when these additional ltscs will become
48
00:01:58,239 --> 00:02:03,118
available
49
00:02:00,000 --> 00:02:06,478
and how long they'll be supported for
50
00:02:03,118 --> 00:02:10,000
starting with visual studio 2022 every
51
00:02:06,478 --> 00:02:13,598
six months in the fall and in the spring
52
00:02:10,000 --> 00:02:15,520
we will release a new ltsc that supports
53
00:02:13,598 --> 00:02:18,318
the skus that our enterprise and
54
00:02:15,520 --> 00:02:21,680
professional customers use
55
00:02:18,318 --> 00:02:25,359
each ltsc release will be supported and
56
00:02:21,680 --> 00:02:27,520
kept secure for 18 months
57
00:02:25,360 --> 00:02:29,599
having better visibility into our
58
00:02:27,520 --> 00:02:32,400
upcoming release schedule
59
00:02:29,598 --> 00:02:34,878
will hopefully be helpful to you as you
60
00:02:32,400 --> 00:02:36,400
plan your upcoming business upgrade
61
00:02:34,878 --> 00:02:40,159
cycles
62
00:02:36,400 --> 00:02:42,640
additionally these ltscs now completely
63
00:02:40,159 --> 00:02:43,680
behave as independently installable
64
00:02:42,639 --> 00:02:47,199
products
65
00:02:43,680 --> 00:02:51,840
which means that it's easier to receive
66
00:02:47,199 --> 00:02:51,839
the correct notifications and updates
67
00:02:53,680 --> 00:02:58,159
the second improvement i'd like to
68
00:02:56,159 --> 00:03:00,799
highlight here in this talk
69
00:02:58,158 --> 00:03:02,000
is an even more fundamental change to
70
00:03:00,800 --> 00:03:03,760
the product
71
00:03:02,000 --> 00:03:05,919
in fact i'm going gonna demo this
72
00:03:03,759 --> 00:03:09,280
because it's so cool
73
00:03:05,919 --> 00:03:12,559
with visual studio 2022 you can now
74
00:03:09,280 --> 00:03:15,280
configure where your clients are going
75
00:03:12,560 --> 00:03:18,319
to get their updates from
76
00:03:15,280 --> 00:03:21,439
we call these update channels
77
00:03:18,318 --> 00:03:23,839
furthermore you can also configure what
78
00:03:21,439 --> 00:03:26,079
update channels are available to your
79
00:03:23,840 --> 00:03:29,920
organization
80
00:03:26,080 --> 00:03:33,040
let me show you what i'm talking about
81
00:03:29,919 --> 00:03:36,238
here on this machine i've installed the
82
00:03:33,039 --> 00:03:40,239
visual studio 2022 product and i have
83
00:03:36,239 --> 00:03:42,400
the visual studio 2022 installer opened
84
00:03:40,239 --> 00:03:45,200
the visual studio installer is actually
85
00:03:42,400 --> 00:03:46,959
a completely separate app from the main
86
00:03:45,199 --> 00:03:49,359
visual studio ide
87
00:03:46,959 --> 00:03:51,598
the installer manages all of the
88
00:03:49,360 --> 00:03:54,640
instances that i have installed on the
89
00:03:51,598 --> 00:03:57,199
machine including previous versions
90
00:03:54,639 --> 00:04:00,399
you can see here that i happen to have
91
00:03:57,199 --> 00:04:03,280
both visual studio 2022 and
92
00:04:00,400 --> 00:04:05,360
an older version of visual studio 2019
93
00:04:03,280 --> 00:04:07,280
installed
94
00:04:05,360 --> 00:04:10,560
the new installer that comes with visual
95
00:04:07,280 --> 00:04:14,000
studio 2022 now has the capability of
96
00:04:10,560 --> 00:04:16,319
configuring the update channels or where
97
00:04:14,000 --> 00:04:18,879
each one of these visual studio products
98
00:04:16,319 --> 00:04:22,000
should get its future updates from
99
00:04:18,879 --> 00:04:24,079
when i click on the more button
100
00:04:22,000 --> 00:04:27,279
there's now an option
101
00:04:24,079 --> 00:04:29,439
to display the update settings dialog
102
00:04:27,279 --> 00:04:30,799
which allows me to configure the update
103
00:04:29,439 --> 00:04:33,600
channel
104
00:04:30,800 --> 00:04:36,560
you can see here that this instance of
105
00:04:33,600 --> 00:04:39,600
the product is configured to get updates
106
00:04:36,560 --> 00:04:40,560
from the visual studio 2022 current
107
00:04:39,600 --> 00:04:43,199
channel
108
00:04:40,560 --> 00:04:46,478
which contains the latest
109
00:04:43,199 --> 00:04:50,080
product hosted by microsoft
110
00:04:46,478 --> 00:04:54,800
i have the option to switch to either
111
00:04:50,079 --> 00:04:57,918
the 17.0 ltsc baseline channel
112
00:04:54,800 --> 00:05:00,960
or the preview channel
113
00:04:57,918 --> 00:05:03,439
if i choose the ltsc channel
114
00:05:00,959 --> 00:05:05,758
then all of my subsequent updates and
115
00:05:03,439 --> 00:05:08,800
notifications will be sourced from the
116
00:05:05,759 --> 00:05:11,680
latest release that is available on that
117
00:05:08,800 --> 00:05:14,160
ltsc channel
118
00:05:11,680 --> 00:05:17,439
oh one more thing
119
00:05:14,160 --> 00:05:19,520
don't forget to actually do the update
120
00:05:17,439 --> 00:05:21,519
after you change a channel
121
00:05:19,519 --> 00:05:24,879
setting the update channel and updating
122
00:05:21,519 --> 00:05:27,680
the product are two separate actions
123
00:05:24,879 --> 00:05:28,800
many of our enterprise customers have to
124
00:05:27,680 --> 00:05:31,439
manage
125
00:05:28,800 --> 00:05:33,439
customized environments and enforced
126
00:05:31,439 --> 00:05:35,360
customized policies
127
00:05:33,439 --> 00:05:37,918
for example sometimes in these
128
00:05:35,360 --> 00:05:40,560
environments the client machines don't
129
00:05:37,918 --> 00:05:43,758
have access to the internet
130
00:05:40,560 --> 00:05:46,560
or sometimes the development teams want
131
00:05:43,759 --> 00:05:49,120
to tightly control exactly what version
132
00:05:46,560 --> 00:05:51,918
of the product their team uses
133
00:05:49,120 --> 00:05:54,720
for these types of scenarios the it
134
00:05:51,918 --> 00:05:57,198
admins usually wind up in creating and
135
00:05:54,720 --> 00:05:59,600
maintaining a network layout of the
136
00:05:57,199 --> 00:06:02,080
visual studio product that they then
137
00:05:59,600 --> 00:06:04,720
make available for their client machines
138
00:06:02,079 --> 00:06:08,800
to install or update from
139
00:06:04,720 --> 00:06:11,440
well with the new ability to configure
140
00:06:08,800 --> 00:06:13,840
where the client looks for updates you
141
00:06:11,439 --> 00:06:16,240
can easily configure it to look for
142
00:06:13,839 --> 00:06:17,918
updates in a layout location that you
143
00:06:16,240 --> 00:06:21,360
make available
144
00:06:17,918 --> 00:06:23,038
and since layouts are very popular with
145
00:06:21,360 --> 00:06:25,120
it administrators
146
00:06:23,038 --> 00:06:27,918
we thought it'd be helpful to make this
147
00:06:25,120 --> 00:06:30,240
layout changing functionality work for
148
00:06:27,918 --> 00:06:31,918
all visions of visual studio that the
149
00:06:30,240 --> 00:06:34,639
installer controls
150
00:06:31,918 --> 00:06:37,918
in other words this functionality will
151
00:06:34,639 --> 00:06:41,038
work down level for vs 2019
152
00:06:37,918 --> 00:06:41,918
and vs 2017.2
153
00:06:41,038 --> 00:06:44,719
again
154
00:06:41,918 --> 00:06:47,279
let me show you what i'm talking about
155
00:06:44,720 --> 00:06:50,000
going back to my example i already
156
00:06:47,279 --> 00:06:53,038
showed you that my visual studio 2022
157
00:06:50,000 --> 00:06:56,079
instance can get updates from one of
158
00:06:53,038 --> 00:06:58,399
three microsoft hosted channels
159
00:06:56,079 --> 00:07:01,519
now it just so happens that my visual
160
00:06:58,399 --> 00:07:04,959
studio 29 instance was installed on this
161
00:07:01,519 --> 00:07:07,758
machine a while ago via a network layout
162
00:07:04,959 --> 00:07:10,318
you can see here that the update channel
163
00:07:07,759 --> 00:07:13,680
is named private channel and the package
164
00:07:10,319 --> 00:07:15,598
location is here on this network server
165
00:07:13,680 --> 00:07:17,120
that was used to install from a long
166
00:07:15,598 --> 00:07:18,879
time ago
167
00:07:17,120 --> 00:07:21,598
now the update channel name for this
168
00:07:18,879 --> 00:07:23,918
layout install says private channel
169
00:07:21,598 --> 00:07:26,240
simply because we made the word private
170
00:07:23,918 --> 00:07:28,159
channel be the default channel name in
171
00:07:26,240 --> 00:07:30,879
situations like this
172
00:07:28,160 --> 00:07:33,840
where an older product had already been
173
00:07:30,879 --> 00:07:36,399
installed long before this new 2022
174
00:07:33,839 --> 00:07:38,079
installer arrived
175
00:07:36,399 --> 00:07:40,159
so the last thing i'd like to show you
176
00:07:38,079 --> 00:07:42,478
in this section is the ability to
177
00:07:40,160 --> 00:07:44,720
somewhat customize
178
00:07:42,478 --> 00:07:47,439
what shows up in this drop down
179
00:07:44,720 --> 00:07:49,120
it's possible to configure what update
180
00:07:47,439 --> 00:07:50,560
options are available within your
181
00:07:49,120 --> 00:07:52,879
organization
182
00:07:50,560 --> 00:07:54,959
for example you can add additional
183
00:07:52,879 --> 00:07:57,759
network locations to service update
184
00:07:54,959 --> 00:07:59,918
channels or you can hide microsoft
185
00:07:57,759 --> 00:08:02,240
channels and prevent your clients from
186
00:07:59,918 --> 00:08:04,639
looking at microsoft servers as a source
187
00:08:02,240 --> 00:08:07,199
for updates
188
00:08:04,639 --> 00:08:09,598
suppose i am an administrator in a very
189
00:08:07,199 --> 00:08:14,400
locked down environment and i wanted to
190
00:08:09,598 --> 00:08:17,439
make both my 2022 instance and my 2019
191
00:08:14,399 --> 00:08:20,079
instance get updates from new layouts
192
00:08:17,439 --> 00:08:22,240
that i just created based on security
193
00:08:20,079 --> 00:08:24,399
updates from microsoft that came out
194
00:08:22,240 --> 00:08:26,800
last patch tuesday
195
00:08:24,399 --> 00:08:31,198
also i don't really like the default
196
00:08:26,800 --> 00:08:33,278
name private channel in my 2019 instance
197
00:08:31,199 --> 00:08:34,320
so i want to change that channel name
198
00:08:33,278 --> 00:08:36,559
too
199
00:08:34,320 --> 00:08:40,320
well i can do all of this by configuring
200
00:08:36,559 --> 00:08:43,199
a few entries in this client's registry
201
00:08:40,320 --> 00:08:43,200
which i'll do now
202
00:08:43,360 --> 00:08:49,839
i have here this registry file that i'll
203
00:08:45,679 --> 00:08:49,838
import into the registry
204
00:08:53,679 --> 00:08:58,719
now i'll bring the update settings
205
00:08:56,000 --> 00:09:00,799
dialog up again and you can see
206
00:08:58,720 --> 00:09:02,800
that i've added my layout
207
00:09:00,799 --> 00:09:05,278
in this 2022
208
00:09:02,799 --> 00:09:05,278
version
209
00:09:05,759 --> 00:09:08,559
i have the current channel
210
00:09:07,759 --> 00:09:13,278
and
211
00:09:08,559 --> 00:09:13,278
i have my new private layout channel too
212
00:09:13,519 --> 00:09:19,600
in this 2019 version
213
00:09:17,120 --> 00:09:21,360
i've renamed private channel to
214
00:09:19,600 --> 00:09:22,800
something that's more meaningful to my
215
00:09:21,360 --> 00:09:25,440
organization
216
00:09:22,799 --> 00:09:28,319
and i've also added another layout
217
00:09:25,440 --> 00:09:30,320
channel here too
218
00:09:28,320 --> 00:09:33,040
this particular configuration i
219
00:09:30,320 --> 00:09:35,200
demonstrated is just an example we have
220
00:09:33,039 --> 00:09:38,319
a few other dials available to
221
00:09:35,200 --> 00:09:40,240
facilitate slightly different scenarios
222
00:09:38,320 --> 00:09:42,480
so refer to the visual studio
223
00:09:40,240 --> 00:09:45,039
administrator's guide for additional
224
00:09:42,480 --> 00:09:47,600
details
225
00:09:45,039 --> 00:09:50,240
i hope you can see and appreciate that
226
00:09:47,600 --> 00:09:53,839
configuring and managing updates is now
227
00:09:50,240 --> 00:09:56,159
a lot easier with visual studio 2022
228
00:09:53,839 --> 00:09:58,000
even though my demo illustrated how to
229
00:09:56,159 --> 00:09:59,360
change a channel through the ui in the
230
00:09:58,000 --> 00:10:02,320
installer
231
00:09:59,360 --> 00:10:05,278
you can also get to this ui directly
232
00:10:02,320 --> 00:10:07,519
within the ide by going to the help menu
233
00:10:05,278 --> 00:10:10,078
and checking for updates
234
00:10:07,519 --> 00:10:12,399
and most importantly this functionality
235
00:10:10,078 --> 00:10:14,479
is accessible through the command line
236
00:10:12,399 --> 00:10:16,799
so that admins can manage this stuff
237
00:10:14,480 --> 00:10:18,800
programmatically
238
00:10:16,799 --> 00:10:21,679
the third improvement
239
00:10:18,799 --> 00:10:25,278
i'd like to make you aware of
240
00:10:21,679 --> 00:10:27,359
is regarding layouts
241
00:10:25,278 --> 00:10:29,919
as i mentioned earlier
242
00:10:27,360 --> 00:10:32,159
a lot of enterprises use layouts to
243
00:10:29,919 --> 00:10:33,519
control which exact version of the
244
00:10:32,159 --> 00:10:35,519
product is used within their
245
00:10:33,519 --> 00:10:37,759
organization
246
00:10:35,519 --> 00:10:39,600
as with most important things in life
247
00:10:37,759 --> 00:10:42,639
one of the biggest costs of using
248
00:10:39,600 --> 00:10:44,560
layouts is dealing with the maintenance
249
00:10:42,639 --> 00:10:47,439
layout maintenance is absolutely
250
00:10:44,559 --> 00:10:49,039
necessary in order to keep both them
251
00:10:47,440 --> 00:10:51,920
and their clients
252
00:10:49,039 --> 00:10:54,719
updated and secure
253
00:10:51,919 --> 00:10:57,439
with visual studio 2019 and below there
254
00:10:54,720 --> 00:10:59,200
are few shall we say hurdles with
255
00:10:57,440 --> 00:11:01,360
managing layouts
256
00:10:59,200 --> 00:11:04,160
the process of updating layouts was
257
00:11:01,360 --> 00:11:06,159
sometimes rather difficult to either do
258
00:11:04,159 --> 00:11:09,519
or to get right
259
00:11:06,159 --> 00:11:11,519
in some situations the new layout folder
260
00:11:09,519 --> 00:11:14,240
would not be recognized
261
00:11:11,519 --> 00:11:16,799
and in other situations it was tricky to
262
00:11:14,240 --> 00:11:19,519
determine exactly what the layout would
263
00:11:16,799 --> 00:11:21,919
even be updated to
264
00:11:19,519 --> 00:11:24,959
we've recently spent a lot of time and
265
00:11:21,919 --> 00:11:27,519
effort polishing up these scenarios and
266
00:11:24,958 --> 00:11:30,479
with visual studio 2022 we've made it
267
00:11:27,519 --> 00:11:33,519
much easier for you to confidently
268
00:11:30,480 --> 00:11:37,039
update and maintain layouts
269
00:11:33,519 --> 00:11:39,440
first of all you can now reliably change
270
00:11:37,039 --> 00:11:42,480
the network location of a layout
271
00:11:39,440 --> 00:11:44,959
in other words if your client installed
272
00:11:42,480 --> 00:11:47,360
from a layout in one location
273
00:11:44,958 --> 00:11:50,239
and you've recently created a layout in
274
00:11:47,360 --> 00:11:52,639
another location you can easily
275
00:11:50,240 --> 00:11:54,000
configure your client to update from the
276
00:11:52,639 --> 00:11:56,079
new layout
277
00:11:54,000 --> 00:11:58,320
by using the change update channel
278
00:11:56,078 --> 00:12:00,399
functionality that i just showed you
279
00:11:58,320 --> 00:12:02,560
this is a pretty simple concept and a
280
00:12:00,399 --> 00:12:03,519
lot of our customers just expected it to
281
00:12:02,559 --> 00:12:05,838
work
282
00:12:03,519 --> 00:12:07,519
well it just didn't always work before
283
00:12:05,839 --> 00:12:09,680
but i'm happy to say
284
00:12:07,519 --> 00:12:11,519
it the scenario works now all of the
285
00:12:09,679 --> 00:12:14,159
time
286
00:12:11,519 --> 00:12:15,679
now in order to change layout update
287
00:12:14,159 --> 00:12:18,399
locations
288
00:12:15,679 --> 00:12:20,638
you just need to have the functionality
289
00:12:18,399 --> 00:12:22,839
that comes with this new and improved
290
00:12:20,639 --> 00:12:26,639
visual studio 2022
291
00:12:22,839 --> 00:12:30,160
installer so we're providing the ability
292
00:12:26,639 --> 00:12:34,879
for you to distribute this new installer
293
00:12:30,159 --> 00:12:37,039
in your older 2019 and 2017 layouts
294
00:12:34,879 --> 00:12:39,759
once the new installer gets installed on
295
00:12:37,039 --> 00:12:42,319
your client machines then the clients
296
00:12:39,759 --> 00:12:44,799
will be able to switch to get updates
297
00:12:42,320 --> 00:12:46,720
from a new layout
298
00:12:44,799 --> 00:12:48,479
the next set of layout improvements i
299
00:12:46,720 --> 00:12:50,240
want to call your attention to is with
300
00:12:48,480 --> 00:12:52,639
the bootstrappers
301
00:12:50,240 --> 00:12:56,560
the bootstrapper is the file that's
302
00:12:52,639 --> 00:12:58,240
named something like vsenterprise.exe
303
00:12:56,559 --> 00:13:00,719
and it's a thing that you double click
304
00:12:58,240 --> 00:13:03,839
on to install visual studio
305
00:13:00,720 --> 00:13:06,720
it basically has just enough information
306
00:13:03,839 --> 00:13:09,120
to kick start the installation process
307
00:13:06,720 --> 00:13:11,600
the bootstrapper can also be used to
308
00:13:09,120 --> 00:13:14,078
update a layout
309
00:13:11,600 --> 00:13:16,320
in earlier versions of the product if
310
00:13:14,078 --> 00:13:19,039
you wanted to update your layout to a
311
00:13:16,320 --> 00:13:23,120
very specific version of visual studio
312
00:13:19,039 --> 00:13:26,559
you might have discovered this webpage
313
00:13:23,120 --> 00:13:28,399
which has links to all of our available
314
00:13:26,559 --> 00:13:31,199
bootstrappers
315
00:13:28,399 --> 00:13:33,440
you may have clicked one of these links
316
00:13:31,200 --> 00:13:35,120
next to the exact version that you
317
00:13:33,440 --> 00:13:37,440
wanted
318
00:13:35,120 --> 00:13:40,078
downloaded that bootstrapper and use it
319
00:13:37,440 --> 00:13:42,079
to update your layout
320
00:13:40,078 --> 00:13:43,439
a simple but immensely helpful
321
00:13:42,078 --> 00:13:46,159
improvement we've made to the
322
00:13:43,440 --> 00:13:48,399
bootstrapper is to reflect both the
323
00:13:46,159 --> 00:13:50,559
channel and the product version
324
00:13:48,399 --> 00:13:51,679
in the files properties
325
00:13:50,559 --> 00:13:54,719
here
326
00:13:51,679 --> 00:13:57,519
i have a 2022 bootstrapper
327
00:13:54,720 --> 00:13:59,440
you can see that the file properties in
328
00:13:57,519 --> 00:14:03,198
the details tab
329
00:13:59,440 --> 00:14:05,120
now tells you which version and channel
330
00:14:03,198 --> 00:14:07,919
it will install
331
00:14:05,120 --> 00:14:11,278
this information helps you confirm that
332
00:14:07,919 --> 00:14:13,838
what you execute to update a layout is
333
00:14:11,278 --> 00:14:15,600
actually what you intend
334
00:14:13,839 --> 00:14:18,160
this bootstrapper here is going to
335
00:14:15,600 --> 00:14:21,440
install the latest release that exists
336
00:14:18,159 --> 00:14:23,278
on the 17.0 ltsc channel
337
00:14:21,440 --> 00:14:25,360
and it's going to configure the layout
338
00:14:23,278 --> 00:14:26,958
to use that channel
339
00:14:25,360 --> 00:14:29,360
another way we're making layout
340
00:14:26,958 --> 00:14:32,239
maintenance easier is by providing
341
00:14:29,360 --> 00:14:33,919
another location for you to acquire
342
00:14:32,240 --> 00:14:37,039
updates from
343
00:14:33,919 --> 00:14:39,120
as you're presumably aware earlier in
344
00:14:37,039 --> 00:14:41,439
2021
345
00:14:39,120 --> 00:14:43,440
we started shipping visual studio
346
00:14:41,440 --> 00:14:46,079
administrator updates through the
347
00:14:43,440 --> 00:14:49,519
microsoft update channel
348
00:14:46,078 --> 00:14:50,958
as part of distributing through moo
349
00:14:49,519 --> 00:14:52,799
we've been putting all of our
350
00:14:50,958 --> 00:14:55,679
administrator updates up on the
351
00:14:52,799 --> 00:14:57,838
microsoft catalog 2.
352
00:14:55,679 --> 00:15:00,078
so you can also update a layout by just
353
00:14:57,839 --> 00:15:02,160
downloading one of these update packages
354
00:15:00,078 --> 00:15:03,679
from the catalog and use that to update
355
00:15:02,159 --> 00:15:06,159
your layout
356
00:15:03,679 --> 00:15:08,799
by keeping your layouts updated with the
357
00:15:06,159 --> 00:15:11,198
packages that you get here you can have
358
00:15:08,799 --> 00:15:13,838
confidence that your layout will get
359
00:15:11,198 --> 00:15:16,240
updated to the exact same version of
360
00:15:13,839 --> 00:15:18,639
visual studio that we're promoting as
361
00:15:16,240 --> 00:15:21,600
current and secure
362
00:15:18,639 --> 00:15:25,039
again for everything i've discussed here
363
00:15:21,600 --> 00:15:28,159
read the online administrator's guide
364
00:15:25,039 --> 00:15:30,799
for details on how to do all of this
365
00:15:28,159 --> 00:15:35,278
now the final thing i would like to make
366
00:15:30,799 --> 00:15:37,359
you aware of is just how many benefits
367
00:15:35,278 --> 00:15:39,519
visual studio comes with
368
00:15:37,360 --> 00:15:42,720
and how easy it is
369
00:15:39,519 --> 00:15:45,198
for your users to access them
370
00:15:42,720 --> 00:15:47,839
the vast majority of companies when they
371
00:15:45,198 --> 00:15:50,078
purchase rights to use visual studio do
372
00:15:47,839 --> 00:15:53,199
it by way of subscriptions
373
00:15:50,078 --> 00:15:55,519
there are two main ways of distributing
374
00:15:53,198 --> 00:15:57,439
subscriptions to your users
375
00:15:55,519 --> 00:16:00,078
the old school method involves
376
00:15:57,440 --> 00:16:01,920
distributing keys which works
377
00:16:00,078 --> 00:16:05,758
in the sense that it allows your teams
378
00:16:01,919 --> 00:16:07,360
to use just the visual studio product
379
00:16:05,759 --> 00:16:09,839
but there's so much more goodness that
380
00:16:07,360 --> 00:16:12,639
the subscription has to offer that the
381
00:16:09,839 --> 00:16:15,440
old key method won't unlock
382
00:16:12,639 --> 00:16:17,600
instead if you took the additional step
383
00:16:15,440 --> 00:16:19,040
of assigning email addresses to
384
00:16:17,600 --> 00:16:21,759
subscriptions
385
00:16:19,039 --> 00:16:24,000
then each person would have access to
386
00:16:21,759 --> 00:16:26,959
the additional benefits that the
387
00:16:24,000 --> 00:16:29,600
subscription offers such as azure
388
00:16:26,958 --> 00:16:30,958
credits pluralsight training
389
00:16:29,600 --> 00:16:32,639
or access
390
00:16:30,958 --> 00:16:34,879
to all historical downloads that
391
00:16:32,639 --> 00:16:36,799
microsoft produced
392
00:16:34,879 --> 00:16:38,720
so we really encourage you to both
393
00:16:36,799 --> 00:16:41,120
assign their email addresses to
394
00:16:38,720 --> 00:16:44,399
subscriptions and to encourage your
395
00:16:41,120 --> 00:16:46,399
users to visit myvisualstudio.com
396
00:16:44,399 --> 00:16:49,198
either through the website or through
397
00:16:46,399 --> 00:16:52,078
the ide to become aware of the other
398
00:16:49,198 --> 00:16:54,639
resources that are available to them
399
00:16:52,078 --> 00:16:57,719
one way for an admin to assign email
400
00:16:54,639 --> 00:17:00,320
addresses is to go to the manage
401
00:16:57,720 --> 00:17:03,600
visualstudio.com portal and either
402
00:17:00,320 --> 00:17:06,318
assign names individually or upload a
403
00:17:03,600 --> 00:17:09,360
file that contains a bunch of names
404
00:17:06,318 --> 00:17:12,000
we recently enabled another convenient
405
00:17:09,359 --> 00:17:13,599
way for admins to assign email addresses
406
00:17:12,000 --> 00:17:16,000
to subscriptions
407
00:17:13,599 --> 00:17:17,519
you can now create an azure active
408
00:17:16,000 --> 00:17:20,318
directory group
409
00:17:17,519 --> 00:17:22,558
assign that to a subscription
410
00:17:20,318 --> 00:17:24,558
and then simply add your users to this
411
00:17:22,558 --> 00:17:26,879
aad group
412
00:17:24,558 --> 00:17:28,960
at any rate i hope you and your users
413
00:17:26,880 --> 00:17:31,280
are able to take advantage of all the
414
00:17:28,960 --> 00:17:35,440
extra value that your visual studio
415
00:17:31,279 --> 00:17:35,440
subscriptions entitle youtube
416
00:17:35,919 --> 00:17:39,520
thank you very much for listening this
417
00:17:37,919 --> 00:17:42,160
talk and learning about the changes
418
00:17:39,519 --> 00:17:44,798
we've made to visual studio to improve
419
00:17:42,160 --> 00:17:46,960
the it admin experience
420
00:17:44,798 --> 00:17:49,599
you can find additional details of
421
00:17:46,960 --> 00:17:51,600
everything i've discussed in the online
422
00:17:49,599 --> 00:17:54,240
documentation of the visual studio
423
00:17:51,599 --> 00:17:56,558
administrator's guide
424
00:17:54,240 --> 00:17:58,880
we're in the process of planning for the
425
00:17:56,558 --> 00:18:01,038
next release of visual studio and would
426
00:17:58,880 --> 00:18:03,120
love to hear your feedback
427
00:18:01,038 --> 00:18:05,440
we have a survey available
428
00:18:03,119 --> 00:18:08,000
where you our partners can leave your
429
00:18:05,440 --> 00:18:10,160
contact information along with details
430
00:18:08,000 --> 00:18:11,679
of your environment and any challenges
431
00:18:10,160 --> 00:18:13,038
that you're having
432
00:18:11,679 --> 00:18:15,120
that way we'll have a better
433
00:18:13,038 --> 00:18:16,879
understanding of your situation so that
434
00:18:15,119 --> 00:18:18,798
we can better design for it in the
435
00:18:16,880 --> 00:18:22,720
future
436
00:18:18,798 --> 00:18:25,359
we've also enabled a special it admin
437
00:18:22,720 --> 00:18:26,960
way for you to submit bug reports or
438
00:18:25,359 --> 00:18:29,439
problem to us
439
00:18:26,960 --> 00:18:30,400
the initial subscription submission is
440
00:18:29,440 --> 00:18:32,798
public
441
00:18:30,400 --> 00:18:34,080
but we can make it more private if you'd
442
00:18:32,798 --> 00:18:36,319
like
443
00:18:34,079 --> 00:18:38,798
of course you can always reach out to
444
00:18:36,319 --> 00:18:41,599
your account manager as well
445
00:18:38,798 --> 00:18:42,720
lastly we put announcement on the vs
446
00:18:41,599 --> 00:18:44,959
blog
447
00:18:42,720 --> 00:18:47,120
so read that periodically and search on
448
00:18:44,960 --> 00:18:49,200
the admin keyword to find the content
449
00:18:47,119 --> 00:18:51,199
that you might be most interested in
450
00:18:49,200 --> 00:18:53,759
we're looking forward to continued
451
00:18:51,200 --> 00:18:54,880
partnership with it admins in the years
452
00:18:53,759 --> 00:18:59,440
to come
453
00:18:54,880 --> 00:18:59,440
stay safe and happy admini
31854
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.
Afrikaans
Albanian
Amharic
Arabic
Armenian
Azerbaijani
Basque
Belarusian
Bengali
Bosnian
Bulgarian
Catalan
Cebuano
Chichewa
Chinese (Simplified)
Chinese (Traditional)
Corsican
Croatian
Czech
Danish
Dutch
English
Esperanto
Estonian
Finnish
French
Frisian
Galician
Georgian
German
Greek
Gujarati
Haitian Creole
Hawaiian
Hungarian
Icelandic
Indonesian
Irish
Italian
Japanese
Kazakh
Khmer
Korean
Kurdish (Kurmanji)
Kyrgyz
Lao
Latvian
Lithuanian
Luxembourgish
Macedonian
Malagasy
Malay
Maltese
Maori
Mongolian
Myanmar (Burmese)
Nepali
Norwegian
Pashto
Polish
Portuguese
Romanian
Russian
Samoan
Serbian
Sesotho
Shona
Sinhala
Slovak
Slovenian
Somali
Swahili
Swedish
Tajik
Thai
Turkish
Ukrainian
Urdu
Uzbek
Vietnamese
