Ne juha za vas! Je Cisco juha nacističke NLB proizvoda?

Danas, I tried to access a document library via windows explorer. This doc lib is living inside a system that consists of two WFE’s load balanced by some kind of Cisco NLB solution. (Ako / kada je mrežu čarobnjaci mi reći što je to, Ja ću ažurirati ovaj post).

Windows explorer couldn’t connect. I did some research and eventually, Mreža čarobnjaci rekao da WebDAV je onemogućio / Ne podržava / beneath the dignity of the NLB.

Tako, assuming the network wizards aren’t just telling me the network wizard equivalent of "take a long walk off a short bridge", Moram se pitati — ne NLB, po prirodi, onemogućiti WebDAV? Do we lose our windows file explorer interface to SharePoint? Is Cisco the Juha od nacista?

Upravljanje Moss / WSS okruženja — ukorak s Microsoftove baze znanja

Microsoft creates knowledge base articles day in and day out and some of those are darned important to know about if you live in the SharePoint world.

Držim do brzine s njima putem usluge koje pružaju dobre ljudi na www.kbalertz.com. KBAlertz enables you to sign up for your favorite MS technology and they send you digest versions of Microsoft KB articles via email.

Web aplikacija privatnosti, Sigurnost mjesta i sigurnosti Obrezivanje — Upoznajte svoju konfiguraciju

(NADOPUNJENO 11/29 objasniti kako pristupiti web postavke aplikaciju putem UI)

I had one of those "why is MOSS doing this to me????" moments today. Na kraju, sve je to moja krivnja.

We have an enterprise MOSS project going on and we want to secure "place holder" sites so that no user may access it or see it. That’s easy:

  1. Idi na licu mjesta.
  2. Razbijte nasljeđivanje sigurnosni.
  3. Uklonite svaki korisnik / grupa od mjesta dozvolama.

Gore navedeni trebali ostaviti samo administratoru zbirke web-mjesta s dozvolom da bi vidjeli site.

Ako netko drugi prijavljuje, oni više ne bi trebao vidjeti stranice i to bi trebao biti sigurnosno-obrezuje na svim uobičajenim mjestima.

Ali … nije bilo. Istovremeno, I suddenly realize that my "Joe User" standard user test account with no priv’s other than restricted read access has a "Site Actions" choice everywhere he goes. I double check one thing and double check something else. I pick up the phone to call a colleague, but put it down and check something else. I go for a walk and try everything all over again. I call a colleague and leave a message. And then, konačno, Smatram da je na Ethan blog, his opening graph makes it quite simple:

MOSS 2007 ima novu značajku pod nazivom Web Application Pravila. To su sigurnosne dozvole koji je vezan za web-aplikacija. Ove sigurnosne postavke nadjačati sve sigurnosne postavke koja je postavljena na mjestu zbirci ili Stranici (Tkanje) Razina za tog korisnika.

A quick visit to web application policies shows that "NT Authority\authenticated users" had been granted Full Read. I removed them from the list and everything finally started working as expected. I believe they were added in the first place by someone with the mistaken impression that that is best method to grant read access to everyone in the enterprise. It does, ali, naprezanje citat, "It does not mean what you think it means."

Access web application policies this way:

  1. Idi na središnjoj administraciji
  2. Odaberite aplikacija za upravljanje
  3. Select "Policy for Web Application"
  4. Na tom zaslonu, make sure you pick the correct web application. Za mene je, to je defaultno web aplikacije središnje admin koji ne može biti onaj koji želite.

Kad sam imala taj problem, Tražila sam sljedećih izraza i dobio iznenađujuće malo u smislu izravne pomoći po tom pitanju:

Akcije web vidljive za sve korisnike

Akcije web vidljivi svim korisnicima

licu mjesta radnje nisu sigurnosni obrezuje

osigurati MOSS stranice

Uvod u mahovine sigurnosti

Technorati Tags:

Brzo i jednostavno: Koristite Fiksni Pitanje Riječ za Search Results Temeljnih

Quick and Simple Instructions:

Edit a page and add a Search Core Results web part.

Edit that web part and expand "Fixed Keyword Query".

Add the fixed keyword query (e.g. ContentType:"Training invoice" TrainingInvoiceNumber:1111)

Expand Results Query Options and change "Cross-Web Part query ID" to a value other than "User Query" (e.g. "Query 2").

