My SharePoint links from this week (weekly)

  • JavaScript tricks for SharePoint

    tags: SharePoint JavaScript

  • Many organizations are finding that leveraging the full suite of capabilities SharePoint offers requires introduction of a new requirement – that of dealing with, managing and exploiting taxonomies.  Of course taxonomies are not new, but there is some confusion about where managed metadata services and the term store end and true taxonomy management begins.  There are also some misconceptions about the process of deriving and applying taxonomies in SharePoint.  The following are five areas of confusion that we have seen in our engagements and research.

    tags: SharePoint taxonomy myths

  • You can synchronize a SharePoint library, contact list, task list, Project task list and a certain type of SharePoint external list with Microsoft Outlook 2010. Because many SharePoint 2010 users also use Outlook 2010 to collaborate and coordinate activities and projects, the ability to synchronize these libraries and lists can help you become more efficient, especially if you work offline or don’t have convenient access to your SharePoint sites all the time.

    tags: SharePoint Office Outlook

Posted from Diigo. The rest of my favorite links are here.

  • JavaScript tricks for SharePoint

    tags: SharePoint JavaScript

  • Many organizations are finding that leveraging the full suite of capabilities SharePoint offers requires introduction of a new requirement – that of dealing with, managing and exploiting taxonomies.  Of course taxonomies are not new, but there is some confusion about where managed metadata services and the term store end and true taxonomy management begins.  There are also some misconceptions about the process of deriving and applying taxonomies in SharePoint.  The following are five areas of confusion that we have seen in our engagements and research. 

    tags: SharePoint taxonomy myths

  • You can synchronize a SharePoint library, contact list, task list, Project task list and a certain type of SharePoint external list with Microsoft Outlook 2010. Because many SharePoint 2010 users also use Outlook 2010 to collaborate and coordinate activities and projects, the ability to synchronize these libraries and lists can help you become more efficient, especially if you work offline or don’t have convenient access to your SharePoint sites all the time.

    tags: SharePoint Office Outlook

Posted from Diigo. The rest of my favorite links are here.

Biwug3011: SharePoint 2010 Multilingual User Interface (MUI) Deep dive

BIWUG is hosting an interesting evening on SharePoint 2010 Multilingual User Interface.

I also heard from the president of the BIWUG  that the #SharePint will be organized with actually pints :-)
So no #ShareCola or #ShareMinutemaid but actually real Belgian beer, hence a real #SharePint!

Doing a SharePoint project in a multilingual environment can be tricky. In this BIWUG session we will focus on how the new MUI (Multilingual User Interface) allows for multilingual collaboration scenarios.  We will show you how MUI and the SharePoint variations framework relate to each other.  Next to showing the out of the box features we will do a deep dive for developers explaining how to use the MUI framework in SharePoint custom solutions. The session will wrap up with some best practices and pitfalls as well as a round the table discussion to exchange ideas. 

 

<Update>

I heard there are some books that need a new owners. #bookGivaAway with special thanks to WROX.

</Update>

Agenda:

18:00-18:30 – Welcome and snacks

18:30-19:30 – SharePoint MUI – Part I  (Speakers: Andy Van Steenbergen & Joris Poelmans)
19:30-19:45 – Break
19:45:20:45 – SharePoint MUI – Part II  (Speakers: Andy Van Steenbergen & Joris Poelmans)
20:45 – … SharePint!

I hope to meet and greet you all there.
You can use the link here under to register.

Speaking at BIWUG on October 27th about Governance

On Thursday October 27th BIWUG organizes an evening full with great information. I’ll be a part of that, speaking about SharePoint Governance. Or we can also call it Governance for SharePoint. I’ll also participate in the second part of the evening where we’ll talk about the past, the present and the future of BIWUG. Oh yes, for the record, the third part of that evening will also involve some me, but in the form of attending and trying to get a good conversation and meeting great people at the #SharePint.

During this session I want to give the attendees a different view on Governance. Most probably (and hopefully) a view they didn’t thought at before. Yes, I’m talking about the softer side of a SharePoint deployment.

dreamstime_872766

This is the sessions abstract : Stop thinking about features features features when talking about governance. When designing governance for a SharePoint implementation, a lot (not to say all) energy and words go out to technical stuff, SLA’s and not to the things that define the business value. And the business value is not only a perfect technically tuned and performant SharePoint farm (if that even exists).

