Cannot restore from recycle bin

The Recycle Bin provides a safety net when deleting documents, list items, lists, folders and files. When you or site visitors delete any of these items from a Web site, the items are placed in the Recycle Bin.

Problem Description:

Unable to restore files/folders from Site Collection Recycle Bin

When we try to restore we get the following exception:

Error Message: Unable to restore ‘file name’

Troubleshooting Steps:

1)   Checked on the path from where the Folder was deleted and confirmed that it was not modified or deleted i.e. all the top-level folders/sites where intact to get to the folder.

2)   Checked for the available quota on site by means of storman.aspx

·         Open the site

·         Site actions

·         Site settings

·         Site collection administration

·         Storage allocation (storman.aspx)

All looked fine still unable to restore

Resolution:

·         Checked the Document Library where the folder had to be restored and found a folder named similar to the folder which was to be restored. E.g. RC PHASETEST4 as to RC PHASETEST3

·         So, renamed the similar folder to something else and tried restore, it worked. Once restored reverted the renamed folder to original.

If you have any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you

The folder may be located in an unavailable location, protected with a password, or the filename contain illegal characters

Different users…different issues but all are using the same product i.e. SharePoint

And we are here to resolves the issues and guide them in right directions.

This time-I am sharing in interesting issues which is based on sharepoint designer. User opened a ticket by mentioning that she is getting the following error message while opening the site in sharepoint designer.

The folder 'http://localhost' isn't accessible. The folder may be located in an unavailable location, protected with a password, or the filename contains a / or \.

What needs to be done if we encounter such issues? If we notice carefully then we will come to know that the error message is self explanatory. Ok-what exactly?

Here are the guidelines by which you can check the parameters one by one and get back to me in case of any questions/queries/information required:

1)   There is no such site or folder?

2)   This location is inaccessible because you are using FORM Authentication? You need to extend the web application on another port to connect to SPD.

3)   URL contains illegal characters?

4)   URL contains file names i.e. default.aspx

5)   Check in Central Administration > Application Management > Authentication Providers. Make sure "Enable Client Integration" is set to "Yes".

Thank you. Please feel free to contact/any queries/any questions, I would be more than happy to help you as well as resolves your issues.

Use Central Administration to restore a Web application in SharePoint 2010

To restore a Web application by using Central Administration

1. Verify that the user account performing this procedure is a member of the Farm Administrators group. Additionally, verify that the Windows SharePoint Services Timer V4 service and the Farm Database Access account have Full Control permissions on the backup folder.

2. In Central Administration, on the Home page, in the Backup and Restore section, click Restore from a backup.

3. On the Restore from Backup — Step 1 of 3: Select Backup to Restore page, from the list of backups, select the backup job that contains the farm or Web application backup, and then click Next.

4. On the Restore from Backup — Step 2 of 3: Select Component to Restore page, select the check box that is next to the Web application, and then click Next.

5. On the Restore from Backup — Step 3 of 3: Select Restore Options page, in the Restore Component section, make sure that Farm\ appears in the Restore the following content list.

In the Restore Only Configuration Settings section, make sure that the Restore content and configuration settings option is selected.

In the Restore Options section, under Type of Restore, select the Same configuration option. A dialog box appears that asks you to confirm the operation. Click OK.

Click Start Restore.

6. You can view the general status of all recovery jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status for the current recovery job in the lower part of the page in the Restore section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the recovery to start.

If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Sprestore.log file at the UNC path that you specified.

Error message when you try to add an existing Windows SharePoint Services 3.0 list to an Access 2007 database: "You do not have the necessary permissi

Symptoms:
You try to add an existing Microsoft Windows SharePoint Services 3.0 list to a Microsoft Office Access 2007 database. When the Windows SharePoint Services list contains a column name that has more than 64 characters, you receive an error message that resembles the following:

You do not have the necessary permissions to use the '' object. Have your system administrator or the person who created this object establish the appropriate permissions for you.Note The term "column name" is what you see in the SharePoint user interface. Colum name is the column’s display name.

Cause:
This problem occurs because the Access 2007 database engine disallows columns that have names that contain more than 64 characters.

MS KB Article:

Lync 2010 Trunk Media Bypass

Lync 2010 Trunk Media Bypass

Hello Guys,

Almost everyone heard about Trunk Media Bypass however you how it work, how to configure the same, today I will show you same.

Trunk Media Bypass is the media from the Lync client destined for PSTN/SIP-trunk or vice-versa always traversed through the Mediation Server.

