My kollega, David Drinkwine, does a (slightly more than) pen-on-napkin estimate for building a truly world class intranet for a large enterprise organization. Jy kan read about it here: (http://www.bigapplesharepoint.com/pages/View-An-Insight.aspx?BlogID=86&stitle=WCI).
</einde>
SP2010 is baie cool dinge, maar ek wens hulle sou aangepas het om die taal op lys en biblioteke instellings 'bladsye wanneer dit kom by die bestuur van die inhoud tipes:
Dieselfde taal was in plek vir WSS / MOSS. Net verander die woord "verwyder" te "verwyder" en dit sal duidelik maak net meer sin.
Volg my op Twitter http://www.twitter.com/pagalvin
</einde>
My nuutste artikel vir SharePointBriefing.com is op en skop hier: http://sharepointbriefing.com/features/article.php/3887276/The-Road-to-SharePoint-Mastery.htm
Hier is 'n teaser:
Dit is basies 'n mooi kort en verkorte weergawe van my gewildste openbare aanbieding oor "Op SharePoint om te leer." Geen banjo grappies, egter.
Check dit uit!
</einde>
Volg my op Twitter http://www.twitter.com/pagalvin
(Let daarop: hierdie artikel is oor wat hier gepos: http://www.endusersharepoint.com/?p=1912)
Werk 09/01/09: Gegrond op twitter terugvoer, 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, wat gebruik Path (selfs in MOSS standaard uitgawe) don’t work in BPOS because their initiation and other forms use InfoPath. Hopefully that clears things up.
Ek het 'n kans om werklik te grawe in Microsoft Online se offer vroeër vanjaar en spesifiek die besigheid produktiwiteit aanlyn suite (BPOS). This came along before I even hard a firm plan to set out on my own at Arcovis. I immediately saw, egter, BPOS kan 'n belangrike deel van my maatskappy se interne infrastruktuur en met verloop van tyd, 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.
Soos die woord "suite" in BPOS impliseer, jy kry 'n klein bondeltjie van aansoeke:
Jy kan koop elkeen van hulle afsonderlik, Ek glo. It’s all spelled out relatively clearly on the Microsoft aanlyn werf. You may be able to get better deals through MSFT partners. Arcovis has been working with Wolk Strategieë en dit lyk asof hulle om hul dinge te leer ken, so ek wil sluit dit in jou lys van verskaffers, as jy 'n multi-verkoper soek.
Ek Gee 'n oorsig van my ervaring en gedagtes vir elk van hierdie.
Dit is 'n bedryf ruil omgewing en uit my perspektief, 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 (wat is 'n groot). Good stuff.
Dit bied ook die Outlook Web Access (OWA) interface. That means I can get my email on any machine that has a web browser.
My HTC selfoon, met Windows Mobile 6.1(?) connected to it nicely via Active Sync. It did this in exactly the way I expected and wanted.
Ek vind myself nie veel meer as 'n toevallige uitkyk en ruil gebruiker, sodat daar dalk regtig belangrik Exchange funksies wat net nie ondersteun nie en ek weet dat dit nie noodwendig.
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. In werklikheid, Dit is beter, want dit net werk.
Bottom line - Hosted Exchange is wat dit moet wees, en ek is baie tevrede met dit.
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, om te kyk hoe hulle my oplossings te breek sodat ek weet hoe om hulle op te los, doen verkope aanbiedings, ens.. 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. Egter, vir my doeleindes, dit is wonderlik.
So ver, 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 kollegas weet wanneer ek, wat my skedule is soos op hierdie oomblik, en kan IM my (alhoewel die IM-koppelvlak is redelik dof, op sy beste). 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, opgedra om 'n taak, ens.. 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 gunsteling bietjie, natuurlik, 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:
Basies, al die dinge wat jy sou verwag die SharePoint te gebruik vir.
Langs die pad, Ons gebruik tegniese funksies soos:
Wat ek nie kan doen met dit? 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.
Jy basies 'n baie tegniese vermoë en gedwing word om te leef binne die grense van out-of-the-box SharePoint funksionaliteit.
I can live with that. I have found myself wanting to slap together an event receiver or use a custom action once or twice,, maar vir die grootste deel, Ek sien nie die gebrek aan.
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 bied 'n baie interessante lessenaar program wat dit moontlik maak om vinnige en maklike toegang tot al die BPOS funksies:
Jy hoef nie om dit te gebruik, maar skakel die behoefte om aan te meld in elk van die aansoeke apart en vir live vergadering, Dit is baie lekker want jy kan met net 'n "ontmoet nou"-sessie doen 2 kliek (een op die internet konferensies "knoppie hierbo en die ander op die web-leser wat verskyn). It’s also nice to get OWA with one click, asof jy net kan sit dit in jou browser gunstelinge sowel.
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, Ek kan oopmaak webblaaiers en sluit aan my BPOS omgewing sonder om ooit nodig om geloofwaardigheid te betree.
Microsoft made BPOS available to me for free so I am not currently paying the monthly per user fee at this time. Egter, Ek sien waarde daar en jy kan op geloof aanvaar (of nie) 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!), teenwoordigheid, oomblik live vergaderings - dit is 'n baie funksies wat ek wil hard, sorely miss if I had to live without it. My business would be severely impacted without it. Could I find replacement functionality? Probably, maar ek dink dat ek wil hê om dit te Cobble saam uit 'n verskeidenheid van ander verskaffers, complicating my life. BPOS has so far proven itself to be stable and reliable. For the right kind of customer (soos my maatskappy), BPOS is die moeite werd sterk oorweeg.
</einde>
Volg my op Twitter http://www.twitter.com/pagalvin
Ek is na aanleiding van MSDN forums vir meer as 'n jaar (en moontlik byna 2 jaar op hierdie punt) 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).
Neem MSDN as 'n voorbeeld, Ek het eers na standaard forum bladsy soos die Algemene Vrae vir SharePoint hoofblad hier: http://social.technet.microsoft.com/Forums/en-US/sharepointgeneral/threads
Jy moet dadelik sien dat die forums is RSS enabled, soos aangedui:
Ek het al met behulp van Google Reader vir die bestuur van my RSS Feeds vir 'n lang tyd (www.google.com / reader). 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 bied vir my 'n mooi uitsig van die plaas self:
En uiteindelik, Google laat my gebruik van die sleutelbord te blaai deur die plasings in die forums op hierdie manier.
Ek kan vinnig scan deur poste en fokus net op dié wat ek voel ek kan 'n waardevolle bydrae kan lewer.
Alerts close the loop. Updates to posts don’t come through RSS (maar ek dink hulle gebruik om 'n lang tyd gelede). Egter, As ek 'n antwoord op 'n forum plaas, the forums alert me via email and IM that someone responded in turn. Of, As ek nie 'n sinvolle bydrae te lewer, maar ek wil weet wat ander te sê het, Ek kan boor in dit en uitdruklik versoek om kennisgewings wanneer ander nie reageer.
In 'n uur of minder jy kan hierdie proses opgestel en en in 'n week van gereelde gebruik, leer om die verskillende sleutelbord truuks en kortpaaie sodat dit 'n tweede natuur.
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/.
Forums is 'n wonderlike manier, moontlik die beste manier kort van die direkte persoonlike ervaring, van die leer van die produk en kry 'n mooi opname van hoe die wêreld, op groot, uses SharePoint. Give it a try!
</einde>
Volg my op Twitter http://www.twitter.com/pagalvin
Die rede waarom ons so baie tyd spandeer (of indien, in elk geval) 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.
Wat wenslik doelwit te bereik, 'n dokument bestuur en plan kan oorgaan in 'n klomp "Jy mag" en "Jy mag nie se", soos in:
"Jy mag" en "jy mag nie" beslis het hul plek in die bestuur plan.
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. (Daar is byvoordele gevalle waar die gemeenskap samewerking is nie nodig nie, soos wanneer SharePoint word deur 'n baie klein aantal streng bestuur gebruikers; Ek is seker jy kan dink van ander). 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.
</einde>
Volg my op Twitter http://www.twitter.com/pagalvin
Ek kan skryf op groot lengte oor MSDN forums, etiket, benoemings konvensies, soek, ens.. I may do that, in werklikheid. I wanted to point out a small thing which may help people have a better overall experience.
Ek het die afgelope tyd is om die mense te vertel dat as jy in 'n soort van probleem met jou SharePoint omgewing, die ontwikkelingsprojek of ander SharePoint aktiwiteit wat verband hou met, 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, Ek maak veranderinge in die register na 'n sleutel "/ foo / bar / almostThere / isThisIt / noThisIsNotIt / iCantBelieveIAmDoingThis / finallyThere!"Op die advies van 'n blog verskyn op bladsy 8 of a Google search. When that doesn’t work, Ek het uiteindelik na 'n vraag te MSDN (bijv. hier: 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:
So, basies, dit is maklik en vry, en jy het 'n goeie kans om 'n soort van die antwoord, maar dit sal 'n rukkie neem om daardie antwoord te kry (weer, tensy jy gelukkig is).
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, maar ek doen nie (ten minste, Ek voel nie dat die pad nie meer). 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.
</einde>
Volg my op Twitter http://www.twitter.com/pagalvin
Ek het gelees 'n paar retrospectieves op 2008 and this has got me to thinking about 2009. Here are my guesses at the future of SharePoint in 2009.
Ek is 'n SharePoint MVP en as gevolg, 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.
Met dit uit die pad, op die voorspellings ...
I believe that FAST will become a very hot topic in 2009. It’s already well known in the enterprise search community. Egter, almal wat speel rond met SharePoint in 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, byna almal in die SharePoint gemeenskap sal gehoor het van en 'n mening oor 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. Byvoorbeeld, 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 soek sal neem sommige van FAST se funksies.
Ek glo dit sal kom in 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 🙂
Ek hoop dit sal 'n beter ondersteuning vir gebruikers voorsien in SharePoint Designer en veral workflow.
Ek het nie veel anders weet, I have been actively tracking what I do find here: http://delicious.com/pagalvin/SharePoint_O14.
Vandag, most SharePoint vendors seem to be gadget oriented. Take Bamboes of Corasworks byvoorbeeld. They have a huge following and great portfolio of products. Egter, dit lyk asof hulle soort van gadgety vir my of ontwikkelaar / tool focused. Admin tools, workflow tools, ens.. That’s not a criticism at all because SharePoint can definitely use some gadgets.
In 2009, sommige verkopers (en heel moontlik Bamboo hulself, As ek dit gelees het korrek) bymekaar sal sit verticalized besigheid aansoeke in die vorm van templates, funksies, oplossings, ens.. 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.
Op dieselfde tyd, Silverlight and other cool .NET stuff will fuel new, better and more interesting gadgets.
Sharepointreviews.com will become the essential community catalog of these products.
2009 will see the emergence of the End User as a major focus for bloggers, organizations and Microsoft themselves. Mark Miller’s End User SharePoint.Com played a big role in 2008 and will continue to do so in 2009. End Users will begin to blog, help to transform user groups into less technical venues and even convince someone or organization to launch a pure End User focused conference.
Speaking of conferences – they will continue to expand and grow in number and focus. Aside from end user content, they will continue to cater to developers and administrators.
Virtual conferences will start to pick up and existing conferences will provide live feeds to remote attendees who cannot or choose not to attend in person.
Free venues will expand, soos Mike Lotter’s (et al) SharePoint Saterdag.
This is going to be very important because there will continue to be a large influx of new developers, admins and end users who will be craving the kind of information these groups provide.
Demand for social computing features will rise. All things being equal, maatskappye wat implementeer effektiewe sosiale rekenaar strategieë sal beter doen en sterker wees as hulle mededingers.
Kleiner maatskappye sal neem hierdie funksies meer vinnig en doeltreffend as groot maatskappye.
Groot maatskappye: beware 🙂
In 2008, 'n baie SharePoint bloggers en organisasies en Microsoft hulself spandeer baie tyd uitzoeken die beste manier is om sekere probleme op te los (gewoonlik tegniese probleme).
There are still opportunities to define and foster adoption of best practices. Egter, terwyl ons al uitzoeken die beste manier om te installeer, instel en bestuur SharePoint, honderde en duisende van maatskappye is die installering, configuring and managing SharePoint without those best practices at hand.
In 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 and possibly spawn a cottage industry providing remediation services for companies that really need and use SharePoint, but are hurting badly because of poor decisions made early in their implementation.
In 2009, the Mother Ship will return and bring Bob Fox home.
I didn’t start working with SharePoint myself in any real way until January 2007. Dit lyk vir my dat SharePoint regtig geneem het en bewys kan lewer 'n baie waarde in hierdie twee jaar. Ek dink dat in baie maniere, Dit het nie regtig reguit self uit totdat die infrastruktuur werk. Dit het nog steeds sy foute en probleme, maar ons het almal kom langs pad sedert 01/2007. 2009 gaan 'n banier jaar vir SharePoint wees.
</einde>
Volg my op Twitter http://www.twitter.com/pagalvin
Dit is 'n redelik gewild "pragtige 40" sjabloon. It also has a bug which is widely known (Ek het selfs al blog oor hoe om dit op te los).
Sogeti vrygestel van 'n codeplex projek hierdie week wat die fout opgelos (wat op sigself is 'n mooi, maar nie aardskuddende) maar hulle het ook beweer dat hulle 'n baie tornooi probleem opgelos: sekuriteit. The fab 40 Die sjabloon vereis 'n baie vrygewige sekuriteit instelling (gebruikers moet bydraer vlak toegang tot feitlik alles). Not any more! According to the codeplex summary:
"Hierdie sjabloon sluit ook 'n nuwe persoonlike workflow aksie wat jou in staat stel om die template om te werk sonder om te gee alle gebruikers bydra regte tot die kursusse."
Dit is goeie dinge en die moeite werd.
</einde>