This evening will start at 18:00 in the offices of Microsoft (Leonardo Davincilaan 3 , 1935 Zaventem).
If you are interested in this session and haven’t subscribed yet, it can get tough to get in. 74 people already registered for this session and it’s sold out.

SharePoint Connections PreConference day

For the first time I have registered for a pre conference day. Actually I registered for the pre and post conference session.

The pre-conference workshop was delivered by Dan Holme ( and the topic was : “SharePoint Collaboration Masterclass”. It was an interesting session with a few new items for me but it definitely triggered some ideas.

Dan talked about the “administrator jumpstart”. Basically he explained which accounts you better create (actually you’ll need them) before you start installing and configuring SharePoint 2010. Also it is a best practice to use Powershell scripts to install and configure your farm(s). Especially when you have an Acceptance, Pre-Production and Production environment, by scripting the installation and configuration, you can be sure that they are installed and configured the same way. Another interesting point he mentioned, was that the Cumulative Updates are handled differently in SharePoint 2010 then in SharePoint Server 2007 (MOSS 2007). Now, when you have SharePoint server 2010 installed, you don’t need to install the CU OF SharePoint Foundation prior to the installation of the CU for SharePoint Server. So you can install the SharePoint Server CU directly. This will save some time and reboots.
Also, when you don’t configure the outgoing email settings, all the features that use this (like alerts) will not be activated on you sites.

After the first break, the subject was Creating the Collaboration Application. Interesting to hear was this advice. Don’t use (or configure) Claims Based authentication, unless you are really sure you will need/use it.
Dan also mentioned that it is a best practice to use A record in your DNS server setting and not C Names.
When creating your top level Site Collection, the Publishing Site might be a very good choice if you would like to brand your sites. (via the masterpages). The publishing site has more masterpages ‘installed’ and this would make it easier to apply some custom branding on these sites.  Oh yes, of course when you used the Publishing Site template, you will not be able to create a subsite other then another Publishing site,unless you activate these Site templates in the Look and Feel section / Page Layouts and Templates. You can access these pages via the Site Settings.
Today, there were no sacrifices done to the Demo Gods, so some of his demos didn’t work well. Like the one where Dan would show how you can adopt users by creating shortcuts in the Network Locations. But he explained it pretty good.

After Lunch Security was the topic. Claims based authentication can store extra attributes  or properties, so you can use these properties to target content . (For instance country)
Dan also told you don’t need to extend WebApplications anymore when you want to use multiple authentication providers.
Another best practice explained. To allow a user (even a visitor) to see a certain site in his or hers Mysite, you can create a new “default” group. You give this group very restricted permissions on the site, and you add ALL the site users to this group (besides the other groups like members or visitor). By doing this, these users will see the site appear in their MySite. Oh yes, small remark, this will only work with individual user rights, not when adding an Active Directory group.

Dan also gave a demonstration of the Office integration and SharePoint, but again, the demo gods weren’t our friends.

After the break, Dan talked, while you could really see him fighting his jetlag, about the Remote BLOB Storage . What I remember and noted was that the default RBS (Filestream provider) can only use local drives, and that you can also use AvePoint DocAve extender for this. A good advice was that when you use SQL backup, you should also backup your BLOB location manually. This is not needed when you use the backup procedures in Central Admin, and I presume third party tools will also tackle this.

The last topic was Managed Metadata and the Taxonomy living together with the Folksonomy. Dan also showed the metadata based views and filters.

We had a really nice chat after the session, with some additional Q&A, and then I went out to diner with Marcel Franke. Because diner took more time then I thought, I wasn’t able to attend the DIWUG session.
Arriving back at my hotel I saw Karine Bosh (MVP and also known for some of us as ‘The CAML girl’) and I sacrificed myself to go out for diner with her, although I just drank a few Grimbergen beers, but we had a really nice conversation about SharePoint, U2, Phil Collins and job satisfaction.

Nintex Workflow for SharePoint 2010 released

I guess it was not an accident that Nintex released Nintex Workflow 2010 on day 1 of #WPC, the Microsoft Worldwide Partner Conference.

When I was searching for some Nintex video’s on Youtube, I found this very nice video of Mike Fitzmaurice explaining with his well known and recognizable voice what Nintex Workflow 2010 is.

For the readers who are not familiar with Nintex workflow, it adds a drag-and-drop workflow designer, connectivity and advanced workflow features to the Microsoft SharePoint document management and collaboration platform, empowering business users and IT Professionals alike to quickly and easily automate business processes; from a simple leave approval request, to complex integration across external applications and data sources.

The slogan of Nintex is “Worklfow for everyone™” and if you ask me, that’s what they bring

I would like to add or emphasize a really important reason why Nintex Workflow is IMO “better” then a custom development workflow. Release management. When a Visual Studio workflow is ready for production and a WSP (SharePoint Solution) file is produced, you have to go to he release management procedures and processes, and they can be quite hard with SharePoint.

The moment my SharePoint 2010 environment is up and running , I will start to experiment with Nintex Workflow 2010, and if time allows me, I’ll even post about that :-)

