Thanks, Ivan. I've not tried this, but looking at the XML file in Ryan's link below, it should be possible to do it with OneSite.
You'd hard-code the XML files to point to a local path on the client machine, create a Content Push policy, let it unpack to that hard-coded folder, and specify a command-line to execute the deployment tool. Without OneSite you could do something similar using a batch file to make a local copy, or use an environment variable in the XML file. Please let me know if you need to deploy this in future, we could design a workflow to do it, and send status messages for reporting. thanks, Deepak Kumar, Chief Technology Officer, Adaptiva. Seattle, WA - 98033. Tel: 425-823-4500, Cell: 425-647-9095 http://www.adaptiva.com/onesite-deep-dive/ [Description: Description: adaptiva_logo4c-small] Simply Works! [email-signature-awards] From: [email protected] [mailto:[email protected]] On Behalf Of Lindenfeld, Ivan Sent: Friday, September 19, 2014 11:25 AM To: [email protected] Subject: [mssms] RE: Deploying O365 Chris, I know the OneSite product we’re a customer. We’re also an Office 365 subscriber. I also have talked through but did not deploy O365. We are deploying Office Pro Plus still and updating it with SCCM, the Software Update and service pack way. For this, a product like OneSite is a fantastic help. (We took 81 DP’s down to 1. This is not an ad for OneSite, so I’ll take it back to your situation.) We decided not to deploy the O365 bits because we could not control the updates without many source locations to manage. We have >1000 WAN links and 19,000 clients. It would have meant building another patch and update network on top of an existing working solution and managing that. Inefficient. Oh, and we couldn’t just let O365 update itself on Microsoft’s schedule because of WAN links and no ability to manage bandwidth usage over them. You either deploy Office 365 to your computers and take updates when they come, which may work if you are all in 1 building with a big internet connection; or you deploy Office 365 and build a virtual WAN of updates that you download from Microsoft and put on your DP’s (in your case). The latter is the framework of your question. A content management network like OneSite or Nomad doesn’t help this. Heck, I would need more info, but outside of O365 I’m not sure OneSite would meet the “everything needs to come from the DP’s” requirement, but I suppose you could map the OneSite Virtual Network through existing DP’s. It may not matter if it’s political or security matter. Ivan Lindenfeld From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Friday, September 19, 2014 1:13 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Deploying O365 Sounds like 1E Nomad or Adaptiva OneSite would be perfect for you. Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Barnes,Chris Sent: Friday, September 19, 2014 1: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 [Penske75new] 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 [Penske75new] 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. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. ________________________________ NOTICE: The information contained in this message is proprietary and/or confidential and may be privileged. If you are not the intended recipient of this communication, you are hereby notified to: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately.
