Jouledoc Notes on Web

Hiding “View all site content” on the Quick Launch Bar

<style>
.ms-quicklaunchheader{display: none;}
</style>

Powered by ScribeFire.

Share This

Consider the following scenarios that occur when you upgrade Microsoft Windows SharePoint Services 2.0 or Microsoft Windows SharePoint Services 3.0:

Share This

Use the Packages feature to export and to import a Windows SharePoint Services Web site

You can use the Packages feature to move a Web site as empty content. When a Web site is moved as empty content, list data that is part of the original Web site does not move with the Web pages in the package. However, documents in a document library are packaged and will be moved with the Web pages in the package.

To use the Packages feature to move a Windows SharePoint Services Web site from one server to another, follow these steps:

Read the rest of this entry »

Share This

dim dayweekdim strBackup dayweek = datepart("w",(date)) strBackup = """C:Program FilesCommon FilesMicrosoft Sharedweb server extensions60BINstsadm""" + _

"-o backup -url http://companyweb -filename x:backupscompanyweb" + cstr(dayweek) + ".dat -overwrite"

 Set WshShell = WScript.CreateObject("WScript.Shell") Return = WshShell.Run(strBackup, 0, true) Set WshShell = Nothing

To add this script as a scheduled task, follow these steps:

Powered by ScribeFire.

Share This

To turn on Windows SharePoint Services usage logging in an Office
SharePoint Server farm, you must first turn on Usage Analysis
Processing in Windows SharePoint Services 3.0, and then turn on
Advanced Usage Analysis Reporting service in Shared Services
Administration. To do this, follow these steps:

Powered by ScribeFire.

Share This

Thank
you for your suggestion. I did as you suggested, and stopped the
Windows SharePoint Services Search. When I did the standard search, it
worked normally. When I did the Search: This Site, I got a message I
had not gotten before…. It was

Your search cannot be completed because this site is not assigned to an indexer.

I
restarted the SharePoint Services Search, but still got the same
error. So I looked up what I needed to check to verify my Indexer
settings and found the following: “To start it, you have to visit your
content database in Central Admin Application Management. In the SharePoint Web Application Management section, click on Content Databases. This should expose your content database for the farm.”

So
I did just that. I went to Application Management on the Central
Administration site and clicked on Content Databases. I saw my
database; WSS_Content and clicked on it to view the settings. Sure
enough, the Search Server (Indexer) was not selected. I chose my index
server (my only SP server) and clicked OK. I retried the Search: This
Site, and got a message that there were no results to be found!!! Woo
Hoo!!! No error message!!!

I
stopped and restarted my Content Crawls by going to Shared Services
Admin>Shared Services>Search Settings (under Search)>Content
sources and crawl schedules. I have 3 sources; the SP server and
sites, a shared folders directory, and the Exchange Public Folders
directory. I stopped and started the crawl on all 3 and then tried the
Search: This Site once again…… Success!!!! I am getting search
results now.

Unfortunately,
I do not know if this was the actual root cause of the problem I was
experiencing with the Search: This Site function. I had not been
getting an Indexer error previously. This one is a head
scratcher….. I am glad it is working though.

Powered by ScribeFire.

Share This

taken from http://workerthread.wordpress.com/2008/01/03/configure-pdf-ifilter-in-wss-30/

There are various posts around on setting up MOSS 2007 to use the
PDF IFilter, and some stuff on Windows SharePoint Services 3.0 as
well. I’ve found a method which works for me, so I wanted to put this
together in one place - not least of all so I can find it when out on
site with a client.

Out of the box neither WSS 3 nor MOSS 2007 will index content
located in Acrobat PDF files, so you need to set up the IFilter. I’ve
also found that that PDF files loaded prior to the installation of the
filter won’t be re-crawled automatically, so to be on the safe side you
might want to kick off a full crawl.

Here is what I’ve found works for WSS 3.0:

1. First, you need to download the Adobe PDF IFilter 6.0, which you can find at this URL.
   You should also get hold of a suitable Icon to use with PDFs, so that
   when they are listed in a document library they are easily
   recognisable. There is a 17 x 17 one available on the Adobe web site here.
2. Once you’ve downloaded the IFilter, install it on your WSS 3.0 server, and then follow the instructions on registry settings in Microsoft KB Article 927675.
   I’ve always found that providing the Adobe IFilter installed properly,
   the only setting I need to add is the Search Extensions one listed in
   step 2. Also note step 5 re stopping and re-starting the search
   service.
3. Now you need to set up the Icon file. If you downloaded the
   icon file in step 1 above, you will have a file called
   pdficon_small.gif. You need to copy this onto your WSS 3.0 server,
   into drive:\Program Files\Common FIles\Microsoft Shared\Web Server
   extensions\12\TEMPLATE\IMAGES.
4. Next you need to edit the XML file which WSS uses to link
   file extensions to icons. This file is called DOCICON.XML and is
   located at drive:\Program Files\Common FIles\Microsoft Shared\Web
   Server extensions\12\TEMPLATE\XML. Navigate to that folder and locate
   the file. I would suggest making a backup copy first, then opening the
   file in NotePad. You need to add a mapping key for PDFs at the bottom
   of the file, above the </ByExtension> closing tag. The new key
   will be <Mapping Key=”pdf” Value=”pdficon_small.gif” OpenControl=””/> (note that XML is case sensitive so make sure you use same case as previous entries). Then save the file.
