I rith na seachtaine seo caite, mo chomhghleacaí and I were doing some work for a client in NYC. We were testing a different aspects of a MOSS implementation using their "standard" stáisiún oibre a thógáil (le hais ár ríomhairí glúine). While doing that, ar siúl againn i roinnt earráidí a leanas ag na céimeanna:

• Oscail cáipéis focal MS via fuinneoga taiscéalaí (a úsáideann WebDAV).
• Dhéanamh ar athrú.
• Sábháil sé.

Tháinig muid a thuiscint go bhfuil roinnt uaireanta (de ghnáth ar an chéad uair) shábháil againn an doiciméad, the save didn’t "stick." Save did not save. We would pull that document back up and our changes simply were not there.

Ní raibh muid a thuiscint an cheist fréimhe ag an bpointe seo, but we figured that we should make sure that the latest MS Office service pack had been installed on that work station. The IT folks went and did that. We went through the test again and we discovered a new problem. When we saved it, fuair muid anois an earráid seo:

An uair seo, dhealraigh sé cosúil go raibh gach athrú, i ndáiríre, shábháil, whether we answered Yes or No to the scripts question.

Bhí orainn ar deireadh le breathnú ar an leagan iarbhír na hOifige agus casadh sé amach go raibh an stáisiún oibre rith MS Oifig 2000 le seirbhís pacáiste 3 a léiríonn suas faoi Cabhair -> About as "Office 2002".

An mhorálta an scéal: Beidh mé úsáid i gcónaí Oifig 2003 mar mo leagan oifig bonnlíne íosta nuair a úsáid WebDAV agus CAONAIGH.

</deireadh>

Liostáil le mo bhlag.

(Chun críocha inneall cuardaigh, Tá an téacs seo an earráid a):

Líne: 11807

Ruabhreac: 2

Earráid: Ní Réad tacú leis an maoin nó modh

Cód; 0

URL: http://sharepoint01/DocumentReview/_vti_bin/owssvr.dll?location=Documents/1210/testworddocument.doc&dialogview=SaveForm

Ar mhaith leat dul ar aghaidh scripteanna a reáchtáil ar an leathanach seo?

In one or my very first blog posts, Mé cur síos ar an bpróiseas foriomlán lean muid ag dul ar imirce le custaiméir ó SPS 2003 to MOSS. A reader left a comment asking for more detail and here it is.

Ar an ábhar sin tionscadal imirce, bhí againn a fháil ar bhealach maith chun bogadh a lán de na SPS 2003 documents over to MOSS. The initial load was easy enough. Create a new target document library in MOSS and use windows explorer to move the documents.

This is the new document library:

Open up two windows explorers. Point the first at SPS 2003 and the second at the new document library in MOSS. The following screen shot shows this. Note that the top browser is actually pointing at my c:\temp drive, but you can imagine it pointing to an SPS 2003 document library:

After that drag and drop operation, my target looks like this:

