Ningunha sopa para ti! Cisco é o nazi da sopa de NLB produtos?

Hoxe, 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. (Se / cando os asistentes de rede me dicir o que é, Vou actualizar este post).

Windows explorer couldn’t connect. I did some research and eventually, os asistentes de rede, dixo que WebDAV é desactivada por / non é soportado polo / beneath the dignity of the NLB.

Así, assuming the network wizards aren’t just telling me the network wizard equivalent of "take a long walk off a short bridge", Eu teño que saber — fai NLB, por natureza, desactivar o WebDAV? Do we lose our windows file explorer interface to SharePoint? Is Cisco the Soup Nazi?

Xestionar Moss / Ambientes WSS — mantendo-se coa base de coñecemento de 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.

Eu segue ata a velocidade con eles a través dun servizo solicitado polos pobos bos en 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.

Política de Aplicación web, Sitios de seguridade ea seguridade de corte — Coñeza a súa configuración

(Actualizado 11/29 para explicar como acceder a configuración de directiva de aplicación web a través da interface de usuario)

I had one of those "why is MOSS doing this to me????" moments today. A finais, é todo culpa miña.

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. Vaia á páxina web.
  2. Rompe a herdanza de seguridade.
  3. Eliminar todos os usuarios / grupo de permisos da web.

O anterior debe deixar só o administrador do conxunto de sitios web con permiso para ver o sitio web.

Se alguén fai login, deben deixar de ver o sitio e debe ser aparado de seguridade de todas as partes habituais.

Pero … non era. Á vez, 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, finalmente, Eu creo que a Blog de Ethan, his opening graph makes it quite simple:

Moss 2007 ten un novo recurso chamado Política de aplicacións web. Estas son os permisos de seguridade que está vinculada a unha aplicación web. Estas opcións de seguridade substituír calquera configuración de seguridade que está definido no conxunto de sitios web ou sitio web (Tea) nivel para o usuario.

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, pero, estirar unha cita, "It does not mean what you think it means."

Access web application policies this way:

  1. Vaia á Administración Central
  2. Seleccione Xestión de Aplicacións
  3. Select "Policy for Web Application"
  4. Nesa pantalla, make sure you pick the correct web application. Para min, o defecto é a aplicación web de administración central, que pode non ser o que quere.

Cando eu tiven ese problema, Procurei as frases seguintes e ten moi pouco en termos de axuda directa sobre esta cuestión:

Accións da web visibles para todos os usuarios

Accións da web visibles para todos os usuarios

accións do sitio de seguridade non son aparadas

protexer un sitio Moss

introdución ao musgo de seguridade

Technorati Tags:

Rápido e sinxelo: Use palabras clave Consulta fixo en principais resultados da investigación

Instrucións rápidas e sinxelas:

Editar unha páxina e engadir un Search Core Results web Part.

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