I guess it was not an accident that Nintex released Nintex Workflow 2010 on day 1 of #WPC, the Microsoft Worldwide Partner Conference.

When I was searching for some Nintex video’s on Youtube, I found this very nice video of Mike Fitzmaurice explaining with his well known and recognizable voice what Nintex Workflow 2010 is.

For the readers who are not familiar with Nintex workflow, it adds a drag-and-drop workflow designer, connectivity and advanced workflow features to the Microsoft SharePoint document management and collaboration platform, empowering business users and IT Professionals alike to quickly and easily automate business processes; from a simple leave approval request, to complex integration across external applications and data sources.

The slogan of Nintex is “Worklfow for everyone™” and if you ask me, that’s what they bring

 

I would like to add or emphasize a really important reason why Nintex Workflow is IMO “better” then a custom development workflow. Release management. When a Visual Studio workflow is ready for production and a WSP (SharePoint Solution) file is produced, you have to go to he release management procedures and processes, and they can be quite hard with SharePoint.

The moment my SharePoint 2010 environment is up and running , I will start to experiment with Nintex Workflow 2010, and if time allows me, I’ll even post about that :-)

Why Microsoft is wrong in their SharePoint bring to market approach.

Since a few years I execute the job of SharePoint consultant. SharePoint seems to be one of the most successful product, maybe even the most successful product Microsoft has launched. Then why should a guy like me complain about that Microsoft is wrong in their bring to market? They probably earn billion$ with SharePoint. And they should, because it is a great product! But at the end of this post, in the quote you can see my worry.

During the SharePoint Evolution conference SPEVO held in April of this year, my memory was refreshed of something that was said during one of the analyst sessions in the SharePoint Conference 2009 (SPC09) in Las Vegas.
The SPEVO was actually the SharePoint Best Practices Europe Conference, but because of the launch of a new version called SharePoint 2010 there were not a lot best practices to share on SharePoint 2010. BUT the organizers of this conference really got the message I’ll talk about in this blog post. They organized a IW (Information Worker stream) In fact, they organized even 2 parallel streams. Well done Steve Smith!

During a session from Symon Garfield, he explained why 70% of all projects fail. There are several reason, like unclear requirements, scope changes. One of the main failure reasons is that a SharePoint project can’t be driven only by IT.
SharePoint is a business driven product. IT can install, deploy and support it, but it can not solely drive it toward long term success.
You also need to have a good user adoption plan, and some corporate guidelines (let’s call them governance) to make sure that when people really start using SharePoint, it doesn’t get a maze where you can’t do or find anything. If you take a look at the Microsoft Press books, about 99% of the SharePoint books are technically focused. There is a lack of business side books. (Thank you Michael Samspon for representing this 1%)

During that analyst panel session at SPC09 there was a discussion about having a third pillar next to the Developers and IT PRO’s. The name was not specified, but lets call this group Functional people, or Functionals.  For me, but also for all SharePoint projects in general, I thought that was good, no even great news.

But until now, nothing has changed. From Microsoft’s opinion you are or a developer, or an IT PRO.There is no new group. Or you write code, or you have access to Central Admin.

A good example of this are Ignite Sessions. They are organized for IT Professionals and Developers, but not for Functionals. Even with such a huge release of  SharePoint 2010, where a lot extra power is provided to PowerUsers, and it very important to have that link between Business and IT.

Or the Microsoft SharePoint 2010: Developer and IT Professional Learning Plan.

In my first conversation with Karine Bosch (a Belgian SharePoint MVP) right after a BIWUG session  we were talking about what we did in the SharePoint world. When she explained what she does I replied, “Oh, you’re a code sh|tter”, without being disrespectful. That’s good because we need SharePoint code writers I replied, (you can also read developers)  to cover non ‘Out Of The Box’ functionality , When I explained what I do, I summarized it with “I’m a document sh|tter”. And We also need them (I guess). Actually that’s also what Karine confirmed.

