Nru soppa għalik! Huwa Cisco l-Nazisti Soppa tal-prodotti NLB?

Illum, 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. (Jekk / meta l-wizards network tell me dak li hu, I ser taġġorna din il-kariga).

Windows explorer couldn’t connect. I did some research and eventually, l-wizards netwerk qal li WebDAV huwa b'diżabilità mill / mhux sostnut minn / beneath the dignity of the NLB.

Allura, assuming the network wizards aren’t just telling me the network wizard equivalent of "take a long walk off a short bridge", I wonder — ma NLB, min-natura, jiskonnettja WebDAV? Do we lose our windows file explorer interface to SharePoint? Is Cisco the Soppa Nazisti?

Maniġerjali MOSS / Ambjenti WSS — tlaħħaq ma bażi ta 'għarfien ta' Microsoft

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.

I iżommu sa veloċità magħhom permezz ta 'servizz jipprovdi mill-folks tajba fil 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.

Politika Web Applikazzjoni, Siti ta 'sigurtà u s-Sigurtà Tirqim — Know konfigurazzjoni tiegħek

(UPDATED 11/29 biex jispjegaw kif jaċċessaw settings web politika applikazzjoni permezz tal-UI)

I had one of those "why is MOSS doing this to me????" moments today. Fl-aħħar, dan kollu tort tiegħi.

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. Mur għall-sit.
  2. Kisser il-wirt sigurtà.
  3. Neħħi kull utent / grupp minn permessi sit.

Ta 'hawn fuq għandhom iħallu biss l-amministratur ġbir sit bil-permess biex tara d-sit.

Jekk xi ħadd ieħor zkuk fil, dawn ma kellhomx jibqgħu ara s-sit u għandu jkun sigurtà mirqum mill-postijiet kollha tas-soltu.

Iżda … ma kienx. Fl-istess ħin, 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, finalment, I isibu li fi Blog Ethan tal, his opening graph makes it quite simple:

MOSS 2007 għandha karatteristika ġdida msejħa Politiki applikazzjoni tal-web. Dawn huma permessi sigurtà li hija marbuta ma 'Web Applikazzjoni. Dawn is-settings tas-sigurtà jwarrab kwalunkwe ambjent ta 'sigurtà li huwa stabbilit fil-Ġbir sit jew f'sit (Web) livell għal dak l-utent.

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, iżda, li strain kwotazzjoni, "It does not mean what you think it means."

Access web application policies this way:

  1. Mur Amministrazzjoni Ċentrali
  2. Agħżel Applikazzjoni ta 'Ġestjoni
  3. Select "Policy for Web Application"
  4. Fuq dik screen, make sure you pick the correct web application. Għalija, huwa defaults għall-applikazzjoni tal-web ta 'admin ċentrali li ma jistax ikun l-waħda tixtieq.

Meta kelli din il-problema, I mfittxija għall-frażijiet li ġejjin u ltqajna ftit sorprendenti f'termini ta 'għajnuna diretta fuq din il-kwistjoni:

Azzjonijiet sit viżibbli għall-utenti kollha

Azzjonijiet sit viżibbli għall-utenti kollha

azzjonijiet sit mhumiex sigurtà mirquma

jiżgura sit MOSS

introduzzjoni għas-sigurtà ħażiż

Quick u sempliċi: Uża Mistoqsija Keyword fissi fil Riżultati Core Fittex

Malajr u sempliċi Istruzzjonijiet:

Jeditjaw paġna u żid Core Riżultati web part Fittex.

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