Engadir a consulta contrasinal fixo (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").

Notas:

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: Departamentos e Produtos.

O conxunto de sitios produto contén, por suposto, product information. Each product in the site collection aggregates data from multiple sources.

Un dos departamentos, códigos e de probas, 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".

Un gran beneficio deste enfoque: We can edit the XSL from the core search results web part and generate any format that we want.

Vexa aquí (http://devcow.com/blogs/jdattis/archive/2007/04/17/SharePoint_2007_How_to_Rollup_Content_from_multiple_Site_Collections.aspx) para debate outro blogueiro sobre este tema.

</final>Rexístrate para o meu blog.

Diga-me sobre o seu blog!

Se mantén un blog que é, polo menos, mínimamente ligado ao SharePoint, please let me know in comments. I would love to add you to my lista de blogs.

Se mantén un blog que non está ligado ao SharePoint, pero quere que eu engadir lo de calquera xeito, deixe-me saber. I’ll may create a separate blog list.

Por favor, indique:

  • A súa URL do seu blog (obviamente)
  • Unha breve descrición do seu 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.

Grazas!

Horario empregado Formación e Obras Template — Decremento erro no modelo

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

Course managers create courses. When creating a course, o director especifica o número máximo de prazas dispoñibles.

The template provides for self-service enrollment. I enroll and a workflow attached to the registration list decrements the "available seats" asociado co referido curso.

Individuals may also unregister from a course. The bug lies here. Unregistering from a course does not increment the available seats counter. Como resultado, available seats is not accurate. This bug is compounded by the fact that when available seats decrements to zero, non o rexistro de autoservizo se permite.

Afortunadamente, Microsoft provides the workflow for this process. Even better, é un fluxo de traballo simple e directa creada a través do SharePoint Design.

Siga estes pasos de alto nivel para resolve-lo:

  1. Lume ata SDP.
  2. Acceda ao sitio web baseado fóra do modelo de formación.
  3. Access "Attendee unregistration" fluxo de traballo.
  4. Insire estes pasos (Eu fixen as dúas primeiras etapas):
    1. Calcular Cursos:Asentos ocupados menos 1 (Saída Variable:Calc)
    2. (entón) Actualizar elemento en Cursos

Fai clic en Finalizar e listo.

As capturas de pantalla:


SharePoint Deseño:

imaxe

Fluxo de traballo rematou:

imaxe

Calcule Drill-down:

imaxe

Actualizar elemento Cursos:

imaxe

Deixa unha boa nova frecuentemente; dar unha mala noticia cedo

Eu fun un consultor para unha morea de anos e como calquera consultor experimentado sabe, good communication is one of the key pillars to the successful delivery of a project. É tan obvio, it’s really almost boring to talk about. This isn’t a post about generic communication. Pola, Eu estou escribindo sobre o lado máis sombrío de comunicación — comunicación de malas novas.

Nin que dicir ten que dar unha boa nova para o cliente está feito todo o tempo, as often as possible. Who doesn’t want to give good news? Who doesn’t like to hear good news?

Por outra banda, bad news is no fun at all. I have always struggled with this. In the earlier days of my career, Gustaríame saber algo estaba mal con un proxecto e, en vez de dicir ao cliente, 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 para 80 horas á semana?

Cal é a mellor forma de xestionar malas novas? 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 (probablemente ha), there may be incriminations and accusations and hurt feelings. Pero, cando as emocións refrescar, there’s still six weeks left on the project. Six weeks is a good chunk of time. There’s time to adjust plans, cambiar horarios, a bola rolar en ampliación do orzamento (boa sorte!) and just generally come to grips with the "facts on the ground" and devise a new plan that still results in a successful project.

Caso en cuestión: Eu estou traballando nun proxecto caracterizado por:

  • T&E budget with a capped "Not to exceed" valor en dólar.
  • A "best efforts will be made" promesa de entregar X, Y e Z ata o final do proxecto.
  • Lack of promised key resources on the client side. These resources were not withheld on purpose, nor for any "bad" razón, pero eles foron retidos.
  • A dawning realization as the project passed the half-way point that we were not going to be able to deliver "Z" (sobre todo porque os recursos comprometidos non foron realmente dispoñible).
  • Regular status reports and "CYA" documentación que apoiou nos (o equipo de consultoría) up.
  • Equipo de implementación ções con membros procedentes da empresa de consultoría (a miña empresa) eo cliente.
  • Equipo de xestión lonxe, in both a metaphorical and physical sense. The management team was focused on another large enterprise project and due to space constraints, o equipo de implementación foi aloxado nun edificio separado no campus, down a hill and relatively far way from "civilization".

Con preto de seis semanas que restan no orzamento do proxecto, nós (o equipo de implementación) 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" para entregar Z e aínda que tivo gran xustificación para a falta de entrega … a liña de fondo é que non estaba mirando bo — non estabamos indo entregar Z en forma de calidade que faría calquera orgulloso.

Recoñecendo esta, fomos para a xestión e díxolles que o orzamento do proxecto sería consumida por unha determinada data e que estabamos en apuros con Z.

Un mini-treboadas estalou nos próximos días.

Día 1: Equipo de xestión chama no seu equipo para unha reunión especial (nós, os consultores non son convidados). 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 "Síndrome de Estocolmo" é * realmente * usado, pero comeza a foto. We’re a tight-knit group, ao final, eo equipo vén traballando connosco día consultores dentro e fóra hai varios meses.

Día 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: axenda unha reunión co equipo de implementación integral (Consultoría, incluíndo).

Día 5: Equipo completo atopa, 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.

Se tivese esperado ata tres semanas permaneceu, ou peor aínda, unha ou dúas semanas, it would have been much different. Instead of a constructive meeting to re-align the project, teriamos sido tirar informes de estado, parsing the contract and reviewing old emails to justify this or that decision. We would have "won" but is it really "winning" neste caso?

Así, se ten que dar malas novas, give it early. Bad news given late isn’t just bad, é horríbel.

Uso “Persoa ou grupo” nunha columna calculada

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

Bottom line, isto non funciona en WSS 3.0 (ou Moss).

Engadindo unha columna calculada, 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, dille:

Un ou máis referencias de columnas non son permitidas, por que as columnas son definidas como un tipo de datos que non é soportado en fórmulas.

Resolución: 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.

Ligazóns útiles en campos calculados en xeral:

AVISO LEGAL rápida: Eu creo que o anterior para ser certas e precisas, pero xa vin o suficiente trucos intelixentes aquí e alí en Moss / WSS que eu non sería moi sorprendido (curioso se quere) 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, por favor me aviso!

Moss / WSS dime: “A páxina foi modificada por outro autor …” pero en realidade, non era.

We did some heavy duty re-organizing of our site taxonomy via "Manage Content and Structure". For reasons unknown to me, este proceso (a pesar de traballar no esencial) broke some navigation links in the quick launch. The broken links are characterized by:

  • Wrong URL. Por exemplo, it should be "/sites/departments/HumanResources/…". Con todo, the new link is "/sites/Corporate/HumanResources/…".
  • Anacos repetido na secuencia de consulta do título, como no:

/locais / departamentos / HumanResources / _layouts / viewlsts.aspx?BaseType=0?BaseType=0?BaseType=0?BaseType=0

That’s easy enough to fix via site settings/navigation. Except, Moss me preséntase con iso cando eu tentar facelo:

imaxe

O feito é, ninguén está a facer calquera modificación non (ademais de me, claro).

Unha rápida procura transfórmase este MSDN foros de debate: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1691577&SiteID=1

William Heurdier coloca-lo ben no penúltimo (a partir de 10/02/07) publicar:

Feito é:

Para restaurar títulos corrompidos, ten que :

– eliminar todas as roldas baixo corrupto título

– eliminar corrupto título

– A partir das definicións da lista, add a removed list to the quick launch (Este rexenerar un non corrupto título)

Está, entón, preparado para ir….


Sharepoint especialista – Cap Gemini Sogeti Suíza

Eu estaba un pouco confuso, porque eu seguía querendo ir á páxina de navegación, make the change and then get hit with the "page was modified" message. Eventualmente, 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!

</final>

Rexístrate para o meu blog!

Problemas coa “Pausa Ata Data” actividade en fluxos de traballo SPD-creados

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

Fondo:

We have a business requirement where an environmental engineering manager needs to ensure that 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 (or her assistant) enters all the required permits and reminder dates at the start of the year. The system then does all the heavy lifting.

Environment:

Moss, 64 bocado, virtual machine environment (development box), 2 servers (SQL on server #1, everything else on server #2).

Problems:

The Pause Until Date action seems like the perfect solution and it may well prove itself to be. Con todo, it does not work well out of the box (for us).

  1. The workflow job was not scheduled to run, ever. I discovered this by reading through Christopher White’s (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:\>

    That was a surprising result but easily solved:

    C:\>stsadm -o setproperty -propertyname "job-worfklow" -propertyvalue "every 1 minutes between 0 e 59" -url http://localhost

    Operation completed successfully.

    C:\>

    Upon doing that, the first "In Progress" workflow quickly fired up and did it’s job.

  2. Desafortunadamente, the next one didn’t work as expected. Agradecidamente, Christopher refers us aquí (http://support.microsoft.com/kb/932816). As of writing of this entry, we’re waiting for the IT department to obtain that hotfix, but it does look promising. Our copies of the affected .dll’s do not share the same byte size, so hopefully this will solve the problem.

Resolución:

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

Questions / Issues Addressed:

Pause Until Date does not work.

Pause Until Date does not resume.

Workflow status does not change from "In Progress"

Workflow status stays "In Progress"