With Lync 2010, a Mediation Server can now have a one to many relationships with media gateways, allowing a single Mediation Server to control multiple PSTN Gateways, IP-PBXs or E-SBCs. This flexible relationship is made possible via a powerful new Media Bypass feature in Lync 2010.

How to Configure Media Bypass on a Trunk?

1. Log on to the computer as a member of the RTCUniversalServerAdmins group, or as a member of the CsVoiceAdministrator, CsServerAdministrator, or CsAdministrator role. Open a browser window, and enter the Admin URL to open the Lync Control Panel.

2. In the left navigation bar, click Voice Routing and click Trunk Configuration.

3. On the Trunk Configuration page, use one of the following methods to configure a trunk:

·        Double-click an existing trunk (for example, the Global trunk) to display the Edit Trunk Configuration dialog box.

·        Click New, and select a scope for the new trunk:

1. Site trunk: Choose the site for this trunk configuration from the Select a Site dialog box, and then click OK. If a trunk has already been created for a site, the site does not appear in the Select a Site dialog box.

2. Pool trunk: Choose the service for this trunk configuration (for example, a PSTN gateway at a specified site) from the Select a Service dialog box, and then click OK. If a trunk has already been created for a service, the service does not appear in the Select a Service dialog box.

4. Give a value in the Maximum early dialogs supported box. This is the maximum number of forked responses a PSTN gateway, IP-PBX, or ITSP Session Border Controller can receive to an INVITE that it sent to the Mediation Server. The default value is 20.

5. Select one of the following Encryption support level options:

·        Required: To help protect traffic between the Mediation Server and the gateway or PBX, secure real-time transport protocol (SRTP) encryption must be used.

·        Optional: SRTP encryption will be used if the service provider or equipment manufacturer supports it.

·        Not Supported: SRTP encryption is not supported by the service provider or equipment manufacturer and therefore will not be used.

6. If you want media to bypass the Mediation Server for processing by the trunk peer, select the Enable media bypass check box.

7. Select the Centralized media processing check box if there is a well-known media termination point (for example, a PSTN gateway where the media termination has the same IP as the signaling termination). Deselect this check box if the trunk does not have a well-known media termination point.

8. If the trunk peer supports receiving SIP REFER requests from the Mediation Server, select the Enable refer support check box. Deselect the check box if the trunk peer does not support receiving SIP REFER requests from the Mediation Server.

9. (Optional) Associate and configure translation rules for the trunk:

·        To choose one or more rules from a list of all translation rules available in your Enterprise Voice deployment, click Select. In Select Translation Rules, click the rules that you want to associate with the trunk and then click OK.

·        To define a new translation rule and associate it with the trunk, click New.

·        To edit a translation rule that is already associated with the trunk, click the rule name and then click Show details.

·        To copy an existing translation rule to use as a starting point for defining a new rule, click the rule name and click Copy, and then click Paste.

·        To remove a translation rule from the trunk, highlight the rule name and click Remove.

10. Make sure the trunk’s translation rules are arranged in the correct order. Highlight the rule name and then click the up or down arrow to change a rule’s position in the list.

11. Click OK when you are finished configuring the trunk.

12. On the Trunk Configuration page, click Commit, and then click Commit all.

Thank you.

Restore a Web application in SharePoint Server 2010 using Windows PowerShell

You can use Windows PowerShell to restore a Web application manually or as part of a script that can be run at scheduled intervals.

To restore a Web application by using Windows PowerShell
1. On the Start menu, click All Programs.
2. Click Microsoft SharePoint 2010 Products.
3. Click SharePoint 2010 Management Shell.
4. At the Windows PowerShell command prompt, type the following command:
Restore-SPFarm -Directory (BackupFolderName) -RestoreMethod Overwrite -Item (WebApplicationName) [-BackupId (GUID)] [-Verbose]

Where:
- BackupFolderName, is the full path to the folder you use for backup files.
- WebApplicationNam, is the name of the Web application that was backed up.
- GUID, is the identifier of the back up to use for the restore operation.

If you do not specify the value of the BackupID parameter, the most recent backup will be used. You cannot restore a Web application by using a configuration-only backup. You can view the backups for the farm by typing the following:
Get-SPBackupHistory -Directory -ShowBackup

SharePoint 2013 Downloads and Links

As we all know Microsoft released public beta for SharePoint 2013 recently. Here are below some good links to download all related stuffs to SharePoint 2013.

Hardware and software requirements for SharePoint 2013 - Click here