That’s why in my humble opinion that Microsoft is acting wrongly. Until now, they don’t provide any special documentation or support for these Functionals. Besides some sales and marketing information on how SharePoint will make your organization more productive, there is no specific information for the Functionals. They are just twilights. They act the “Build it and they will come” way.
And they should pay attention to this, because otherwise SharePoint might become one of these “Oooh darn, it’s a SharePoint” applications.

That’s also why I am so happy that guys like Michael Samspon, the author of Seamless Teamwork, a book on using SharePoint from a business perspective, Raymond Dux Sy , the author of SharePoint for Project Management: How to Create a Project Management Information System (PMIS) and Paul Culmsee take a different approach on SharePoint. I will do my best to provide useful information like these guys do in their blogs, webcasts, books, … That will be my way to contribute to the grey twilight zone that Microsoft can’t fill.

On the other hand, I must admit that I know a few, but just a few guys that are good at coding, have a good knowledge of the the Out Of The Box functionality of SharePoint and are able to talk to the business and translate their requirements to SharePoint functionality. These are the golden egg chickens…

But to conclude, what I’m trying to explain is that Microsoft, and the Microsoft partners will be judged by their clients (the business) based on the return SharePoint gives to the business, not on it’s nice technical gracefulness.

Just for the record, here are my my questions to Microsoft.

What are your intentions to this issue? (When)Are you planning to setup a functional stream?

Since a few years I execute the job of SharePoint consultant. SharePoint seems to be one of the most successful product, maybe even the most successful product Microsoft has launched. Then why should a guy like me complain about that Microsoft is wrong in their bring to market? They probably earn billion$ with SharePoint. And they should, because it is a great product! But at the end of this post, in the quote you can see my worry.

During the SharePoint Evolution conference SPEVO held in April of this year, my memory was refreshed of something that was said during one of the analyst sessions in the SharePoint Conference 2009 (SPC09) in Las Vegas.
The SPEVO was actually the SharePoint Best Practices Europe Conference, but because of the launch of a new version called SharePoint 2010 there were not a lot best practices to share on SharePoint 2010. BUT the organizers of this conference really got the message I’ll talk about in this blog post. They organized a IW (Information Worker stream) In fact, they organized even 2 parallel streams. Well done Steve Smith!

During a session from Symon Garfield, he explained why 70% of all projects fail. There are several reason, like unclear requirements, scope changes. If you take £SharePoint,  one of the main reasons is that a SharePoint project can’t be driven only by IT. SharePoint is a business driven product. IT can install, deploy and support it, but it can not solely drive it toward long term success.
You also need to have a good user adoption plan, and some corporate guidelines (let’s call them governance) to make sure that when people really start using SharePoint, it doesn’t get a maze where you can’t do or find anything. If you take a look at the Microsoft Press books, about 99% of the SharePoint books are technically focused. There is a lack of business side books. (Thank you Michael Samspon for representing this 1%)

During that analyst panel session at SPC09 there was a discussion about having a third pillar next to the Developers  and IT PRO’s. The name was not specified, but lets call this group Functional people, or Functionals.  For me, but also for all SharePoint projects in general, I thought that was good, no even great news.

But until now, nothing has changed. From Microsoft’s opinion you are or a developer, or an IT PRO.There is no new group. Or you write code, or you have access to Central Admin.

Take for example the Ignite Sessions. They are organized for IT Professionals and Developers, but not for Functionals. Even with such a huge release of  SharePoint 2010, where a lot extra power is provided to PowerUsers, and it very important to have that link between Business and IT.

Or the Microsoft SharePoint 2010: Developer and IT Professional Learning Plan.

In my first conversation with Karine Bosch (a Belgian SharePoint MVP) right after a BIWUG session  we were talking about what we did in the SharePoint world. When she explained what she does I replied, “Oh, you’re a code sh|tter”, without being disrespectful. That’s good because we need SharePoint code writers (you can also read developers)  to cover non ‘Out Of The Box’ functionality , When I explained what I do, I summarized it with “I’m a document sh|tter”. And We also need them (I guess). Actually that’s also what Karine confirmed.

