SharePoint Illegal Characters
Today we started to bring in the documents for our new department and found lot of errors trying to move the folders and the documents to SharePoint. This is due to the Illegal characters in the naming conventions.
Characters that can't or shouldn't be used in File, folder and site names.
~ # % & * { } \ : < > ? / + | " . _
Notes:
- Period can't be used consecutively in the middle of a name or at the end
- Underscore shouldn't be used at the start of any name
- Spaces are encoded as %20 (3 characters) and count to the 240 character Web-DAV file length limit
Event ID 3351-Login failed for user ‘NT AUTHORITY\ANONYMOUS LOGON’
Today 01/04/2011, as part of my monthly checks, I noticed a whole bunch of 3351 errors in the event log on the SharePoint front end web server.
Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Database
Event ID: 3351
Date: 1/4/2011
Time: 12:44:45 AM
User: N/A
Computer: MOSSSERVER
Description:
SQL database login failed. Additional error information from SQL Server is included below.
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
Resolution: First I started to check the application pool account of the portal site and found they were all set as defined. After a thorough investigation found that the Windows SharePoint Services VSS Writer account is running as local system account. Changed the account to the AD Farm Account and found that the issue is resolved.
Accounts used by application pools or service identities are in the local administrator group
Least Privilege Service Accounts for SharePoint 2010
In the last few years, enterprises have come to care about least privilege—the security concept that relates to an account being given only the permissions it requires to perform its tasks, nothing more. Least privilege is important for security, auditing, and compliance, and it applies not only to the accounts used by human beings, but also by service accounts.
And, like least privilege, enterprises have come to care about service accounts as well. I remember the days when it was perfectly acceptable to create a service account and set “password never expires.” Now, most enterprises have security policies that explicitly forbid such configuration because of the open door it leaves into a system.
During the next few weeks, I’ll be posting steps to help you deploy SharePoint with least privilege and to manage SharePoint service accounts. Let’s start by clearing up some confusion and all-too-prevalent mistakes that I see made with SQL Server, SharePoint administration, and farm accounts—and don’t be surprised that at least some of the confusion is due to the weirdness of the SharePoint setup wizard itself.
3 Accounts
Microsoft describes the administrative and service accounts required for initial deployment but skims over some important details and emphases, so let’s take a look at the three accounts this week, then we’ll return to some refiners next week.
SharePoint 2010 Virtual Labs
Microsoft has published a number of Virtual Labs on MSDN and TechNet, simplifying a range of testing scenarios focused on SharePoint 2010. Customers already familiar with Microsoft’s Virtual Labs know that the resources are offered free of charge, and are available to all, not just MSDN and TechNet subscribers
“Microsoft SharePoint 2010 makes it easier for people to work together. Using SharePoint 2010, your people can set up Web sites to share information with others, manage documents from start to finish, and publish reports to help everyone make better decisions,” Microsoft revealed.
At the bottom of this article, you will be able to find a list of links pointing you to the TechNet and MSDN Virtual Labs for SharePoint Server 2010. Obviously, the TechNet Virtual Labs are focused on IT pros, while the MSDN resources are designed for developers. SharePoint Server 2010 RTM’d in mid-April 2010, along with additional products including Office 2010, Visio 2010 and Project 2010. As of May 12, 2010, SharePoint Server 2010 along with all the solutions enumerated above became available for purchase to business customers worldwide.
SharePoint Server 2010 Virtual Labs are essentially virtualized instances of the product running in Hyper-V on a Microsoft Server. Customers that want to access the resources will need to be running Windows and use Internet Explorer 8, IE7, or IE6. Since the virtual machines with SharePoint 2010 are running on Microsoft servers, customers don’t need to worry about details such as downloading, deploying or configuring the product. For each Virtual Lab, IT pros and devs get a 90-minute block of time per module, but they can also sign up for more
From TechNet:
TechNet Virtual Lab: Backup and Restore in SharePoint Server 2010
TechNet Virtual Lab: Business Continuity Management in SharePoint Server 2010
TechNet Virtual Lab: Configuring Remote Blob Storage FILESTREAM Provider for SharePoint Server 2010
TechNet Virtual Lab: Configuring Tenant Administration on SharePoint Server 2010
TechNet Virtual Lab: Configuring User Profile Synchronization in SharePoint Server 2010
TechNet Virtual Lab: Introduction to Microsoft SharePoint Server 2010 Upgrade
TechNet Virtual Lab: New IT Pro Features in SharePoint Server 2010
TechNet Virtual Lab: Windows PowerShell in SharePoint Server 2010
From MSDN:
MSDN Virtual Lab: Developing a BCS External Content Type with Visual Studio 2010
MSDN Virtual Lab: Developing a Visual Web Part in Visual Studio 2010
MSDN Virtual Lab: Developing SharePoint 2010 User Interface with Silverlight in Visual Studio 2010
PowerShell Tips for SharePoint 2010
Here is a quick guide for PowerShell tips in SharePoint 2010:
http://www.powergui.org/servlet/KbServlet/download/2812-102-4534/SharePoint2010PowerShell.pdf
And this Technet article gives a complete mapping of STSADM commands with PowerShell Commands:
http://technet.microsoft.com/en-us/library/ff621081.aspx