Bottom line: jekk inti tixtieq li tuża proprjetà profil f'regola għall-ħolqien udjenzi, il-propjetà għandha tkun viżibbli għal "kulħadd."

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. F'dan il-każ, l-proprjetà udjenza huwa msemmi "SITECD" u permezz tal-konvenzjoni, ħwienet 3 Kodiċi karattru. Huwa kien iddefinixxa l-udjenza u regola li qal li jekk "SITECD ugwali" ABG "", mbagħad jinkludi li l-profil utent fl-udjenza.

Huwa twaqqaf profil utent wieħed ma 'dak il-valur u kkompilata l-udjenza, but MOSS simply wouldn’t add that user. I noticed that the privacy setting for that profile was set to “me only” (l-aktar forma restrittivi) 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

</aħħar>Abbona għall-blog tiegħi.

Follow lili Twitter fi 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. parti web iView). 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, l-utent mhux se jkollhom jidħlu ID tagħhom meta hit up dik is-sistema.

That part worked well for me. Madankollu, dan iqajjem il-kwistjoni, "Kif ma l-utent bidla li id ​​l-utent jew il-password?” The user might have made a mistake, jew forsi inti qed tagħmel xi testijiet f'ambjent DEV u jeħtieġ li jaqilbu malajr bejn il-kontijiet.

I do not know-risposta għal din, imma jien taf li inti tista 'tmur fil Amministrazzjoni Ċentrali u jamministraw kredenzjali tal-utent:

Ċentrali Amministrazzjoni -> Operazzjonijiet -> Manage Uniku Sign-On -> Manage Kont Informazzjoni għal applikazzjoni Definizzjoni Intrapriża

Minn hemm, inti tista 'tispeċifika l-applikazzjoni esterna (e.g. SAP) and the account you want to delete. You can also change the mapping.

Jekk inti taf kif jippermettu lill-utenti finali biex jinbidlu direttament kredenzjali tagħhom, kindly post a comment 🙂

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi 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 ħolqot karta bajda kwalità għolja ħafna fuq dan is-suġġett.

L-ewwel ostaklu kelli biex jingħelbu kien - fejn hija l-parti web iView? Għal xi raġuni, ewwel ħsieb tiegħi kienet li I d jkollhom li tniżżel minn sit x'imkien, perhaps SAP’s site. Kelli 1/2 convinced myself that iView web parts might even cost extra. Of course, huma inklużi ma MOSS (I think Enterprise; dan huwa dak li jien jużaw hawn fi kwalunkwe każ). 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 kienet qed tuża l-parti web u miżmuma jkollna dan il-messaġġ annoying:

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

Il-white paper jgħid b'mod ċar li jeditjaw fajl konfigurazzjoni li jinsabu fil-fajl "<Drive Ittra:>\Program Files\Microsoft Office Servers\12.0\Config\TrustedSAPHosts.config”. The first dozen times I looked at that, kollha rajt kien "Program Files ... konfigurazzjoni" u I marru minnufih lill- 12 doqqajs. 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, iżda li storja oħra għal jum ieħor.

Bottom line:

1. web partijiet iView huma inklużi barra mill-kaxxa ma SharePoint (probabbilment Enterprise).

2. Il-fajl konfigurazzjoni magic, "TrustedSAPHosts.config", ma jgħix fil- 12 doqqajs.

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Tonight, 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, speċjalment meta I aċċess xejn fir-rokna ta 'fuq tal-lemin li jikkawża drop-down biex, ukoll, 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, huwa raġonevolment malajr, but even that feels slow. Normalment, 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 jiem ilu(!). I disconnect and that that solves my performance problem.

</aħħar>

Abbona għall-blog tiegħi.

Imxejna ilhom jaħdmu fil-ittestjar ta 'aċċettazzjoni utent (UAT) ambjent li, meta mqabbla ma 'l-iżvilupp, hija mejta bil-mod.

Huwa ambjent kkumplikata tuża FBA, SQL 2008, SSRS u l-applikazzjonijiet estiżi web aċċessibbli fuq l-internet li jużaw https, hekk huwa kien diffiċli li jillokalizzaw l-kwistjoni.

