SharePoint and Other Rants https://docs.microsoft.com/archive/blogs/joekr/feed.xml Tue, 16 Apr 2019 05:13:47 GMT en-US hourly 1 SharePoint 2013 IA - Content Taxonomy https://docs.microsoft.com/archive/blogs/joekr/sharepoint-2013-ia-content-taxonomy Mon, 04 Nov 2013 19:39:00 GMT https://blogs.msdn.microsoft.com/joekr/2013/11/04/sharepoint-2013-ia-content-taxonomy/ This first in a multi-part series on SharePoint Information Architecture focuses on the content taxonomy or IA around the logical placement of documents stored in SharePoint

 

.

 

Enjoy!

]]> Provision New User Properties in SSP https://docs.microsoft.com/archive/blogs/joekr/provision-new-user-properties-in-ssp Sun, 06 Jun 2010 11:57:14 GMT https://blogs.msdn.microsoft.com/joekr/2010/06/06/provision-new-user-properties-in-ssp/ This is more of a reminder for me to go back to later, but hopefully, it may help someone else out there.

Since I am provisioning this as part of a feature receiver scoped at the web application level, you will see the "myWebApp" provisioned accordingly,

But if you have any SPSite object, you can get the webapplication directly as a property from there.

Essentially, all I want to do is create a new user property, I can access later through the profile store.

SPWebApplication myWebApp = (SPWebApplication)properties.Feature.Parent;

   

//Set up SSP

ServerContext sc = ServerContext.GetContext(myWebApp);

 

//initialize user profile config manager object

UserProfileConfigManager upcm = new UserProfileConfigManager(sc);

 

//sample to create a new section

PropertyCollection pcol = upcm.GetPropertiesWithSection();

Property prop = pcol.Create(false);

prop.Name = "ServerRedirect";

prop.DisplayName = "Server Redirect";

prop.Type = "string";

prop.Length = 255;

prop.IsUserEditable = true;

prop.IsVisibleOnEditor = true;

prop.IsVisibleOnViewer = true;

prop.IsAlias = false;

pcol.Add(prop);

 

One thing a colleague did make sure to remind me of, was MAKE SURE YOU have provisioned your SSP or this obviously will not work!

]]> Create Document Retention MOSS 2007 – Part I https://docs.microsoft.com/archive/blogs/joekr/create-document-retention-moss-2007-part-i Fri, 04 Jun 2010 14:50:36 GMT https://blogs.msdn.microsoft.com/joekr/2010/06/04/create-document-retention-moss-2007-part-i/ I know I haven't written for quite some time and I am apologetic for that, however, this post hopefully will make up for it.

How many times have you said to yourself, I need a document retention policy inside of SharePoint 2007 regardless of what document libraries we create or documents we upload? Furthermore, I want the ability to "pause" or put on some sort of "legal hold" on a document to push out the archiving and disposal of these documents. Finally, I have quite a few content types and would like to potentially treat these with different retention policies and they may not go to any record center because we cannot ensure they are records. I have had numerous customers who have asked for this and my recent answer is oh, wait until SharePoint 2010 which they frown and say oh.

In this post, I am going to provide to you a way to turn the oh, into Ah HA!

We are going to write a series of features that will provide all of the above functionality.

Step 1:

In most solution packages you will have a fields feature and that will be simply provisioning the fields you need. In this case, we are going to write the feature.xml file like:

<?xml version="1.0" encoding="utf-8" ?>

<Feature Id="BF67889E-FBDF-40d5-A6A6-B6F9C9CE6658"

Title="MyFields"

Description="This feature provisions all fields to necessitate appropriate metadata"

Version="12.0.0.0"

Scope="Site"

xmlns="http://schemas.microsoft.com/sharepoint/">

<ElementManifests>

<ElementManifest Location="fields.xml"/>

</ElementManifests>

</Feature>

 

And the fields.xml feature like:

<?xml version="1.0" encoding="utf-8" ?>

<Elements xmlns="http://schemas.microsoft.com/sharepoint/">

<Field ID="{84027183-0549-4bfb-8601-7DDDB12EED12}"

Name="LegalHold"

SourceID="http://schemas.microsoft.com/sharepoint/v3"

StaticName="LegalHold"

Group="ABC"

Type="Boolean"

Description="Allows individual to place document on hold"

DisplayName="LegalHold">

<Default>0</Default>

</Field>

<Field ID="{DBA5FD1B-97A0-470f-89B8-EB98BC28061A}"

Name="LegalStartDate"

SourceID="http://schemas.microsoft.com/sharepoint/v3"

StaticName="LegalStartDate"

Group="ABC"

Type="DateTime"

Hidden="FALSE"

ReadOnly="TRUE"

Description="Tells record when the start of the last legal hold was"

DisplayName="Legal Start Date" />

<Field ID="{14CE4BF3-F83A-410d-A454-A12FD20A60A9}"

Name="LegalEndDate"

SourceID="http://schemas.microsoft.com/sharepoint/v3"

StaticName="LegalEndDate"

Group="ABC"

Type="DateTime"

Hidden="FALSE"

ReadOnly="TRUE"

Description="Tells record when the end of the last legal hold was"

DisplayName="Legal End Date" />

<Field ID="{DBA90AA4-B671-4c49-9ABF-C8C819DE0F13}"

Name="ArchiveDate"

SourceID="http://schemas.microsoft.com/sharepoint/v3"

StaticName="ArchiveDate"

Group="ABC"

Type="DateTime"

Hidden="FALSE"

ReadOnly="TRUE"

Description="Tells retention when to archive record"

DisplayName="Archive Date" />

<Field ID="{1D6D2CE5-ABCD-4368-829B-085D3FBE99FB}"

Name="DisposeDate"

SourceID="http://schemas.microsoft.com/sharepoint/v3"

StaticName="DisposeDate"

Group="ABC"

Type="DateTime"

Hidden="FALSE"

ReadOnly="TRUE"

Description="Tells retention when to delete the record"

DisplayName="Dispose Date" />

<Field ID="{1CDE08F2-DAF6-4449-B481-31095207A983}"

Name="NewStartDate"

SourceID="http://schemas.microsoft.com/sharepoint/v3"

StaticName="NewStartDate"

Group="ABC"

Type="DateTime"

Hidden="FALSE"

ReadOnly="TRUE"

Description="This field is used to keep track of new retention schedule based on Legal Holds"

DisplayName="New Start Date" />

<Field ID="{96AAF204-A5E0-4851-A6F4-B3235EBEA185}"

Name="_Archival"

SourceID="http://schemas.microsoft.com/sharepoint/v3"

StaticName="_Archival"

Group="ABC"

Type="Integer"

Description="(in years) how long before record get archived"

DisplayName="Archive Schedule" />

<Field ID="{67A14E20-617B-46d8-8598-433782CC9E4E}"

Name="_Disposal"

SourceID="http://schemas.microsoft.com/sharepoint/v3"

StaticName="_Disposal"

Group="ABC"

Type="Integer"

Description="(in years) how long before record get deleted"

DisplayName="Dispose Date" />

<Field ID="{2A8BB895-2D13-4300-BF67-487A82BA00AD}"

Name="_Archived"

SourceID="http://schemas.microsoft.com/sharepoint/v3"

StaticName="_Archived"

Group="ABC"

Type="Boolean"

