WEBVTT
00:00:01.540 --> 00:00:03.690
Hello.
Welcome to Ignite day four.
00:00:03.690 --> 00:00:09.508
I hope you're enjoying your
conference experience so far.
00:00:09.508 --> 00:00:12.260
Thanks for
coming along today to this session.
00:00:12.260 --> 00:00:18.640
This is the Office 365 ProPlus and
Office 20XX Mixing it up session.
00:00:18.640 --> 00:00:20.690
My name is Jon Maunder,
00:00:20.690 --> 00:00:24.400
I'm a technology solution
professional at Microsoft.
00:00:24.400 --> 00:00:29.066
So my role is to work with our
customers and our partners,
00:00:29.066 --> 00:00:34.100
to understand and to talk
about our productivity tools.
00:00:34.100 --> 00:00:36.290
So Office Client and
00:00:36.290 --> 00:00:40.639
Office 365 ProPlus being one of
the core technologies there.
00:00:41.730 --> 00:00:45.190
And really what we're going
to be talking about today
00:00:45.190 --> 00:00:50.330
is a session that's been born
out of customer conversation.
00:00:50.330 --> 00:00:53.060
So, the customers that
I've talked to and
00:00:53.060 --> 00:00:58.020
partners that I've talked to,
they're in a world where we have
00:00:58.020 --> 00:01:01.510
traditional Office MSI
installations.
00:01:01.510 --> 00:01:04.290
And they're looking
potentially to move forward
00:01:04.290 --> 00:01:08.204
with the latest version of Office.
00:01:08.204 --> 00:01:14.556
And they want to know, why would I
consider Office 365 ProPlus over and
00:01:14.556 --> 00:01:20.306
above the traditional MSI Windows
Server Update Services model?
00:01:20.306 --> 00:01:24.800
Why would I move forward
with this new technology?
00:01:24.800 --> 00:01:30.510
So really this session's about
why deploy Office 365 ProPlus,
00:01:30.510 --> 00:01:34.745
but crucially understanding the
differences between what Office 365
00:01:34.745 --> 00:01:38.869
ProPlus delivers and the impact it
has on an existing environment.
00:01:39.960 --> 00:01:44.320
Exactly what is it inside of
ProPlus that's different and
00:01:44.320 --> 00:01:48.900
that needs to change, and
how that impacts our overall
00:01:48.900 --> 00:01:53.350
upgrade process, but
also management moving forward.
00:01:53.350 --> 00:01:56.260
So, what we're gonna be doing is
we're gonna be framing this session
00:01:56.260 --> 00:01:59.750
in a high-level conceptual
that a project upgrade and
00:01:59.750 --> 00:02:01.280
management life cycle.
00:02:01.280 --> 00:02:04.485
So, as we go through,
we'll understand the differences.
00:02:04.485 --> 00:02:08.560
We'll understand the impact of
ProPlus on our overall environment.
00:02:10.400 --> 00:02:13.230
So we'll also be talking
about some customer examples.
00:02:13.230 --> 00:02:16.720
So I wanna highlight to you
that this has been done before.
00:02:16.720 --> 00:02:18.400
It is being done right now, and
00:02:18.400 --> 00:02:20.870
we're having some great
successes around this.
00:02:20.870 --> 00:02:23.682
So if you have concerns,
if you have questions,
00:02:23.682 --> 00:02:26.367
then let's absolutely
have a conversation.
00:02:26.367 --> 00:02:29.908
And let's show you some customers
that are actually doing that.
00:02:29.908 --> 00:02:33.450
So from me to you guys,
a quick poll.
00:02:33.450 --> 00:02:37.505
How many people here are evaluating
Office 365 ProPlus today?
00:02:37.505 --> 00:02:41.220
Wow, that's a pretty large amount.
00:02:41.220 --> 00:02:44.050
And how many people are actively
deploying it today?
00:02:45.920 --> 00:02:47.810
So, good, there's a fair
amount of people actively
00:02:47.810 --> 00:02:48.480
deploying it as well.
00:02:49.630 --> 00:02:50.840
Excellent stuff.
00:02:50.840 --> 00:02:52.940
And another question from me to you,
00:02:52.940 --> 00:02:55.400
how many here are customers
of Microsoft?
00:02:57.620 --> 00:02:58.500
Pretty much everybody.
00:02:58.500 --> 00:02:59.850
Okay, great news.
00:02:59.850 --> 00:03:02.080
How many come from
a partner community?
00:03:03.950 --> 00:03:05.370
Okay, so we've got some
partners in here as well.
00:03:05.370 --> 00:03:05.979
Excellent stuff.
00:03:07.820 --> 00:03:13.848
So, let's start with
understanding today's challenges.
00:03:13.848 --> 00:03:16.872
Well for a start,
we have end of support for
00:03:16.872 --> 00:03:18.892
legacy versions of Office.
00:03:18.892 --> 00:03:21.430
This is critical to business today.
00:03:21.430 --> 00:03:26.260
If you have to stay in a compliance
in a supported model for
00:03:26.260 --> 00:03:29.755
your business,
it is critical to stay up to date,
00:03:29.755 --> 00:03:34.820
then it is important to understand
what we mean by mainstream support,
00:03:34.820 --> 00:03:39.270
and extended support, and actually
how that impacts your business.
00:03:39.270 --> 00:03:44.760
So Office 2003, that went out of
support, along with Windows XP.
00:03:44.760 --> 00:03:48.080
So we don't support that
with Office 365 ProPlus.
00:03:48.080 --> 00:03:52.520
If you have a Windows XP desktop
estate, we need to consider
00:03:52.520 --> 00:03:56.520
an OS upgrade along with
an Office upgrade project.
00:03:56.520 --> 00:03:58.880
It's not just a case
of upgrading Office,
00:03:58.880 --> 00:04:02.350
because we don't support it
in the 365 product stack.
00:04:02.350 --> 00:04:09.098
Office 2007 is in extended support
as of October the 12th, 2012.
00:04:09.098 --> 00:04:11.790
So it's currently in
extended support.
00:04:11.790 --> 00:04:16.520
So that means we have a five-year
period with extended support that
00:04:16.520 --> 00:04:18.660
will be going out of support
in the next few years.
00:04:19.860 --> 00:04:21.150
And then Office 2010,
00:04:21.150 --> 00:04:26.750
end of mainstream support as
of October the 14th, 2015.
00:04:26.750 --> 00:04:29.330
That's an important
date to remember.
00:04:29.330 --> 00:04:29.970
So again,
00:04:29.970 --> 00:04:34.370
if your business is reliant on
being in a supported model,
00:04:34.370 --> 00:04:37.800
you need to be thinking about moving
into the next version of Office.
00:04:39.390 --> 00:04:43.947
Also part of today's challenges is
actually the Office upgrade process
00:04:43.947 --> 00:04:44.549
itself.
00:04:44.549 --> 00:04:47.830
Costly, disruptive, time-consuming.
00:04:47.830 --> 00:04:51.951
If we have product releases
on a traditional MSI basis,
00:04:51.951 --> 00:04:56.699
potentially every three years
we're releasing a new product.
00:04:56.699 --> 00:05:00.549
It's not necessarily meaning that
you're going to take that as soon as
00:05:00.549 --> 00:05:01.830
we release it.
00:05:01.830 --> 00:05:05.910
We appreciate that you may be
waiting for service pack one to come
00:05:05.910 --> 00:05:10.680
along or maybe a few security bug
fixes, feature updates as well.
00:05:10.680 --> 00:05:13.520
So potentially you're
stretching that time period
00:05:13.520 --> 00:05:17.330
of deploying one version
of Office to the next.
00:05:17.330 --> 00:05:20.990
And those large gaps can be very
disruptive to your business.
00:05:20.990 --> 00:05:25.373
It can be very disruptive to your
end users who have to be trained in
00:05:25.373 --> 00:05:28.812
moving forward with
the latest version of Office.
00:05:28.812 --> 00:05:32.040
And even the upgrade
projects themselves.
00:05:32.040 --> 00:05:35.820
Large teams, you're putting those
together, you're then auditing and
00:05:35.820 --> 00:05:39.300
understanding your environment,
understanding the impact of what
00:05:39.300 --> 00:05:42.300
bringing a new version
of Office means.
00:05:42.300 --> 00:05:44.843
And actually,
what we see on average,
00:05:44.843 --> 00:05:50.170
is 12 plus months before the first
seat is deployed into production.
00:05:50.170 --> 00:05:53.830
That's a huge wait time
before you can get any value
00:05:53.830 --> 00:05:57.580
out of your Office platform from
the day that you purchase it.
00:05:57.580 --> 00:06:01.610
So getting immediate value out
of your platform is crucial.
00:06:01.610 --> 00:06:03.740
You've paid for it,
you want to use it.
00:06:03.740 --> 00:06:06.800
You don't want to wait a year, two
years, three years until you deploy
00:06:06.800 --> 00:06:10.030
it to your end users, because
potentially they've moved on.
00:06:10.030 --> 00:06:12.230
Your business requirements
have changed.
00:06:12.230 --> 00:06:16.350
And even, potentially, Shadow IT,
is now coming into play,
00:06:16.350 --> 00:06:20.290
and your users are going out because
they see what's in the market.
00:06:20.290 --> 00:06:23.250
They understand that the latest and
greatest is out there, and
00:06:23.250 --> 00:06:25.170
can help their business.
00:06:25.170 --> 00:06:25.930
And they're going out and
00:06:25.930 --> 00:06:29.800
they're purchasing their own
products, outside of your control.
00:06:29.800 --> 00:06:32.370
So it's important to get
that value out of it, and
00:06:32.370 --> 00:06:34.070
deliver that back into the business.
00:06:36.320 --> 00:06:39.870
So I want to introduce you
to the high-level process.
00:06:39.870 --> 00:06:44.310
So again, this is how we're gonna
be framing the session, evaluation.
00:06:44.310 --> 00:06:48.000
We need to evaluate what's new,
and what's different, over and
00:06:48.000 --> 00:06:51.840
above the traditional
MSI technology.
00:06:51.840 --> 00:06:55.820
So what we can then do is
plan how that will impact us.
00:06:55.820 --> 00:06:58.380
Plan for those new features,
and the new functionality.
00:06:59.860 --> 00:07:03.906
We also need to audit and understand
what's in our environment today.
00:07:03.906 --> 00:07:08.305
That's also very important because,
of course, you have add-ins,
00:07:08.305 --> 00:07:13.000
you have solutions, and they're all
relying on a platform that's heavily
00:07:13.000 --> 00:07:17.348
integrated into the desktop,
especially with traditional Office.
00:07:17.348 --> 00:07:20.714
We have the com registrations,
the solutions add-ins,
00:07:20.714 --> 00:07:23.599
your Excel spreadsheets,
your Word documents,
00:07:23.599 --> 00:07:27.183
they're important to the way
that your business functions.
00:07:27.183 --> 00:07:30.167
And those add-ins of course
also need to work properly.
00:07:30.167 --> 00:07:33.894
So you need to understand how
application compatibility is gonna
00:07:33.894 --> 00:07:35.460
work in a new Office model.
00:07:36.980 --> 00:07:39.940
Testing application compatibility.
00:07:39.940 --> 00:07:41.030
We have a new mechanism.
00:07:41.030 --> 00:07:42.270
We have a new process.
00:07:42.270 --> 00:07:43.680
I'd like to introduce
you to that as well.
00:07:45.160 --> 00:07:47.340
Also then we have
deployment options.
00:07:47.340 --> 00:07:49.270
Lots of deployment options.
00:07:49.270 --> 00:07:51.470
And how do we manage Office overall?
00:07:51.470 --> 00:07:56.183
And again one of the differences
between managing Office in a 365
00:07:56.183 --> 00:08:00.733
ProPlus click-to run-technology and
a traditional Office and
00:08:00.733 --> 00:08:02.401
an MSI functionality.
00:08:02.401 --> 00:08:04.930
And then of course
end user training.
00:08:04.930 --> 00:08:07.960
We talked about that length of
time that it might take for
00:08:07.960 --> 00:08:10.710
you to get from one version
of Office to another.
00:08:10.710 --> 00:08:14.000
And that's gonna cause huge
disruption to your end users.
00:08:14.000 --> 00:08:17.276
So what can we do with the new
Office 365 ProPlus to actually
00:08:17.276 --> 00:08:19.678
enable you to be more
agile in your business?
00:08:22.138 --> 00:08:24.530
So let's start with the evaluation.
00:08:24.530 --> 00:08:27.839
What's new and
different in Office 365 ProPlus?
00:08:34.326 --> 00:08:38.496
Traditional Office versus Office
365 ProPlus is probably worth,
00:08:38.496 --> 00:08:43.280
at this point, us doing some level
setting with our naming conventions.
00:08:43.280 --> 00:08:47.337
When I say traditional
Office I'm talking about MSI,
00:08:47.337 --> 00:08:52.904
Windows Installer Package, WSUS,
the Windows server update services.
00:08:52.904 --> 00:08:55.227
I'm not necessarily
talking about legacy,
00:08:55.227 --> 00:08:58.290
because of course we do have
the latest versions of Office.
00:08:58.290 --> 00:09:02.620
Office 2016 is in preview today,
as MSI as well.
00:09:02.620 --> 00:09:05.708
So I'm framing legacy Office and
00:09:05.708 --> 00:09:10.900
the new Office with MSI and
WSUS as traditional Office.
00:09:12.040 --> 00:09:16.410
Office 365 ProPlus is very
much our Office as a service.
00:09:16.410 --> 00:09:20.700
If you purchase Office 365 as
a productivity platform and
00:09:20.700 --> 00:09:24.580
it includes Office 365 ProPlus,
it's still the full, fat client.
00:09:24.580 --> 00:09:28.530
It's the rich client, but
it's not Office Online.
00:09:28.530 --> 00:09:31.260
Office Online is
a different experience.
00:09:31.260 --> 00:09:32.380
It's a different service.
00:09:32.380 --> 00:09:35.490
So it's important to understand
that that is different.
00:09:36.490 --> 00:09:42.110
We still have the same requirements,
so Windows XP is not supported.
00:09:42.110 --> 00:09:44.450
We still have the 32-bit,
64-bit architecture.
00:09:45.450 --> 00:09:48.490
We still have a lot of
options around deployment.
00:09:48.490 --> 00:09:50.326
We're gonna be talking about
some of those options today.
00:09:50.326 --> 00:09:54.725
Group policy, so we can still
control our Office installs
00:09:54.725 --> 00:09:57.610
with our administrative templates.
00:09:57.610 --> 00:09:59.434
And extensibility.
00:09:59.434 --> 00:10:03.420
How we wrapped extensibility into
our Office product is exactly
00:10:03.420 --> 00:10:06.460
the same as we do with
traditional Office.
00:10:06.460 --> 00:10:09.070
We still have those APIs and
those object models, and
00:10:09.070 --> 00:10:09.720
they're still static.
00:10:11.450 --> 00:10:13.310
So what's new and different?
00:10:13.310 --> 00:10:17.290
Licensing and activation is very
important, as is identity and
00:10:17.290 --> 00:10:18.630
authentication.
00:10:18.630 --> 00:10:21.810
These are fundamental
changes in the new Office.
00:10:21.810 --> 00:10:25.190
Office 365 ProPlus introduces
a way where we have
00:10:25.190 --> 00:10:27.700
user subscription licensing.
00:10:27.700 --> 00:10:30.450
So now, as an individual user,
00:10:30.450 --> 00:10:33.180
I have a license around
my productivity platform.
00:10:34.480 --> 00:10:38.340
For 365 ProPlus, I also have
the capability under user
00:10:38.340 --> 00:10:43.800
subscription license to leverage
my mobile devices and my tablets.
00:10:43.800 --> 00:10:47.540
And I can extend into using
share computer activation,
00:10:47.540 --> 00:10:49.170
virtual desktop
environments as well.
00:10:51.320 --> 00:10:52.600
But we need an identity for that.
00:10:52.600 --> 00:10:56.590
And we need to authenticate against
that for license activation.
00:10:56.590 --> 00:10:59.650
So we'll be taking a look at
the processes around that, and
00:10:59.650 --> 00:11:01.200
what you need to take
into consideration.
00:11:02.290 --> 00:11:04.320
And of course
the deployment technology.
00:11:04.320 --> 00:11:07.970
We have this new deployment
technology called click-to-run, so
00:11:07.970 --> 00:11:10.920
we've been talking about
how that changes things and
00:11:10.920 --> 00:11:15.200
how you can leverage that platform
to give you a more efficient
00:11:15.200 --> 00:11:17.370
management and update process.
00:11:18.580 --> 00:11:22.070
So the product updates and
the product versions also change.
00:11:22.070 --> 00:11:27.390
We make available monthly builds and
you can take control of that and
00:11:27.390 --> 00:11:29.440
push that into
production yourselves.
00:11:29.440 --> 00:11:35.250
It's not about us making changes
that impacts you directly.
00:11:35.250 --> 00:11:36.520
You have options and
00:11:36.520 --> 00:11:39.610
you have control around in
the Office 365 ProPlus.
00:11:40.810 --> 00:11:43.260
We also have different
mechanisms for auditing as well.
00:11:43.260 --> 00:11:47.270
We will be taking a look at some
of the auditing capabilities.
00:11:47.270 --> 00:11:52.080
We can get the source file packages,
we can download those and
00:11:52.080 --> 00:11:54.470
we can do what we want
with those as well.
00:11:54.470 --> 00:11:57.970
That's different than traditional
Office where we'd be delivering
00:11:57.970 --> 00:12:01.080
potentially an iSO and
an MSI for you to work with.
00:12:01.080 --> 00:12:04.480
And of course side by
side on the client, so
00:12:04.480 --> 00:12:09.360
how it impacts legacy Office,
and the Office 365 ProPlus.
00:12:12.020 --> 00:12:14.200
So, quick look at
system requirements,
00:12:14.200 --> 00:12:16.060
we won't dwell on this too much.
00:12:16.060 --> 00:12:18.260
The key thing here,
again I've mentioned this,
00:12:18.260 --> 00:12:21.820
is we don't support Windows XP
with Office 365 ProPlus.
00:12:21.820 --> 00:12:22.810
It's out of support.
00:12:22.810 --> 00:12:25.610
So nothing's going to
be happening with that.
00:12:25.610 --> 00:12:28.770
And also our browsers, it's worth
mentioning the browsers here.
00:12:28.770 --> 00:12:32.030
Without add ins, some of our add
ins that we place into Office
00:12:32.030 --> 00:12:35.030
365 Pro Plus,
they leverage the browser.
00:12:35.030 --> 00:12:38.160
So it's important to understand
that we do have system requirements
00:12:38.160 --> 00:12:39.730
around our browser
technologies as well.
00:12:42.610 --> 00:12:45.740
So what's new in Group Policy for
our new technology?
00:12:46.740 --> 00:12:52.820
So we do have content specific to
click-to-run namely around enabling
00:12:52.820 --> 00:12:56.770
automatic updates and managing those
updates, managing target versions
00:12:56.770 --> 00:13:00.980
as well, ensuring that you've set
your sights on a particular build,
00:13:00.980 --> 00:13:05.180
in a particular point in time and
you can dynamically control that.
00:13:05.180 --> 00:13:08.810
There's a whole range of these
setting that you can set up at time
00:13:08.810 --> 00:13:12.790
of install, but what Group Policy
allows you to do is then go and
00:13:12.790 --> 00:13:14.810
dynamically update that.
00:13:14.810 --> 00:13:16.970
So we've included that in our
new technologies as well.
00:13:18.220 --> 00:13:20.360
And of course telemetry.
00:13:20.360 --> 00:13:23.920
We have this new capability called
telemetry that's gonna help us
00:13:23.920 --> 00:13:29.100
do our auditing and our checking
of what's in our Office estates,
00:13:29.100 --> 00:13:33.770
our solutions, our add-ins, and
we utilize group policy very heavily
00:13:33.770 --> 00:13:35.409
to activate that and
to control that.
00:13:38.420 --> 00:13:42.220
We also have a new way of
servicing office 365 pro-class.
00:13:42.220 --> 00:13:45.260
So we're now talking about
updates not upgrades.
00:13:45.260 --> 00:13:48.840
So we no longer have this
disruptive manner where we have,
00:13:48.840 --> 00:13:52.050
okay I'm on a version
of Office say 200,7 and
00:13:52.050 --> 00:13:56.359
I need to potentially jump to 2013
or maybe move forward to 2016.
00:13:57.510 --> 00:14:01.520
But actually there's a whole range
of things that have changed there,
00:14:01.520 --> 00:14:04.160
and I need my business
to maintain agility.
00:14:04.160 --> 00:14:07.650
I need to be able to push that out
and allow them to get to know it and
00:14:07.650 --> 00:14:09.060
get to understand it.
00:14:09.060 --> 00:14:12.700
So we make these builds available
on a monthly basis, and they've
00:14:12.700 --> 00:14:15.800
actually got some updates based on
some of the things that we announced
00:14:15.800 --> 00:14:20.920
a night this week around updates and
how we can manage our latest and
00:14:20.920 --> 00:14:24.440
greatest builds and also our
security packs and bug fixes.
00:14:25.830 --> 00:14:28.970
But it's important to understand
that updates are accumulative.
00:14:28.970 --> 00:14:30.380
Conversely with MSI,
00:14:30.380 --> 00:14:35.210
there is sequential, adding a lot
of time onto our base installs.
00:14:35.210 --> 00:14:37.960
So, if I have to go
from a base 2013,
00:14:37.960 --> 00:14:41.980
for example, I may then need to go
and install Service Pack one and
00:14:41.980 --> 00:14:46.570
a whole range of other
service packs and updates.
00:14:46.570 --> 00:14:48.040
Where updates are cumulative,
00:14:48.040 --> 00:14:52.330
going from one build to the next is
just gonna take those delta changes,
00:14:52.330 --> 00:14:56.120
and it's just gonna impact
a restart one time.
00:14:56.120 --> 00:15:00.970
So we have smaller differences
coming out to Office 365 Pro Plus,
00:15:00.970 --> 00:15:05.890
and also, we pushed that update
mechanism back over to the client,
00:15:05.890 --> 00:15:09.290
so it's no longer essential
server manager platform.
00:15:09.290 --> 00:15:11.110
We actually get to
control the client and
00:15:11.110 --> 00:15:17.220
how that behaves with our updates
rr we can do background updating.
00:15:17.220 --> 00:15:21.220
Again, we can leverage group
policy to suppress notifications,
00:15:21.220 --> 00:15:25.290
to schedule updates, and to ensure
we are on the correct version
00:15:25.290 --> 00:15:26.350
at the correct point in time.
00:15:26.350 --> 00:15:30.150
I'm gonna mention ((telemetry)).
00:15:30.150 --> 00:15:32.700
So allowing our IT and
00:15:32.700 --> 00:15:36.800
our business functions to understand
what's in our office estates.
00:15:36.800 --> 00:15:38.220
What solutions are being used?
00:15:38.220 --> 00:15:39.570
What add-ons are being used?
00:15:39.570 --> 00:15:41.420
What documents are being created?
00:15:41.420 --> 00:15:42.580
What versions are failing?
00:15:42.580 --> 00:15:44.320
What versions are succeeding?
00:15:44.320 --> 00:15:47.890
Getting that report and using that
data models to make decisions and
00:15:47.890 --> 00:15:49.700
to drive down help desk costs.
00:15:52.100 --> 00:15:55.300
So the updates and
future compatibility story.
00:15:55.300 --> 00:15:57.630
We get a lot of
questions around this.
00:15:57.630 --> 00:16:02.230
You know, today, with MSI,
we get to deliver monthly updates,
00:16:02.230 --> 00:16:06.080
we still do that, security and
bug fixes and changes and you can
00:16:06.080 --> 00:16:11.420
get notified using WSUS and okay I
wrap that out and I can push it out.
00:16:11.420 --> 00:16:14.030
Crucially I also need to do things
like application testing so
00:16:14.030 --> 00:16:16.570
I am going to push that out
to my validation group.
00:16:16.570 --> 00:16:19.380
What we have here is
00:16:19.380 --> 00:16:23.850
the same object model in APIs
that we are using since 2010.
00:16:23.850 --> 00:16:26.670
We're using an Apps for
Office model.
00:16:26.670 --> 00:16:31.510
So if you have apps that you've
purchased or that you've built, and
00:16:31.510 --> 00:16:35.700
they are build for the apps for
Office standard, moving forward into
00:16:35.700 --> 00:16:39.378
365 Pro Plus, and moving forward
throughout our monthly builds,
00:16:39.378 --> 00:16:43.270
will maintain that object model and
that API,
00:16:43.270 --> 00:16:48.600
we'll ensure you have a service
level agreement wrapped around that.
00:16:48.600 --> 00:16:52.140
So yes, we are updating or
we're making available updates for
00:16:52.140 --> 00:16:53.930
Office on a monthly basis.
00:16:53.930 --> 00:16:54.880
You have the control.
00:16:54.880 --> 00:16:58.980
But we also want to give you the
confidence that you have the ability
00:16:58.980 --> 00:17:02.030
to move forward without
it necessarily impacting
00:17:02.030 --> 00:17:05.269
your add-ins and your
registrations that you developed.
00:17:08.554 --> 00:17:12.420
We still have the same life cycle
policy as traditional Office,
00:17:12.420 --> 00:17:13.350
as well.
00:17:13.350 --> 00:17:16.440
It's still that 12 month
supportability life cycle.
00:17:16.440 --> 00:17:19.790
And we're able to say,
okay, as long as, say for
00:17:19.790 --> 00:17:22.140
example, January, I deliver a build.
00:17:22.140 --> 00:17:26.290
As long as I'm on the next build
along, by February of the next year,
00:17:26.290 --> 00:17:29.280
or January of the next year,
that I'm still in a supported model,
00:17:29.280 --> 00:17:33.560
and that is not a break fixed
boundary it's a support boundary.
00:17:33.560 --> 00:17:35.750
Meaning that if you want
to call up Microsoft and
00:17:35.750 --> 00:17:39.590
you have a support problem,
then yes, we'll absolutely help you,
00:17:39.590 --> 00:17:43.770
but we'll need to ensure that your
at least in 12 month support.
00:17:43.770 --> 00:17:45.280
12 month build numbers.
00:17:45.280 --> 00:17:47.952
And that's exactly
the same as our MSI.
00:17:51.482 --> 00:17:53.375
So, Click-to-Run.
00:17:53.375 --> 00:17:54.890
What is Click-to-Run?
00:17:54.890 --> 00:17:58.700
Well it enables us to
deliver Office as a service.
00:17:58.700 --> 00:18:03.450
So we have this analogy where
I have a mobile device,
00:18:03.450 --> 00:18:04.549
I have my app store.
00:18:05.630 --> 00:18:07.560
I go and buy an app and
that's great.
00:18:07.560 --> 00:18:08.180
It's fine.
00:18:08.180 --> 00:18:09.200
I have that app.
00:18:09.200 --> 00:18:10.250
And every now and again.
00:18:10.250 --> 00:18:11.770
Maybe weekly and maybe monthly.
00:18:11.770 --> 00:18:15.830
My phone will tell me there's
a new update in the app store.
00:18:15.830 --> 00:18:18.110
So I can click on that
update in the app store.
00:18:18.110 --> 00:18:20.395
It runs and updates and
then that's it.
00:18:20.395 --> 00:18:21.490
I forget about it.
00:18:21.490 --> 00:18:24.424
I use the new features,
whatever's come to fruition.
00:18:24.424 --> 00:18:29.180
With Office-as-a-Service that's very
much the model we're going for.
00:18:29.180 --> 00:18:31.030
There's an update available.
00:18:31.030 --> 00:18:32.130
Do you want to take it?
00:18:32.130 --> 00:18:34.620
Yes we do.
We want to stay on the latest build.
00:18:34.620 --> 00:18:38.190
We wanna get the latest features
that are tying into the rest of our
00:18:38.190 --> 00:18:39.860
productivity platform.
00:18:39.860 --> 00:18:40.900
We want that.
00:18:40.900 --> 00:18:43.020
So when an update
gets made available,
00:18:43.020 --> 00:18:45.380
let's run that through
application testing.
00:18:45.380 --> 00:18:48.230
Let's ensure that we validate it and
it works.
00:18:48.230 --> 00:18:52.070
And let's push it onto production
and see how we can also make that.
00:18:52.070 --> 00:18:54.300
Actually leveraging
the Click-to-Run technology,
00:18:54.300 --> 00:18:58.150
the virtualization technology allows
us to do things like running side by
00:18:58.150 --> 00:18:59.679
side with legacy versions of Office.
00:19:00.990 --> 00:19:03.940
Or we can deliver Office
directly to the end user via
00:19:03.940 --> 00:19:05.140
the Office 365 portal.
00:19:05.140 --> 00:19:10.160
So you can give the control back to
your end users, if you wanted to,
00:19:10.160 --> 00:19:14.260
to allow them to go into Office
365 portal, click on install,
00:19:14.260 --> 00:19:17.030
they can choose their architecture,
they can choose their language, and
00:19:17.030 --> 00:19:19.460
they can get that installed
on their local machine.
00:19:19.460 --> 00:19:21.410
Assuming that they're
local administrators, and
00:19:21.410 --> 00:19:22.880
you want to allow that.
00:19:22.880 --> 00:19:26.380
This is a great use case for
those remote workers,
00:19:26.380 --> 00:19:29.400
giving them the ability to
update from wherever they are.
00:19:29.400 --> 00:19:32.410
And then
the Content Delivery Network.
00:19:32.410 --> 00:19:37.240
We're making these bills available
on a monthly basis globally,
00:19:37.240 --> 00:19:39.160
distributed globally.
00:19:39.160 --> 00:19:43.047
So you have the option to take
a build from our content delivery
00:19:43.047 --> 00:19:47.310
network and actually then download
that to your local network, and
00:19:47.310 --> 00:19:50.003
execute your testing,
your validation,
00:19:50.003 --> 00:19:53.095
and push that out to
production in your control.
00:19:53.095 --> 00:19:55.268
So you still have that
control around that.
00:19:55.268 --> 00:19:59.740
And we talk about it being
evergreen and always up to date.
00:19:59.740 --> 00:20:02.448
So again, we're making those
monthly bills available.
00:20:02.448 --> 00:20:07.228
We're also wrapping in product
features, new things that
00:20:07.228 --> 00:20:11.921
are coming with Office we feel
may benefit your business.
00:20:11.921 --> 00:20:14.371
So we've got a great
example within Office,
00:20:14.371 --> 00:20:16.507
we have this tell me
what you want to do.
00:20:16.507 --> 00:20:19.920
And it's actually a search
bar that appeared in Office.
00:20:19.920 --> 00:20:23.148
One month it appeared and
actually, instead of having to find
00:20:23.148 --> 00:20:25.940
the controls I can just tell
Office what I want to do and
00:20:25.940 --> 00:20:27.443
it takes me to the controls.
00:20:27.443 --> 00:20:28.582
It's a great feature.
00:20:28.582 --> 00:20:30.120
And it got delivered in a month.
00:20:31.160 --> 00:20:34.240
Our IT department let us know
that this feature was coming
00:20:34.240 --> 00:20:37.250
using notifications that
we have at Microsoft.
00:20:37.250 --> 00:20:41.000
And then we can anticipate that
change, the next month we have that.
00:20:41.000 --> 00:20:43.670
We can take advantage
of that new capability.
00:20:43.670 --> 00:20:45.110
I love that feature.
00:20:45.110 --> 00:20:48.706
Especially if you're tying it into
the overall productivity platform,
00:20:48.706 --> 00:20:52.302
it's great, because if we release
things like groups in Office 365,
00:20:52.302 --> 00:20:54.227
you'll see groups appear in Outlook.
00:20:54.227 --> 00:20:58.344
You'll see groups appear in your
other applications that you want
00:20:58.344 --> 00:20:58.941
them to.
00:20:58.941 --> 00:21:01.261
So we've released a new feature,
00:21:01.261 --> 00:21:05.662
you can get that experience in
Office the month it gets released.
00:21:05.662 --> 00:21:08.480
And I've mentioned IT
control manageability.
00:21:08.480 --> 00:21:11.430
Having that capability to take
Office in, to do what you need to
00:21:11.430 --> 00:21:13.990
with it before then pushing
it out to production.
00:21:16.890 --> 00:21:20.530
So let's take a quick look at
the Click-to-Run Install Flow.
00:21:21.580 --> 00:21:24.660
So, we have this
Office Deployment Tool.
00:21:24.660 --> 00:21:27.470
There's actually a session
at Ignite called,
00:21:27.470 --> 00:21:30.500
that talks all around
the Office Deployment Tool.
00:21:33.060 --> 00:21:38.166
So what the Office Deployment Tool
is doing, as IT administrators,
00:21:38.166 --> 00:21:43.623
is allowing us to execute a download
and install and uninstall an update,
00:21:43.623 --> 00:21:48.745
a repair, actually configure and
customize Office as we need it to.
00:21:48.745 --> 00:21:51.837
And we have essentially what
the Office Deployment Tool is,
00:21:51.837 --> 00:21:54.565
is a setup.exe bootstrapper
with a configuration,
00:21:54.565 --> 00:21:56.520
a customizable configuration file.
00:21:57.520 --> 00:22:02.002
So when we run setup.exe it
downloads the basic prerequisites,
00:22:02.002 --> 00:22:04.760
those ICAP files, it brings
those down to our local machine.
00:22:06.300 --> 00:22:08.620
And what it actually then does,
is it deploys and
00:22:08.620 --> 00:22:15.490
runs the Office Click-to-Run client,
and then moves into user mode.
00:22:15.490 --> 00:22:18.340
So, this is utilizing
the user account,
00:22:19.600 --> 00:22:24.550
the person that's locked in
who runs Officeclicktorun.exe.
00:22:24.550 --> 00:22:27.765
That then goes away and downloads
the full prerequisites required,
00:22:27.765 --> 00:22:32.480
it then installs
a Click-to-Run service.
00:22:32.480 --> 00:22:36.580
Now this service then moves into
System Mode, so local system account
00:22:36.580 --> 00:22:41.330
is then running our streaming and
our
00:22:41.330 --> 00:22:46.420
integration processes in parallel
to the first run experience.
00:22:46.420 --> 00:22:48.490
So, when you configure Office and
you set it up and
00:22:48.490 --> 00:22:52.220
it starts running, we'll see that
first run experience that, welcome,
00:22:52.220 --> 00:22:55.710
hi, welcome to Office, these are all
the great things that you can do.
00:22:55.710 --> 00:23:00.570
Of course, as IT professionals, you
can suppress those notifications.
00:23:00.570 --> 00:23:02.540
But in the local system
account in system mode,
00:23:02.540 --> 00:23:05.290
what's happening is that we're
now streaming those bits from
00:23:05.290 --> 00:23:08.590
the content delivery network all
from your local installation point.
00:23:08.590 --> 00:23:11.968
So, it might be a system center
configuration distribution point or
00:23:11.968 --> 00:23:14.412
it might be a DFS file share,
network file share,
00:23:14.412 --> 00:23:17.200
whatever that may be,
it's not streaming.
00:23:17.200 --> 00:23:19.805
We now give you the capability
to start using Office and
00:23:19.805 --> 00:23:23.034
in the background it's doing things
like the com registrations and
00:23:23.034 --> 00:23:25.655
is working in the background
integration for Office.
00:23:25.655 --> 00:23:31.250
As I say, the Click-to-Run Service
runs for the lifetime of Office.
00:23:31.250 --> 00:23:35.830
While it's in user mode the
clicktorun.exe, that actually ends.
00:23:35.830 --> 00:23:39.300
That executes a last run task,
and then that ends.
00:23:41.130 --> 00:23:44.470
So taking a quick look a little bit
deeper into it, we have this virtual
00:23:44.470 --> 00:23:48.800
file system that's getting delivered
using the Initiated Context.
00:23:48.800 --> 00:23:52.870
So, as IT professionals, if you want
to track a deployment, look for
00:23:52.870 --> 00:23:55.560
the integrated Office.exe,
00:23:55.560 --> 00:23:58.590
that's how you're gonna be able
to track the deployments, and
00:23:58.590 --> 00:24:01.570
the installation of Office
on a particular machine.
00:24:02.610 --> 00:24:06.575
And again, we see that it kicks
into the streaming service,
00:24:06.575 --> 00:24:10.698
the streaming begins and
moves into the local system account,
00:24:10.698 --> 00:24:12.742
the system context of 10%.
00:24:12.742 --> 00:24:15.894
And roughly around the 15% mark,
within usually two or
00:24:15.894 --> 00:24:19.882
three minutes, we're able to start
utilizing Office, it's then gonna
00:24:19.882 --> 00:24:24.280
start caching those bits, it's also
going to do bit prioritization.
00:24:24.280 --> 00:24:27.330
So if you want to use Office,
you want to start up PowerPoint,
00:24:27.330 --> 00:24:30.770
you want to start up Word,
it will prioritize the bits to
00:24:30.770 --> 00:24:34.930
get that application running
as quickly as possible, and
00:24:34.930 --> 00:24:36.130
then that will finalize out.
00:24:37.480 --> 00:24:41.910
So again, a different mechanism to
how the MSI, the traditional Office,
00:24:41.910 --> 00:24:44.530
gets installed,
we have the streaming version,
00:24:44.530 --> 00:24:49.610
we have this virtual file system
that provides a level of separation
00:24:49.610 --> 00:24:54.285
between the application and the OS
provides enough integration to
00:24:54.285 --> 00:24:58.400
ensure that our com registrations
are still active and working.
00:24:58.400 --> 00:25:02.027
We still have compatibility
with the operating system.
00:25:06.148 --> 00:25:09.794
So, that's a bit about some
of the key facts that you may
00:25:09.794 --> 00:25:14.141
want to understand before moving
forward with Click-to-Run and
00:25:14.141 --> 00:25:16.560
the Office 365 ProPlus product.
00:25:17.630 --> 00:25:19.600
And then auditing,
00:25:19.600 --> 00:25:22.770
there's a good reason why I
put auditing before planning.
00:25:22.770 --> 00:25:26.440
Although, these two do
very much interchange.
00:25:26.440 --> 00:25:29.510
Because auditing can
help us with planning.
00:25:29.510 --> 00:25:32.890
But of course we still need to
plan how we're going to audit.
00:25:32.890 --> 00:25:36.070
So, let's take a little
bit of a look about
00:25:36.070 --> 00:25:38.300
auditing our environment here.
00:25:39.740 --> 00:25:43.320
So, we now have a modern
Office compatibility story.
00:25:43.320 --> 00:25:46.460
So, Office Migration Planning
Management Tools and
00:25:46.460 --> 00:25:50.970
the Office Environment Assessment
Toolkits, they're still around,
00:25:50.970 --> 00:25:53.820
you can still get hold
of that information,
00:25:53.820 --> 00:25:56.440
but really what we're doing is
we're looking to move over to our
00:25:56.440 --> 00:25:58.910
telemetry, our telemetry dashboard.
00:25:58.910 --> 00:26:01.540
That's gonna allow us
to fully audit and
00:26:01.540 --> 00:26:04.590
fully understand what's in
our Office environment.
00:26:04.590 --> 00:26:09.010
Discover what's being used today,
solutions, add-ins, documents,
00:26:09.010 --> 00:26:10.240
that kind of thing.
00:26:10.240 --> 00:26:13.950
And what we then need to do,
is understand what's important.
00:26:13.950 --> 00:26:17.574
You may want to bring the business
into these conversations,
00:26:17.574 --> 00:26:20.848
hey guys, we found these add-ins,
these solutions,
00:26:20.848 --> 00:26:24.559
these documents that are being used,
and are they important?
00:26:24.559 --> 00:26:28.508
Well I've got 25 people that are
using them, they're C-level staff,
00:26:28.508 --> 00:26:31.894
they're directors, let's put
some importance around that,
00:26:31.894 --> 00:26:34.230
let's do some proactive
checking on that.
00:26:34.230 --> 00:26:37.758
But over here, we have one or
two people using it,
00:26:37.758 --> 00:26:43.200
not too sure that we'd even purchase
this or even if we're managing it.
00:26:43.200 --> 00:26:44.910
Is this important to look at?
00:26:44.910 --> 00:26:50.060
Do we need to look or bring in this
add-in and officially support it?
00:26:50.060 --> 00:26:53.194
If not, well let's put some
reactive testing around it,
00:26:53.194 --> 00:26:56.710
let's ensure that they can talk to
us and we can troubleshoot that, but
00:26:56.710 --> 00:26:59.210
let's not necessarily
plan that out from.
00:26:59.210 --> 00:27:02.870
Let's not take the time to bring
that into our project, let's leave
00:27:02.870 --> 00:27:06.350
that as an outlier and concentrate
on what's important to the business.
00:27:07.730 --> 00:27:09.750
And then of course
we need to validate.
00:27:09.750 --> 00:27:13.939
So we need to deploy Office
365 ProPlus to a set of users,
00:27:13.939 --> 00:27:19.190
ideally IT-friendly users,
who are gonna be honest and
00:27:19.190 --> 00:27:22.880
give you some open feedback about
exactly whether their add-ins and
00:27:22.880 --> 00:27:25.080
their solutions
are working properly.
00:27:25.080 --> 00:27:25.966
And bring them in and
00:27:25.966 --> 00:27:28.896
ensure that things are working
properly before you move forward.
00:27:30.219 --> 00:27:31.680
And then management.
00:27:31.680 --> 00:27:36.239
How the compatibility model now can
also help you with your deployment,
00:27:36.239 --> 00:27:38.855
tracking and monitoring,
reporting and
00:27:38.855 --> 00:27:41.931
analyzing exactly what
you have in that estate.
00:27:41.931 --> 00:27:46.787
And actually, you can help drive
down help desk costs by proactively
00:27:46.787 --> 00:27:51.643
seeing and understanding those
events that are either succeeding or
00:27:51.643 --> 00:27:55.661
failing, which operating
system they're running on,
00:27:55.661 --> 00:28:00.013
what version they're running on,
and then you can go into and
00:28:00.013 --> 00:28:02.549
proactively work on those issues.
00:28:02.549 --> 00:28:06.149
It's probably worth while at this
point, highlighting one of my
00:28:06.149 --> 00:28:09.946
colleague sessions, we have Using
Its Office Telemetry Dashboards
00:28:09.946 --> 00:28:12.930
to Manage Change,
which is by Curtis Owen.
00:28:12.930 --> 00:28:15.190
That was yesterday, so
00:28:15.190 --> 00:28:18.870
if you didn't go to that session,
please do check out the recording.
00:28:18.870 --> 00:28:21.910
He'll be going through
the Office Telemetry and
00:28:21.910 --> 00:28:25.270
the Office Telemetry dashboard,
exactly how that works and
00:28:25.270 --> 00:28:28.760
what's in the product, so
very well worth taking a look there.
00:28:29.790 --> 00:28:31.179
Crucially, again,
00:28:31.179 --> 00:28:35.270
understanding from reports what
issues are being detected and
00:28:35.270 --> 00:28:39.294
the performance of Office and
understanding who has Office.
00:28:39.294 --> 00:28:43.269
So when your stakeholders say how
far along of the deployment plan
00:28:43.269 --> 00:28:47.531
are we, well hey, you can give them
a data model, you can even surface
00:28:47.531 --> 00:28:51.449
that into Power BI and just give
them a dashboard to manage that.
00:28:51.449 --> 00:28:55.775
So we're giving you a proactive
way to update the data for
00:28:55.775 --> 00:29:00.373
your stake holders to understand
where you are in your Office
00:29:00.373 --> 00:29:05.172
deployments and to understand
your total investment as well.
00:29:05.172 --> 00:29:07.960
So now let's take a look at
what you need to plan for.
00:29:07.960 --> 00:29:11.106
So now we've evaluated
the new 365 ProPlus,
00:29:11.106 --> 00:29:15.173
we understand that there's a new
deployment technology, and
00:29:15.173 --> 00:29:18.949
some of the benefits around
using the new auditing tools.
00:29:18.949 --> 00:29:21.888
But we need to plan for things
like identity and authentication.
00:29:24.685 --> 00:29:29.371
So user subscription licensing for
Office 365 ProPlus
00:29:29.371 --> 00:29:33.910
gives us the ability to use
Office on multiple devices.
00:29:33.910 --> 00:29:38.760
Office 365 ProPlus, a user
subscription license, five PC or
00:29:38.760 --> 00:29:46.205
Macs, plus, five tablet devices,
plus five mobile devices.
00:29:46.205 --> 00:29:49.927
Now in this session we're not gonna
talk about the mobile devices and
00:29:49.927 --> 00:29:52.943
the tablets, this is very
much around the Office 365
00:29:52.943 --> 00:29:55.018
ProPlus client on the PC and
the Macs.
00:29:55.018 --> 00:29:59.413
But, ultimately, what we need to do
to license them is have an identity
00:29:59.413 --> 00:30:01.336
in the Office 365 Service.
00:30:01.336 --> 00:30:04.948
Or we have three identity
models that we can leverage.
00:30:04.948 --> 00:30:08.150
We also have a minimum
set of attributes.
00:30:08.150 --> 00:30:11.400
So if you're in an organization
that wants to restrict because you
00:30:11.400 --> 00:30:15.830
are a secure organization who's
concerned about too much data in
00:30:15.830 --> 00:30:19.180
the cloud, we have a minimum set of
attributes that we'll just highlight
00:30:19.180 --> 00:30:21.820
that you need to be
ensuring on ROM or
00:30:21.820 --> 00:30:25.330
are being synchronized if you're
using directory synchronization.
00:30:25.330 --> 00:30:28.580
And also leveraging modern
authentication in the new
00:30:28.580 --> 00:30:29.510
Office platform as well.
00:30:30.840 --> 00:30:34.230
So a very brief overview, I'm
sure from this entire conference,
00:30:34.230 --> 00:30:36.770
you've probably seen this
slide five or six times.
00:30:36.770 --> 00:30:38.170
For those of you who haven't,
00:30:38.170 --> 00:30:41.348
the first identity model we
have here is cloud identity.
00:30:41.348 --> 00:30:44.350
Zero on-premises infrastructure.
00:30:44.350 --> 00:30:49.050
So if you're looking to take
advantage of Office 365 ProPlus
00:30:49.050 --> 00:30:52.952
immediately, I don't want
to do anything except for
00:30:52.952 --> 00:30:56.572
deploy Office 365 ProPlus,
go for cloud identities.
00:30:56.572 --> 00:31:00.770
There's no on-premises integrations
that are gonna be required.
00:31:00.770 --> 00:31:04.790
You can use an Excel file,
a CSV file.
00:31:04.790 --> 00:31:08.780
And even if you wanted to, you
could take a CSV directory export,
00:31:08.780 --> 00:31:11.243
push that into that CSV file, and
00:31:11.243 --> 00:31:17.130
use PowerShell to script the import
of your users into Office 365.
00:31:17.130 --> 00:31:19.864
And you could PowerShell
the licensing activation for
00:31:19.864 --> 00:31:21.680
Office ProPlus as well.
00:31:21.680 --> 00:31:22.530
If you want to get up and
00:31:22.530 --> 00:31:26.080
running in Office 365 ProPlus,
yes you need an identity.
00:31:26.080 --> 00:31:29.123
But no, it doesn't need
to be time consuming and
00:31:29.123 --> 00:31:32.624
you don't need on-premises
infrastructure to do it.
00:31:32.624 --> 00:31:34.830
The second one is
synchronized identity.
00:31:34.830 --> 00:31:37.400
So running a directory
synchronization service
00:31:37.400 --> 00:31:40.690
on premises that will
allow you to automatically
00:31:40.690 --> 00:31:42.679
synchronize your
directories into the cloud.
00:31:44.620 --> 00:31:47.060
And our third one is
federated identities.
00:31:47.060 --> 00:31:50.790
Allowing us to bring
the authentication and authorization
00:31:50.790 --> 00:31:54.790
processes back on to our on-premises
active directory platform and
00:31:54.790 --> 00:31:58.300
even wrap around some cloud access
policies to ensure that it's secure.
00:32:01.050 --> 00:32:03.620
So these are the minimum
attributes required to deliver
00:32:03.620 --> 00:32:07.570
Office 365 ProPlus news and
directory synchronization.
00:32:07.570 --> 00:32:11.010
I thought this was
a worthwhile slide to add up.
00:32:11.010 --> 00:32:15.380
This information is in TechNet and
if you're using the new
00:32:15.380 --> 00:32:18.160
Azure Active Directory
Synchronization Tool which I would
00:32:18.160 --> 00:32:24.080
be encouraging, you will have a set
of options to restrict by app.
00:32:24.080 --> 00:32:26.550
So select Restrict by App.
00:32:26.550 --> 00:32:29.190
Select Office 365 ProPlus.
00:32:29.190 --> 00:32:31.632
And even if this is too many,
there's actually one or
00:32:31.632 --> 00:32:33.140
two that you can take out.
00:32:33.140 --> 00:32:35.300
Things like the pwdLastSets.
00:32:35.300 --> 00:32:39.034
You can actually take some of
these attributes out as well, but
00:32:39.034 --> 00:32:41.927
these are the minimum
recommended attributes.
00:32:45.319 --> 00:32:49.074
In addition to this, and
again, over and above MSI,
00:32:49.074 --> 00:32:52.650
what we have are our
client access policies.
00:32:52.650 --> 00:32:56.122
But this is important to note
that some of these client access
00:32:56.122 --> 00:32:59.129
policies will block
the Office Licensing Service.
00:33:00.320 --> 00:33:03.910
That's required for licensing and
activation for Office.
00:33:03.910 --> 00:33:07.410
So if you are external
to your network and
00:33:07.410 --> 00:33:12.430
you want to come in to a licensed
Office from an external
00:33:12.430 --> 00:33:16.185
IP address or whatever the policy
that you've created, some of these
00:33:16.185 --> 00:33:20.380
will actually block that activation
and licensing process to Office.
00:33:20.380 --> 00:33:23.140
You may be seeing activation
errors and problems there.
00:33:23.140 --> 00:33:26.010
So it's well worth
noting that actually
00:33:26.010 --> 00:33:29.478
if you're using client access
policies, then it could potentially
00:33:29.478 --> 00:33:32.910
be causing problems around your
licensing of Office as well.
00:33:32.910 --> 00:33:35.650
However, we do have conditional
access that you can use.
00:33:35.650 --> 00:33:39.940
This is a superset of
the client access policies.
00:33:39.940 --> 00:33:43.060
You'll see these things in things
like Active Directory Federation
00:33:43.060 --> 00:33:47.430
Services 3.0, Azure Active directory
premium, those kind of things.
00:33:47.430 --> 00:33:51.698
And then allow you to secure
your environment in a more
00:33:51.698 --> 00:33:57.030
granular compliant mechanism.
00:33:57.030 --> 00:34:01.340
And of course, modern
authentication, now allowing you
00:34:01.340 --> 00:34:04.670
to take advantage of things like
multi-factor authentication for
00:34:04.670 --> 00:34:05.850
Office.
00:34:05.850 --> 00:34:09.280
So once again,
if your users are in Office 365 and
00:34:09.280 --> 00:34:12.900
you're authenticating through
to Active Directory or
00:34:12.900 --> 00:34:18.170
even the cloud, you are able to wrap
around multi-factor authentication.
00:34:18.170 --> 00:34:22.510
Prompting users to enter in a PIN
number, or answer a text message, or
00:34:22.510 --> 00:34:23.730
a telephone call, or
00:34:23.730 --> 00:34:29.660
even use the phone factor app to
authenticate going into Office.
00:34:29.660 --> 00:34:34.230
So things like Outlook, that can
now use the modern authentication
00:34:34.230 --> 00:34:37.980
platform to ensure that,
if your device changes location,
00:34:39.340 --> 00:34:41.060
in the morning,
you're in the office that's fine.
00:34:41.060 --> 00:34:44.500
In the afternoon you go to a cafe,
and
00:34:44.500 --> 00:34:48.140
you get Internet on an external IP
address, you may want to implement
00:34:48.140 --> 00:34:52.270
more structured authentication when
they land on an external IP address.
00:34:52.270 --> 00:34:53.640
You can absolutely do that.
00:34:53.640 --> 00:34:55.982
Challenge for
multi-factor authentication and
00:34:55.982 --> 00:34:58.050
ensure you're working
with secure model.
00:35:00.810 --> 00:35:02.010
So licensing and activation.
00:35:02.010 --> 00:35:04.630
No key management
service is required.
00:35:04.630 --> 00:35:06.100
So no KMS.
00:35:06.100 --> 00:35:09.090
And no product keys for
the multiple activation keys.
00:35:09.090 --> 00:35:10.680
We don't need the MAK keys anymore.
00:35:10.680 --> 00:35:12.310
It's online activation.
00:35:12.310 --> 00:35:15.677
So you're essentially
outsourcing the licensing and
00:35:15.677 --> 00:35:19.010
activation mechanisms to Microsoft.
00:35:19.010 --> 00:35:22.856
Again, taking into consideration
those client access policies,
00:35:22.856 --> 00:35:23.868
but ultimately,
00:35:23.868 --> 00:35:28.360
what we are doing here is you're
giving us the online activation.
00:35:28.360 --> 00:35:32.140
It does require Internet access
at least once every 30 days.
00:35:32.140 --> 00:35:36.903
If you're an organization that is
potentially research or government,
00:35:36.903 --> 00:35:41.125
and you have machines that will
never see the light of the Internet
00:35:41.125 --> 00:35:41.679
at all.
00:35:41.679 --> 00:35:43.325
They're 100% locked down.
00:35:43.325 --> 00:35:45.820
They will never get
an Internet connection.
00:35:45.820 --> 00:35:49.202
Then we advise you to go
MSI traditional Office on
00:35:49.202 --> 00:35:50.700
the latest version.
00:35:50.700 --> 00:35:53.460
Because if that can't
get to the Internet,
00:35:53.460 --> 00:35:54.960
then you will not be
able to license it or
00:35:54.960 --> 00:35:58.160
maintain the activation on there,
so that's just something to note.
00:35:58.160 --> 00:36:01.360
If you're in a lockdown environment,
go traditional Office,
00:36:03.010 --> 00:36:05.410
because it will move into
reduced functionality mode.
00:36:05.410 --> 00:36:08.180
So we still have Office in there,
but it's view and print only.
00:36:09.400 --> 00:36:11.260
If you're seeing problems
with your licensing and
00:36:11.260 --> 00:36:16.430
activation, we can use the Office
software protection platform.
00:36:16.430 --> 00:36:20.060
And there's a set of tools that
allow you to run activation,
00:36:20.060 --> 00:36:21.850
force activation.
00:36:21.850 --> 00:36:26.370
You'll also be able to do things
like check the activation status,
00:36:26.370 --> 00:36:27.300
and check the product key.
00:36:27.300 --> 00:36:29.360
And if you're having a problem, and
00:36:29.360 --> 00:36:34.412
you call up support,
use the OSPP.vbs,
00:36:34.412 --> 00:36:38.670
run the activation and
the statuses, and
00:36:38.670 --> 00:36:41.540
actually go and get the logs as
well and send them over to us,
00:36:41.540 --> 00:36:46.540
cuz when you're running the OSPP.vbs
it will run logging for you as well.
00:36:46.540 --> 00:36:48.770
So there is some information
around troubleshooting and
00:36:48.770 --> 00:36:50.210
logging I'm happy to provide you.
00:36:52.500 --> 00:36:57.140
So let's take a quick look at
the activation activities.
00:36:57.140 --> 00:36:58.986
So at time of install,
00:36:58.986 --> 00:37:03.740
we have an initial
registration of the computer.
00:37:03.740 --> 00:37:07.240
We send the org ID, the machine key,
the machine name, and
00:37:07.240 --> 00:37:08.260
the machine ID.
00:37:08.260 --> 00:37:12.989
This allows us to track how many
machines have been activated.
00:37:12.989 --> 00:37:17.160
Because we have that
five PC MAC activation.
00:37:17.160 --> 00:37:21.930
Which means as an IT organization,
something we announced on some
00:37:21.930 --> 00:37:26.030
blog posts and Ignite,
we now have the ability for
00:37:26.030 --> 00:37:29.590
IT administrators to manage
these activations as well.
00:37:29.590 --> 00:37:32.330
So, previously, it would have to
be a user going into the portal.
00:37:32.330 --> 00:37:34.780
They would see their
list of machines.
00:37:34.780 --> 00:37:36.590
If they wanted to
activate a sixth one,
00:37:36.590 --> 00:37:38.750
they'd have to go in and
deactivate one.
00:37:38.750 --> 00:37:41.470
Well, now an IT administrator
can actually go in and
00:37:41.470 --> 00:37:43.780
deactivate one on a user's behalf.
00:37:45.750 --> 00:37:48.590
And then we have
a Subscription Status Check and
00:37:48.590 --> 00:37:50.110
a Product Key Management Check.
00:37:50.110 --> 00:37:52.710
So, these go out on
a regular basis and
00:37:52.710 --> 00:37:55.540
they do things like ensure
that you're still licensed.
00:37:55.540 --> 00:37:59.529
And also they deliver that
product key to you as well.
00:37:59.529 --> 00:38:03.167
So we make sure that
information comes down and
00:38:03.167 --> 00:38:05.040
gets checked back out.
00:38:05.040 --> 00:38:08.820
And this will maintain Office
in full functionality mode.
00:38:08.820 --> 00:38:11.330
And this is why we need to
have Internet connection,
00:38:11.330 --> 00:38:15.210
because it needs to hit the service
at least once every 30 days.
00:38:18.540 --> 00:38:22.480
So, what's a Microsoft
presentation without an eye check?
00:38:22.480 --> 00:38:25.670
So, what we have here is the ports,
00:38:25.670 --> 00:38:29.000
protocols, and URLs for
Office 365 ProPlus.
00:38:29.000 --> 00:38:32.010
You can go to Bing,
type in this title, and
00:38:32.010 --> 00:38:33.730
find all this information.
00:38:33.730 --> 00:38:39.070
I just thought this is worth
highlighting again here.
00:38:39.070 --> 00:38:44.520
The key thing to notice
here is actually what we
00:38:46.610 --> 00:38:51.600
have are things like the local
system account being used,
00:38:51.600 --> 00:38:56.360
and we also have the logged
on user being used as well.
00:38:56.360 --> 00:39:02.140
So, it's important when we think
about proxies, and managing proxies,
00:39:02.140 --> 00:39:06.090
that we take into consideration
the URLs that we need to whitelist.
00:39:06.090 --> 00:39:09.014
We need to allow direct access to.
00:39:13.727 --> 00:39:15.395
So Local System account and
00:39:15.395 --> 00:39:18.230
User account require
a proxy configuration.
00:39:18.230 --> 00:39:21.036
And you can use
the Automatic Proxy files.
00:39:21.036 --> 00:39:23.920
There's the proxy.pac files.
00:39:23.920 --> 00:39:26.850
Worthwhile noting,
don't put it on a file location.
00:39:26.850 --> 00:39:28.760
See if you can serve that
up via the web server.
00:39:30.240 --> 00:39:34.030
And here's just an example
PAC file we're using here.
00:39:34.030 --> 00:39:38.930
So what we're saying is that
an example set of domains, and
00:39:38.930 --> 00:39:40.730
this isn't a definitive list here.
00:39:40.730 --> 00:39:43.360
You need to check the tenant
articles for the full list.
00:39:43.360 --> 00:39:44.790
But just a sample here.
00:39:44.790 --> 00:39:48.183
What we're doing here is
we're bypassing the proxy to
00:39:48.183 --> 00:39:52.325
these services, to ensure that
we can maintain that activation.
00:39:56.093 --> 00:39:57.728
And language packs of course.
00:39:57.728 --> 00:40:01.162
In MSI world, there was a level
of well, I need to go and
00:40:01.162 --> 00:40:03.119
purchase a new language pack.
00:40:03.119 --> 00:40:06.427
Language packs in Office 365
ProPlus, the user subscription.
00:40:06.427 --> 00:40:07.739
They come with it.
00:40:07.739 --> 00:40:12.066
You're able to download
those language packs, and
00:40:12.066 --> 00:40:15.114
bring them into your
source files and
00:40:15.114 --> 00:40:20.250
your network locations and
then distribute them out.
00:40:20.250 --> 00:40:23.040
We do advise you do this
at the time of install.
00:40:23.040 --> 00:40:26.300
So you can use the Office deployment
tool to download all the languages
00:40:26.300 --> 00:40:27.550
that you need, and
00:40:27.550 --> 00:40:31.490
then to install the languages that
you are going to require after that.
00:40:31.490 --> 00:40:34.720
We can do things like the language
interface patch, the proofing tools,
00:40:34.720 --> 00:40:37.450
the spoofing languages
after the fact,
00:40:37.450 --> 00:40:42.560
using those MSI language packs, but
we do actually advise you to port
00:40:42.560 --> 00:40:45.690
that into the core source before,
then, going ahead and deploying.
00:40:47.180 --> 00:40:50.340
And the first language
determines the Shell UI.
00:40:50.340 --> 00:40:53.640
If you want to change
the core language of Office,
00:40:53.640 --> 00:40:56.660
you need to rerun
the office deployment tool
00:40:56.660 --> 00:40:59.400
with that language on the top
of the language ID list.
00:41:00.400 --> 00:41:04.360
So, we do get a few questions around
well I need to change the shell UI,
00:41:04.360 --> 00:41:08.570
language packs are fine, but
I need to change the core language.
00:41:08.570 --> 00:41:13.309
You need to rerun the configuration
file in the Office deployment tool
00:41:13.309 --> 00:41:15.650
to change that shell UI language.
00:41:19.503 --> 00:41:20.500
So, what about testing?
00:41:21.830 --> 00:41:24.600
Side by side on the client.
00:41:24.600 --> 00:41:32.020
So the answer to side by side
is legacy versions of Office MSI
00:41:32.020 --> 00:41:37.660
can run side by side with the latest
version of Office 365 ProPlus.
00:41:37.660 --> 00:41:42.794
So moving forward, or
we have 2016, Office 2016 and
00:41:42.794 --> 00:41:47.537
V16 Office 365 ProPlus as
the version number behind
00:41:47.537 --> 00:41:52.094
Office 2016 will run with
legacy versions of MSI.
00:41:52.094 --> 00:41:56.395
So if you have Office 2013
Professional Plus MSI, or
00:41:56.395 --> 00:42:01.324
Office 2013 Standard MSI and
you want to move to Office 365
00:42:01.324 --> 00:42:05.265
ProPlus Version 16 released
later on in the year,
00:42:05.265 --> 00:42:10.270
you can run those side-by-side,
but not the same version.
00:42:10.270 --> 00:42:14.690
So side-by-side,
Office 2013, MSI, and
00:42:14.690 --> 00:42:21.490
Office 365 ProPlus today, we don't
support side-by-side on a client.
00:42:21.490 --> 00:42:24.290
That's not to say that technically
you can't go and achieve that.
00:42:24.290 --> 00:42:25.910
But it's not a supported mechanism.
00:42:28.090 --> 00:42:29.570
We don't advise that.
00:42:29.570 --> 00:42:33.130
And the main reason is, actually,
because there are shared DLL's there
00:42:33.130 --> 00:42:36.290
and they'll start
to cause conflicts.
00:42:36.290 --> 00:42:40.579
We do include Project and
Visio 2013 into this mix.
00:42:43.290 --> 00:42:47.080
So again, just for reference,
here we have our supported and
00:42:47.080 --> 00:42:48.440
unsupported.
00:42:48.440 --> 00:42:52.770
I need to highlight now,
this is a point in time reference,
00:42:52.770 --> 00:42:55.450
as in this is what's
happening today.
00:42:55.450 --> 00:42:58.500
Please don't take this ahead
when we release 2016 and
00:42:58.500 --> 00:43:01.510
say, hey you know,
this chart's wrong.
00:43:01.510 --> 00:43:04.220
This is a point in time chart,
so it's worth while noting that.
00:43:04.220 --> 00:43:08.281
But you see here we're
bringing in Visio and
00:43:08.281 --> 00:43:12.781
Project as well because
we need to support well,
00:43:12.781 --> 00:43:16.952
we do support Office
365 ProPlus fit to run
00:43:16.952 --> 00:43:21.696
with legacy versions of
Visio MSI and Project MSI.
00:43:21.696 --> 00:43:25.412
But if you bring it up
into the Office Project or
00:43:25.412 --> 00:43:30.560
Visio MSI 2013 with Office
365 ProPlus fit to run today,
00:43:30.560 --> 00:43:34.560
that's not going to
be a supported model.
00:43:34.560 --> 00:43:36.960
So it's either all click-to-run,
or all MSI.
00:43:38.280 --> 00:43:41.630
Your alternatives there are to
virtualize one or the other.
00:43:41.630 --> 00:43:44.920
So you can virtualize it,
push it out using Remote App or
00:43:44.920 --> 00:43:48.849
Azure Remote App and virtualize
one of those versions if needs be.
00:43:55.560 --> 00:43:57.514
So what are our deployment choices?
00:43:57.514 --> 00:43:58.779
Oh we have a question.
00:43:58.779 --> 00:44:03.979
>> So can we have a side by side
32 bit version and 64 bit version?
00:44:03.979 --> 00:44:07.477
>> Okay so the question is can we
have a side by side 32 bit version
00:44:07.477 --> 00:44:08.731
and 64 bit version?
00:44:08.731 --> 00:44:11.476
No we don't support 32 bit.
00:44:11.476 --> 00:44:14.837
It needs to be the same
architecture, so 32 and 32 or
00:44:14.837 --> 00:44:15.774
64 and 64.
00:44:15.774 --> 00:44:19.526
Again, to overcome that,
you can virtualize 64 bits and
00:44:19.526 --> 00:44:22.678
deliver that using remote app,
for example, and
00:44:22.678 --> 00:44:25.920
deliver 32 bit architecture
on the rich client.
00:44:27.000 --> 00:44:27.500
Thanks.
00:44:30.530 --> 00:44:34.102
Okay, so let's take a look at some
of our deployment methods for
00:44:34.102 --> 00:44:35.516
Office 365 ProPlus.
00:44:35.516 --> 00:44:41.580
So local installation,
we can as an end user,
00:44:41.580 --> 00:44:45.920
if I have local admin rights,
I can go to the Office 365 portal,
00:44:45.920 --> 00:44:50.740
I can download, and I can install
Office 365 ProPlus myself.
00:44:50.740 --> 00:44:54.630
As IT pros,
you can switch off that capability,
00:44:54.630 --> 00:44:58.338
ensuring that when users go
there to the Office 365 portal,
00:44:58.338 --> 00:45:01.760
that they are not able to
download Office themselves.
00:45:01.760 --> 00:45:03.380
So if you want to control Office and
00:45:03.380 --> 00:45:06.760
have that in a managed environment,
you can switch that off.
00:45:08.050 --> 00:45:11.640
And as an end user, if you wanted
to, you could go ahead and
00:45:11.640 --> 00:45:13.520
download the Office deployment tool,
and
00:45:13.520 --> 00:45:18.280
run setup.exe/configure,
pass the configuration file, and
00:45:18.280 --> 00:45:20.790
it'll stream it from
a content delivery network.
00:45:20.790 --> 00:45:25.570
Or customize that configuration.xml
and have it point to a local file
00:45:25.570 --> 00:45:27.969
store or
distribution point of your choice.
00:45:29.010 --> 00:45:31.830
But this has essentially
installed it on the local machine.
00:45:31.830 --> 00:45:34.810
And then we have
network installation.
00:45:34.810 --> 00:45:37.760
So again, the Office Deployment Tool
plays a key part for
00:45:37.760 --> 00:45:39.260
our managed deployments.
00:45:39.260 --> 00:45:42.820
If you want to place the source
files on a network file
00:45:42.820 --> 00:45:45.460
share, do that.
00:45:45.460 --> 00:45:48.470
And then you can deliver
the Office Deployment Tool locally
00:45:48.470 --> 00:45:53.290
to the clients, and that will
allow you to run setup.exe,
00:45:53.290 --> 00:45:55.850
pass the configuration file into it,
00:45:55.850 --> 00:45:59.760
ensuring that your source path
is pointing to that file share.
00:45:59.760 --> 00:46:04.678
And it'll stream the install from
a network installation point.
00:46:04.678 --> 00:46:08.160
And then our Enterprise Software
Distribution Mechanisms.
00:46:08.160 --> 00:46:09.740
System Center Configuration Manager.
00:46:09.740 --> 00:46:12.190
So could I just get a show of hands.
00:46:12.190 --> 00:46:14.870
How many people here today are using
System Center Configuration Manager?
00:46:16.290 --> 00:46:18.310
Okay so a very large amount.
00:46:18.310 --> 00:46:20.090
How many people are using LandDesk?
00:46:20.090 --> 00:46:23.440
A couple of people
are using LandDesk, cool.
00:46:23.440 --> 00:46:24.250
How about BigFix?
00:46:26.080 --> 00:46:27.960
Two or three people, okay great.
00:46:27.960 --> 00:46:29.686
So you can still use those tools.
00:46:29.686 --> 00:46:31.536
All of the tools,
all of the players for
00:46:31.536 --> 00:46:33.840
Enterprise Software Distribution.
00:46:33.840 --> 00:46:36.786
You can use those with
Office 365 ProPlus.
00:46:36.786 --> 00:46:42.127
We're still leveraging setup.exe,
and passing a configuration file,
00:46:42.127 --> 00:46:47.398
so you still have that capability to
deliver that using those platforms.
00:46:47.398 --> 00:46:51.232
And we actually have a very good
case study for LAN desk actually,
00:46:51.232 --> 00:46:55.020
and I'll get onto that in the,
later part of the presentation.
00:46:55.020 --> 00:46:57.670
And of course we can leverage the
Microsoft InTune platform as well if
00:46:57.670 --> 00:46:59.990
you want to enable
those remote users.
00:46:59.990 --> 00:47:02.450
Still deliver Office in
an managed environment.
00:47:02.450 --> 00:47:03.220
A controlled way.
00:47:03.220 --> 00:47:05.470
You want to control
the target versions.
00:47:05.470 --> 00:47:08.140
You want to control the update
settings those kind of things.
00:47:08.140 --> 00:47:10.995
You can absolutely deliver
those through Microsoft InTune.
00:47:12.170 --> 00:47:16.440
And you can even put it in
a golden image, a Windows image.
00:47:17.760 --> 00:47:21.920
Install the app build,
ensure that it's not activated,
00:47:21.920 --> 00:47:25.520
ensure that you are rearming it,
and then sys prep it.
00:47:25.520 --> 00:47:28.020
You can put that to the side.
00:47:28.020 --> 00:47:31.180
And that allows you to then
use Office 365 ProPlus.
00:47:31.180 --> 00:47:32.570
When you deploy that build and
00:47:32.570 --> 00:47:36.780
expand it, you can configure it to
go out and get the latest updates.
00:47:36.780 --> 00:47:39.880
Remember that it's only gonna
pull the differences between
00:47:39.880 --> 00:47:42.840
what's installed and
what you're making available.
00:47:42.840 --> 00:47:46.730
It's not gonna go and sequentially
look for lots of service packs or
00:47:46.730 --> 00:47:47.990
lots of updates.
00:47:47.990 --> 00:47:50.330
It's gonna go ahead and
get the latest build, or
00:47:50.330 --> 00:47:52.110
whichever build that you're
specifying in there.
00:47:53.530 --> 00:47:56.880
And then, when a user wants to log
on, they can then activate that.
00:47:56.880 --> 00:47:59.170
If you're using Active Directory
Federation Services or
00:47:59.170 --> 00:48:02.010
another single-sided provider,
you can suppress those
00:48:02.010 --> 00:48:05.030
notifications in the sign-in and
you can just start Office.
00:48:06.310 --> 00:48:08.480
And we can run this in
Application Virtualization.
00:48:08.480 --> 00:48:09.746
We can use AppV 5.
00:48:10.770 --> 00:48:13.780
And using the office deployment
tool, we can flatten the package,
00:48:13.780 --> 00:48:16.560
and deliver it as an AP V package.
00:48:16.560 --> 00:48:20.320
It's not a case of wrapping
up Office, installing it,
00:48:20.320 --> 00:48:21.910
wrapping it up, and delivering it.
00:48:21.910 --> 00:48:25.925
The office deployment tool will take
out all your task sequencing, and
00:48:25.925 --> 00:48:31.970
it will just run setup.exe/packager,
pass it to the configuration file,
00:48:31.970 --> 00:48:34.310
and it will flatten it and
it will do everything for
00:48:34.310 --> 00:48:37.500
you and then you can load that
into your App-V environment so
00:48:37.500 --> 00:48:38.710
we can still deliver via App-V.
00:48:38.710 --> 00:48:42.760
And then remote desktop services and
virtual infrastructures.
00:48:42.760 --> 00:48:47.240
So we can deliver Office 365
ProPlus using remote app or
00:48:47.240 --> 00:48:48.748
as your remote app.
00:48:48.748 --> 00:48:50.560
And virtual desktop
environments like VDI,
00:48:50.560 --> 00:48:54.100
both persistent and
bold flavors of that.
00:48:54.100 --> 00:48:58.470
And we can use shared computer
activation which allows us
00:48:58.470 --> 00:49:03.790
to actually install Office 365
ProPlus in a shared environment.
00:49:03.790 --> 00:49:06.660
Whether it's a physical machine or
a virtual machine.
00:49:06.660 --> 00:49:09.455
And that session,
when a user logs in,
00:49:09.455 --> 00:49:12.900
they don't count towards
your five by five by five.
00:49:12.900 --> 00:49:17.470
So you can have multiple
Remote Desktop Services or
00:49:17.470 --> 00:49:22.280
virtual desktop infrastructure
sessions running with 365 ProPlus.
00:49:22.280 --> 00:49:25.590
But not have it count
towards that license account.
00:49:28.720 --> 00:49:33.222
So what we're ultimately saying,
is that MSI versus Click-to-Run,
00:49:33.222 --> 00:49:36.100
we have exactly the same
deployment options,
00:49:36.100 --> 00:49:38.560
just like any other
version of Office.
00:49:40.140 --> 00:49:43.449
And this is, I think this is
well worth highlighting here,
00:49:43.449 --> 00:49:47.292
it's actually local network
enterprise distribution application
00:49:47.292 --> 00:49:49.423
virtualization, remote sessions.
00:49:49.423 --> 00:49:53.949
It all works and you have those
options available to you.
00:50:03.653 --> 00:50:07.700
So lets take a quick look at the
System Center Configuration Manager.
00:50:07.700 --> 00:50:11.580
And again,
this could very well apply to
00:50:11.580 --> 00:50:15.720
other distribution software,
ultimately what we do is we go and
00:50:15.720 --> 00:50:18.490
get the Office Deployment Tool,
I have that, great,
00:50:18.490 --> 00:50:19.770
I'm going to expand that.
00:50:19.770 --> 00:50:22.740
I got my setup.exe, and
I've got configuration files.
00:50:22.740 --> 00:50:26.705
And I can make as many
configuration files as I like.
00:50:26.705 --> 00:50:29.610
And then use that
deployment tool to go and
00:50:29.610 --> 00:50:31.300
download the source files for
office.
00:50:31.300 --> 00:50:33.100
So I now have those available to me.
00:50:33.100 --> 00:50:37.867
I've selected the version that
I want and I have that locally.
00:50:37.867 --> 00:50:38.800
I then can go in and
00:50:38.800 --> 00:50:41.664
create an application in
Configuration Manager, and
00:50:41.664 --> 00:50:45.800
I can distribute the application
to all my distribution points.
00:50:45.800 --> 00:50:49.646
I can then deploy and using
System Center Configuration Manager,
00:50:49.646 --> 00:50:54.340
2012 R2, we have it user aware and
device aware,
00:50:54.340 --> 00:50:58.540
so you can deploy it to a particular
user or set of users or
00:50:58.540 --> 00:51:02.310
to a particular device or
set of devices.
00:51:02.310 --> 00:51:05.940
And again there is another session
that's already been played out this
00:51:05.940 --> 00:51:10.890
week around deploying Office 365
ProPlus using Configuration Manager.
00:51:10.890 --> 00:51:11.810
It's a bit more of a deep dive and
00:51:11.810 --> 00:51:15.910
I'll actually go through
step by step how to do this.
00:51:15.910 --> 00:51:18.770
But of course we can
also task sequence
00:51:18.770 --> 00:51:23.490
run installation of legacy versions
of Office in Configuration Manager.
00:51:23.490 --> 00:51:27.450
We do have some tools around from
our FixIT collection that will
00:51:27.450 --> 00:51:30.130
allow you to do things that clean
up legacy versions of Office.
00:51:32.340 --> 00:51:33.780
So a quick deployment overview here.
00:51:36.450 --> 00:51:39.980
So if I have my HQ,
I have my Branch Office, and
00:51:39.980 --> 00:51:42.183
I have my Remote Office
& my Remote Users.
00:51:42.183 --> 00:51:48.370
And what I can do here is, we have
the Office Content Delivery Network,
00:51:48.370 --> 00:51:52.920
using the Office Deployment Tool I
can go and get the source files and
00:51:52.920 --> 00:51:56.950
I can place them onto my systems
here, and we can then distribute
00:51:56.950 --> 00:52:00.766
those to branch offices, or
to other cloud services.
00:52:00.766 --> 00:52:04.850
And using
System Center Configuration Manager,
00:52:04.850 --> 00:52:08.160
we can pre-cache from
the distribution point
00:52:08.160 --> 00:52:10.990
onto local machines, or
we can trickle that down to them,
00:52:10.990 --> 00:52:14.280
so however long you want
that process to take.
00:52:14.280 --> 00:52:17.170
You can take the source
files locally And
00:52:17.170 --> 00:52:21.040
then what you can do is execute
setup.exe/configure, and
00:52:21.040 --> 00:52:23.960
it will look for
the local source files.
00:52:26.605 --> 00:52:30.290
And we can also stream it
from a distribution point.
00:52:30.290 --> 00:52:33.390
So here, what we're doing is
we're leaving the source files
00:52:33.390 --> 00:52:37.680
in the distribution point, and then
we're running setup.exe/configure,
00:52:37.680 --> 00:52:41.580
but pointing the source path,
up into the distribution point, and
00:52:41.580 --> 00:52:45.230
it will then run that click to
run streaming process through,
00:52:45.230 --> 00:52:47.030
down on to those local machines.
00:52:55.552 --> 00:52:59.015
And then what we're able to do for
those remote users, those people
00:52:59.015 --> 00:53:02.661
that are never in the office, maybe
you're in your sales workforce and
00:53:02.661 --> 00:53:06.247
they're out and about, actually you
don't want them calling back to
00:53:06.247 --> 00:53:09.953
the distribution point all the time,
you don't want them have to be tied
00:53:09.953 --> 00:53:13.710
to a VPN and saturate your RAM, what
we can actually then do is leverage.
00:53:15.230 --> 00:53:19.465
Again, we could use the GPO's to
automatically set that update path
00:53:19.465 --> 00:53:24.450
rr point at those client machines
to the cloud, which means
00:53:24.450 --> 00:53:27.960
that when they run an install
it's going to go to the cloud.
00:53:27.960 --> 00:53:31.541
And based upon the configuration
file settings, you can target
00:53:31.541 --> 00:53:35.053
a version for them to get from
our Content Delivery Network, so
00:53:35.053 --> 00:53:39.297
you're effectively outsourcing your
distribution points to Microsoft,
00:53:39.297 --> 00:53:41.638
and here we have global
end points there.
00:53:41.638 --> 00:53:44.253
So you're able to go out and
say wherever I am,
00:53:44.253 --> 00:53:46.880
I can always get the latest
version of Office.
00:53:55.462 --> 00:53:57.810
Well, we mentioned
Windows Imaging as well.
00:53:58.900 --> 00:54:03.590
So you can deploy during the build
and capture task sequence.
00:54:04.760 --> 00:54:08.200
Run ospprearm, and force this patch.
00:54:08.200 --> 00:54:12.290
This will clean out Office, ensure
that its not activated, ensure that
00:54:12.290 --> 00:54:17.130
there isn't a product key embedded
in Office, because if that happens,
00:54:17.130 --> 00:54:21.410
and you deploy that build there's
a product here that's listed, and
00:54:21.410 --> 00:54:25.160
it may have timed out by the time
you actually get to deploy and
00:54:25.160 --> 00:54:29.160
expand an image onto,
onto that machine.
00:54:29.160 --> 00:54:32.810
If it's four weeks plus so, more
than 30 days it's going to go into
00:54:32.810 --> 00:54:36.150
reduced functionality mode and
you may have some difficulties
00:54:36.150 --> 00:54:39.410
around proxies and firewalls and
it may say, hey, you know,
00:54:39.410 --> 00:54:43.630
I've got a product here that's been
used in a number of other builds.
00:54:43.630 --> 00:54:47.699
So what we're advising here, run
ospprearm, clean it out, capture it
00:54:47.699 --> 00:54:51.034
and then deploy it, because
what happens when it expands,
00:54:51.034 --> 00:54:54.570
it will then go out for activation
according to the user that's
00:54:54.570 --> 00:54:57.198
done that,
rather than an IT Administrator.
00:54:57.198 --> 00:55:01.018
And what we actually see here is
that if you deploy a fresh version
00:55:01.018 --> 00:55:05.477
of MSI Office, and within four weeks
before we've released any updates to
00:55:05.477 --> 00:55:09.791
that, you can have, fine I've got
the latest version, but when it gets
00:55:09.791 --> 00:55:13.753
plus four weeks, we see that build
time come that expansion time,
00:55:13.753 --> 00:55:16.569
that install time actually
increasing a lot.
00:55:16.569 --> 00:55:21.008
If you were to take, for example,
Office 2013 MSI, deliver that into
00:55:21.008 --> 00:55:25.164
a build, and then expand it, you've
got Service Pack 1 to go on, and
00:55:25.164 --> 00:55:28.968
then you've got all of those other
patches that need to go on, it
00:55:28.968 --> 00:55:32.928
could be an hour and a half before
you're up and running in Office.
00:55:32.928 --> 00:55:37.135
However, it's always the same amount
of time of click to run cuz it's
00:55:37.135 --> 00:55:40.740
only ever looking for
the next bill that you specify.
00:55:40.740 --> 00:55:44.230
It's only ever gonna take
the delta differences and
00:55:44.230 --> 00:55:46.310
download, install, and run.
00:55:46.310 --> 00:55:48.420
It's very quick, very quick.
00:55:48.420 --> 00:55:51.310
Moving forward, if you're plus
four weeks, plus six weeks,
00:55:51.310 --> 00:55:54.990
plus eight weeks, plus 12 weeks,
plus six months, it’s only gonna go
00:55:54.990 --> 00:55:58.220
out and get the differences
between the build that has and
00:55:58.220 --> 00:56:03.920
the build that your
making available to it.
00:56:03.920 --> 00:56:08.560
And again App-V, utilizing
that Office Deployment Tool.
00:56:08.560 --> 00:56:13.240
Making sure that you're able to
bring those source files down.
00:56:13.240 --> 00:56:19.078
And using setup.exe/packager, we're
able to flatten those files down and
00:56:19.078 --> 00:56:24.460
then you can input the App-V
files into your environment.
00:56:24.460 --> 00:56:28.727
And in terms of updates, what you
can do is to re-run that process,
00:56:28.727 --> 00:56:32.405
re-package the latest
version of Office and
00:56:32.405 --> 00:56:35.720
App-V will still only
take the deltas.
00:56:35.720 --> 00:56:38.240
So we're still only taking
the deltas even though you have
00:56:38.240 --> 00:56:41.790
repackaged a full version of Office.
00:56:41.790 --> 00:56:44.960
You're still only going to be doing
the delta synchronization there.
00:56:44.960 --> 00:56:48.600
And of course we can then go
ahead and get our add ins and
00:56:48.600 --> 00:56:50.680
collection groups
all configured out.
00:56:52.400 --> 00:56:55.050
So again,
use Office Deployment Tool,
00:56:55.050 --> 00:56:59.240
it does require an output path,
so setup.exe/packager,
00:56:59.240 --> 00:57:02.820
pass it the configuration file, and
then allow it, give it an output
00:57:02.820 --> 00:57:06.870
path to ensure that you've got a
location to place those App-V files.
00:57:06.870 --> 00:57:10.050
And there are some minimum
attributes here that are required in
00:57:10.050 --> 00:57:14.791
order for this process to complete
but ultimately we no longer have 20
00:57:14.791 --> 00:57:19.920
to 30 task sequences that we need
to go through for office MSI.
00:57:19.920 --> 00:57:22.730
That packager will just
do everything for you.
00:57:22.730 --> 00:57:26.963
You don't need to do anything
after you've run that.
00:57:26.963 --> 00:57:29.320
So here's an example.
00:57:29.320 --> 00:57:34.191
Office Deployment Configuration file
here, so again, setup.exe/packager,
00:57:34.191 --> 00:57:37.805
my configuration file, and
then give it the output path, and
00:57:37.805 --> 00:57:40.724
we have the minimum
allotting the Office client,
00:57:40.724 --> 00:57:45.173
here's my architecture, this is the
version, this is the product ID, and
00:57:45.173 --> 00:57:49.240
here are the languages, so that's
the minimum requirement there.
00:57:52.825 --> 00:57:54.520
And then Shared computer activation.
00:57:55.640 --> 00:58:01.750
Allowing us to deploy Office 365 Pro
Plus to our remote desktop services,
00:58:01.750 --> 00:58:07.580
so today and minimum version
of RDS that we have is
00:58:07.580 --> 00:58:13.713
2008 R2 Citrix XenApp,
is your remote up, that's fine.
00:58:13.713 --> 00:58:17.790
You can deploy to your
virtualization technologies.
00:58:17.790 --> 00:58:22.625
We did actually work with Citrix
to get this stuff working,
00:58:22.625 --> 00:58:25.140
so you'll be good there.
00:58:25.140 --> 00:58:28.121
Also installation on
a physical shared machine, so
00:58:28.121 --> 00:58:31.575
if you have factory warehouses,
if you're in a hospital and
00:58:31.575 --> 00:58:34.692
you have a nurses work station,
maybe kiosk workers,
00:58:34.692 --> 00:58:38.351
maybe they're shop floor workers
in your retail branches, and
00:58:38.351 --> 00:58:41.602
you have a machine that people
go into on a regular basis,
00:58:41.602 --> 00:58:45.530
no one owns the machine but you want
to offer an Office experience to,
00:58:45.530 --> 00:58:50.248
maybe 50% of the population, but the
other 50%, they don't have Office.
00:58:50.248 --> 00:58:53.811
You've decided you that don't
need to license them for Office,
00:58:53.811 --> 00:58:57.310
you're just delivering maybe
a kiosk licensing plan to them for
00:58:57.310 --> 00:58:58.242
Office 365.
00:58:58.242 --> 00:59:01.755
You don't need to necessarily pay
for Office for those people, but
00:59:01.755 --> 00:59:04.773
those other people who are still
using that same machine,
00:59:04.773 --> 00:59:06.280
they do have Office.
00:59:06.280 --> 00:59:08.120
How do we deal with that?
00:59:08.120 --> 00:59:10.990
We can actually deal with that
using shared computer activation,
00:59:10.990 --> 00:59:14.690
and we'll show you a little
bit about this, but again,
00:59:14.690 --> 00:59:17.717
it doesn't count
the overall 5x5 licensing.
00:59:19.350 --> 00:59:23.820
So every time I spin up
a virtual environment, or
00:59:23.820 --> 00:59:26.470
I'm going to a shared
physical machine,
00:59:26.470 --> 00:59:29.820
it's not counting to my other PC or
my other activations.
00:59:29.820 --> 00:59:33.580
I don't need to go to my IT
administrator to ask them
00:59:33.580 --> 00:59:35.720
to deactivate anything every time.
00:59:37.220 --> 00:59:39.210
So what's the user
experience look like?
00:59:41.120 --> 00:59:46.135
So first we have our Office 365
ProPlus user here, they login, it
00:59:46.135 --> 00:59:51.335
hits that Office Licensing Service,
and it's happy, it activates.
00:59:51.335 --> 00:59:54.888
So then they finish and
someone else comes along, so
00:59:54.888 --> 00:59:59.592
the User 2 comes in, logs into that,
they have a version of Office.
00:59:59.592 --> 01:00:00.555
It's fine.
01:00:00.555 --> 01:00:04.410
Remember Office is still
installed on this machine.
01:00:04.410 --> 01:00:07.270
But Office Licensing Service is
bringing up that activation.
01:00:07.270 --> 01:00:11.550
And then we have a non-Office
365 ProPlus user here.
01:00:11.550 --> 01:00:18.166
So they try and login,
and they can't login.
01:00:18.166 --> 01:00:21.686
The bits, the source files,
the application still exist on
01:00:21.686 --> 01:00:24.517
the computer, but
it's not fully activating,
01:00:24.517 --> 01:00:28.540
meaning that they can only view and
they can only print.
01:00:28.540 --> 01:00:31.230
So, it's not about removing
Office for some people and
01:00:31.230 --> 01:00:32.880
deploying Office for others.
01:00:32.880 --> 01:00:35.210
It's about having a version
of Office on there,
01:00:35.210 --> 01:00:39.610
based on their license, they can
get to use the full functionality.
01:00:39.610 --> 01:00:40.880
Because of course,
01:00:40.880 --> 01:00:45.540
those kiosk users, you may want them
to be able to read Word documents,
01:00:45.540 --> 01:00:48.340
read PowerPoint documents,
read Excel documents.
01:00:48.340 --> 01:00:49.610
In reduced functionality,
01:00:49.610 --> 01:00:52.960
which is what this will deliver to
those users, they can still do that.
01:01:00.942 --> 01:01:04.144
So there are a couple of
additional attributes when you're
01:01:04.144 --> 01:01:07.100
using the Office deployment
tool you need to run.
01:01:07.100 --> 01:01:12.180
So display level equals none and
accepts end user license agreement
01:01:12.180 --> 01:01:15.810
ensuring that they don't get a first
welcome experience when they start
01:01:15.810 --> 01:01:19.250
up, and ensuring that things
get activated nice and quickly.
01:01:19.250 --> 01:01:22.658
Also the property names, so
SharedComputerLicensing value = 1.
01:01:22.658 --> 01:01:27.230
So it's important to
set that up as well.
01:01:27.230 --> 01:01:29.770
So here's an example file of that.
01:01:29.770 --> 01:01:32.560
So you can run setup.exe/configure.
01:01:32.560 --> 01:01:35.590
You can even make registry
changes as well, so
01:01:35.590 --> 01:01:39.080
there are two options for
doing this.
01:01:39.080 --> 01:01:43.050
So you can apply the configuration
file at the time of install or
01:01:43.050 --> 01:01:47.270
you can modify the registry key and
add that shared computer licensing
01:01:47.270 --> 01:01:51.400
with a setting of =1 to
change a physical machine or
01:01:51.400 --> 01:01:54.060
a virtual machine over to
share computer activation.
01:01:57.341 --> 01:02:00.671
>> So, the activation didn't
happen for those computers?
01:02:00.671 --> 01:02:03.748
Is it shared or what?
01:02:03.748 --> 01:02:05.772
>> So the question is,
is there activation for
01:02:05.772 --> 01:02:06.927
those shared machines?
01:02:06.927 --> 01:02:10.670
There is temporary activation for
those users who have licenses.
01:02:10.670 --> 01:02:14.570
So any user who comes to a shared
machine, and they log in,
01:02:14.570 --> 01:02:19.090
and they start up Office,
if you're using single sign on,
01:02:19.090 --> 01:02:21.450
it'll seamlessly log
them into Office.
01:02:21.450 --> 01:02:24.160
If you're not using single sign on,
they'll be prompted for
01:02:24.160 --> 01:02:26.230
their username and
password credentials.
01:02:26.230 --> 01:02:28.610
That will then temporarily
activate Office for
01:02:28.610 --> 01:02:30.720
the duration of their session.
01:02:30.720 --> 01:02:33.290
If they then log off and
another user logs in,
01:02:33.290 --> 01:02:35.220
they'll be prompted for
the same username and password.
01:02:35.220 --> 01:02:37.390
If they don't have a user license,
01:02:37.390 --> 01:02:40.160
it won't activate and it'll just
be in reduced functionality mode.
01:02:40.160 --> 01:02:42.480
And if that person
then logs off again and
01:02:42.480 --> 01:02:45.900
someone else comes along
they'll be prompted for log in.
01:02:45.900 --> 01:02:50.580
They'll see the sign on and
Office will then activate, and
01:02:50.580 --> 01:02:52.830
then they'll get to use Office.
01:02:52.830 --> 01:02:54.330
It's a temporary activation.
01:02:54.330 --> 01:02:57.070
So if the same person comes
back to that same session
01:02:57.070 --> 01:02:58.740
they won't be prompted again.
01:02:58.740 --> 01:03:01.440
Unless they leave it, say,
five, six, seven, eight, nine,
01:03:01.440 --> 01:03:02.940
ten days to come back
to that session,
01:03:02.940 --> 01:03:06.440
in which case that the token is
likely to be expired by that point.
01:03:06.440 --> 01:03:08.290
So it's a tamper activation,
01:03:08.290 --> 01:03:13.170
conversely with the full version
with a non-shared computer machine,
01:03:13.170 --> 01:03:15.650
it is every 30 days that
that process is happening.
01:03:15.650 --> 01:03:17.050
So effectively,
what we're doing is we're but
01:03:17.050 --> 01:03:19.950
shrinking that activation
life cycle down.
01:03:24.070 --> 01:03:26.580
So, uninstallation of Office.
01:03:26.580 --> 01:03:29.489
So again we do have fix
it that's out there,
01:03:29.489 --> 01:03:34.890
that will allow you to go through an
uninstall legacy versions of Office.
01:03:34.890 --> 01:03:37.474
This is also supported for
pro plus, and
01:03:37.474 --> 01:03:41.357
there is also a mechanism using
the click to run technology.
01:03:41.357 --> 01:03:44.750
You can actually pass it,
set up run Wenc/configure.
01:03:44.750 --> 01:03:50.181
Then pass a configuration file that
includes the remove tags rather
01:03:50.181 --> 01:03:55.422
then the add tags and that will
actually remove things like Office
01:03:55.422 --> 01:04:01.030
365 ProPlus, Visio project,
all the click to run flavors.
01:04:01.030 --> 01:04:02.690
So in terms of click-to-run,
01:04:02.690 --> 01:04:07.060
we can remove click-to-run software
using the Office deployment tools.
01:04:10.420 --> 01:04:16.790
So how do we manage the builds
in terms of Office 365 ProPlus?
01:04:16.790 --> 01:04:21.860
Well to start with updates,
we have three update mechanisms.
01:04:21.860 --> 01:04:25.020
So we have the scheduled
task that gets deployed
01:04:25.020 --> 01:04:27.050
at time of installation.
01:04:27.050 --> 01:04:29.690
And again,
these things can be tweaked and
01:04:29.690 --> 01:04:30.940
changed using group policy.
01:04:31.960 --> 01:04:35.180
User initiated, so
a user can go into Office,
01:04:35.180 --> 01:04:39.010
click on I want to update Office,
and they can update from there.
01:04:39.010 --> 01:04:40.700
Using group policy.
01:04:40.700 --> 01:04:44.680
IT administrators can remove
this from the user interface,
01:04:44.680 --> 01:04:49.130
so you can ensure that your users
cannot update Office themselves.
01:04:49.130 --> 01:04:51.010
So we can remove this.
01:04:51.010 --> 01:04:52.900
And then we have Command-line.
01:04:52.900 --> 01:04:56.600
So you can use things like system
center configuration manager,
01:04:56.600 --> 01:05:01.850
package up our Office C2R Client,
actually push
01:05:01.850 --> 01:05:07.020
that out to those client machines
to force the update process.
01:05:07.020 --> 01:05:12.120
So we're able to by the minute pa
the scheduled task, allow users to
01:05:12.120 --> 01:05:15.890
update it, or force the command-line
down to get that working.
01:05:21.120 --> 01:05:26.810
So again, we have a range
of group policy controls.
01:05:26.810 --> 01:05:33.220
These mechanisms can be configured
at time of install but we also have
01:05:33.220 --> 01:05:38.918
group policy to dynamically
update these settings as well.
01:05:42.539 --> 01:05:46.540
So let's have a quick overview
of the upgrade process.
01:05:46.540 --> 01:05:50.120
So, if we want to go ahead and we
01:05:50.120 --> 01:05:54.820
want to trigger an upgrade process
it will look for a new build.
01:05:54.820 --> 01:05:56.290
If that new build is available,
01:05:56.290 --> 01:05:59.930
it will then go and
download Delta differences.
01:05:59.930 --> 01:06:03.220
If we're going from one version,
say 15.1 to 15.2, only skipping
01:06:03.220 --> 01:06:08.060
a version, we do something
called Delta Binary Compression.
01:06:08.060 --> 01:06:12.590
Reducing that download size from
either the content delivery network,
01:06:12.590 --> 01:06:14.850
or that local installation
point by up to 80%.
01:06:14.850 --> 01:06:19.590
So it's a significant reduction
on the bandwidth required.
01:06:19.590 --> 01:06:22.800
And if you'll then ready to apply,
we'll go through and
01:06:22.800 --> 01:06:25.400
check if the Office
processes are running.
01:06:25.400 --> 01:06:29.610
If the Office processes are running,
it won't update Office.
01:06:29.610 --> 01:06:32.670
But if we close them down,
we can update Office.
01:06:32.670 --> 01:06:36.830
And updating Office is actually
just an application restart.
01:06:36.830 --> 01:06:39.510
So you can update Office
on a very rapid basis,
01:06:39.510 --> 01:06:43.810
on a monthly basis with very little
impact with business and users.
01:06:43.810 --> 01:06:46.980
It does in place restart and
01:06:46.980 --> 01:06:50.260
it allow you to pick up from
exactly where you were.
01:06:50.260 --> 01:06:53.120
At point of restart, or
that application restart.
01:06:53.120 --> 01:06:54.900
It doesn't require an operating
system system restart,
01:06:54.900 --> 01:06:58.020
and it doesn't require you to
scrub Office like it does with
01:06:58.020 --> 01:06:59.950
an MSI version.
01:06:59.950 --> 01:07:02.780
It just does an in-place upgrade.
01:07:02.780 --> 01:07:08.170
So we can really deliver an agile
update mechanism to the business and
01:07:08.170 --> 01:07:11.260
to your end users,
just by restarting Office.
01:07:11.260 --> 01:07:14.790
And it will give them back
exactly the place they're in.
01:07:14.790 --> 01:07:16.750
If it's a complex
calculation in Excel,
01:07:16.750 --> 01:07:20.170
if they're working on a PowerPoint
document, it will close Office.
01:07:20.170 --> 01:07:22.990
Anywhere from 30 seconds
to two minutes later it
01:07:22.990 --> 01:07:25.710
will restart Office and
you're on a new version.
01:07:25.710 --> 01:07:27.830
It is that simple.
01:07:27.830 --> 01:07:30.891
It really reduces the disruption
from moving forward with Office.
01:07:37.418 --> 01:07:39.430
We're also able to roll back.
01:07:39.430 --> 01:07:42.060
So again, we can leverage things
like assistance configuration
01:07:42.060 --> 01:07:48.280
manager or use that OfficeC2R.exe to
downgrade as well as update Office.
01:07:48.280 --> 01:07:52.810
So it's just a series of builds,
specifying those builds.
01:07:52.810 --> 01:07:58.270
In the command line can take you
to another version of Office.
01:07:58.270 --> 01:08:02.720
It's not necessarily backwards and
forwards, it's just another version.
01:08:02.720 --> 01:08:07.540
So what we see here in our example,
I can go to the command prompt or
01:08:07.540 --> 01:08:08.630
PowerShell.
01:08:08.630 --> 01:08:11.330
I can find the Office C2R client.
01:08:11.330 --> 01:08:16.678
The ClientX64 because this is where
the particular has been installed.
01:08:16.678 --> 01:08:22.770
OfficeC2rClient.exe /update
forappshutdown=True so
01:08:22.770 --> 01:08:24.330
we're forcing application restart.
01:08:24.330 --> 01:08:27.390
Do we want to display anything to
the end user we can add true or
01:08:27.390 --> 01:08:28.240
false.
01:08:28.240 --> 01:08:30.530
And then update to
a particular version.
01:08:30.530 --> 01:08:32.470
And now we need to control
that very quickly.
01:08:32.470 --> 01:08:38.490
And finally training our end users.
01:08:38.490 --> 01:08:41.240
So now we have a very
agile mechanism for
01:08:41.240 --> 01:08:43.680
delivering office to our end users.
01:08:43.680 --> 01:08:48.550
There's a whole range of resources
that we're making available to you
01:08:48.550 --> 01:08:51.540
to pre warn your users that
a new feature's coming.
01:08:51.540 --> 01:08:53.880
To be sure that your
users can be trained and
01:08:53.880 --> 01:08:56.450
up to date on the latest features.
01:08:56.450 --> 01:08:57.150
Rather than say,
01:08:57.150 --> 01:08:59.570
hey, three years later we've
got all of this new stuff.
01:08:59.570 --> 01:09:00.600
The UI has changed.
01:09:00.600 --> 01:09:03.460
Look at the new features and
functionality.
01:09:03.460 --> 01:09:04.910
We gotta find all of
these controls again.
01:09:04.910 --> 01:09:07.670
Well actually we are going to make
all of this stuff available to
01:09:07.670 --> 01:09:09.440
you in advance.
01:09:09.440 --> 01:09:12.360
You can take advantage of our
resources, of our training videos,
01:09:12.360 --> 01:09:13.880
our documentation.
01:09:13.880 --> 01:09:15.530
Create and write a newsletter.
01:09:15.530 --> 01:09:16.120
Push it out.
01:09:16.120 --> 01:09:18.050
So we're gonna have a new
version of Office this month.
01:09:18.050 --> 01:09:19.280
This is the very latest.
01:09:19.280 --> 01:09:21.750
It's taking advantage of
groups in Office 365.
01:09:21.750 --> 01:09:22.870
And here's a video.
01:09:22.870 --> 01:09:26.730
And point your users
to our resources.
01:09:26.730 --> 01:09:30.010
Insure that you can deliver
an agile business experience.
01:09:30.010 --> 01:09:33.550
And agile Office experience to
your end users by leveraging
01:09:33.550 --> 01:09:34.850
our resources.
01:09:34.850 --> 01:09:38.200
So you no longer have to go through
that lengthy adoption and training
01:09:39.220 --> 01:09:44.030
internal marketing process to get
your end users back up and running,
01:09:44.030 --> 01:09:45.230
back up and productive.
01:09:45.230 --> 01:09:48.848
Because it's all about productivity.
01:09:48.848 --> 01:09:51.880
It's all about being on
the latest technology,
01:09:51.880 --> 01:09:55.390
being able to deliver value
back into your business.
01:09:55.390 --> 01:09:59.150
And ensuring that we can maintain
compliance and compatibility and
01:09:59.150 --> 01:10:00.400
support moving forward.
01:10:02.520 --> 01:10:04.350
So, some of the key
takeaways from this session.
01:10:05.960 --> 01:10:11.450
Familiar deployment options,
exactly the same as
01:10:11.450 --> 01:10:14.819
Office MSI, so we still have all
those options available to us.
01:10:15.860 --> 01:10:17.720
Rapid deployment mechanisms.
01:10:17.720 --> 01:10:20.350
You still have control
of how you do that.
01:10:20.350 --> 01:10:21.390
Just because it's Office for
01:10:21.390 --> 01:10:24.470
service does not mean that
you don't have control.
01:10:24.470 --> 01:10:27.260
It doesn't mean we control
Office on your behalf.
01:10:27.260 --> 01:10:30.670
We just make things available
to you, and you can take them.
01:10:30.670 --> 01:10:33.390
You can automate the update
process as well.
01:10:33.390 --> 01:10:38.760
Use PowerShell scripts, use task
schedules, download the content,
01:10:38.760 --> 01:10:43.280
push that into a query user
acceptance group, then escalate,
01:10:43.280 --> 01:10:47.080
after a week or two,
escalate that into production and
01:10:47.080 --> 01:10:51.730
deliver that to your end users using
group policy, using tough schedules,
01:10:51.730 --> 01:10:53.360
using para scripts.
01:10:53.360 --> 01:10:55.709
You can automate the entire
upgrade process.
01:10:57.110 --> 01:11:00.580
We have new authentication and
licensing processes ensuring that
01:11:00.580 --> 01:11:04.450
your users are licensed, insuring
that you can activate Office.
01:11:04.450 --> 01:11:08.270
I made sure to, if you use lease,
your organization,
01:11:08.270 --> 01:11:11.770
you can deactivate a license and
reprovision it to someone else.
01:11:11.770 --> 01:11:12.920
Don't worry about the bits.
01:11:12.920 --> 01:11:14.950
If they still have the bits,
the bits are free.
01:11:14.950 --> 01:11:16.650
It's the license that costs.
01:11:16.650 --> 01:11:19.310
And you control the license
in the Office cloud.
01:11:19.310 --> 01:11:21.250
So, that's an important
take away as well.
01:11:22.710 --> 01:11:24.150
And telemetry.
01:11:24.150 --> 01:11:28.330
Use telemetry, understand
what's in your Office estates,
01:11:28.330 --> 01:11:33.380
understand how Office is impacting
your business, what solutions and
01:11:33.380 --> 01:11:37.330
add ins are being used,
what documents are being used,
01:11:37.330 --> 01:11:41.400
understand where successes and
failures are in your environments.
01:11:41.400 --> 01:11:43.770
And which operating
systems are working best.
01:11:43.770 --> 01:11:48.350
Understand the performance of Office
overall, and surface that back into
01:11:48.350 --> 01:11:51.210
the business as well as the help
desk to drive down those costs.
01:11:53.240 --> 01:11:55.530
So I'd just like to end on
some customer examples.
01:11:57.630 --> 01:12:00.520
Henkel over in Germany,
01:12:00.520 --> 01:12:04.920
moved more than 40,000 users from
2003 to ProPlus in five months.
01:12:06.670 --> 01:12:09.510
Rapid deployment, significant.
01:12:09.510 --> 01:12:10.670
3M as well.
01:12:11.860 --> 01:12:15.230
Delivering the tools,
fast, easy to use, and
01:12:15.230 --> 01:12:17.460
in a very diverse environment.
01:12:17.460 --> 01:12:20.210
And Hamburg Port Authority as well.
01:12:20.210 --> 01:12:26.330
Reducing that effort for
upgrading Office by up to 75%.
01:12:26.330 --> 01:12:32.810
So there are some additional case
study references in the slide deck.
01:12:32.810 --> 01:12:36.220
I do encourage you to go ahead and
download the deck.
01:12:36.220 --> 01:12:38.290
It's available from Yammer.
01:12:39.550 --> 01:12:43.560
We are running, have about two and
a half minutes left.
01:12:43.560 --> 01:12:46.860
More than happy to take questions,
but I'll be here for the duration.
01:12:46.860 --> 01:12:48.720
So please do come and grab me.
01:12:48.720 --> 01:12:51.960
And finally, let's just thank
you for the session today,
01:12:51.960 --> 01:12:55.245
for coming along and don't forget
to fill out your evaluations.
01:12:55.245 --> 01:13:01.840
[APPLAUSE]