English:

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. RemoteStsAdm is to answer this problem, allowing admin to execute StsAdm remotely. You can download the source code from MSDN Galery here or read the original article in previous post here. 

Yesterday, I have released ImportPSModule that will easy PowerShell module distribution, allow update notification and configuration. The RemoteStsAdm PowerShell module is now available via NuGet, so that you don’t need to download and extract manually. All will be done seamlessly, and whenever we got script update – you will get notified as soon as you open PowerShell session.

So what do you wait for, open PowerShell session and type following:

Import-PSModule RemoteStsAdm 

You may already know PsGet by Chaliy or PsGet by Anurse for PowerShell module distribution. They have created PowerShell module distribution mechanism with different approach.

Chaliy uses PowerShell script approach and customized module directory. Everytime you want to distribute your PowerShell module, you have to fork his github project to update Directory.xml content. Even tough the instruction in https://github.com/chaliy/psget/wiki/How-to-add-your-module-to-the-directory is very clear, however I think there is risk of incorrect Directory.xml modification.

Anurse uses PowerShell manifest approach and standard NuGet package to download and put module in appropriate location. In this case you can create a NuGet package containing PowerShell files and publish it to NuGet repository. Using his module, you will be able to get PowerShell module from NuGet repository right to your console. I like this approach because it uses standard NuGet package and publishing process. However, sometimes I want to be able to register the new module in my profile. I also want to ensure that I always use latest PowerShell Module package – ie. update local module automatically when there is new module in NuGet repository.

So then, I started to create Import-PSModule a PowerShell script module that will give you functionalities such as:

1. Importing PS Module from NuGet repository
2. Load imported module to current session
3. Register imported module to current user profile or all user profile
4. Un-register imported module from current user profile or all user profile
5. Auto-update imported module when user start PowerShell session

To start using the module, start PowerShell session and type following

(new-object Net.WebClient).DownloadString("http://blog.libinuko.com/wp-content/plugins/download-monitor/download.php?id=1") | iex 

The script will perform following actions:

1. Download latest ImportPSModule from central NuGet repository.
2. Install the package to desired location. If you choose to install in User-Module or Global-Module, all future packages will be installed under Module path. If you choose to install in other folder, then all future package will be installed within installation folder.
3. Load the ImportPSModule to the memory. It will also  download latest NuGet.CommandLine package if you don't have in your system.

So what do you waiting for? Start to install the module and publish your PowerShell module in NuGet repository. But don't forget TAG "PSModule" to your NuGet package.

If you want to validate InstallPSModule.ps1, please click here InstallPSModule (115) .

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:

1. 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.com/sites/myothersitecollection/_vti_bin/lists.asmx. The site collection has been virtualized by SharePoint.

   Without virtualization any web service consumer will have to access to the same path, usually in the root; for example /_services/mywebservice.asmx">/_services/mywebservice.asmx">http://<webapps>/_services/mywebservice.asmx

2. You can not have SPContext

   SPContext is very powerful object in SharePoint development. Using this context, we can retrieve current SharePoint context without having to instantiate it. For example, you can get current SPWeb by calling SPContext.Current.Web – and you don’t need to dispose it (in fact you’re not suppose to dispose it). Still using SPContext you can have direct access to list and everything under SharePoint.

   Without having direct access to SPContext, you have to instantiate SPWeb or SPSite using normal constructor with URL as parameter. It means new SPSite/SPWeb thread in the server memory, and you have to dispose it once you’ve done working with it.

So, how can we write custom web service for SharePoint in supported mode?

Before we start, we have to understand SharePoint architecture and how does the processing works for web services. I take following picture from SharePoint Architecture in MSDN. It describe how SharePoint process our request. There is SPHttpApplication which has SPRequestModule and any additional ASP.NET Module; and before the request returned back to the user SPHttpHandler is doint the job.

How SharePoint process web services?

If we dig into into the process on how SharePoint process request to web services in _vti_bin.