Download Microsoft SharePoint Server 2013 Preview: Click here

Product key for the above: 6RNT8-XV26M-GWH36-VMGQH-94MMH

Download SharePoint Foundation 2013 Preview: Click here

Download SharePoint Designer 2013: Click here

SharePoint 2013: presentation: IT pro training (PPTX): Click here

Download ebook for Deployment guide for SharePoint 2013 Preview: Click here

SharePoint 2013 training for developers (Videos): Click here

Download SharePoint 2013 training for IT pros (Videos): Click here

What changes from SharePoint 2010 to SharePoint 2013 preview: Click here

What's new in social computing in SharePoint Server 2013 Preview: Click here

SharePoint 2013 Preview installation and configuration guide: Click here

Capabilities and features in SharePoint 2013 (Video): Click here

Physical architecture and logical architecture of SharePoint 2013: Click here

API set in SharePoint 2013: Click hereSharePoint 2013 video tutorial link: Click here

Microsoft Office Professional Plus 2013 Preview: Click here

SharePoint 2013 forum for IT Professional and Developers: Click here

Microsoft SharePoint 2013 forum for IT Professional: Click here

Microsoft SharePoint 2013 forum for Developers: Click here

Hardware and software requirements for SharePoint 2013 Preview

In this article we will discuss about the Hardware and Software requirements for SharePoint 2013 preview.

SharePoint 2013 Preview can be installed in different scenarios like single server with built-in database installations, single-server farm installations, and multiple-server farm installations.

Hardware Requirement:

Single server with a built-in database or single server that uses SQL Server:

RAM: 8 GB
Processor: 64-bit, 4 cores
Hard Disk space: 80 GB

Single server with a built-in database or single server that uses SQL Server:

RAM: 24 GB
Processor: 64-bit, 4 cores
Hard Disk space: 80 GB

Web server or application server in a three-tier farm:

RAM: 12 GB
Processor: 64-bit, 4 cores
Hard Disk space: 80 GB

Database servers:

RAM: 8 GB for small deployments and 16 GB for Medium deployment
Processor: 64-bit, 4 cores for small deployments and 64-bit, 8 cores for medium deployments
Hard Disk space: 80 GB

Database Requirement mainly: Microsoft SQL Server 2008 R2 (Service Pack 1) 64bit or Microsoft SQL Server 2012 (64bit)

Software requirements:

Minimum requirements for a database server in a farm:

- 64-bit edition of Microsoft SQL Server 2012 or 64-bit edition of SQL Server 2008 R2 Service Pack 1

- 64-bit edition of Windows Server 2008 R2 Service Pack 1 (SP1) Standard, Enterprise, or Datacenter or the 64-bit edition of Windows Server 2012 Release Candidate Standard or Datacenter

- Microsoft .NET Framework version 4.5 Release Candidate (RC)

Minimum requirements for a single server with built-in database:

- Microsoft SQL Server 2008 R2 SP1 - Express Edition

- 64-bit edition of Windows Server 2008 R2 Service Pack 1 (SP1) Standard, Enterprise, or Datacenter or the 64-bit edition of Windows Server 2012 Release Candidate Standard or Datacenter

- Microsoft .NET Framework version 4.5 Release Candidate (RC)

Minimum requirements for front-end web servers and application servers in a farm:

- 64-bit edition of Windows Server 2008 R2 Service Pack 1 (SP1) Standard, Enterprise, or Datacenter or the 64-bit edition of Windows Server 2012 Release Candidate Standard or Datacenter.

- SQL Server 2008 R2 SP1 Native Client

Check the below link for more information on it:
http://technet.microsoft.com/en-us/library/cc262485(office.15).aspx

SharePoint 2010 Object Model Classes

Microsoft SharePoint Server 2010 offers a highly structured server-side object model that makes it easy to access objects that represent the various aspects of a SharePoint Web site. From higher-level objects, you can drill down through the object hierarchy to obtain the object that contains the members you need to use in your code. Reference

Here there are some SharePoint Object model classes.

In the top SPFarm class is there.

SPFarm: This reference the entire SharePoint Server Farm.
By using this you can create a new farm or you can connect to a existing a existing farm.

Namespace: Microsoft.SharePoint.Administration

SPServer: By using this class you can browse through the collections of servers belongs to the Farm.

SPSite: Represent a Site collection.

SPWeb: Represent a web site.

SPUserToken: The SPUserToken class represents a token for a valid SharePoint user.

SPList: SPList corresponds to a single list instance, whether that is a list of items or a document library.

