Check it out http://denver.craigslist.org/for/2970214010.html
http://www.jwz.org/xscreensaver/download.html
The above link will take you to a very nice person who has spent a bunch of time compiling 200+ screen saves from years past. You will find screen savers from both PC and Mac olden days :)
Currently running Mac OS X Lion 10, with no issues. Enjoy!!
Enable all supported languages for all site collections within SharePoint 2010 Web Application. Based off this post http://msdn.microsoft.com/en-us/library/ff800886.aspx
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 | ################################################################################# ########################## Change Inputs Below ################################## ################################################################################# #$WebAppURL = "http://redleader" ################################################################################# ########################## Code, No Changes Below ############################### ################################################################################# clear $PSSnapin = Remove-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue | Out-Null $PSSnapin = Add-PsSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue | Out-Null $WebApp = Get-SPWebApplication $WebAppURL Foreach ($Site in $WebApp.Sites) { $Web = $Site.RootWeb $Web.IsMultilingual = $true $WebRegionSettings = New-Object Microsoft.SharePoint.SPRegionalSettings($Web) Foreach ($lang in $WebRegionSettings.InstalledLanguages) { If ($Web.SupportedUICultures -notcontains $lang.LCID) { $Web.AddSupportedUICulture($lang.LCID) } } $Web.Update() $Web.Close() $Web.Dispose() $Site.Close() $Site.Dispose() } |
I just upgraded to PowerGUI 3.2.0.2237 today. I ran into an issue once I attempted to debug a script that I know works. The error output contained this “Microsoft SharePoint is not supported with version 4.0.30319.261 of the Microsoft .Net Runtime.”
Based on the release notes of PowerGUI 3.2.0.2237 it seems they added .net 4.0 support natively. Not sure if it was supossed to be backwards compatible automatily or not, but at first galnce its not. If you want to continue to run you SharePoint 2010 2.0 cmdlets in PowerGUI, the only way I found was to change a config file. Please follow the below. If someone knows a better way of doing this im all ears!! Thanks
The below only works with x64. I’m sure there is a smiler config setting in the x86 ScriptEditor but I do not cover it below.
- Goto: C:\Program Files (x86)\PowerGUI\
- Make a backup copy of this file “ScriptEditor.exe.config” then open in your favorite xml editor.
- Make the below edit to your xml file, on line 4.
<?xml version=”1.0″ encoding=”utf-8″ ?>
<configuration>
<startup useLegacyV2RuntimeActivationPolicy=”true”>
<supportedRuntime version=”v4.0″ sku=”.NETFramework,Version=v4.0″ />
<supportedRuntime version=”v2.0.50727″ />
</startup>
After
<?xml version=”1.0″ encoding=”utf-8″ ?>
<configuration>
<startup useLegacyV2RuntimeActivationPolicy=”true”>
<!–<supportedRuntime version=”v4.0″ sku=”.NETFramework,Version=v4.0″ />–>
<supportedRuntime version=”v2.0.50727″ />
</startup>
** Update 03/02/12 ** I think there is just some conflict with Visual Studio 2010 components that are installed .net 4 & etc.. and this PowerGUI version. Or maybe that its an upgrade. Who knows.. I did however install PowerGUI on another machine today, and it worked fine with the SharePoint 2010 cmdlets.
Don’ Freak!!!
Just delete the PowerPoint Service Application and this error goes away. Not sure if this is 100% true but it seems like one of the CU updates breaks access to the PowerPoint Service Application from Central Administration.
Spent hours trying to figure out why I couldnt check-out and check-in excel files or any files for that matter in SharePoint 2010. From a Windows 7, Office 2010, IE9 computer I never ran into issues, however with a Windows XP, Office 2007 and IE 8 I couldn’t. Kept getting the error “the document could not be checked out”. Ran fiddler traces and looked at ULS logs and really nothing pointed to any issues. Finally after many searches I found this article: TechNet http://social.technet.microsoft.com/Forums/en-US/sharepoint2010setup/thread/4e41fd23-1b8c-45e3-a4e8-fdba4e852317/ . Please see post from “Carlos_Shepardos” Sure enough I was missing a root site collection within my web app. So I didn’t have to install anything or change any settings on my client computers, just created a root site collection that the end user doesn’t even need access to. Hopefully if you catch yourself using Windows XP, Office 2007 and IE8, you will find my blog. I hope it works for you.
Enable is the first PS command. The second is used if you would like to use CredSSP creds. Clicking the links will take you to the Technet article.
Original Post: http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spfilecollection.aspx
**Please note** I didn’t attempt to “dispose”, so make sure to add it…
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 | $PSSnapin = Add-PsSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue | Out-Null clear $org = "http://blueleader" $dest = "http://redleader" $orgLibrary = (Get-SPWeb $org).Folders["Documents"] $destLibrary = (Get-SPWeb $dest).Folders["Documents"] $destFiles = $destLibrary.Files foreach ($file in $orgLibrary.Files) { $curFile = $file.OpenBinary() $destURL = $destFiles.Folder.Url + "/" + $file.Name $destFiles.Add($destURL, $curFile, $true) } |
It has come to my attention that there is still a handful of folks out there writing PowerShell with NOTEPAD…. I won’t name names… But you all know who you are.
Anyway I use a free tool from Quest software called PowerGUI. See the link to the latest build http://community-downloads.quest.com/powergui/Release/3.0/PowerGUI.3.0.0.2015.msi or http://powergui.org This is the tool that you “never leave home without”. It’s just like visual studio in the sense that you can step into code and debug variables, for each loops, you name it, it can do it. Please let me know if you have any questions.
BTW, a solid second place winner is… Microsoft Windows PowerShell ISE http://technet.microsoft.com/en-us/library/dd315244.aspx
The script enumerates a folder structure based off the input section of the PowerShell script. It then detects all .wsp files in any folder at the root of the folder and below. Once the list of files is compiled by PowerShell, it begins to either upgrade or installs each detected wsp. The script has a bit of logic when attempting an install or upgrade. If the PowerShell script detects that the solution is already deployed to the farm, it will first attempt to retract the solution, once completed it then removes the solution before it attempts to install and deploys the feature to all web applications.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 | ###################################### ######## Set Variables ############### ###################################### $InstallDIR = "C:\install" ###################################### #### CODE, No Changes Necessary ###### ###################################### Write-Host "Working, Please wait...." Add-PSSnapin microsoft.sharepoint.powershell -ErrorAction SilentlyContinue $Dir = get-childitem $InstallDIR -Recurse $WSPList = $Dir | where {$_.Name -like "*.wsp*"} Foreach ($wsp in $WSPList ) { $WSPFullFileName = $wsp.FullName $WSPFileName = $wsp.Name clear Write-Host -ForegroundColor White -BackgroundColor Blue "Working on $WSPFileName" try { Write-Host -ForegroundColor Green "Checking Status of Solution" $output = Get-SPSolution -Identity $WSPFileName -ErrorAction Stop } Catch { $DoesSolutionExists = $_ } If (($DoesSolutionExists -like "*Cannot find an SPSolution*") -and ($output.Name -notlike "*$WSPFileName*")) { Try { Write-Host -ForegroundColor Green "Adding solution to farm" Add-SPSolution "$WSPFullFileName" -Confirm:$false -ErrorAction Stop | Out-Null Write-Host -ForegroundColor Green "Checking Status of Solution" $output = Get-SPSolution -Identity $WSPFileName -ErrorAction Stop $gobal = $null if ($output.Deployed -eq $false) { try { Write-Host -ForegroundColor Green "Deploy solution to all Web Apps, will skip if this solution is globally deployed" Install-SPSolution -Identity "$WSPFileName" -GACDeployment -AllWebApplications -Force -Confirm:$false -ErrorAction Stop | Out-Null } Catch { $gobal = $_ } If ($gobal -like "*This solution contains*") { Write-Host -ForegroundColor Green "Solution requires global deployment, Deploying now" Install-SPSolution -Identity "$WSPFileName" -GACDeployment -Force -Confirm:$false -ErrorAction Stop | Out-Null } } Sleep 1 $dpjobs = Get-SPTimerJob | Where { $_.Name -like "*$WSPFileName*" } If ($dpjobs -eq $null) { Write-Host -ForegroundColor Green "No solution deployment jobs found" } Else { If ($dpjobs -is [Array]) { Foreach ($job in $dpjobs) { $jobName = $job.Name While ((Get-SPTimerJob $jobName -Debug:$false) -ne $null) { Write-Host -ForegroundColor Yellow -NoNewLine "." Start-Sleep -Seconds 5 } Write-Host } } Else { $jobName = $dpjobs.Name While ((Get-SPTimerJob $jobName -Debug:$false) -ne $null) { Write-Host -ForegroundColor Yellow -NoNewLine "." Start-Sleep -Seconds 5 } Write-Host } } } Catch { Write-Error $_ Write-Host -ForegroundColor Red "Skipping $WSPFileName, Due to an error" Read-Host } } Else { $skip = $null $tryagain = $null Try { if ($output.Deployed -eq $true) { Write-Host -ForegroundColor Green "Retracting Solution" Uninstall-SPSolution -AllWebApplications -Identity $WSPFileName -Confirm:$false -ErrorAction Stop } } Catch { $tryagain = $_ } Try { if ($tryagain -ne $null) { Uninstall-SPSolution -Identity $WSPFileName -Confirm:$false -ErrorAction Stop } } Catch { Write-Host -ForegroundColor Red "Could not Retract Solution" } Sleep 1 $dpjobs = Get-SPTimerJob | Where { $_.Name -like "*$WSPFileName*" } If ($dpjobs -eq $null) { Write-Host -ForegroundColor Green "No solution deployment jobs found" } Else { If ($dpjobs -is [Array]) { Foreach ($job in $dpjobs) { $jobName = $job.Name While ((Get-SPTimerJob $jobName -Debug:$false) -ne $null) { Write-Host -ForegroundColor Yellow -NoNewLine "." Start-Sleep -Seconds 5 } Write-Host } } Else { $jobName = $dpjobs.Name While ((Get-SPTimerJob $jobName -Debug:$false) -ne $null) { Write-Host -ForegroundColor Yellow -NoNewLine "." Start-Sleep -Seconds 5 } Write-Host } } Try { Write-Host -ForegroundColor Green "Removing Solution from farm" Remove-SPSolution -Identity $WSPFileName -Confirm:$false -ErrorAction Stop } Catch { $skip = $_ Write-Host -ForegroundColor Red "Could not Remove Solution" Read-Host } if ($skip -eq $null) { Try { Write-Host -ForegroundColor Green "Adding solution to farm" Add-SPSolution "$WSPFullFileName" -Confirm:$false -ErrorAction Stop | Out-Null $gobal = $null try { Write-Host -ForegroundColor Green "Deploy solution to all Web Apps, will skip if this solution is globally deployed" Install-SPSolution -Identity "$WSPFileName" -GACDeployment -AllWebApplications -Force -Confirm:$false -ErrorAction Stop | Out-Null } Catch { $gobal = $_ } If ($gobal -like "*This solution contains*") { Write-Host -ForegroundColor Green "Solution requires global deployment, Deploying now" Install-SPSolution -Identity "$WSPFileName" -GACDeployment -Force -Confirm:$false -ErrorAction Stop | Out-Null } } Catch { Write-Error $_ Write-Host -ForegroundColor Red "Skipping $WSPFileName, Due to an error" Read-Host } Sleep 1 $dpjobs = Get-SPTimerJob | Where { $_.Name -like "*$WSPFileName*" } If ($dpjobs -eq $null) { Write-Host -ForegroundColor Green "No solution deployment jobs found" } Else { If ($dpjobs -is [Array]) { Foreach ($job in $dpjobs) { $jobName = $job.Name While ((Get-SPTimerJob $jobName -Debug:$false) -ne $null) { Write-Host -ForegroundColor Yellow -NoNewLine "." Start-Sleep -Seconds 5 } Write-Host } } Else { $jobName = $dpjobs.Name While ((Get-SPTimerJob $jobName -Debug:$false) -ne $null) { Write-Host -ForegroundColor Yellow -NoNewLine "." Start-Sleep -Seconds 5 } Write-Host } } } Else { Write-Host -ForegroundColor Red "Cannot Install $WSPFileName, Please try manually" Read-Host } } } |