Home - Chris Gideon

7/2/2008

I have seen countless issues induced by not excluding the right directories in a file level antivirus. I am happy to say we have an article on the subject now. Please take it into consideration when deploying WSSv3 or MOSS.

952167 Folders may have to be excluded from antivirus scanning when you use a file-level antivirus program in Windows SharePoint Services 3.0 or in SharePoint Server 2007
http://support.microsoft.com/default.aspx?scid=kb;EN-US;952167

Posted at 1:09 PM by NORTHAMERICA\cgideon | Permalink | Email this Post | Comments (0)

6/6/2008

Hotfixes and SP1

SharePoint Products and Technologies Service Pack 1 Resource Center

http://technet.microsoft.com/en-us/office/sharepointserver/bb735839.aspx

942388 Issues that are fixed in Windows SharePoint Services 3.0 by Windows SharePoint Services 3.0 Service Pack 1

http://support.microsoft.com/default.aspx?scid=kb;EN-US;942388

942390 Description of the SharePoint Server 2007 issues that are fixed by the 2007 Microsoft Office servers Service Pack 1

http://support.microsoft.com/default.aspx?scid=kb;EN-US;942390

For deploying fixes in general here are the proper steps.

Deploy software updates for Office SharePoint Server 2007

http://technet.microsoft.com/en-us/library/cc263467(TechNet.10).aspx

For a green field deployment I recommend you slip stream as per Create an installation source that includes software updates (Office SharePoint Server 2007)

http://technet.microsoft.com/en-us/library/cc261890(TechNet.10).aspx

WSS v3 Post SP1 (public) fixes that have shipped since SP1

948945 Description of the Windows SharePoint Services 3.0 hotfix package: February 21, 2008

http://support.microsoft.com/default.aspx?scid=kb;EN-US;948945

948957 Description of the Windows SharePoint Services 3.0 hotfix package: February 22, 2008

http://support.microsoft.com/default.aspx?scid=kb;EN-US;948957

949399 Description of the Windows SharePoint Services 3.0 hotfix package: February 27, 2008

http://support.microsoft.com/default.aspx?scid=kb;EN-US;949399

949956 Description of the Windows SharePoint Services 3.0 hotfix package: March 17, 2008

http://support.microsoft.com/default.aspx?scid=kb;EN-US;949956

950279 Description of the Windows SharePoint Services 3.0 hotfix package: March 21, 2008

http://support.microsoft.com/default.aspx?scid=kb;EN-US;950279

950484 Description of the Windows SharePoint Services 3.0 hotfix package: March 27, 2008

http://support.microsoft.com/default.aspx?scid=kb;EN-US;950484

952292 Description of the Windows SharePoint Services 3.0 hotfix package: May 12, 2008

http://support.microsoft.com/default.aspx?scid=kb;EN-US;952292

MOSS post sp1 (public) fixes that have shipped since SP1

944710 Description of the SharePoint Server 2007 hotfix package: January 31, 2008

http://support.microsoft.com/default.aspx?scid=kb;EN-US;944710

948947 Description of the SharePoint Server 2007 hotfix package: February 21, 2008

http://support.microsoft.com/default.aspx?scid=kb;EN-US;948947

949955 Description of the SharePoint Server 2007 hotfix package: March 17, 2008

http://support.microsoft.com/default.aspx?scid=kb;EN-US;949955

950280 Description of the SharePoint Server 2007 hotfix package: March 21, 2008

http://support.microsoft.com/default.aspx?scid=kb;EN-US;950280

950292 Description of the SharePoint Server 2007 hotfix package: March 21, 2008

http://support.microsoft.com/default.aspx?scid=kb;EN-US;950292

950487 Description of the SharePoint Server 2007 hotfix package: March 27, 2008

http://support.microsoft.com/default.aspx?scid=kb;EN-US;950487

952294 Description of the SharePoint Server 2007 hotfix package: May 8, 2008