That’s why (I would say) in my humble opinion that Microsoft is acting wrong. Until now, they don’t provide any special documentation or support for these Functionals.  Besides some sales and marketing information on how SharePoint will make your organization more productive, there is no specific information for the Functionals. They are just twilights.
And they should pay attention to this, because otherwise SharePoint might become one of these “Oooh darn, it’s a SharePoint” applications.

That’s also why I am so happy that guys like Michael Samspon, the author of Seamless Teamwork, a book on using SharePoint from a business perspective, Raymond Dux Sy , the author of SharePoint for Project Management: How to Create a Project Management Information System (PMIS) and Paul Culmsee take a different approach on SharePoint. I will do my best to provide useful information like these guys do in their blogs, webcasts, … That will be my way to contribute to the grey twilight zone that Microsoft can’t fill.

On the other hand, I must admit that I know a few, but just a few guys that are good at coding, have a good knowledge of the the Out Of The Box functionality of SharePoint and are able to talk to the business and translate their requirements to SharePoint functionality. These are the golden egg chickens…

But to conclude, what I’m also trying to explain is that Microsoft, and the Microsoft partners will be judged by their clients (the business) based on the return SharePoint gives to the business, not on it’s nice technical gracefulness.

 

Just for the record, here are my my questions to Microsoft.

What are your intentions to this issue? (When)Are you planning to setup a functional stream?

Last minute : How to Best Gather Requirements for SharePoint: free seminar by @meetduxLast minute : How to Best Gather Requirements for SharePoint: free seminar by @meetdux


Open Lecture – How to Best Gather Requirements for SharePoint

Monday, June 28, 2010 6:00 PM – 7:30 PM CEST

USPJ Academy invites you to the first open lecture of the academy. If you want to learn more about USPJ Academy, please visit our web pages at http://www.uspja.com/

Poor requirements can be attributed to failed SharePoint implementations. The key to successful SharePoint implementation is properly developing requirements. A lot of people know that this is important, however, only a handful of folks truly understand what it takes to do this right.

In this presentation, you will learn key techniques in effectively eliciting, analyzing, prioritizing, validating and documenting requirements for SharePoint projects.

In addition, participants will be able to identify:

  • Key components of requirements gathering process
  • Why requirements traceability is paramount in defining ROI in SharePoint projects
  • Why having a well defined business case is necessary to effectively initiate requirements gathering

The primary audience for this class are executives, managers, analysts, consultants who wish to properly implement SharePoint and immediately reap its’ organizational benefits.

Participants will get presentation notes, checklists, and templates.

It’s a great lecture, held by one of the true masterminds of SharePoint project management, Dux Raymond Sy. (Twitter: MeetDux)

Register (no cost) on https://www1.gotomeeting.com/register/729809009

SharePoint 2010 VHD files : download them now!

Last week, exactly one week ago SharePoint 2010 and Office 2010 got launched. More information on http://sharepoint.microsoft.com/2010launch 

Since May 8th the Information worker VHD files are ready to be downloaded. You can find them at the Microsoft download center

You can also download them with the Akamai download manager
(links updated at September 17th 2010)

The download is about 18 GB big.

This is the content of the VHDs:

Virtual machine “A” contains the following pre-configured software:

  1. Windows Server 2008 R2 Standard Evaluation Edition x64, running as an Active Directory Domain Controller for the “CONTOSO.COM” domain with DNS and WINS
  2. Microsoft SQL Server 2008 R2 Enterprise Edition with Analysis, Notification, and Reporting Services
  3. Microsoft Office Communication Server 2007 R2
  4. Microsoft Visual Studio 2010
  5. Microsoft SharePoint Server 2010 Enterprise Edition
  6. Microsoft Office Web Applications
  7. Microsoft FAST Search for SharePoint 2010
  8. Microsoft Project Server 2010
  9. Microsoft Office Professional Plus 2010
  10. Microsoft Visio 2010
  11. Microsoft Project 2010
  12. Microsoft Office Communicator 2007 R2

Virtual machine “B” contains the following pre-configured software:

  1. Windows Server 2008 R2 Standard Evaluation Edition x64, joined to the “CONTOSO.COM” domain
  2. Microsoft Exchange Server 2010

Active directory has been preconfigured over 200 “demo” users with metadata in an organizational structure. All of these user profiles have been imported and indexed for search within SharePoint Server 2010.
SharePoint Server 2010 has been configured in a “Complete” farm using the default SQL Server 2008 R2 instance. A default site has been created using the Team Site template at http://intranet.contoso.com/ and a FAST Search Center at http://intranet.contoso.com/search/.
As shipped virtual machine “A” requires image “B” for email. Running image “B” is optional.

