Posts
245
Trackbacks
0
January 2011 Entries
SharePoint Learning Resources

The last 6 to 8 months have been a blur.  They have gone fast!
Back in June I took part in a group that was creating content for Microsoft Learning to have it be their Microsoft Official Curriculum lineup for SharePoint 2010.  In that process I noticed there was something different about SharePoint 2010 when compared to the wealth and quality of documentation that had been available when SharePoint 2007 was out.  There is a lot of it!

There is of course the MOC Offerings, and the material I worked on is Course 10174A: Configuring and Administering Microsoft SharePoint 2010.  And many other courses available.  But it does not stop there, Microsoft has made available course through other channels, like TechNet and MSDN.

 

The portal for IT Pros highlights the following:

Getting Started with SharePoint Server 2010 for IT Pros

SharePoint 2010 Advanced IT Professional Training

SharePoint 2010 Enterprise Search IT Professional Training

 

The developer portal highlights the following:

Get Started Developing on SharePoint 2010

SharePoint 2010 Advanced Developer Training

SharePoint 2010 Enterprise Search Developer Training

Posted On Wednesday, January 26, 2011 4:26 AM | Comments (0)
OneNote for iPhone

I remember looking forward to the day when my favorite Office tool would be available as an app for the iPhone, that day is today!

Free at the moment, not sure if that will change.

Check it out here … http://itunes.apple.com/us/app/onenote/id410395246?mt=8

Posted On Tuesday, January 18, 2011 5:30 PM | Comments (0)
How do you automate a SharePoint 2010 deployment?

In the last couple of months SharePoint traffic (consulting, training and speaking) has picked up.  And with that also the requests for deployments.  There are good, great, bad and really bad things around this. But that is for another topic.  However part of the good and great has been the fact of organizations wanting to do a proof of concept deployment (even when WSS or MOSS has been deployed).

We can go through a session (Microsoft has the SDPS concept, SharePoint Deployment Planning Services) of discovering what the customer wants to achieve from their investment in the platform and then also proceed to model the solution that would fit their needs.  But it should not stop there.  The next step should be a POC (as many have requested) to test out.

Now, on to the meat of this post.  How do I deploy?  While it is a good process to watch and see all of it take place, not many have the time to sit through that.  Even more so, when that has been part of the description of deploying the platform in the sessions mentioned above.

I will, though, break it into a deployment for development purposes and a deployment of a farm.

Two tools (or scripts) for those two different types of deployment.

First, let me address the development environment.  Around the last week in October, Chris Johnson (SharePoint Product Team) announced a SharePoint Easy Setup for Developers.  The kit itself will assist you in installing SharePoint Server (in standalone mode), the tools that go around Visual Studio, Expression Studio and the Office 2010 tools.

Here is the link to Chris’ post: http://blogs.msdn.com/b/cjohnson/archive/2010/10/28/announcing-sharepoint-easy-setup-for-developers.aspx

The other scenario is the use of a script in assisting you through the deployment of a farm. Now, this is not to override planning.  It should highlight the need for planning even more.  How?  Having your service accounts planned, the structure of the sites and the scale of your deployment.  Enter AutoSPInstaller.  This is a CodePlex project, and the intent behind this is not only to automate the installation but to give some meaning and get some sense out of what goes on during a SharePoint deployment.

How?  Take for example the creation of the databases, when we do the initial OOB deployment by using the wizard, more times than not, we leave the names as they are.  How is that a “bad thing”?  Let’s make it a better practice to rename those Databases, and have them take on a name that is not “GUID-ized”. Having a better naming convention will not hurt, on the other hand will allow for consistency.

Here is the link to AutoSPInstaller’s site on CodePlex:

http://autospinstaller.codeplex.com/

Posted On Wednesday, January 5, 2011 5:33 AM | Comments (1)
Great SharePoint Community Resources

3 sites that any person working with SharePoint should visit are:

SharePoint Magazine

SharePoint Magazine is an online magazine dedicated to the world of SharePoint and related Information Worker Technologies.

End User SharePoint

Community driven content, at this point in time the site is a historical archive of content released.

Nothing But SharePoint

I see this as the natural evolution of EndUserSharePoint.com
Follows on the same great principle of community driven content, but expanding from the world of End User to the IT Pro and Developer realms.

Posted On Sunday, January 2, 2011 8:17 AM | Comments (0)
Adventures in Lab Management Configuration: Part 2 of 3

The first post was the high level overview.

Now it is time for the details on what was done to the existing CMMI Project based on CMMI v 4.2.

