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

I’ve been working with SharePoint SSO and learning as I go. One way in which this works is that you tell SharePoint about external applications. Users log into that application via some SharePoint function (bijv. iView web deel). The first time the user performs this action, it prompts them for the correct user id and password to use for that system. It’s setting up a mapping between your SharePoint credentials and your credentials for that backend system. Thereafter, Die gebruiker sal nie hul ID te tree wanneer hulle getref het dat die stelsel.

That part worked well for me. Egter, Dit lei tot die vraag, "Hoe die gebruiker verander wat 'n gebruiker id of wagwoord?” The user might have made a mistake, Of miskien het jy besig met 'n toets in 'n dev omgewing en die behoefte om vinnig te skakel tussen rekeninge.

Ek weet nie die antwoord op daardie, maar ek weet dat jy kan gaan in die Sentrale Administrasie en die bestuur van die gebruiker se geloofsbriewe:

Sentrale Administrasie -> Bedrywighede -> Bestuur Single Sign-On -> Bestuur rekening inligting vir 'n Enterprise Aansoek Definisie

Van daar, jy kan die eksterne program (bijv. SAP) and the account you want to delete. You can also change the mapping.

As jy weet hoe om die einde kliënte toelaat om direk verander hul geloofsbriewe, kindly post a comment 🙂

</einde>

Skryf in op my blog.

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

I needed to do some minimal proving today that iView web parts can work in my client’s environment. I’ve never worked with this slice of SharePoint before.

Microsoft het 'n baie hoë gehalte wit papier op hierdie onderwerp.

Die eerste hindernis het ek moes oorkom was - waar is die iView web deel? Vir een of ander rede, my first thought was that I’d have to download it from a site somewhere, perhaps SAP’s site. Ek moes 1/2 convinced myself that iView web parts might even cost extra. Natuurlik, they are included with MOSS (I think Enterprise; that’s what I’m using here in any event). I’ve seen the standard “add a web part” dialog box hundreds or more times and always glossed over it. No more!

The next obstacle is that I can’t read instructions.

I was using the web part and kept getting this annoying message:

No SAP servers are configured for this site. Contact your administrator to configure trusted SAP servers.

The white paper clearly says to edit a configuration file located at file “<Drive Letter:>\Program Files\Microsoft Office Servers\12.0\Config\TrustedSAPHosts.config”. The first dozen times I looked at that, all I saw was “Program Files…Config” and I went straight away to the 12 Hive. Once I finally slowed down to read it, I realized my mistake and it was easy to fix.

I continued on my merry way with SSO configuration. It’s not all at clear to me if that worked, but that’s another story for another day.

Bottom line:

1. iView web parts are included out of the box with SharePoint (probably Enterprise).

2. The magic configuration file, “TrustedSAPHosts.config”, does not live in the 12 Hive.

</einde>

Skryf in op my blog.

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

Vanaand, I’m doing some hobby work with a virtual machine running on my desktop. I’m connecting via IE on my laptop and I’m noticing horrible performance. IE keeps freezing, veral wanneer ek toegang tot enige iets in die boonste regterkantste hoek wat jou sal lei tot 'n drop-down te, goed, drop down. I would click on Site Actions and things freeze up for a while. They would freeze long enough for me to switch over to another browser window and do something else. If I confine myself to navigating around from page to page, dit is redelik vinnig, but even that feels slow. Gewoonlik, things are very fast.

I’ve had this happen to me before and I think that I ended up rebooting at the time. I’m about to do that when I somehow notice I’m still VPN’d to a client from 2 dae gelede(!). I disconnect and that that solves my performance problem.

</einde>

Skryf in op my blog.

Ons het gewerk in 'n gebruiker aanvaarding toets (UAT) omgewing wat, in vergelyking tot die ontwikkeling, is dood stadig.

Dit is 'n ingewikkelde omgewing met behulp van FBA, SQL 2008, SSRS en uitgebreide web programme oor die internet toeganklik met https, so dit is moeilik om die probleem op te spoor.

Vir 'n vorige kliënt, ons gebruik FBA met 'n LDAP rol verskaffer (en lidmaatskap verskaffer). One of my colleagues, baie meer slim as wat ek, determined that the "out of the box" LDAP rol verskaffer, wanneer dit gebruik word in daardie omgewing, wasn’t scaling well. To solve this problem for that client, he implemented a nice caching scheme in a custom role provider.

