StsAdm

SharePoint 2010 : RemoteStsAdm PowerShell Module

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 […] […] Few month ago I have introduced RemoteStsAdm, a PowerShell module that enable you to execute StsAdm.exe remotely. StsAdm.exe is a command line administration tools for SharePoint. Unfortunately to run StsAdm, one must log-in to SharePoint server member – since the tool can not be executed remotely.

SharePoint 2010 : RemoteStsAdm PowerShell Module

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.

SharePoint 2010: Remote StsAdm using PowerShell

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.

StsAdm –o copyfarmappbincontent is available in CodePlex

English Remember about critics to “stsadm –o copyappbincontent” to deploy SharePoint resource in my previous post here. At the end of the post, I think that it should be “stsadm –o copyfarmappbincontent” instead. Why? Because the last will work in centralized deployment mode, same as solution deployment. But what’s the secret? Why the standard copyappbincontent doesn’t work in farm configuration? I’ll post in another article. But now, I have created the project in Codeplex.

Critics to SharePoint resource deployment “stsadm –o copyappbincontent”

StsAdm –o copyfarmappbincontent is available in CodePlex - SharePoint and Other Things - Sep 0, 2009[…] Remember about critics to “stsadm –o copyappbincontent” to deploy SharePoint resource in my previous post here. […]

Critics to SharePoint resource deployment “stsadm –o copyappbincontent”

English When you start to work with localization in SharePoint, I believe that you may end with one of Mikhail Dikov proposal here or here . Partially I agree with his proposal, to leverage the resource deployment through the UI. However, his strategy may fail when you apply to server farm architecture with multiple Web Front End (WFE). You have to go to every WFE, and activate/deactivate the feature before you can get it deployed in all WFE.