SharePoint 2010 Prerequisite Installer command options

The preparation tool installs the following prerequisites:

• Web Server (IIS) role
• Application Server role
• Microsoft .NET Framework version 3.5 SP1
• Microsoft Sync Framework Runtime v1.0 (x64)
• Microsoft Filter Pack 2.0
• Microsoft Chart Controls for the Microsoft .NET Framework 3.5
• Windows PowerShell 2.0
• SQL Server 2008 Native Client
• Microsoft SQL Server 2008 Analysis Services ADOMD.NET
• ADO.NET Data Services Update for .NET Framework 3.5 SP1
• A hotfix for the .NET Framework 3.5 SP1 that provides a method to support token authentication without transport security or message encryption in WCF.
• Windows Identity Foundation (WIF)

Prerequisites Download Links....

• Windows Server 2008 with SP 2 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 (http://go.microsoft.com/fwlink/p/?LinkID=160770)
• Windows Server 2008 R2 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 (http://go.microsoft.com/fwlink/p/?LinkID=166231)
• Microsoft .NET Framework 3.5 Service Pack 1 (http://go.microsoft.com/fwlink/p/?LinkId=131037)
• Windows Identity Foundation for Windows Server 2008 (http://go.microsoft.com/fwlink/p/?LinkID=160381)
• Windows Identity Foundation for Windows Server 2008 R2 (http://go.microsoft.com/fwlink/p/?LinkID=166363)
• Microsoft Sync Framework v1.0 (http://go.microsoft.com/fwlink/p/?LinkID=141237)
• Microsoft Office 2010 Filter Packs (http://go.microsoft.com/fwlink/p/?LinkId=191851)
• Microsoft Chart Controls for Microsoft .NET Framework 3.5 (http://go.microsoft.com/fwlink/p/?LinkID=141512)
• Windows PowerShell 2.0 (http://go.microsoft.com/fwlink/p/?LinkId=161023)
• Microsoft SQL Server 2008 Native Client (http://go.microsoft.com/fwlink/p/?LinkId=166505)
• Microsoft SQL Server 2008 Analysis Services ADOMD.NET (http://go.microsoft.com/fwlink/p/?linkid=160390)
• KB979917 - QFE for Sharepoint issues - Perf Counter fix & User Impersonation (http://go.microsoft.com/fwlink/p/?LinkId=192577)
  
  • For Windows Server 2008 SP2, download the Windows6.0-KB979917-x64.msu (Vista) file.
  • For Windows Server 2008 R2, download the Windows6.1-KB979917-x64.msu (Win7) file.
• ADO.NET Data Services Update for .NET Framework 3.5 SP1 (http://go.microsoft.com/fwlink/p/?LinkId=163519) for Windows Server 2008 SP2
• ADO.NET Data Services Update for .NET Framework 3.5 SP1 (http://go.microsoft.com/fwlink/p/?LinkId=163524) for Windows Server 2008 R2 or Windows 7
• Microsoft Silverlight 3 (http://go.microsoft.com/fwlink/p/?LinkId=166506)
• SQL Server 2008 R2 Reporting Services Add-in for Microsoft SharePoint Technologies 2010 (http://go.microsoft.com/fwlink/p/?LinkId=192588)
• SQL Server Remote BLOB Store installation package from the Feature Pack for Microsoft SQL Server 2008 R2. For the download, go to the Download Center(http://go.microsoft.com/fwlink/p/?LinkID=177388).
• Microsoft Server Speech Platform (http://go.microsoft.com/fwlink/p/?LinkID=179612)
• Speech recognition language for English (http://go.microsoft.com/fwlink/p/?LinkID=179613)
• Speech recognition language for Spanish (http://go.microsoft.com/fwlink/p/?LinkID=179614)
• Speech recognition language for German (http://go.microsoft.com/fwlink/p/?LinkID=179615)
• Speech recognition language for French (http://go.microsoft.com/fwlink/p/?LinkID=179616)
• Speech recognition language for Japanese (http://go.microsoft.com/fwlink/p/?LinkID=179617)
• Speech recognition language for Chinese (http://go.microsoft.com/fwlink/p/?LinkID=179618)

• 2010 Server Language Packs for SharePoint Server 2010, Project Server 2010, Search Server 2010, and Office Web Apps 2010 (http://go.microsoft.com/fwlink/p/?LinkId=197415)

Below links might not be updated ones...... use the below if above doesn't work......

Application Server Role, Web Server (IIS) Role
Microsoft Sync Framework Runtime v1.0 (x64)
(http://download.microsoft.com/download/C/9/F/C9F6B386-824B-4F9E-BD5DF95BB254EC61/
Redist/amd64/Microsoft%20Sync%20Framework/Synchronization.msi)
Microsoft Chart Controls for the Microsoft .NET Framework 3.5 (
http://download.microsoft.com/download/c/c/4/cc4dcac6-ea60-4868-a8e0-
62a8510aa747/MSChart.exe)
Microsoft .NET Framework 3.5 Service Pack 1
(http://download.microsoft.com/download/2/0/e/20e90413-712f-438c-988efdaa79a8ac3d/
dotnetfx35.exe)
Windows PowerShell 2.0 (http://download.microsoft.com/download/2/8/6/28686477-3242-4E96-9009-
30B16BED89AF/Windows6.0-KB968930-x64.msu)
http://go.microsoft.com/fwlink/?LinkID=166363" - Windows Identity Framework (Win2008 R2)
(http://download.microsoft.com/download/D/7/2/D72FD747-69B6-40B7-875BC2B40A6B2BDD/
Windows6.1-KB974405-x64.msu)
WCF fix for Win2008 SP2 (http://download.microsoft.com/download/6/8/1/681F5144-4092-489B-
87E4-63F05E95079C/Windows6.0-KB976394-x64.msu)
WCF fix for Win2008 R2 (http://download.microsoft.com/download/E/C/7/EC785FAB-DA49-4417-
ACC3-A76D26440FC2/Windows6.1-KB976462-v2-x64.msu)
Windows Identity Framework (Win2008 SP2) (
http://download.microsoft.com/download/D/7/2/D72FD747-69B6-40B7-875BC2B40A6B2BDD/
Windows6.0-KB974405-x64.msu)
SQL Server 2008 Native Client (http://download.microsoft.com/download/3/5/5/35522a0d-9743-4b8ca5b3-
f10529178b8a/sqlncli.msi)
Microsoft SQL Server 2008 Analysis Services ADOMD.NET
(http://download.microsoft.com/download/b/9/a/b9a78047-d269-4a25-88a1-
9c4321d90677/SQLSERVER2008_ASADOMD10.msi)
IIS management cmdlets 
SQL 2008 R2 Reporting Services SharePoint 2010 Add-in
Microsoft Server Speech Platform Runtime
Microsoft Server Speech Recognition Language - TELE(en-US)

***********************************************************************

To install the download prerequisites follow the steps given below…
Copy all the download prerequisite to a network shared folder.
Place each download in a designated folder.

Open the notepad and copy the following script into the notepad.

/SQLNCli:"\\TEOPAN\SP2010_Prerequisites\SQLNativeClient\sqlncli.msi"
/KB976462:"\\TEOPAN\SP2010_Prerequisites\KB976462\Windows6.1-KB976462-v2-x64.msu"
/IDFX:"\\TEOPAN\SP2010_Prerequisites\Win2K8R2\Windows6.1-KB974405-x64.msu"
/NETFX35SP1:"\\TEOPAN\SP2010_Prerequisites\.Net 3.5 SP1\dotnetfx35.exe"
/PowerShell:"\\TEOPAN\SP2010_Prerequisites\PowerShell 2.0\Windows6.0-KB968930-x64.msu"
/Sync:"\\TEOPAN\SP2010_Prerequisites\Sync framework1.0\Synchronization.msi"
/ChartControl:"\\TEOPAN\SP2010_Prerequisites\MS Chart Control\MSChart.exe"
/FilterPack:"\\TEOPAN\SP2010_Prerequisites\FilterPack\FilterPack64bit.exe"
/ADOMD:"\\TEOPAN\SP2010_Prerequisites\SQL Server 2008\SQLSERVER2008_ASADOMD10.msi"
/ReportingServices:"\\TEOPAN\SP2010_Prerequisites\Reporting Service Add-on\rsSharePoint.msi"
/Speech:"\\TEOPAN\SP2010_Prerequisites\Speech Platform\SpeechPlatformRuntime.msi"
/SpeechLPK:"\\TEOPAN\SP2010_Prerequisites\Speech Platform\MSSpeech_SR_en-US_TELE.msi"
/KB976394:"\\TEOPAN\SP2010_Prerequisites\Windows 2008 SP2\Windows6.0-KB976394-x64.msu"

Note-: Change IDFX parameter to IDFXR2 If you are installing this argument file in Windows Server 2008 R2.

Make changes with respect to the file locations for each pre-installer argument/parameter.
Once we are done with the changes save the file with the name ―PrerequisiteInstaller.Arguments.txt.
Copy this file to SharePoint installation folder.
Open the command prompt by typing command CMD.
Locate the SharePoint installation folder.
Type PrerequisiteInstaller.exe and hit enter key


*****************************************************************************
***Command Line Options***
/continue - This is used to tell the installer that it is continuing from a restart
/unattended - No user interaction. Exit codes:
  0    - Success
  1    - Another instance of this application is already running
  2    - Invalid command line parameter(s)
  1001 - A pending restart blocks installation
  3010 - A restart is needed
  Other error codes - From the prerequisite installation that failed last
/? - Display this message

The installer installs from the file specified in the command line options below where 'file' denotes the file to install from. If the option is not specified, it downloads the file from the internet and installs. If the option is not applicable to the current operating system, it ignores it.

 /SQLNCli:file - Install Microsoft SQL Server 2008 Native Client from file

 /ChartControl:file - Install Microsoft Chart Controls for Microsoft .NET Framework 3.5 from file

 /W2K8SP2:file - Install Windows Server 2008 SP2 from file

 /NETFX35SP1:file - Install Microsoft .NET Framework 3.5 SP1 from file

 /PowerShell:file - Install Windows PowerShell 2.0 from file

 /KB976394:file - Install Hotfix for Microsoft Windows (KB976394) from file

 /KB976462:file - Install Hotfix for Microsoft Windows (KB976462) from file

 /IDFX:file - Install Windows Identity Foundation (KB974405) from file

 /IDFXR2:file - Install Windows Identity Foundation (KB974405) for Windows Server 2008 R2 from file

 /Sync:file - Install Microsoft Sync Framework Runtime v1.0 (x64) from file

 /FilterPack:file - Install Microsoft Filter Pack 2.0 from file

 /ADOMD:file - Install Microsoft SQL Server 2008 Analysis Services ADOMD.NET from file

 /ReportingServices:file - Install SQL 2008 R2 Reporting Services SharePoint 2010 Add-in from file

 /Speech:file - Install Microsoft Server Speech Platform Runtime from file

 /SpeechLPKDEDE:file,/SpeechLPK:file,/SpeechLPKESES:file,/SpeechLPKFRFR:file,/SpeechLPKITIT:file,/SpeechLPKKOKR:file,/SpeechLPKPTBR:file and /SpeechLPKRURU:file - Install Microsoft Server Speech Recognition Language - TELE from file for de-de, en-us, es-es, fr-fr, it-it, ko-kr, pt-br and ru-ru locales respectively

Estimate RAM/memory requirements SQL server- SharePoint 2010

The memory required for SharePoint Server 2010 is directly related to the size of the content databases that you are hosting on a server that is running SQL Server.
As you add service applications and features, your requirements are likely to increase. The following table gives guidelines for the amount of memory we recommend.

Combined size of content databases	RAM recommended for computer running SQL Server
Minimum for small production deployments	8 GB
Minimum for medium production deployments	16 GB
Recommendation for up to 2 terabytes	32 GB
Recommendation for the range of 2 terabytes to 5 terabytes	64 GB
Recommendation for more than 5 terabytes	Additional RAM over 64 GB can improve SQL Server caching speed

Note:
These values are higher than those recommended as the minimum values for SQL Server because of the distribution of data required for a SharePoint Server 2010 environment. For more information about SQL Server system requirements, see Hardware and Software Requirements for Installing SQL Server 2008 (http://go.microsoft.com/fwlink/p/?LinkId=129377).

Other factors that may influence the memory required include the following:

• The use of SQL Server mirroring.
• The frequent use of files larger than 15 megabytes (MB).

How to estimate content database size

Estimate content database storage

The following process describes how to approximately estimate the storage required for content databases, without considering log files:

1. Calculate the expected number of documents. This value is referred to as D in the formula.
   
   How you calculate the number of documents will be determined by the features that you are using. For example, for My Sites or collaboration sites, we recommend that you calculate the expected number of documents per user and multiply by the number of users. For records management or content publishing sites, you may calculate the number of documents that are managed and generated by a process.
   
   If you are migrating from a current system, it may be easier to extrapolate your current growth rate and usage. If you are creating a new system, review your existing file shares or other repositories and estimate based on that usage rate.
2. Estimate the average size of the documents that you will be storing. This value is referred to as S in the formula. It may be worthwhile to estimate averages for different types or groups of sites. The average file size for My Sites, media repositories, and different department portals can vary significantly.
3. Estimate the number of list items in the environment. This value is referred to as L in the formula.
   
   List items are more difficult to estimate than documents. We generally use an estimate of three times the number of documents (D), but this will vary based on how you expect to use your sites.
4. Determine the approximate number of versions. Estimate the average number of versions any document in a library will have (this value will usually be much lower than the maximum allowed number of versions). This value is referred to as V in the formula.
   
   The value of V must be above zero.
5. Use the following formula to estimate the size of your content databases:
   
   Database size = ((D × V) × S) + (10 KB × (L + (V × D)))
   
   The value of 10 KB in the formula is a constant that roughly estimates the amount of metadata required by SharePoint Server 2010. If your system requires significant use of metadata, you may want to increase this constant.

As an example, if you were to use the formula to estimate the amount of storage space required for the data files for a content database in a collaboration environment with the following characteristics, you would need approximately 105 GB.

 

Input	Value
Number of documents (D)	200,000 Calculated by assuming 10,000 users times 20 documents
Average size of documents (S)	250 KB
List items (L)	600,000
Number of non-current versions (V)	2 Assuming that the maximum versions allowed is 10

Database size = (((200,000 x 2)) × 250) + ((10 KB × (600,000 + (200,000 x 2))) = 110,000,000 KB or 105 GB

SharePoint 2010 Vs SharePoint 2013 Preview

Features deprecated in SharePoint 2013 Preview

The following features and functionality have been deprecated or changed in SharePoint 2013 Preview.

Visual upgrade

Description: The visual upgrade feature in SharePoint Server 2010 is not available in SharePoint 2013 Preview. For the upgrade from Office SharePoint Server 2007 to SharePoint Server 2010, you could choose to use the visual upgrade feature to give site collection owners and site owners the opportunity to preserve the previous user interface temporarily while still upgrading the infrastructure and databases, site collections, and features to the latest version. This allowed site collection owners and site owners to update customizations to work in the new user interface. Once the database and site collection upgrade was complete, the user had the option to upgrade the user interface on a more granular level of the website (SPWeb object).

Reason for change: The visual upgrade feature is replaced with deferred site collection upgrade. The site collection upgrade process is not reversible. The deferred site collection upgrade is a more comprehensive upgrade process than visual upgrade.

Visual upgrade preserved only the old master pages, CSS files, and HTML files. Deferred site collection upgrade preserves much more, including SPFeature functionality. To achieve the deferred site collection upgrade, major changes in the architecture were required, including the removal of visual upgrade.

With deferred site collection upgrade, you can continue to use the UI from the previous version (SharePoint Server 2010) more seamlessly than is possible with visual upgrade. The master page, CSS, JScript, and SPFeatures will remain in SharePoint Server 2010 mode. One key difference is that the granularity of upgrading the user interface is per site collection (SPSite) instead of site (SPWeb). Users can still preview their site in the new SharePoint 2013 Preview user interface before committing. However, this is accomplished by creating and upgrading a temporary copy of their site collection instead of a preview in the existing instance of the site collection. The reason for previewing a copy of the site collection is because of the complexity of what occurs during site collection upgrade. Once a site collection is upgraded, it cannot be rolled back. Therefore, performing a preview would not be possible except in a copy of the site collection.

Migration path: Site collection administrators who are using visual upgrade to continue to use SharePoint Server 2007 must move to the SharePoint Server 2010 user interface before upgrading to SharePoint 2013 Preview. After the content database is upgraded, users can use deferred site collection upgrade to continue to use the SharePoint Server 2010 experience for their site collections. Site collection administrators can be notified by their farm administrator when a site collection is ready for upgrade and the site collection administrators can then choose to either perform the upgrade of their site collection or optionally first preview the new functionality in a temporary copy of their site collection.

Any SharePoint user interface might have dependencies on visual upgrade. The main dependency was getting the user interface version and then outputting the correct user interface (new or legacy). The visual upgrade API feature is updated so that the user interface version is remapped to the new site collection compatibility level property. This returns the same information about which version the site uses as before. Therefore, dependent code does not need to change.

Document Workspace site template

Description: When you create a site in SharePoint 2013 Preview, the Document Workspace site template is not available.

Reason for change: The scenario of collaborating on a document is now provided by the Team Site site template. The Document Workspace site template was removed from SharePoint 2013 Preview to simplify the list of templates that are available when a user creates a new site collection.

Migration path: Existing sites that were created by using the Document Workspace site template will continue to operate in SharePoint 2013 Preview. The Document Workspace site template will be removed completely from the next major release of SharePoint and sites that were created by using the Document Workspace site template will not be supported.

Personalization Site site template

Description: When you create a site in SharePoint 2013 Preview, the Personalization Site site template is not available.

Reason for change: The Personalization Site site template was not a widely used site template. The Personalization Site site template was removed from SharePoint 2013 Preview to simplify the list of templates that are available when a user creates a new site collection.

Migration path: Existing sites that were created by using the Personalization Site site template will continue to operate in SharePoint 2013 Preview. The Personalization Site site template will be removed completely from the next major release of SharePoint and sites that were created by using the Personalization Site site template will not be supported.

Meeting Workspace site templates

Description: When you create a site in SharePoint 2013 Preview, all five of the Meeting Workspace site templates are not available. This includes the Basic Meeting Workspace, Blank Meeting Workspace, Decision Meeting Workspace, Social Meeting Workspace, and Multipage Meeting Workspace.

Reason for change: SharePoint 2013 Preview and Office 2013 Preview provide other features that support meetings and collaboration. For example, you can use Lync to conduct live meetings, OneNote to take notes during meetings, and a SharePoint team site or My Site to store shared meeting notes.

Migration path: Existing sites that were created by using the Meeting Workspace site templates will continue to operate in SharePoint 2013 Preview. The Meeting Workspace site templates will be removed completely from the next major release of SharePoint and sites that were created by using the Meeting Workspace site templates will not be supported.

Group Work site template and Group Work solution

Description: When you create a site in SharePoint 2013 Preview, the Group Work site template is not available. This Group Work site template provides a groupware solution that teams can use to create, organize, and share information. The Group Work site template includes the Group Calendar, Circulation, Phone-Call Memo, document library, and other basic lists. The Group Work site template and the Group Work solution are discontinued and not available in SharePoint 2013 Preview.

Reason for change: The Group Work site template was not a widely used site template. The Group Work site template was removed from SharePoint 2013 Preview to simplify the list of templates that are available when a user creates a new site collection.

Migration path: Existing sites that were created by using the Group Work site template will continue to operate in SharePoint 2013 Preview. The Group Work site template will be removed completely from the next major release of SharePoint and sites that were created by using the Group Work site template will not be supported.

Visio Process Repository site template

Description: When you create a site in SharePoint 2013 Preview, the Visio Process Repository site template will continue to be available. However, the Visio Process Repository site template will be removed in the next major release of SharePoint.

Reason for change: The Visio Process Repository site template is not a widely used site template. The Visio Process Repository site template was removed from SharePoint 2013 Preview to simplify the list of templates that are available when a user creates a new site collection.

Migration path: Not required. The Visio Process Repository site template is available in SharePoint 2013 Preview.

Unghosting and customizing CSS files

Description: The following methods are included in SharePoint 2013 Preview, but will be removed from the next major release of SharePoint:

• Microsoft.SharePoint.SoapServer.Webs.CustomizeCss
• Microsoft.SharePoint.SoapServer.Webs.RevertCss

The Webs.CustomizeCss method applies style sheet customization to a particular file.

The Webs.RevertCss method reverts style sheet customization of a file to the default style sheet.

These two methods are stored in Webs.asmx.cs and are defined in Webswsdl.asps.

Reason for change: The methods are outdated and are no longer needed.

Migration path: None.

Imaging Web service

Description: The Imaging Web service provides functionality for creating and managing picture libraries. The Imaging Web service will be removed from the next major release of SharePoint. The Imaging Web service is included and supported in SharePoint 2013 Preview.

Reason for change: The Imaging Web service is not widely used. The only client application for the Imaging Web service, Office Picture Manager, is no longer included with SharePoint 2013 Preview. The Imaging Web service is being removed to reduce security vulnerabilities and to simplify the number of ways to connect to SharePoint 2013 Preview.

Migration path: All the functionality of the Imaging Web service is available through the client-side object model (CSOM). The CSOM provides client-side applications with access to a subset of the SharePoint Foundation server object model, including core objects such as site collections, sites, lists, and list items. Also, Web Distributed Authoring and Versioning (WebDAV) provides clients with key functionality of the Imaging Web service (for example, upload, download, and rename).

Excel Services — Can't edit workbooks in the browser that have external data connections

Description: Workbooks with external data connections that use Windows authentication cannot be refreshed in the browser. Instead, you are prompted to open the workbook in the Excel client program. Workbooks that have database or Windows credentials stored either in the Secure Store Service or in the connection string can still be edited in the browser. This change applies only when Excel Web App Preview in Office Web Apps Server Preview is used to view workbooks, not when Excel Services in SharePoint Server 2013 Preview is used.

Reason for change: This is a design limitation in SharePoint 2013 Preview.

Migration path: You can still refresh these workbooks in the Excel client program. Additionally, a service application administrator can configure that workbooks are viewed in SharePoint 2013 Preview instead of Office Web Apps Server Preview.

Web Analytics in SharePoint Server 2010

Description: Web Analytics in SharePoint Server 2010 has been discontinued and is not available in SharePoint 2013 Preview. Analytics processing for SharePoint 2013 Preview is now a component of the Search service.

Reason for change: A new analytics system was required for SharePoint 2013 Preview that included improvements in scalability and performance, and that had an infrastructure that encompasses SharePoint Online. The Analytics Processing Component in SharePoint 2013 Preview runs analytics jobs to analyze content in the search index and user actions that are performed on SharePoint sites.

SharePoint 2013 Preview still logs every click in SharePoint sites and still provides a count of hits for every document. User data is made anonymous early in the logging process and the Analytics Processing Component is scalable to the service.

This analytics data is used in SharePoint 2013 Preview to provide new item-to-item recommendation features, to show view counts that are embedded in SharePoint 2013 Preview and Search Server user interface, to provide a report of the top items in a site and list, and to influence the relevancy algorithm of search.

What happens to Web Analytics after upgrade: The Web Analytics Service is not upgraded to the Analytics Processing Component in SharePoint 2013 Preview. When you upgrade to SharePoint 2013 Preview, the databases that contain the data from Web Analytics in SharePoint Server 2010 are not removed. These databases are not used by or maintained by the Analytics Processing Component in SharePoint 2013 Preview. This means that documents on sites in SharePoint Server 2010 that are upgraded will show a hit count of 0.

When you upgrade to SharePoint 2013 Preview, do not attach and upgrade the databases that contain the data from Web Analytics in SharePoint Server 2010. We recommend that you turn off Web Analytics in the SharePoint Server 2010 environment before you copy the content databases that you want to upgrade to SharePoint 2013 Preview.

Reports from Web Analytics for the top items in a site are carried forward. Reports that show browser traffic, top users of a site, and referring URL are not carried forward and are not used by the Analytics Processing Component in SharePoint 2013 Preview.

Administrative reports for the quota usage of site collections in the farm are not available in SharePoint 2013 Preview.

SharePoint 2013 Preview does not support the Web Analytics Web Part. After a farm is upgraded to SharePoint 2013 Preview, all instances of a Web Analytics Web Part will not function. The page that includes the Analytics Web Part will render and a message appears that informs the user that the Web Part is no longer supported.

Migration path: None. Data collection for Analytics Processing in SharePoint 2013 Preview starts immediately for sites, including SharePoint Server 2010 sites.

SharePoint 2013 /15 Training videos for IT pro

http://technet.microsoft.com/en-us/sharepoint/fp123606.aspx

Nice videos and articles from MS

Activate Blackberry internet service on unlocked bold 9650 from other country like USA

Hi,
       Most of the users who had been using blackberry handset in other countries like USA, who come to India face issues with activating blackberry services. I had the blackberry bold 9650 handset from Verizon which works on both CDMA and GSM. The set worked fine in USA. The problems started when I started using it in India, with little or no help from customer care of mobile operator, who normally don't have any clue on how to configure blackberry handset.

Few of the problems which I faced are mentioned below....

• upon activation of 3g services, the EDGE icon next to signal bars will display as edge (lower case).
• Host routing table will not have entries in spite sending many successful registration messages.
• Service Books will not have entries for Blackberry Internet service.
• Customer care will give you absurd reasons for his/her technical incompetency or no knowledge about how blackberry works or is configured.
• CC will even try to blame your unlocked phone, stating that it's still locked to previous operator and cannot be activated.

The fact is all the above myth told to you by customer care is false. I knew I had an unlocked phone as I unlocked it myself. So there was no question of phone being still locked to Verizon. I assume that you have already activated your BIS/BES plan for your phone prior to following the steps given below.

Steps to I did to resolve this...

•  Changed the GSM/umts network settings to 1x/EV (CDMA), even though the GSM sim was inserted.
• Switched off the phone. Even took out battery and placed it back
• booted the phone again.
• Phone catches the signal of CDMA operator whose PRL is uploaded into phone.
• In my case I uploaded the TATA indicom PRL file and replaced the Verizon prl file.
• Clear log by pressing alt+L + Alt+G + Alt+L + Alt+G and press call key.
• Press BB menu button and select clear log
• Goto network settings and select GSM/UMTS from dropdown.
• Phone search for the GSM signal matching the sim card and this time it will show "EDGE" instead on "edge" next to signal bar.
• Go to Host routing table and press BB menu button and select register now.
• You will get message registration message sent.
• Check messages and you will see a HRT message in message box.
• After few seconds you should get another message stating that your mobile is registered.
• Check Host routing table and you will now see values.
• Check service books to make sure all entries related to BIS is present there.
• Go back to network operator's blackberry registration site.
• In my case it was vodafone so registered a new user at site
  https://hutch.blackberry.com/html?brand=hutch .
• Prior to registering to site make sure host routing table has entries.
• Once it's registered, you can add email accounts on the site that will be automatically synced to your phone in couple of minutes.

Service Architecture model for SharePoint 2010

Here are some videos I found on MS site

Service Architecture intro

Architectural and Logical Overview

Creating Custom Service Applications

The BlackBerry® Client for Microsoft® SharePoint

The BlackBerry® Client for Microsoft® SharePoint® enables secure enterprise collaboration and puts essential team resources and document management tools into the hands of mobile professionals.

View Demo

Document-based mobile collaboration for
BlackBerry smartphones

Securely check out, download, edit, upload, check in and send links to shared documents from anywhere in the world.


Add calendar events directly from a SharePoint calendar into your BlackBerry calendar, and add BlackBerry calendar appointments into SharePoint to stay in sync with team members.


Find content, edit documents and manage events easily, thanks to tight integration with core BlackBerry applications such as email, calendar and Documents To Go®.

Secure and manageable for IT

Leverages existing BlackBerry® Infrastructure and support, while providing robust and scalable mobile access to Microsoft® SharePoint®.


Allows users to work with Microsoft SharePoint content without repeated logins, thanks to NTLMv2 support.



Lets mobile users collaborate quickly on documents without emailing them or saving copies to their computers.


Provides trusted BlackBerry security and IT policies, and respects Microsoft SharePoint access controls.

Source -: http://in.blackberry.com/business/software/sharepoint/

Install Nero 11 on Windows server 2008 R2 and Windows 8

According to the Nero 11 page, Nero 11 supports all modern Windows operating systems, including Windows 7. And according to Microsoft, software that work on Windows 7 should work fine on Windows 8 as well. So, that means Nero 11 should work fine on Windows 8 but it doesn’t! In fact, you can’t install Nero 11 on Windows 8 Or windows server 2008/R2 When you try to install Nero 11 on Windows 8, you get “Nero requires that your computer is running Windows XP at least SP3, Windows Vista with at least SP1, or Windows 7” error.

Running Nero 11 setup in compatibility mode doesn’t help either. 

Users who have a legal copy of Nero 11 and can’t live without Nero 11 on Windows 8 may want to know a possible workaround to install Nero. If you are one of the early adopters of Windows 8 and missing Nero 11 on Windows 8, then you’ll be glad to know that it’s possible to install Nero 11 software on Windows 8 with a simple workaround.

Procedure:

Step 1: First things first. Download your copy of Nero 11 from here. You may need to provide your email address to download a trial copy from Nero web page. Users who have a copy of Nero 11 on CD may skip this step.

Step 2: Run the setup and proceed until you get “Nero requires that your computer is running Windows XP at least SP3, Windows Vista with at least SP1, or Windows 7” error. Click Ok button to cancel the installation.

Step 3: Open Run dialog (use Windows + R keys). In the Run dialog box, type %temp%and press enter key to launch Temp folder.

Step 4: Here, locate the folder named NeroInstallFiles and copy the folder to your desktop (or any other location).

Step 5: Open NeroInstallFiles folder and locate nero.mmstrial.msi file. Do a right-click on the file, select Properties. Switch to Compatibility tab, and then select Run this program in compatibility mode for Previous versions of Windows option. Click Apply button.

Step 6: Now run nero.mmstrial.msi file and follow the normal installation procedure to install Nero 11 on your Windows 8 PC without any issues. Do note that you need at least 5 GB of free disk space on your Windows 8/Windows server 2008 drive to be able to install Nero 11.

Changes required for Windows Server 2008/R2-:

1.  Download Orca MSI Editor (alt link ) and install it.
2. Search for .msi files in the  NeroInstallFiles folder.
3. Right click first msi file and select "Edit with OCRA" from the menu.
4. Select "Launch Condition" from left-hand side window pane
5. Edit the "Condition" value and remove the word "Not" (without quotes) from the last ( Remember not to remove the first Not word)
6. Save the msi and close ocra.
7. Repeat the above steps for all msi files.
8. Also replace the contents of file oslist.txt located inside the folder <Nero install folder>\ISSetupPrerequisites\systemRequirementValidator with the below...

#White/Black list (+/-): Arch Major.Minor.SP.Build

#x32 systems

#XP SP3+

Arch=32 OS=5.1 SP>=3

#Vista SP1+

Arch=32 OS=6.0 SP>=1

#Win7 SP RTM and higher

Arch=32 OS>=6.1.0.7600

#Vista SP1+

Arch=64 OS=6.0 SP>=1

#Win7 RTM and higher

Arch=64 OS>=6.1.0.7600

#Windows Server 2008, 2008 R2 (ProductType!=VER_NT_WORKSTATION)

OS>=6.0 ProductType=1

OS>=6.1 ProductType=1

#Win7 SP SP2 and higher

Arch=32 OS=6.1 SP>=2

Arch=64 OS=6.1 SP>=2

#Win8 and higher

OS>=6.2

Post modifying all MSI files start the setup again and this time you should be able to install Nero on windows 2008 server /R2. Contact me if you face any issues.

Modify sandbox code/solution execution timeout value using powershell

Default value of sandbox code/solution execution timeout is 30 seconds, there are times when one needs to increase this value to get complex code executed.

To view execution timeout value use following PS command-:

Write-Host $uc.ResourceMeasures["CPUExecutionTime"].AbsoluteLimit

Write-Host $uc.ResourceMeasures["CPUExecutionTime"].ResourcesPerPoint

To Modify above values use the following PS Commands-:

1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
2. $uc=[Microsoft.SharePoint.Administration.SPUserCodeService]::Local
   $uc.ResourceMeasures["CPUExecutionTime"].AbsoluteLimit = <LimitValue>$uc.ResourceMeasures["CPUExecutionTime"].ResourcesPerPoint = <PointValue>$uc.ResourceMeasures["CPUExecutionTime"].Update()$uc.Update()
   Where:
   
   
   • <LimitValue>
    is the new maximum limit value.
   • <PointValue>
    is the new number of resources per resource point.

For more information on sandbox solutions refer to the this link.