Download 2010 Information Worker Demonstration Virtual Machine (Beta) from Microsoft

I bit happy about the Microsoft have just released the newly configured Virtual Machine built for Microsoft SharePoint 2010 R2. now I can demonstrate the latest beta of Office 2010 and SharePoint 2010 in an information worker scenario to my customers? 

In order to run this demo you will need the following hardware:
- Windows Server 2008 R2 with the Hyper-V role enabled
- Intel VT or AMD-V capable processor
- 8 GB or more RAM
- 50 GB of NTFS-formatted hard disk space required for install

Download it from Microsoft Download Center

It has two sets of VM

Virtual Machine “A” has the following pre-configured software’s

- Windows Server 2008 SP2 Standard Edition x64, running as an Active Directory Domain Controller for the “CONTOSO.COM” domain with DNS and WINS

- Microsoft SQL Server 2008 SP1 + CU2 Enterprise Edition with Analysis, Notification, and Reporting Services

- Microsoft Office Communication Server 2007 R2

- Visual Studio 2010 Beta 2 Ultimate Edition

- Microsoft SharePoint Server 2010 Enterprise Edition Beta 2

- Microsoft Office Web Applications Beta 2

- FAST Search for SharePoint 2010 Beta 2

- Microsoft Project Server 2010 Beta 2

- Microsoft Office 2010 Beta 2

- Microsoft Office Communicator 2007 R2

Virtual Machine “B” contains the following pre-configured software’s

- Windows Server 2008 R2 Standard Evaluation Edition x64, joined to the “CONTOSO.COM” domain

- 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, with “contoso\administrator” granted administrator permissions. SharePoint Server 2010 has been configured in a “Complete” farm using Kerberos authentication and the default SQL Server 2008 instance for data, and has a site collection created using the Team Site template at http://intranet.contoso.com/ and a FAST Search Center at http://intranet.contoso.com/search/.

Performance Considerations

If possible, unpack and run the VM image on a separate, fast hard drive (7200 RPM or better) from the operating system of the host machine. If this is being done on a laptop, a second internal drive or external eSATA drive works best, though USB 2.0 (make sure it’s 2.0, 1.1 is too slow) or Firewire is acceptable.

For absolute best performance use a second internal SSD drive.

Planning for Upgrade from SharePoint Portal Server 2003 to SharePoint Server 2010

On the Configuration part of side… In order to upgrade to SharePoint Foundation 2010 or SharePoint Server 2010, you must first be running Windows SharePoint Services 3.0 at SP2 or Microsoft Office SharePoint Server 2007 at SP2, respectively. For customers running prior versions of SharePoint, including Windows SharePoint Services 2.0 and SharePoint Portal Server 2003, this means that you must first upgrade to Windows SharePoint Services 3.0 SP2 or Microsoft Office SharePoint Server 2007 SP2 prior to upgrading to 2010 versions. Windows SharePoint Server 3.0 with SP2 is available as a free download, and trial versions of Microsoft Office SharePoint Server 2007 are available and supported for use in this upgrade/migration process: SP2 Slipstream Downloads and Trial Versions Windows SharePoint Services 3.0 (32-bit) with SP2 http://www.microsoft.com/downloads/details.aspx?FamilyId=EF93E453-75F1-45DF-8C6F-4565E8549C2A Windows SharePoint Services 3.0 (64-bit) with SP2 http://www.microsoft.com/downloads/details.aspx?familyid=9FB41E51-CB03-4B47-B89A-396786492CBA Microsoft Office SharePoint Server 2007 Trial Version (32-bit) with SP2 http://www.microsoft.com/downloads/details.aspx?FamilyId=2E6E5A9C-EBF6-4F7F-8467-F4DE6BD6B831 Microsoft Office SharePoint Server 2007 Trial Version (64-bit) with SP2 http://www.microsoft.com/downloads/details.aspx?familyid=3015FDE4-85F6-4CBC-812D-55701FBFB563 Please note that the trial product versions are licensed for 180 days of use from the date of installation. Upgrade Method This upgrade process should be done using the Database Migration approach documented in the following links: Windows SharePoint Services and Microsoft Office SharePoint Server 2007 Determine upgrade approach (Office SharePoint Server) http://technet.microsoft.com/en-us/library/cc263447.aspx Determine upgrade approach [Windows SharePoint Services] http://technet.microsoft.com/en-us/library/cc287821.aspx SharePoint Foundation 2010 and SharePoint Server 2010 (pre-release documentation) Determine upgrade approach (SharePoint Server 2010) http://technet.microsoft.com/en-us/library/cc263447(office.14).aspx Determine upgrade approach (SharePoint Foundation 2010) http://technet.microsoft.com/en-us/library/cc287821(office.14).aspx Note that this method is referred to as “Database attach upgrade” in pre-release documentation Please note that there are manual steps involved in this upgrade path in order to maintain some configuration information, as documented in the links above. Example Upgrade Sequence The upgrade documentation above should be referenced for full detail and information, but the following illustrates an example of an upgrade sequence for moving from Office SharePoint Server 2007 to SharePoint Server 2010. 1. Prepare Farms a. Set up a small, temporary farm running Office SharePoint Server 2007 b. Set up full SharePoint 2010 farm and verify that it is configured and running correctly 2. Upgrade content from 2003 to 2007 a. Detach the content databases from the 2003 farm and take the 2003 farm offline b. Attach the content databases to the 2007 farm and upgrade them c. Verify the content has upgraded and that the 2007 farm is working correctly 3. Upgrade content from 2003 to 2007 a. Detach the content databases from the 2007 farm b. Attach the content databases to the SharePoint Server 2010 farm and upgrade them in parallel c. Verify the content has upgraded to SharePoint 2010 and is working correctly 4. Start serving requests on the SharePoint Server 2010 farm Again, this is just an example for illustration: for full detail, including all steps and important considerations, please review the existing and pre-release documentation linked above. Additional Information and Notes Please note that SharePoint Server 2010 Beta cannot be upgraded to the final release version (RTM). Any use of these steps or guidelines with any pre-release version of SharePoint 2010 should be for testing/evaluation only. This upgrade path will necessarily mean a move from 32-bit OS architecture to 64-bit OS architecture. Windows SharePoint Services 2.0 and SharePoint Portal Server 2003 were supported only on 32-bit operating systems, as opposed to SharePoint Foundation 2010 and SharePoint Server 2010, which are supported only on 64-bit operating systems. The database platform selected for Microsoft Office SharePoint Server 2007 or Windows SharePoint Services 3.0 should be consistent with the planned platform for Microsoft SharePoint Server 2010 or Microsoft SharePoint Foundation 2010. For example, if SQL Server 2008 will serve as the database software for the Microsoft Office SharePoint Server 2007 or Windows SharePoint Services 3.0 trial versions you should maintain that version for Microsoft SharePoint Server 2010 or Microsoft SharePoint Foundation 2010 to avoid downgrade support limitations such as SQL Server 2008 to SQL Server 2005. For additional information on SQL Server 2008 downgrade rights see: SQL Server 2008 Licensing Frequently Asked Questions http://www.microsoft.com/sqlserver/2008/en/us/licensing-faq.aspx

Working with PowerShell in SharePoint 2010