Żid il-mistoqsija keyword fiss (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").

Noti:

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: Dipartimenti u l-Prodotti.

Il-kollezzjoni sit prodott fih, naturalment biżżejjed, product information. Each product in the site collection aggregates data from multiple sources.

Wieħed mill-dipartimenti, kodiċijiet u ttestjar, 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 benefiċċju sbieħ minn dan l-approċċ: We can edit the XSL from the core search results web part and generate any format that we want.

Ara hawn (http://devcow.com/blogs/jdattis/archive/2007/04/17/SharePoint_2007_How_to_Rollup_Content_from_multiple_Site_Collections.aspx) għal diskussjoni blogger ieħor fuq dan is-suġġett.

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

Tell me dwar blog tiegħek!

Jekk inti żżomm blog li hija inqas minimament konness ma SharePoint, please let me know in comments. I would love to add you to my lista blog.

Jekk inti żżomm blog li ma jkunx ikkonnettjat ma SharePoint iżda trid lili biex iżżid hija xorta waħda, let me know. I’ll may create a separate blog list.

Jekk jogħġbok agħti:

  • Your blog URL (ovvjament)
  • Deskrizzjoni qasira tal-blog tiegħek.

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.

Grazzi!

Impjegat Skeda Taħriġ u Materjali Template — Bug decrement fil-mudell

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

Course managers create courses. When creating a course, il-maniġer tispeċifika numru ta 'postijiet disponibbli.

The template provides for self-service enrollment. I enroll and a workflow attached to the registration list decrements the "available seats" assoċjati ma 'dak il-kors.

Individuals may also unregister from a course. The bug lies here. Unregistering from a course does not increment the available seats counter. Bħala riżultat, available seats is not accurate. This bug is compounded by the fact that when available seats decrements to zero, mhux aktar reġistrazzjoni self-service huwa permess.

Fortunatament, Microsoft provides the workflow for this process. Even better, huwa workflow straight-quddiem maħluqa permezz SharePoint Designer.

Segwi dawn il-passi ta 'livell għoli biex jiffissaw dan:

  1. Fire up SDP.
  2. Aċċess għas-sit bbażata off-mudell taħriġ.
  3. Access "Attendee unregistration" workflow.
  4. Daħħal dawn il-passi (I magħmula minnhom l-ewwel żewġ passi):
    1. Ikkalkula Korsijiet:Seats Mimlijin minus 1 (Output biex Varjabbli:calc)
    2. (imbagħad) Aġġornament oġġett Korsijiet

Ikklikkja Finish u qed isir.

Screen shots:


SharePoint Designer:

immaġni

Workflow lest:

immaġni

Ikkalkula drill-down:

immaġni

Aġġornament oġġett fil Korsijiet:

immaġni

Agħti aħbar tajba spiss; jagħtu aħbar ħażina kmieni

Stajt kien konsulent għal ħafna snin u issa bħala kwalunkwe konsulent b'esperjenza jaf, good communication is one of the key pillars to the successful delivery of a project. Huwa daqshekk ovvja, it’s really almost boring to talk about. This isn’t a post about generic communication. Minflok, Jien bil-miktub dwar il-ġenb jiskuraw ta 'komunikazzjoni — komunikazzjoni aħbar ħażina.

Huwa ovvju li l-għoti aħbar tajba għall-klijent isir il-ħin kollu, as often as possible. Who doesn’t want to give good news? Who doesn’t like to hear good news?

Fuq in-naħa flip, bad news is no fun at all. I have always struggled with this. In the earlier days of my career, Nixtieq taf xi ħaġa kienet awry ma 'proġett u minflok javżak-klijent, 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 li 80 ġimgħat siegħa?

X'inhi l-aħjar mod biex jimmaniġġaw aħbar ħażina? 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 (probabbilment se), there may be incriminations and accusations and hurt feelings. Iżda, meta emozzjonijiet jibred off, there’s still six weeks left on the project. Six weeks is a good chunk of time. There’s time to adjust plans, bidla iskedi, jiksbu l-ballun rolling fuq estensjonijiet tal-baġit (Xorti tajba!) and just generally come to grips with the "facts on the ground" and devise a new plan that still results in a successful project.

Kawża fil-punt: Jien jaħdmu fuq proġett ikkaratterizzat minn:

  • T&E budget with a capped "Not to exceed" ammont ta 'dollari.
  • A "best efforts will be made" wegħda li jagħti X, Y Z u sa tmiem proġett.
  • Lack of promised key resources on the client side. These resources were not withheld on purpose, nor for any "bad" raġuni, imma dawn kienu miżmuma.
  • A dawning realization as the project passed the half-way point that we were not going to be able to deliver "Z" (prinċipalment għaliex ir-riżorsi mwiegħda kinux attwalment disponibbli).
  • Regular status reports and "CYA" dokumentazzjoni li appoġġjata us (it-tim konsultazzjoni) up.
  • Tim implimentazzjoni sewwa maħdumin mal-membri mfassla mill-organizzazzjoni konsultazzjoni (kumpanija tiegħi) u l-klijent.
  • Tim ta 'ġestjoni Distanti, in both a metaphorical and physical sense. The management team was focused on another large enterprise project and due to space constraints, it-tim implimentazzjoni ġie miżmuma f'bini separat fuq il-kampus, down a hill and relatively far way from "civilization".

B'madwar sitt ġimgħat tax-xellug fuq il-baġit tal-proġett, aħna (it-tim implimentazzjoni) 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" li jagħti Z u anki jekk kellna ġustifikazzjoni kbira għaliex intilfet l-kunsinna … il-bottom line huwa li ma kienet qed tfittex tajba — ma konniex se jagħti Z fil-forma ta 'kwalità li jagħmel xi ħadd kburi.

Jagħrfu din, aħna marru għall-ġestjoni u qaltilhom li l-baġit tal-proġett se jiġi kkunsmat minn ċerta data u li konna fl-inkwiet mal Z.

A firestorm mini faqqa matul il-jiem li ġejjin.

Jum 1: Tim ta 'Ġestjoni sejħiet fil-persunal tagħha għal laqgħa speċjali (aħna, l-konsulenti ma jkunux mistiedna). 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" huwa * attwalment użati *, but you get the picture. We’re a tight-knit group, wara kollox, u l-istaff ilha taħdem magħna konsulenti jum fi u barra għal diversi xhur issa.

Jum 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: iskeda laqgħa mat-tim implimentazzjoni sħiħa (inklużi konsulenti).

Jum 5: Tim sħiħ jissodisfa, 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.

Jekk kellna stenniet sa biss tliet ġimgħat baqgħu, jew saħansitra agħar, ġimgħa jew ġimgħatejn, it would have been much different. Instead of a constructive meeting to re-align the project, aħna kienu ġbid rapporti ta 'status, parsing the contract and reviewing old emails to justify this or that decision. We would have "won" but is it really "winning" f'dan il-każ?

Allura, jekk inti għandek tagħti aħbar ħażina, give it early. Bad news given late isn’t just bad, huwa horrible.

Jużaw “Persuna jew grupp” fil-kolonna kkalkulata

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

Bottom line, dan ma taħdimx fl WSS 3.0 (jew MOSS).

Meta tiżdied kolonna kkalkulata, 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, hija jgħidlek:

Wieħed jew aktar referenzi kolonna mhumiex permessi, minħabba li l-kolonni huma definiti bħala tip ta 'data li mhijiex appoġġjata fil-formuli.

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

Links utli dwar oqsma kkalkulati b'mod ġenerali:

Quick disclaimer: Nemmen li l-hawn fuq biex ikunu vera u preċiża, imma stajt tidher tricks għaqlija biżżejjed hawn u hemm fil MOSS / WSS li jien mhux se jkun estremament sorpriż (agog jekk inti se) 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, jekk jogħġbok let me know!

MOSS / WSS jgħidlekx me: “Il-paġna ġiet modifikata mill-awtur ieħor …” imma attwalment, ma kienx.

We did some heavy duty re-organizing of our site taxonomy via "Manage Content and Structure". For reasons unknown to me, dan il-proċess (għalkemm jaħdmu fil-prinċipali) broke some navigation links in the quick launch. The broken links are characterized by:

  • Wrong URL. Per eżempju, it should be "/sites/departments/HumanResources/…". Madankollu, the new link is "/sites/Corporate/HumanResources/…".
  • Ripetuti bits fuq il-sekwenza mistoqsija tal-intestatura, kif fil-:

/siti / dipartimenti / HumanResources / _layouts / viewlsts.aspx?BaseType = 0?BaseType = 0?BaseType = 0?BaseType = 0

That’s easy enough to fix via site settings/navigation. Except, MOSS jippreżenta lili ma dan meta I tipprova tagħmel dan:

immaġni

Il-fatt hu, ebda waħda qed tagħmel kull bidla hemm (apparti minn me, tal-kors).

A quick tfittxija dawriet up dan forums diskussjoni MSDN: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1691577&SiteID=1

William Heurdier jistipula out nicely fil-l ta 'qabel (bħala ta ' 10/02/07) post:

Fatt huwa:

Għal reset intestaturi korrotta, inti għandek :

– tneħħi l-listi taħt l-intestatura korrotta

– neħħi korrotta intestatura

– Mill-issettjar lista, add a removed list to the quick launch (Dan riġenerat intestatura non korrotta)

Inti mbagħad tajba biex tmur….


Sharepoint Espert – Sogeti Cap Gemini Isvizzera

I kien daqsxejn konfuż minħabba I tinżamm jixtiequ li jmorru għall-paġna ta 'navigazzjoni, make the change and then get hit with the "page was modified" message. Eventwalment, 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!

</aħħar>

Abbona għall-blog tiegħi!

Problemi bil “Pause Sa Data” attività workflows SPD-maħluqa

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

Sfond:

Għandna rekwiżit tan-negozju fejn manager inġinerija ambjent jeħtieġ li tiżgura li 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 (jew assistent tagħha) enters all the required permits and reminder dates at the start of the year. The system then does all the heavy lifting.

Ambjent:

MOSS, 64 bit, ambjent magna virtwali (kaxxa iżvilupp), 2 servers (SQL fuq server #1, kull ħaġa oħra fuq server #2).

Problemi:

The Pause Until Date action seems like the perfect solution and it may well prove itself to be. Madankollu, ma jaħdimx sew barra mill-kaxxa (għalina).

  1. Ix-xogħol workflow kienx skedat jiddekorri, ever. I discovered this by reading through Christopher White Paper (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:\>

    Dan kien riżultat sorprendenti imma jissolvew faċilment:

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

    Operazzjoni kompluta b'suċċess.

    C:\>

    Malli tagħmel dan, the first "In Progress" workflow malajr fired up u ma impjieg huwa.

  2. Sfortunatament, the next one didn’t work as expected. Thankfully, Christopher refers us hawn (http://support.microsoft.com/kb/932816). As of writing of this entry, aħna qed jistennew għall-dipartiment IT sabiex tikseb dan hotfix, but it does look promising. Our copies of the affected .dll’s do not share the same byte size, hekk nisperaw li dan se ssolvi l-problema.

Workaround:

Re-running the stsadm -o setproperty command seemed to prod the workflow timer awake. It would, bejn wieħed u ieħor 7 minuti wara, actually wake up and continue along with the workflow.

Mistoqsijiet / Kwistjonijiet indirizzati:

Pause Sa Data ma taħdimx.

Pause Sa Data ma jerġa 'jibda.

Workflow status does not change from "In Progress"

Workflow status stays "In Progress"