Bilješke:

Using core search results in this manner allowed me to create a page that shows information from another site collection. The client has two major site collections: Departments and Products.

The product site collection contains, naturally enough, product information. Each product in the site collection aggregates data from multiple sources.

One of the departments, codes and testing, is on such source. When users access product XYZ, they should see codes and testing data directly on the XYZ main page. Since codes and testing is hosted in another site collection, it’s a little awkward. We decided to use the core search results web part since search spans site collections. Codes and Testing manages product data via a custom list that is constrained by a specific content type. Aa keyword query that uses first the content type and then the product number narrow down the search to a single row in the custom list.

The keyword query above is an AND. It returns documents of content type "Training Invoice" and where the invoice number equals "1111".

A nice benefit from this approach: We can edit the XSL from the core search results web part and generate any format that we want.

Vidi ovdje (http://devcow.com/blogs/jdattis/archive/2007/04/17/SharePoint_2007_How_to_Rollup_Content_from_multiple_Site_Collections.aspx) for another blogger’s discussion on this topic.

</kraj>Pretplatite se na moj blog.

Reci mi o svom blogu!

Ako održavati blog koji je barem minimalno spojen na SharePoint, please let me know in comments. I would love to add you to my popis blogova.

Ako održavati blog koji nije spojen na SharePoint, ali ja želim da ga dodate svejedno, javite mi. I’ll may create a separate blog list.

Molim Vas, dajte:

  • Vaš blog URL (očito)
  • Kratak opis bloga.

I want to keep the link to "active" blogovi, which I’m roughly defining as one post per week and minimum three months old. If you don’t meet that "requirement" add your name to comments anyway. It’s *my* list so I can break my own rule if I want to.

Hvala!

Zaposlenik raspored treninga i materijali predlošku — Snižavanja bug u predlošku

The client noticed a bug today with the above mentioned template.

Course managers create courses. When creating a course, the manager specifies maximum number of available seats.

The template provides for self-service enrollment. I enroll and a workflow attached to the registration list decrements the "available seats" associated with that course.

Individuals may also unregister from a course. The bug lies here. Unregistering from a course does not increment the available seats counter. Kao rezultat toga, available seats is not accurate. This bug is compounded by the fact that when available seats decrements to zero, no more self-service registration is allowed.

Fortunately, Microsoft provides the workflow for this process. Even better, it’s a straight-forward workflow created via SharePoint Designer.

Follow these high level steps to fix it:

  1. Fire up SDP.
  2. Access the site based off the training template.
  3. Access "Attendee unregistration" tijek rada.
  4. Insert these steps (I made them the first two steps):
    1. Calculate Courses:Filled Seats minus 1 (Izlaz na Varijabla:calc)
    2. (zatim) Update item in Courses

Click Finish and you’re done.

Screen shots:


SharePoint Designer:

slika

Finished workflow:

slika

Calculate drill-down:

slika

Update item in Courses:

slika

Daj dobre vijesti često; daju lošu vijest rano

Ja sam bio konzultant za mnogo godina i sada, kao svaki iskusni konzultant zna, good communication is one of the key pillars to the successful delivery of a project. To je tako očito, it’s really almost boring to talk about. This isn’t a post about generic communication. Umjesto toga, Pišem o tamnijoj strani komunikacije — komuniciranja loših vijesti.

To ide bez rekavši da daje dobre vijesti za klijenta obavlja se cijelo vrijeme, as often as possible. Who doesn’t want to give good news? Who doesn’t like to hear good news?

Na drugoj strani, bad news is no fun at all. I have always struggled with this. In the earlier days of my career, Ja bih znao da nešto nije naopako s projektom, a umjesto reći klijentu, I would work longer hours to try and solve the problem. I would enjoin my team to work harder. It’s a natural enough impulse to think that a super-human effort can save the day. Some times this works, some times it does not. Even when it "works" it’s often a mixed bag. Is the quality of the deliverable really up to spec when key parts have been developed over several 60 na 80 sat tjedana?

Koji je najbolji način da se nositi loše vijesti? The answer is: tell it early. Don’t wait until one week before the project budget will be consumed. If you know six weeks out that there simply isn’t enough time to deliver some bit of promised functionality, tell the client right then and there. The client may get upset (Vjerojatno hoće), there may be incriminations and accusations and hurt feelings. Ali, kad emocije ohladiti, there’s still six weeks left on the project. Six weeks is a good chunk of time. There’s time to adjust plans, promijeniti raspored, dobili loptu valjanje na proračunske nastavcima (sretno!) and just generally come to grips with the "facts on the ground" and devise a new plan that still results in a successful project.

Slučaj u točki: Radim na projektu karakterizira:

  • T&E budget with a capped "Not to exceed" dolar iznos.
  • A "best efforts will be made" Obećanje da dostavi X, Y i Z do kraja projekta.
  • Lack of promised key resources on the client side. These resources were not withheld on purpose, nor for any "bad" razlog, ali oni su zadržana.
  • A dawning realization as the project passed the half-way point that we were not going to be able to deliver "Z" (uglavnom zbog obećana sredstva zapravo nisu dostupni).
  • Regular status reports and "CYA" Dokumentacija koja nas podlogom (savjetovanje tim) up.
  • Skopčana provedba ekipa s članovima izvučeni iz konzultantske organizacije (moja tvrtka) i klijent.
  • Distant upravljanje tim, in both a metaphorical and physical sense. The management team was focused on another large enterprise project and due to space constraints, Provedba momčad bila smještena u zasebnoj zgradi na kampusu, down a hill and relatively far way from "civilization".

S otprilike šest tjedna ostalo na projektnom proračunu, mi (Provedba momčadi) knew that we were trouble. The contract said that we needed to deliver "Z". Even though the project is time & materials and even though we only promised "best efforts" dostaviti Z, a iako smo imali veliku opravdanje za nestale dostavu … Dno crta je da on nije izgleda dobro — da nećemo isporučiti Z u obliku kvalitetu koja bi netko ponosan.

Prepoznajući to, otišli smo na upravljanje i rekao im da je proračun projekta bi se konzumira u određenom roku i da smo bili u nevolji s Z.

Mini FireStorm izbio tijekom sljedećih nekoliko dana.

Dan 1: Uprava kluba poziva u svojoj osoblja za poseban sastanak (mi, konzultanti nisu pozvani). Contracts are printed and handed out to everyone and a line-by-line review ensues. Management puts the staff members on the defensive. I don’t think the phrase "Stockholmski sindrom" je * zapravo * koristiti, ali ćete dobiti sliku. We’re a tight-knit group, uostalom, a osoblje je radio s nama konzultanti dan in i out za nekoliko mjeseci.

Dan 2: Management calls another staff meeting. They feel a little better. They want options and ideas for moving forward. They realize there’s still six weeks remaining in the current project budget, which is still a decent bit of time. One of the action items: zakazati sastanak s puna provedba tim (uključujući i konzultanti).

Dan 5: Cijeli tim sastaje, constructive meeting ensues and a new achievable plan put into place. Even better, we’ve already begun discussing phase two and the client invites us to prepare proposals for that phase immediately.

Ako smo čekali dok samo tri tjedna ostala, ili još gore, jedan ili dva tjedna, it would have been much different. Instead of a constructive meeting to re-align the project, mi bi bili čupanje izvješća o stanju, parsing the contract and reviewing old emails to justify this or that decision. We would have "won" but is it really "winning" u ovom slučaju?

Tako, ako imate dati loše vijesti, give it early. Bad news given late isn’t just bad, to je strašno.

Korištenje “Osoba ili Grupa” u izračunatom stupcu

People commonly ask about using a column of data type "Person or Group" in another column of data type "Calculated".

Bottom line, to ne rade u WSS 3.0 (ili MOSS).

Kod dodavanja izračunatog stupca, WSS shows the list of fields it allows you to use for the calculation. If you type in the name of a column that is not in its list, to vam govori:

Jedna ili više stupaca reference ne smiju, jer su stupovi definira kao vrstu podataka koji nije podržan u formulama.

Rješenje: Use an event handler. The event handler fires when the user saves the item. It performs the update you would have wanted the calculated column to do for you.

Korisni linkovi na izračunatih polja općenito:

Brza disclaimer: Vjerujem da gore da bi bilo istinito i točno, ali vidio sam dovoljno dosjetljivim trikovima tu i tamo u MOSS / WSS da neću biti vrlo iznenađeni (nestrpljivo ako hoćeš) if someone has figured out a way to do this without resorting to code. If you’ve figured out clever work-around or know someone that did, javite mi!

MOSS / WSS mi govori: “Stranica je izmijenjena od strane drugih autora na …” ali zapravo, nije bilo.

We did some heavy duty re-organizing of our site taxonomy via "Manage Content and Structure". For reasons unknown to me, taj proces (iako radi u glavni) broke some navigation links in the quick launch. The broken links are characterized by:

  • Wrong URL. Na primjer, it should be "/sites/departments/HumanResources/…". Međutim, the new link is "/sites/Corporate/HumanResources/…".
  • Ponovljeni bita na niz upita od naslova, kao u:

/mjesta / odjela / HumanResources / _izgledi / viewlsts.aspx?BaseType=0?BaseType=0?BaseType=0?BaseType=0

That’s easy enough to fix via site settings/navigation. Except, MOSS mi predstavlja s tim kad sam probati i učiniti ga:

slika

Činjenica je, nitko se ne postoje nikakve promjene (Osim mene, naravno).

Brza pretraga pretvara se u raspravu MSDN foruma: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1691577&SiteID=1

William Heurdier ga izlaže lijepo u predzadnjem (od 10/02/07) pošta:

Činjenica je:

Za vraćanje oštećene naslove, moraš :

– ukloniti sve popise po korumpiran naslova

– uklanjanje oštećene naslova

– Iz popisa postavkama, add a removed list to the quick launch (Ovo regeneraciju oštećene non naslova)

Vi ste onda dobro proći….


Sharepoint Expert – Cap Gemini Sogeti Švicarska

Bio sam malo zbunjena jer sam se želio ići u navigacijskom stranici, make the change and then get hit with the "page was modified" message. Konačno, I realized I had to go to the list settings and remove/add it to quick launch. That did the trick. Happy times are here again!

</kraj>

Pretplatite se na moj blog!

Problemi s “Pauza do datuma” aktivnost u SPD-stvorenih radnih tijekova

UPDATE 12/10/07: Hotfix as described in MSDN KB929816 solved the problem for us mentioned below. Obtain the hotfix and then install on each server on the farm. Tada, sharepoint configuration utility on each server. Here is the MS Support link for that KB: http://support.microsoft.com/kb/932816.

Pozadina:

Imamo poslovne zahtjev u kojem inženjerstva okoliša manager treba osigurati da 30 some-odd manufacturing locations located throughout the United States needs to ensure that those plants file for their various state-mandated permits in a timely fashion. One approach we’ve investigated leverages the "Pause Until Date" activity available to us via SharePoint Designer worfklow. The engineering manager (ili njezin pomoćnik) enters all the required permits and reminder dates at the start of the year. The system then does all the heavy lifting.

Okolina:

MOSS, 64 bit, virtualni stroj okoliš (Razvoj box), 2 poslužitelji (SQL na poslužitelju #1, sve ostalo na poslužitelju #2).

Problemi:

The Pause Until Date action seems like the perfect solution and it may well prove itself to be. Međutim, to ne radi i iz kutije (za nas).

  1. Tijek posao nije na rasporedu, ever. I discovered this by reading through Christopher Whitea (http://chrissyblanco.blogspot.com/2007/06/issues-with-delay-activity-in-moss.html) excellent write-up by using stsadm thusly:

    C:\>stsadm -o getproperty -propertyname "job-workflow" -url http://localhost

    <Property Exist="No" />

    C:\>

    To je čudno, ali rezultat se lako riješiti:

    C:\>stsadm -o setproperty -propertyname "job-worfklow" -propertyvalue "every 1 minuta između 0 i 59" -url http://localhost

    Operacija je uspješno završena.

    C:\>

    Na taj događaj, the first "In Progress" tijek brzo vatru i učinio da je posao.

  2. Nažalost, the next one didn’t work as expected. Srećom, Christopher refers us ovdje (http://support.microsoft.com/kb/932816). As of writing of this entry, čekamo IT odjela dobiti taj hitni popravak, but it does look promising. Our copies of the affected .dll’s do not share the same byte size, pa se nadam da će to riješiti problem.

Rješenje:

Re-running the stsadm -o setproperty command seemed to prod the workflow timer awake. It would, grubo 7 minuta kasnije, actually wake up and continue along with the workflow.

Pitanja / Razmatrana pitanja:

Pauza Do danas ne rade.

Pauza do datuma se ne vraća.

Workflow status does not change from "In Progress"

Workflow status stays "In Progress"