It’s is really good to see the way the PowerShell interacts with the SharePoint 2010. I can say that this PowerShell scripting is really an extended form of the STSADM utility with additional programmatically features which can be achieved through batch files.
In this post I am going to show you how PowerShell works… and some tips and tricks for the PowerShell module on the SharePoint 2010
Let’s us create a new Web under the PowerShell console for the SharePoint 2010. To create a new Web under the existing Site Collection, PowerShell scripting will use the following command
“New-SPWeb”
The following are the input parameters for the respective command.
SYNTAX
New-SPWeb
[-Url] <String>
[-Language <UInt32>]
[-Template <SPWebTemplatePipeBind>]
[-Name <String>]
[-Description <String>]
[-AddToQuickLaunch]
[-UniquePermissions]
[-AddToTopNav]
[-UseParentTopNav]
[-AssignmentCollection <SPAssignmentCollection>]
[-Verbose]
[-Debug]
[-ErrorAction <ActionPreference>]
[-WarningAction <ActionPreference>]
[-ErrorVariable <String>]
[-WarningVariable <String>]
[-OutVariable <String>]
[-OutBuffer <Int32>]
[-WhatIf]
[-Confirm]

PowerShell provides us a set of commands which draws out the SharePoint Out-Off-Box functionalities and also it extends the SharePoint Object model.

Write-Host “Defining variables for creating a new Web under the different Site Collection”
# define variables for script
$SiteTitle = “Lab 1 – Getting Started”
$SiteUrl = “http://sharepoint2010v/Lab01/”
$SiteTemplate = “STS#0″
Write-Host “Creating a new SharePoint Web under the URL – “ $SiteUrl
PS C:\> New-SPWeb -Url $SiteUrl -Template $SiteTemplate -Name $SiteTitle
Write-Host “New SharePoint Web has been successfully created.”

Pack the above code snippet in a notepad and save it as CreateNewSite.ps1

Powershell -Command “& {.\CreatenewSite.ps1}” -NoExit
pause

Again pack the above two lines of code as a batch file and save it as “ExecuteNewSiteCreation.bat”
Now, run the above created “ExecuteNewSiteCreation.bat” file. PowerShell creates a new Web under the specified Site Collection…
Note: you should modify the “$SiteUrl” variable in order to execute the above scenarios.

Happy programming… will see more updates on the Powershell developement on SharePoint 2010…

A Fresh move towards the UP – navigation button embedded on the SharePoint 2010 ribbon.

This enables the end users to access the site hierarchy very quickly. Microsoft had implemented this instead of the breadcrumb.

Nicely carried out this design… Happy delving…

SharePoint 2010 Videos Revealed – Development Experience

If you are curious what the development experience are gonna be in SharePoint 2010, there are now 10 modules with multiple videos per module that go through the details of using Visual Studio 2010 to customize your Microsoft SharePoint Foundation

Here are the links to the 10 video modules:

Module 1: Getting Started: Building Web Parts in SharePoint 2010

Module 2: What Developers Need to Know About SharePoint 2010

Module 3: Building Blocks for Web Part Development in SharePoint 2010

Module 4: Accessing SharePoint 2010 Data and Objects with Server-Side APIs

Module 5: Accessing SharePoint 2010 Data and Objects with Client-Side APIs

Module 6: Accessing External Data with Business Connectivity Services in SharePoint 2010

Module 7: Developing Business Processes with SharePoint 2010 Workflows

Module 8: Creating Silverlight User Interfaces for SharePoint 2010 Solutions

Module 9: Sandboxed Solutions for Web Parts in SharePoint 2010

Module 10: Creating Dialog Boxes and Ribbon Controls for SharePoint 2010

My Gnani is on Sharepoint hunt to Malaysia

—–Original Message—–
From: gnanavelb@zylog.co.in [mailto:gnanavelb@zylog.co.in]
Sent: Monday, February 02, 2009 9:32 AM
To: Murali Rama Krishnan; Sudharsan K
Subject: Reg: I am in Malaysis – JOHOR

Hi Friends,

I am fine here. What about you?.

I will send my contact number and skype Id today.

Thanks,
Gnanavel B.

——————————————————————–
mail2web – Check your email from the web at

http://link.mail2web.com/mail2web

SharePoint Designer encountered an error generating the initiation form

The root activity type is invalid

Assembly information for one or more assemblies referencing a type is missing from the safe list in the web.config file.
On the server, revert the web.config file in the root directory to the original version. This may require a clean install of Microsoft Office SharePoint Server 2007 or Microsoft Windows SharePoint Services 3.0.
(or)
Make sure that the following markup is present in your web.config file. You can copy the necessary sections or the entire markup as necessary.

<authorizedType Assembly="System.Workflow.Activities, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Namespace="System.Workflow.*" TypeName="*" Authorized="True" />
<authorizedType Assembly="System.Workflow.ComponentModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Namespace="System.Workflow.*" TypeName="*" Authorized="True" />
<authorizedType Assembly="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" Namespace="Microsoft.SharePoint.Workflow" TypeName="SPWorkflowActivationProperties" Authorized="True" />
<authorizedType Assembly="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" Namespace="Microsoft.SharePoint.Workflow" TypeName="SPWorkflowTaskProperties" Authorized="True" />
<authorizedType Assembly="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" Namespace="Microsoft.SharePoint.Workflow" TypeName="SPWorkflowHistoryEventType" Authorized="True" />
<authorizedType Assembly="Microsoft.SharePoint.WorkflowActions, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" Namespace="Microsoft.SharePoint.WorkflowActions" TypeName="*" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System" TypeName="Guid" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System" TypeName="DateTime" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System" TypeName="Boolean" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System" TypeName="Double" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System" TypeName="String" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.Collections" TypeName="Hashtable" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.Collections" TypeName="ArrayList" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.Diagnostics" TypeName="DebuggableAttribute" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.Runtime.CompilerServices" TypeName="CompilationRelaxationsAttribute" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.Runtime.CompilerServices" TypeName="RuntimeCompatibilityAttribute" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System" TypeName="Int32" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System" TypeName="TimeSpan" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.Collections.ObjectModel" TypeName="Collection`1" Authorized="True" />
<authorizedType Assembly="System.Workflow.Runtime, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Namespace="System.Workflow.Runtime" TypeName="CorrelationToken" Authorized="True" />
it solved my problem…

hurry, happy coding…

Edit Page option missing from default list template pages…

After a long back… while working on the clients module (related with the lists in sharepoint)
i’ve noticed that the Edit Page option from the Site Settings menu were missing on pages that uses the default list item templates pages…
(e.g. NewForm.aspx, EditForm.aspx, and DispForm.aspx)

this is beacuse all other respective template pages does’t contains even single webpart zone in the Sharepoint application pages.
to do so, 

Steps to enable the Edit Page Option in the Site Settings Menu in the SharePoint…

• Click the New item for the respective List from the Sharepoint
• After navigating to the NewForm.aspx – you may notify that the Edit Page option in the Site Setting menu were been disabled…
• Click the Edit with Microsoft SharePoint Designer from the File menu of the Internet Explorer.
• Click the list form webpart and create a new space near to that… make sure the &nbsp; is been added in source view of the Sharepoint Designer.
• Add a Webpart Zone on the respective area
• (Optional) You can add a webpart to test wheather the updraft scenorio matches (for e.g. DataView Webpart)…
• Now the you can edit the NewForm.aspx page with custom Webparts…

• 

  NewForm.aspx

  

  EditForm.aspx

  

  DispForm.aspx

  
  

  

  Add a Webpart Zone on the respective area

  

  Adding a Webpart

  

  Enabled Edit Page in Site Setings Menu

  
  
  

Alternate options for the developers who create a custom list template defenitions through the Visual studio Extension for SharePoint Project template

• Go Create New Project -> Pick the list template with (Custom List).
• Double click the NewForm.aspx and add the following lines of code to enable the edit page option in site settings menu…
  <WebPartPages:WebPartZone runat="server" Frametype="TitleBarOnly" id="Zone1" Title="loc:Right"><ZoneTemplate></ZoneTemplate></WebPartPages:WebPartZone>
• Make sure you have added above code to all custom list template page (e.g. EditForm.aspx, and DispForm.aspx)

Cheers…