Zuretzat zopa No! Cisco da NLB produktuen nazien zopa?

Gaur egun, 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. (/ Denean sare morroiak esango dit zer den, Post hau eguneratuko dut).

Windows explorer couldn’t connect. I did some research and eventually, sare morroiak esan WebDAV desgaituta dago arabera / ez du onartzen / beneath the dignity of the NLB.

Beraz,, assuming the network wizards aren’t just telling me the network wizard equivalent of "take a long walk off a short bridge", Galdetzen daukat — du NLB, Naturak, desgaitu WebDAV? Do we lose our windows file explorer interface to SharePoint? Is Cisco the Zopa nazien?

MOSS kudeatzea / Ingurune WSS — mantentzeko Microsoft-en jakintza-oinarri

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.

Jarraitu nuen haiekin bizkortzeko zerbitzu baten bidez ona Folks hornitu at 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 Aplikazio-politika, Segurtasun-guneak eta segurtasuna trimming — Ezagutu zure konfigurazioa

(EGUNERATUA 11/29 nola web aplikazio politika ezarpenak sartzeko azaltzeko UI bidez)

I had one of those "why is MOSS doing this to me????" moments today. Azkenean, Nire errua da guztia.

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. Gunera joan.
  2. Break segurtasun ondarea.
  3. Kendu erabiltzaile bakoitzak / talde baimenak gune batetik.

Gainetik besterik gune-administratzaile-bilduma utzi behar baimena gune ikusi nahi dituzten.

Inork egunkaria bada, ez da gehiago behar dute ikusi gune eta izango da, ohiko leku guztietako segurtasun-moztutako.

Baina … ez zen. Aldi berean,, 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, azkenik, Dut aurkitu duen Ethan bloga, his opening graph makes it quite simple:

Moss 2007 izeneko web aplikazioa politikak ezaugarri berri bat dauka. Horiek segurtasun-baimen hori web aplikazio lotuta daude. Segurtasun ezarpen horiek baliogabetzeko edozein segurtasun-ezarpen bat da, bilduma, edo Web Gunearen ezarri (Web) erabiltzaile maila.

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, baina, Aurrekontu bat iragazi nahi, "It does not mean what you think it means."

Access web application policies this way:

  1. Administrazio Zentralari joan
  2. Aukeratu Gestión
  3. Select "Policy for Web Application"
  4. Pantaila horretan, make sure you pick the correct web application. Niretzat, lehenetsi admin erdiko aplikazio web eta horrek agian ez da nahi duzuna da.

Noiz arazo hori izan nuen, Bilatuko du ondorengo esaldi dut eta lortu harrigarriro txiki zuzeneko laguntza dagokionez gai honetan:

Gune ekintzak erabiltzaile guztientzat ikusgai

Gune ekintzak erabiltzaile guztientzat ikusgai

gune ekintzak ez dira segurtasun-moztutako

ziurtatzeko MOSS gune bat

to goroldioa segurtasun sarrera

Technorati Tags:

Azkarra eta sinplea: Finkoa erabili beharreko testua bilaketari Core emaitzak

Azkarra eta sinplea jarraibideak:

Aldatu orri bat eta bilatu Core emaitzak web zati gehitu.

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