SPListItem: This defines a reference to a specific item of a list.

SPDocumentLibrary: This type represents a document library.

SPFile: This class is used to enumerate the files contained in a document library.

SPPrincipal: This class is the parent class for SPGroup and SPUser.

SPControl: This class we need while developing web controls or Web Parts.

SPContext: This is a very useful class and it has some direct methods to access useful information about current requests.

Different DLLs for Client Object Model SharePoint

There are different client object model like managed client object model, ECMAScript object model, Silverlight client object model etc. To work with these object models SharePoint provides certain classes which exists inside some dlls. These dlls are very leightweight as compared to SharePoint server object model. So it is a good idea to know about the dlls used and there locations.

Managed Object Model:

Dlls needed:

- Microsoft.SharePoint.Client
- Microsoft.SharePoint.Client.Runtime

Location: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI (If SharePoint installation done in C drive)

ECMAScript Object Model:

JS needed:

- SP.js , SP.Core.js , SP.Ribbon.js , and SP.Runtime.js .

Location: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS (If SharePoint installation done in C )

Silverlight Object Model:

Dlls needed:

- Microsoft.SharePoint.Client.Silverlight
- Microsoft.SharePoint.Client.Silverlight.Runtime

Location: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\ClientBin (If SharePoint installation done in C drive)drive)

Client Object Model SharePoint 2010 Details:

MOSS 2007 provides Web services which are difficult to use and always returns XML documents and XML data needs to be parsed manually.

These are simple APIs to add, retrieve, update and manage data in SharePoint. There are some tasks you can not do using client object model like creating a web application.

These classes are very easy to use and prefix sp is removed in the naming of client object model classes. For example in Server object model if the class is SPList now in client object model the class name is List.

Behind the schene client object model interact with some wcf services to communicate with SharePoint.

To work with client object model you need to refer 2 dlls which can be found in the following locations, refer to Managed Object Model, as discussed above:

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI

The 2 dlls are:

- Microsoft.SharePoint.Client.dll
- Microsoft.SharePoint.Client.Runtime.dll

Here is an example to create a list of type Announcement list by using SharePoint 2010 client object model.

