Tag Archives: product

SharePoint rock star wanted for Europe

Following the success of Winshuttle’s product suite as an effective way of utilising the SharePoint platform for SAP process optimisation, we are ramping up our global SharePoint competencies. We have an immediate opening for a highly motivated SharePoint rock star in Europe.

We are looking for a consultant with solid SharePoint experience who can work directly with business units to compose solutions. Are you interested? You will be helping customers to optimise SAP processes through the use of Winshuttle and SharePoint technologies. Prior experience with SAP is desired but not a must.

This is an awesome role where you will be part of a strategically important Acceleration Team where the primary objectives are customer readiness and enablement. As such, your focus will be on short and sharp engagements that prove the value of Winshuttle software and help customers to hit the ground running.

Key responsibilities include project scoping, solution architecture and proof-of-concept delivery. Expect to be working with many different customers across Europe. Ideally, you should be based out of our EMEA head office in London, but we would be willing to consider other arrangements.

I’ll be in Berlin for the European SharePoint Conference, 17th through 20th of October, and in London during the first week of November. If you are interested, please drop me a line (kristian dot kalsing at winshuttle dot com) and we can arrange to meet up for a chat. This will be a lot of fun!


Read More

Quick Start programme for SharePoint

IRW have developed an effective ‘Quick-Start’ programme for SharePoint understanding and adoption within an organisation.
IRW’s KickStart for SharePoint is an approach designed for businesses or departments that want to utilise the core SharePoint product features and explore the possible maximisation of the product. The KickStart for SharePoint includes the following deliverables:
•Project Definition, Initiation and Requirements Definition
•Analysis and consultancy work regarding these requirements
•Initial SharePoint customisation and deployment
•Training/Knowledge Transfer sessions
•Workshop and presentation on options, benefits and roadmap going forward
•Project Report, Benefits review and forward planning
IRW’s KickStart for SharePoint provides a number of benefits; it allows your organisation to see the potential of Microsoft Office SharePoint, gain acceptance and buy-in from users, and the business, but from a very low initial cost base. The length of engagement is 10 days. Additional days can be added as needed after the initial engagement.
For more information visit IRW Systems and SharePoint
Read More

Transforming your Enterprise Business

One of the best parts of my job is the opportunity I have to talk with our partners. The Microsoft Project partner ecosystem is dedicated, vast and highly skilled! They provide a great deal of insight on deployment, adoption and overall feedback which is important to us for business and product planning.

With many of our Project partners’ businesses doing really well given the industry Project Management demand, it gives us an opportunity to talk about the future. A common discussion topic is how partners should think about their business over the next few years with the explosion of devices, democratization of IT, shift to the cloud and constant desire for change and innovation with tight budgets. These factors aren’t Project or Microsoft specific rather they are relevant to the software industry.

In our discussions, two themes that generally emerge are Cloud and Partner-to-Partner opportunities. These incidentally were also the focus at WPC this year.

The Cloud. The word “cloud” is overloaded – it could mean Public Cloud (for eg. Office 365, Azure, Salesforce) or Private Cloud (for eg. Hyper-V, VMWare). And each one of these can be sub-segmented even further: Software as a Service (SaaS), Platform as a Service, Infrastructure as a Service, etc. In any case, the reality is that the cloud is an important business consideration and a current technology trend. Microsoft is leading with the cloud and uniquely positioned to offer services for On-Premises and the Cloud. And whether you are a System Integrator (SI) or Independent Software Vendor (ISV), the cloud is something that you should consider for your product and business strategies. Here is one way to think about your business if you’re a partner that is enterprise focused today:

- Enterprise market. The cloud offers a new way for enterprises to deploy (eg. don’t have to install software, manage hardware, etc)  and purchase software (eg. pay subscription fee, don’t have to buy server hardware, etc). As a partner, this means you want to focus on business scenarios, adoption, interoperability, migration and customization. There’s a lot of opportunity in this space and an opportunity to engage your existing customers and help them move to the cloud.

