Bottom line: Ako želite koristiti profil imovine u pravilu za stvaranje publiku, Objekt mora biti vidljiv "svima."

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. U tom slučaju, Publika je imovina pod nazivom "SITECD", a prema konvenciji, pohranjuje 3 kod pojedinih znakova. On je definirao publiku i pravilo da je rekao da ako "SITECD jednak 'ABG'", zatim su tu korisnički profil u publici.

On je postavio jedan korisnički profil s tom vrijednosti, a sastavio je publiku, but MOSS simply wouldn’t add that user. I noticed that the privacy setting for that profile was set to “me only” (najstrožu oblik) 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 objasnio: Informacijskog Zaštitno Duboko Zaronite u Microsoft Office SharePoint Server 2007, i da sam pokrivena ovu točku u samom poglavlju sam pisao :). I would have thought that every word I wrote in that chapter would be seared into my memory.

Matt Morse piše ovo gore u prekrasnim detaljima i ovdje sam ga upućuje u poglavlju: http://blogs.pointbridge.com/Blogs/morse_matt/Pages/Post.aspx?_ID=50

</kraj>Pretplatite se na moj blog.

Slijedite me na Twitter-u 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-dio). 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, korisnik neće morati unijeti svoje osobne kad su hit taj sustav.

That part worked well for me. Međutim, što otvara pitanje, "Kako se korisnik promijeniti tu korisničko ime i zaporku?” The user might have made a mistake, ili možda radite neki testiranje u razvojnom okruženju i potrebu za brzo prebacivanje između računa.

Ne znam odgovor na to pitanje, ali znam da možete ići u središnjoj administraciji i upravljanje korisničke vjerodajnice:

Središnja uprava -> Operacije -> Upravljanje Single Sign-On -> Upravljanje podacima o računu za jedan Definicija Enterprise Application

Odatle, možete odrediti vanjsku primjenu (e.g. SAP) and the account you want to delete. You can also change the mapping.

Ako znate kako da krajnjim korisnicima izravno promijeniti svoje vjerodajnice, kindly post a comment 🙂

</kraj>

Pretplatite se na moj blog.

Slijedite me na Twitter-u 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 je stvorio vrlo kvalitetan bijeli papir na ovu temu.

Prva prepreka sam morao prevladati je - gdje je dio web IVIEW? Iz nekog razloga, Moja prva pomisao bila je da ću morati skinuti s web-negdje, perhaps SAP’s site. Morao sam 1/2 convinced myself that iView web parts might even cost extra. Naravno, oni su uključeni u MOSS (Mislim Enterprise; to je ono što sam koristeći ovdje u svakom slučaju). 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.

Ja je korištenjem web-dijela i držati uzimajući ovaj dosadne poruke:

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

Bijeli papir jasno kaže urediti konfiguracijske datoteke se nalazi u datoteci "<Vozite Pismo:>\Program Files\Microsoft Office Servers\12.0\Config\TrustedSAPHosts.config”. The first dozen times I looked at that, sve što sam vidjela bila je "Program Files ... Config" i otišao sam ravno do 12 košnica. 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, ali to je druga priča za neki drugi dan.

Bottom line:

1. IVIEW web dijelovi uključeni su iz kutije sa SharePoint (Vjerojatno Enterprise).

2. Čarolija konfiguracijske datoteke, "TrustedSAPHosts.config", ne živi u 12 košnica.

</kraj>

Pretplatite se na moj blog.

Slijedite me na Twitter-u http://www.twitter.com/pagalvin

Večeras, 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, pogotovo kad sam pristupiti ništa u gornjem desnom kutu da bi izazvati pad-dolje, dobro, 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, to je razumno brzo, but even that feels slow. Normalno, 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 dana(!). I disconnect and that that solves my performance problem.

</kraj>

Pretplatite se na moj blog.

Radili smo na testiranje korisnika prihvaćanje (UAT) okolina koja, u odnosu na razvoj, je mrtav spor.

