Are you sure? I’ve worked remote and worked not remote, and trench warfare between team factions can happen in both situations. It’s leadership and culture issues that leads to that kind of collaboration breakdown, and can happen even with locally collocated teams. In a large company many of your collaborators are going to be in other cities anyway.
The point I would like to make is, in that team of 20 not sharing information and not seeking input was a problem, even though people sat right next to each other. And that problem could have been solved very easily by putting most of the decision making into one pagers, Google Docs and bug tracker, as well well as by defining the goals more clearly.
That is a cultural problem which remote team members did not create, but merely magnified. It existed before we joined and after we left. It resulted in a project which you need to have a PhD in computer science to figure out how to use, and as a result few teams inside Google use it.
Which is a long-winded way of suggesting, that if introducing remote workers shows some cracks in your team structure, perhaps there's a deeper reason why, and things aren't 100% ideal to begin with.
BTW: The best I’ve read about this so far is: “The Culture Code”