- Small & Medium Business (SMB) market. The cloud offers a unique way to reach new customers that weren’t able to install and manage “enterprise” software in the past. In this case, these are potential new customers to the industry. And while this represents an entirely new opportunity space, the partner engagement and business model is quite different. SMB customers are not necessarily looking for deep engagements; rather, they are interested in lighter involvement to get their solution up and running. The number of users are much smaller than enterprise customers and in this space, you’re potentially looking at a larger volume of customers with less users each. If you’re a partner that’s traditionally focused on enterprise customers, the questions are 1) are you interested in the SMB market and 2) if you are, how will you transform your business to have lighter touch, higher volume engagements that are similar in nature to the SaaS business model of subscription payments?

Partner-to-Partner.
Think about how you can offer additional services and scale your business by partnering with other partners. Before you start reaching out to partners, think about the types of partnerships you need to be successful and then recruit and invest in select partners. Be thoughtful on what your business drivers are and which partnerships will help you build your business. For example, do you need to partner with a hoster? Do you need resellers? A training company? An outsourcing company? Or even someone in the same space as you with broader global reach? And while these questions seem very straightforward, many partners don’t invest the time to think about their own partner strategy. It’s important for someone on your leadership team to be thinking about P2P opportunities.


Read More

SharePoint Lifecycle Management Solution with Project Server 2010

Author: Christophe Fiessinger , Senior Technical Product Manager, Microsoft Corporation

I am excited to announce the release of SharePoint Lifecycle Management Solution with Project Server 2010. Microsoft SharePoint Server 2010 provides a vast number of capabilities that empower both business users and IT to create solutions quickly. For this reason, many organizations consider implementing SharePoint as a central platform to address a wide array of business solutions. For those organizations, it is likely that they will need a good way to track, manage, and prioritize those business requests. The SharePoint Lifecycle Management Solution with Project Server 2010 provides a framework and guidance for managing SharePoint business requests and includes two white papers and a sample dataset.

This no-code solution includes:

  • Business Decision Maker/Technical Decision Maker white paper containing a business evaluation of how Microsoft Project Server 2010 can be employed to help manage your SharePoint Lifecycle through enhancement requests and project proposals.
  • Technical white paper contains step-by-step instructions on how to install and customize the SharePoint Lifecycle Management solution, along with basic instructions on how to use it.
  • Project Server 2010 sample databases and templates that can be used to illustrate concepts. The sample dataset requires a farm that has a working installation of Microsoft SharePoint 2010 with Project Server 2010 fully configured (please refer to Project Server 2010 Tech Center); and the Dynamic Workflow and Workflow Visualization web part solutions from Microsoft Project 2010 Solution Starters.
For an overview of the solution produced by Jornata, please watch this recent recording from Tech.Ed last week: http://channel9.msdn.com/Events/TechEd/NorthAmerica/2011/OSP202

BDM white paper Table of Content
Why Customers Choose SharePoint
SharePoint as a Central Service
SharePoint Lifecycle Management
Introducing the SharePoint Lifecycle Management Solution with Project Server 2010
    Managing SharePoint Requests
    Discovery and Further Definition
    SharePoint Project Selection
    Project Planning and Management
    Evaluating SharePoint Project Success
SharePoint Lifecycle Management Solution with Project Server 2010: Key Benefits
About the Solution
    Solution Artifacts
Conclusion

Last but not least do not forget to check out other existing white papers on Microsoft Project Portfolio Management offering on our Project site at http://www.microsoft.com/project/en/us/articles-white-papers.aspx.
 

Read More

FILESTREAM with SharePoint 2010

​Author: Bill Baer, Senior Technical Product Manager, Microsoft Corporation – SharePoint

FILESTREAM is a new feature in SQL Server 2008 that enables the storage of unstructured data on a NTFS file system. FILESTREAM (local or remote) is supported in SharePoint 2010 as one mechanism of reducing capital expenditures through enabling the storage of large binary unstructured data on content addressable or commodity storage.

Unstructured Data
Unstructured data refers to information that does not adhere to a defined model or does not fit well into relational tables in SharePoint unstructured data can refer to Microsoft Office document file formats, video, audio, and related file types.
 
Structured Data
Structured data in SharePoint refers to the metadata associated with its corresponding unstructured data or BLOB. Relational databases are most often cited as examples of structured data.
 
