Comments for pshell.info

Comment on Uploading files to SharePoint Revisited by Alexey

Alexey — Sun, 04 May 2008 07:31:56 +0000

OpenRead is way more memory efficient in my recent experience. thanks for the hint.

Comment on Uploading files to SharePoint Revisited by Alexey

Alexey — Mon, 21 Apr 2008 03:08:17 +0000

I finally resorted to
$my_filestream=[io.file]::ReadAllBytes($my_filename)

Do you think OpenRead is better?

Comment on SharePoint, PowerShell and XML by SharePoint Thinks, Links and Clinks

SharePoint Thinks, Links and Clinks — Tue, 01 Apr 2008 16:27:26 +0000

STSADM Command References…

Quick Outline for more detailed items on STSADM, especially with PowerShell goodness TechNet Powerful…

Comment on Uploading Documents To SharePoint by pshell.info / Uploading files to SharePoint Revisited

pshell.info / Uploading files to SharePoint Revisited — Sun, 09 Mar 2008 19:06:34 +0000

[…] a long time ago I blogged about uploading files to SharePoint using PowerShell (see original article). That script used the get-content cmdlet and is very slow. The script below should work better as […]

Comment on Uploading Documents To SharePoint by Alexey

Alexey — Thu, 07 Feb 2008 07:08:31 +0000

A nice example, but it works some 10-60 times slower than WebDAV drag & drop (16 KB/sec local %windir%\system32\LogFiles upload - about 280 KB each). Any ideas as to how we can improve performance?

Comment on SharePoint, PowerShell and XML by Fred Morrison

Fred Morrison — Tue, 20 Nov 2007 14:24:42 +0000

To get stsadm to work in PowerShell, I had to add the following to profile.ps1, located in directory C:\WINDOWS\system32\windowspowershell\v1.0\.

Set-Alias -Name stsadm -Value $env:CommonProgramFiles”\Microsoft Shared\Web Server Extensions\12\BIN\STSADM.EXE”

Hope this helps others struggling with the same error.

Comment on PowerShell script to check ESX patch status by James Kamienski

James Kamienski — Mon, 19 Nov 2007 22:38:06 +0000

Oops! A little too quick on the draw…

You also need to add this so it decrypts the password back so it can be used with plink.exe

Below this line:

$password = Read-Host -assecurestring â€œEnter root passwordâ€

Add these:

$Ptr=[System.Runtime.InteropServices.Marshal]::SecureStringToCoTaskMemUnicode($password)
$password = [System.Runtime.InteropServices.Marshal]::PtrToStringUni($Ptr)

Now it should all work….

*8)

Comment on PowerShell script to check ESX patch status by James Kamienski

James Kamienski — Mon, 19 Nov 2007 21:35:22 +0000

A quick suggestion…

Put this line at the top of the script….

$password = Read-Host -assecurestring “Enter root password”

and remove this one…

$password=â€passwordâ€

This way you will be prompted for a password won’t have a text file sitting out there with your root password! *8)

Comment on SharePoint, PowerShell and XML by admin

admin — Mon, 05 Nov 2007 22:08:22 +0000

Fred,

It should work without doing anything special. I also have the path where stsadm.exe is in my system path variable. But that’s it. And that’s on a plain install of SharePoint with PowerShell added. Nothing else….

Comment on SharePoint, PowerShell and XML by Fred Morrison

Fred Morrison — Mon, 05 Nov 2007 19:15:09 +0000

Can’t run stsadm in PowerShell. When I try running STSADM.EXE from within PowerShell, as shown in your example, I get an error:
The term ’stsadm.exe’ is not recognized ….

I had previously issued a cd ‘C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN’ to make sure I was in the correct directory.

What else needs to be done to allow direct execution of stsadm.exe from within PowerShell?