Great – Thanks for the feedback guys.
Chris Barnes Senior Technical Specialist Penske Automotive Group, Inc. Desk: (248) 648-2528 Cell: (248) 767-4415 [cid:[email protected]] PENSKECARS.COM<http://penskecars.com/> From: [email protected] [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Friday, September 19, 2014 12:20 PM To: [email protected] Subject: [mssms] RE: Deploying O365 Updates are handled differently and have nothing to do with the SourcePath specified during initial install. You can either set a local UNC using group policy or disable updates and push the updated O365 Pro Plus “package” from ConfigMgr again. Disabling auto-updates and re-pushing the app sounds like a big deal but it’s really not. It’s effectively the exact same that the auto-updater does, however, you do lose the very nice user messaging and coordination that comes with it. A hybrid solution was documented recently at http://blogs.technet.com/b/ouc1too/archive/2014/09/05/patching-office-365-with-configuration-manager-2012-or-how-i-learned-to-stop-worrying-and-love-the-click2rclient.aspx J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Barnes,Chris Sent: Friday, September 19, 2014 1:05 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Deploying O365 Thanks Jason – The updates is more of what I am asking about. They cannot be updated automatically. The have to be put through our UAT process. So if the source path isn’t specified on the install, it will reach out to Microsoft to update. How are people handling the source path, without using another technology like 1E, BranchCache, DFS, Azure DP, etc. Chris Barnes Senior Technical Specialist Penske Automotive Group, Inc. Desk: (248) 648-2528 Cell: (248) 767-4415 [cid:[email protected]] PENSKECARS.COM<http://penskecars.com/> From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Friday, September 19, 2014 10:56 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Deploying O365 You don’t need to do anything. The SourcePath parameter is optional and if not specified “Setup will look in the current folder for the Office source files”. Re: http://technet.microsoft.com/en-us/library/jj219426.aspx#BKMK_AddElement Given your requirement, make sure you plan out how you are going to do your updates also. If you don’t do anything, all of your click-to-run installations will automatically update themselves over the Internet (if they can). J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Barnes,Chris Sent: Friday, September 19, 2014 12:09 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Deploying O365 Thanks Ryan and Jason – How is everyone managing the content for deploying and updating O365 using SCCM? We have over 100 Distribution Points now, is there any way around having 100 different .XML files that would point to the local DP for the source? We have a restriction on our network that content must be pulled from the local DP, and cannot be pulled across the WAN. DFS is not going to be an option either. Chris Barnes Senior Technical Specialist Penske Automotive Group, Inc. Desk: (248) 648-2528 Cell: (248) 767-4415 [cid:[email protected]] PENSKECARS.COM<http://penskecars.com/> From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Ryan Fielder Sent: Friday, September 19, 2014 5:25 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Deploying O365 Chris, Check out these two sites. http://www.configmgr.no/2013/06/09/how-to-deploy-office-365-with-click-to-run-and-configmgr/ http://jackstromberg.com/2013/05/deploying-office-2013-professional-plus-from-office365-offline/ -Ryan From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Thursday, September 18, 2014 9:56 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Deploying O365 That is incorrect. Click to run must be deployed to the system (or a user with admin rights) because there is some initial per-system installation that must be done including a scheduled task and some core App-V components. From http://technet.microsoft.com/en-us/library/jj219423(v=office.15).aspx: “Users must be local administrators on their computers to install Click-to-Run for Office 365 products.” J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Barnes,Chris Sent: Thursday, September 18, 2014 6:26 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] Deploying O365 Hey guys, I thought I heard someone say that O365 Click to Run needed to be deployed to a User in SCCM, that it could not be deployed to a System. Didn’t sound right, so I wanted to get some other verification of that. I couldn’t find anything in my Googling that would say one way or another, anyone have any input? Chris Barnes Senior Technical Specialist Penske Automotive Group, Inc. Desk: (248) 648-2528 Cell: (248) 767-4415 [cid:[email protected]] PENSKECARS.COM<http://penskecars.com/> ________________________________ Penske Automotive Group and its affiliates will never sell or rent your email address in violation of applicable law. This email and any files transmitted with it are confidential and intended solely for use of the individual or entity to whom they are addressed. Please delete all copies if you are not the intended recipient.