Hidden="FALSE"

ReadOnly="TRUE"

Description="Is record in archive status"

DisplayName="Archived">

<Default>0</Default>

</Field>

</Elements>

 

Step 2:

The first feature is going to be scoped at a "Site" level and will extend the document library content type by adding the necessary fields needed to make this work.

I will call this feature LegalHold and I will simply point to a feature activation receiver.

The feature.xml file will look something like:

<?xml version="1.0" encoding="utf-8" ?>

<Feature Id="38B5399F-4DAB-4938-8F92-B474A319F9B2"

Title="Legal Holds"

Description="This feature provides an extension to the document content type to allow for legal holds"

Version="12.0.0.0"

Scope="Site"

ReceiverAssembly="MyNameSpace.Features, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f6e07d4bee530c01"

ReceiverClass="MyNameSpace.Features.LegalHoldFeatureReceiver" xmlns="http://schemas.microsoft.com/sharepoint/" >

</Feature >

 

The receiver code will look something like this:

using System;

using Microsoft.SharePoint;

namespace MyNameSpace.Features

{

class LegalHoldFeatureReceiver : SPFeatureReceiver

{

   

public static void LinkFieldToContentType(SPWeb web,string contentType, SPField field)

{

SPContentType ct = web.ContentTypes[contentType];

ct.FieldLinks.Add(new SPFieldLink(field));

ct.Update();

}

   

public override void FeatureActivated(SPFeatureReceiverProperties properties)

{

//Expand Document Content Type to add additional Fields and Disposition Workflow

using (SPSite spsite = (SPSite )properties.Feature.Parent)

{

using (SPWeb spweb = spsite.RootWeb)

{

try

{

//Extend Document Content Type

   

LinkFieldToContentType(spweb, "Document", spweb.Fields[new Guid("{84027183-0549-4bfb-8601-7DDDB12EED12}")]);

   

LinkFieldToContentType(spweb, "Document", spweb.Fields[new Guid("{DBA5FD1B-97A0-470f-89B8-EB98BC28061A}")]);

   

LinkFieldToContentType(spweb, "Document", spweb.Fields[new Guid("{14CE4BF3-F83A-410d-A454-A12FD20A60A9}")]);

   

LinkFieldToContentType(spweb, "Document", spweb.Fields[new Guid("{DBA90AA4-B671-4c49-9ABF-C8C819DE0F13}")]);

   

LinkFieldToContentType(spweb, "Document", spweb.Fields[new Guid("{1D6D2CE5-ABCD-4368-829B-085D3FBE99FB}")]);

   

LinkFieldToContentType(spweb, "Document", spweb.Fields[new Guid("{1CDE08F2-DAF6-4449-B481-31095207A983}")]);

   

LinkFieldToContentType(spweb, "Document", spweb.Fields[new Guid("{2A8BB895-2D13-4300-BF67-487A82BA00AD}")]);

}

catch { }

}

}

}

public override void FeatureDeactivating(SPFeatureReceiverProperties properties)

{

throw new NotImplementedException ();

}

public override void FeatureInstalled(SPFeatureReceiverProperties properties)

{

throw new NotImplementedException ();

}

public override void FeatureUninstalling(SPFeatureReceiverProperties properties)

{

throw new NotImplementedException ();

}

}

}

 

 

Step 3:

We then are going to write the feature to "staple" the former feature to the farm globally. You can choose to only staple site definitions but in most cases I have found that the customer wants this "everywhere".

We are going to name this feature "MyKewlStaple"

The feature.xml file will simply point to the elements file as such:

<?xml version="1.0" encoding="utf-8" ?>

<Feature Id="ACC0BA0A-E0AF-4ee0-BECB-94B8C71E2B18"

Title="My Kewl Staple"

Description="This feature staples all other features to appropriate site templates"

Version="12.0.0.0"

Scope="Farm"

xmlns="http://schemas.microsoft.com/sharepoint/">

<ElementManifests>

<ElementManifest Location="elements.xml"/>

</ElementManifests>

</Feature>

 

The elements.xml file will do the staple like so:

<Elements xmlns="http://schemas.microsoft.com/sharepoint/">

<!--Global Features-->

<!--Legal Holds-->

<FeatureSiteTemplateAssociation Id="38B5399F-4DAB-4938-8F92-B474A319F9B2" TemplateName="GLOBAL" />

<FeatureSiteTemplateAssociation Id="A13B775C-FB57-4171-9907-D2B97A3F9B6F" TemplateName="GLOBAL" />

</Elements>

 

Step 4:

Now we want to be able to give the users somewhere to provision a retention schedule list in which they can modify retention schedules by content type. In my scenario I have an administration site under "sites/admin" and so we will be provisioning the list there. Because I do everything through content types, I will also create the content type feature in this step.

The feature.xml for the content type will be:

<?xml version="1.0" encoding="utf-8" ?>

<Feature Id="F45B1769-EBF2-4bc9-A0DA-F89B6802DB95"

Title="ABC Content Types"

Description="This feature provisions all Content Types to necessitate appropriate metadata"

Version="12.0.0.0"

Scope="Site"

xmlns="http://schemas.microsoft.com/sharepoint/">

<ElementManifests>

<ElementManifest Location="ctypes.xml"/>

</ElementManifests>

</Feature>

 

The ctypes.xml which provisions the content type will be:

<Elements xmlns="http://schemas.microsoft.com/sharepoint/">

<ContentType ID="0x01A4"

BaseType="0x01"

Description="This stores Retention Schedule by Content Type"

Group="ABC"

Name="RetentionList"

Version="0">

<FieldRefs>

<FieldRef ID="{96AAF204-A5E0-4851-A6F4-B3235EBEA185}" Name="_Archival" DisplayName="Archive Schedule" />

<FieldRef ID="{67A14E20-617B-46d8-8598-433782CC9E4E}" Name="_Disposal" DisplayName="Dispose Schedule" />

</FieldRefs>

 

 

The feature.xml for the retention list looks like:

<?xml version="1.0" encoding="utf-8" ?>

<Feature Id="A4CC0C25-6697-42cf-9ED4-94ED548B9186"

Title="Retention List"

Description="This feature provisions the Content Type Retention List"

Version="12.0.0.0"

Scope="Web"

xmlns="http://schemas.microsoft.com/sharepoint/">

<ElementManifests>

<ElementManifest Location="Retention\ListTemplateElements.xml"/>

<ElementManifest Location="Retention\ListInstanceElements.xml"/>

<ElementFile Location="Retention\schema.xml"/>

</ElementManifests>

</Feature>

 

I provide the template for the retention list which looks like (ListTemplateElements):

<?xml version="1.0" encoding="utf-8" ?>

<Elements xmlns="http://schemas.microsoft.com/sharepoint/">

<ListTemplate Name="Retention"

DisplayName="Retention"

Description="This template provides the retention schedules by content type"

BaseType="0"

Type ="6003"

OnQuickLaunch="TRUE"

SecurityBits="11"

Sequence="410"

Image="/_layouts/images/itgen.gif" />

</Elements>

 

I instantiate the list like (ListInstanceElements):

<?xml version="1.0" encoding="utf-8" ?>

<Elements xmlns="http://schemas.microsoft.com/sharepoint/">

<ListInstance Id="6537B4F6-13B7-4d48-BC90-D01483859A95"

