maandelikse Argiewe: April 2009

Bestuur is 'n bemarkingsplan te

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 nie skep SharePoint sekuriteit groep; gebruik AD plaas.
  • Jy mag nie skep dopgehou in dokument biblioteke; gebruik om die inhoud tipes en menings plaas.
  • Jy sal skep al dokument inhoud tipes grond af 'n spesifieke persoonlike basis tipe.
  • Jy mag nie 'n inligting taksonomie wat gebaseer is af vandag se maatskappy org grafiek.

"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>

Skryf in op my blog.

Volg my op Twitter http://www.twitter.com/pagalvin

Oplossing: Samestelling van MOSS Gehoor voeg geen nuwe lede

Bottom line: As jy wil 'n profiel eiendom te gebruik in 'n reël vir die skep van gehore, die eiendom moet sigbaar wees aan "almal."

I was working with a co-worker yesterday and he was building out a MOSS audience based on a custom user profile property in MOSS. In hierdie geval, die gehoor eiendom is die naam "SITECD" en deur konvensie, slaan 'n 3 karakter-kode. Hy het bepaal die gehoor en 'n reël wat sê dat as "SITECD gelyk aan 'ABG", dan sluit die gebruiker profiel in die gehoor.

Hy het 'n enkele gebruiker profiel met dat die waarde en saamgestel om die gehoor, but MOSS simply wouldn’t add that user. I noticed that the privacy setting for that profile was set to “me only” (die mees beperkende vorm) and I remembered reading somewhere that property profiles used in rules must be visible by “everyone”. He made that change and that solved the problem.

The really funny thing about this is that I “remembered” reading about this. It was nagging at me this morning for some reason and I realized that I had written a chapter in this book, MOSS Verduidelik: 'N Werker se inligting te duik diep in Microsoft Office SharePoint Server 2007, en dat ek hierdie punt behandel het in die baie hoofstuk het ek geskryf :). I would have thought that every word I wrote in that chapter would be seared into my memory.

Matt Morse skryf dit op in 'n pragtige detail hier en ek verwys dit in die hoofstuk: http://blogs.pointbridge.com/Blogs/morse_matt/Pages/Post.aspx?_ID=50

</einde>Skryf in op my blog.

Volg my op Twitter http://www.twitter.com/pagalvin

Technorati Tags: ,

Gebruik MSDN (en ander) Forum vir SharePoint Ondersteuning

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:

  • Dit is in elk geval gratis aan jou.
  • Daar is geen gewaarborgde SLA (waarvan ek weet, ten minste).
  • Daarom, dit kan 'n lang tyd neem om vir mense om te reageer.
  • Mense reageer dikwels uiteindelik nie.
  • As jy wag totdat 2 of 3 dae na die probleem 1 opgeduik, jy woes is vir 'n antwoord en forums is nie 'n goeie plek vir 'n noodgeval hulp (tensy jy gelukkig is).

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>

Skryf in op my blog.

Volg my op Twitter http://www.twitter.com/pagalvin

Technorati Tags: ,

Klein Nota Oor Microsoft Online Services wagwoorde en Administrasie

Ek het begin om te werk met Microsoft se Small Business produktiwiteit Online Suite n paar maande gelede, but now I have some better reason to be using it.

Ek is nog steeds besig om my manier om dit, sodat ek kan wees om 'n paar van die terminologie verkeerd, maar daar is basies twee groot koppelvlakke: die administrasie sentrum en die dienste wat hulle.

Die stelsel het my vertel dat ek het my wagwoord te verander, so I went ahead and did that. That allowed me to proceed and work with the services part (SharePoint, e-pos, en live vergadering). Egter, toe ek na die administrasie skerm, sou dit nie laat my deur vir my vertel dat hy nie glo dat my wagwoord korrek was.

The behavior was a little odd. If I entered the password I *thought* it should be, it would blank out the userid and the password and tell me the password or userid was incorrect. If I entered a blatantly wrong password, dit sal vertel my dieselfde, maar hou die gebruiker ID veld ongeskonde.

Ek het al speel rond met dit vir 'n rukkie en uiteindelik genoem (ja, op 'n Sondag oggend). Ongelooflik, 'n mede-, Ben, answered the phone right away. En, Ek het nie 'n kredietkaart te betree.

Lang storie kort, the administration center password uses different password rules than the services password. Admin password must contain alpha, numeric and special characters. When I changed my admin password the first time, Ek het nie volg die reël (dit het ook nie waarsku my!). I was able to change it to a valid administration password and got back in.

As jy ervaar dat die soort van probleme in die toekoms, jy weet wat vir my gewerk het en hopelik sal dit werk vir jou.

</einde>Skryf in op my blog.

Volg my op Twitter http://www.twitter.com/pagalvin

Die SharePoint soos 'n besigheid bedryf stelsel

Vandat ek gehoor het 'n kwotasie, na bewering tydens 'n Q&'N sessie met Steve Ballmer in Maart 2007, I’ve sort of been holding my breath for something to happen. The quote was basically this: “SharePoint is an operating system for business applications.” Knowing a fair bit about SharePoint and a middling bit about operating systems, I thought it was really apt. I’m holding my breath, waiting for companies to really buy into that concept and start to build applications within the SharePoint “operating system.”

Ek het 'n baie gedink aan hierdie onderwerp gewy hierdie jaar (gaan terug na my 2009 voorspellings) en ek gaan om te praat oor dit by die Mei 2de SharePoint Saterdag gebeurtenis in Washington.

Dit is die opsomming van my aanbieding, getiteld "Die gebruik van die SharePoint platform Vertikale Aansoeke om te bou":

"Horisontale?"Vertikale?"Wat wil hierdie woorde beteken in 'n SharePoint konteks? SharePoint, soos ons dikwels hoor, is 'n "platform" vir die bou van toepassings. Hierdie feit word dikwels op ons verloor sedert die sogenaamde horisontale platform funksies, soos dokument bestuur en soek, are so easy and useful in and of themselves. Egter, SharePoint is nog sterker en groter waarde sal terugkeer wanneer dit gebruik om vertikale aansoeke wat aangepas is om jou besigheid se dag om te voldoen aan die dag vereistes te skep. Hierdie sessie beskryf hoe platform funksies in 'n verticalized oplossing met behulp van 'n ware voorbeeld vir die wêreld om sake te vergader - 'n verkope kwotasie bestuur en kliënt poort. Die spreker se doel is om jou oë oop te maak aan die moontlikhede die SharePoint platform en op te bou sy horisontale platform gespesialiseerde oplossings vir jou vertikale organisasie te skep.

As daardie vak nie jou boot dryf, there are a bunch of other good topics. And DC is a great venue in and of itself to visit.

Registrasie open hierdie Donderdag, 04/16. Keep on top of the site and grab a seat before it’s too late 🙂

</einde>

Skryf in op my blog.

Volg my op Twitter http://www.twitter.com/pagalvin

Kanadese Notule

Hierdie keer het verlede week, Ek was in Montreal, bywoning van die hoogs aanbeveel SharePoint Summit 2009. I gave a 3.5 hour tutorial on installing and customizing SharePoint. It was a scary subject on many levels. I’m not really a SharePoint admin, maar ek weet genoeg om 'n handleiding oor die onderwerp te gee. (Gelukkig, Geoff Schaller van Sagteware Doelwitte in Australië, onder 'n paar ander, was in die skare 'n paar van die dieper vrae te beantwoord [Ek weet nie wat hulle in die put, maar ons moet 'n paar van dit hier in die VSA]).

Maar, back to many levels of scariness… It had a lot of potential to be very boring. I actually installed WSS and then upgraded it to MOSS. In front of a room full of people. Canadian poeple. There were long 5 en 7 minute gaps where we were watching the installation process chug along. I needed to fill that time with something useful and interesting. I’m not sure I succeeded.

Ten slotte, it was loooong. Three and one half hours. That’s a long presentation. I made a little joke of it, saying “We have a long presentation ahead of us. Three and one half hours. That’s 210 minute. And I don’t even know how many minutes that is in Canadian.”

Almal het gelag en as gevolg, Montreal is officially on my Good Places list 🙂

Selfs as hulle het nie gelag my grap, I would love Montreal. I try very hard to be open minded and not take my cues from Suid-Park, maar ek moet erken, om my hartseer, that I had no idea how great is the metropolis of Montreal. I can’t wait to go back in a few months, wanneer dit 'n bietjie warmer, om weer te besoek.

Op 'n soort van verwante noot, Ek sit ook deur Erik Swenson se eerste openbare aanbieding getiteld "IA en Branding Proses: Sketse wireframes te Hi-Fidelity ontwerpe. " (Erik is my kollega EMC). Check out the abstract here: http://www.sharepointsummit2009.com/conference_day2.htm. Ek het selfs aangeteken is dit vir hom vir. I tried several times for some “action shots” and zoomed in on him when he paused to drink some water. I didn’t always succeed, but I tried 🙂

</einde>

Skryf in op my blog.

Volg my op Twitter http://www.twitter.com/pagalvin

Technorati Tags: