Adepto te ad SharePoint User Group!

In duo septimanas, Ego ministrabant in New Jersey SharePoint user coetus et novo novos Eboracensis SharePoint Tincidunt user coetus (Morbi convallis felis SharePoint magis contra instituta).

In New Jersey, the good people of NewsGator presented their product and covered a lot of very interesting social computing concepts. If you’re looking to incorporate social computing into your organization in a system-assisted way and can’t get out-of-the-box SharePoint to do it for you, graviter reprehendo ex NewsGator. It’s very good stuff. A lot of great social computing functionality and (in a demo environment saltem) bene factum.

I’m personally convinced that companies that begin to adopt social computing attitudes and systems will outperform those that do not. It’s too useful to ignore or, ad hoc puto, to even delay. It can make a tremendous difference in day-to-day operations if done correctly. I’ll write some more about this later.

In New York nocte, the NY SharePoint Developers group kicked off its inaugural meeting at the MSFT office on 52nd and 6th. John Bender presented on how to create a custom stsadm extension. I’ve read about it, sed videntes "vivere" clarifies things. It’s much easier than I realized. No need for features/solutions, just an XML file and a DLL. He walked through a process for recursively finding and displaying security settings for sites and lists in a site collection. He took it farther to describe how this could be part of an auditing process. This group focuses purely on development and so doesn’t come into conflict with larger more established SharePoint user group which is frequently talking at a higher level.

Sunt coetus omnes trans mundi. Check them out.

</finem>

Scribet ad mea blog.

Technorati Tags:

Emailing Cotidie Negotium recordationes // Looping in SharePoint amet Workflow

I wrote up a detailed article a few weeks ago describing how to create a SharePoint Designer workflow that sends a task reminder email on a daily basis. It’s been edidit in novum SharePoint Latin site. More generally, articulum ostendit quam creare a looping structura in SPD.

In emporium habet a varietate articulos possidet, inter alia, ipsa technica effercio, interviews and industry news. I recommend you add it to your RSS feed.

Si opus ministerii vel vendere, I’d also consider advertising on the site. It’s off to a strong start with several thousand pairs of eyes looking at it already. That’s sure to grow.

Denique, si iam prurigo scribere aliquid et posside eam in fronte maioris audientibus, this is a great time and place to scratch it.

</finem>

Scribet ad mea blog.

Technorati Tags:

SharePoint Optimus Actiones conferentia

Ego dicendi in SharePoint Optimus Actiones colloquium in November.

It’s sort of a funny story. I was in Virginia presenting at the SUGDC colloquium and that Friday was the deadline to submit speaking proposals for the BP conference. The organizers described how they would use a "blind selection" Expositio et ratio eligendi operam fieret ex pretio, etc. To maximize my chances of getting selected, I submitted two proposals. The selection committee picked both.

Collega (Natalya Voskresenskaya) and I will discuss a real-world governance model that we and our client put together for a substantial SharePoint rollout project last summer. The objective here is to describe the details of the governance plan and why we believe it represents best practices in the context of Sharepoint, Regimen et similis turmas.

Secundo, I will present a process for obtaining great business requirements from End Users. This goes back to one of my very early blog posts, indecenter titulus "MUSCUS: Efficax introductio ad Organizatio".

Colloquium ipsum et plenum magnis INSANE videtur esse altus suadeo discerpens te a a opus tribus diebus, iunctura in in haec visa et networking cum tam colloquium attendees et loquentium. It will be time and money well spent.

Hope to see you there 🙂

</finem>

Scribet ad mea blog.

Technorati Tags:

Mea Latest “In Defensio SharePoint amet” Articulus est Available

Marcam Miller super ad Finem User SharePoint has posted my latest article about using SharePoint Designer to create great workflow solutions up on his site. Reprehendo eam.

In hoc articulo, Ego loqui de consilio processus et, in maior detail, quam ad posuit certa et iterabilem test processus usura SharePoint features (consuetudinem tabulatum, site templates). The article targets End Users, sed accessus bonum tincidunt quoque.

</finem>

Scribet ad mea blog.

Quomodo Narra tua SharePoint Job?

Hoc fit quoties vobis? I’m sitting at my laptop, lectio blogs, respondens ad forum Postings, 2 exemplaria visivae Studio aperta et VPN'd ad aliud cultor cum sua visivae Studio + 15 pasco fenestras (a typicam die) et aliquis nomine Samantha (uxorem, videtur) refert me, "Sumus esse ibi in 30 minutes. Get dressed."