There are 3 scenarios of http request to the web services,

1. Disco request, identified by suffix ?DISCO in the web service address. For example, */_vti_bin/list.asmx?Disco
2. WSDL request, identified by suffix ?WSDL in the web service address. For example, */_vti_bin/list.asmx?Wsdl
3. Web service post request. For example, */_vti_bin/list.asmx?op=GetListItems

Every request will be processed by SPHttpHandler (SharePoint) and ScriptHandlerFactory (system.web.extension), but the SPHttpHandler will be selective only for Disco and Wsdl request.

On disco/wsdl request, SPHttpHandler will transfer the request to wsdisco.aspx or wswsdl.aspx using Server.Execute operation. This operation ensure that wsdisco.aspx/wswsdl.aspx is receiving same request object. wsDISCO.aspx or wsWSDL.aspx will then instantiate SharePoint Context object. Any *.aspx will be successfully instantiate SharePoint context object because they are managed by SPHttpApplication and hence it also impacted by SPVirtualPath provider from SharePoint which will activate path virtualization.

Next, wsDISCO.aspx will transfer the request to the <service>DISCO.aspx and wsWSDL.aspx will transfer to the <service>WSDL.aspx – using Server.Execute operation. So here we have seen 2 transfer operation. At the end, the result is correct WSDL/DISCO request. The correct WSDL/DISCO will point to the correct virtual path of the request. (Remember how do you create <service>disco.aspx / <service>wsdl.aspx)

When a consumer use the contract and tries to consume it. The SPHttpHandler will no longer intercept the request, but the normal ScriptHandlerFactory from System.Web.Extensions. However with the correct path in disco/wsdl, now the asmx now have the ability to look into current context from SharePoint. And hence you will be able to use SPContext.Current.Web in custom web services.

Part-2 is how to start create custom web services. I will need help from my buddy Denni , he will code for me. –

References

