1 00:00:03,090 --> 00:00:08,430 So I now I want to summarize what we learned about software deployment and group policy in this module. 2 00:00:09,330 --> 00:00:16,620 So ASI or group policy software installation provides a really basic software deployment software distribution 3 00:00:16,620 --> 00:00:21,420 feature that allows you to install MSA packages on a per computer or per user basis. 4 00:00:22,320 --> 00:00:28,320 So again, you're limited to those MSA packages and there are obviously a few flexibilities that you 5 00:00:28,320 --> 00:00:32,640 have within that per computer and for user deployment around publishing or assigning. 6 00:00:33,480 --> 00:00:36,940 But by and large, it's a pretty limited capability. 7 00:00:37,860 --> 00:00:41,760 So you can publish per user where you can assign per user in per computer. 8 00:00:41,760 --> 00:00:46,380 And in either case, the user must log on or reboot to get that new package installed. 9 00:00:47,280 --> 00:00:52,170 Now when you're deploying packages, you should definitely use a DFC share if possible. 10 00:00:53,040 --> 00:00:57,780 This avoids the issue that I mentioned where servers that you've got packages on get retired and the 11 00:00:57,780 --> 00:01:02,670 sort of link between the client that's installed that application and the original share package is 12 00:01:02,670 --> 00:01:07,140 lost and you can no longer upgrade or manage those packages through group policy. 13 00:01:08,010 --> 00:01:13,860 So DFC kind of abstracts the physical server from that deployment path and allows you to trade out servers 14 00:01:13,860 --> 00:01:15,900 as needed underneath the DFC share. 15 00:01:15,900 --> 00:01:20,520 And the client is none the wiser in terms of knowing which server it's getting its package from. 16 00:01:21,390 --> 00:01:27,210 So I talked about lifecycle management of packages using ACI and I mentioned that and even showed that 17 00:01:27,210 --> 00:01:32,370 you can patch and upgrade applications, but you definitely want to use an administration install of 18 00:01:32,370 --> 00:01:37,440 the MSI file as long as it's supported because that allows you to do that. 19 00:01:37,440 --> 00:01:38,670 Patching that I showed. 20 00:01:39,540 --> 00:01:43,560 Without that administrative install, you can't really patch a deployment. 21 00:01:44,490 --> 00:01:50,520 So it's important that if you deploy an MSI file, use that slash option on my MSI exact to essentially 22 00:01:50,520 --> 00:01:53,340 get that administrative install out to your share package. 23 00:01:54,190 --> 00:02:00,010 And then finally avoid those scenarios where the user can remove a package or try to manage an application 24 00:02:00,010 --> 00:02:02,410 that's been deployed by group policy themselves. 25 00:02:03,280 --> 00:02:08,380 What ends up happening and it's really easy to get into this situation and really hard to get out of 26 00:02:08,380 --> 00:02:10,420 it is once a package gets orphaned. 27 00:02:11,320 --> 00:02:15,940 In other words, either the user has removed it, but group policy still thinks it's there. 28 00:02:16,060 --> 00:02:20,860 Or, in the case of the share going away or the server going away, the client is no longer able to 29 00:02:20,860 --> 00:02:22,660 be managed through that relationship. 30 00:02:23,480 --> 00:02:28,220 There really are no tools in group policy software installation to fix that scenario. 31 00:02:29,060 --> 00:02:34,550 So you really have to keep that relationship between client and server clean and let group policy do 32 00:02:34,550 --> 00:02:36,260 all of the lifecycle management. 33 00:02:37,190 --> 00:02:42,140 If you don't let group policy do that lifecycle management, then you end up in these kind of orphaned 34 00:02:42,140 --> 00:02:45,260 scenarios where you can no longer manage that package. 35 00:02:46,160 --> 00:02:50,120 So that kind of concludes what I wanted to talk about with software deployment. 36 00:02:51,040 --> 00:02:55,810 In the next module, I'm going to talk a little bit about user and settings and data management and 37 00:02:55,810 --> 00:02:57,640 how group policy can help with that.