Yangu mwenzake, David Drinkwine, does a (slightly more than) pen-on-napkin estimate for building a truly world class intranet for a large enterprise organization. Unaweza read about it here: (http://www.bigapplesharepoint.com/pages/View-An-Insight.aspx?BlogID=86&stitle=WCI).
</mwisho>
SP2010 ni baridi sana mambo, lakini napenda wangeweza kurekebishwa kwenye orodha ya lugha na kurasa maktaba mazingira 'linapokuja aina kusimamia maudhui:
lugha moja alikuwa katika nafasi kwa WSS / MOSS. Kubadili tu neno "futa" na "kuondoa" na itakuwa wazi tu kufanya zaidi ya akili.
Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin
</mwisho>
My latest article for SharePointBriefing.com is up and kicking here: http://sharepointbriefing.com/features/article.php/3887276/The-Road-to-SharePoint-Mastery.htm
Hapa ni teaser:
Hii ni kimsingi toleo pretty mfupi na kufupishwa ya mada yangu maarufu ya umma juu ya "On kujifunza SharePoint." Utani ugombo hakuna, hata hivyo.
Kuangalia ni nje!
</mwisho>
Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin
(Kumbuka: makala hii ilikuwa kuvuka-posted hapa: http://www.endusersharepoint.com/?p=1912)
Mwisho 09/01/09: Kulingana na maoni Twitter, I need to clarify that InfoPath is supported in the sense that BPOS provides forms libraries. What I mean when I write "not supported in any way" is that InfoPath forms services functions are not supported. That means that you can’t publish an InfoPath form to BPOS and and have it render in the web browser. It also means that some out of the box workflows, which use InfoPath (even in MOSS standard edition) don’t work in BPOS because their initiation and other forms use InfoPath. Hopefully that clears things up.
I had a chance to really dig into Microsoft Online’s offering earlier this year and specifically the business productivity online suite (BPOs). This came along before I even hard a firm plan to set out on my own at Arcovis. I immediately saw, hata hivyo, that BPOS could be a key part of my company’s internal infrastructure and over time, it has become exactly that. Arcovis, uses it on a daily basis. I thought I’d share some of that experience from a practical perspective in case you want to evaluate it for yourself or are just curious about it.
As the word “suite” in BPOS implies, you get a small bundle of applications:
You can buy each of them separately, Naamini. It’s all spelled out relatively clearly on the Microsoft online site. You may be able to get better deals through MSFT partners. Arcovis has been working with Wingu Mikakati and they seem to know their stuff, so I’d include them in your list of vendors if you do a multi-vendor search.
I outline my experience and thoughts for each of these respectively.
This is a hosted exchange environment and from my perspective, it works like any other Exchange server I have ever used. It’s fully integrated with all of my fellow Arcovis partners’ environments and gives me access to the calendar (which is huge). Good stuff.
It also provides the Outlook Web Access (OWA) interface. That means I can get my email on any machine that has a web browser.
My HTC mobile phone, running Windows Mobile 6.1(?) connected to it nicely via Active Sync. It did this in exactly the way I expected and wanted.
I don’t consider myself much more than a casual outlook and exchange user so there may be really important Exchange features that just aren’t supported and I wouldn’t necessarily know it.
I think the strongest recommendation I make for this is that I am completely unaware that my exchange environment is “somewhere else.” I don’t know see any difference in Exchange and how I use it on a daily basis versus the half dozen or so other times I used someone’s exchange environment. Kwa kweli, this is better because it simply works.
Bottom line – hosted exchange is what it needs to be and I’m very happy with it.
This is a truly indispensible tool when you’re in the consulting business. I fire up instant live meetings several times a week to show intermediate work product to clients, to watch them break my solutions so that I know how to fix them, do sales presentations, nk. Live meeting is bundled with BPOS and it’s very easy to use.
I’m even less of a live meeting expert than I am on exchange. Hata hivyo, for my purposes, it’s great.
Hadi sasa, I use communicator almost only for presence information. I say “only” but have that presence data available to me whenever I’m connect has become addictive. With communicator installed and running, my colleagues know when I’m available, what my schedule is like at this moment, and can IM me (though the IM interface is pretty dull, at best). It’s one of those things that I really miss when I don’t have it. I actually get a little annoyed when my colleagues aren’t running communicator because the presence information is missing.
The presence indicator feels pervasive. It shows up in SharePoint whenever their name appears as an author to a document, assigned a task, nk. It shows in email, embedded right in outlook. It shows up in the communicator client itself.
For the most it just sits there running in the background and decorates my outlook and SharePoint screens with real-time presence information. It’s very cool.
My favorite bit, bila shaka, is SharePoint.
BPOS provides a modified version of MOSS standard edition. I’ll explain “modified” below. We’ve been using our BPOS SharePoint portal for stuff like:
Kimsingi, all the stuff you’d expect to use SharePoint for.
Along the way, we use technical features like:
What can’t I do with it? There are a bunch of things that would be nice:
The last bit is a little sad because we can’t do as much search configuration I would like.
You basically give up a lot of technical capability and are forced to live within the confines of out-of-the-box SharePoint functionality.
I can live with that. I have found myself wanting to slap together an event receiver or use a custom action once or twice,, but for the most part, I don’t notice the lack.
I should add that this is not a comprehensive list of the differences between a hosted “on prem” MOSS environment and SharePoint on line. Cloud Strategies has a very detailed presentation that goes into all that if you’re interested. I’m speaking from the perspective of a business owner leveraging the tool.
Microsoft provides a nifty desktop application that enables quick and easy access to all of the BPOS functions:
You don’t need to use it, but eliminates the need to log into each of the applications separately and for live meeting, It’s quite nice because you can do a “meet now” session with just 2 clicks (one on the “web conferencing” button above and another on the web browser that pops up). It’s also nice to get OWA with one click, though you can just put that in your browser favorites as well.
The other major advantage with this desktop application is that it provides a background kind of single sign on service. As long as this is running in the background, I can open up web browsers and connect to my BPOS environment without ever needing to enter credentials.
Microsoft made BPOS available to me for free so I am not currently paying the monthly per user fee at this time. Hata hivyo, I see value there and you can accept on faith (au siyo) that I would pay for this service. The fact is that I can’t count on Microsoft providing this for free forever and it’s become so strongly integrated with my business that moving … the mind quails.
BPOS is an insanely feature rich platform. Exchange, SharePoint (MOSS Standard!), presence, instant live meetings – it’s a lot of functionality that I would sorely, sorely miss if I had to live without it. My business would be severely impacted without it. Could I find replacement functionality? Probably, but I think I would have to cobble it together from a variety of other vendors, complicating my life. BPOS has so far proven itself to be stable and reliable. For the right kind of customer (like my company), BPOs ni thamani ya kuzingatia nguvu.
</mwisho>
Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin
Nimekuwa kufuatia vikao MSDN kwa vizuri zaidi ya mwaka (na uwezekano wa karibu 2 miaka katika hatua hii) and every now and then I hear from someone how “hard” it is to do that. I find it quite easy and thought I’d share my “technique”. This technique also works for www.endusersharepoint.com (http://www.endusersharepoint.com/STP).
Kuchukua MSDN kama mfano, Mimi kwanza kwenda kwenye ukurasa wa kiwango jukwaa kama vile Maswali Mkuu kwa ajili ya ukurasa SharePoint kuu hapa: http://social.technet.microsoft.com/Forums/en-US/sharepointgeneral/threads
Unapaswa haki mbali taarifa kwamba vikao ni RSS kuwezeshwa, kama inavyoonekana:
Nimekuwa kutumia Google Reader kwa ajili ya kusimamia yangu RSS feeds kwa muda mrefu sasa (www.google.com / msomaji). I go there, add the RSS feed for the forum and now I’m getting all new forums posts via RSS. My Google feeds for SharePoint forums look like this:
Google inatoa mimi mtazamo mzuri wa posting yenyewe:
Na hatimaye, Google lets mimi kutumia keyboard na kitabu kupitia matangazo katika vikao kwa njia hii.
Siwezi haraka Scan kupitia posts na mkazo tu kwa wale nahisi naweza kutoa mchango muhimu.
Alerts close the loop. Updates to posts don’t come through RSS (ingawa nadhani wao kutumika muda mrefu uliopita). Hata hivyo, kama mimi baada ya kukabiliana na jukwaa posting, the forums alert me via email and IM that someone responded in turn. Au, kama siwezi kutoa mchango muhimu lakini nataka kujua nini wengine kusema, Siwezi kuchimba ndani yake na kupanga kuomba alerts wakati wengine kufanya kujibu.
Katika saa au chini unaweza kuweka mchakato huu juu na na katika wiki ya matumizi ya kawaida, kujifunza mbinu mbalimbali na njia za mkato keyboard hivyo kwamba hii inakuwa asili ya pili.
I use the exact same technique for End User SharePoint.Com’s “Stump the Panel” forums. This is their RSS feed: http://www.endusersharepoint.com/STP/rss/.
Vikao ni njia ya kutisha, pengine njia bora ya muda wa uzoefu wa moja kwa moja binafsi, ya kujifunza bidhaa na kupata utafiti mzuri wa dunia jinsi, saa kubwa, uses SharePoint. Give it a try!
</mwisho>
Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin
Sababu ya sisi kutumia muda sana (au lazima, anyway) working out governance plans is because we want the SharePoint solution to be as effective as possible. We want good infrastructure and rules to keep it humming and safe in case of disaster. We want good security processes to both properly secure the environment but also make it reasonable to manage. We want a good information architecture that will stand the test of time, ideally managing to survive a major organizational change in the company.
To achieve that desirable objective, a governance document and plan can devolve into a bunch of “thou shall” and “thou shall not’s”, kama katika:
"Wewe atakuwa" na "wewe wala" hakika kuwa na nafasi zao katika mpango wa utawala.
A more successful governance plan will also have a strong marketing angle. It should sell and justify itself to the maximum extent possible. A truly successful governance plan relies upon the voluntary cooperation of all SharePoint users. (Kuna pindo kesi ambapo ushirikiano wa jamii si zinahitajika, kama vile wakati SharePoint hutumiwa na idadi ndogo sana ya watumiaji kukazwa imeweza; Mimi nina uhakika unaweza kufikiria wengine). If the user community doesn’t buy into your governance plan then it will be partially successful at best.
I use that word “buy” deliberately. The community will buy the governance plan if it’s fundamentally sound and you go to some effort to sell them on it. Selling leads to marketing and that’s why I think that a governance plan should be considered a marketing plan too. Convince your end users that they need to follow the governance plan and they will voluntarily follow it. If you can get a critical mass of people following the governance plan then the plan’s benefits follow and you’ll have a stronger environment for it.
</mwisho>
Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin
Mimi naweza kuandika juu kwa kirefu kuhusu MSDN vikao, etiquette, kumtaja mikataba, kutafuta, nk. I may do that, kwa kweli. I wanted to point out a small thing which may help people have a better overall experience.
Nimekuwa siku za hivi karibuni imekuwa kuwaambia watu kwamba kama wewe kukimbia katika baadhi ya aina ya tatizo na SharePoint mazingira yako, maendeleo ya mradi au nyingine SharePoint kuhusiana shughuli, post a question to the forums earlier in your action chain rather than later. I know for myself that when I have a problem, a number of potential solutions present themselves right away. I order these potential solutions in terms of likelihood, applicability and how easy they are to investigate. I go through that list and by the time I’ve gotten to #10, Mimi nina kufanya mabadiliko ya Usajili wa ufunguo "/ foo / bar / almostThere / isThisIt / noThisIsNotIt / iCantBelieveIAmDoingThis / finallyThere!"Kwa ushauri wa blog kupatikana katika ukurasa 8 of a Google search. When that doesn’t work, Mimi hatimaye baada ya swali kwa MSDN (e.g. hapa: http://social.technet.microsoft.com/Forums/en-US/sharepointgeneral/threads).
I suggest that you reverse that approach. Post the forums much earlier in your investigation because:
Hivyo, kimsingi, ni rahisi na bure na una risasi nzuri katika kupata aina fulani ya jibu, lakini itachukua muda kupata jibu (tena, isipokuwa wewe ni bahati).
I used to think that I should hold off on looking for community help because I don’t want to waste someone’s time asking for help when I could find it out myself. Some forum moderators and active participants may feel that way, lakini mimi si (angalau, Mimi wala kuhisi kwamba njia yoyote zaidi). I don’t see any downside. The worst case is that you post a question and then answer it yourself some time later, possibly “wasting” some one’s time. I don’t see a big risk in that and there’s value in the researching of questions like that in any event.
</mwisho>
Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin
Nimesoma retrospectives chache juu ya 2008 and this has got me to thinking about 2009. Here are my guesses at the future of SharePoint in 2009.
Mimi nina MVP SharePoint na kama matokeo, I sometimes get a little advance information before it’s public. I am NOT making any such information public. I really haven’t been around long enough to be entrusted with that kind of stuff anyway.
Pamoja na kwamba nje ya njia, kwenye utabiri ...
I believe that FAST will become a very hot topic in 2009. It’s already well known in the enterprise search community. Hata hivyo, kwamba kila mtu anacheza karibu na SharePoint katika 2009 will soon be interested in this product and what it can do for them. New consulting companies will spring up around it and existing partners will work and scramble to add it to its portfolio. This time next year, karibu kila mtu katika jamii SharePoint itakuwa nimesikia habari na kuwa na maoni juu FAST.
FAST is targeted at large companies and that will continue. I think there’s at least an outside chance that Microsoft will release a more focused version of the product that is accessible to smaller companies. Failing that, they will open up the SharePoint search engine so that it can be customized along the lines that FAST can be customized. Kwa mfano, FAST uses pipeline architecture for consuming content and indexing it. FAST admins and developers can assemble pipeline components per data source and even create new pipeline components. We don’t have this flexibility with SharePoint today. If FAST remains firmly targeted at very large companies, SharePoint tafuta mapenzi kupitisha baadhi ya makala ya FAST.
Naamini itakuwa kuja nje katika 2009.
I believe that it will provide us the ability to secure views on a list or document library. This may be more of a hope than a belief 🙂
Natumaini itakuwa kutoa baadhi msaada bora kwa watumiaji wa mwisho katika Designer SharePoint na hasa workflow.
Sijui kiasi kingine, I have been actively tracking what I do find here: http://delicious.com/pagalvin/SharePoint_O14.
Leo, most SharePoint vendors seem to be gadget oriented. Take Mianzi au Corasworks kwa mfano. They have a huge following and great portfolio of products. Hata hivyo, wanaonekana aina ya gadgety kwangu au developer / tool focused. Admin tools, workflow zana, nk. That’s not a criticism at all because SharePoint can definitely use some gadgets.
Katika 2009, baadhi ya wachuuzi (sana na uwezekano wa Bamboo wenyewe, kama mimi kusoma hii kwa usahihi) kuweka pamoja maombi ya biashara verticalized katika fomu ya templates, makala, ufumbuzi, nk. I’m thinking about the fabulous forty templates today but tailored to specific industries. I’m sort of surprised it’s not already exploited this way. SharePoint is a platform for delivering these kinds of things. What’s everyone waiting for? They won’t wait any longer in 2009.
Wakati huo huo, Sliverlight na nyingine baridi. NET mambo itazua mpya, bora zaidi na ya kuvutia gadgets.
Sharepointreviews.com itakuwa muhimu jumuiya ya orodha ya bidhaa hizo.
2009 utaona kuibuka mtumiaji Mwisho kama shabaha kuu kwa wanablogu, organizations and Microsoft themselves. Mwisho Mark Miller Maoni ya SharePoint.Com jukumu kubwa la 2008 and will continue to do so in 2009. End Users will begin to blog, kusaidia kubadilisha makundi ya mtumiaji katika kumbi chini ya kiufundi na hata kushawishi mtu au shirika kuzindua safi mtumiaji wa mwisho ililenga mkutano.
Speaking of conferences – they will continue to expand and grow in number and focus. Aside from end user content, wataendelea kuhudumia watengenezaji na watendaji.
Mikutano virtual kuanza kuchukua na zilizopo mikutano itatoa kuishi feeds kwa waliohudhuria kijijini ambao hawawezi au kuchagua si kuhudhuria katika mtu.
Kumbi bure itapanua, kama vile Mike Lotter ya (et al) SharePoint Jumamosi.
Hii ni kwenda kuwa muhimu sana kwa sababu kuna itaendelea kuwa na kufurika kubwa ya watengenezaji mpya, admins na watumiaji wa mwisho ambao watakuwa tamaa aina ya taarifa makundi haya kutoa.
Demand for social computing features will rise. All things being equal, makampuni ambayo kutekeleza mikakati madhubuti ya kompyuta kijamii kufanya vizuri na kuwa na nguvu zaidi kuliko washindani wao.
Makampuni madogo kupitisha makala haya kwa haraka zaidi na kwa ufanisi zaidi kuliko makampuni makubwa.
Makampuni makubwa ya: beware 🙂
Katika 2008, mengi ya wanablogu SharePoint na mashirika na Microsoft wenyewe alitumia muda mwingi kuhesabia njia bora ya kutatua matatizo ya baadhi ya (kawaida matatizo ya kiufundi).
There are still opportunities to define and foster adoption of best practices. Hata hivyo, wakati tumekuwa kuhesabia njia bora ya kufunga, configure na kusimamia SharePoint, mamia na maelfu ya makampuni wamekuwa kufunga, Configuring na kusimamia SharePoint bila mazoea ya wale bora katika mkono.
Katika 2009, a lot of companies are going to realize they have some deeply rooted problems to solve and will be looking to the elite members of the SharePoint community and Microsoft for help to fix them. I think this will extend well into 2010 na uwezekano wa spawn sekta ya Cottage kutoa huduma remediation kwa makampuni ambayo kwa kweli wanahitaji na kutumia SharePoint, lakini ni kuumiza vibaya kwa sababu ya maamuzi maskini kufanywa mapema katika utekelezaji wake.
Katika 2009, Meli mama atarudi na kuleta Bob Fox nyumbani.
Mimi si kuanza kufanya kazi na SharePoint mwenyewe katika njia yoyote halisi hadi Januari 2007. Inaonekana kwangu kwamba SharePoint ina kweli kuchukuliwa mbali na kuthibitika yenyewe uwezo wa kutoa mengi ya thamani katika miaka hii miwili. Nadhani kwamba katika njia nyingi, haikuwa kweli kunyoosha yenyewe nje mpaka miundombinu update. Bado ina matatizo yake na mende, lakini tumekuwa wote kuja njiani tangu 01/2007. 2009 ni kwenda kuwa mwaka bendera kwa SharePoint.
</mwisho>
Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin
Hii ni haki maarufu "fabulous 40" template. It also has a bug which is widely known (Nimekuwa hata blogged kuhusu jinsi ya kurekebisha).
Sogeti iliyotolewa codeplex mradi wiki hii kwamba fixes mdudu (ambayo ni nzuri na yenyewe, lakini si kuvunja ulimwengu) lakini pia wanadai kuwa wametatua tatizo sana thornier: security. The fab 40 template inahitaji wakarimu sana usalama wa mazingira ya (watumiaji mahitaji mchangiaji ngazi ya upatikanaji wa kila kitu karibu). Not any more! According to the codeplex summary:
"This template also includes a new custom workflow action which enables the template to work without having to give all users contribute permissions to the courses list."
Kwamba ni vizuri stuff na thamani ya kuangalia nje.
</mwisho>