Mihi in a OBSTUPEFACIO, errare circa domum confuse, currum proxime accedere scio, Phasellus at dolor a parte dextra dicitur in me, "Ergo, quid faciam vivere?"

Haec colloquia numquam bene.

Me: "Ahh … Sum solutiones artifex EMC."

Innominatam persona: blank obtutuque

Me: "Ego operari cum productum dicitur SharePoint … suus a Microsoft."

NP: "Euge! Ego audivit quod comitatu! What is SharePoint?"

Me: "Umm … facit cooperatio … populi ad participes notitia … Suus suggestum enim aedificium negotiis sol…"

NP: Oculos linitionem.

Me: "Sum programmator."

NP: "Euge! I know people in my company that do programming! When I was in high school, Ego lusit circa cum SUMMUS."

Et pars super sermone, nos ad aliquid facilius loqui de, sicut politica.

Quis cura ad describere quomodo tractare hoc?

</finem>

Scribet ad mea blog.

Technorati Tags:

Latentes Consuetudo Actiones in SharePoint

Plures menses, dum operantes in consilium enim a client, I created a feature. Among other things, quod pluma definitur consuetudo actio (apparent sub site occasus). The only purpose for this custom action was to demonstrate to me that the feature activation was working as expected. Basically, Ego usus ut a rudis forma debugging.

Multo ad mea confusioni, hoc debugging artificium fecit a Dev ad UAT et ad productionem ante aliquis obtinuit circa ad petens, "Quid est hoc xyzzy pagina?"

Iam, Nulla sit amet enim et nolle uninstall pluma, fix elements.xml and then reinstall.

Todd Bleaker pointed out an easy way to handle it. In his words:

"CustomActions sunt non transtulerunt in database, leguntur directe a Elements.xml file et transtulerunt in application statu ad runtime. Ita, non opus ad deactivate, uninstall, restituo, et Nulla Feature ad tollere CustomAction. Iustus auferre a Elements.xml file et redivivus applicationem stagnum(s) efficitur. Nunc dicendum est in sequenti tempore, non videre CustomAction ultra."

Secutus mandatis et, utique, operantur.

In meam, this is a department level installation with just a single WFE. If you find yourself with this problem in future and with multiple WFE’s, Credo in singulis habebis transferre.

</finem>

Scribet ad mea blog.

Technorati Tags: ,

Configurare Thesaurus in MUSCUS

Ego operantes in architectura review document hoc septimana et insinuat, inter alia, that the client consider using the thesaurus to help improve the end user search experience. Having never done this myself, I wanted to do a quick hands-on test so that my suggestion is authentic.

Erat mirabiliter difficile ad instar quam ad, quamvis est, in facto, quite easy. There’s a pretty good bit of information on the thesaurus (reprehendo hic et hic, enim). Autem, illis Docs sunt aut WSS 2.0 / SPS 2003 oriented or they don’t actually spell out what do to after you’ve made your changes in the thesaurus. They provide a great overview and fair bit of detail, sed suus non satis ad transire consummatione linea.

Gradibus operati me:

  1. Make the changes to the thesaurus. (Infra pro momenti note)
  2. Ad cultor et sileo in "Officium SharePoint Server Lorem" servitium.

A summitatem proni ad Mr. J. D. Wade (bio). He provided the key bit about restarting the search service and rescued me from endless, time consuming and unnecessary iisresets and full index crawls. This episode probat, iterum, quod Twitter is the awesome. (Sequi me in egestas hic. I follow any SharePoint person that follows me).

I don’t know if this functionality is available in WSS. If it is or is not, placere relinquat comment vel email me et ego update hoc post.

Maximus note: There’s conflicting information on which XML thesaurus file to change. There’s this notion of "tsneu.xml" ut in "neutra" Thesaurus. I wasted some time working with that one. In meam, Ego opus mutare "tsenu.xml" lima sita sub folder de App ID se: \\win2003srv c $ elit Files Microsoft Officium Servers 12,0 Data Officium Server Applications 3c4d509a-75c5-481c-8bfd-099a89554e17\Config. I assume that in a multi-farm situation, te hoc mutatio ubique query server currit.

</finem>

Scribet ad mea blog.

Technorati Tags: , ,

Vestibulum nec urna magna-scala MUSCUS: 50k diurno, 10 Decies totalis

Praeterita septimana, quis interroganti de creando a pulchellus altum volumen SharePoint environment quod prorsus tractandi novum documenta (10,000 +/- hoc in casu). I don’t know much about this, sed gratias ad hoc chartam albam, Sentio melius informati.

