Imo linea: Si vis proprio uti profile in regula partum Audientiis, proprium esse manifestum "omnes."

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 hoc, audientibus res nominatur "SITECD" et per conventionem, a recondit 3 moribus conueniebat. Quem definitum audientibus et plerumque dicitur, quod si "SITECD pares 'ABG", tunc comprehendunt quod Minutiae in auditorium.

Posuit et valorem unius user Quantcast cum compilavit in auditorium, but MOSS simply wouldn’t add that user. I noticed that the privacy setting for that profile was set to “me only” (maxime forma restrictiva) 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, MUSCUS Explained: Indicio immensi artifex demerguntur in Microsoft Muneris SharePoint Server 2007, et operui in hoc ipsum scripsi capitulo :). I would have thought that every word I wrote in that chapter would be seared into my memory.

Matt Morse scribit in hac specie pulchrum atque hic sum referenced in capitulo: http://blogs.pointbridge.com/Blogs/morse_matt/Pages/Post.aspx?_ID=50

</finem>Scribet ad mea blog.

Sequi me in Twitter ad 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 (e.g. iView web part). 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, the user won’t have to enter their ID when they hit up that system.

That part worked well for me. Autem, it begs the question, “how does the user change that user id or password?” The user might have made a mistake, or maybe you’re doing some testing in a dev environment and need to quickly switch between accounts.

I don’t know the answer to that, but I do know that you can go into Central Administration and manage the user’s credentials:

Central Administration –> Operations –> Manage Single Sign-On –> Manage Account Information for an Enterprise Application Definition

From there, you can specify the external application (e.g. SUBRUO) and the account you want to delete. You can also change the mapping.

If you know how to allow end users to directly change their credentials, kindly post a comment 🙂

</finem>

Scribet ad mea blog.

Sequi me in Twitter ad 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 creavit ipsa princeps qualitas chartam albam DE EODEM.

Primum autem obstaculum superare habui erat - Ubi textus partem iView? Propter aliquam causam,, prima cogitatio mea esset quod debuit download is a site alicubi, perhaps SAP’s site. Habui 1/2 convinced myself that iView web parts might even cost extra. Utique, eae musco (Puto Enterprise; Quoquo hinc usura id quod sum). 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.

Ego usura est textus huius partis et custodivit molestus nuntius questus:

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

Dicit paper album plane sit aspernatur in configuration file sita file "<Coegi tabellae:>\Program Files\Microsoft Office Servers\12.0\Config\TrustedSAPHosts.config”. The first dozen times I looked at that, Vidi cuncta erat "Elit Lima ... Config" et ego statim perrexerunt ad 12 alveare. 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, Est autem alia ratio, quod unum diem.

Imo linea:

1. iView telam partes eae ex arca archa cum SharePoint (Inceptum probabiliter).

2. Magicae configuration file, "TrustedSAPHosts.config", non habitabunt in 12 alveare.

</finem>

Scribet ad mea blog.

Sequi me in Twitter ad http://www.twitter.com/pagalvin

Nocte, 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, maxime cum causa accedere ad id quod superius dextera, usque guttulæ, bene, 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, suus rationabiliter vivos, but even that feels slow. Normally, 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 days ago(!). I disconnect and that that solves my performance problem.

</finem>

Scribet ad mea blog.

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.

It’s a good practice, probably even a Best Practice, to review your search reports once a month and look for opportunities to add best bets, 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’ 🙂

</finem>

Scribet ad mea blog.

In New Jersey SharePoint User Group occurrentes nocte, Microsoft Sr. Product artifex DuWayne Harrison obtulisset Microsoft Data Protection Procurator 2007. DuWayne was great (data in auxilium, et nomina audit ex una et altera urna non recolo). Vos can adepto praesentationis materias hie.

Usque nocte, Ego numquam de DPM.

Im 'non a persona ratio typus admin, so I’m writing this from SharePoint consultant’s perspective and may get some of the words wrong. Mihi, DPM is a backup/restore solution for Microsoft "stuff":

• Files
• SQL
• O / S
• Rectum apparatus (vivo tergum de VM, etsi ipsa VM cursor Unix).
• Peperit metalli recuperare (i.e. EXITIALIS hardware elit).

Ultra quod effercio, which I would consider to be minimal requirements for any kind of "real" tergum / restituo Product, DPM also has built-in intelligence for SharePoint. It understands about server farms and lets you restore:

• Totam databases (e.g. content, config, etc).
• Collectiones Site
• Singula loca
• Singulis (e.g. documenta).

The actual restore process involves extracting the target data from the backup and save it into a "restore farm" atque inde, movens ad producendum environment (sive ubicumque uolueris restituet). 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 (maxime in physicis topology) sed indiget ut compositus secundum Templates, versions, etc.

Consummationem non vidi finem amet, but DuWayne did show screen shots and some live demos. It seems to be as good as it needs to be, Nulla at mediocri.

I was particularly struck by the pricing. Obviously, ne me ad hanc, Aliquam sed orci magna est dure, ut opinor, (in USD):

• $600 pro se DPM.
• Hardware pro servo DPM (et media et omnia vasa socius).
• $450 Singulis server vos volo ut tergum sursum ("enterprise" licenciam).

A quinque server villam esset constant ad summum:

• $600 nam DPM
• $450 x 5 servientes = $2,250

Totalis sumptus in dissentiet: $2,850

In praxi, it would be less. You wouldn’t necessarily need to have DPM installed on each web front end, enim. 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 die genere praesto, si opus sit, non apparet alicui, quod accipere.

Omnia in omnibus, Puto suus dignum certe quaerimus, si vestri 'vultus pro notitia sicco illic præsidium solutionem SharePoint.

</finem>

Scribet ad mea blog.

Aliquam: http://twitter.com/pagalvin