using (ClientContext context = new ClientContext(http://Amardeep:8787/sites/Training))

{  //Create a new list

ListCreationInformation listCreationInformation = new ListCreationInformation();

listCreationInformation.Title = "My Announcements List";

listCreationInformation.Description += "Here is my list created by client object midel";

listCreationInformation.TemplateType = (int)ListTemplateType.Announcements;

listCreationInformation.QuickLaunchOption = Microsoft.SharePoint.Client.QuickLaunchOptions.On;

List list = context.Web.Lists.Add(listCreationInformation);

context.ExecuteQuery();
}

More Details: Refer to the link.

SharePoint Server 2013: Boosting Performance and Support for Real Business Solutions

The Preview of SharePoint Server 2013, which debuted for customer evaluation at the Worldwide Partner Conference in Toronto in mid-July, suggests this release will offer extraordinary power for business information-gathering and decision-making. Beyond its widely touted features, such as streamlined user and site experiences and enhanced collaboration (including social networking), SharePoint Server 2013 provides strategic improvements in support of bottom-line business essentials—workflow, business intelligence, business connectivity services, mobile productivity, eDiscovery and more.

Read on for highlights of a few features we think will be important to SharePoint enthusiasts looking for new ways to extend the value of their SharePoint deployment.

Workflow
SharePoint Server 2013 offers a new workflow service called Windows Azure Workflow. It is built on the Windows Workflow Foundation components of.NET Framework 4.5. The SharePoint 2010 Workflow platform is still the default in SharePoint Server 2013, and any workflows created in it will continue to work in SharePoint Server 2013.

However, those who choose to install and configure the new workflow service will benefit from enterprise-grade features including:

• Activity / Workflow Artifact Management
• Elastic Scale
• Fully Declarative Authoring
• High Density and Multi-Tenancy
• Instance Management
• Managed Service Reliability
• REST and Service Bus Messaging
• Tracking and Monitoring

 

Business Intelligence
In SharePoint Server 2013, the platform’s business intelligence (BI) tools have been fine-tuned for better performance and integration with business tools including the Microsoft Office productivity suite. Features include:

• The Business Intelligence Center site template has been updated and streamlined for ease of use.
• PerformancePoint Services now supports the iPad with BI viewing and interaction taking place thorough the Safari browser.
• Users can copy entire PerformancePoint dashboards and dependencies.
• An enhanced PerformancePoint UI facilitates filter viewing and management.
• Users working with Excel Services reports that use SQL Server Analysis Services data or PowerPivot data enjoy extended functionality.
• Excel Services now supports calculated measures and calculated members.
• Timelines in Excel Services now behave in the same manner as if they were viewed in the Excel client.

Business Connectivity Services
With the debut of SharePoint Server 2013, Microsoft has built upon the Business Connectivity Services model introduced with SharePoint 2010. This powerful feature, which enables SharePoint to access information from external data systems such as SAP, ERP, CRM and other data-driven applications, previously supported installation and use of external content types only at the farm level, which presented complications for use of BCS in many situations.

                                           

In SharePoint 2013, external content types can be scoped through “apps,” self-contained, easy-to-use bits of functionality designed for end users. Companies can develop apps that access external data from a variety of sources but do not change or affect the code on any underlying system or platform.

Microsoft has also added support for Open Data Protocol (OData) Business Data Connectivity connections in addition to connections for .NET, SQL Server and WCF. Previously, SharePoint was an OData provider, but now users can connect to an external data source using OData. (Visual Studio 2010 will generate all the Business Connectivity Services operations for all OData operations.)

Mobile Productivity
SharePoint Server 2013 now features optimized viewing capabilities and productivity enhancements across various mobile platforms (Windows; iOS; Android). New features to support mobile devices include:

• Updated browser UI: A lightweight Contemporary view now joins the previously available Classic and Full-Screen UI browser interfaces.

• Flexible site rendering: Rather than the single default mobile view used in SharePoint 2010, SharePoint sites can be optimized for different mobile devices and platforms.
• Geo-location: SharePoint Server 2013 supports a geo-location field type that enables lists to be geo-aware (among other capabilities).
• SharePoint Server 2013 supports push notifications (to applications that support them) of site updates, such as the addition of a list or an update to an item. Notifications can occur through the Microsoft Push Notification Service or platform-specific notification services.

eDiscovery
With SharePoint 2013, Microsoft is introducing a new eDiscovery solution. Key new features include:

• Site-based management and collaboration for eDiscovery cases with statistical tracking. Each case has its own site with an “eDiscovery Set”—the universe of search resources and their search filters (as well as action options).
• All sites are accessed through a common portal (the eDiscovery Center) for search, preservation, query and export of relevant materials. Search results are displayed based on the user’s permissions.
• Multiple Exchange mailboxes, SharePoint sites/farms and file shares can be associated with cases and then preserved in their entirety or queried to refine the pool of preserved content.
• Content holds include a new “in-place hold,” a feature that enables users to continue working with the preserved content from Exchange mailboxes and SharePoint sites. Users can change the content, but a content snapshot is recorded at the time of preservation and stays in hold, even if the user deletes the content. All held material is indexed in a preservation hold library visible only to Administrators and other authorized individuals.
• Query-building enables authorized users to define a scope for searching held resources, with additional filtering by message type or file type. Users can then view statistics about the items, preview results (documents; lists; pages; Exchange objects) and export (into the Electronic Data Reference Model format) the items for separate review, if desired.

Records Management and Compliance
SharePoint Server 2013’s records management and compliance features provide more security for your business. The most significant new feature is site-based retention. Any retention policies created in SharePoint Server 2013 apply to SharePoint project sites and any Exchange Server team mailboxes associated with those sites.

Better Search Architecture and Performance
To provide more powerful search capabilities, Microsoft has integrated more data from Microsoft Research and Bing, implemented the latest version of FAST technology, and incorporated new, extensible index, query and crawl frameworks.

All components and databases related to the search operation reside on application servers and database servers, respectively. No search components are hosted on Web servers.

For more details or to download the SharePoint 2013 Server Preview, visit: http://technet.microsoft.com/en-us/sharepoint/fp142374.aspx

What's New in Windows Server 2012 Active Directory

You can divide the "what's new" categories in Windows Server 2012 Active Directory into two roughly equal parts: brand new and merely improved. Either way, you're going to like what you see.

New Features:

Let's take a look at the new high-level features, starting with the brand-new functions:

GUI for Recycle Bin Microsoft introduced the Active Directory Recycle Bin in Windows Server 2008 R2, but it was limited by its Windows PowerShell-only exposure. This time it gets a GUI.

UI for Fine-Grained Password Policies Also gaining a GUI are fine-grained password policies.

Dynamic Access Control (DAC) Windows Server 2008 R2 brought the File Classification Infrastructure (FCI). This version's DAC adds far greater functionality to the (optional) second layer of FCI resource authorization.

Windows PowerShell History Viewer You see the Windows PowerShell commands that correspond to actions you perform in the Active Directory Administrative Center UI.

Windows PowerShell Cmdlets for Active Directory Replication and Topology More cmdlets

Active Directory-Based Activation (ADBA) The good: ADBA eliminates the need for a Key Management Service server. The bad: Only forthcoming Windows 8 computers can leverage ADBA. Seriously, Microsoft?

Flexible Authentication Secure Tunneling (FAST) The nickname for FAST is "Kerberos armoring," if that tells you anything. It isn't enabled by default and requires clients that support it. Think you'll be using it anytime soon?

Refreshed Features

Now let's move on to the merely improved bits:

Virtual Snapshot and Cloning Support Active Directory and hypervisor snapshots didn't mix before. Now they do, if your hypervisor supports VM Generation ID.

ADPREP Integrated into DC Promotion Can't recall the proper steps to promote a member server to a DC? No worries, it's in there.

Active Directory Federation Services (ADFS) Now In-Box Adding ADFS no longer requires a separate installation. ADFS also gains multiple improvements. Watch this space, because you'll be seeing and using more ADFS in the years to come.

Domain Join via DirectAccess One word: Nifty! Nine words: Computers can now be domain-joined over the Internet. You'll need DirectAccess first. Trust me: You'll want it.

Kerberos Constrained Delegation (KCD) Across Domains Another of those capabilities you've probably never used, but probably will in the future. KCD was first introduced in Windows Server 2003. Now it can span domains.

Group Managed Service Accounts (GMSAs) MSAs in Windows Server 2008 R2 made administering service accounts easier. GMSAs in this version extend their support to clustered and load-balanced services.

While individually these new features might not seem like a lot, as a group they're a good reason to step up your Active Directory to Windows Server 2012 as soon as you can. 

If you know about some more features please do let me know.

Cannot read from source file or disk error while using explorer view

The Explorer View is an excellent feature that is integrated with windows SharePoint Services that allows a user to access a document library as if you were accessing a file system through a Windows Explorer window.

Being end users, everyone might feel that this is very easy to use. But there are multiple complex interactions happening with different technologies to make documents which are not present in file systems to viewable using explorer.

Problem Description:

While trying to cut and paste files or folders from one document library to another using windows explorer view, the following error message may occur:

“Cannot read from source file or disk”.

This issue cannot be reproducible in a Windows XP environment; however this can be reproducible in Vista / Windows 7 / Windows 2008 / Windows 2008 R2. Here are some Scenarios when you do cut and paste of files / folders:

- MOVE between sites collections in the same web application works with XP

- MOVE between sites collections not in the same web application works with Vista and 7

- MOVE between two mapped drives (using net use command where one connected to site col1, and the second one connected to site col2) works with Vista and 7 (within a same web application, or between two webs application)

Resolutions:

Two workarounds are available so select anyone as per the flexibility.

1: COPY and PASTE the required data; then DELETE the files instead of using CUT and PASTE.

2: Create two mapped drives using "net use" command. Then complete CUT/PASTE between the mapped drives.  

If you have any queries/questions regarding the above mentioned information then please let me know. Thank you.

SharePoint 2010: Site Collection Administrator does not receive storage quota alerts

To help manage site and server resources, an administrator of the local server computer can specify quotas that are used to limit the amount of storage available on a site and the number of users that are added to a site collection. These quotas help to ensure that one site cannot deplete so many resources that other sites can no longer function.

The server administrator can use locks to stop sites from exceeding the storage quota limits, and to block all users from accessing a site if necessary.

A user is a SharePoint Site Collection Administrator. The Site Collection reaches its quota, and has passed the warning limit. However, the user does not receive a warning email message. 

Probable causes:

This issue occurs because the warning email message only goes to the Site Owner.

Resolution:

To resolve this issue, validate that the user is not the Site Owner. To do this, follow these steps: 

1)      Log on to any server of the farm. 

2)      Open Central Administration. 

3)      Application Management, and then

4)      Click View All Site Collections.  

5)      Find the site in question.  

6)   Notice the "Primary administrator." 

The primary site collection administrator will be the user who receives quota alerts. If the customer has to change this, we can run the following cmdlet:

stsadm -o siteOwner -url <Site Collection> -ownerLogin <Domain\Alias>

If you have any queries/questions/doubts regarding the mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues :)