بایگانی ماهانه: آوریل 2009

Governance is a Marketing Plan Too

The reason we spend so much time (or should, در هر صورت) 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”, همانطور که در:

  • Thou shall not create SharePoint security group; use AD instead.
  • Thou shall not create folders in document libraries; use content types and views instead.
  • Thou shall create all document content types based off a specific custom base type.
  • Thou shall not create an information taxonomy based off today’s company org chart.

“Thou shall” and “thou shall not” certainly have their place in the governance 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. (There are fringe cases where community cooperation is not needed, such as when SharePoint is used by a very small number of tightly managed users; I’m sure you can think of others). 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.

</پایان>

مشترک شدن در وبلاگ من.

من در توییتر در http://www.twitter.com/pagalvin

راه حل: کامپایل تماشاگران MOSS می افزاید بدون کاربران جدید

خط پایین: if you want to use a profile property in a rule for creating audiences, the property must be visible to “everyone.”

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. در این مورد, the audience property is named “SITECD” and by convention, stores a 3 character code. He had defined the audience and a rule that said that if “SITECD equals ‘ABG’”, then include that user profile in the audience.

He set up a single user profile with that value and compiled the audience, but MOSS simply wouldn’t add that user. I noticed that the privacy setting for that profile was set to “me only” (the most restrictive form) 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 Explained: An Information Worker’s Deep Dive into Microsoft Office SharePoint Server 2007, and that I covered this point in the very chapter I wrote :). I would have thought that every word I wrote in that chapter would be seared into my memory.

Matt Morse writes this up in beautiful detail here and I referenced it in the chapter: http://blogs.pointbridge.com/Blogs/morse_matt/Pages/Post.aspx?_ID=50

</پایان>مشترک شدن در وبلاگ من.

من در توییتر در http://www.twitter.com/pagalvin

با استفاده از MSDN (و دیگر) انجمن ها برای شیرپوینت پشتیبانی

من می توانم در طول بزرگ در مورد انجمن MSDN ارسال, علم اداب معاشرت, نامگذاری کنوانسیون, جستجو, غیره. I may do that, در واقع. I wanted to point out a small thing which may help people have a better overall experience.