Title="Retention Schedule"

Url="Lists/Retention"

Description="This list the retention schedule for ABC"

TemplateType="6003"

OnQuickLaunch="TRUE">

<Data>

<Rows>

<Row>

<Field Name="Title">Default</Field>

<Field Name="_Archival">6</Field>

<Field Name="_Disposal">1</Field>

</Row>

</Rows>

</Data>

</ListInstance>

</Elements>

 

Finally, I will provide just the pieces of the schema.xml file that I have changed. For a shortcut, I first copy the schema.xml file from 12\templates\features\customlist\custlist\schema.xml.

I changed the following sections:

First line:

<List xmlns:ows="Microsoft SharePoint" Title="Retention Schedule" FolderCreation="FALSE" Direction="$Resources:Direction;" Url="Lists/Retention" BaseType="0">

 

<MetaData>

<ContentTypes>

<ContentTypeRef ID="0x01A4">

<Folder TargetName="Item" />

</ContentTypeRef>

<ContentTypeRef ID="0x0120" />

</ContentTypes>

<Fields>

<Field ID="{96AAF204-A5E0-4851-A6F4-B3235EBEA185}" Name="_Archival" Type="Integer" Description="(in years) how long before record get archived" DisplayName="Archive Schedule" />

<Field ID="{67A14E20-617B-46d8-8598-433782CC9E4E}" Name="_Disposal" Type="Integer" Description="(in years) how long before record get deleted" DisplayName="Dispose Date" />

</Fields>

 

ViewFields:

<ViewFields>

<FieldRef Name="Attachments" />

<FieldRef Name="LinkTitle" />

<FieldRef Name="_Archival" />

<FieldRef Name="_Disposal" />

</ViewFields>

 

Step :

Now that we have a place that the users can modify retention schedules, we have provisioned the fields, added them to content types, and extended the document content type we are ready for the "final" step which will be creating the event receivers that are attached to every list template id of 101 which will be all document libraries created in the farm.

The feature.xml files will look like:

<?xml version="1.0" encoding="utf-8" ?>

<Feature Id="A13B775C-FB57-4171-9907-D2B97A3F9B6F"

Title="Legal Holds"

Description="This feature provides document item event receiver for legal holds"

Version="12.0.0.0"

Scope="Web"

xmlns="http://schemas.microsoft.com/sharepoint/">

<ElementManifests>

<ElementManifest Location="elements.xml"/>

</ElementManifests>

</Feature>

The interesting thing about the above is that it will go ahead and attach the receivers to all document library templates.

The elements file for attaching the code would look like:

<?xml version="1.0" encoding="utf-8" ?>

<Elements xmlns="http://schemas.microsoft.com/sharepoint/">

<Receivers ListTemplateId="101">

<Receiver>

<Name>Document Adding Event</Name>

<Type>ItemAdded</Type>

<SequenceNumber>25000</SequenceNumber>

<Assembly>MyNameSpace.Features, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f6e07d4bee530c01</Assembly>

<Class>MyNameSpace.Features.LegalHoldItemEventReceiver</Class>

<Data></Data>

<Filter></Filter>

</Receiver>

</Receivers>

<Receivers ListTemplateId="101">

<Receiver>

<Name>Document Updated Event</Name>

<Type>ItemUpdated</Type>

<SequenceNumber>25001</SequenceNumber>

<Assembly>MyNameSpace.Features, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f6e07d4bee530c01</Assembly>

<Class>MyNameSpace.Features.LegalHoldItemEventReceiver</Class>

<Data></Data>

<Filter></Filter>

</Receiver>

</Receivers>

</Elements>

 

The code for the receiver would look like:

using System;

using Microsoft.SharePoint;

namespace MyNameSpace.Features

{

class LegalHoldItemEventReceiver : SPItemEventReceiver

{

//Sets

public override void ItemAdded(SPItemEventProperties properties)

{

base.ItemAdded(properties);

using (SPWeb spweb = properties.OpenWeb())

{

if (spweb.Fields.ContainsField("NewStartDate"))

{

//Set the base counter for archive

properties.ListItem["NewStartDate"] = DateTime.Today;

 

//Get list of content types and set retention schedule

string AdminUrl = spweb.Url.Replace(spweb.ServerRelativeUrl,string.Empty) + @"/sites/admin";

string contentType = properties.ListItem.ContentType.Name;

 

//Set Default Values if no default set

int archiveSchedule = 6;

int disposeSchedule = 1;

using (SPSite adminSite = new SPSite(AdminUrl))

{

using (SPWeb adminWeb = adminSite.OpenWeb())

{

SPList lstRetention = adminWeb.Lists["Retention Schedule"];

//Run CAML for Content Type

string strQuery = @"<Where><Eq><FieldRef Name='Title' /><Value Type='Text'>" + contentType + @"</Value></Eq></Where>";

SPQuery ctQuery = new SPQuery();

ctQuery.ViewFields = "<FieldRef Name='Title'/><FieldRef Name='_Archival'/><FieldRef Name='_Disposal'/>";

ctQuery.Query = strQuery;

SPListItemCollection splic = lstRetention.GetItems(ctQuery);

if (splic.Count > 0)

{

archiveSchedule = (int)splic[0][new Guid("{96AAF204-A5E0-4851-A6F4-B3235EBEA185}")];

disposeSchedule = (int)splic[0][new Guid("{67A14E20-617B-46d8-8598-433782CC9E4E}")];

}

else

{

//if no results Run CAML for Default

strQuery = @"<Where><Eq><FieldRef Name='Title' /><Value Type='Text'>Default</Value></Eq></Where>";

ctQuery = new SPQuery();

ctQuery.ViewFields = "<FieldRef Name='Title'/><FieldRef Name='_Archival'/><FieldRef Name='_Disposal'/>";

ctQuery.Query = strQuery;

splic = lstRetention.GetItems(ctQuery);

if (splic.Count > 0)

{

archiveSchedule = (int)splic[0][new Guid("{96AAF204-A5E0-4851-A6F4-B3235EBEA185}")];

disposeSchedule = (int)splic[0][new Guid("{67A14E20-617B-46d8-8598-433782CC9E4E}")];

}

}

}

}

 

//Set Archive and Dispose Dates for record

properties.ListItem["ArchiveDate"] = DateTime.Today.AddYears(archiveSchedule);

properties.ListItem["DisposeDate"] = DateTime.Today.AddYears(archiveSchedule + disposeSchedule);

this.DisableEventFiring();

try

{

properties.ListItem.Update();

}

catch { }

finally

{

this.EnableEventFiring();

}

}

}

}

public override void ItemUpdated(SPItemEventProperties properties)

{

base.ItemUpdated(properties);

using (SPWeb spweb = properties.OpenWeb())

{

//Only run the code if the Legal Hold box has been modified

if (spweb.Fields.ContainsField("LegalHold"))

{

bool BeforeLegalHold = true;

bool AfterLegalHold = true;

if (properties.BeforeProperties["LegalHold"] == null || properties.BeforeProperties["LegalHold"].ToString() == "false")

{

BeforeLegalHold = false;

}

if (properties.AfterProperties["LegalHold"] == null || properties.AfterProperties["LegalHold"].ToString() == "false")

{

AfterLegalHold = false;

}

if (BeforeLegalHold != AfterLegalHold)

{

//Get list of content types and set retention schedule

string AdminUrl = spweb.Url.Replace(spweb.ServerRelativeUrl, string.Empty) + @"/sites/admin";

string contentType = properties.ListItem.ContentType.Name;

//Set Default Values if no default set

int archiveSchedule = 6;

int disposeSchedule = 1;

using (SPSite adminSite = new SPSite(AdminUrl))

{

using (SPWeb adminWeb = adminSite.OpenWeb())

{

SPList lstRetention = adminWeb.Lists["Retention Schedule"];

//Run CAML for Content Type

string strQuery = @"<Where><Eq><FieldRef Name='Title' /><Value Type='Text'>" + contentType + @"</Value></Eq></Where>";

SPQuery ctQuery = new SPQuery();

ctQuery.ViewFields = "<FieldRef Name='Title'/><FieldRef Name='_Archival'/><FieldRef Name='_Disposal'/>";

ctQuery.Query = strQuery;

SPListItemCollection splic = lstRetention.GetItems(ctQuery);

if (splic.Count > 0)

{

archiveSchedule = (int)splic[0][new Guid("{96AAF204-A5E0-4851-A6F4-B3235EBEA185}")];

disposeSchedule = (int)splic[0][new Guid("{67A14E20-617B-46d8-8598-433782CC9E4E}")];

}

else

{

//if no results Run CAML for Default

strQuery = @"<Where><Eq><FieldRef Name='Title' /><Value Type='Text'>Default</Value></Eq></Where>";

ctQuery = new SPQuery();

ctQuery.ViewFields = "<FieldRef Name='Title'/><FieldRef Name='_Archival'/><FieldRef Name='_Disposal'/>";

ctQuery.Query = strQuery;

splic = lstRetention.GetItems(ctQuery);

if (splic.Count > 0)

{

archiveSchedule = (int)splic[0][new Guid("{96AAF204-A5E0-4851-A6F4-B3235EBEA185}")];

disposeSchedule = (int)splic[0][new Guid("{67A14E20-617B-46d8-8598-433782CC9E4E}")];

}

}

}

}

if (AfterLegalHold)

{

//Empty Archive, Dispose and Last Legal End Dates

properties.ListItem[new Guid("{DBA90AA4-B671-4c49-9ABF-C8C819DE0F13}")] = null;

properties.ListItem[new Guid("{1D6D2CE5-ABCD-4368-829B-085D3FBE99FB}")] = null;

properties.ListItem[new Guid("{14CE4BF3-F83A-410d-A454-A12FD20A60A9}")] = null;

//Set Last Legal Start Date

properties.ListItem[new Guid("{DBA5FD1B-97A0-470f-89B8-EB98BC28061A}")] = DateTime.Today;

}

else

{

//Set Last Legal End Dates, Base Counter

properties.ListItem[new Guid("{14CE4BF3-F83A-410d-A454-A12FD20A60A9}")] = DateTime.Today;

//Get Difference between start and end legal hold dates

TimeSpan datediff = DateTime.Today.Subtract((DateTime)properties.ListItem[new Guid("{DBA5FD1B-97A0-470f-89B8-EB98BC28061A}")]);

//Get current base counter date

DateTime dtCurrentBaseCounterDate = (DateTime)properties.ListItem[new Guid("{1CDE08F2-DAF6-4449-B481- 31095207A983}")];

properties.ListItem[new Guid("{1CDE08F2-DAF6-4449-B481-31095207A983}")] = dtCurrentBaseCounterDate.AddDays(datediff.Days);

//Set Archive, Dispose Dates based on retention schedules

properties.ListItem[new Guid("{DBA90AA4-B671-4c49-9ABF-C8C819DE0F13}")] = dtCurrentBaseCounterDate.AddDays(datediff.Days).AddYears(archiveSchedule);

properties.ListItem[new Guid("{1D6D2CE5-ABCD-4368-829B-085D3FBE99FB}")] = dtCurrentBaseCounterDate.AddDays(datediff.Days).AddYears(archiveSchedule + disposeSchedule);

}

this.DisableEventFiring();

try

{

properties.ListItem.Update();

}

catch { }

finally

{

this.EnableEventFiring();

}

}

}

}

}

}

} 

 

After all this, you now have an automatically calculated Archive and Dispose date that the users can control via content type as well as the ability to pause based on legal holds!

In the next post on this series, I will provide the mechanism to automatically provision the scope that will tell what documents need to be archived and deleted as well as provide the timer job that does so!

Hope this helps

]]> 2007 Out of the Box Site Template Video Series https://docs.microsoft.com/archive/blogs/joekr/2007-out-of-the-box-site-template-video-series Fri, 09 Apr 2010 10:08:00 GMT https://blogs.msdn.microsoft.com/joekr/2010/04/09/2007-out-of-the-box-site-template-video-series/ Nikhil Shringarpurey (CTO of ProSource)  has a wonderful set of one minute videos that demonstrate the functions of each of the common out of the box template, complete with audio and video walkthroughs.

 This is extremely useful if you are just looking for a quick tutorial of what each one has and does for the business.

 I highly recommend reviewing these for audiences who are new to SharePoint 2007.

 These videos are located at:  http://www.themossmen.com/profiles/nikhil/Media

]]> Discussion Thread Reply Problem https://docs.microsoft.com/archive/blogs/joekr/discussion-thread-reply-problem Mon, 04 May 2009 12:48:00 GMT https://blogs.msdn.microsoft.com/joekr/2009/05/04/discussion-thread-reply-problem/ Today we are going to address the practical problem of notifications in a discussion thread. The case study is that I would like the owner of a discussion topic to receive email notifications whenever someone replies to their particular thread. I also do not want to write code (elimination of SPAlert through list item even receiver). We can't do an alert because the whole list is managed by several people and replies must be dynamic.

In comes workflow through SPD (SharePoint Designer) to save the day.

First, create a workflow in SPD:

You must then define your new workflow and set the parameters.

  • Give this workflow a name you can remember
  • Make absolutely sure that the discussion board you are trying to modify is chosen as this will determine the fields available later in the workflow
  • Only choose "Automatically start this workflow when a new item is created" as we don't want manual intervention and changes may not be warranted.
  • When Complete, chose next

We will then set the conditions parameter up. This will trigger this workflow if it meets the conditions you supply. In this case, we are simply going to tell the workflow to fire if this is not a root post. In other words, all replies will trigger this workflow and the initial creation of the thread will not. Also notice that we are giving this particular step a name.

When completed conditions, your screen should look like the below as "0" means false in this case:

Now we are going to focus on "Actions". This determines what the workflow is actually going to do. In this case, we want to email the discussion thread owner and so we are going to choose "Send an Email".

In the "To" field we can have a "workflow lookup" which will run a workflow within a workflow. Essentially what we want to do is determine the owner of the thread based on the current item's data. So if John Doe sends a reply to Jane Doe, we don't want to email Jane Doe.

So if you look at the filled out properties you can see that we are going to send it to the "created by" field of the top level thread. We are mapping the current item to the Discussion thread by the current Item's Parent Folder ID to the ID of the thread. This will pull back the created by owner and here is the magic.

Finally we can choose Finish and we are complete with the workflow after testing of course.

I hope this thread has been helpful to you and cheers!

]]> Social Networking: A Transformation of Communication https://docs.microsoft.com/archive/blogs/joekr/social-networking-a-transformation-of-communication Thu, 30 Apr 2009 10:56:45 GMT https://blogs.msdn.microsoft.com/joekr/2009/04/30/social-networking-a-transformation-of-communication/ Introduction and Overview

In 2003, after the technology bubble exploded or rather imploded a small website was launched with the simple intent of allowing people to communicate with each other by searching on people's interests, background, skills, and desires. People from within like communities, high schools and prior working environments could now start their very own virtual web site with absolutely no programming skill. A simple interface for end users plus a more advanced API mechanism for developers who did code allowed a plethora of opportunities. You could change your background images, talk to people and put a virtual you or avatar out for the entire world to see. MySpace quickly became one of the world's largest websites, a household name and still today is one of the three largest social networking sites.     

The concept of social networking was then kicked off. Social networking can be defined as "...the grouping of individuals into specific groups, like small rural communities or a neighborhood subdivision.." (What Is Social Networking? - What is Social Networking?). Soon after and using MySpace's massive success, LinkedIn launched a "professional portal" or networking site. LinkedIn quickly recognized that what worked for personal networking should be able to be leveraged in the professional space. The LinkedIn portal allowed for a public professional resume, recommendations and research into portfolios of work an individual has accumulated over their professional career. This resource has been invaluable for recruiters in finding talent. Facebook is the next evolution of social networking sites and is targeted more toward adults who have little time for such "time killers". Facebook does not allow much customization, however, there are many "Facebook Apps" that interface with the end user and allow multiple people to play games together, to instant message one another and create photo albums amongst other things. Orkut is a strong competitor of Facebook, however, it seems that its popularity was targeted mainly to Brazil for some reason perhaps because the owning company (Google), failed to market appropriately within other regions. As of just a few days before the writing of this paper the New York Times reported "Google began a campaign to get people to create these profiles, using its biggest gun: the Google search engine. If you want to control what people see when they search for your name, create a profile and click the box to have it included in Google search results." (Hansel 21 Apr. 2009).

Finally, we come to Twitter of course. Although Twitter by definition only falls loosely into the category of social networking, it is such a phenomenon, that I feel it needs to be addressed. With most social networking sites, there is a "wall" or status field in which a user updates some sort of text and users who monitor or are "friends" with them can see the collection of updates. This poses a problem if a user updates too often and it is considered rude or against social networking etiquette to post or change status more than around three times a day. Twitter is quite different as it is essentially a "stream" of updates that occur by an individual. As a matter of etiquette, it is not out of line to post a status such as "brushing my teeth and loving my new toothpaste" or "driving to the store to pick up a gallon of milk". To a non-user of such software, it seems overly intrusive and very difficult to maintain. This is proved extremely efficient as Twitter can operate off the principle of SMS messaging or in laymen's terms, text messaging. As the generation of young men and women are growing up, text messaging has come to dominate the tweens and teens and it is hard to imagine a world in where you cannot text message your bff (best friend forever). Twitter allows you to text your status to it and it will interpret the stream and render for people who "follow" your stream. As many teens text every day streams of activities multiple times anyway, to x number of friends, this now allows an individual to follow all friends in a very efficient way. During vacations, this becomes even more interesting as people tend to want to know new and exotic places people are going to and visiting.

This works not only for friend to friend communication but let us now examine updates from political sources, your favorite car company, ESPN or CNN. Would it not be nice to have automatic updates for your favorite topics if you so choose to follow these companies. What about deals or coupons. In the context of this paper we will delve deeper into this topic later.

Benefits

As you can clearly see, the benefits of social networking as a science and technology allow groups of individuals to communicate on a different level with one another.

  • People Finding: A large benefit of most social networking sites is the ability to find individuals based on a variety of parameters that are further specialized dependent on the social networking site. Many of these sites go so far as to recommend individuals to communicate with based on your existing network and personal parameters. For instance, if you are from Dallas, Texas and you work for Microsoft, the site may suggest another individual also in Dallas who works for Microsoft as the likelihood that you know this person exponentially increases.
  • Continuing Communication: A main feature of most social networking sites allow for the continuing communication by way of feeds, games or applications that facilitate the communication between networked communities. The benefits of this are that instead of picking up the phone and calling twenty five people, you can update your status once and you can convey what you are doing to your entire network. One of the most challenging tasks of friendship or even acquaintances is the communication and this venue allows an efficient means of that communication.
  • Matchmaking: Given the right context one can actually argue match-making sites such as e-Harmony could be considered social networking in a rudimentary way. The benefits of these sites obviously allow the hope of social networking in a more intimate fashion. The paradigm here is slightly different, as these sites actually work in reverse from other social networking sites. In most sites, you probably already know the individual you are searching for in some fashion either personally or by way of some other outlet like word of mouth or media outlet. In a matchmaking site however, you are being matched based on compatibility or other search criteria. Once a match is made and the site is no longer needed, virtual communication would not occur through this same site. This sort of site would not target audience retention but instead market to a specific profile property. I personally believe that eventually these sites will be deprecated in lieu of other social networking sites that already offer this along with the other networking features.
  • Technological Skills Advancement: The Washington Times recently posted an article related to the benefits of social networking as it relates to children growing up in the digital age. Lisa Tripp, co-author of a new book dealing with social networking called "Hanging Out, Messing Around, Geeking Out: Living and Learning New Media" states "Certain technical skills in the coming years are not going to be just about consuming media," she says. "It is also going to be about producing media. It is not just about writing a blog, but also how to leave comments that say something. Learning to communicate like this is contributing to the general circulation of culture" (Goff 28 Jan. 2009).
  • Monetization: A business could not be a business without of course generating revenue and thus a benefit for the social networking sites themselves would have to be the revenue generating potential. In May of 2008 the USA Today posted an article stating that where a large group of users are, money of course will follow "Murphy and other Facebook executives are well aware of that concern. "Advertisers follow people," says Sheryl Sandberg, a former Google executive who recently was named Facebook's chief operating officer. "We have 70 million active members. Once you have engaged users, the revenue will follow in that order." (Swartz 11 May 2008).

     

Dangers

Although the benefits of social networking are clearly stated and certainly relevant in today's society, one must be aware of the dangers of such technology as there are quite a few.

  • Personal information: One of the primary dangers of social networking sites is the amount of private information that can be exposed. Information such as home address and home telephone number if not marked private can be seen by all and this may not be what you want. It is important therefore, to research what profile information you or your children complete and expose to the world at large. Identity theft is one of the most rapidly growing crimes around the world and social sites as discussed in this paper along with carelessness further exacerbates the already mounting issue.
  • Public Domain: To elaborate on the point above, many individuals treat their Facebook site as their private bedrooms when in fact they should treat it as their front yard (Golic and Greenberg 2009). Essentially what the commentators were trying to say is that be careful what is exposed to the general public because while your most personal friends may enjoy the content, your next potential employer may not. Employers often times are asking for MySite, Facebook and Linked-In addresses of potential employees and many times are not pleased by what "interesting" content appears.
  • Predators: When asked about dangers of such sites of MySpace, Facebook or others like these, the media focuses primarily on the potential predators preying on children pretending they are individuals they are not. As avatars and virtual personalities are a benefit to the social networking community, they are also a very real and present danger. Movies, daytime television and news stations have all focused on this issue and it is of paramount importance that parents monitor or friend their children on these sites to make sure that communications are appropriate. In 2006, the CBS evening news stated "The Center for Missing and Exploited Children reported more than 2,600 incidents last year of adults using the Internet to entice children. With numbers like that, you'd think all parents would be hovering over their kids, wanting to know what they're doing online. But authorities say many parents are clueless about their kids' MySpace profiles." (Kreiser 6 Feb. 2006). It is also important to teach the children that these types of things do occur and to be on the lookout just as they would in meeting a stranger on the street.
  • Hackers: It stands to reason that where internet users go, hackers are there waiting with open arms (or malicious intent as it were). It is well known that the largest sites are usually the most attacked by hackers such as Microsoft.com as the exposure and resume potential for hackers lends credibility in the community. The Washington Post posted an article in 2008 which states simply " Social networking sites such as Facebook, MySpace and LinkedIn are fast emerging as some of the most fertile grounds for malicious software, identity thieves and online mischief-makers" (Krebs 9 Aug. 2008). As with any unknown or unexpected email attachment, one must be cautious of content on the web. Do not ever download and install anything you are unsure about. Research is of upmost importance when dealing with new software as seemingly benign software such as happy face emoticons often times can be the most malicious to your computer.

    

Possible Futures

So the obvious question is now what is next? I propose that we will start to see at social networking play a major role in the following categories:

  • Targeted Marketing campaigns: As a benefit of social networking, this paper allowed that where internet users go, so shall the online advertising. Imagine now that based on your profile, the advertisers can now target specifically to your needs concise and specific merchandise to your very demographic. Not only are you an internet user, you are a male between ages x and y, live in this region, work in this area and more. The advertising potential is virtually limitless.
  • Business Use: Already business are starting to see the benefits of social networking within the walls of the corporation. Consider that you would like to speak to the foremost expert in xyz system at your company. You could simply do a skills search in the people finder and communicate with this person. Let us take this one step farther and begin to "crawl" through email and other digital communication like instant messaging. Let us imagine that we could identify people intrinsically as experts in a particular system based on proximity of communications. Essentially if you could say that you correspond with person "A" who is an expert in technology "B" and because you communicate on a regular basis on that topic, by default, you must have some level of knowledge in the subject matter. Now jumping off the cliff in assumptions, what if this now qualifies you as an intermediary so essentially even if you do not know the answer to a question in the space, you know someone who does. This kind of knowledge and skills networking will be the wave of the future in businesses in my opinion.
  • Consumer Product Integration: People are becoming enamoured with "gadgets". Besides the television, their cell phones, their "Touch" and cool "gizmos" in their cars, what if we can dynamically Tweet locations based on vehicle or cell GPS. The DVR could Tweet status on television shows and perhaps control feeds of Tweets from friends or status updates on Facebook streaming directly to your television set without the need for your cell phone.
  • Political Campaigns: Already on the evening news you can see individuals blogs and Twitter accounts to be able to follow them. You can follow President Obama and the day to day tasks. I see that this will begin to be a political sounding board in the future added with the other medium such as television, radio and old fashion signs on the side of the road.

 

Conclusions

While social networking is blazing a new trail in technology and revolutionizing modern day communications, individuals must be aware of the dangers and take action to protect both themselves and their children from such dangers. As with most new things, arming oneself with knowledge of what is available and what can be done is the most important step in avoiding potential pitfalls. Communication ironically is the cornerstone to a pleasant and enjoyable social networking experience.

 

 

 

 

References

Goff, Karen G. "Social networking benefits validated." Washington Times 28 Jan. 2009. 23 Apr. 2009 <http://www.washingtontimes.com/news/2009/jan/28/social-networking-benefits-validated/>.

Golic, Mike, and Mike Greenberg. Mike & Mike in the Morning. ESPN Radio. 2009.

Hansel, Saul. "Google's Black-Box Social Network." New York Times 21 Apr. 2009. 23 Apr. 2009 <http://bits.blogs.nytimes.com/2009/04/21/googles-black-box-social-network/>.

Krebs, Brian. "Hackers' Latest Target: Social Networking Sites." Washington Post 9 Aug. 2008. 23 Apr. 2009 <http://www.washingtonpost.com/wp-dyn/content/article/2008/08/08/AR2008080803671.html>.

Kreiser, John. "CBS Evening News with Katie Couric." MySpace: Your Kids' Danger? CBS. New York, New York. 6 Feb. 2006. CBS Evening News with Katie Couric. 6 Feb. 2006. CBS. 27 Apr. 2009 <http://www.cbsnews.com/stories/2006/02/06/eveningnews/main1286130.shtml>.

Swartz, Jon. "Social-networking sites work to turn users into profits." USA Today 11 May 2008. 23 Apr. 2009 <http://www.usatoday.com/tech/techinvestor/industry/2008-05-11-social-networking_N.htm>.

What Is Social Networking? - What is Social Networking? 23 Apr. 2009 <http://www.whatissocialnetworking.com/>.

]]> A look at MOSS 2007 Performance Part I – Performance Counters https://docs.microsoft.com/archive/blogs/joekr/a-look-at-moss-2007-performance-part-i-performance-counters Sat, 04 Oct 2008 18:19:03 GMT https://blogs.msdn.microsoft.com/joekr/2008/10/04/a-look-at-moss-2007-performance-part-i-performance-counters/ Introduction

This series is intended to be a multi-part look at MOSS performance. There are many articles out there related to the performance analysis of MOSS but I wanted to attempt to compile some of that information and add some personal insight to the pool.

The scenario this is to address is to attempt the first steps in analyzing the question of "Why is my MOSS performing in a less ideal way that I would like?". We are also going to take a look at some ways in which we can proactively monitor the system with no additional tools to purchase.

Part one of this series will focus on Performance Counters.

Performance Counters

Assumption: Windows Server 2003 or higher is being utilized as the host operating system

General Counters

The following table will outline the performance counters for the base operating system that should be monitored along with thresholds and what the tolerance factor may mean if we are outside of those thresholds.

CPU

Counter

Threshold

General Recommendation

Description

Processor\% Processor Time\_Total

>80%-85% over 3 intervals

Add CPUs if utilization is consistently High

The total percentage of processor usage for a server.

System\Processor Queue Length\(N/A)

>#CPU's + 1

Add Faster CPU's

Exceeding the threshold indicates that the processors are not fast enough to process requests as they occur and that you are running out of processor power.

Processor\Interrupts\Sec

>1000

May indicate Hardware Issue

  

   

Memory

Counter

Threshold

General Recommendation

Description

Memory\Pages/sec\(N\A)

>200

Increase RAM

  

Memory\Pages Faults/sec\(N\A)

> (Drives x 4096)

Increase RAM

A high rate of page faults indicates a lack of physical memory.

Memory\Available Mbytes\(N\A)

<10% Available

Increase RAM

The amount of physical memory in MBs, immediately available for allocation to a process or for system use on the server.

Memory\Pool Nonpaged Bytes\(N\A)

<10%

Increase RAM

  

PagingFile\%Usage

>70%

Faster Disks/Better Controller/Add Disks/Increase RAM

Review this value in conjunction with memory—available megabytes and page faults per second—to understand paging activity on the server.

   

Disk

Counter

Threshold

General Recommendation

Description

PhysicalDisk\% Disk Time\DriveLetter

>80%

Controller or RAM

  

PhysicalDisk\Current Disk Queue Length\DriveLetter

>2

Faster Disks/Better Controller/Add Disks

  

LogicalDisk\%Idle Time\DriveLetter

>20%

Faster Disks/Better Controller/Add Disks

Reports the percentage of time during the sample interval that the disk was idle. If this value is very low, the logical disk is very busy.

   

Network

Counter

Threshold

General Recommendation

Description

Network interface\BytesTotalPer2ndInterface

>50% Avail Network Speed

Add Faster NICs/Check Switch

The rate at which bytes are sent and received over each network adapter.

   

ASP.NET

Counter

Threshold

General Recommendation

Description

ASP.NET\Requests per second_total

  

This is a great monitor for capacity as we will look at in a different part of this series

The rate at which bytes are sent and received over each network adapter.

   

MOSS WFE

Object

Counter

Threshold

Description

Web service*

Get requests per second_total or individual portal or per Windows SharePoint Portal Services site

Through ongoing monitoring, trends begin to emerge that equate get requests per second with CPU consumption.

Generally speaking, this is the rate at which clients are requesting information from the front-end Web servers.

   

MOSS Query Server

Object

Counter

Threshold

Description

Search

Query rate

200 per second

The number of queries posted to the server per second. Keep in mind this counter should be watched on the dedicated search servers.

Search

Succeeded queries

This counter should be used mostly for troubleshooting search problems.

The number of queries that produce successful searches; monitor this counter along with the failed queries counter when troubleshooting search problems.

Search catalogs

Number of documents

Microsoft has tested up to 5,000,000 documents.

This counter identifies the total number of documents in the catalog.

Search catalogs

Queries rate_(index names or all instances)

Indicates which indexes are most searched by users.

The number of queries posted to indexes per second; in conjunction with other performance data, this counter can help determine if your index configuration can be optimized.

Web service*

Get requests per second_total or individual portal or Windows SharePoint Portal Services site.

With ongoing monitoring, trends emerge that equate requests per second with CPU consumption.

Generally speaking, this is the rate that clients are requesting information from the front-end Web servers.

   

MOSS Index Server

Object

Counter

Threshold

Description

Search indexer catalogs

Number of documents

Microsoft has tested up to 5,000,000 documents.

The number of documents in the catalog

Search indexer catalogs

Index size MB

256,000 (256 GB)

The current size of index data in megabytes

   

I want to thank a colleague of mine, Kirk for providing much of this information that was MOSS specific

References:

English, B. (2004). Microsoft SharePoint Products and Technologies Resource Kit. New York: Microsoft P.

]]> A look at MOSS 2007 Performance Part II – IIS Log Analysis https://docs.microsoft.com/archive/blogs/joekr/a-look-at-moss-2007-performance-part-ii-iis-log-analysis Sat, 04 Oct 2008 15:19:00 GMT https://blogs.msdn.microsoft.com/joekr/2008/10/04/a-look-at-moss-2007-performance-part-ii-iis-log-analysis/ Introduction

In part one of this performance series we focused on performance counters and thresholds around those counters in an effort to monitor the performance of your MOSS platform. In this section, I plan to walk through some helpful items in analyzing your IIS Logs.

This is by no means an exhaustive review of parsing the logs; however, I do want to go through some review on IIS log parsing as well as some samples. For an in depth review, please see the references section of this article.

The first thing that any good software company will do when a diagnostic ticket comes in is ask for the company's ULS and IIS logs. What do they do with those logs behind the proverbial curtain? The first thing that will need to happen, is to parse through the logs to seek the answers that you want.

What are we looking for? How do we do this parsing?

Log Parser

Log Parser 2.2 is a free download from http://www.microsoft.com/downloads/details.aspx?FamilyID=890cd06b-abf8-4c25-91b2-f8d975cf8c07&displaylang=en and is a command-line SQL-like tool that can be used to parse pretty much any file. It is very powerful and in my humble opinion, is extremely underutilized.

The data that you can extract is truly amazing and only your imagination will limit you here.

The Log Parser syntax is very similar to Transact SQL syntax. To call the query, you will add the following switches:

-i

This is the input file type which can have values to read Event Logs, Performance Counters, IIS Logs and much more. The format for IIS Logs is "IISW3C"

-o

This is the output file type than can have values like NAT (Native or in console) and Chart which has quite a few more switches

-rtp

This switch will outline how many records will be output. For all, you simply will use a value of -1

   

These are just some of the switches you can include and for a complete reference, please read the log parser book referenced in the reference section.

In your FROM clause, you can separate multiple sources so if you have multiple folders where IIS logs are stored you can easily do this with little effort.

Examples

Hourly Request Count

Say we want to get a baseline of requests broken down by hour to IIS, we can run a query similar to:

logparser -i:IISW3C -o:NAT -rtp:-1 "SELECT QUANTIZE(TO_TIMESTAMP(date, time), 3600) AS Date_Hour, COUNT(*) INTO RequestsPerHourReport.txt FROM C:\IIS\W3SVC49737048\*.* WHERE (EXTRACT_EXTENSION(TO_LOWERCASE(cs-uri-stem)) IN ('aspx'; 'html'; 'asp')) GROUP BY Date_Hour"

   Note:  Updated 11/3/09, per Mike Wise, we should modify this script to strip out 401 http responses to eliminate the anonymous requests in NTLM.

This shows some of the things that you can do with the language. You can change this up by converting this to a chart like:

logparser -i:IISW3C -o:chart -chartTitle:"HTTP Requests Per Hour" -view -chartType:ColumnStacked3d "SELECT QUANTIZE(TO_TIMESTAMP(date, time), 3600) AS Hour, COUNT(*) INTO RequestsPerHourReport.gif FROM C:\IIS\W3SVC49737048\*.* WHERE (EXTRACT_EXTENSION(TO_LOWERCASE(cs-uri-stem)) IN ('aspx'; 'html'; 'asp')) GROUP BY Hour"

   

If you are not following section one of this series, you can get somewhat of a request per second (RPS) count dividing the values by 3600 again.

Status Code Breakdown

To breakdown a count and then do analysis on status codes for IIS you can run a query similar to the following:

logparser.exe -i:IISW3C -o:NAT -rtp:-1 "SELECT STRCAT(STRCAT(TO_STRING(sc-status),'.'),TO_STRING(sc-substatus)), COUNT(*) AS StatusCount INTO StatusCodeRatio.txt FROM C:\IIS\W3SVC49737048\*.* GROUP BY STRCAT(STRCAT(TO_STRING(sc-status),'.'),TO_STRING(sc-substatus))"

   

Bandwidth Analysis

There are many times that you may want to measure bandwidth on your IIS servers for load purposes. You can do this by running a query like:

logparser -i:IISW3C -o:NAT -rtp:-1 "SELECT QUANTIZE(TO_TIMESTAMP(date, time), 3600) AS Hour, DIV(Sum(cs-bytes),1024) AS Incoming(K), DIV(Sum(sc-bytes),1024) AS Outgoing(K) INTO HourlyBandwidthReport.txt FROM C:\IIS\W3SVC49737048_0918_0919\*.* GROUP BY Hour"

   