SQL Server and Unstructured Data Storage
There are three (3) approaches to storing unstructured data with SQL Server, RBS, SQL BLOB, and FILESTREAM:
  • Remote BLOB Storage (RBS) in which SharePoint relies on a new layer in SQL Server to read or update BLOB data stored outside of the database on separate BLOB Stores (file system or dedicated BLOB stores)
  • SQL BLOB which refers to traditional BLOB storage with SharePoint, BLOB data is stored along side the structured metadata in the Content Database
  • FILESTREAM
 
FILESTREAM Overview
FILESTREAM is implemented on the varbinary(max) datatype instructing the database engine to store unstructured data on the file system through a FILESTREAM filegroup that contains file system directories instead of the files themselves also known as data containers. Data containers are the interface between database engine storage and file system storage. varbinary is the binary data type designation for binary large objects stored in SharePoint 2010 content databases and refers to variable-length binary data. (MAX) refers to a value that max indicates that the maximum storage size is 2^31-1 bytes or otherwise 2GB. Remote BLOB Storage does not provide a mechanism to exceed to the 2GB file size limit imposed by SharePoint.
 
In SharePoint 2010 remote BLOB data is referenced by a unique identifier in content databases configured for RBS (see illustration).
 
 
 

 
 
FILESTREAM offers several benefits as related to performance 1) FILESTREAM uses the NT system cache for caching file data reducing the effect that FILESTREAM data has on Database Engine performance and 2) the SQL Server buffer pool is not used; therefore, memory is available for query processing.
 
FILESTREAM provides optimum value in scenarios where SharePoint is used to storage large BLOB data such as video files that will benefit from FILESTREAM or BLOB data that exceeds 1MB.
 
Special Considerations
 
FILESTREAM and Business Continuity Management
 
Database mirroring does not support FILESTREAM since a FILESTREAM filegroup cannot be created on the principal server and database mirroring cannot be configured for a database that contains FILESTREAM filegroups. If the FILESTREAM provider is used to store BLOB data locally (within the same content database) the database cannot be configured for database mirroring.
 
If the FILESTREAM provider is configured to store the BLOB data within a separate SQL database or when using a 3rd party BLOB store, the content database can be mirrored; however, database mirroring will apply only to the content database and not the BLOB data. The BLOB data needs to be handled separately and kept in sync with the associated metadata (content database). For FILESTREAM BLOB databases, this can be done through log shipping.
 
To learn about the differences between FILESTREAM and SQL Server Remote BLOB Store see also http://blogs.msdn.com/b/sqlrbs/archive/2009/11/18/sql-server-remote-blob-store-and-filestream-feature-comparison.aspx.
 
FILESTREAM and the Office Web Applications Cache
 
The Office Web Applications cache is used by Word and PowerPoint Web Applications to create a version of a document requested for viewing through the browser improving performance and reducing resource consumption on server machines by making cached versions of a document or presentation available in cases where there are multiple requests for the same document. 
 
The Office Web Applications cache occurs in two (2) distinct tiers, on the server file system and within a “specialized” site collection hosted on a per Web application basis. Document or presentation requests made through the Office Web Applications are served through both caches as the images are rendered for client consumption. Both cache locations are used by all site collections within a Web application where the Office Web Applications features activated.
 
Content databases where FILESTREAM is configured will store the cached versions of the document or presentation in the configured provider location.  It is recommended to configure the Office Web Applications cache on a database that is not configured for FILESTREAM.
 
Configuring FILESTREAM with SharePoint 2010
The instructions that follow are designed to be used on a single-server deployment for demonstration purposes and implements the local FILESTREAM Provider.
 
Enable FILESTREAM on the target SQL Server Instance
 
1.       On the Start menu, point to All Programs, point to Microsoft SQL Server 2008 (R2), point to Configuration Tools, and then click SQL Server Configuration Manager.
2.       In the list of services, right-click SQL Server Services, and then click Open.
3.       In the SQL Server Configuration Manager snap-in, locate the instance of SQL Server on which you want to enable FILESTREAM.
4.       Right-click the instance and then click Properties.
5.       In the SQL Server Properties dialog box, click the FILESTREAM tab.
6.       Select the Enable FILESTREAM for Transact-SQL access check box.
7.       If you want to read and write FILESTREAM data from Windows, click Enable FILESTREAM for file I/O streaming access. Enter the name of the Windows share in the Windows Share Name box.
8.       If remote clients must access the FILESTREAM data that is stored on this share, select Allow remote clients to have streaming access to FILESTREAM data.
9.       Click Apply.
10.    Click Start, click All Programs, click Microsoft SQL Server 2008 (R2), and then click SQL Server Management Studio.
11.    In SQL Server Management Studio, click New Query to display the Query Editor.
12.    In Query Editor, enter the following Transact-SQL code:
 