من به تازگی شده است گفتن مردم است که اگر شما را به نوعی از مشکل با محیط شیرپوینت خود را اجرا کنید, طرح توسعه و یا سایر فعالیت های مرتبط با شیرپوینت, 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, من ایجاد تغییرات در رجیستری را به یک کلید "/ تولی / نوار / almostThere / isThisIt / noThisIsNotIt / iCantBelieveIAmDoingThis / finallyThere!"در مشاوره یک وبلاگ در صفحه 8 of a Google search. When that doesn’t work, من در نهایت یک سوال به MSDN (e.g. اینجا: 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:

  • این برنامه رایگان به شما به هر حال.
  • هیچ SLA تضمین شده وجود دارد (که من آگاه هستم, حداقل).
  • بنابراین, آن می تواند مدت زمان طولانی برای مردم را به پاسخ.
  • مردم اغلب در نهایت پاسخ.
  • اگر شما منتظر بمانید تا 2 یا 3 روز پس از مشکل برای اولین بار ظاهر, شما از کوره در رفته برای پاسخ و انجمن ها مکان خوبی برای کمک اضطراری نیست (مگر اینکه شما خوش شانس هستید).

پس, بطور اساسی, آن آسان و رایگان است و شما باید در موقعیت خوبی قرار گرفتن برخی از نوع پاسخ, اما آن را در حالی که برای دریافت کنید که پاسخ (دوباره, مگر اینکه شما خوش شانس هستید).

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, اما من نمی (حداقل, من که راه احساس نمی). 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.

</پایان>

مشترک شدن در وبلاگ من.

من در توییتر در http://www.twitter.com/pagalvin

برچسب ها: ,

نکته کوچک درباره مایکروسافت خدمات آنلاین کلمات عبور و مدیریت

I started to work with Microsoft’s Small Business Productivity Online Suite several months ago, but now I have some better reason to be using it.

I’m still working my way around it, so I may be getting some of the terminology wrong, but basically there are two major interfaces: the administration center and the services themselves.

The system was telling me that I had to change my password, so I went ahead and did that. That allowed me to proceed and work with the services part (شیرپوینت, پست الکترونیک, and live meeting). اما, when I went to the administration screen, it wouldn’t let me in by telling me that it didn’t believe my password was correct.

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, it would tell me the same, but keep the user ID field intact.

I’ve been playing around with this for a little while and finally called (بله, on a Sunday morning). باور نکردنی, a fellow, Ben, answered the phone right away. و, I didn’t have to enter a credit card.

داستان کوتاه مدت, 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, I didn’t follow that rule (nor did it warn me!). I was able to change it to a valid administration password and got back in.

If you experience that kind of problem in future, you know what worked for me and hopefully it will work for you.

</پایان>مشترک شدن در وبلاگ من.

من در توییتر در http://www.twitter.com/pagalvin

شیرپوینت به عنوان یک سیستم عامل کسب و کار

از زمانی که من شنیده ام نقل قول, بنا به گزارش ها در س&جلسه با استیو بالمر در ماه مارس 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.”

من بسیاری از فکری به این موضوع در سال جاری اختصاص داده ام (رفتن به من 2009 پیش بینی) و من قصد دارم تا در این مورد صحبت می کنند در مه 2 شیرپوینت شنبه مراسمی در واشنگتن.

این خلاصه سخنرانی من است, تحت عنوان "با استفاده از بستر های نرم افزاری شیرپوینت به ساخت برنامه های کاربردی کسب و کار های عمودی":

"افقی?"" عمودی?"چه این کلمات را در یک زمینه شیرپوینت متوسط? شیرپوینت, همانطور که ما اغلب این مطلب را می شنوم که, "پلت فرم" برای برنامه های کاربردی ساختمان. این واقعیت این است که اغلب ما از به اصطلاح ویژگی های پلت فرم افقی از دست داده, مانند مدیریت اسناد و جستجو, are so easy and useful in and of themselves. اما, شیرپوینت است حتی قوی تر و ارزش بیشتری استفاده می شود که برای ایجاد برنامه های کاربردی عمودی طراحی شده برای دیدار روز کسب و کار خود را به نیاز روز بازگشت. در این جلسه توضیح می دهد که چگونه به جمع آوری ویژگی های پلت فرم به یک راه حل verticalized با استفاده از یک مثال کسب و کار واقعی جهان - خرید و فروش اعلان فرآیند مدیریت و دروازه مشتری. هدف گوینده است برای باز کردن چشم خود را به امکانات از پلت فرم شیرپوینت و به اهرم ویژگی های افقی پلت فرم خود را به ایجاد راه حل های کسب و کار تخصصی برای سازمان عمودی خود را.

در صورتی که موضوع قایق خود را شناور نیست, there are a bunch of other good topics. And DC is a great venue in and of itself to visit.

ثبت نام باز می شود این پنج شنبه, 04/16. Keep on top of the site and grab a seat before it’s too late 🙂

</پایان>

مشترک شدن در وبلاگ من.

من در توییتر در http://www.twitter.com/pagalvin

کانادا دقیقه

این زمان در هفته گذشته, من در مونترال بود, حضور به شدت توصیه می شود نشست شیرپوینت 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, اما من می دانم که به اندازه کافی برای دادن آموزش در مورد این موضوع. (خوشبختانه, جف Schaller از اهداف نرم افزار در استرالیا, در میان چند نفر دیگر, در میان جمعیت بود برای پاسخ به برخی از سوالات عمیق تر [من نمی دانم آنچه را که آنها در آب به پایین وجود دارد قرار داده است, اما ما نیاز به برخی از آن را در اینجا در ایالات متحده]).

اما, 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 و 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.

سرانجام, 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 دقیقه. And I don’t even know how many minutes that is in Canadian.”

همه خندید و به عنوان یک نتیجه, Montreal is officially on my Good Places list 🙂

حتی اگر آنها در شوخی من خندید, I would love Montreal. I try very hard to be open minded and not take my cues from پارک جنوبی, اما اعتراف میکنم, به غم وغصه من, that I had no idea how great is the metropolis of Montreal. I can’t wait to go back in a few months, هنگامی که آن را کمی گرم تر, برای دیدار دوباره.

در یک نوع از توجه داشته باشید مرتبط, من همچنین از طریق نشست اریک Swenson اولین سخنرانی عمومی با عنوان "IA و نام تجاری فرآیند: اسکچ Wireframes به سلام طراحی و وفاداری است. " (اریک همکاران EMC من است). Check out the abstract here: http://www.sharepointsummit2009.com/conference_day2.htm. من حتی آن را برای او ثبت. 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 🙂

</پایان>

مشترک شدن در وبلاگ من.

من در توییتر در http://www.twitter.com/pagalvin