The first step was to go into Visual Studio, then from the Team Project Collection Settings and then to the Process Template Manager.  Once there, it was a matter of selecting the appropriate template (MSF for CMMI Process Improvement v5.0) and download to a point I could reference later (for example C:\Templates).

Then on to using the steps from the guidance post.

Since I was using an x64 deployment, I will make reference to the path as <toolpath>, however the actual path to reference in a 64-bit environment is “C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE”.

As I mentioned on the previous post, make sure to first perform a backup of the Configuration, Collection and Warehouse DBs.  If you did not apply any changes to the names and such, then you will find those as tfs_Configuration, tfs_DefaultCollection and tfs_Warehouse.

Now, the work needed with the witadmin tool:

That includes the uploading of the structures that differ from v4.2 to v5.0

There is likely going to be an issue with the naming of some fields.

For example, TFS 2010 likes something along the lines of “Area ID”, whereas TFS 2008 would have had it as “AreaID”.  So, this will need to be corrected.  Some posts will have you go through this after the errors pop up.  I would recommend doing this process prior to executing the importwitd process. 

witadmin listfields /collection:<path to collection> > c:\ListFields.txt

Review the following fields:

AreaID, review the Name property and validate if it states “AreaID”, the you will need to rename the Name field to reflect “Area ID”.

ExternalLinkCount, RelatedLinkCount, HyperLinkCount, AttachedFileCount and IterationID would be the other fields to check.

To correct the issue, then execute the following:

witadmin changefield /collection:<path to collection> /n:"System.ExternalLinkCount" /name:"External Link Count"

Repeat for Area ID, Related Link Count, Hyperlink Count, Attached File Count and Iteration ID.  Once this is done, proceed with the commands below.

witadmin importwitd /collection:<path to collection> /p:<project> /f:"<path to downloaded template>\MSF for CMMI Process Improvement v5.0\WorkItem Tracking\TypeDefinitions\TestCase.xml"

witadmin importwitd /collection:<path to collection> /p:<project> /f:"<path to downloaded template>\MSF for CMMI Process Improvement v5.0\WorkItem Tracking\TypeDefinitions\SharedStep.xml"

witadmin importcategories /collection:<path to collection> /p:<project> /f:"<path to downloaded template>\MSF for CMMI Process Improvement v5.0\WorkItem Tracking\categories.xml"

Modifications to the Bug Definition:

First step is to export the existing definition.

witadmin exportwitd /collection<path to collection> /p:<project> /n:bug /f:"<path to downloaded template>\MSF for CMMI Process Improvement v5.0\MyBug.xml"

Make modifications to recently exported MyBug.xml file.  Details for the modification are here:  http://msdn.microsoft.com/en-us/library/ff452591.aspx#ModifyTask

Once the changes are done, proceed with the import command

witadmin importwitd /collection:<path to collection> /p: <project> /f:"<path to downloaded template>\MSF for CMMI Process Improvement v5.0\MyBug.xml"

Repeat the process for the the Scenario or Requirement Type Definition

witadmin exportwitd /collection<path to collection> /p:<project> /n:requirement /f:"<path to downloaded template>\MSF for CMMI Process Improvement v5.0\MyRequirement.xml"

Make modifications to recently exported MyRequirement.xml file.  Details for the modification are here:  http://msdn.microsoft.com/en-us/library/ff452591.aspx#ModifyTask

Once the changes are done, proceed with the import command

witadmin importwitd /collection:<path to collection> /p: <project> /f:"<path to downloaded template>\MSF for CMMI Process Improvement v5.0\MyRequirement.xml"

Provide the Bug Field Mapping definition, after creating the file as specified here: http://msdn.microsoft.com/en-us/library/ff452591.aspx#TCMBugFieldMapping

tcm bugfieldmapping /import /mappingfile:"<path to downloaded template>\MSF for CMMI Process Improvement v5.0\bugfieldmappings.xml" /collection:<path to collection> /teamproject:<project name>

Posted On Saturday, January 1, 2011 8:51 PM | Comments (0)
Free eBook: Programming Windows Phone 7 by Charles Petzold

This book is available for download from http://charlespetzold.com/phone/index.html

You will find the pdf file for the book and a zip file with the sample code.

Posted On Saturday, January 1, 2011 7:39 PM | Comments (0)
Disclaimer: The views expressed on this blog are my own and do not necessarily reflect the views of my employer.

Creative Commons License


Check out my about.me profile!

INETA Community Speakers Program

Follow enriquelima on Twitter
Locations of visitors to this page