O meu compañeiro, David Drinkwine, does a (slightly more than) pen-on-napkin estimate for building a truly world class intranet for a large enterprise organization. Pode read about it here: (http://www.bigapplesharepoint.com/pages/View-An-Insight.aspx?BlogID=86&stitle=WCI).
</final>
SP2010 é unha cousa moi legal, pero me gustaría que puidesen axustar o idioma da lista e páxinas de bibliotecas das definicións cando se trata de tipos de contido xestión:
A lingua estaba no lugar para WSS / Moss. Só ten que cambiar a palabra "delete" para "eliminar" e só pode simplemente facer máis sentido.
Siga-me no Twitter http://www.twitter.com/pagalvin
</final>
O meu último artigo para SharePointBriefing.com é para arriba e patadas aquí: http://sharepointbriefing.com/features/article.php/3887276/The-Road-to-SharePoint-Mastery.htm
Aquí está o teaser:
Esta é basicamente unha versión moi curta e condensada da miña presentación en público máis popular "para aprender SharePoint." Sen bromas banjo, con todo.
Consulte!
</final>
Siga-me no Twitter http://www.twitter.com/pagalvin
(Nota: Este produto está cruzada posta aquí: http://www.endusersharepoint.com/?p=1912)
Actualizar 09/01/09: Con base no feedback do 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, que InfoPath uso (mesmo en Moss Standard Edition) don’t work in BPOS because their initiation and other forms use InfoPath. Hopefully that clears things up.
Eu tiven a oportunidade de realmente cavar en oferta en liña de Microsoft a principios deste ano e, especialmente, o 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, con todo, BPOS que podería ser unha parte fundamental da infraestrutura interna da miña empresa e ao longo do tempo, 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.
Como a palabra "suite" en BPOS implica, que obtén un pequeno paquete de aplicacións:
Podes mercar cada unha delas por separado, Creo. It’s all spelled out relatively clearly on the Microsoft sitio en liña. You may be able to get better deals through MSFT partners. Arcovis has been working with Estratexias de nubes e eles parecen coñecer as súas cousas, entón eu inclui-los na súa lista de provedores, se fai unha busca multi-vendor.
Eu delinear a miña experiencia e pensamentos de cada unha delas respectivamente,.
Este é un ambiente de intercambio Hosted e da miña perspectiva, 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 (que é enorme). Good stuff.
Tamén ofrece o Outlook Web Access (OWA) interface. That means I can get my email on any machine that has a web browser.
O meu teléfono móbil HTC, Windows Mobile 6.1(?) connected to it nicely via Active Sync. It did this in exactly the way I expected and wanted.
Eu non me considero moito máis que unha perspectiva do usuario casual e intercambio para que haxa recursos do Exchange realmente importantes que simplemente non son compatibles e non necesariamente sabe que.
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. En realidade, este é mellor porque simplemente funciona.
Bottom line - aloxado cambio é o que ten que ser e estou moi feliz con el.
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, ve-los romper miñas solucións para que eu saiba como reparalos los, facer presentacións de vendas, etc. 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. Con todo, para os meus propósitos, é óptimo.
Ata agora, 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, meus compañeiros saben cando estou dispoñible, o que a miña axenda é como neste momento, e pode IM me (aínda que a interface IM é ben aburrido, no mellor dos casos). 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, asignada unha tarefa, etc. 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.
Meu anaco favorito, claro, 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:
Basicamente, todo o que esperar para utilizar o SharePoint para.
Ao longo do camiño, usan características técnicas como:
O que non podo facer con el? 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.
Vostede basicamente dar unha morea de capacidade técnica e son forzados a vivir dentro dos límites de out-of-the-box funcionalidade do SharePoint.
I can live with that. I have found myself wanting to slap together an event receiver or use a custom action once or twice,, pero para a maior parte, Eu non notar a falta.
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 ofrece unha aplicación de escritorio bacana que permite o acceso fácil e rápida a todas as funcións BPOS:
Non é preciso usalo, pero elimina a necesidade de entrar en cada un dos programas por separado e para a reunión en directo, É moi bo porque podes facer un "encontro agora" sesión con só 2 click (unha sobre o "web conferencia" botón anterior e outro sobre o navegador web que aparece). It’s also nice to get OWA with one click, que pode só poñer isto nos seus favoritos do navegador, así.
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, Podo abrir os navegadores web e conectar o meu ambiente BPOS sen precisar escribir as credenciais.
Microsoft made BPOS available to me for free so I am not currently paying the monthly per user fee at this time. Con todo, Vexo valor alí e pode aceptar a fe (ou non) 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. Cambio, SharePoint (Moss estándar!), presenza, instantánea reunións en directo - é unha serie de funcións que eu sería moi, sorely miss if I had to live without it. My business would be severely impacted without it. Could I find replacement functionality? Probably, pero eu creo que eu tería que improvisar xuntos a partir dunha variedade de outros provedores, complicating my life. BPOS has so far proven itself to be stable and reliable. For the right kind of customer (como a miña empresa), BPOS val consideración forte.
</final>
Siga-me no Twitter http://www.twitter.com/pagalvin
Teño acompañado foros do MSDN para máis dun ano (e, posiblemente, case 2 ano neste punto) 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).
Tomando como exemplo MSDN, A primeira vez que ir á páxina estándar, como o foro de Cuestións xerais para SharePoint páxina principal aquí: http://social.technet.microsoft.com/Forums/en-US/sharepointgeneral/threads
Ten que inmediatamente observar que os foros son RSS habilitado, como se mostra:
Está a usar o Google Reader para xestionar os meus feeds RSS para un longo tempo agora (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 ofrece-me unha fermosa vista da mensaxe en si:
E, finalmente, Google me permite usar o teclado para percorrer as fotos no foro deste xeito.
Podo rapidamente facer a pescudas a través de mensaxes e concentrarse só sobre aqueles que sinto que podo dar unha contribución útil.
Alerts close the loop. Updates to posts don’t come through RSS (aínda que eu creo que usaron para moito tempo). Con todo, se eu publicar unha resposta a unha mensaxe do foro, the forums alert me via email and IM that someone responded in turn. Ou, se eu non podo dar unha contribución útil, pero quero saber o que outros teñen a dicir, Podo furar-lo e pedir explicitamente avisos cando os outros non responden.
Nunha hora ou menos pode definir este proceso para arriba e unha semana de uso regular, aprender os trucos e atallos de teclado diferentes para que isto se fai unha segunda natureza.
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/.
Os foros son un xeito impresionante, posiblemente, o mellor xeito curta de experiencia persoal directa, de aprendizaxe do produto e obter un levantamento legal de como o mundo, en xeral, uses SharePoint. Give it a try!
</final>
Siga-me no Twitter http://www.twitter.com/pagalvin
A razón por que gastar tanto tempo (ou debería, de calquera xeito) 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.
Para lograr este obxectivo desexable, un documento de gobernanza e plan pode transformar-se en unha morea de "ti debe" e "ti non é", como no:
"Ti debe" e "ti non" seguramente teñen o seu lugar no plan de goberno.
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. (Hai casos marxinais, onde non é necesaria a cooperación da comunidade, como cando o SharePoint é usado por un número moi reducido de usuarios ben xestionadas; Estou seguro que pode pensar en outros). 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.
</final>
Siga-me no Twitter http://www.twitter.com/pagalvin
Podería escribir longamente sobre foros MSDN, etiqueta, convencións de nomenclatura, buscar, etc. I may do that, de feito. I wanted to point out a small thing which may help people have a better overall experience.
Eu recentemente foi dicir á xente que, se ten algún tipo de problema co seu ambiente SharePoint, proxecto de desenvolvemento ou outra actividade relacionada SharePoint, 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, Estou facendo cambios no rexistro para unha clave "/ foo / bar / almostThere / isThisIt / noThisIsNotIt / iCantBelieveIAmDoingThis / finallyThere!"O consello dun blog atopar na páxina 8 of a Google search. When that doesn’t work, Eu finalmente publicar unha pregunta para MSDN (e.g. aquí: 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:
Así, basicamente, é doado e gratis e ten unha boa oportunidade de obter algún tipo de resposta, pero vai levar un pouco para chegar a resposta (novo, a menos que ten sorte).
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, pero eu non (polo menos, Eu non me sinto máis así). 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.
</final>
Siga-me no Twitter http://www.twitter.com/pagalvin
Lin algunhas retrospectivas sobre 2008 and this has got me to thinking about 2009. Here are my guesses at the future of SharePoint in 2009.
Eu son un SharePoint MVP e como resultado, 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.
Con iso fóra do camiño, en que as predicións ...
I believe that FAST will become a very hot topic in 2009. It’s already well known in the enterprise search community. Con todo, todo o mundo que xoga co SharePoint en 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, case todos na comunidade SharePoint terá oído falar e ter unha opinión sobre a 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. Por exemplo, 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, Investigación do SharePoint pode adoptar algunhas das características da FAST.
Eu creo que vai saír en 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 🙂
Espero que isto pode fornecer algún soporte mellor para os usuarios finais no SharePoint Designer e, particularmente, o fluxo de traballo.
Non sei moito máis, I have been actively tracking what I do find here: http://delicious.com/pagalvin/SharePoint_O14.
Hoxe, most SharePoint vendors seem to be gadget oriented. Take Bambú ou Corasworks por exemplo. They have a huge following and great portfolio of products. Con todo, eles parecen tipo de gadgety para min ou creador / tool focused. Admin tools, ferramentas de workflow, etc. That’s not a criticism at all because SharePoint can definitely use some gadgets.
En 2009, algúns provedores (e moi posiblemente si bambú, se eu ler isto correctamente) vai reunir aplicacións de negocios verticalizadas en forma de templates, recursos, solucións, etc. 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.
Á vez, Silverlight e outras cousas Net legal. Abastecerá novo, aparellos mellores e máis interesantes.
Sharepointreviews.com vai facer o catálogo esencial comunidade destes produtos.
2009 Vai ver a aparición do usuario final como un dos principais focos para blogueiros, organizations and Microsoft themselves. Mark Miller End User SharePoint.Com desempeñou un papel importante na 2008 and will continue to do so in 2009. End Users will begin to blog, axudar a transformar grupos de usuarios en lugares menos técnicos e mesmo convencer a alguén ou unha organización para lanzar un usuario final puro conferencia centrouse se.
Speaking of conferences – they will continue to expand and grow in number and focus. Aside from end user content, eles van continuar a atender a desenvolvedores e administradores.
Conferencias virtuais comezará a ir e conferencias existentes proporcionará transmisións en directo para os participantes remotos que non poden ou optan por non comparecer en persoa.
Espazos libres ha ampliar, como Mike Lotter de (et ai) SharePoint sábado.
Isto vai ser moi importante que vai seguir sendo un gran fluxo de novos desenvolvedores, administradores e usuarios finais que serán desexo o tipo de información que estes grupos ofrecen.
Demand for social computing features will rise. All things being equal, empresas que aplican estratexias eficaces de computación social vai facer mellor e ser máis forte do que os seus competidores.
As pequenas empresas van adoptar estes recursos de forma máis rápida e eficaz que as grandes empresas.
Grandes empresas: beware 🙂
En 2008, unha morea de blogueiros e organizacións do SharePoint e Microsoft gasta-se moito tempo para descubrir a mellor forma de resolver certos problemas (problemas técnicos xeralmente).
There are still opportunities to define and foster adoption of best practices. Con todo, mentres estamos tentando descubrir a mellor forma de instalar, configurar e xestionar SharePoint, centos e miles de empresas teñen que chegou a instalar, configuración e xestión SharePoint sen esas mellores prácticas na man.
En 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 e, posiblemente, xerar unha industria prestación de servizos de reparación para as empresas que realmente precisan e usan SharePoint, pero son gravemente prexudicadas debido de malas decisións feitas no inicio da súa posta en marcha.
En 2009, a nave nai vai volver e traer Bob Fox casa.
Non comece a traballar co SharePoint min de forma real ata xaneiro 2007. Paréceme que o SharePoint realmente despegou e se revela capaz de proporcionar unha gran cantidade de valor nestes dous anos. Eu creo que, en moitos aspectos, realmente non endereitarse-se para fóra ata actualizar a infraestrutura. El aínda ten os seus erros e problemas, pero todos nós temos que chegou ao longo camiño dende 01/2007. 2009 será dun ano destacada para SharePoint.
</final>
Siga-me no Twitter http://www.twitter.com/pagalvin
Este é un moi popular "fabuloso 40" modelo. It also has a bug which is widely known (Eu mesmo escribín sobre como resolve-lo).
Sogeti emitiu un proxecto CodePlex esta semana que corrixe o erro (o que é bo por si só, pero non a terra tremer) pero eles tamén afirman ter resolto un problema máis espiñento moi: seguridade. The fab 40 modelo require unha configuración de seguranza moi xeneroso (necesidades de usuarios nivel contribuínte o acceso a practicamente todo). 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."
Isto é algo bo e paga a pena revisar.
</final>
