I end-up in creating the PowerShell script (as shown in below) to re-sync the usage statistics using RecalculateStorageUsed() Method.

foreach ($spsite in Get-SPSite -url *) {
$oStorage = $spsite.SPBase.Usage.Storage
Write-Host Old Storge: $oStorage
$spsite.SPBase.RecalculateStorageUsed()
$spsite.SPBase.Dispose()
$tSPSite = $spsite.GetSPObject()
$nStorage = $tSPSite.Usage.Storage
Write-Host $tSPSite.Url Updated from $oStorage to $nStorage
$tSPSite.Dispose()
}

Also, we could have use Gary Lapointe’s STSADM extension — which has gl-recalculateusage STSADM command to sync the site usage statistics on SharePoint.

SQL Reporting Services in SharePoint Integration Mode

When you integrate a report server with an instance of a SharePoint product, items and properties are stored in the SharePoint content databases. This provides a deeper level of integration between the server technologies that effects how content is stored, secured, and accessed.

Storing report items and properties in SharePoint content databases allows you to browse SharePoint libraries for report server content types, secure items using the same permission levels and authentication provider that controls access to other business documents hosted on a SharePoint site, use the collaboration and document management features to check reports in and out for modification, use alerts to find out if an item has changed, and embed or customize the Report Viewer Web part on pages and sites within the application. If you have sufficient permissions within a SharePoint site, you can also generate report models from shared data sources and use Report Builder to create reports.

The report server continues to provide all data processing, rendering, and delivery. It also supports all scheduled report processing for snapshots and report history. The following diagram shows the server components together:

SQL Reporting Services in Native Mode

Reports are being hosted in a separate server as Native Mode and developers are adding the reports URL in to the SharePoint Pages. When we open a report by clicking the link in SharePoint page, SharePoint redirected to the Report Server URL. Thus, report server is running as an isolated server from the SharePoint.

Click to open the Windows PowerShell Command Builder in a new browser window.

SharePoint 2010 Resource Centers: http://technet.microsoft.com/en-us/sharepoint/ff465365

Download the code here

Hope this helps.

For more information, http://sharepoint.microsoft.com/blog/Pages/BlogPost.aspx?pID=971

As mentioned in the subjected above, we have encountered the issue that existing alerts were not firing after the site migration. I digged into the Micrsoft Knowledge Base and I found out the below support article.

http://support.microsoft.com/kb/936759

There is an awesome tool for SharePoint administrator to update these existing alerts.The new stsadm -o updatealert command was released in the SharePoint Administration Toolkit. For more information and to download the toolkit, visit one of the following Microsoft Web sites, depending on the version of Windows SharePoint Services that you are running.

SharePoint Administration Toolkit x64

SharePoint Administration Toolkit x86

For more information, see the “Microsoft SharePoint Administration Toolkit” white paper. To do this, visit the following Microsoft Web site:

Enjoy!!!

There are multiple options for SP administrator to achieve this task like creating URLMapping element in the web.config, or writing URL Rewriting using HTTP Modules, etc. But these methods are time consuming and we can not test code as we are working on the production migration. So, the only option is to change the redirection URL at the IIS level. Below is the workable and quick solution for this task.

Just set “The exact URL entered above” and “A permanent redirection for this resource” on the IIS and enter your fully qualified host name entry as follows

http://contoso.corp.com$S$Q

The $S$Q will maintain all URLs on our other host names that enter.

This would redirect all your http://contoso.external.com/* HTTP calls to http://contoso.corp.com/*.

How simple is it right?

SP administrator should have to use some tool to find out these hard-coded urls and change it manually. The below SQL query would point out the hard-coded URLs in each content databases. Also, I heard some webparts are available at the CodePlex.com to find and replace these hard-coded URLs.

use [CONTENT_DATABASE_NAME]
go

select webs.title as SiteName, navnodes.url as AbsoulteUrl, webs.fullurl as location
from navnodes
join webs on navnodes.webid = webs.id
where navnodes.url like ‘%http://%’

It is a real hard to understand the issue from user who is working remotely at client location. Normally, IT support folks used to setup a webex session to see what is happening in their machine to understand the issue. But this method would not apply for a user can not accept or share their desktop due their work environment restrictions.
Only option is to share the screenshot between user computer and IT support professional. But IT support professional could not easily identify the root cause of an issue or troubleshoot the issue using screenshot of user desktop.

CAUSE:

I had an experience with external user with same situation as mentioned above. So we decided to gather the information in regards to external user getting access denied. We analyzed the various areas as shown in below.

Things we gathered,
1. User account setup is okay
2. Her account works on Guest VLan on Corporate COE PC (IE7)
3. User account works on IT Support Professional home internet (IE7)
4. User account will not work on NAMSA PC (IE8)

So, it is clearly shows that IE8 is causing the issue.

RESOLUTION:

We advised them to make sure their Trusted Sites zone allows ‘Automatic login with current username and password’.
Open IE, Tools -> Internet Options -> Security -> Trusted Sites.
1. Click ‘Sites’ and make sure the URL is in there.
2. Click ‘Custom Level’, scroll to the bottom and ensure ‘Automatic Logon with current user name and password’ is selected.

When attempting to create/open a document in a SharePoint list or view a list in Datasheet view, you receive one of the messages below:

1. The list cannot be displayed in Datasheet view for one or more of 
the following reasons:
 - A datasheet component compatible with Windows SharePoint Services 
is not installed.
 - Your Web Browser does not support ActiveX controls.
 - Support for ActiveX controls is disabled.
-OR-
 The list is displayed in Standard view. It cannot be displayed in 
Datasheet view for one or more of the following reasons: A datasheet 
component compatible with Microsoft SharePoint Foundation is not 
installed, your browser does not support ActiveX controls, a component is 
not properly configured for 32-bit or 64-bit support, or support for 
ActiveX controls is disabled. 2. The document could not be created. The required application 
may not be installed properly, or the template for this document library 
cannot be opened. 3. The document could not be opened for editing. A Windows SharePoint 
Services compatible application could not be found to edit the document.