If you are using Firefox as your default browser, then either you get
an IE tab add-on to view SharePoint sites in Firefox, or type your user
name and password each time when you access to the SharePoint server.
There is a way thought to allow you to save your typed Windows
credentials in Firefox to prevent you from repeatly typing the Windows
user name and password.
Enter “about:config” in the address bar of Firefox and hit [Enter]
Do a search on "ntlm", at least three entries should appear
Double click the entry titled
"network.automatic-ntlm-auth.trusted-uris" and set its value to .yourdomain (do not
forget the dot). You can have multiple domains by entering them as comma-separated.
Restart your Firefox to get it to kick in.
Woila! No more irritating login prompts. This only works with NTLM authentication and not Kerberos.
<script type="text/javascript">// <![CDATA[
var Username = document.getElementById("zz16_Menu").innerHTML ;
var end = Username.indexOf("<");
var nameOnly = Username.substring(8, end);
document.write(nameOnly);
// ]]></script>
This technique is a little complex for my liking however, so here’s a snappier way to grab the current login name (using Jquery):
var Username = $("#zz16_Menu").text();
document.write(Username);
Note that the #zz16 identifier will vary based on your Master page. Use the Firefox Web Developer tools or Internet Explorer F12 tools to find out what the ID should be on your SharePoint site.
Using this type of technique is definitely more brittle than actually using a CAML query however in my mind would be more performant than actually doing a lookup in the DB. Would love to know if someone knows the scoop on that..
Update 05/12/2011
As my colleague Colin pointed out – the name that appears on the top right can really be anything and can change – for example if a user gets married and their name changes. A better approach would be to retireve the value programmatically using SPServices ( http://spservices.codeplex.com/wikipage?title=$%28%29.SPServices.SPGetCurrentUser ). As of version v0.6.1, you can also request the ID of the user by specifying fieldName: “ID”. Much more stable to use in most scenarios:
Trying to import an Excel file in as SharePoint 2010 List resulted in the error:
The specified file is not a valid spreadsheet or contains no data to import
Double-checked the spreadsheet for formula errors, consistency etc. everything looked good but still no importo. The solution is to go to Internet Explorer > Internet Options > Security > Trusted Sites and add your SharePoint site to the list of trusted sites. You can use a *. to avoid having to list multiple subdomains, e.g. “https://*.mySharePointSite.com”
Be sure to disable the HTTPS checkbox if it’s not a requirement for your deployment.
Out of the box, the SharePoint 2010 User Profile page uses a bit of Javascript to truncate the user’s bio info like Email, School etc. with a “more information” hyperlink that can be clicked to show all the info. The user’s bio/description text is also similarly semi-hidden on page load.
The following quick CSS hack can make both these detail areas fully visible by default, and also hide the “more information” / “hide information” hyperlink”:
1. Open the file in a plain text editor or CSS editor of choice.:
C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions14TEMPLATELAYOUTS1033STYLESmysitelayout.css
2. Paste the following CSS into
the bottom of the file:
/* IT Groove -
Added to keep the Show More Information/About Bio dialog in an opened state
initially */
#ctl00_PlaceHolderMain_ctl11_showHideLink
{
display:none;
}
.ms-contactcardtext3
{
display:block !important;
overflow:visible !important;
}
/* */
3. Save file. Users will have to press Ctrl-F5 or go into their browser and manually delete the file cache
for the changes to take effect. Avoid deleting users browser cookies when clearing cache to avoid frustrations, just clear the file cache.
Just remember, you’re modifying core SharePoint CSS which is most definitely not a best practice, but can do the trick for you in some circumstances!
A basic issue – the client has their Active Directory DisplayName populated in the style of “LastName, FirstName“. Legacy business requirements dictate that the DisplayName stays in that format – but the SharePoint champion comes along and indicates that it would be preferable to have the SharePoint 2010 UI show the users DisplayName in the standard “FirstName LastName” format.
After quickly toying with the idea of using Jquery or some other front-end patch to just reverse the names – complications arose – number one being the data in the DisplayName field in AD was inconsistent, with various flavours and styles of data that was mashed together over the years. Active Directory is aptly named- people will mess up this data actively. Not to be trusted. The solution:
1. Set up the SharePoint 2010 User Profile Synchronization and use custom field mapping.
2. Create a new profile property in AD called customDisplayName and give it the values Firstname Lastname 3. Map the new customDisplayName property to the SP DisplayName property.
So, the end result should be that users would now see their DisplayName throughout the SP application populated with the AD field data “FirstName LastName”
Getting User Profile Synchronization itself planned, configured and deployed is a big task. This post will let help you plan out your first moves.
( .xls download )
Profile sync worksheet tab of the specifies information that you might need to gather if you have not already configured the SharePoint Server infrastructure. It is used with the Configure profile synchronization topic on TechNet. The Property mapping worksheet tab is obsolete; it has been replaced by the User Profile Properties Planning worksheet.
NOTE: When performing the intital setup, it’s important to remember that MS best practice is to not have your Active Directory Domain Controller on the same server as SharePoint. So you need to follow a different path if you are using a dev server with AD and SQL all wrapped into the one server, than if you would be deploying to a production setup with AD DC on a separate server. Spence Harbar in particular notes this in a few places but it will confuse the hell out of you with the AD setup requirements unless you understand the distinct setup paths required for both scenarios.
