Chris I specifically meant the install files
Regards the updates then GPO linked to AD Site or Config & Settings linked to collections might well be the way to go. > On 19 Sep 2014, at 18:30, Barnes,Chris <[email protected]> wrote: > > What part of the process is handling that? For instance, if we had 1 app / > package / program that ran the install. How does the office install know to > go to DP1 for its content which is local, and not DP2, which is across 3 > different hops on the WAN? > > I thought that this had to be specified in the config.xml where to look for > updates? > > As for other products, my managements stance has been why should we have to > pay for a 1E, or use branchcache to deploy Microsofts flagship application, > when we already have SCCM. I tend to agree with them on that. > > > Chris Barnes > > Senior Technical Specialist > Penske Automotive Group, Inc. > Desk: (248) 648-2528 > Cell: (248) 767-4415 > > <image001.jpg> > PENSKECARS.COM > > From: [email protected] [mailto:[email protected]] > On Behalf Of Jason Wallace > Sent: Friday, September 19, 2014 10:19 AM > To: [email protected] > Subject: Re: [mssms] RE: Deploying O365 > > If you are meaning the source entry for installation try taking the line out > - it will then look in the current folder which is perfect for SCCM. > > > > On 19 Sep 2014, at 18:12, Barnes,Chris <[email protected]> wrote: > > 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 > > <image001.jpg> > PENSKECARS.COM > > From: [email protected] [mailto:[email protected]] > On Behalf Of Ryan Fielder > Sent: Friday, September 19, 2014 5:25 AM > To: [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]] > On Behalf Of Jason Sandys > Sent: Thursday, September 18, 2014 9:56 PM > To: [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]] > On Behalf Of Barnes,Chris > Sent: Thursday, September 18, 2014 6:26 PM > To: [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 > > <image001.jpg> > 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. > > > > > >