1. Writing Custom Web Services for SharePoint Products and Technology (http://msdn.microsoft.com/en-us/library/dd583131(v=office.11).aspx)

2. SharePoint Architecture (http://msdn.microsoft.com/en-us/library/bb892189(v=office.12).aspx )

3. Architectural Overview of Windows SharePoint Services (http://msdn.microsoft.com/en-us/library/dd583133(v=office.11).aspx)

4. Modifying Built-In SharePoint Files (http://msdn.microsoft.com/en-us/library/bb803457(v=office.12).aspx)

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. However, I am not convince that this tools will be compatible with the future Operating System.

So, what is the option?
PowerShell and Remoting!

PowerShell has been introduced during Windows 2008 era. However, Windows 2003 server owner can apply KB968930 (http://support.microsoft.com/kb/968930) to bring PowerShell functionality to their server. PowerShell will replace command.com because of the flexibility – enabling integration between shell and operating system itself.

Let's get our job done

1. First enable remoting on the SharePoint Server.

    Enable-PSRemoting -Force

2.  Prepare the stsadm command alias

 $executable = "$env:ProgramFiles\Common Files\Microsoft Shared\web server extensions\12\bin\stsadm.exe" 

3.  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-remoting-2/) . Now we will create new function that uses Invoke-RemoteCommand. Basically, we will construct commandline parameter for Invoke-RemoteCommand. We also try to provide AS-IF user call stsadm.

function StsAdm
{
   param(
      [string] $commandOptions,
      [string] $username,
      [string] $password
   )

   $executable = "$env:ProgramFiles\Common Files\Microsoft Shared\web server extensions\12\bin\stsadm.exe"

   Invoke-RemoteCommand -commandline "'$executable' $commandOptions" -username $username -password $password

}

Usage : StsAdm -commandOptions "-o enumwebs" -username "setup account" -password "setup password"

And voila, you have remote stsadm function without compromising security policy.

English

There are some webcast about Microsoft Project 2010 Solution Starters. It demonstrate the power and extensibility of SharePoint 2010 and Project 2010. Find out yourself on user experience series and code walkthrough here:

User experience series:

1. Microsoft Project 2010 Solution Starters – User Experience #1
2. Microsoft Project 2010 Solution Starters – User Experience #2

Code walkthrough:

1. Microsoft Project 2010 Solution Starters Drilldown & Code Walkthrough #1
2. Microsoft Project 2010 Solution Starters Drilldown & Code Walkthrough #2
3. Microsoft Project 2010 Solution Starters Drilldown & Code Walkthrough #3
4. Microsoft Project 2010 Solution Starters Drilldown & Code Walkthrough #4

So , are you dare to take the challenge and move to the new platform?

English

When I am looking for a way to compress file(s) into Zip, I find a blog from David Aiken here (Compress Files with Windows PowerShell then package a Windows Vista Sidebar Gadget) . I will just focus on Add-Zip function and nothing more.

Here is the original code:

function Add-Zip
{
    param([string]$zipfilename) 

    if(-not (test-path($zipfilename)))
    {
           set-content $zipfilename ("PK" + [char]5 + [char]6 + ("$([char]0)" * 18))
           (dir $zipfilename).IsReadOnly = $false
     } 

     $shellApplication = new-object -com shell.application
     $zipPackage = $shellApplication.NameSpace($zipfilename) 

     foreach($file in $input)
     {
            $zipPackage.CopyHere($file.FullName)
            Start-sleep -milliseconds 500
     }
}

usage: dir c:\demo\files\*.* -Recurse | add-Zip c:\demo\myzip.zip

I am raising two problems with the code:

1. Looking at the usage example, it is clear that the function accept only fully path filename. The reason, on line-12 , the $shellApplication.NameSpace parameter is $zipfilename; and this is not possible without giving fully path filename.

2. On line-16, the operation expect that $input array will contains object with FullName properties, that why the usage example uses DIR. What about if you just want to specify a filename?

With the 2 problem above, I am ready to improve that function. In the new improved version, Get-ChildItem will help us to convert any string representation of a file to a fully path filename. It won’t break DIR piping functionality, since actually Get-ChildItem is dir (and extra) functionality.

Here is the improved version:

function Add-Zip
{
	param([string]$zipfilename)

    $currFile = $zipfilename | get-childitem
	if(-not (test-path($zipfilename)))
	{
		set-content $currFile.FullName ("PK" + [char]5 + [char]6 + ("$([char]0)" * 18))
		(dir $currFile.FullName).IsReadOnly = $false
	}

	$shellApplication = new-object -com shell.application
	$zipPackage = $shellApplication.NameSpace($currFile.Fullname)

	$input | % {
            $file = $_ | get-childitem
            $zipPackage.CopyHere($file.FullName)
            Start-sleep -milliseconds 500
	}
}

usage: "FileInThisFolder.txt" -Recurse | add-Zip "ZipInThisFolder.zip"
        dir c:\demo\files\*.* -Recurse | add-Zip c:\demo\myzip.zip

So, I hope you enjoy the improved version.

English:

I am interesting to the PowerShell remoting topic from PowerShell Cookbook Chapter 29 here (http://www.pavleck.net/powershell-cookbook/ch29.html). In order to solve double-hop problem, it uses schedule task. The sample create schedule task to Enable-PSRemoting in remote machine.

But don’t you think we need something more generic to overcome double-hop problem? PowerShell offers Enable-WSManCredSSP or Kerberos so that the process can delegates the credential to execute next-hop process. However,  CredSSP is only available on Windows 7 and above. What about OS before Windows 7 or Windows Server 2008?  If you have Windows 7 or Windows Server 2008 – you may follow tutorial in this link (http://www.ravichaganti.com/blog/?p=1230). But if you have Windows 2003 or previous version, then you must keep reading.

So, lets start by defining our function Invoke-RemoteCommand. This command will accept :

1. (Optional) Taskname, name of task identifier
2. Commandline, actual command for example powershell or cmd.exe
3. Username, credential to execute the command
4. Password, password for the credential to execute the command

function Invoke-RemoteCommand{

    param(
       [System.String]
       $taskname = (get-date -format "'Demo task' dd-MM-yyyy hh.mm.ss"),

       [System.String]
       $commandline = "cmd /c 'dir c:\'",

       [Parameter(Mandatory=$true)]
       [String]
       $username,

       [parameter(Mandatory = $true)]
       [String]
       $password
   )

    schtasks /create /tn $taskname /tr $commandline /sc weekly  /ru $username /rp $password | out-null
    schtasks /run /tn $taskname | out-null
    write-host "Waiting task execution." -nonewline -foreground green
    do {
      $taskStatus = schtasks /query /fo csv /v | convertfrom-csv | ? { $_.TaskName.TrimStart("\") -eq "$taskname"}
      sleep 10
      write-host "." -nonewline -foreground green
    } while ($taskStatus."Status" -eq "Running")
    write-host "Success!" -foreground green
    schtasks /delete /tn $taskname /f | out-null
    return $taskStatus
}

For example, we want to list directory of the ServerX by issuing command to ServerY. Normally, following command will fail because of double-hop problem (it doesn’t matter whether you supply user credential, it will still failed):

Invoke-Command -ComputerName ServerY -Script { "dir \\ServerX\d$" }

Using the new function, we change the command into

invoke-command -script { Invoke-RemoteCommand -cmd "powershell -noprofile -command 'dir \\ServerX\d$'" -username "domain\user" -password "password" }

The last script will performs following:

1. Create schedule tasks with a specific identifier

2. Command in schedule task is “powershell –noprofile …..”

3. Execute schedule tasks

4. Wait until execution completes

5. Return the status

Finally, the script will work in Windows 2003 , Windows 7, Windows Vista or Windows 2008.

English

In previous post I have demonstrated “How to create cascading lookup field” in SharePoint 2010 using InfoPath. I will extend the possibility by utilizing Client Object Model and SharePoint Designer; therefore we don’t need InfoPath to have the cascading lookup field.

Using same scenario where City is cascading lookup field from the selected Country, we’ll see together how Client Object Model solve the problem. In this solution we need to create JS referral to SP.js for Client Object Model and JQuery to help us working with DOM.

Some key points in the video:

1. Put JQuery distribution in 14hive\Layouts.

2. Add Javascript link referral in the AdditionalPageHead place holder.

   1: <SharePoint:ScriptLink Language="Javascript" Localizable="False" runat="server" Name="jquery-1.4.4.min.js"/>

   2: <SharePoint:ScriptLink Name="SP.js" runat="server" OnDemand="true" Localizable="false"/>

3. Add Javascript code to modify cascading selector and create Client Object Model call to retrieve cascaded value in Main conten place holder.

   1: <script type="text/javascript">

   2: // JQuery_Script

   3: 

   4: var spListItems;

   5: 

   6: // Cascading lookup main function

   7: function FilterLookup(filterSource,lookupList)

   8: {

   9:    var filterElement = $("select[title='" + filterSource + "'] option:selected");

  10:    if(filterElement.length == 0) return;

  11: 

  12:    var selectedFilterText =  filterElement.text();

  13:    var selectedFilterValue = filterElement.value;

  14:

  15:    var clientCtx = new SP.ClientContext.get_current();

  16:    var spList = clientCtx.get_web().get_lists().getByTitle(lookupList);

  17:

  18:    var camlQuery = new SP.CamlQuery();

  19:    camlQuery.set_viewXml('<View><Query><Where><Eq><FieldRef Name=\''+ filterSource +'\'/>' +

  20:         '<Value Type=\'Text\'>'+ selectedFilterText +'</Value></Eq></Where></Query></View>');

  21:

  22:    this.spListItems = spList.getItems(camlQuery);

  23:    clientCtx.load(spListItems);

  24:    clientCtx.executeQueryAsync(Function.createDelegate(this, this.onQuerySucceeded), Function.createDelegate(this, this.onQueryFailed) );

  25:

  26: } // 

  27: 

  28: function onQuerySucceeded(sender, args) {

  29: 

  30:    alert(this.selectedFilterText);

  31:    // Get CityElement Select or Input

  32:    var cityElement = $("select[title='City']");

  33:    if(cityElement.length == 0) { alert('Unknown'); }

  34: 

  35:     var options = '';

  36:     var listItemEnumerator = spListItems.getEnumerator();

  37:

  38:     while (listItemEnumerator.moveNext()) {

  39:         var oListItem = listItemEnumerator.get_current();

  40:         options += '<option value="' + oListItem.get_id() + '">' + oListItem.get_item('Title') +'</option>';

  41:     }

  42:    cityElement.html(options);

  43: }

  44: 

  45: function onQueryFailed(sender, args) {

  46:     alert('Request failed. ' + args.get_message() + '\n' + args.get_stackTrace());

  47: }

  48: 

  49: 

  50: // Attach function on document ready

  51: $(document).ready(

  52:    function() {

  53:       ExecuteOrDelayUntilScriptLoaded(FilterLookup,"sp.js");

  54:       //FilterLookup("Country","City");

  55:

  56:        // Get CountryElement Select or Input

  57:       var countryElement = $("select[title='Country']");

  58:       if(countryElement.length == 0)

  59:       {

  60:            countryElement = $("input[title='Country']");

  61:       }

  62:       if(countryElement.length != 0) {

  63:        if(countryElement[0].optHid) {

  64:           $("input[id='" + countryElement[0].optHid + "']").bind("propertychange", function() { FilterCity(); });

  65:

  66:        } else{

  67:           $("select[title='Country']").change(function() { FilterLookup("Country","City"); });

  68:

  69:        }

  70:

  71:    }

  72:

  73: 

  74:    }); // Document ready

  75: 

  76: </script>

4. Finally save and set the new form as default form.

English:

Sometimes you may received a request to change rating icons, from a normal star to a love icon. So, how would you do it?

Figure 1. Original rating icons

Figure 2. Modified love rating icons

1. Find and prepare rating icons.  In this case I will need to prepare 4 styles rating icons

Title	Sample	Size
a. Empty Rating		16×16
b. Selected Rating		16×16
c. Rating Overlay		448×16
d. Rating Overlay RightToLeft		448×16

2. Save the new icons under 14 hive\Images.

3. Create script to modify SPWeb property bag. To ease our job, I will use PowerShell script as follows,

[System.Reflection.Assembly]::LoadWithPartialName(“Microsoft.SharePoint”) > $null

$spSite = new-object Microsoft.SharePoint.SPSite(“http://win2k8″);
$spWeb = $spSite.OpenWeb();

$spWeb.Properties["Ratings_NewRatingIconUrl"] = “/_layouts/Images/love_RatingsNew.png”;
$spWeb.Properties["Ratings_EmptyIconUrl"] = “/_layouts/Images/love_RatingsEmpty.png”;
$spWeb.Properties["Ratings_ImageStripUrl"] = “/_layouts/Images/love_Ratings.png”;
$spWeb.Properties["Ratings_ImageStripRtlUrl"] = “/_layouts/Images/love_Ratingsrtl.png”;

$spWeb.Properties.Update();
$spWeb.Dispose();
$spSite.Dispose();

iisreset

4. Voila ! And you can refresh your browser to see the changes.

5. Finally you can distribute your solution into a solutions package with feature activation events to register/un-register custom rating images.

English:

This is graphical guidelines to disable My Site or My Profile link in a portal.

1. Open Central Administration , and click on “Manage service applications”.

2. Open Central Administration , and click on “Manage service applications”.

3. Click on “Manage User Permissions”

4. Remove “Use Personal Features” permission for the Groups/Users.

5. If you can’t see the new rules being reflected in the site. You can restart “User Profile Service”

6. And now, the users will not be able to see My Site / My Profiles link.