5. That’s pretty much it, but if you already have PDFs uploaded
   to your WSS server I would recommend starting a full crawl. You can do
   the with STSAdm, the command syntax is Stsadm -o spsearch -action fullcrawlstart . More on this on TechNet here.

Powered by ScribeFire.

Share This

Oleh Anita
Yossihara

Beberapa ibu
rumah tangga sibuk menata kue di rumah Nuriah (40) di
Kampung Cidemang,
Kelurahan Pandeglang, Kabupaten Pandeglang, Banten,
Selasa (15/1) siang.
Ibu-ibu itu menyiapkan makanan untuk acara doa
bersama berkait meninggalnya
Slamet (45), suami Nuriah.

Sehari sebelumnya, suami Nuriah nekat gantung
diri hingga tewas di
sebuah kamar kosong di rumahnya. Jasad Slamet pertama
kali ditemukan
oleh istrinya yang baru pulang dari berbelanja di Pasar
Badak,
Pandeglang. Tubuh ayah empat anak itu sudah menggantung di
tengah
kamar, dengan seutas tali plastik melilit di
lehernya.

Read the rest of this entry »

Share This

Berikut adalah beberapa script log parser yang akan sering digunakan, untuk hasil reporting.

• Checking Jenis Browser yang akses web server

Select top 50 to_int(mul(100.0,PropCount(*))) as Percent, count(*) as TotalHits, cs(User-Agent) as Browserfrom [LogFileName]group by Browserorder by Totalhits desc

• Melihat total bandwidth harian yang ada di web server

Select To_String(To_timestamp(date, time), ‘MM-dd’) As Day, Div(Sum(cs-bytes),1024) As Incoming(K), Div(Sum(sc-bytes),1024) As Outgoing(K)From [LogFileName]Into BandwidthByDay.gifGroup By Day

• Total Hits per Hours

SELECT QUANTIZE(TO_LOCALTIME(TO_TIMESTAMP(date,time)),3600) As Hour, cs-uri-stem As Url, COUNT(*) As HitsFROM [LogFileName]WHERE cs-uri-stem LIKE ‘%index.htm%’GROUP BY Url, HourORDER By Url

• Request by URI

SELECT top 80

QUANTIZE(TO_TIMESTAMP(date, time), 3600) as Hour,
TO_LOWERCASE(STRCAT(’/',EXTRACT_TOKEN(cs-uri-stem,1,’/'))) as URI,
COUNT(*) AS RequestsPerHour,
SUM(sc-bytes) AS TotBytesSent,
AVG(sc-bytes) AS AvgBytesSent,
Max(sc-bytes) AS MaxBytesSent,
ADD(1,DIV(Avg(time-taken),1000)) AS AvgTime,
ADD(1,DIV(MAX(time-taken),1000)) AS MaxTime

FROM [LogFileName]
GROUP BY Hour, URI
Having RequestsPerHour > 10
ORDER BY RequestsPerHour ASC

• Top 10 Images by size

Select Top 10 StrCat(Extract_Path(TO_Lowercase(cs-uri-stem)),’/') AS RequestedPath, Extract_filename(To_Lowercase(cs-uri-stem)) As RequestedFile, Count(*) AS Hits, Max(time-taken) As MaxTime, Avg(time-taken) As AvgTime, Max(sc-bytes) As BytesSentFrom [LogFileName]Where (Extract_Extension(To_Lowercase(cs-uri-stem)) IN (’gif’;'jpg’;'png’)) AND (sc-status = 200)Group By To_Lowercase(cs-uri-stem)Order By BytesSent, Hits, MaxTime DESC

• Top 20 clients yang akses ke webserver

Select Top 20 c-ip AS Client, Count(*) AS HitsINTO Chart.gifFROM [LogFileName]GROUP BY c-ipORDER BY Hits Desc

• Waktu yang dibutuhkan untuk load virtual directory

SELECT CASE EXTRACT_TOKEN(cs-uri-stem, 2, ‘/’) WHEN NULL THEN ‘/’ ELSE EXTRACT_PREFIX(cs-uri-stem, 1, ‘/’) END As VDir, QUANTIZE(time-taken, 100) As TimeTaken, COUNT(*) As NumHits
FROM [LogFileName]
GROUP BY TimeTaken, VDirORDER BY TimeTaken, VDir DESC
SELECT CASE EXTRACT_TOKEN(cs-uri-stem, 2, ‘/’) WHEN NULL THEN ‘/’ ELSE EXTRACT_PREFIX(cs-uri-stem, 1, ‘/’) END As VDir, QUANTIZE(time-taken, 100) As TimeTaken, COUNT(*) As NumHits
FROM ex05111606.log
GROUP BY TimeTaken, VDirORDER BY TimeTaken, VDir DESC

Powered by ScribeFire.

Share This

Hm mungkin agak telat untuk membahas apa itu Log Parser namun gak ada salahnya untuk di buat my sticky note
Versi terbaru log parser adalah versi Log Parser 2.2 bisa di download di www.logparser.com
Kelebihan dari Log Parser adalah kemampuannya untuk membaca log file pada windows yaitu Event Log, Registry,file system, IIS LOG dan Active Directory lalu menampilkan kembali dalam berbagai macam format seperti file XML, file CSV, HTML dan Chart.

proses untuk membaca dari log file atau lebih dikenal sebagai scripting menggunakan syntax SQL seperti contoh ini:

LogParser “SELECT TimeGenerated, SourceName, EventID, Message INTO Events.xml FROM System”

dan hasilnya akan di tampilkan dalam format XML.

download disini

Powered by ScribeFire.

Share This