Għal klijent preċedenti, aħna użati FBA ma 'fornitur rwol LDAP (u l-fornitur sħubija). One of my colleagues, ferm aktar għaqlija minn I, determined that the "out of the box" Fornitur rwol LDAP, meta jintuża f'dak l-ambjent, wasn’t scaling well. To solve this problem for that client, he implemented a nice caching scheme in a custom role provider.

Din is-sitwazzjoni dehret simili, so we looked into replicating that solution to the today’s client. As I was debugging that, I ndunat li dan il-messaġġ se spiss jidhru fil-log Sistema (minn Viewer Avveniment):

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

I ħa dan ifisser li l-pool app ġie riċiklaġġ ferm, wisq spiss u li jispjega l-problema prestazzjoni.

I looked at the app pool’s properties and its "Recycling" page showed that the property "Maximum virtual memory (fil 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" li għaddej hemmhekk, iżda b'mod ċar xi tip ta 'kawża / effett ħaġa jiġri u għal issa, l-ambjent UAT tkun tista 'tintuża.

</aħħar>

Abbona għall-blog tiegħi.

Huwa prattika tajba, probabbilment anki l-aħjar prattika, biex tirrevedi tfittxija tiegħek rapporti darba fix-xahar u tfittex opportunitajiet biex iżżid imħatri aħjar, 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’ 🙂

</aħħar>

Abbona għall-blog tiegħi.

Fil- New Jersey SharePoint User Group laqgħa aħħar lejl, Microsoft Sr. speċjalista prodott DuWayne Harrison ippreżentat Microsoft Manager Protezzjoni tad-Data 2007. DuWayne was great (u kien appoġġjat minn wieħed jew żewġ kollegi mill-udjenza li l-ismijiet I ma recall). Tista 'tikseb l-materjali preżentazzjoni hawn.

Sa l-aħħar bil-lejl, I qatt ma semgħu DPM.

Jien ma sistema persuna tip admin, so I’m writing this from SharePoint consultant’s perspective and may get some of the words wrong. Lili, DPM is a backup/restore solution for Microsoft "stuff":

• Fajls
• SQL
• O / S
• Magni virtwali (backup tal-VM jgħixu, anki jekk il-VM innifsu qed taħdem Unix).
• Rkupru ta 'metall Bare (I.E. ħsara fil-hardware katastrofiku).

Lil hinn minn dan Jittieħed, which I would consider to be minimal requirements for any kind of "real" backup / jirrestawraw prodott, DPM also has built-in intelligence for SharePoint. It understands about server farms and lets you restore:

• Databases Kollu (e.g. kontenut, konfigurazzjoni, eċċ).
• Kollezzjonijiet sit
• Siti individwali
• Oġġetti individwali (e.g. dokumenti).

The actual restore process involves extracting the target data from the backup and save it into a "restore farm" u mbagħad minn hemm, jmexxuh għall-ambjent tal-produzzjoni (jew fejn inti tixtieq li terġa). 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 (prinċipalment fil-topoloġija fiżiku) iżda ma bżonn li jaqblu f'termini ta 'mudelli, Verżjonijiet, eċċ.

I ma tara tmiem sħiħa li tintemm demo, but DuWayne did show screen shots and some live demos. It seems to be as good as it needs to be, inqas għal ambjent daqs moderat.

I was particularly struck by the pricing. Obviously, ma jżommux me dan, imma nemmen li l-prezzijiet l-aktar għali hija bejn wieħed u ieħor kif ġej (f'USD):

• $600 għall DPM innifsu.
• Hardware għal server DPM (u l-għalf assoċjati għall-midja u dak kollu li).
• $450 għal kull server li inti tixtieq li back up ("enterprise" liċenzja).

A farm server ħamsa tiswa aktar:

• $600 għall DPM
• $450 x 5 servers = $2,250

Spiża totali fil-liċenzji: $2,850

Fil-prattika, it would be less. You wouldn’t necessarily need to have DPM installed on each web front end, per eżempju. 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 klassi jum disponibbli, għalkemm mhuwiex ovvju għalija li xi ħadd se verament bżonn li teħodha.

Kollox ma 'kollox, Naħseb li huwa ċertament min investigazzjoni jekk int hemmhekk tfittex għal soluzzjoni għall-protezzjoni tad-data SharePoint.

</aħħar>

Abbona għall-blog tiegħi.

Twitter: http://twitter.com/pagalvin