Now it’s time to deal with the metadata. Assume we have just one column of metadata for these documents named "location." We can see from the above "all documents" view that the location is blank. It’s easy enough to use a data sheet view to enter the location, or even go into each document’s properties one by one to add a location. Let’s assume that there is no practical way to assign the location column a value automatically and that end users must do this by hand. Furthermore, ligean ar glacadh leis go bhfuil na céadta de dhoiciméid (b'fhéidir na mílte) and that it will take many many days to update the metadata. As we all know, no one is going to sit down and work for four of five days straight updating meta data for documents. Ina áit sin, they will break that out over a period of weeks or possibly longer. To facilitate this process, we can create an "untagged data" view as shown:

Anois, when someone sits down to spend their allocated daily hour or two to tag migrated documents, they can use the "untagged documents" view to focus their effort:

As users tag documents, they drop off this list.

This notion of an untagged data view can also help with a class of data validation problem people inquire about on the forums. As an bosca, there’s no way to prevent a user from uploading a document to MOSS and then not enter meta data. We can specify that a particular site column is mandatory and the user won’t be allowed to push the save button. Mar sin féin, if the user uploads and then closes the browser (or uses windows explorer to upload the document), we can’t force the user to enter meta data (arís, amach as an bhosca).

This approach can be used to help with that situation. We can use a "poorly tagged data" view to easily identify these documents and correct them. Couple this with a KPI and you have good visibility to the data with drill-down to manage these exceptional circumstances.

</deireadh>

Liostáil le mo bhlag.

An tseachtain seo, I’ve struggled a bit with my team to get MOSS installed in a simple two-server farm. Having gone through it, Tá mé tuiscint níos fearr do na cineálacha fadhbanna a thuairisciú daoine ar na fóraim MSDN agus in áiteanna eile.

An chumraíocht feirme deiridh:

• SQL / Innéacs / Inlíon WFE taobh istigh an balla dóiteáin.
• WFE i DMZ.
• Some kind of firewall between the DMZ and the internal server.

Before we started the project, we let the client know which ports needed to be open. During the give and take, back and forth over that, we never explicitly said two important things:

1. SSL means you need a certificate.
2. The DMZ server must be part of a domain.

Day one, we showed up to install MOSS and learned that the domain accounts for database and MOSS hadn’t been created. To move things along, we went ahead and installed everything with a local account on the intranet server.

Ag an bpointe seo, we discovered the confusion over the SSL certificate and, Faraor, decided to have our infrastructure guy come back later that week to continue installing the DMZ server. Idir an dá linn, we solution architects moved ahead with the business stuff.

A weekend goes by and the client obtains the certificate.

Our infrastructure guy shows up and discovers that the DMZ server is not joined to any domain (either a perimeter domain with limited trust or the intranet domain). We wasted nearly a 1/2 day on that. If we hadn’t let the missing SSL certificate bog us down, we would have discovered this earlier. Oh well….

Another day passes and the various security committees, interested parties and (not so) innocent bystanders all agree that it’s OK to join the DMZ server with the intranet domain (this is a POC, tar éis an tsaoil, not a production solution).

Infrastructure guy comes in to wrap things up. This time we successfully pass through the the modern-day gauntlet affectionately known as the "SharePoint Configuration Wizard." We have a peek in central administration and … yee haw! … DMZ server is listed in the farm. We look a little closer and realize we broke open the Champaign a mite bit early. WSS services is stuck in a "starting" stádas.

Fada scéal gearr, it turns out that we forgot to change the identity of the service account via central administration from the original local account to the new domain account. We did that, re-ran the configuration wizard and voila! We were in business.

</deireadh>

Liostáil le mo bhlag.

Cé nach bhfuil sé fíor literally, mar ábhar praiticiúil, ní mór ceann tosaigh gréasáin idirlín-os i DMZ bheith i bhfearann (i.e. Ní roinnt freastalaí standalone ina grúpa oibre beag féin). It doesn’t need to be in the same domain as the internal WFE(s) agus freastalaithe eile (agus is dócha nár chóir), ach ní mór é a bheith ina fearainn.

My colleagues and I spent an inordinate amount of time on a proposal which included SharePoint pre-requisites. This included a comprehensive list of firewall configurations that would enable the DMZ server to join the farm and so forth. Faraor, theip orainn a chur le pianbhreith áit éigin a dúirt, a mbeidh an éifeacht, "the whole bloody point of this configuration is to allow your DMZ WFE server, i bhfearann, a bheith ar an bhfeirm inmheánach."

A stoirm foirfe na n-imeachtaí, nuair a d'fhéach muid d'fhág go bunúsach nuair a d'fhéadfadh muid a d'fhéach ceart, conspired a cheilt ar an bhfadhb uainn go dtí go cothrom go déanach sa phróiseas, rud a chosc dom ó mo agairt "insint nuacht olc go luath" riail.

Osna.

Liostáil le mo bhlag.