When you say "behind 19 DP's" I don't follow you.. Back when I did use
Riverbeds, which was on SMS 2003 I should say, we used them in-place of DP's.
In very small offices the cached on the riverbed typically would suffice for
content when doing patches etc. Again, now there are much better ways to
accomplish this goal. i.e. Nomad
________________________________
John Marcum
MCITP, MCTS, MCSA
Desktop Architect
Bradley Arant Boult Cummings LLP
________________________________
[MVP] <https://mvp.microsoft.com/en-us/overview>
[MMS] <http://mmsmoa.com/>
From: [email protected] [mailto:[email protected]] On
Behalf Of Ryan Shugart
Sent: Wednesday, March 2, 2016 2:07 PM
To: [email protected]
Subject: RE: [mssms] Use of Riverbeds at remote offices
Actually we use Riverbeds behind about 19 DPs at remote offices and it works
just fine. We use HTTP, not HTTPS traffic for our DPs (yes I know and that
will change) so can't comment on the certs but its been fine. We did run into
issues with the Riverbeds with the old CM07 environment and had to put bypasses
on all the remote DPs but that hasn't come up again in 2012R2. So yes, someone
does use Riverbeds, they still exist.
Ryan
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Marcum, John
Sent: Wednesday, March 2, 2016 12:57 PM
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] Use of Riverbeds at remote offices
Jeeze... that post was 5 years ago! Nobody uses Riverbeds anymore. When I did
say that I liked Riverbeds it was only as a WAN accelerator not anything more.
It sounds like you are trying to run a DP on the appliance. If that's the case
I'm unfamiliar with that use case, probably because as I said...Nobody uses
riverbeds anymore. :)
If I had a branch office scenario where I needed a DP and I couldn't have a DP
I'd buy nomad and be done with it. That is simple, cheap and well proven
technology.
________________________________
John Marcum
MCITP, MCTS, MCSA
Desktop Architect
Bradley Arant Boult Cummings LLP
________________________________
[MVP] <https://mvp.microsoft.com/en-us/overview>
[MMS] <http://mmsmoa.com/>
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Jason Wallace
Sent: Wednesday, March 2, 2016 10:29 AM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] Use of Riverbeds at remote offices
Hi there folks
I was wondering if someone would have some detail on using Riverbed Steelheads
with CM Agents please?
We are working on a CM design with DPs at a head office location hosting
BranchCache and clients at remote offices. Between them we have a number of
SteelHeads and I am keen to find out more about how this scenario stands up.
The customer only supports Riverbedding HTTPS traffic so the assumption is that
we will be supplying the web server certs of the DPs so that they can get at
the data while in transit in order to cache it
As I have been BinGoogling I have found that Mr Marcum is a fan but Mr Sandys
is not
https://social.technet.microsoft.com/Forums/systemcenter/en-US/d9ced859-9fe9-4210-9418-3b3f5e02be45/riverbed-scenario?forum=configmgrgeneral
I also note that RiOS 8.5 introduced support for BranchCache in hosted mode.
Now I know that CM does not support Hosted mode, running in distributed mode
but should the customer implement this does anyone know if the Riverbeds then
publish a service connection point?
Best Wishes
Jason
________________________________
Confidentiality Notice: This e-mail is from a law firm and may be protected by
the attorney-client or work product privileges. If you have received this
message in error, please notify the sender by replying to this e-mail and then
delete it from your computer.
MiTek Holdings, Inc., 2011-2014, All Rights Reserved
________________________________
This communication (including any attachments) contains information which is
confidential and may also be privileged. It is for the exclusive use of the
intended recipient(s). If you are not the intended recipient(s), please note
that any distribution, copying, or use of this communication or the information
in it is strictly prohibited. If you have received this communication in error,
please notify the sender immediately and then destroy any copies of it.