http://support.microsoft.com/default.aspx?scid=kb;EN-US;952294

Content Deployment Rollup

952698 Description of the Windows SharePoint Services 3.0 hotfix package: May 20, 2008 (Now available)

http://support.microsoft.com/default.aspx?scid=kb;EN-US;952698

952704 Description of the Office SharePoint Server 2007 hotfix package: May 20, 2008 (Now available)

http://support.microsoft.com/default.aspx?scid=kb;EN-US;952704

What should I have in my slipstream to get the latest fixes?

WSS v3 SP1+MOSS SP1+952294 (MOSS global)+ 948947(MOSS blackout combined global local)+ 952292(WSS global)+ 948957(WSS local to English)

What should I apply in conjunction with SP1 if I am already deployed?

952294 (MOSS global)+ 948947(MOSS blackout combined global local)+ 952292(WSS global)+ 948957(WSS local to English)

Do I have to PSConfig after each fix?

No, you can deploy SP1 for both MOSS and WSSv3 plus all the fixes and PSCONFIG one time.

You can view each of those articles for what has been fixed. Remember you should always deploy fixes in pairs of Global and Local for your language per product. That's why at this time you need 4 fixes (2 WSS 2 MOSS) post sp1 to get current

Hope this helps,

Chris

Posted at 10:47 AM by NORTHAMERICA\cgideon | Permalink | Email this Post | Comments (0)

5/29/2008

We are hiring

If there are any SharePoint Admin/Developers out there looking to take their career and product knowledge to the next level, our team is hiring.

http://members.microsoft.com/careers/search/details.aspx?JobID=5C954EBB-17CC-4C91-8D5D-7324AEE27FEA&start=1&interval=10&SortCol=DatePosted

Dedicated Support Engineer - Microsoft SharePoint Portal Server
Location - Austin, Tx

Primary responsibilities include providing technical support for customer service delivery and availability, while ensuring satisfaction with Microsoft SPS. The ideal candidate should have knowledge of all current MOSS 2007 capabilities and product future functionality (MOSS 2007 product development roadmap). Knowledge of SharePoint development capabilities since this resource will mentor customer development teams. Candidate should skills in the integration capabilities of SharePoint with other technologies such as CRM. Candidate should possess knowledge of SharePoint infrastructure requirements and operations. Ideal candidate should have practical experience of implementing SharePoint (preferable for the retail industry) and experience leveraging the impact of SharePoint as a solution to replace content management solutions. Ideal candidate should have knowledge of MOSS 2007 end-user capabilities including information such as what the end-users can do and what the end-users shouldn't do.

This person will be responsible for delivering technical support to a strategic Microsoft Services customer. The ideal candidate should have at least 4 years experience with several MSFT Enterprise products. This candidate should posses a superior knowledge and demonstrated technical proficiency in Microsoft SharePoint Portal Server (SPS), with experience in managing large environments.

Qualifications: 4 year technical degree or equivalent work experience, plus 3-5 years experience in technical support or MIS in an Enterprise environment. Ideal candidate should be able to demonstrate technical competence. Current Windows MCSE preferred. MCSE required within 6 months of joining the team. Candidate must possess the ability to effectively communicate with customer managers and executives on technical and business issues. Strong organization, time management, project management and negotiation skills. The successful applicant must be able to start within 30 days of offer acceptance.

If you haven't been to Austin you don't know what you're missing.

http://www.frommers.com/destinations/austin/

http://cityguides.msn.com/citylife/greenarticle.aspx?cp-documentid=4848625

http://www.austintexas.org/

Posted at 10:23 AM by NORTHAMERICA\cgideon | Permalink | Email this Post | Comments (0)

5/2/2008

New White Paper on Mirroring Available

White paper: Case Study of High Availability for SharePoint using Database Mirroring

Yet more info on the user of SQL Server 2005 Mirroring and SharePoint.

Posted at 1:22 PM by NORTHAMERICA\cgideon | Permalink | Email this Post | Comments (0)

