November, 2009

  • Jie Li's GeekWorld

    SharePoint Server 2010 Beta Key

    • 4 Comments

    Please do note this is BETA keys, not for trial, not for RTM. This should not be used with any implementation. I leave this post here just for record, nothing more. [11/18/2010]

     

    In case you can’t find it on download page after registration page:

    SharePoint Server 2010 Beta(Enterprise Client Access License features) product key:

    PKXTJ-DCM9D-6MM3V-G86P8-MJ8CY

    BV7VC-RMR6B-26P6Y-BTQDG-DX2KQ

    Both keys can be used. Feel free to post it elsewhere!

    EDIT: The second key is a wrong one. Thanks to Olivier Brin to point it out. That key is for search server trial. Please use the first one during beta period, we will also update download center to remove the second one.

    Jie.

  • Jie Li's GeekWorld

    OS Environment Comparison for SharePoint Server 2010 Beta Evaluation

    • 0 Comments

    SharePoint Server 2010 can be installed on Windows Vista, Windows 7, Windows Server 2008 and Windows Server 2008 R2. You can find installation steps for different OSes on MSDN: http://msdn.microsoft.com/en-us/library/ee554869(office.14).aspx . So is there any difference between these OSes when you want to play with SharePoint? Here’s a table to compare different configuration. If you have any suggestions on this table, please comment and I will update.

    Note: I’m not discussing SharePoint Foundation 2010 in this table. 

      Advantages Disadvantages
    Vista/Win7
    • Quickly switch to developing/demo environment by reboot
    • Hibernate/Sleep support
    • Possible to use all memory
    • No pre-req installer
    • useless services started
    • If it is not the main OS, then another partition is needed
    • If it is the main OS, SharePoint installation will likely to affect the performance of your other programs
    • If standalone installation and local account is used, then configuration/dev experience could be quite different from servers in domain enviroment
    Vista/Win7 Virtualized
    • I can’t see any reason… If you can virtualize a vista x64, then you should virtualize a server OS since you can always save states
    • No pre-req installer
    • useless services started
    • If standalone installation and local account is used, then configuration/dev experience could be quite different from servers in domain enviroment
    • If host machine does not have enough memory this could have performance problem
    • Performance is slower than real machine
    • 64bit virtualization software like Hyper-V, VritualBox and VMWare is required
    Win7 VHD Boot
    • All advantages for Win7
    • VHD can be put on the same partition with main OS
    • Possible to sysprep and redeploy image to other dev machine
    • Possible to use all memory
    • Good for dev or demo laptops
    • All disadvantages for Win7
    • If bitlocker is enabled, then VHD still need to be put on another partition
    • After sysprep, everything needs to be reconfigured.
    2008/2008 R2
    • Full experience of SharePoint Server 2010
    • Possible to use all memory
    • If it is not the main OS, then another partition is needed
    • If it is the main OS, SharePoint installation will likely to affect the performance of your other programs (it is always recommended to install SharePoint without any other progams on the machine)
    • Slower reboot process
    • Lack of device drivers for some hardware
    • Some companies do not allow dev to install Server OS
    2008/2008 R2 Virtualized
    • Full experience of SharePoint Server 2010
    • Can be moved and redistributed
    • Can use virtualization technology like save states, snapshots, live migration
    • Best way for developing/evaluation, if hardware requirement can be met
    • Can be used to build HA solutions
    • If host machine does not have enough memory this could have performance problem
    • Performance is slower than real machine
    • 64bit virtualization software like Hyper-V, VritualBox and VMWare is required
    2008 R2 VHD Boot
    • Full experience of SharePoint Server 2010
    • Possible to sysprep and redeploy image to other dev machine
    • Possible to use all memory
    • All disadvantages for Win2008/R2
    • If bitlocker is enabled, then VHD still need to be put on another partition
    • After sysprep, everything needs to be reconfigured.

    Remember – boot from VHD does not mean virtualization – it has nothing to do with virtualization at all. In that case, you can’t move such VHD directly to other machine. When you want to move the VHD, you have to sysprep it, which will lose all configuration on the system.

    So, for developers, I would suggest dual boot or VHD boot to Windows 7 or virtualization. For IT Pros, 2008/R2/virtualization should be the way to go for evaluation. But you should judge that yourself – it depends on your environment and your goal.

    Jie Li

    Technical Product Manager, SharePoint

  • Jie Li's GeekWorld

    Update Center for Office Products is now online

    • 0 Comments

    The update center for Office and SharePoint is online now.

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

    From now on, things like patches and updates will have an official place to communicate. You can subscribe to the RSS feed OfficeAndRelatedProductsUpdates if you want.

    I will stop doing the long CU blog post on SharePoint team blog. We will post a notice when something is available, and point customer to the update center for more information.

    Jie.

  • Jie Li's GeekWorld

    User Profile Sync Setup in SharePoint Server 2010 Beta

    • 20 Comments

    This is how I setup user profile sync for SharePoint Server 2010 Beta on my machine. You should not take this as an official guide. But the steps may help if you have been drive crazy. :)

    You should also check out TechNet article and the steps on our team blog first, they are more "official". And it's not come from "another MS guy in the wild" like me:)

    [Update - we are considering to gather all information and put it back to TechNet article, could be video walkthrough, screenshots, and hope that could help. After that is done, i may remove the content here.]

    The following steps in done on Windows Server 2008 R2. But it also applies to Windows Server 2008. The WCF fix for R2 and Win7 is not currently available to public but it will be released in coming days here.

    1. Start with a fresh SharePoint Farm installation, make sure WCF fix (Please refer to my pervious post) is already applied on the machine.
    2. A web application is already created at port 80. A site collection is also created.
    3. Don’t do anything on User Profile Service Application now…If you did, you may need to rebuild the farm. (am i kidding? no… this is beta.)
    4. Click System SettingsManage Services on server.
    5. Start Microsoft SharePoint Foundation User Code Service – this maybe not necessary, but I always do it first.
    6. If you are on Domain Controller, run the following script to make sure User Code Service has the right permission to run.
      $acl = Get-Acl HKLM:\System\CurrentControlSet\Control\ComputerName
      $person = [System.Security.Principal.NTAccount]"Users"
      $access = [System.Security.AccessControl.RegistryRights]::FullControl
      $inheritance = [System.Security.AccessControl.InheritanceFlags]"ContainerInherit, ObjectInherit"
      $propagation = [System.Security.AccessControl.PropagationFlags]::None
      $type = [System.Security.AccessControl.AccessControlType]::Allow
      $rule = New-Object System.Security.AccessControl.RegistryAccessRule($person, $access, $inheritance, $propagation, $type)
      $acl.AddAccessRule($rule)
      Set-Acl HKLM:\System\CurrentControlSet\Control\ComputerName $acl
    7. Start User Profile Synchronization Service. After you click the link, it should show something like this:
      snap0120
    8. Although the service is “Starting”, we can check the timer job if it is running properly. Click MonitoringCheck job status. Now you may find a job “ProfileSynchronizationSetupJob” is running. This may take several minutes to finish. If it finished instantly then something is wrong, you may have to rebuild it again.
      snap0119
    9. When it’s finished, the job will disappear from Running category. Now check Services again, user profile sync service should be “Started”.
      snap0121
    10. Time to setup connection! Click Application ManagementManage service applications. Scroll down to find and click User Profile Service Application. (Hint: you can copy the link to this item and add this to Resource links on Central Administration main page to save time in the future. You can do the same to Search and Managed Metadata.)
    11. It is possible that you get an empty status now. It’s okay.
      snap0122
    12. Click Configure Synchronization Connections.
    13. Oh – why I got this? “An error has occurred while accessing the SQL Server database or the SharePoint Server Search Service. If this is the first time you have seen this message, try again later. If this problem persists, contact your administrator.”
      snap0123
    14. Do a IISRESET in cmd line. Refresh the page,  problem solved.
      snap0124
    15. Now, click Create New Connection.
    16. Fill in your domain information. Choose the users or OU you want to import. Click Ok.
      snap0125  snap0126
    17. The connection you just created should be there. If not, you may need to rebuild. (I’m a bad guy, always telling you bad news.)
      snap0127
    18. Now go back to User Profile Service Application, the numbers should be shown on the side.
      snap0128
    19. You can choose to Start Profile Synchronization now. After some time, the number would change. It depends on the size of the OU you just chose.
      snap0129
    20. Click Manage User Profiles, and try to find a user. Yes, he is there!
      snap0130 

    Jie Li

    Technical Product Manager, SharePoint

  • Jie Li's GeekWorld

    Public Download for SharePoint 2010 Beta Products

    • 0 Comments

     

    Finally! Please note the OS requirement of SharePoint Fundation 2010 and SharePoint Server 2010 should be Windows Server 2008 x64 and Windows Server 2008 R2 only. We are working to correct those pages.

    The prerelease (beta) version is for evaluation purposes only.  Upgrade to the final release version is not supported.

    SharePoint Foundation 2010 Beta
    http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=906c9f5a-6505-4eba-bf24-95e423ac1703

    Microsoft SharePoint Server Enterprise 2010 Beta
    http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=77c30c6c-47fc-416d-88e7-8122534b3f37

    Microsoft SharePoint 2010 Products (Beta) Management Pack
    http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=c8a9d749-b7a8-412a-b2db-f3e464ed3fcf

    Microsoft SharePoint Foundation 2010 (Beta) Management Pack
    http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=43d5ee9a-b9a6-441d-a35e-8a7b9b15e20c

    Microsoft Office Web Apps (Beta)
    http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=27d81b1c-18ae-4983-8e1c-224bb747eb99

    Microsoft FAST Search Server 2010 for SharePoint Beta
    http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=bcc37c48-11fb-40a2-8cfb-743de20260f6

    Microsoft FAST Search Server 2010 for SharePoint Internet Sites Beta
    http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=aa37e8b0-c4d6-4452-a476-b81ee0bfbda5 

    Microsoft SharePoint Server for Internet Sites Enterprise 2010 Beta
    http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=580fc452-4948-44ab-9995-a0599271ad48

    Microsoft SharePoint Designer 2010 Beta (64-bit)
    http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=eeda9ab1-ac53-4870-9e1c-38940343d677

    Microsoft SharePoint Designer 2010 Beta (32-bit)
    http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=82df15bd-16a5-460e-a7c4-22599c669bb1

    Forefront Protection 2010 for SharePoint Beta 2

    Related FAST Documents on Download Center: 

    FAST Search Server Cmdlets Overview (Beta)

    FAST Search Server deployment and configuration (Beta)

    Known Issues – FAST Search Server 2010 for SharePoint (Beta)

    Planning and Architecture for FAST Search Server 2010 for SharePoint (Beta)

    FAST Search Server for SharePoint PowerShell Cmdlet Help (Beta)

    Monitoring for FAST Search Server

     

    You can refer to my pervious post for SharePoint Server 2010 Beta installation steps. 

    http://blogs.msdn.com/opal/archive/2009/11/16/installation-notice-for-sharepoint-2010-public-beta.aspx

     

    Jie Li

    Technical Product Manager, SharePoint

  • Jie Li's GeekWorld

    Installation Notice for SharePoint 2010 Public Beta

    • 41 Comments

    [3/9/2010 - WCF fix need to be installed after .Net Framework 3.5.1 is enabled (since it's a WCF fix, which is part of .Net Framework. Otherwise it cannot apply to the system. This fix will be automatically downloaded and installed by pre-requisite installer in RC/RTM build)

    [12/7 - +Office Web Apps on Win7] 

    [11/23 - added a short notice on win7+Office Web Application - this will not install and no workaround so far

    [11/21 - added setup keys in case people can't find them]

    [11/19 - updated user profile sync instructions - update WCF Fix for R2 and Win7 - update script for PowerPoint View/Edit] 

    Since SharePoint 2010 has been made available for MSDN/TechNet subscriber public now, here’re some steps you would like to follow to get a successful installation. But keep in mind: This beta is not supported and you CANNOT upgrade the installation to RTM when it’s released. This Beta should only be used for evaluation purpose.

    The public download of SharePoint Server 2010 Beta (Enterprise) is here:
    http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=77c30c6c-47fc-416d-88e7-8122534b3f37

    The key you can use is:

    PKXTJ-DCM9D-6MM3V-G86P8-MJ8CY

    BV7VC-RMR6B-26P6Y-BTQDG-DX2KQ This key should be avoided - it is a wrong key.

    Any one in the two would work. 

    Please note there's no technical difference between SharePoint Server 2010 + Enterprise CAL and SharePoint Server for Internet Sites Enterprise. It is only about licensing.

    1. Read hardware and software requirement article on TechNet.
    2. Prepare a Windows Server 2008 x64 machine with 8GB memory. Windows Server 2008 R2 requires a hotfix which is not yet released to have the service applications running so I don’t recommend to use that now which is released finally so now you can use it. Web Server Editions are not supported. Windows Server Fundation edition is not supported either. You can also install SharePoint 2010 on Windows 7 and Vista, however additional steps would be required as pre-requisite installer does not work currently on client OS.Windows 7 N and KN would not work due to an installer bug. Please also note Office Web Application cannot needs to follow the same edit of config.xml to be installed on client OS.

      If you give the machine very little memory, something like 2GB, and even have SQL Server running on the same machine, you would likely to get some timeout errors with service applications, for example, search and user profile.
    3. Get your AD ready. Create a new account for services, for example contoso\sp_admin.
      1.       Open Active Directory Users and Computers
      2.       Right click domain and select “Delegate Control”
      3.       Click Next
      4.       Click Add
      5.       Enter object name (i.e. contoso\sp_admin)
      6.       Click Ok
      7.       Click Next
      8.       Select “Create a custom task to delegate”
      9.       Click Next
      10.     Check "Replicating directory changes”
      11.     Click Next
      12.     Click Finish 
    4. Prepare SQL Server 2005/2008 envoriment. If it is on a different box, don't forget Windows Firewall settings. For SQL Server on Windows 2008/R2, you can use the script in KB968872 to open all necessary ports.
      1. SQL Server 2005 SP3 and CU3
      2. SQL Server 2008 SP1 and CU2
    5. Run Pre-Requisition Installer to download and install required components. You can also download them seperately. I listed all download links in SharePoint 2010 Pre-Requisites Download Links. The links are also available in requirement article, or by clicking “Learn more about…” in the installer.
    6. Install WCF FIX: A hotfix that provides a method to support the token authentication without transport security or message encryption in WCF is available for the .NET Framework 3.5 SP1 (Windows Server 2008, Windows Server 2008 R2) . Please note the 2008 fix also applies to Vista, while the 2008 R2 fix also applies to Windows 7.
      If you don't have this fix installed, you will get "Unrecognized attribute 'allowInsecureTransport'" error in ULS log. And most of the service applications will not run properly.
    7. Setup the farm using complete farm installation. Standalone installation is not recommended, and should be only used when you want to install SharePoint 2010 on Windows 7/Vista for dev purpose.
    8. Go with configuration wizard to setup all service applications. Use the user you created in step 3 as SharePoint Managed Account for services and web applications.
    9. Read Config Profile Synchronization to setup profile sync. Dave Pae is going to post complete steps for Profile Sync on SharePoint Team Blog. Follow the instruction on SharePoint Team Blog. You can also check my steps on how to setup user profile sync.
    10. If you are using SharePoint on DC, the following Windows PowerShell command would need to be run to enable Sandboxed Solutions.
      $acl = Get-Acl HKLM:\System\CurrentControlSet\Control\ComputerName
      $person = [System.Security.Principal.NTAccount]"Users"
      $access = [System.Security.AccessControl.RegistryRights]::FullControl
      $inheritance = [System.Security.AccessControl.InheritanceFlags]"ContainerInherit, ObjectInherit"
      $propagation = [System.Security.AccessControl.PropagationFlags]::None
      $type = [System.Security.AccessControl.AccessControlType]::Allow
      $rule = New-Object System.Security.AccessControl.RegistryAccessRule($person, $access, $inheritance, $propagation, $type)
      $acl.AddAccessRule($rule)
      Set-Acl HKLM:\System\CurrentControlSet\Control\ComputerName $acl

    11. If you are trying to use Office Web Apps on DC(Office Web Application need to be installed seperately, like a language pack or an update. Please also note that Office Web Application cannot be installed on needs to follow the same edit of config.xml to install on Windows 7), then the following commands need to be run to make the services work. Please note that in different languages, Service Application names could be localized. You can find them out by Get-SPServiceApplications, and then change the names in the script as necessary.

      Please do note that Office Web Apps is not supported on a DC. So this configuration should never be used in production.


      $e = Get-SPServiceApplication | where {$_.TypeName.Equals("Word Viewing Service Application")}
      $e.WordServerIsSandboxed = $false
      $e.WordServerIsSandboxed

      $p = Get-SPServiceApplication | where {$_.TypeName.Equals("PowerPoint Service Application")}
      $p.EnableSandboxedViewing = $false
      $p.EnableSandboxedEditing = $false
      $p.EnableSandboxedViewing
      $p.EnableSandboxedEditing
      #(Please use the below script for PowerPointServiceApplication - You need to enter "Y" for the answer of each cmd)
      Get-SPPowerPointServiceApplication | Set-SPPowerPointServiceApplication -EnableSandboxedViewing $false
      Get-SPPowerPointServiceApplication | Set-SPPowerPointServiceApplication -EnableSandboxedEditing $false

      In the server's c:\windows\system32\inetsrv\config\applicationHost.config
      Add the line below in the end of the dynamicTypes.
      <add mimeType="application/zip" enabled="false" />

      IISRESET

    12. Enable Developer Dashboard and turn to OnDemand for troubleshooting page performance issues. It can be done by STSADM or SharePoint 2010 Management Shell (Windows PowerShell).

      1. STSADM: stsadm -o setproperty -pn developer-dashboard -pv OnDemand

      2. Windows PowerShell:

        $svc=[Microsoft.SharePoint.Administration.SPWebService]::ContentService

        $ddsetting=$svc.DeveloperDashboardSettings

        $ddsetting.DisplayLevel=[Microsoft.SharePoint.Administration.SPDeveloperDashboardLevel]::OnDemand

        $ddsetting.Update()

    Happy SharePointing!

    Jie Li

    Technical Product Manager, SharePoint

Page 1 of 1 (6 items)