To je komplicirano okruženje pomoću FBA, SQL 2008, SSR i proširene web aplikacija dostupnih preko interneta putem https, tako da je bilo teško pronaći pitanje.

Za prethodni klijent, koristili smo FBA s LDAP uloga davatelja (i članstvo usluga). One of my colleagues, daleko pametniji od mene, determined that the "out of the box" LDAP Uloga usluga, kada se koristi u tom okruženju, wasn’t scaling well. To solve this problem for that client, he implemented a nice caching scheme in a custom role provider.

Ova situacija se činilo slično, so we looked into replicating that solution to the today’s client. As I was debugging that, Primijetio sam da je ova poruka često će se pojaviti u sustavu zapisnik (iz 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.

Uzeo sam to znači da app bazen je recikliranje sada, daleko previše često, a to bi objasnilo problem performansi.

I looked at the app pool’s properties and its "Recycling" page showed that the property "Maximum virtual memory (u megabajta)" 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" da se tamo događa, ali jasno nekakav uzrok / učinak stvar se događa, a za sada, UAT okoliš je korisna.

</kraj>

Pretplatite se na moj blog.

To je dobra praksa, vjerojatno čak i najbolje prakse, pregledati vaše pretraživanje izvještava jednom mjesečno i tražiti mogućnosti za dodavanje najbolje oklade, 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’ 🙂

</kraj>

Pretplatite se na moj blog.

Na New Jersey SharePoint User Group ispunjavanju sinoć, Microsoft Sr. proizvod specijalist DuWayne Harrison prikazani Microsoft Data Protection Manager 2007. DuWayne was great (i bio je podržan od strane jednog ili dva kolegama iz publike čija imena ne sjećam). Možete dobiti materijale za prezentaciju ovdje.

Do sinoć, Nikad nisam čuo za DPM.

Nisam sustav admin Vrsta osoba, so I’m writing this from SharePoint consultant’s perspective and may get some of the words wrong. To me, DPM je backup / vraćanje rješenje za Microsoft "stvari":

• Datoteke
• SQL
• O / S
• Virtualni strojevi (živjeti backup VM, čak i ako VM sama Unix).
• Bare metal oporavak (i.e. katastrofalna hardver neuspjeh).

Iza te stvari, što bih uzeti u obzir da se minimalni zahtjevi za bilo kakav "pravi" backup / vratiti proizvod, DPM also has built-in intelligence for SharePoint. It understands about server farms and lets you restore:

• Čitave baze podataka (e.g. sadržaj, config, itd.).
• Site zbirke
• Pojedinačne stranice
• Pojedinačne stavke (e.g. dokumenti).

Stvarni vratiti proces uključuje vađenje ciljane podatke iz backup i spremite ga u "vraćanja farmi" i onda od tamo, premještanja u proizvodnji okoliš (ili gdje god želite vratiti). 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 (uglavnom u fizičkom topologije) ali ne treba odgovarati u smislu predložaka, verzije, itd..

Nisam vidio cijeli kraja do kraja demo, but DuWayne did show screen shots and some live demos. It seems to be as good as it needs to be, barem umjereno veličine okoliš.

I was particularly struck by the pricing. Obviously, ne držite me to, ali vjerujem da je najskuplja cijena je otprilike ovakav (u USD):

• $600 za DPM sama.
• Hardver za DPM poslužitelj (i povezane stvari za medije i sve koji).
• $450 za svaki poslužitelj želite kopiju ("Poduzeće" dozvola).

Pet farmi poslužitelja će koštati najviše:

• $600 za DPM
• $450 x 5 poslužitelji = $2,250

Ukupni trošak u licenci: $2,850

U praksi, it would be less. You wouldn’t necessarily need to have DPM installed on each web front end, na primjer. 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 Dan klase dostupan, iako to nije jasno mi je da netko stvarno bi trebao uzeti ga.

Sve u svemu, Mislim da je svakako vrijedno istražuju, ako ste vani u potrazi za rješenje za zaštitu podataka za SharePoint.

</kraj>

Pretplatite se na moj blog.

Cvrkut: http://twitter.com/pagalvin