Many of our folks in the field rely on SharePoint Farm Version number information in Central Administration to compare the patch level between servers. While this number is showing the latest SharePoint Foundation, it doesn’t always mean that you have a completely patched SharePoint farm. The reason, because Microsoft releases many different type of patches:
Cummulative updates (CU) Server packages (Uber packages) Public updates (PU) Stefan Gossner wrote an excellent blog about SharePoint patch terminology and the impact your farm patch level in “SharePoint Patching Demystified” .
English:
During the operation of our Reporting Service Server, one of our clients reported accidental reports unavailability. Following is the screen capture on his browser :
Accoding to server maintenance history, there was no action performed on that server. So, what can caused this sudden unavailability?
To investigate the issue, we activate ASP.NET debuging in web.config, and browse to the report page. And now we have more precise information that Microsoft.
SharePoint 2010 : RemoteStsAdm PowerShell Module | Ideas For … | Mastering Sharepoint - Sep 6, 2011
[…] the original post here: SharePoint 2010 : RemoteStsAdm PowerShell Module | Ideas For … ← SharePoint 2010 Development with Visual Studio 2010 (Microsoft […] SharePoint 2010: RemoteStsAdm PowerShell Module is available via NuGet | Ideas For Free - Dec 0, 2011
[…] Few month ago I have introduced RemoteStsAdm, a PowerShell module that enable you to execute StsAdm.
SharePoint 2010 : RemoteStsAdm PowerShell Module | Ideas For … | Mastering Sharepoint - Sep 6, 2011
[…] the original post here: SharePoint 2010 : RemoteStsAdm PowerShell Module | Ideas For … ← SharePoint 2010 Development with Visual Studio 2010 (Microsoft […] SharePoint 2010: RemoteStsAdm PowerShell Module is available via NuGet | Ideas For Free - Dec 0, 2011
[…] Few month ago I have introduced RemoteStsAdm, a PowerShell module that enable you to execute StsAdm.
English
The STSADM.exe is command-line tool for administration of Office SharePoint Server (SharePoint 2007, SharePoint 2010). It is installed on the same location as SharePoint Products and Technologies location: %COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\12\bin (for SharePoint 2007) or %COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\14\bin (for SharePoint 2010). You must be Farm Administrator to be able to run the tool.
By default, the STSADM.exe must be executed locally since it will access SharePoint Object Model.
English
The STSADM.exe is command-line tool for administration of Office SharePoint Server (SharePoint 2007, SharePoint 2010). It is installed on the same location as SharePoint Products and Technologies location: %COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\12\bin (for SharePoint 2007) or %COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\14\bin (for SharePoint 2010). You must be Farm Administrator to be able to run the tool.
By default, the STSADM.exe must be executed locally since it will access SharePoint Object Model.
English
If you have read my comments on the Writing Custom Web Service for SharePont, Is it supported here (http://blog.libinuko.com/2011/02/16/sharepoint-writing-custom-web-service-for-sharepoint-is-it-supported/) ; you may have already created standard ASPNET web services. It is working, but with some limitation:
You can not have path virtualization
Virtualization is one of SharePoint’s technique provided by SPVirtualPath provider, that enable virtualization of your web service path. For example, list.asmx will be available for http://mysite.com/_vti_bin/lists.asmx , or http://mysite.
English
In large network, issuing a command to remote server from current terminal is sometimes necessary. Some propose client-server mode; for example Remote StsAdm (http://netstsadm.codeplex.com/) and other propose to use PsExec (http://thingsthatshouldbeeasy.blogspot.com/2009/08/run-stsadm-commands-remotely.html).
The client-server mode requires installation of 3rd party tools. This kind of installation sometimes (or most of the time) is forbidden by company security policy.
Second option using PsExec from SysInternal (now part of Microsoft) doesn’t requires installation to SharePoint server and may be the correct approach.
PowerShell : Remote StsAdm using PowerShell | Ideas For Free - Aug 3, 2011
[…] Remember my previous post about how to avoid double hop problem? (http://blog.libinuko.com/2011/04/29/powershell-how-to-overcome-double-hop-problem-in-powershell-remo...) . Now we will create new function that uses Invoke-RemoteCommand. Basically, we will construct […] Mike C - Jun 5, 2012
I am getting the error shown below: Invoke-RemoteCommand : A parameter cannot be found that matches parameter name ‘cmd’. PS C:\Users\myname> invoke-command -script { Invoke-RemoteCommand -cmd “powershell -noprofile -command ‘dir \\server1\d$‘” -username “domain\myname” -password “########” } At line:1 char:51 + invoke-command -script { Invoke-RemoteCommand -cmd <<<< ”powershell -noprofile -command ‘dir \\server1\d$‘” -use rname “domain\myname” -password “#####3!