The possibilities continue on, but these are some of the more common that I personally use in initial diagnostics.

Extendibility

We can take the "SELECT" query out and create a "*.sql" file and call it that way. An example would be to create a file called "c:\myTest.sql" that contains the following text:

SELECT * FROM %source%

   

We then can call myTest.sql like:

Logparser.exe file:myTest.sql?source="c:\locationofIISLogs\*.* –i:IISW3C –o:NAT –rtp:-1 > outputFile.txt

   

As you can see, with the addition of parameterization and files, now we can extend this out much further.

References

Burnett, M., & Giuseppini, G. (2005). Microsoft Log Parser Toolkit. Syngress.

]]> Enabling HTTP Compression in IIS https://docs.microsoft.com/archive/blogs/joekr/enabling-http-compression-in-iis Thu, 04 Sep 2008 15:54:38 GMT https://blogs.msdn.microsoft.com/joekr/2008/09/04/enabling-http-compression-in-iis/  

The following submission was done by Kuba Njie, another services employee that I have had the extreme pleasure of working with. This was a great article and as such….

 

You can enable HTTP compression server-wide or on a specific directory. HTTP compression improves bandwidth utilization and speeds up Web site performance. In addition, you can compress static or dynamic responses.

 

Note
You must be a member of the Administrators group on the local computer to perform the following procedure or procedures. As a security best practice, log on to your server by using an account that is not in the Administrators group, and then use the runas command to run IIS Manager as an administrator. At a command prompt, type

runas /user:Administrative_AccountName"mmc %systemroot%/system32/inetsrv/iis.msc".

 

Procedures

To enable global HTTP compression by using IIS Manager

 

1.

In IIS Manager, double-click the local computer, right-click the Web Sites folder, and then click Properties.

2.

Click the Service tab, and in the HTTP compression section, select the Compress application files check box to enable compression for dynamic files.

3.

Select the Compress static files check box to enable compression for static files.

4.

In the Temporary directory box, use the default location, or type the path to a local directory or click Browse to locate a directory. Once a static file is compressed, it is cached in this temporary directory until it expires, or the content changes. The directory must be on the local drive of an NTFS–formatted partition. The directory cannot be compressed or shared, and the access control lists (ACLs) for the directory must include Full Control access to the identity of the application pool or to the IIS_WPG group.

5.

Under Maximum temporary directory size, click a folder size option. If you specify a maximum size under Limited to (in megabytes) (the default setting is 95 MB), then when the limit is reached, IIS automatically cleans up the temporary directory by applying the "least recently used" rule.

6.

Click Apply, and then click OK.

 

Note:

You must be a member of the Administrators group on the local computer to run scripts and executables. As a security best practice, log on to your computer by using an account that is not in the Administrators group, and then use the runas command to run your script or executable as an administrator. At a command prompt, type

runas /profile /user:MyComputer/Administratorcmd

to open a command window with administrator rights and then type cscript.exeScriptName (include the script's full path and any parameters).

 

 

To enable global HTTP compression by using Adsutil.vbs

1.

Open a command prompt.

2.

To enable dynamic compression, type the following at the command prompt and then press ENTER:

cscript adsutil.vbs set w3svc/filters/compression/parameters/HcDoDynamicCompression true

3.

To enable static compression, type the following at the command prompt and then press ENTER:

cscript adsutil.vbs set w3svc/filters/compression/parameters/HcDoStaticCompression true

To enable HTTP Compression for Individual Sites and Site Elements

1.

Disable global static compression by executing the following command at a command prompt:

adsutil set w3svc/filters/compression/parameters/HcDoStaticCompression false

2.

Enable static compression at this directory by executing the following command at a command prompt:

adsutil set w3svc/1/root/Home/StyleSheets/DoStaticCompression true

 

To disable static compression for only a single directory, first enable global static compression (if it is disabled) and then disable static compression at that directory. For example, to enable static compression for a directory at http://www.contoso.com/Home/StyleSheets, perform the following steps:

1.

Disable global static compression by executing the following command at a command prompt:

adsutil set w3svc/filters/compression/parameters/HcDoStaticCompression true

2.

Enable static compression at this directory by executing the following command at a command prompt:

adsutil set w3svc/1/root/Home/StyleSheets/DoStaticCompression false

 

Note

•

For a detailed discussion of how HTTP compression works, how to test compression, and detailed compression configuration options, see Using HTTP Compression for Faster Downloads.

  

•

For information on configuring the types of files IIS compresses server-wide, see Customizing the File Types IIS Compresses.

]]> Building a Login Page for your Authorization Provider https://docs.microsoft.com/archive/blogs/joekr/building-a-login-page-for-your-authorization-provider Wed, 06 Aug 2008 15:31:10 GMT https://blogs.msdn.microsoft.com/joekr/2008/08/06/building-a-login-page-for-your-authorization-provider/ There are many times in where you may want to "bypass" log in for MOSS 2007 because an SSO provider has already provided authentication. In this case, you could have written your own membership and role providers like here and implemented those providers like here.

Now you need to actually login but either do not like the out of the box login and want to provide your own, or as mentioned above, there is no need.

The following is a sample of what you may do in the Page_Load event of the login page. You of course will want to change the web configuration file to point to your MOSS implementation to the correct location.

public void AuthenticateToMOSS()

        {

            HttpCookie cookie = Request.Cookies["SMSESSION"];

            Utilities mySQLCalls = new Utilities();

   

            string myUser = string.Empty;

            string url = string.Empty;

   

            try

            {

                        // The user has been authenticated.

                        // 1. Create the ticket.

   

                        FormsAuthenticationTicket ticket = new FormsAuthenticationTicket(

   

                         1, // version

                         myUser,    // This will be whatever your username will be and stored in MOSS for authorization

                         DateTime.Now,    // issue time is now

                         DateTime.Now.AddDays(1), // expires tomorrow

                         true,    // cookie is persistent

                         "member");   // role assignment is stored in the UserData

                        HttpCookie cookie1 = new HttpCookie(FormsAuthentication.FormsCookieName,

                        FormsAuthentication.Encrypt(ticket));

   

                        if (Session["RedirectURL"] == null)

                        {

                            //Here you can redirect somewhere in MOSS

                            Session["RedirectURL"] = FormsAuthentication.GetRedirectUrl(myUser, true);

                            Session["UID"] = iUID;

                        }

   

                        //// 2.5  Create Timeouts for cookies involved

                        if (cookie != null)

                        {

                            cookie.Expires = DateTime.Now.AddDays(1);

                            Response.Cookies.Add(cookie);

                        }

                        cookie1.Expires = DateTime.Now.AddDays(1);

   

                        //// 3. Attach the cookie to the outbound response.

                        Response.Cookies.Add(cookie1);

   

                        // 4. Do the redirect.

   

   

                        this.Page.Response.Redirect(url, false);

                    }

            catch (System.Threading.ThreadAbortException)

            {

                //Do nothing

            }

            catch (Exception exc)

            {

                System.Diagnostics.Debug.Print(exc.ToString());

                Response.Clear();

                Response.Write(exc.ToString());

                Response.End();

            }

            finally

            {

            }

        }

   

Please notice that I am persisting all cookies here for client integration.  I am also manually creating my ticket as MOSS seemed to have issues with the one-liner.

 This is sample and may need some modification.

]]>