1
00:00:00,440 --> 00:00:02,640
[Autogenerated] we've just looked at to cloud based methods for

2
00:00:02,640 --> 00:00:06,500
deploying apps in Tune and Microsoft Store for business.

3
00:00:06,500 --> 00:00:08,430
Now it's time to look at some of the apps that many

4
00:00:08,430 --> 00:00:10,400
companies are likely to want deployed.

5
00:00:10,400 --> 00:00:14,770
Microsoft Office Office 3 65 as we'll see as many versions,

6
00:00:14,770 --> 00:00:17,880
but Pro plus is the one we're concerned with in this clip.

7
00:00:17,880 --> 00:00:22,440
It's a subscription service for enterprises that includes the core office apps,

8
00:00:22,440 --> 00:00:26,940
plus some non core apps like publisher Access and OneDrive.

9
00:00:26,940 --> 00:00:31,120
However, Pro Plus does not include exchange SharePoint ER teams.

10
00:00:31,120 --> 00:00:33,640
You also get web versions of the core apps,

11
00:00:33,640 --> 00:00:35,900
and licensed users can install the software on a

12
00:00:35,900 --> 00:00:38,190
maximum of five devices per user.

13
00:00:38,190 --> 00:00:39,060
By the way,

14
00:00:39,060 --> 00:00:43,640
Pro Plus at this writing is these only version that we can deploy via in tune.

15
00:00:43,640 --> 00:00:45,070
To put things into some context,

16
00:00:45,070 --> 00:00:49,930
it might be useful to do a quick comparison of office 3 65 versus Office 2019.

17
00:00:49,930 --> 00:00:53,860
Office 3 65 provides on premises software plus online

18
00:00:53,860 --> 00:00:55,600
web versions of the applications.

19
00:00:55,600 --> 00:00:58,080
Customers make recurring payments based on the number of

20
00:00:58,080 --> 00:01:00,500
users licensed and the licenses Paya's UGO,

21
00:01:00,500 --> 00:01:02,720
although depending on the license and annual commitment,

22
00:01:02,720 --> 00:01:06,790
may be required customers receive feature updates analogous

23
00:01:06,790 --> 00:01:09,530
to the feature updates in Windows 10 twice per year

24
00:01:09,530 --> 00:01:12,030
automatically and at no extra charge.

25
00:01:12,030 --> 00:01:15,980
Customers also receive cloud services such as OneDrive and optionally,

26
00:01:15,980 --> 00:01:17,450
others, depending on the license.

27
00:01:17,450 --> 00:01:20,590
Finally, we can deploy the pro plus edition via in tune.

28
00:01:20,590 --> 00:01:23,830
By contrast, Office 2019 is on premises.

29
00:01:23,830 --> 00:01:26,160
Software only know online versions.

30
00:01:26,160 --> 00:01:30,740
It requires a one time payment that conveys a perpetual use license.

31
00:01:30,740 --> 00:01:34,380
But that license does not include the semiannual feature updates and

32
00:01:34,380 --> 00:01:37,270
only includes cloud services for a five year period.

33
00:01:37,270 --> 00:01:42,340
We cannot at present deploy office 2019 via in tune now within the office.

34
00:01:42,340 --> 00:01:43,480
3 65 family.

35
00:01:43,480 --> 00:01:45,040
We distinguish between enterprise,

36
00:01:45,040 --> 00:01:47,830
business and consumer editions within the Enterprise family,

37
00:01:47,830 --> 00:01:50,000
which requires an annual financial commitment.

38
00:01:50,000 --> 00:01:53,200
We have E one with Cloud services only E three with the

39
00:01:53,200 --> 00:01:55,770
addition of the office core apps E five,

40
00:01:55,770 --> 00:01:58,900
which further adds Power BI I and Pro Plus,

41
00:01:58,900 --> 00:02:01,980
which provides the core apps plus access and publisher on

42
00:02:01,980 --> 00:02:04,460
the PC platform as well as OneDrive.

43
00:02:04,460 --> 00:02:08,000
The business editions of Office 3 65 permit monthly payments and