Enim me, haec charta alba fere iustum librum Marcus momento, but I did start reading through it and thought I’d highlight my main take-away. SharePoint can be scaled to handle, minimum, hoc onere:

  • 50k novum documenta diurno.
  • 10 decies totalis documenta.

I write the 50k/10MM figures because they are easy enough to remember. As long as you know they are minimums, you won’t get into trouble. The maximums are at least 10 percent superior quam et summa tuning, nequaquam multus altior.

Gratias, Mike Walsh, iterum eius septimanis WSS FAQ updates et correctionibus stipes. If you’re not subscribed to it, ut serio cogitare de faciendo.

</finem>

Scribet ad mea blog.

Perficientur SharePoint — Velox (Sed inusitata) Tip

Weve 'been opus in a user acceptationem testing (UAT) quod environment, prout comparatur ad progressum, mortuus est tarda.

Suus turpis elit using FBA, SQL 2008, SSRS telam et extensa super Penitus applications pervia usura https, Quaestio est igitur dura inuestigandum.

Nam priore client, usi sumus FBA cum LDAP partes provisor (et sociari provisor). One of my colleagues, multo magis quam callidus, determined that the "out of the box" LDAP partes provisor, cum dicitur quod environment, wasn’t scaling well. To solve this problem for that client, he implemented a nice caching scheme in a custom role provider.

Hoc simile videbatur, so we looked into replicating that solution to the today’s client. As I was debugging that, Animadverti quod hoc nuntio frequenter apparent Ratio stipes (a vicis Visum):

A worker process with process id of ‘XXX’ serving application pool ‘Home – 80’ has requested a recycle because it reached its virtual memory limit.

Ego tulit hoc intelligitur quod usque app est piscina redivivus, et id explicare nimis saepe effectus problema.

I looked at the app pool’s properties and its "Recycling" page showed that the property "Maximum virtual memory (in megabytes)" had been set to true and had been set to 5000. That seems like enough, but I decided to unset the value and that had an immediate positive effect. No more app pool recycling. No more mysterious slow-downs and pauses.

I don’t really understand the underlying "stuff" quod agitur ibi, sed manifeste aliquid genus causae / effectus rei iam aguntur et pro, in environment UAT est utilis.

</finem>

Scribet ad mea blog.

Technorati Tags:

Fairfield / WestChester SharePoint User Group in Iunctio

My colleague (Natalya Voskresenskaya) and I will be speaking at the Fairfield/Westchester SharePoint User Group meeting at 6:00 In PM 07/16 (Wednesday). We are talking about the content query web part. This is the same (sed melius quod habetur in Maio Lugduni dedit).

Register hic pre-: https://www.clicktoattend.com/invitation.aspx?code=129626&wa=wsignin1.0

Et utinam non videre Natalya!

Here’s the email Richard Martzelle just sent out on the subject:

Topic: Using Content Query Web Part to Create Business Solutions

Speakers: Paulus Galvin & Natalya Voskresenskaya

Date: July 16th Tempus suscipiat: (Eat & Network): 6:00PM Tempus: 6:30 PM -8:00PM

Meeting Description

MOSS 2007’s Content Query Web Part (CQWP) users possit creare consuetudinem sententiae a multis notitia queried, et nunc ipsum quod in uno. Quamquam hereditas eius potens query & contentus bene polito, CQWP saepius underrated et despiciens pluma. CQWP is both a "data extraction engine" (reperio usquam documentis vel album items in a collection site) et quoque in primo genere evidenter præsentationem tool quod users ad moderari contentus est quomodo sistuntur per HTML involvens et splendor format styles ut paene quolibet modo.

In hoc demo-grave sessionem, CQWP solvere dabunt operam uti eu Vestibulum facilisis mollis neque per ostentationem

• use default CWQP features, possidet Nisl id Aenean Curabitur tellus

• use CWQP as a reporting tool anywhere in a site collection via filter criteria such as "all documents created today"

• change look & sentio of negotium notitia query consequitur ad exaggerandam, notitia ostendere columnis adiectis, notitia ostendere eget format, aliique

• show how CQWP can aid in content type administration (i.e. invenietis omnia documenta particularis potentia ictum mutato content type ut intelligant a definitione CT)

• describe some limitations of CQWP

• provide a list of resources for advanced CQWP techniques, possidet blogs, ECQWP Codeplex project & Documenta MSDN

</finem>

Scribet ad mea blog.

Technorati Tags: