Matul il-ġimgħa li għaddiet, tiegħi kollega and I were doing some work for a client in NYC. We were testing a different aspects of a MOSS implementation using their "standard" workstation jibnu (għall-kuntrarju laptops tagħna). While doing that, aħna dam fis ftit żbalji minn dawn il-passi:

• Tiftaħ dokument kelma SM permezz ta 'twieqi Explorer (li juża WebDAV).
• Tagħmel bidla.
• Ħlief dan.

Aħna daħal li tirrealizza li xi drabi (normalment l-ewwel darba) aħna salvati id-dokument, the save didn’t "stick." Save did not save. We would pull that document back up and our changes simply were not there.

Aħna ma fehmux il-kwistjoni għerq f'dan il-punt, 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, aħna issa ltqajna dan l-iżball:

Din id-darba, deher simili kull bidla kienet, fil-fatt, salvat, whether we answered Yes or No to the scripts question.

Aħna finalment kellhom ħarsa lejn l-verżjoni attwali ta 'Uffiċċju u jirriżulta li l-workstation kien għaddej MS Office 2000 b'unità tas-servizz 3 li turi up taħt Help -> About as "Office 2002".

Il-morali ta 'l-istorja: I dejjem se jużaw Office 2003 bħala minimu verżjoni tiegħi uffiċċju linja bażi meta jużaw WebDAV u MOSS.

</aħħar>

Abbona għall-blog tiegħi.

(Għal skopijiet search engine, dan huwa test l-iżball tal-):

Linja: 11807

Char: 2

Error: Għan ma jappoġġax din il-proprjetà jew il-metodu

Kodiċi; 0

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

Do inti tixtieq li tkompli taħdem skripts fuq din il-paġna?

In one or my very first blog posts, I deskritt-proċess ġenerali aħna segwit biex jemigraw klijent mill SPS 2003 to MOSS. A reader left a comment asking for more detail and here it is.

Għal dak il-proġett migrazzjoni, aħna kellha ssib mod tajjeb biex jimxu ħafna 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. Barra minn, let’s assume there are hundreds of documents (maybe thousands) 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. Minflok, they will break that out over a period of weeks or possibly longer. To facilitate this process, we can create an "untagged data" tara kif jidher:

Issa, meta xi ħadd tiltaqa stabbiliti biex jonfqu siegħa kuljum allokat tagħhom jew tnejn biex tag dokumenti emigraw, they can use the "untagged documents" ħsieb li tiffoka l-isforz tagħhom:

Bħala dokumenti tag utenti, dawn qatra off din il-lista.

This notion of an untagged data view can also help with a class of data validation problem people inquire about on the forums. Barra mill-kaxxa, 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. Madankollu, jekk l-uploads utent u mbagħad jagħlaq il-browser (jew użi twieqi Explorer biex ittella 'dokument), ma nistgħux seħħ il-utent biex jidħol meta data (darb'oħra, barra mill-kaxxa).

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.

</aħħar>

Abbona għall-blog tiegħi.

Din il-ġimgħa, I’ve struggled a bit with my team to get MOSS installed in a simple two-server farm. Having gone through it, I ikollhom apprezzament akbar għall-tip ta 'problemi nies tirrapporta dwar l-forums MSDN u bnadi oħra.

Il-konfigurazzjoni farm finali:

• SQL / Indiċi / Intranet WFE ġewwa l-firewall.
• WFE fil-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.

F'dan il-punt, we discovered the confusion over the SSL certificate and, sfortunatament, decided to have our infrastructure guy come back later that week to continue installing the DMZ server. Fil-ħin medju, 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, wara kollox, 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" status.

Long storja qasira, 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.

</aħħar>

Abbona għall-blog tiegħi.

Għalkemm mhuwiex litteralment veru, bħala kwistjoni prattiku, internet li jħarsu web tarf ta 'quddiem fil-DMZ għandu jkun fil-dominju (I.E. mhux xi server standalone fil workgroup ftit tagħha stess). It doesn’t need to be in the same domain as the internal WFE(i) u servers oħra (u probabbilment m'għandhomx), iżda jeħtieġ li jkun dominju.

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. Sfortunatament, aħna naqset li tiżdied sentenza x'imkien li qal, l-effett, "the whole bloody point of this configuration is to allow your DMZ WFE server, f'qasam, biex jissieħbu fl-farm intern."

A maltempata perfetta ta 'avvenimenti, fejn aħna bażikament ħares xellug meta aħna jista ħarsu dritt, conspired biex jaħbu din il-problema minna sakemm pjuttost tard fil-proċess, b'hekk jiġi evitat me milli jinvoka tiegħi "tell aħbar ħażina kmieni" regola.

Daqqa.

Abbona għall-blog tiegħi.