Don’t know if you ever heard of the tool, but i like it.
When analysing (big) log files, it’s nice to have a tool that can help you with that.
the log files that SharePoint creates are not very friendly. this tool comes to the aid.
Get it here: http://code.msdn.microsoft.com/ULSViewer
ever since working with SharePoint 2010 i wondered how the navigation was configured. then this morning i found this qoute.
Once you activate publishing for a site collection, every template within that
site collection will use the publishing navigation controls. This means that if
you create a team site as a subsite to a publishing site, that team site will use the
publishing navigation, not the team site navigation described earlier.
Hope this will information will help others also.
A question i hear from a lot of customers is:
Do i need to update/upgrade to Office 2010 when upgrading to SharePoint 2010 ? Most companies don’t want to update (again) and tell there users a new version of Office will be installed.
What you need to know is: Which features of SharePoint 2010 require Office 2010. If that is known you can decide to upgrade to Office 2010, or to postpone this upgrade.
So, which features require office 2010 to be installed:
- Open, edit, and save documents using Office Web Apps
- View and update SharePoint ’ s managed keywords and tags
- Display SharePoint’s managed keywords and tags within the actual document
- Navigate by keywords when browsing existing Office documents
- Reduced protection of documents using Microsoft Information Rights Management (IRM)
- Reduced ability to add digital signatures with Microsoft IMS
- Restrict editing per user with Microsoft IMS
- Allow co-authoring of an Office document in realtime
- Offline access to SharePoint content with SharePoint Workspace
- Integrate Microsoft Access applications in SharePoint
If these features are not required or a not important at first, you can decide not to upgrade to office 2010.at least not at first. you can always decide later to upgrade.
Hope this information will help others to decide if an upgrade is needed.
I found a nice atricle introducing : Visual Studio 2010 Tools for SharePoint Development
it’s an article from the MSDN magazine
If you installed Microsoft SharePoint Server 2010 For Internet Sites Enterprise, and then you tried to activate the product by using the enterprise key before May 25, 2010, you encounter the following symptoms:
- The following Enterprise features are not available, or the features have reduced functionality:
- Access Services
- InfoPath Forms Services
- Chart Web Parts
- Excel Services
- PerformancePoint Services
- Visio Services
To verify that you are encountering this issue, consider the following scenarios:
For more info and a solution look here : http://support.microsoft.com/kb/2143810
As of today for those access to a MSDN account can download:
- SharePoint 2010
- Office 2010
Have fun with it !
For those who didn’t hear it yet (not sure if that is possilbe 😉 )
SharePoint 2010 reaches RTM!
For me personally the most important information about the release was:
They will be able to download the product in English, French, Spanish, German, Russian, and Dutch via the Volume Licensing Service Center starting April 27
Yes !! This release we don’t have to wait until the dutch language pack comes out.
And yes i will install the english version, but i still need the dutch support/language files to satisfy the user .
For everyone who is considering installing SharePoint in their native language from the start > rethink !
Not sure if you know what you are doing but the error messages are also translated. And this doesn’t make it easy to search for answers, if you don’t know what the problem is.
Those who know, know you like an English base installation. However, don’t forget : the language of the sitecollection is the default language of al sub-sites.
NOTE: not sure how SharePoint 2010 handles this, have’n’t had the change to test this yet.
So finaly i got a customer who asked me to do something i really didn’t know if it was possible.
Already been working on it for 2 days now and it seems that i have got it working.
Ok, so what was the wish of this customer:
I have a SharePoint 2003 32 bit single server dutch installation with a sql 2000 database. It has some custom webparts, some custom templates and sitescollections have some odd behaviours. Please transform this environment to a SharePoint 2007 environment 64 bit on windows 2008 servers, using sql 2008 as database server, configured as a small farm, using a UK installation with dutch language packs.
Most of the wishes can be done separately, but all together, i was not sure if this was going to work.
furthermore, did i mention that the database was 50Gb 😮
Toplevel the next steps are taken
- upgrade SharePoint 2003 to sp2
- Run prescan tool
- backup database(s)
- install Sharepoint 2007
- install all needed language packs
- restore sql backup
- install templates
- copy images (from images folder in 12-hive)
- use stsadm with addcontentdb option
- manually correct all issues (some migrated lists, templates and functionality that was no longer working)
Et voila, we had over 90% working again.
So the next days i will be fine-tuning the installation, creating scripts, making an installation manual, because …. we have to do it all ones more .
Never a dull day in SharePoint land.
Ever since i started installing SharePoint 2007 (over 2 years ago), i have been configuring Alternate Access Mappings.
This was never a problem. Up until yesterday.
Yesterday i configured SharePoint AAM for an installation i had done earlier.
For the record: Sharepoint 2006 x64 on a Windows 2008R2 x64. I must say: it was my first experience with 2008R2
Set al the settings that needed to be set.
Computername : Sharepoint1
New “Nice” name: Intranet
I created the AAM entries, and since i was configuring the machine (contained 1 empty site collection) i also started search.
I stopped the search after 38 minutes, because that was impossibly long
I then tried to reach the sharepoint site and i the only thing a got was a blank page where access denied should have been visible.
So besides not able to login, i also was not presented the right page.
This made me start my quest for information on the internet.
I assumed it was IIS7 related. 2008R2 has some new features and installation points. example : ASP.net 3.5.1 is automatically installed.
I took me a whole lot of time and testing to find out that the problem was eventually solved using the disableloopback registry setting.
Simply settings this registry setting, then rebooting and everything works as intended.
So for every out there that has problems with AAM and Windows2008 (not sure if it’s R2 only or not)
Try the registry setting first. Here you can find more information about it
It’s a simple setting, doesn’t cost a lot of time, and can be easily removed.