44
00:02:08,000 --> 00:02:11,070
include business essentials providing cloud services only

45
00:02:11,070 --> 00:02:13,610
business providing core apps and OneDrive,

46
00:02:13,610 --> 00:02:17,700
including desktop versions and business premium with pretty much everything.

47
00:02:17,700 --> 00:02:18,790
And finally, the consumer.

48
00:02:18,790 --> 00:02:21,310
Additions include personal, which, as the name implies,

49
00:02:21,310 --> 00:02:25,090
is a one person licenses home which differs from personal and that you could

50
00:02:25,090 --> 00:02:28,680
license up to six people in the household and home and student,

51
00:02:28,680 --> 00:02:33,340
including only the three apps that students are most likely to need.

52
00:02:33,340 --> 00:02:37,900
The general procedure for deploying office 3 65 within Tune is to navigate to

53
00:02:37,900 --> 00:02:41,560
the apps note of the main endpoint manager Edmund center page,

54
00:02:41,560 --> 00:02:47,740
click all apps and then add and choose Microsoft 365 apps as the app type.

55
00:02:47,740 --> 00:02:49,750
Now we give the apps sweet a name,

56
00:02:49,750 --> 00:02:52,990
description and category by the apps Sweet Information tab,

57
00:02:52,990 --> 00:02:54,610
along with informational and privacy.

58
00:02:54,610 --> 00:02:56,040
You RL's if we wish.

59
00:02:56,040 --> 00:02:57,620
When it comes to configuring the settings,

60
00:02:57,620 --> 00:03:01,710
we have two main choices we can use in tunes Configuration Designer,

61
00:03:01,710 --> 00:03:05,490
which lets us inter actively configure the app suite that is,

62
00:03:05,490 --> 00:03:10,060
Select the apps We wish to deploy and configure the app Sweet information,

63
00:03:10,060 --> 00:03:14,540
which includes miscellaneous choices such as 32 or 64-bit binaries,

64
00:03:14,540 --> 00:03:18,530
whether to remove old MVC based versions of office and properties,

65
00:03:18,530 --> 00:03:21,440
including language choices, among others.

66
00:03:21,440 --> 00:03:21,700
Now,

67
00:03:21,700 --> 00:03:25,490
as an alternative to using the configuration designer we can enter XML data

68
00:03:25,490 --> 00:03:29,690
generated by earlier tools such as these E office deployment tool or the

69
00:03:29,690 --> 00:03:33,440
online office customization tool that contain similar information to the

70
00:03:33,440 --> 00:03:35,860
choices offered by the configuration designer.

71
00:03:35,860 --> 00:03:40,640
The last step is to assign this sweet to one or more Azure aid groups.

72
00:03:40,640 --> 00:03:40,810
Well,

73
00:03:40,810 --> 00:03:42,860
let's show you what this process looks like in the

74
00:03:42,860 --> 00:03:46,350
Microsoft endpoint Edmund center, the new home for Microsoft In tune,

75
00:03:46,350 --> 00:03:49,050
we've navigated to the apps page and selected all

76
00:03:49,050 --> 00:03:50,820
apps and click to the add button.

77
00:03:50,820 --> 00:03:53,580
The first decision is to specify the app type,

78
00:03:53,580 --> 00:03:59,220
which for us will be the Windows 10 entry under Microsoft 365 apps.

79
00:03:59,220 --> 00:04:02,800
Then we'd click the select button and the many Wizard begins

80
00:04:02,800 --> 00:04:05,380
with the app Sweet Information tab shown here,

81
00:04:05,380 --> 00:04:09,200
where we can provide a name and description for the sweet and optionally

82
00:04:09,200 --> 00:04:13,890
provide category and URL details as well as specify whether the software

83
00:04:13,890 --> 00:04:17,840
should appear is a featured app on the company portal.

84
00:04:17,840 --> 00:04:21,700
Now the next tab is these configure apps Sweet tab notice that we've

85
00:04:21,700 --> 00:04:25,420
chosen configuration designer for the configuration settings format

86
00:04:25,420 --> 00:04:28,060
rather than nXML file created by another utility.