Last week, exactly one week ago SharePoint 2010 and Office 2010 got launched. More information on http://sharepoint.microsoft.com/2010launch 

Since May 8th the Information worker VHD files are ready to be downloaded. You can find them at http://is.gd/cfVcv

You can also download them with the Akamai download manager

The download is about 18 GB big.

This is the content :

Virtual machine “A” contains the following pre-configured software:

  1. Windows Server 2008 R2 Standard Evaluation Edition x64, running as an Active Directory Domain Controller for the “CONTOSO.COM” domain with DNS and WINS
  2. Microsoft SQL Server 2008 R2 Enterprise Edition with Analysis, Notification, and Reporting Services
  3. Microsoft Office Communication Server 2007 R2
  4. Microsoft Visual Studio 2010
  5. Microsoft SharePoint Server 2010 Enterprise Edition
  6. Microsoft Office Web Applications
  7. Microsoft FAST Search for SharePoint 2010
  8. Microsoft Project Server 2010
  9. Microsoft Office Professional Plus 2010
  10. Microsoft Visio 2010
  11. Microsoft Project 2010
  12. Microsoft Office Communicator 2007 R2

Virtual machine “B” contains the following pre-configured software:

  1. Windows Server 2008 R2 Standard Evaluation Edition x64, joined to the “CONTOSO.COM” domain
  2. Microsoft Exchange Server 2010

Active directory has been preconfigured over 200 “demo” users with metadata in an organizational structure. All of these user profiles have been imported and indexed for search within SharePoint Server 2010.
SharePoint Server 2010 has been configured in a “Complete” farm using the default SQL Server 2008 R2 instance. A default site has been created using the Team Site template at http://intranet.contoso.com/ and a FAST Search Center at http://intranet.contoso.com/search/.
As shipped virtual machine “A” requires image “B” for email. Running image "B" is optional.

SharePoint 2010 RTM

Yesterday Jeff Teper announced on the SharePoint Team blog some great news

–quote–

Today we reached an exciting engineering milestone- the release-to-manufacturing (RTM) for Office 2010, SharePoint 2010, Visio 2010 and Project 2010!

RTM is the final engineering milestone and a major achievement for all of the internal teams who worked so hard to get to this point. As tirelessly as our engineering teams worked, we would never have reached this milestone without incredibly active participation from our customers and partners. More than 5,000 organizations and partners have worked with us on rapid deployment and testing of the products, and the feedback that we’ve received from all these programs has shaped a fantastic set of products that I’m sure our customers will love.

Our Volume License customers with active Software Assurance (SA) on these products will be one of the first to receive the 2010 set of products. 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. Other languages will be available on a rolling timeline. Customers without SA will be able to purchase the new products through Volume Licensing from Microsoft partners starting May 1.

–End Quote–

Full article can be read via this link

SharePoint 2010 beta available on MSDNSharePoint 2010 beta beschikbaar op MSDN

A nice day today. 2 days earlier than expected the SharePoint 2010 beta is released. It is available on MSDN (for MSDN subscriptions only)

If you have a MSDN subscription you can download it from this location https://msdn.microsoft.com/en-gb/subscriptions/securedownloads/default.aspx

SharePoint Designer 2010 BETA , SharePoint Foundations 2010 BETA (WSS 4.0) and Office 2010 BETA has also been released. Happy downloading and experimenting!

BUT… there are some issues. PLEASE read a http://bit.ly/2rNgl8 blog before you start installingHet is een mooie dag vandaag. 2 dagen eerder dan verwacht is de SharePoint 2010 BETA gereleased. Je kan ze downloaden op de MSDN website (op voorwaarde dat je een MSDN abonnement hebt)

Dus, als je een MSDN abo hebt, kan je SharePoint 2010 downloaden via deze link https://msdn.microsoft.com/en-gb/subscriptions/securedownloads/default.aspx

SharePoint Designer 2010 BETA , SharePoint Foundations 2010 BETA (WSS 4.0) en Office 2010 BETA zijn ook gereleased. Happy downloading and experimenting!

Ohja.. Er zijn toch wel wat probleempjes. Voorlopig geen Win2k8 R2 installatie mogelijk
lees vooral http://bit.ly/2rNgl8 voor je je in dit avontuur stort