2/15/2008

MOSS/WSSv3 Greenfield deployment

I am going to try and keep this post current over time. In a nutshell this is what I would want if I was doing a MOSS deployment from scratch today in terms of bits.

.NET Framework 2.0 SP1

http://www.microsoft.com/downloads/details.aspx?FamilyID=79bc3b77-e02c-4ad3-aacf-a7633f706ba5&DisplayLang=en

.NET Framework 3.0 Service Pack 1

http://www.microsoft.com/downloads/details.aspx?familyid=EC2CA85D-B255-4425-9E65-1E88A0BDB72A&displaylang=en

MOSS SP1 Integrated (not out yet but can be done) Instructions can be found here:

http://technet2.microsoft.com/Office/f/?en-us/library/21dcf8aa-8a6e-4325-aa17-0188e491361c1033.mspx

If WSS only then the SP1 Integrated Build can be found here:

http://www.microsoft.com/downloads/details.aspx?FamilyId=EF93E453-75F1-45DF-8C6F-4565E8549C2A&displaylang=en

By following the steps linked above you can integrate the rollups.

Description of the SharePoint Server 2007 hotfix package: March 27, 2008

http://support.microsoft.com/?id=950487

Description of the Windows SharePoint Services 3.0 hotfix package: March 27, 2008

http://support.microsoft.com/?id=950484

Hope this helps,

Chris

Posted at 12:59 PM by NORTHAMERICA\cgideon | Permalink | Email this Post | Comments (0)

2/12/2008

Disable PAC Validation

As any who know me will attest, I like Kerberos. I especially like Kerberos with SharePoint as I have blogged on many occasions for very technical reasons. That said, one of the points that I had failed to mention (except to the customers I work directly) is PAC validation.

What is a PAC?

PAC stands for Privilege Attribute Certificate. The PAC contains various types of authorization data including groups that the user is a member of, rights the user has, and what policies apply to the user. When the client receives a ticket, the information contained in the PAC is used to generate the user’s access token (from here).

Why am I bringing this up with regard to SharePoint? Because SharePoint does a lot of authentication and one of the benefits to using Kerberos is that you get to move away from the Secure channel authentication (NTLM) work that I have described in this blog as a bottleneck. However, until you disable PAC validation you will still be using the Secure Channel plumbing.

What is the solution?

906736 You experience a delay in the user-authentication process when you run a high-volume server program on a domain member in Windows 2000 or Windows Server 2003

http://support.microsoft.com/default.aspx?scid=kb;EN-US;906736

Hope this helps,

Chris

Posted at 9:41 AM by NORTHAMERICA\cgideon | Permalink | Email this Post | Comments (0)

1/4/2008

Members of the domain local group cannot view a Microsoft Office SharePoint Server 2007 Web site

This post may have value only to me or those into the AD SharePoint interaction. Nonetheless in case you missed it.

932378 Members of the domain local group cannot view a Microsoft Office SharePoint Server 2007 Web site
http://support.microsoft.com/default.aspx?scid=kb;EN-US;932378

Posted at 12:49 PM by NORTHAMERICA\cgideon | Permalink | Email this Post | Comments (0)

9/14/2007

Post Hotfix installation steps

During the installation of a hotfix for SharePoint technologies in V3 (as long as you are not running in silent mode for the patch) you will get a dialog like the one below prompting you to run psconfig.

It is easy to forget about this dialog after the patch is complete. However, it is critical that you run the SharePoint Products and Technologies Configuration Wizard (psconfig) after a hotfix. This wizard or command line depending on the way you run it, will perform an inplace build to build(b2b) upgrade on the SharePoint installation. SharePoint hotfixes are inplace upgrades from one build of SharePoint to another. The hotfix package simply copies the files to disk and registers the binaries. It is the SharePoint Products and Technologies Configuration Wizard that actually upgrades the installation to the new patch.

If you run psconfig -help upgrade from the command line as opposed to the wizard you will see the following.

PSCONFIG.EXE -cmd upgrade

[-wait]

[-force]

[-reghostonupgrade]

[-finalize]

[-inplace <v2v|b2b>]

[-sidebyside]

Performs SharePoint upgrade. This command is automatically executed when running the SharePoint Products and Technologies Configuration Wizard if SharePoint needs to be upgraded.

wait: If specified, the SharePoint Products and Technologies Configuration Wizard does not return until upgrade completes. If not specified, the wizard returns after dispatching a SharePoint Timer service job to perform upgrade. You can view the upgrade job status by accessing the SharePoint Central Administration Web Application using your web browser.

force: If specified, the SharePoint Products and Technologies Configuration Wizard stops any currently running upgrade actions, and then restarts upgrade.

reghostonupgrade: If specified, the SharePoint Products and Technologies Configuration Wizard will revert all content streams during the upgrade.

finalize: If specified, the SharePoint Products and Technologies ConfigurationWizard will finalize the current upgrade. You will not be able to undo this action.

inplace: If specified, the SharePoint Products and Technologies Configuration Wizard will perform an in-place upgrade. If v2v is chosen, then an in-place version to version upgrade will be performed. If b2b is chosen, then an in-place build to build upgrade will be performed.

sidebyside: If specified, the SharePoint Products and Technologies Configuration Wizard will perform a gradual upgrade.

Therefore if you choose to run from the command line you will need to use this syntax.

Psconfig –cmd upgrade –wait –inplace b2b

But this is not enough for hotfixes that include search fixes. For those you also need to let search know about the changes. The way to do this is by running the following stsadm command after patches that contain search fixes.

For MOSS:

Stsadm –o osearch –action start

For WSS help search:

Stsadm –o spsearch –action start

Posted at 7:16 AM by NORTHAMERICA\cgideon | Category: SharePoint | Permalink | Email this Post | Comments (0)

8/28/2007

Fixes for MOSS/WSSV3 before SP1

To get current before SP1 the following fixes can be applied.

WSS 3.0

939592 Description of the Windows SharePoint Services 3.0 hotfix package: June 29, 2007

http://support.microsoft.com/default.aspx?scid=kb;EN-US;939592

MOSS

939654 Description of the SharePoint Server 2007 hotfix package: June 29, 2007

http://support.microsoft.com/default.aspx?scid=kb;EN-US;939654

Search/MOSS

939077 Description of the SharePoint Server 2007 hotfix package for SharePoint Server 2007 and for SharePoint Server 2007 for Search: June 24, 2007

http://support.microsoft.com/default.aspx?scid=kb;EN-US;939077

Posted at 2:12 PM by NORTHAMERICA\cgideon | Permalink | Email this Post | Comments (0)

.Net fixes for MOSS/WSSv3

Here is my list of .net fixes to get you current before SP1 for the Framework.

.Net 3.0

936707 FIX: A .NET Framework 2.0 managed application that has an Authenticode signature takes longer than usual to start

http://support.microsoft.com/default.aspx?scid=kb;EN-US;936707

ASP.NET

934839 FIX: You may receive an exception when you browse a .NET Framework 2.0 ASP.NET Web application

http://support.microsoft.com/default.aspx?scid=kb;EN-US;934839

.Net 2.0

936464 FIX: A client cannot determine whether a chunked HTTP response is completed when the connection is closed before the response is completely sent to the client

http://support.microsoft.com/default.aspx?scid=kb;EN-US;936464

935904 FIX: You receive the System.IndexOutOfRangeException exception error when you use a native image on an x64-based computer in the Microsoft .NET Framework 2.0

http://support.microsoft.com/default.aspx?scid=kb;EN-US;935904

Now to get these fixes see a post from Todd Carter.

Posted at 2:09 PM by NORTHAMERICA\cgideon | Permalink | Email this Post | Comments (0)

RSS Feed