Needed to Print a list item form out so I added this Code to a CEWP at the top of the Form
<code>
<input type=”button” value=” Print this page ” onclick=”window.print();return false;” />
</code>
User Feature Admin tool from Codeplex
Run and search for errors in features.
Remove
Simple … right
Here are some quick notes I ran into when working with our People Picker, or list of all users on Sharepoint 2010.
To see all users of the site: http://SiteAddress/_catalogs/users/simple.aspx
But you cant delete multiple, can only delete each, so go to:
http://SiteAddress/_layouts/people.aspx?MembershipGroupId=0
This will let you delete mutiple users at a time .. huge time saver.
but our people picker was still finding users from the old domain, So i found this: http://technet.microsoft.com/en-us/library/gg602075(d=lightweight,v=office.14).aspx
And set the PeoplePicker to only search our current domain for users. with command:
stsadm -o setsiteuseraccountdirectorypath -path “DC=,DC=local” -url https://SiteCollectionURL
When I started at this new position they were going through a conversion from SharePoint 2007 to 2010 on the Intranet and Extranet. Actually the day before I started they attempted to the conversion and failed, so as soon as I finished my “in processing” I was pulled out of classes and put to work.
One of the first major projects (after getting the sites back up and running) was to perform a document clean up. As many company’s without a web governance standard knows after several years of uploading documents they didn’t have a handle on what was actually on the site. In order to actually see what was on the site I found/modified the following script (if I got it from you please comment if you find this so I can give credit where it is due).
function Get-DocInventory() {
[void][System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint")
$farm = [Microsoft.SharePoint.Administration.SPFarm]::Local
foreach ($spService in $farm.Services) {
if (!($spService -is [Microsoft.SharePoint.Administration.SPWebService])) {
continue;
}
foreach ($webApp in $spService.WebApplications) {
if ($webApp -is [Microsoft.SharePoint.Administration.SPAdministrationWebApplication]) { continue }
foreach ($site in $webApp.Sites) {
foreach ($web in $site.AllWebs) {
foreach ($list in $web.Lists) {
if ($list.BaseType -ne "DocumentLibrary") {
continue
}
foreach ($item in $list.Items) {
$data = @{
"Web Application" = $webApp.ToString()
"Site" = $site.Url
"Web" = $web.Url
"list" = $list.Title
"Item ID" = $item.ID
"Item URL" = $item.Url
"Item Title" = $item.Title
"Item Created" = $item["Created"]
"Item Modified" = $item["Modified"]
"File Size" = $item.File.Length/1KB
}
New-Object PSObject -Property $data
}
}
$web.Dispose();
}
$site.Dispose()
}
}
}
}
Get-DocInventory | Export-Csv -NoTypeInformation -Path d:\temp\inventory.csv
The script will query the sites on the current farm (I would run this from the WFE Server) and return all the Documents. Note this also returned default.aspx and master pages but I would just filter those out of the spreadsheet.
Using one of my past writeups I would have another PowerShell Script upload to a List on our cleanup site and graph out the information so it looked good using Fusion Charts.
Conclusion of the Project BTW was 289k documents trimmed down to roughly 150k… at least it’s a start!!
This site I am working is seems to hate me (as the last few posts can contest). We ran into another problem last night when the Publisher tried to create a new Banner on the Rotating Banner. When they entered the title that included an apostrophe none of the text after the apostrophe showed up. Being a sys admin my answer was just don’t use apostrophes, but they are all communications majors so to them there is a big difference between “Childrens” and “Children’s”.
From my understanding it is because the JSON is using the Single Quote for escape characters hence the apostrophe appears to be the end of the text.
The work around for this was to use the ASCII code for apostrophe so publishers have to enter the text with the code instead of an apostrophe. The Client would then convert the code into an ‘.