EXEC sp_configure filestream_access_level, 2
 
In Query Editor, enter the following Transact-SQL code:
 
RECONFIGURE
Provision the RBS Data Store
 
1.       Click Start, click All Programs, click Microsoft SQL Server 2008 (R2), and then click SQL Server Management Studio.
2.       Expand Databases.
3.       Select the content database for which you want to create a BLOB store, and then click New Query.
4.       In SQL Server Management Studio, click New Query to display the Query Editor.
5.       In Query Editor, enter the following Transact-SQL code:
 
use [Database Name]
 
if not exists (select * from sys.symmetric_keys where name = N’##MS_DatabaseMasterKey##’)create master key encryption by password = N’Admin Key Password !2#4′
 
In Query Editor, enter the following Transact-SQL code:
 
use [Database Name]
 
if not exists (select groupname from sysfilegroups where groupname=N’RBSFilestreamProvider’)alter database [Database Name] add filegroup RBSFilestreamProvider contains filestream
 
In Query Editor, enter the following Transact-SQL code:
 
use [Database Name]
 
alter database [Database Name] add file (name = RBSFilestreamFile, filename = ‘c:\BlobStore’) to filegroup RBSFilestreamProvider
Install the Microsoft SQL Server 2008 R2 Remote Blob Store
 
Download the x64 package for the Microsoft SQL Server 2008 R2 Remote Blob Store from the Microsoft SQL Server 2008 R2 Feature Pack at http://www.microsoft.com/downloads/en/details.aspx?FamilyID=ceb4346f-657f-4d28-83f5-aae0c5c83d52&displaylang=en.
 
Open a Command Prompt with Administrator permissions and execute the following command to install RBS.MSI downloaded in the previous step:
 
msiexec /qn /lvx* rbs_install_log.txt /i RBS.msi TRUSTSERVERCERTIFICATE=true FILEGROUP=PRIMARY DBNAME="<Database Name>" DBINSTANCE="<Instance Name>" FILESTREAMFILEGROUP=RBSFilestreamProvider FILESTREAMSTORENAME=FilestreamProvider_1
 
NOTE
Specify the full path to RBS.MSI in the above state, i.e. C:\Users\Administrator\Desktop\RBS.MSI. Replace the values for DBNAME and DBINSTANCE to match your environment.
 
Enable Remote BLOB Storage
1.       On the Start menu, click All Programs.
2.       Click Microsoft SharePoint 2010 Products.
3.       Click SharePoint 2010 Management Shell.
4.       In the SharePoint 2010 Management Shell, enter the following Windows PowerShell statement to set the content database to be configured:
$database=Get-SPContentDatabase –Identity “Database Name”
In the SharePoint 2010 Management Shell, enter the following Windows PowerShell statement to gets the object that holds settings that determine how the content database uses Microsoft SQL Server Remote Blob Storage:
$rbs=$database.RemoteBlobStorageSettings
In the SharePoint 2010 Management Shell, enter the following Windows PowerShell statement to determine if RBS has been installed for the selected content database:
$rbs.Installed()
NOTE
The result of $rbs.Installed() should be True, if the result is False, verify RBS.MSI has been installed successfully by reviewing rbs_install_log.txt. Ensure the install statement was running In the SharePoint 2010 Management Shell, enter the following Windows PowerShell statement to enable RBS for the selected content database:
 
$rbs.Enable()
In the SharePoint 2010 Management Shell, enter the following Windows PowerShell statements to set the RBSprovider for the selected content database:
$rbs.SetActiveProviderName($rbs.GetProviderNames()[0])
 
$rbs
 

NOTE
The result of $rbs should be:
Table 1

 
Appendix for Table 1
 
Enabled specifies whether or not RBS has been enabled for the selected content database.
 
ActiveProviderName is name of the SQL Remote Blob Storage provider new files will be stored in. This will be null if new files will not be stored using SQL Remote Blob storage.
 
MinimumBlobStorageSize refers to the minimum size a BLOB may be to be considered RBS storage worthy, BLOB data exceeding the specified MinimumBlobStorageSize will be stored in the RBS data store.
 
FILESTREAM performance data shows BLOB data exceeding 1MB provides the most efficient streaming performance. See also http://msdn.microsoft.com/en-us/library/cc949109(SQL.100).aspx.
 

 
To configure the MinimumBlobStorageSize:
1.       On the Start menu, click All Programs.
2.       Click Microsoft SharePoint 2010 Products.
3.       Click SharePoint 2010 Management Shell.
4.       In the SharePoint 2010 Management Shell, enter the following Windows PowerShell statements to configure the MinimumBlobStorageSize at 1MB:
$database = Get-SPContentDatabase “Database Name”
 
$database.RemoteBlobStorageSettings.MinimumBlobStorageSize=1048576
 
$database.Update()
UpgradePersistedProperties specifies the collection of field names and values for fields that were deleted or changed.
 
Validate Installation
To validate the FILESTREAM configuration and RBS installation:
 
1.       Click Start, click All Programs, click Microsoft SQL Server 2008, and then click SQL Server Management Studio.
2.       Expand Databases.
3.       Select the content database for which you want to create a BLOB store, and then click New Query.
4.       In SQL Server Management Studio, click New Query to display the Query Editor.
5.       In Query Editor, enter the following Transact-SQL code:
USE [Database Name]
SELECT * FROM dbo.DatabaseInformation
Confirm that both the RBSCollectionId and RBSProvider rows are available.
 
Test the RBS Data Store
1.       Select a desired Document Library on a site in the configured content database.
2.       Upload a file that is greater than 1 MB.
3.       On the computer that contains the RBS data store, click Start, and then click Computer.
4.       Browse to the RBS data store directory.
5.       Browse to the file list and open the folder that has the most recent modified date (other than $FSLOG). In that folder, open the file that has the most recent modified date. Verify that this file has the same size and contents as the file that you uploaded. If it does not, ensure that RBS is installed and enabled correctly.
The data store directory structure will appear similar to that in the following diagram.
 

 
NOTE
In the event error "The URL ‘<Document Library>/File’ is invalid. It may refer to a nonexistent file or folder, or refer to a valid file or folder that is not in the current Web.” is displayed when uploading documents greater than the configured MinimumBlobStorageSize open SQL Server Configuration Manager and enable Enable FILESTREAM for file I/O streaming access and restart the SQL Server (MSSQLSERVER) service.
 
Additional Resources

 

 

Read More

Search First Migration Accelerator

​Author: Bill Baer, Senior Technical Product Manager, Microsoft Corporation

Search has become the primary means in the Enterprise for surfacing and locating information, as a result, it has become a mission critical component of SharePoint deployments. The rise in adoption of SharePoint 2010 in organizations has led to more customers seeking to leverage the benefits of the new search architectures, whether Enterprise Search in SharePoint 2010 or FAST Search Server 2010, as part of their topologies. In either scenario, customers are faced with a decision on how to accomplish upgrade and accommodate their end users. A result of these decisions can include migrating or upgrading the existing SharePoint deployments to include search, or optionally migrating components of the existing deployments. In the componentized case, many organizations are looking to maintain a familiar user experience, while gaining the performance, scalability, and richness of new search options in SharePoint 2010 – that’s where the Search First Migration Accelerator comes in.
 
The Search First Migration Accelerator is a combination of guidance and tools provided by Microsoft and Metalogix enabling organizations to establish a more granular approach to upgrade by allowing them upgrade their Office SharePoint Server 2007 search component(s) prior to the underlying content, supporting a familiar search user experience, and enabling IT Professionals to approach upgrade in established phases while allowing the organization to benefit from the improvements in SharePoint Search 2010 or FAST Search for SharePoint 2010.
 
 
Download the Search First Migration Accelerator from Metalogix at http://www.metalogix.net/Free-Tools/Search-First-Migration-Accelerator/Download/.
 
Gain additional granularity and support for Search configuration through the SharePoint Enterprise Search Migration Tool for SharePoint Server 2010.
 
When upgrading from Office SharePoint Server 2007 to SharePoint Server 2010 using the database attach upgrade approach, only the source environments’ content is transferred to the destination environment, leaving the configuration settings in the source environment.  Transferring these settings can be a complex task and often require an array of custom tools.  The SharePoint Enterprise Search Migration Tool for SharePoint Server 2010 simplifies this process by providing support for the migration of search-related data such as best bets, search scopes, and site collection search settings.
 
The SharePoint Enterprise Search Migration Tool for SharePoint Server 2010 allows you to programmatically export and import search-related data between Office SharePoint Server 2007, SharePoint Server 2010, and FAST Search Server 2010 for SharePoint.
 
Supported Migration Paths
 
Read the SharePoint Enterprise Search Migration Tool documentation at SharePoint Enterprise Search Migration Tool for SharePoint Server 2010.
 
Download the SharePoint Enterprise Search Migration Tool for SharePoint Server 2010 at http://archive.msdn.microsoft.com/odcsp2010searchmigra.
 
Additional Resources

 

Read More

Export your own TechNet book

You can now build your own book of TechNet articles! For several product versions, the SharePoint IT Pro content team has published collections of TechNet articles as downloadable books that you can read offline and print. We’ve been able to cover only the most basic content sets. Each SharePoint Server or SharePoint Foundation environment is different, and none of the basic books exactly matches any environment.

Happily, our partners at TechNet have introduced a beta release of a new feature that you can use to build your own custom collections of articles! You can choose any articles (up to 100 per collection) from the TechNet library. That means that you can mix content from SQL Server, SharePoint Foundation, Windows Server, Office — any content in the TechNet library. The functionality is in Beta testing right now, but it’s accessible for public use and we encourage you to try it out. Here’s how.

You’ll need a recent browser. Internet Explorer 8 and Internet Explorer 9 work, as do the recent versions of other browsers. You’ll also need a Live ID for signing in to TechNet to export your collection.
Make sure you’re looking at the Lightweight view of the TechNet library. Go to the TechNet library home page. If you’re in Lightweight view, you should see something like this in the upper right corner:
If you don’t, click Lightweight in that corner to switch views.

To build a collection:

  1. Click the arrow next to the printer icon in the upper right corner, and then click Print Multiple Topics.
     
    The Help page will open.
  2. Read the overview on the Help page, and then click Start. The Print Multiple Topics toolbar will appear at the top of the window.
  3. Browse through the TechNet library, picking topics for your collection. Right-click a topic in the left pane to add it or it and its children to your collection.
  4. When you’re finished, click Collection on the Print Multiple Topics toolbar.
  5. On the Manage Collection page, you can change the order of topics and organize them into chapters.
  6. To download or print your collection, choose your file format (XHTML or PDF) and click Export. (Here’s where you sign in to TechNet by using your Live ID if you’re not already signed in.)
  7. Right-click the link to your collection to download it, or click the link to open it.

To start a new collection, click Delete on the Manage Collection page. There’s no way to have multiple active collections yet, so be sure you have a copy of the HTML or PDF file of your existing collection if you want to save it.

We hope you find this Beta functionality useful. Let us know!

 


Read More

Announcing the SharePoint Diagnostic Studio

Body:

Author: Bill Baer, Senior Technical Product Manager, Microsoft Corporation – SharePoint

One of the most challenging aspects of maintaining a SharePoint deployment is understanding why certain events have transpired in the environment, often IT Professionals and Developers only have access to when an event occurred and are tasked with parsing Performance Counters, Event and Diagnostic logs, or executing Transact-SQL statements against the Usage database to put the what and why to the when.  These tasks are typically accomplished through an array of tools such as Excel, Log Parser, SQL Server Management Studio and others and the IT Professional and Developer are challenged to correlate and condense this information into a meaningful format – large complex server farm environments make these tasks all the more difficult.
 
Often the most accessible solutions are used to identify and resolve issues occurring in a server farm environment to include the SharePoint Health Analyzer and Systems Center Operations Manager.

The next version (v2.0) of the SharePoint Administration Toolkit includes the new SharePoint Diagnostics Studio.  The SharePoint Diagnostics Studio provides a 3rd layer than can be implemented to support these processes and solutions.
 
 

In the new version of the SharePoint Administration Toolkit we’ve introduced a new and revised SharePoint Diagnostics Studio that represents a complete departure from previous diagnostics toolkits.  The next generation SharePoint Diagnostics Tool, the SharePoint Diagnostics Studio, presents server diagnostic information in a visual and structured way that enables Developers and IT Professionals to quickly diagnose and act upon intermittent performance, reliability and functionality problems in a SharePoint 2010 environment.

 

The SharePoint Diagnostics Studio offers unprecedented depth surfacing every request, across every machine, remotely, with minimal permissions.  This depth and usage allows the IT Professional or Developer to rapidly identity and isolate issues without requiring access to the physical hardware that supports the underlying environment.

 

 

 

 

 

 

 

The SharePoint Diagnostics Studio gathers and consolidates Event and Diagnostic (ULS) logs in addition to information from the Usage database and presents it through a graphical user interface supporting clarity and a single view into issues impacting a deployment.
 
The SharePoint Diagnostics Studio provides a wide variety of reports intended to address the most common issues impacting capacity, performance, availability, and usage that can be used independently or together to identify and isolate issues occurring in a SharePoint environment.
 

The SharePoint Diagnostics Studio provides reports in 5 separate categories:
1.       Base
2.       Capacity
3.       Performance
4.       Availability
5.       Usage
 
 
Integrated search enables rapid insight into issues that have occurred during the lifecycle of a request allowing the IT Professional or Developer to search against the most common criteria including date and time, Correlation Id, and the source user.
 

Snapshot and export support in the SharePoint Diagnostics Studio provides the ability to take information offline.

 

 

Context sensitive help provides guidance on both the purpose and how each report should be used.
 

 
Download the SharePoint Administration Toolkit and start solving your problems with the SharePoint Diagnostic Studio today.
 
Additional Resources
 
Read the SharePoint Diagnostics Studio documentation at http://technet.microsoft.com/en-us/library/hh144782.aspx.

 

Published: 4/22/2011 3:34 PM

Read More

Done with Training for Now.

I’m back in the office now after being out for a couple of weeks in a SQL Ranger rotation . The training was great, but I was pulled out 2 weeks early to focus on our newest product for MOSS supportability. More on that later. I’ll try to get the blog updated ASAP. There’s a lot of stuff I want to talk about.
BTW… Did you see Joel’s new blog post on Kerberos? http://www.sharepointjoel.com/archive/2008/03/18/kerberos-authentication-and-sharepoint-key-resources.aspx
Too much content to digest in one sitting….(read more)
Read More

SharePoint = Job Security

Just in case you didn’t get the memo SharePoint is the fastest selling server product in the history of Microsoft according to BillG. (doesn’t that also make it the fastest selling server product, period?)
In a blog conversation I had with the honorable Cliff Reeves he noted a very interesting site: http://www.itjobswatch.co.uk/jobs/uk/sharepoint%20server%202007.do It’s all UK focused, but the data surely reflects a global trend. SharePoint is hot and people who know SharePoint are hotter. A quick search of any of the major US based job sites would tell you SharePoint is high demand and the pay is very good. I’m confident this microcosm of hotness will fair well in a possibly existing or pending economic downturn.
In my dealings with customers and partners one thing is clear. There’s not enough SharePoint people to go around. Especially here at Microsoft. Sometimes warm-bodies are good enough especially if they can mumble share and point together in a sentence. The bottom line, if you are in a unappreciated technical field and looking for a more rewarding career consider SharePoint. If you are looking to ramp up on SharePoint quickly there are some good partner and Microsoft training resources. You can find a list of Microsoft training resources here and you can search for SharePoint and Training and get a pretty good list of partner opportunities. If you are completely new to SharePoint I would highly recommend you get some information worker focused training under your belt before diving into administration or development. This will go a long a way towards ensuring a well-rounded SharePoint skill-set….(read more)
Read More