Hierdie situasie was soortgelyk, so we looked into replicating that solution to the today’s client. As I was debugging that, Ek het opgemerk dat hierdie boodskap gereeld sal binnekort in die stelsel log (van Event Viewer):

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

Ek het dit beteken dat die jeug swembad dusver was herwinning, veels te dikwels en dit sou verduidelik 'n prestasie probleem.

I looked at the app pool’s properties and its "Recycling" page showed that the property "Maximum virtual memory (in megagrepe)" 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" wat gaan daar aan, maar dit is duidelik 'n soort van oorsaak / gevolg ding gebeur en vir nou, die UAT omgewing bruikbaar.

</einde>

Skryf in op my blog.

Dit is 'n goeie praktyk, waarskynlik selfs 'n Beste Praktyk, te hersien om jou soektog is een keer oor 'n maand en kyk vir geleenthede om die beste verbintenis te voeg, tune your thesaurus and maybe even uncover some business intelligence that is otherwise hidden to management.

It’s already the 3rd of the month. Time’s awastin’ 🙂

</einde>

Skryf in op my blog.

By die New Jersey SharePoint User Group vergadering verlede nag, Microsoft Sr. produk spesialis DuWayne Harrison aangebied Microsoft Data Protection Bestuurder 2007. DuWayne was great (en hy is deur een of twee kollegas van die publiek wie se name ek kan nie onthou). Jy kan die aanbieding materiaal hier.

Tot gisteraand, Ek het nog nooit gehoor van DPM.

Ek is nie 'n stelsel administrateur tipe persoon, so I’m writing this from SharePoint consultant’s perspective and may get some of the words wrong. Vir my, DPM is a backup/restore solution for Microsoft "stuff":

• Lêers
• SQL
• O / S
• Virtuele masjiene (leef rugsteun van die VM, selfs al is die VM self loop Unix).
• Kaal metaal herstel (d.w.z. katastrofiese hardeware mislukking).

Behalwe dat dinge, which I would consider to be minimal requirements for any kind of "real" Friends / herstel produk, DPM also has built-in intelligence for SharePoint. It understands about server farms and lets you restore:

• Hele databasis (bijv. inhoud, config, ens.).
• Webwerf versamelings
• Individuele webwerwe
• Individuele items (bijv. dokumente).

The actual restore process involves extracting the target data from the backup and save it into a "restore farm" en dan van daar af, beweeg dit na die produksie-omgewing (of waar jy wil om te herstel). I think this is seamless, but there was a lot of emphasis on the need for a "restore farm". The restore farm does not need to match the production environment in every particular (hoofsaaklik in die fisiese topologie) maar nie nodig aan te pas in terme van templates, weergawes, ens..

Ek het nie 'n einde demo te beëindig, but DuWayne did show screen shots and some live demos. It seems to be as good as it needs to be, ten minste vir 'n matige grootte omgewing.

I was particularly struck by the pricing. Obviously, hou my nie op hierdie, maar ek glo dat die duurste prys is ongeveer soos volg (in dollar):

• $600 vir DPM self.
• Hardeware vir 'n DPM bediener (en verwante dinge vir die media en alles wat).
• $450 vir elke bediener wat jy wil om te back-up ("enterprise" lisensie).

'N vyf-bediener plaas sou kos by die meeste:

• $600 vir DPM
• $450 x 5 bedieners = $2,250

Totale koste in lisensies: $2,850

In die praktyk, it would be less. You wouldn’t necessarily need to have DPM installed on each web front end, byvoorbeeld. You don’t necessarily need enterprise licenses either.

The user interface is seems very simple probably would not require any special training to get up to speed. I did ask about that specifically and there is apparently a 1.5 dag klas beskikbaar, maar dit is nie vir my duidelik dat iemand regtig nodig sou wees om dit te neem.

All in all, Ek dink dit is beslis die moeite werd om te ondersoek as jy daar buite op soek na 'n data beskerming oplossing vir SharePoint.

</einde>

Skryf in op my blog.

Twitter: http://twitter.com/pagalvin