Gehitu finkoa keyword kontsulta (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").

Oharrak:

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: Sailak eta Produktuak.

Produktuaren gune bilduma dauka, naturalean nahikoa, product information. Each product in the site collection aggregates data from multiple sources.

Sail bat, kodeak eta azterketa, 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".

Planteamendu honek onura atsegina: We can edit the XSL from the core search results web part and generate any format that we want.

Ikusi hemen (http://devcow.com/blogs/jdattis/archive/2007/04/17/SharePoint_2007_How_to_Rollup_Content_from_multiple_Site_Collections.aspx) Blogger beste gai honi buruzko eztabaida.

</amaiera>Nire blog Harpidetu.

Esadazu zure blog!

Mantentzen baduzu, blog bat bada, hori gutxienez minimoki to SharePoint konektatuta, please let me know in comments. I would love to add you to my blog list.

Mantentzen baduzu, blog bat ez dela SharePoint konektatuta badago, baina nahi gehitzeko Niri hala ere, let me know. I’ll may create a separate blog list.

Please give:

  • Your blog URL (jakina,)
  • A short description of your blog.

I want to keep the link to "active" blogs, 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.

Eskerrik asko!

Langileak prestatzeko Ordutegiak eta Materialen Txantiloi — Decrement plantilla akats

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

Course managers create courses. When creating a course, kudeatzailea eserleku eskuragarri gehienezko kopurua zehazten du.

The template provides for self-service enrollment. I enroll and a workflow attached to the registration list decrements the "available seats" ikastaro lotutako.

Individuals may also unregister from a course. The bug lies here. Unregistering from a course does not increment the available seats counter. Baten ondorioz, available seats is not accurate. This bug is compounded by the fact that when available seats decrements to zero, ez gehiago auto-zerbitzua erregistroa onartzen da.

Zorionez, Microsoft provides the workflow for this process. Even better, SharePoint Designer bidez sortzen zuzen Aurrera workflow bat da.

Jarraitu horiek maila handiko urratsak konpondu:

  1. Sua sortu SDP.
  2. Sartzeko prestakuntza plantilla off oinarritzen Gunean.
  3. Access "Attendee unregistration" workflow.
  4. Txertatu urrats hauek (Horietako lehen bi urrats egin nuen):
    1. Kalkulatzeko Ikastaroak:Bete estaliak ken 1 (Irteera Aldakorra:calc)
    2. (ondoren,) Eguneratu elementu Ikastaroak

Egin klik Amaitu eta Bukatutakoan.

Pantaila plano:


SharePoint Designer:

image

Amaitu workflow:

image

Kalkulatzeko zulatzeko-behera:

image

Eguneratu elementua Ikastaroak:

image

Eman albiste ona maiz; albiste txarra eman hasieran

Izan dut aholkulari bat, orain urte asko, eta esperientziadun aholkulari edozein daki, good communication is one of the key pillars to the successful delivery of a project. Beraz, begi-bistakoa da, it’s really almost boring to talk about. This isn’t a post about generic communication. Horren ordez, Komunikazioaren alde ilunagoa buruz idazten ditut — communicating bad news.

It goes without saying that giving good news to the client is done all the time, as often as possible. Who doesn’t want to give good news? Who doesn’t like to hear good news?

On the flip side, bad news is no fun at all. I have always struggled with this. In the earlier days of my career, I would know something was awry with a project and instead of telling the client, 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 to 80 hour weeks?

What is the best way to handle bad news? 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 (probably will), there may be incriminations and accusations and hurt feelings. Baina, when emotions cool off, there’s still six weeks left on the project. Six weeks is a good chunk of time. There’s time to adjust plans, change schedules, get the ball rolling on budget extensions (good luck!) and just generally come to grips with the "facts on the ground" and devise a new plan that still results in a successful project.

Case in point: I’m working on a project characterized by:

  • T&E budget with a capped "Not to exceed" dollar amount.
  • A "best efforts will be made" promise to deliver X, Y and Z by project’s end.
  • Lack of promised key resources on the client side. These resources were not withheld on purpose, nor for any "bad" reason, but they were withheld.
  • A dawning realization as the project passed the half-way point that we were not going to be able to deliver "Z" (mainly because the promised resources were not actually available).
  • Regular status reports and "CYA" documentation that backed us (the consulting team) up.
  • Tightly knit implementation team with members drawn from the consulting organization (Nire enpresa) and the client.
  • Distant management team, in both a metaphorical and physical sense. The management team was focused on another large enterprise project and due to space constraints, the implementation team was housed in a separate building on campus, down a hill and relatively far way from "civilization".

With roughly six weeks left on the project budget, dugu (the implementation team) 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" to deliver Z and even though we had great justification for missing the delivery … the bottom line is that it wasn’t looking good — we were not going to deliver Z in a shape a quality that would make anyone proud.

Recognizing this, we went to management and told them that the project budget would be consumed by a certain date and that we were in trouble with Z.

A mini firestorm erupted over the next few days.

Day 1: Management team calls in its staff for a special meeting (dugu, the consultants are not invited). 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 "Stockholm Syndrome" is *actually* used, but you get the picture. We’re a tight-knit group, azken finean, and the staff has been working with us consultants day in and out for several months now.

Day 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: schedule a meeting with full implementation team (including consultants).

Day 5: Full team meets, 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.

If we had waited until just three weeks remained, or even worse, one or two weeks, it would have been much different. Instead of a constructive meeting to re-align the project, we would have been pulling out status reports, parsing the contract and reviewing old emails to justify this or that decision. We would have "won" but is it really "winning" kasu honetan?

Beraz,, if you have to give bad news, give it early. Bad news given late isn’t just bad, izugarria da.

Erabiliz “Pertsona edo Talde” bat kalkulatzen zutabean

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

Behean line, horrek ez du lan egiten WSS 3.0 (edo MOSS).

Noiz kalkulatzen zutabe bat gehituz, 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, pasatzean,:

Bat edo gehiago zutabe erreferentziak ez dira onartzen, zutabeak dira datu-mota bat bezala definitzen duelako ez dela formula onartzen.

Sahiesteko: 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.

Erabilgarria eremu kalkulatzen loturak, oro har,:

Quick Lege-oharra: Gainetik egiazkoak eta zehatzak izan behar duela uste dut,, baina ikusi dut nahikoa clever trikimailu han eta hemen MOSS / WSS litzateke hori ez dut oso harrituta (agog duzu bada) 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, please let me know!

MOSS / WSS esaten dit: “Orria izan da egilearen beste aldaketa on …” baina, egia esan,, ez zen.

We did some heavy duty re-organizing of our site taxonomy via "Manage Content and Structure". For reasons unknown to me, Prozesu honetan (nagusi, nahiz eta lan-) broke some navigation links in the quick launch. The broken links are characterized by:

  • Wrong URL. Adibidez, it should be "/sites/departments/HumanResources/…". Hala eta guztiz ere, the new link is "/sites/Corporate/HumanResources/…".
  • Errepikatzen buruzko epigrafe kontsulta katea bit, bezala:

/guneak / sail / HumanResources / _layouts / viewlsts.aspx?BaseType = 0?BaseType = 0?BaseType = 0?BaseType = 0

That’s easy enough to fix via site settings/navigation. Except, MOSS aurkezten me batera, eta saiatu dut:

image

Izan ere,, inork ez edozein aldaketa ez dago egiten ari da (alde batera from me, jakina).

Bilaketa bizkor bat bihurtzen da, hau MSDN eztabaida foroak: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1691577&SiteID=1

William Heurdier ere, planoan out nicely azkenaurreko en (gisa 10/02/07) bidaltzeko:

Izan da:

Hondatuta izenburuak berrezarri, behar duzu :

– kendu zerrendak guztiak epigrafe hondatuta pean

– kendu hondatuta epigrafe

– Zerrenda ezarpenen, add a removed list to the quick launch (Hau birsortzeko ez hondatuta epigrafe)

Ondoren, zaude onak joan….


Sharepoint aditua – Sogeti Cap Gemini Suitza

Apur bat nahastu izan dut mantendu I nabigazio orrira nahi duelako, make the change and then get hit with the "page was modified" message. Azkenean, 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!

</amaiera>

Nire blog Harpidetu!

Arazoak dituzten “Noiz arte pausatu” SPD sortutako fluxuak jarduera

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. Gero, sharepoint configuration utility on each server. Here is the MS Support link for that KB: http://support.microsoft.com/kb/932816.

Aurrekariak:

Enpresa-baldintza, non ingurumen ingeniaritza kudeatzailea behar ziurtatu dugu 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 (edo bere laguntzaile) enters all the required permits and reminder dates at the start of the year. The system then does all the heavy lifting.

Ingurumena:

Moss, 64 bit, Makina birtual ingurumena (garapen kutxa), 2 zerbitzariak (SQL zerbitzari batean #1, beste guztia zerbitzari batean #2).

Arazoak:

The Pause Until Date action seems like the perfect solution and it may well prove itself to be. Hala eta guztiz ere, ez da ongi atera kutxa (Gurekin).

  1. Workflow lana ez zen programatuta exekutatu, ever. I discovered this by reading through Christopher White en (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:\>

    Duten emaitza harrigarria izan zen, baina erraz konpondu:

    C:\>stsadm -o setproperty -propertyname "job-worfklow" -propertyvalue "every 1 minutu artean 0 eta 59" -url http://localhost

    Eragiketa burutu.

    C:\>

    Gainean egiten duten, the first "In Progress" workflow azkar tiro sortu eta bere lana egin.

  2. Tamalez, the next one didn’t work as expected. Zorionez, Christopher refers us hemen (http://support.microsoft.com/kb/932816). As of writing of this entry, IT departamentuko ari gara Hotfix zuzenketa hori lortzeko zain, but it does look promising. Our copies of the affected .dll’s do not share the same byte size, beraz, espero honek arazoa konponduko.

Sahiesteko:

Re-running the stsadm -o setproperty command seemed to prod the workflow timer awake. It would, gutxi gorabehera 7 minutu geroago, actually wake up and continue along with the workflow.

Galderak / Aleak Norentzat:

Data pausatu arte ez du funtzionatzen.

Data pausatu arte ez da hasi berriro.

Workflow status does not change from "In Progress"

Workflow status stays "In Progress"