|
Headed out to SPTechCon in San Francisco next weekend, due to budget issues I wasn't able to get to the big show in Vegas in November. My new job includes leading a team rolling out a SP2013 migration for the enterprise and making recommendations about cloud vs on premises, etc. We are also a huge Yammer client and we'll need to figure out how much it will be integrated into SP by the time we go live.
|
| # ? Feb 24, 2013 23:30 |
|
|
|
| # ? May 25, 2013 13:49 |
|
|
tomapot posted:Headed out to SPTechCon in San Francisco next weekend, due to budget issues I wasn't able to get to the big show in Vegas in November. My new job includes leading a team rolling out a SP2013 migration for the enterprise and making recommendations about cloud vs on premises, etc. We are also a huge Yammer client and we'll need to figure out how much it will be integrated into SP by the time we go live. Heh, let us know how the migration goes. Any reason you're moving so soon? I thought most companies generally waited for the first service pack.
|
| # ? Feb 25, 2013 00:27 |
|
|
Tab8715 posted:Heh, let us know how the migration goes. Any reason you're moving so soon? I thought most companies generally waited for the first service pack. We're still a ways out, but we need to start planning. Our lab is being built out now so we can start testing our apps.
|
| # ? Feb 25, 2013 01:20 |
|
|
Bump! I'm not in IT, but our company is thinking about using SharePoint more. But, the way we're set up, we have same-but-not-same customers around the world. I mean, let's say, we have a global customer who has local offices who make local deals with our local offices. And, though we're global, we do not have the resources to implement a global SharePoint site, only local ones. So now, the talk is to use a particular local server (e.g. USA) to deal with a primarily USA global customer, even if their European subsidiary makes independent deals with our European office. In that case, the European office would access our USA sharepoint site and upload their documents, etc. But, I wonder, surely it must be possible to integrate the data between two different SharePoint servers? Even with mirroring, or linking, or something? In effect, it appears to be one big server, but in effect parts of the site might be kept on one server in USA while other parts might be kept in Europe. Is this kind of thing possible with SharePoint? Is it reasonably easy to implement or not worth the effort?
|
| # ? Apr 16, 2013 13:43 |
|
|
What you're trying to do is going to be actually amazingly difficult. The closest thing you can do is get the DNS similar - https://us-collab.example.com and https://eu-collab.example.com. You can link between the sites of course but the user would need to authenticate to each one separately, which may lead to double login prompts if a user bounces between them regularly. This sounds like BS though. "And, though we're global, we do not have the resources to implement a global SharePoint site, only local ones." You're going to be using more resources (hardware) to implement 2 farms, since none of the shared components can be shared across datacenters, and the time cost is going to be higher because you'll need to patch and maintain double the servers. Since SharePoint is a web application, it's easily made global with minimal additional latency. Just build one. My company is ~20k people and global and we centralize all of our SharePoint data, with no latency-related issues.
|
| # ? Apr 16, 2013 14:00 |
|
|
Urit posted:What you're trying to do is going to be actually amazingly difficult. The closest thing you can do is get the DNS similar - https://us-collab.example.com and https://eu-collab.example.com. You can link between the sites of course but the user would need to authenticate to each one separately, which may lead to double login prompts if a user bounces between them regularly. This sounds like BS though. "And, though we're global, we do not have the resources to implement a global SharePoint site, only local ones." You're going to be using more resources (hardware) to implement 2 farms, since none of the shared components can be shared across datacenters, and the time cost is going to be higher because you'll need to patch and maintain double the servers. Since SharePoint is a web application, it's easily made global with minimal additional latency. Just build one. My company is ~20k people and global and we centralize all of our SharePoint data, with no latency-related issues. Counterpoint/different perspective on this: if you have disaster recovery, regulatory or compliance data in SharePoint that would need to be accessible even if the WAN link is down, you should absolutely deploy separate, local farms for the different business units.
|
| # ? Apr 16, 2013 15:13 |
|
|
Thanks for the feedback. Like I said, I'm not in IT so I was just speculating for curiosity sake. And about our IT department, well, I think we would need to hire more personnel and purchase additional hardware anyway. It's umm... well, let's just say we sometimes "run out of IP addresses" on our internal network and I'm not sure the IT department knows how to use group policy to its maximum efficiency, so I'm less than impressed. Anyway, thanks again for the feedback; I guess I was hoping it would be something that could be done in a more transparent way than is currently proposed but I guess not. I'm not at all involved in the process, though, so I'll just let them do what they do.
|
| # ? Apr 16, 2013 15:19 |
|
|
It depends on what data you are sharing between the different sites as well. Like they said, it's a huge pain to do everything you need it to do, but if you just have external data to share, that's not so bad.
|
| # ? Apr 16, 2013 18:26 |
|
|
|
| # ? May 25, 2013 13:49 |
|
|
6 months ago ------------- me: Hey Infrastructure team that does operating system patching for my servers, please don't install SharePoint patches until I have all my ducks in a row. infrastructure: sure thing 3 months ago ------------- infrastructure: Hey everyone, here are MS the patches we're applying this week me: One of these is a SharePoint patch... infrastructure: Oh yeah, no problem. Won't patch it. This month ------------ infrastructure: Hey everyone, here are the MS patches we're applying this week. d3rt, one of this is a SharePoint patch so we won't apply it me: you rock *log in to SCA today to get a site collection backup for an important project we just kicked off* Health Analyzer: One or more Critical... User profile service failing... Content databases in backwards compatibility mode... Thanks guys.
|
| # ? Apr 30, 2013 21:14 |
|