87
00:04:28,060 --> 00:04:31,000
Our choice lets us set various options on this tab using

88
00:04:31,000 --> 00:04:33,440
the drop-down menus and toggle switches,

89
00:04:33,440 --> 00:04:35,640
the configure apps, sweet menus.

90
00:04:35,640 --> 00:04:38,460
Let us choose which apps in the Sweet we like to deploy,

91
00:04:38,460 --> 00:04:39,370
and below that,

92
00:04:39,370 --> 00:04:43,420
you can see the options for 32-bit versus 64-bit architectures update

93
00:04:43,420 --> 00:04:47,020
channel and whether to automatically remove previously installed MVC

94
00:04:47,020 --> 00:04:49,060
versions of office applications and finally,

95
00:04:49,060 --> 00:04:50,360
in the Properties section.

96
00:04:50,360 --> 00:04:53,860
We can set whether to use shared computer activation licensing,

97
00:04:53,860 --> 00:04:54,500
for example,

98
00:04:54,500 --> 00:04:57,850
in scenarios where multiple individuals are using the same computer and

99
00:04:57,850 --> 00:05:01,470
logging on with their separate credentials and whether to auto except the end

100
00:05:01,470 --> 00:05:04,830
user license agreement and what languages to install.

101
00:05:04,830 --> 00:05:08,020
Now when performing an in tune deployment of office 3 65.

102
00:05:08,020 --> 00:05:10,830
The installation will probably fail if any previous desktop

103
00:05:10,830 --> 00:05:12,470
versions of office exist on the machine.

104
00:05:12,470 --> 00:05:12,610
Now.

105
00:05:12,610 --> 00:05:16,940
We just saw the option in the Configure apps suite page to remove such versions.

106
00:05:16,940 --> 00:05:21,340
But just be aware that this will delete all office 3 65 apps,

107
00:05:21,340 --> 00:05:23,720
even if you're only wanting to install one or two.

108
00:05:23,720 --> 00:05:25,900
So you may wish to handled the situation differently,

109
00:05:25,900 --> 00:05:26,610
for example,

110
00:05:26,610 --> 00:05:30,680
with PowerShell to give you the flexibility to uninstall only selected

111
00:05:30,680 --> 00:05:34,240
office apps before you perform an in tune deployment.

112
00:05:34,240 --> 00:05:36,470
Now the next tab, labeled assignments,

113
00:05:36,470 --> 00:05:39,920
is where we can assign the deployment to Azure 80 groups based on

114
00:05:39,920 --> 00:05:44,050
whether we want the deployment to be required available or in the case

115
00:05:44,050 --> 00:05:46,710
where we want to remove the software uninstalled.

116
00:05:46,710 --> 00:05:50,670
Note the links to add all devices and add all users.

117
00:05:50,670 --> 00:05:54,220
If we want to make an enterprise wide deployment now,

118
00:05:54,220 --> 00:05:57,130
we don't have to use in tune to deploy office 3 65.

119
00:05:57,130 --> 00:06:00,250
Of course, other options include configuration manager,

120
00:06:00,250 --> 00:06:03,780
group policy, manual installation and other third-party,

121
00:06:03,780 --> 00:06:06,640
MDM and land based app deployment tools.

122
00:06:06,640 --> 00:06:10,130
If by chance you are upgrading existing office installations,

123
00:06:10,130 --> 00:06:13,980
be on the lookout for compatibility issues with visual basic for applications,

124
00:06:13,980 --> 00:06:19,530
macros and office Adan's happily some compatibility assessment tools do exist,

125
00:06:19,530 --> 00:06:21,800
including the Microsoft are Edin is Toolkit.

126
00:06:21,800 --> 00:06:25,430
But be aware that the Windows Log Analytics Upgrade Readiness

127
00:06:25,430 --> 00:06:29,080
solution has been retired by Microsoft as a final note.

128
00:06:29,080 --> 00:06:31,780
Although we have focused here on the Windows 10 scenario,

129
00:06:31,780 --> 00:06:43,000
be aware that in tune can also deploy office 3 65 to macOS devices, and with that tidbit you are ready to use in tune to deploy office 3 65 pro plus