We've not seen a customer using MultiCast in a very long time. The 
implementation of the Single Site Download(SSD)  feature in Nomad made the use 
of MC moot.

Ed Aldrich |Technical Enablement Lead
1E | Software Lifecycle Automation for the Digital Business
Mobile: (401) 924-2293
[email protected]<mailto:[email protected]> | www.1e.com<http://www.1e.com/>
[Description: Description: cid:[email protected]] Ent Client Mgmt 
MVP (2003-2016)

From: [email protected] [mailto:[email protected]] On 
Behalf Of Andreas Hammarskjöld
Sent: Tuesday, January 26, 2016 3:58 PM
To: [email protected]
Subject: RE: [mssms] Branch Cache and larger offices

In theory and in a lab it's not a problem, so yes.

But after talking to any "network department" this normally gets shot down in a 
spiral of meetings and "security concerns" leading to more meetings etc...

The actual WS-Discovery is a multicast packet, so use regular multicast 
boundaries to limit it. Now setting that up for a larger company it's not worth 
the pain. Trust me.

Someone of the 1E dudes might want to fill in if people are using MC to limit 
masters these days, it wasn't really used as far as I can remember for the very 
same reasons.

//Andreas

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Jason Wallace
Sent: den 26 januari 2016 15:03
To: [email protected]<mailto:[email protected]>
Subject: [mssms] Branch Cache and larger offices

Hi there folks

I wonder whether any folks have had success with using IGMP forwarding in a 
multi-subnet office in order to improve the utility of Branch Cache to be more 
than just subnet based.

If so, did this work out OK?

Jason



________________________________


Legal Notice: This email is intended only for the person(s) to whom it is 
addressed. If you are not an intended recipient and have received this message 
in error, please notify the sender immediately by replying to this email or 
calling +44(0) 2083269015 (UK) or +1 866 592 4214 (USA). This email and any 
attachments may be privileged and/or confidential. The unauthorized use, 
disclosure, copying or printing of any information it contains is strictly 
prohibited. The opinions expressed in this email are those of the author and do 
not necessarily represent the views of 1E Ltd. Nothing in this email will 
operate to bind 1E to any order or other contract.



Reply via email to