elprimeriso

2011-09-09T16:11:00.003-04:00

Los 10 artistas con más números uno de la historia http://goo.gl/ugPNY

2011-09-09T16:11:00.001-04:00

Los 10 artistas con más números uno de la historia http://goo.gl/ugPNY

2011-09-09T16:05:00.003-04:00

Lista de acortadores url. Ranks Alexa. http://ping.fm/4d8Cy

2011-09-09T16:05:00.001-04:00

Acortadores de url para el uso empresarial de Twitter | Twitter para las empresas http://ping.fm/yxp5F

2011-09-09T16:02:00.001-04:00

Acortadores de url para el uso empresarial de Twitter | Twitter para las empresas http://v.gd/jylOGG

2011-09-09T15:55:00.001-04:00

v.gd - The ethical URL shortener (acortador de URLS) http://v.gd/

2011-09-09T15:52:00.001-04:00

11 Actresses Who Won Oscars By Playing Prostitutes http://goo.gl/DDX2p

2011-09-09T15:39:00.001-04:00

10 Preguntas y Respuestas sobre Steve Jobs http://ping.fm/fX98x

2011-09-09T15:30:00.001-04:00

Los 10 asesinos seriales más famosos en la historia http://ping.fm/x2dsv

2011-09-01T14:21:00.001-04:00

Google lanza una versión off-line de Calendar,Gmail y Docs (google Gmail, Docs and Calendar offline)

2011-09-01T13:55:00.001-04:00

http://ping.fm/KDe1b (red social basada en el anonimato de los usuarios, para compartir mensajes y pensamientos)

2011-08-22T14:27:00.001-04:00

http://yumalicio.us. foods Photos. comida en imagenes

2011-08-04T12:18:00.001-04:00

Generate a Random Name - Generador de nombre y datos personales http://ping.fm/ZZriy

http://htxt.it/ZTAq

2011-05-17T15:30:00.001-04:00

http://htxt.it/ZTAq

http://htxt.it/xPhg

2011-05-17T14:36:00.001-04:00

http://htxt.it/xPhg cientos de Recetas sobre Pizzas.

http://htxt.it/MATX

2011-04-18T13:43:00.001-04:00

http://htxt.it/MATX primeras fotos (history.the first photo)

http://htxt.it/IgZD

2011-04-11T13:27:00.001-04:00

http://htxt.it/IgZD Search for relevant real-time-updated content in 1192026 feeds.Busca contenidos dentro de los canales feeds que tiene almacenados

Frases nucleares par

2011-04-06T13:33:00.001-04:00

Frases nucleares para la vergüenza... | Greenpeace España http://htxt.it/WRFE

50 publicidades cont

2011-04-04T15:49:00.001-04:00

50 publicidades controvertidas con connotaciones sexuales | Diego Mattei Blog http://htxt.it/TQf8

http://blekko.com (n

2010-11-02T12:45:00.001-05:00

http://blekko.com (nuevo buscador de Internet)

http://3.ly/g2mc . P

2010-09-30T13:14:00.001-04:00

http://3.ly/g2mc . Posiciones mas Salvajes del Kamasutra :)

Philips Airfryer te

2010-09-10T16:10:00.001-04:00

Philips Airfryer te permite freír sin aceite (http://is.gd/f4A9h)

http://htxt.it/IZca

2010-09-07T10:12:00.001-04:00

http://htxt.it/IZca .Web con Curiosidades en listas del 1 al 10

http://fur.ly/1nxp.

2010-08-31T10:52:00.001-04:00

http://fur.ly/1nxp. Fantastica Coleccion de Imagenes(11 links with Beautiful Photography)

http://htxt.it/R9SU

2010-08-31T09:13:00.001-04:00

http://htxt.it/R9SU Fotos surrealistas(Surreal Photo Manipulation:40 Amazing Artwork)

help

2010-08-27T08:42:00.001-04:00

help

http://htxt.it/Nym7

2010-07-29T12:47:00.001-04:00

http://htxt.it/Nym7 .Diccionario español de abreviaturas para SMS y chat

http://htxt.it/cQnm

2010-07-29T12:32:00.001-04:00

http://htxt.it/cQnm (new chat rooms decoder) abreviaturas que se utilizan en las salas chat.

PowerShell Blogs (Good bye cmd)

2010-02-04T13:50:00.001-05:00

http://fur.ly/elj . 3 in 1 links about Powershell (3 blogs sobre microsoft PowerShell )

Acortadores de URL.(url shortening service)

2010-02-02T12:15:00.000-05:00

http://fur.ly/eez (3 articles about url shortening.articulos sobre acortadores de URLs)

Super acortadores de URLs (fantastic url shortening services)

http://fur.ly/ (permite crear una url corta en la que se guardan varias direcciones web.Shorten multiple urls into one )

http://urlcorta.es/ (permite crear tres urls reducidas al mismo tiempo,para un solo enlace. 3x1. urlcorta.es, goo.gl, r.im)

help

2010-02-01T15:49:00.001-05:00

help

Lista de códigos para crear carpetas especiales en Windows 7

2010-01-07T15:37:00.001-05:00

Primero fue el modo Dios ahora siguen los codigos esta vez los revela presidente de Windows Steven Sinofsky a Cnet. En la medida que los pruebe pondre para que son.

Aqui se muestran las versiones tanto en ingles como en castellano

Aqui van mis pruebas:

Frameworks CSS

2010-01-04T13:37:00.000-05:00

En esta web se muestra un interesante articulo donde se muestrar 12 frameworks CSS que segun el autor deberiamos conocer.
La grafica esta tomada un articulo ,(Frameworks CSS mas usados), publicado en la misma web.

Enable the secret ‘GodMode’ in Windows 7 (Explorador de Windows 7 en GodMode)

2010-01-04T13:08:00.000-05:00

GodMode is the name given to cheats in video games that provide you with all weapons and access to all areas. As it turns out, Windows 7 has a GodMode cheat as well as uncovered by Caschy. It is basically a control panel of sorts which provides you access to all the features in one explorer window. In the Windows 7 control panel, features are grouped together either in categories or control panel item names. Nothing is grouped under anything in GodMode.
Here’s how to enable it:

Create a new folder.
Rename it to : GodMode.{ED7BA470-8E54-465E-825C-99712043E01C}
That’s it. The icon should change to the one shown below:

This is what the GodMode Window will look like:

I still prefer the control panel over GodMode since everything is easier to find under the categories. I’ve tired this in Windows 7 Ultimate x64 and it works fine. If you try it in Windows Vista, let us know if it works in the comments.

Un Articulo sobre el mismo tema pero esta vez en nuestro idioma. gracias a (http://feeds.feedburner.com/Despuesdegoogle)

http://despuesdegoogle.com/2010/01/04/explorador-de-windows-7-en-godmode/

John W Powell : SharePoint Database Naming Standards

2009-12-21T16:14:00.000-05:00

John W Powell : SharePoint Database Naming Standards

Interesante articulo, que propone un sistema de nomenclatura para las diferentes bases de datos que se crean durante el despliege de una solucion SharePoint. En mi caso utilizo un sistema muy similar solo que todas mis base SharePoint comienzan con MOSS_, es decir:

MOSS_[Farm Name]_[Database Type]_[Name]

Sharepoint 2007 (el otro blog): Nuevas Soluciones de Graficos con JQuery!

2009-12-21T15:55:00.000-05:00

Sharepoint 2007 (el otro blog): Nuevas Soluciones de Graficos con JQuery!

Soluciones mayormente gratuitas, para graficar datos utilizando Jquery

1 – HighCharts http://www.highcharts.com/
2 - Artness mooCSSChart
3 – PlotKit http://www.liquidx.net/plotkit/
4 – JQuery SparkLine http://www.omnipotent.net/jquery.sparkline/
5 – JsCharts http://www.jscharts.com/examples

formspring.me

2009-12-15T16:36:00.001-05:00

Ask me anything http://formspring.me/yodelmis

help

2009-12-15T10:52:00.001-05:00

help

wallcoo.com

2009-12-14T16:59:00.000-05:00

猫猫壁纸酷 wallcoo.com：专业壁纸下载站，提供多分辨率桌面壁纸、宽屏壁纸。
La mejor galería de Wallpapers del mundo
La web es en chino pero vale la pena. Existe http://www.wallcoo.net/ que debe ser la version en ingles, pero este site no se actualiza con frecuencia.
No te preocupes por el idioma, ya que es facil navegar por el.
Ver un Articulo en http://feedproxy.google.com/~r/Arturogoga/~3/WFgW-yueI9o/. Existe mas informacion en

2009-12-01T14:00:00.001-05:00

2009-11-27T13:25:00.001-05:00

service

Premios Bitacoras.com 2009 Ganadores de los Premios Bitacoras.com 2009

2009-11-16T14:12:00.000-05:00

Microblogger del Año: m0d
Mejor Blog Personal: ThinkWasabi
Mejor Blog Tecnológico: ALT1040
Mejor Blog de Negocios: Gurusblog
Mejor Blog de Educación: Yoriento
Mejor Blog de Viajes: Crónicas de una cámara
Mejor Blog de Software y Seguridad: aNieto2K
Mejor Blog Gastronómico: Javi Recetas
Mejor Blog de Humor: Palomitas y Maíz
Mejor Blog Político: Escolar.net
Mejor Blog Cultural: Maikelnai’s Blog
Mejor Blog Periodístico: Blog de Enrique Meneses
Mejor Blog Deportivo: Información Deportiva
Mejor Fotolog: Cristina Granados Photoblog
Mejor Podcast: Kafelog
Mejor Videoblog: Malviviendo
Mejor Blog Social-Medioambiental: S.O.S. Paisajes de Mar
Mejor Blog del Público: Flapa
Mejor Blog del Jurado: La Aldea Irreductible
Premio Especial Honorífico: José Luis Orihuela

aNieto2K | Desarrollo web, Wordpress, y alguna cosilla más

2009-11-16T14:10:00.000-05:00

Mejor Blog de Software y Seguridad:
aNieto2K | Desarrollo web, Wordpress, y alguna cosilla más

SharePoint Solution Installer

2009-11-09T13:30:00.000-05:00

This project is a Windows application for an eased and more user
friendly installation and deployment of SharePoint 2007 solution files
to a SharePoint server farm. Distribute your SharePoint solution files
with this installation program instead of a raw script using STSADM.EXE
to install and deploy the solution.

STSADM Command Line Reference

2009-11-09T12:40:00.000-05:00

STSADM Command Line Reference

Royalty Free Icons & Clipart Stock Images ~ Icons Etc.

2009-11-03T14:34:00.000-05:00

Icons Etc is pleased to offer 115,626 free icons and clipart stock images for web design, application design, graphic design, and many other purposes

115,626 icons de exelente calidad y libres de pago

more:
Royalty Free Icons & Clipart Stock Images ~ Icons Etc.

Quick and Easy way to mass detached all user databases in Microsoft SQL | Nevermore.us

2009-11-03T12:34:00.000-05:00

So, i was cleaning up my “test server” and wanted to detach all the databases i had currently attached in MS SQL. Assuming you installed everything to their default locations this is all you should need to do in order to mass detach all the user db’s.

Como hacer detach de una base de datos sql. Aun cuando en el ejemplo se hace para todas las bases se puede hacer para una unica base de datos

more :
Quick and Easy way to mass detached all user databases in Microsoft SQL | Nevermore.us

more about SSEUTILS.exe by microsoft (esto fue sacado de la pagina de microsoft)

Overview

SSEUtil.exe is a tool that lets you easily interact with SQL Server. Among other things, it allows you to:
• Connect to the main instance or user-instance of SQL Server.
• Create, attach, detach, and list databases on the server.
• Upgrade database files to match the version of the server.
• Execute SQL statements via the console (similar to SQLCMD).
• Retrieve the version of SQL Server running.
• Enable and disable trace flags (for example, to trace SQL statements sent to the server by any client application)
• List the instances of SQL Server on the local machine or on remote machines.
• Checkpoint and shrink a database
• Measure the performance of executing specific queries.
• Create and playback lists of SQL commands for the server to execute.
• Log all input and output.

link to download (para descargar):
http://www.microsoft.com/downloads/details.aspx?FamilyID=fa87e828-173f-472e-a85c-27ed01cf6b02&displaylang=en

traducciones: yomismo

How to use STSADM to Find Site Template Codes and Script Site Creation | eHow.com

2009-10-29T16:31:00.000-05:00

Este articulo puede ser muy importante si, ya que en el se enumeran las diferentes plantillas que trae el sharepoint, en sus versiones MOSS y WSS.
How to use STSADM to Find Site Template Codes and Script Site Creation | eHow.com

111 CSS Gallery To Submit Your Design | Listelog

2009-10-28T09:08:00.000-05:00

111 CSS Gallery To Submit Your Design | Listelog

Five Simple But Powerful PowerShell Functions/Filters for SharePoint

2009-10-27T10:00:00.000-05:00

En este articulo se definen 1 funcion para el trabajo con sharepint

.Get-LocalFarm

Ademas se definen 4 filtros para aplicar a dicha funcion:
.Get-WebService
.Get-WebApplication
.Get-SiteCollection
. Get-Web

See More:

Five Simple But Powerful PowerShell Functions/Filters for SharePoint

PowerShell Tutorial for Beginners - Introduction | PowerShell Pro!

2009-10-26T16:43:00.000-05:00

PowerShell Tutorial for Beginners - Introduction | PowerShell Pro!: "PowerShell Tutorials

* PowerShell Tutorials
* PowerShell Console
* PowerShell Cmdlet
* PowerShell Aliases
* PowerShell Parameters, Objects, and Formatting
* PowerShell Providers
* PowerShell Scripting
* Variables, Arrays, and Hash Tables
* Conditional Logic
* Conditional Logic Using Loops
* PowerShell Functions and Filters - The basics
* PowerShell Scripting with WMI (Properties)
* PowerShell Scripting with WMI Part 2 (Methods)
* PowerShell Scripting with WMI Part 3 (Reports)
* Managing Active Directory with Windows PowerShell"

Master-PowerShell | With Dr. Tobias Weltner - PowerShell.com

2009-10-26T16:12:00.000-05:00

Exelente tutorial sobre powershell
este tutorial esta dividido en:

Chapter 1. The PowerShell Console

Welcome to PowerShell! This chapter will introduce you to the PowerShell console and show you how to configure it, including font colors and sizes, editing and display options.
Chapter 2. Interactive PowerShell

PowerShell has two faces: interactivity and script automation. In this chapter, you will first learn how to work with PowerShell interactively. Then, we will take a look at PowerShell scripts.
Chapter 3. Variables

It is time to combine commands whenever a single PowerShell command can't solve your problem. One way of doing this is by using variables. PowerShell can store results of one command in a variable and then pass the variable to another command.

In addition, variables are rich 'objects' and can do much more than simply store data. In this chapter, we'll explain what variables are and how you can use them to solve complex problems.
Chapter 4. Arrays and Hashtables

No matter how many results a command returns, you can always store the results in a variable because of a clever trick. PowerShell automatically wraps results into an array when there is more than one result. In this chapter, you'll learn how arrays work.

You'll also discover a special type of array, a hash table. While normal arrays use a numeric index to access their elements, hash tables use key-value-pairs.
Chapter 5. The PowerShell Pipeline

The PowerShell pipeline chains together a number of commands similar to a production assembly. So, one command hands over its result to the next, and at the end, you receive the result.
Chapter 6. Using Objects

PowerShell always works with objects. Whenever you output objects into the PowerShell console, PowerShell automatically converts the rich objects into readable text. In this chapter, you will learn what objects are and how to get your hands on PowerShell objects before they get converted to simple text.
Chapter 7. Conditions

You'll need a condition first to compose intelligent PowerShell code capable of making decisions. That's why you'll learn in the first part of this Chapter how to formulate questions as conditions.

In the second part, you'll employ conditions to execute PowerShell instructions only if a particular condition is actually met.
Chapter 8. Loops

Loops are a good example that iterations do not have to be boring. They repeat particular PowerShell statements with the pipeline being one of the areas where you can benefit from loops. Most PowerShell commands wrap their results in arrays, and you'll need a loop when you want to examine single elements in an array more closely.
Chapter 9. Functions

PowerShell has the purpose of solving problems, and the smallest tool it comes equipped with for this is commands. By now you should be able to appreciate the great diversity of the PowerShell command repertoire: in the first two chapters, you already learned how to use the built-in PowerShell commands called cmdlets, as well as innumerable external commands, such as ping or ipconfig. In Chapter 6, the objects of the .NET framework, API calls, and COM component statements were added, providing you with a powerful arsenal of commands.

In Chapters 3-5, command chains forged out of these countless single commands combined statements either by using variables or the PowerShell pipeline.

The next highest level of automation is functions, which are self-defined commands that internally use all of the PowerShell mechanisms you already know, including the loops and conditions covered in the last two chapters. You can also use functions to get the better of the more complex problems that consist of many separate instructions and sequences.
Chapter 10. Scripts

PowerShell scripts function like batch files in the traditional console: scripts are text files that can include any PowerShell code. If you run a PowerShell script, PowerShell will read the instructions in it, and then execute them. As a result, scripts are ideal for complex automation tasks. In this chapter, you'll learn how to create and execute scripts.

PowerShell makes certain requirements mandatory for their execution because scripts can contain potentially dangerous statements. Depending on the security setting and storage location, scripts must have a digital signature or be specified with their absolute or relative path names. These security aspects will also be covered in this chapter.
Chapter 11. Finding and Avoiding Errors

The more complex your commands, pipelines, functions, or scripts become, the more often that errors can creep in. PowerShell has its own remedies for finding and correcting errors at various levels of complexity.

In simple cases, use "what-if" scenarios to check whether a command or a pipeline is really doing what you expect it to do. With the help of such scenarios, you can simulate the result of commands without actually executing the commands. You can permit commands to do their work only after you're convinced that the commands will function flawlessly.

If you've written your own functions or scripts, PowerShell can also step through the code and halt its execution at locations called breakpoints, which allow you to examine functions or scripts more closely at these locations. You can verify whether variables actually do contain an expected result. Moreover, PowerShell offers you the option of integrating debugging messages into functions or scripts. This enables your code to output progress reports to you at key locations when your code is in the development stage.
Chapter 12. Command Discovery and Scriptblocks

In previous chapters you learned step by step how to use various PowerShell command types and mechanisms. After 11 chapters, we have reached the end of the list. You'll now put together everything you've seen. All of it can actually be reduced to just two PowerShell basic principles: command discovery and scriptblocks.

The purpose of this chapter is to tie up the many loose ends of previous chapters and to weave them into a larger whole: the basics are complete and the remaining chapters will put the knowledge gained to the test of daily tasks.
Chapter 13. Text and Regular Expressions

PowerShell distinguishes sharply between text in single quotation marks and text in double quotation marks. PowerShell won't modify text wrapped in single quotation marks but it does inspect text in single quotation marks and may modify it by inserting variable contents automatically. Enclosing text in double quotation marks is the foremost and easiest way to couple results and descriptions.

The formatting operator -f, one of many specialized string operators, offers more options. For example, you can use -f to output text column-by-column and to set it flush. Other string commands are also important. They can replace selected text, change case, and much more.

Pattern recognition adds a layer of complexity because it uses wildcard characters to match patterns. In simple cases, you can use the same wildcards that you use in the file system. Substantially more powerful, but also more complex, are regular expressions.
Chapter 14. XML

Raw information used to be stored in comma-separated lists or .ini files, but for some years the XML standard has prevailed. XML is an acronym for Extensible Markup Language and is a descriptive language for any structured information. In the past, handling XML was difficult, but PowerShell now has excellent XML support. With its help, you can comfortably wrap data in XML as well as read existing XML files.
Chapter 15. The File System

The file system has special importance within the PowerShell console. One obvious reason is that administrators perform many tasks that involve the file system. Another is that the file system is the prototype of a hierarchically structured information system. In coming chapters, you'll see that PowerShell controls other hierarchical information systems on this basis. You can easily apply what you have learned about drives, directories, and files in PowerShell to other areas, including the registry or Microsoft Exchange.
Chapter 16. The Registry

You can navigate the Windows registry just as you would the file system because PowerShell treats the file system concept discussed in Chapter 15 as a prototype for all hierarchical information systems.
Chapter 17. Processes, Services, Event Logs

In your daily work as an administrator, you often have to deal with programs (processes), services, and innumerable entries in event logs so this is a good opportunity to put into practice the basic knowledge you gained from the first 12 chapters. The examples and topics covered in this chapter are meant to give you an idea of the full range of options.

In the course of your reading, you will no doubt rack your brains occasionally and find yourself flipping back pages to the introductory chapters. What's really astonishing are the many and diverse options you have in using the PowerShell pipeline (as discussed in Chapter 5) and associated formatting cmdlets to wring out every last bit of data from pipeline objects. What was just dry theory in Chapter 5 will now become very interesting in the following.
Chapter 18. WMI: Windows Management Instrumentation

It might have escaped your attention, but the Windows Management Instrumentation (WMI) service introduced with Windows 2000 has been part of every Windows version since then. The WMI service is important because it can retrieve information about nearly every aspect of your system and can even make some modifications. However, it would be beyond the scope of this book to go into WMI in greater depth because that alone could fill another volume. For this reason, we will focus on how the WMI service basically works and how PowerShell handles it.
Chapter 19. User Management

For many administrators, managing users is an important part of their work. PowerShell v1 does not contain any cmdlets to manage users. However, you can add them from third-party vendors. But if you do not want any dependencies on third-party tools and snap-ins, you will learn in this chapter how to use native .NET framework methods for user management.
Chapter 20. Your Own Cmdlets and Extensions

Since PowerShell is layered on the .NET framework, you already know from Chapter 6 how you can use .NET code in PowerShell to make up for missing functions. In this chapter, we'll take up this idea once again. You'll learn about the options PowerShell has for creating command extensions on the basis of the .NET framework. You should be able to even create your own cmdlets at the end of this chapter.

Master-PowerShell | With Dr. Tobias Weltner - PowerShell.com

MENSAJERIA WEB

2009-10-14T13:52:00.000-04:00

Todas tus cuentas en un solo cliente:

MOSS 2007 Script Collection

2009-10-13T12:49:00.001-04:00

I’ve been working with SharePoint and PowerShell for quite some time now and I would like to share a couple of Scripts that I use when scripting MOSS. Actually, it’s 44 Scripts, Loads of Coffee and alot of long nights so I hope you enjoy them. There are Links at the bottom of the Post where you can Download all the scripts, or you can Download all scripts from the link below.

moss-script-collection.zip

Down to business then. I’ll put up a scenario based on the Session that I used at the SharePoint UserGroup meeting in Stockholm Sweden, explaining all Steps and how to use the Scripts.

First I set up a Folder where I keep all my scripts, I use C:\Scripts. Then I add the folder to the Windows Path.


PS > $env:path = $env:path + ";c:\scripts"

Adding the Script folder to the Environment Path let’s Us Call the script simply by typing it’s name. so instead of typing:


PS > .\Get-SPSite.ps1 -url http://moss

We can Type:


PS > Get-SPSite -url http://moss

Note, Don’t forget to set the Execution-Policy, otherwise, the scripts won’t run. Read more about it here


PS > Set-ExecutionPolicy RemoteSigned

All Scripts include a help text that explains how to use the Script. To access the helptext simply type the Script Name followed by -help.


PS > Get-SPSite -help

Now We can start Scripting MOSS!

Loading SharePoint Assemblies

The first thing we have to do in order to Access the MOSS 2007 Assemblies is Loading them into PowerShell. Even though they Exist in our Windows Environment, PowerShell isn’t aware of them. By Loading them into our Global Assembly Cache, PowerShell can access and use the MOSS 2007 .NET Classes.


[void][System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint")

Get-SPSite.ps1

First, We’ll Check out the Site Collection. Here’s how we can add our Site Collection to a variable using the Get-SPSite.ps1 script.


PS > $SPSite = Get-SPSite -url http://moss

From the $SPSite object we can retrieve information about our Site Collection


PS > $SPSite | Select Url, Port, Owner | Format-List


Url   : http://moss
Port  : 80
Owner : POWERSHELL\administrator

We Can get usage Information:


PS > $SPSite.Usage


Storage           : 550113
Bandwidth         : 0
Visits            : 0
Hits              : 0
DiscussionStorage : 0


And even information from the WebApplication Pool



PS > $SPSite.WebApplication.ApplicationPool | Select DisplayName, Status | Format-List


DisplayName : SharePoint - 80
Status      : Online


Try Pipe:ing the $SPSite object to Get-Mameber and check out all Available methods and properties available.



PS > $SPSite | Get-Member



Get-SPWeb.ps1


The Get-SPWeb.ps1 Returns a Site instead of a Site Collection through the OpenWeb() method. Through it, we can modify the Title and description of a site, we can add Items, documents and lots more. 



PS > $OpenWeb = Get-SPWeb http://moss



Here's an example on how you can change the Title and Descrition of a Site.



PS > $OpenWeb = Get-SPWeb http://moss
PS > $OpenWeb.Title

Home

PS > $OpenWeb.Description

Home

PS > $OpenWeb.Title = "PowerShell Home"
PS > $OpenWeb.Description = "Demo From PowerShell.nu"
PS > $OpenWeb.Update()



Here's What happened to my MOSS RootWeb Site after running these simple commands.




Get-SPList.ps1


We've accessed The Site Collection and a MOSS Site, Let's look at how to access a List within a Site. We can do this through the Get-SPList.ps1 Scrtipt



PS > $SPList = Get-SPList -url http://moss -List Announcements



Now That we've got a variable holding our List, We can use it to Get or Set List Information and even Get or Set Items and Fields in the List.



PS > $SPList = Get-SPList -url http://moss -List Announcements
PS > $SPList.ItemCount

3

PS > $SPList.Items | ForEach { $_["Title"] }

Get Started with Windows SharePoint Services!
Announcement Added through PowerShell
Demo from PowerShell.nu


Get-SPField.ps1


A List Contains Field which tell us what kind of information we can add to our Items. When Accessing a Field you can use the Get-SPField.ps1 script.



PS > $Field = Get-SPField -url http://moss -List Announcements -Name Expires



The Field holds alot of information such as Type:



PS > $Field.Type

DateTime


You can even edit information in the Field. Here's an Example on How to Hide the Field in Edit Form. When a User Tries to Edit an item in the Announcements List, he won't see the Expires Field.



PS > $Field.ShowInEditForm = $False
PS > $Field.Update()



Get-SPView.ps1


A List Contains a Variaty of Views. Here's how you Access a List View in MOSS 2007 using the Get-SPView.ps1 Script.



PS > $View = Get-SPView -url http://moss -List "Shared Documents" -View "All Documents"



The View contains alot of Methods and Properties. Let's take a look at the Clone() Method.



PS > [void]$View.Clone("My Cloned View",100,$True,$False)



With this Simple Command, I've Created a new View Called "My Cloned View". It's basically a Copy of the "All Documents" View.


Get-SPItem.ps1


When Accessing Items within a List, you can use the Get-SPItem.ps1 Script. Storing the Item in a Variable Allows us to Get And Modify it's properties. The script includes an -All Switch that retrieves All Items in a List instead of just one item.



PS > $Item = Get-SPItem  -url http://moss -List Announcements -Item "Get Started with Windows SharePoint Services!"



Now That we have an Item stored in the $Item Variable, we can Modify it.



PS > $Item["Body"]

Microsoft Windows SharePoint Services helps you to be more eff
ective by connecting people, information, and documents. For information on getting started, see Help.



PS > $Item["Body"] = "New Text in Body"
PS > $Item.Update()



Another Nice Trick is Looping through all Items. First let's Store them in a variable:



PS > $AllItems = Get-SPItem -url http://moss -List Announcements -All


Now Let's Set the Body on All Announcements in the Announcements List.



PS > $AllItems | ForEach { $_["Body"] = "New Text"; $_.Update() }



Add-SPAnnouncement.ps1


Next, let's add an Announcement to our RootWeb Site. Using the Add-SPAnnouncement.ps1 sript, we can add through a One-Liner in PowerShell.



PS > Add-SPAnnouncement -url http://moss -List "Announcements" -Title "Demo from PowerShell.nu" -Body "PowerShell
is Cool!" -Expires (Get-Date).AddHours(1)





Let's say that you have multiple sites in your Site Collection and you want to add an Announcement on each site. This can be solved with a Simple ForEach:



PS > $Sites = "http://moss/HR","http:moss/IT","http://moss/Production","http://moss/Sales"
PS > $Sites | ForEach {
>> Add-SPAnnouncement -url $_ -List "Announcements" -Title "Demo från PowerShell.nu" -Body "

is Coolt!" -Expires (Get-Date).AddHours(1)



This Code adds an announcement on each site in the $Sites Array.


Add-SPCalendar.ps1


The Add-SPCalendar.ps1 script adds new Calendar Entries to a MOSS Calendar List.



PS > Add-SPCalendar -url http://moss -List "Calendar" -Title "SharePoint - PowerShell Demo" -Location "Stockholm" -Description "PowerShell Demo" -StartTime (Get-Date) -EndTime (Get-Date).AddHours(4)



The -StartTime and -EndTime Parameters accept an [DateTime] object, which means that we can use the Get-date CmdLet to Add Dates.




Add-SPLink.ps1


Here's a Script that adds Links to a MOSS Links List. It sets the Link, the Description of the Link and the Notes Field.



PS > Add-SPLink -url http://moss -List "Links" -Link "http://www.powershell.nu" -Description "PowerShell.nu - Blog" -Notes "PowerShell Blog"



Here's what our Newly created Link Item looks like:




Set-SPImageWebPart.ps1


On a Default installed MOSS, The Root Web uses the "Team Site" Template, which has an Image WebPart on the Right Displaying a SharePoint Services Image. Let' go ahead and change the image using the Set-SPImageWebPart.ps1 Script.



PS > Set-SPImageWebPart -url http://moss -WebPart "Site Image" -Image "C:\Demo\Files\PowerShell.jpg"



As you can see in the Image below, Our RootWeb Team Site looks a little PowerShelled.




Set-SPTheme.ps1

Now that we've customized our Site with a New "Site Image", let's go ahead and change the Theme. We'll use the Set-SPTheme.ps1 script to achieve this.



PS > Set-SPTheme -Url http://moss -Theme obsidian



And with a simple One-Liner, we've changed the Theme on our Site. Doing without the script takes about two lines of code, but i Added the script since I think it's pretty cool.




Upload-SPDocument.ps1


This Script lets you Upload Documents to a Document Library in MOSS. Here's how it Works:



PS > Upload-SPDocument -url http://moss -Folder "Shared Documents" -Document "C:\Documents\Excel SpreadSheet.xlsx"



If we look in our "Shared Documents" List, We can see that the Document is uploaded there now.




But What it we want to Upload one hundred documents ? Well, since we are using PowerShell, we can do it with a One-Liner.



PS > gci C:\Documents | ForEach { Upload-SPDocument -url http://moss -Folder "Shared Documents" -Document $_.FullName }



This really shows the Power of Microsoft PowerShell


Add-SPFolder.ps1


Now That we've Uploaded a couple of Files, Let's Add a New Folder to our "Shared Documents". We can do this by using the Add-SPFolder.ps1 script.



PS > Add-SPFolder -Url http://moss -List "Shared Documents" -Name "New Folder"



If we want to Upload Documents Directly to our Folder we can use the Upload-SPDocument.ps1 Script again, we just point it to our New Folder.



PS > Upload-SPDocument -url http://moss -Folder "Shared Documents/New Folder" -Document "C:\Documents\Excel SpreadSheet.xlsx"



Add-SPTextField.ps1


Let's add a couple of Fields to our "Shared Documents" List. First, we'll add a Document Owner Field. In this example we'll use a simple Text field, but you could obviously use a User field instead. We'll get back to the User field a little later in this post.



PS > Add-SPTextField -url http://moss -List "Shared Documents" -Name "Document Owner" -Description "Document Owner"



This Adds a TextField to our List named "Document Owner", if you want the field to Require information, simply add -Required to the command above.




Add-SPChoiceField.ps1


Next, We'll add a Choice Field to our "Shared Document". This can be done by using the Add-SPChoiceField.ps1 Script. Again, if you want the Field to Require information, just add -Required to the command.



PS > Add-SPChoiceField -url http://moss -List "Shared Documents" -Name "Document Type" -Description "Type of Document" -Choices $("Excel","Word","PowerPoint")



Note the -Choices Paramteter. It takes an Array of arguments and Sets each argument as a Choice in the Field. Typing $("Argument1","Argument2") is a quick way to create an array and passing it as an argument to the script.




Add-SPFieldToView.ps1


Now that we have two new Fields in our "Shared Documents", let's add them to the "All Documents" View by using the Add-SPFieldToView.ps1 Script.



PS > Add-SPFieldToView -url http://moss -List "Shared Documents" -Field "Document Owner" -View "All Documents"
PS > Add-SPFieldToView -url http://moss -List "Shared Documents" -Field "Document Type" -View "All Documents"



If we check out our "Shared Documents" list now, we can see that the Fields are Added to the "All Documents" View. You can, of course, use this on any type of List in MOSS 2007.




Set-SPItem.ps1


Here's a Really Useful script when working with Items. The Set-SPItem.ps1 Script can either Create a New Item or Modify an existing Item. At first, Let's take a look on how to Modify existing Items. By Default, the -field param is set to Title, but by changing it to Name, the script will check for a match in the Name Field and if it finds a match, it will update the Item, if it doesn't find a match it will create a New Item. Note that when Creating Items in a Document Library you have to use the Upload-SPDocument.ps1 script.


Note that the -Values takes a HashTable Array of Values to Set on the Item. Let's say a List has Two Fields. A Title field and a Description Field. If I want to Create a New Item Called "New Item" and with The Description "My New Item Description" I could Simply type:



PS > Set-SPItem -url http://moss -List "My List" -Name "New Item" -Values @{"Description" = "My New Item Description"}



If i Want to Edit the Item that i Created i Could reuse the Same Command, since it First looks for an Item Where the Title is Set to "New Item"


Let's say i Don't know the Title of the Item but i Do know It's Description. By using the -Field paramter i Could get the Correct Item and Modify it.



PS > Set-SPItem -url http://moss -List "My List" -Name "My New Item Description" -Field Description -Values @{"Title" = "New Title"; "Description" = "Changed Title and Changed Description of Item"}



Let's Take a Look at the Documents that we Added earlier. Here's an example on adding MetaData on Documents in a Document Library:


PS > Set-SPItem -url http://moss -List "Shared Documents" -Name "Excel SpreadSheet.xlsx" -Field "Name" -Values @{"Document Type" = "Excel"; "Document Owner" = "Niklas Goude"}
PS > Set-SPItem -url http://moss -List "Shared Documents" -Name "Word Document.docx" -Field "Name" -Values @{"Document Type" = "Word"; "Document Owner" = "Niklas Goude"}
PS > Set-SPItem -url http://moss -List "Shared Documents" -Name "PowerPoint Presentation.pptx" -Field "Name" -Values @{"Document Type" = "PowerPoint"; "Document Owner" = "Niklas Goude"}



With these Commands I added information in the "Document Type" Field and the "Document Owner" Field on my three Documents, as the image below show.




Let's Use this Script to Modify the Announcement That we Added Earlier. We'll Change the Body of the Announcement. 



PS > Set-SPItem -url http://moss -List Announcements -Name "Demo from PowerShell.nu" -Values @{"Body" = "Modified With Set-SPItem.ps1
"}



Here's what the Announcemet looks like now:




Add-SPList.ps1


Now Let's create our own Custom List. We'll use the Add-SPList.ps1 Script to do this. Specifying the Type to "Custom List" tells the script to create a "Custom List". You can, of course create any type of list available in MOSS through this script.



PS > Add-SPList -url http://moss -Name "My List" -Description "My Custom Demo List" -Type "Custom List"



This Creates the List, but it doesn't Add the List to the QuickLaunch Bar. Let's check out how to Add a List to the QuickLaunchBar.


Add-SPListToQuickLaunch.ps1


This Script adds lists to the Quicklaunch Bar in MOSS 2007. The Command below shows how you can use the script.



PS > Add-SPListToQuickLaunch -url http://moss -List "My List"



This command adds the List to the QuickLaunch Bar.




Set-SPQuickLaunchOrder.ps1


Let's Change the QuickLaunch Order. We'll use the Set-SPQuickLaunchOrder.ps1 Script that moves a List to the Top of the QuickLaunch.



PS > Set-SPQuickLaunchOrder -url http://moss -List "My List"



If we look at our site now, We can see that our QuickLaunch Order has been Changed. The "My List" List is now on top.




Now That we have a Custom List, Let's Add a couple of different Fields, We'll also add them to the "All Items" View with the Add-SPFieldToView.ps1 script.


Add-SPCurrencyField.ps1


You can Add a Currency Field by using the Add-SPCurrencyField.ps1 Script.



PS > Add-SPCurrencyField -url http://moss -List "My List" -Name Cash -Description "How much Money do you have?"
PS > Add-SPFieldToView -url http://moss -List "My List" -Field Cash -View "All Items"



Add-SPDateTimeField.ps1


Here's how we can add a DateTime Field to a List using the Add-SPDateTimeField.ps1 Script.



PS > Add-SPDateTimeField -url http://moss -List "My List" -Name "Birthday" -Description "When is Your Birthday?"
PS > Add-SPFieldToView -url http://moss -List "My List" -Field Birthday -View "All Items"



Add-SPNoteField.ps1


The Note Field Accepts Text on Multiple Rows. Here we add a Note Field using the Add-SPNoteField.ps1 Script.



PS > Add-SPNoteField -url http://moss -List "My List" -Name Description -Description "About Me.."
PS > Add-SPFieldToView -url http://moss -List "My List" -Field Description -View "All Items"



Add-SPNumberField.ps1


We can also Add Numeric Fields to MOSS. This example shows how  to do that using the Add-SPNumberField.ps1 Script.



PS > Add-SPNumberField -url http://moss -List "My List" -Name Age -Description "How Old Are You?"
PS > Add-SPFieldToView -url http://moss -List "My List" -Field Age -View "All Items"



Add-SPYesNoField.ps1


With the Add-SPYesNoField.ps1 script, We can add a Yes/No Checkbox Field to our List.



PS > Add-SPYesNoField -url http://moss -List "My List" -Name "Windows 7" -Description "Do You Have Windows 7 Installed?"
PS > Add-SPFieldToView -url http://moss -List "My List" -Field "Windows 7" -View "All Items"



Add-SPUserField.ps1


Adding User Fields that point to a Active-Directory User, Can be Added through the Add-SPUserField.ps1 Script.



PS > Add-SPUserField -url http://moss -List "My List" -Name User -Description "User"
PS > Add-SPFieldToView -url http://moss -List "My List" -Field User -View "All Items"



Add-SPMultipleUserField.ps1


A User Field can Allow Multiple Selections. Here's how to add a multiple User Field using the Add-SPMultipleUserField.ps1 script.



PS > Add-SPMultipleUserField -url http://moss -List "My List" -Name "Multiple Users" -Description "Multiple Users"
PS > Add-SPFieldToView -url http://moss -List "My List" -Field "Multiple Users" -View "All Items"



Add-SPMultiChoiceField.ps1


Choice Fields can also accept Multiple Choices. Here's an example on how to add a Multiple Choice Field using the Add-SPMultiChoiceField.ps1 Script.



PS > Add-SPMultiChoiceField -url http://moss -List "My List" -Name "Favorite Music" -Description "Favorite Music" -Choices $("Country","Metal","Rock","Soul","Jazz")
PS > Add-SPFieldToView -url http://moss -List "My List" -Field "Favorite Music" -View "All Items"



Add-SPLookupField.ps1

The Lookup Field Points to an Item in another List. In this Example we'll Point it to the "Tasks" List.



PS > Add-SPLookupField -url http://moss -List "My List" -Name "My Tasks" -Description "My Tasks" -LookupList Tasks
PS > Add-SPFieldToView -url http://moss -List "My List" -Field "My Tasks" -View "All Items"



Add-SPMultiLookupField.ps1


LookupFields Can also have multiple Values. We can add a Multiple LookupList through the Add-SPMultiLookupField.ps1 Script. Again, We'll Use the Tasks List as Lookup.



PS > Add-SPMultiLookupField -url http://moss -List "My List" -Name "Multiple Tasks" -Description "Multiple Tasks" -LookupList Tasks
PS > Add-SPFieldToView -url http://moss -List "My List" -Field "Multiple Tasks" -View "All Items"



Add-SPURLField.ps1


Finally, Let's Add an URL Field to our "Custom List".



PS > Add-SPURLField -url http://moss -List "My List" -Name HomePage -Description "HomePage"
PS > Add-SPFieldToView -url http://moss -List "My List" -Field HomePage -View "All Items"



Now, Let's see what our List Looks like.




Let's Add Two Task Items and then create a New Item in our "Custom List" using the Set-SPItem.ps1 Script.



PS > Set-SPItem -url http://moss -List Tasks -Name "My First Task" -Values @{"Priority" = "(3) Low"; "Status" = "In Progress"; "% Complete" = "0.4"; "Assigned To" = "powershell\Administrator"; "Description" = "My First Task"; "Start Date" = "09/07/09"; "Due Date" = "09/08/09"}
PS > Set-SPItem -url http://moss -List Tasks -Name "My Second Task" -Values @{"Priority" = "(1) High"; "Status" = "Not Started"; "% Complete" = "0"; "Assigned To" = "powershell\Administrator"; "Description" = "My Second Task"; "Start Date" = "09/07/09"; "Due Date" = "09/08/09"}



Here's our New Tasks up and running.




Now Let's Add a New Item in our "Custom List". Note that Fields that Allow multiple Values are divided by a ; in the command below. For Instance, if I want to two values to a multiple Choice Field I would have to Type: @{"MultiChoiceField" = "Value1; Value2; Value3"}.


PS > Set-SPItem -url http://moss -List "My List" -Name "My First Item" -Values @{"Cash" = "10"; "Birthday" = "05/05/1982"; "Description" = "My First Entry"; "Age" = "27"; "Windows 7" = "Yes"; "User" = "powershell\administrator"; "Multiple Users" = "powershell\administrator; powershell\nigo"; "Favorite Music" = "Metal; Country"; "My Tasks" = "My First Task"; "Multiple Tasks" = "My First Task; My Second Task"; "HomePage" = "http://www.powershell.nu; My Blog" }



And Here's what our Item Looks like in MOSS 2007.




Set-SPView.ps1

Let's Modify the Apperance of the "All Tasks" View in the Tasks List so that it Groups By Status. When Modifying appearance of a View, We change the View Query. This can be Done by using the Set-SPView.ps1 Script.



PS > Set-SPView -url http://moss -List Tasks -View "All Tasks" -Query ''



Here's what our Tasks Look like now.




Remember the "Shared Documents that We Added Fields to earlier ? Let's Group the "All Documents" View by one of our New Fields. Note that the Name="Document_x0020_Type" in the Query. It's because the Field has Spaces in its Name.



PS > Set-SPView -url http://moss -List "Shared Documents" -View "All Documents" -Query ''



And now our Documents are Grouped by "Document Type".




Add-SPSpite.ps1


With the Add-SPSite.ps1 Script, we can add New Sites to our Site Collection. There are a Couple of Different Templates that we can use. To get a list of all templates available, SImply type the following commands.



PS > $OpenWeb = Get-SPWeb http://moss
PS > $OpenWeb.GetAvailableWebTemplates(1033) | Select Name



Let's Create a New Site For our IT Department.



PS > Add-SPSite -url http://moss -weburl "IT" -Title "Information Technology" -Description "IT Department" -Template "STS#1"



Here's What the Site looks like now.




Since we used a STS#0 Template, the Site doesn't contain any Lists or information.


Add-SPGroup.ps1


If we want to Add a New Group to our Site Collection we can use the Add-SPGroup.ps1 Script. Here's an example on using the Script.



PS > Add-SPGroup -url http://moss -Group "New Group" -Role Read -Owner "powershell\administrator"



Now our "New Group" is Added to our Site with "Read" Permissions




Add-SPUser.ps1


With our New Group set up, we can go ahead and add users to it. To accomplish this, we can use the Add-SPUser.ps1 Script. Here's an example on adding a User to the "New Group".


PS > Add-SPUser -url http://moss -Group "New Group" -Domain "powershell.nu" -sAMAccountName "goude" -mail "niklas.goude@zipper.se" -FullName "Niklas Goude"



If we look in the Group now, our User will be added.




Add-SPSitePermission.ps1


Let's Give our Group Full Permissions on The IT Site that we created earlier.


PS > Add-SPSitePermission -url "http://moss/IT" -Group "New Group" -Permission "FullMask"



Now all users in the Group have Full Permissions on the "IT" Site. On the RootWeb, they still have Read Permissions.


Add-SPImageWebPart.ps1


Let's Add a New Image WebPart to the IT Site that we just created. Here's an example on how to do it using the Add-SPImageWebPart.ps1 Script.


PS > Add-SPImageWebPart -url http://moss/IT -Name "My Image" -Image "C:\Images\PowerShell.jpg" -ChromeType "None"



Now the Image WebPart is Added to the Site. There are a couple of parameters you can use with this script. simply type Add-SPImageWebPart -help to check out available parameters.



PS > Add-SPImageWebPart -help





Add-SPListViewWebPart.ps1


The Add-SPListViewWebPart.ps1 let's us Add list View WebParts to our Sites. The Script contains a couple of parameters that let's you choose Chrome Type, Zone and a couple of other things. Here's an example on Using the Script.


PS > Add-SPListViewWebPart -url http://moss -List "My List" -Name "Client Statistics" -ChromeType "None"



Here's our New List WebPart in Action!




Remove-SPField.ps1


If you want to Remove a Field From a List you can use the Remove-SPField.ps1 Script. Here's an example on how to use the Script.


PS > Remove-SPField -url http://moss -List "Shared Documents" -Field "Document Type"



Remove-SPItem.ps1


If you want to Remove a List Item you can use the Remove-SPItem.ps1 script. The -name parameter matches with the Title field by default. If you want to match the name with another field, simply use the -field parameter.


PS > Remove-SPItem -url http://moss -List Tasks -name "My First Task"
PS > Remove-SPItem -url http://moss -List Tasks -name "Not Started" -Field Status



Remove-SPList.ps1


If you want to Remove an entire List you can use the Remove-SPList.ps1 script,


PS > Remove-SPList -url http://moss -List Tasks



This Command Removed the Tasks List from the RootWeb Site.


Remove-SPSite.ps1


When Removing a Site from MOSS 2007 You can use the Remove-SPSite.ps1 script. This exmaple shows how to remove the IT Site that we created earlier.


PS > Remove-SPSite -url http://moss/IT



Export-SPSite.ps1


Let's take a Backup of our Site Collection. We can either do this through Central Administration, through an STSADM Command or by Using PowerShell. This Example shows how to use a PowerShell Script to take a Backup of a Site Collection.


PS > Export-SPSite -url http://moss -file Backup.bak -Location C:\Backup\



The Command Places a Backup file in C:\Backup\Backup.bak. to automate this you could set up a Scheduled Task that takes a backup at specified weekdays.


Import-SPSite.ps1


Now That we have a Backup, Let's restore our Site Collection from the Backup file. To achieve this, we can use the Import-SPSite.ps1 Script. Here's an example on how to use the script.


PS > Import-SPSite -url http://moss -file Backup.bak -Location C:\Backup\



Here's a List of All scripts from this Post. Enjoy!


Regards



Goude



Get-SPSite.ps1

Get-SPWeb.ps1

Get-SPList.ps1

Get-SPField.ps1

Get-SPView.ps1

Get-SPItem.ps1

Add-SPAnnouncement.ps1

Add-SPCalendar.ps1

Add-SPLink.ps1

Set-SPImageWebPart.ps1

Set-SPTheme.ps1

Upload-SPDocument.ps1

Add-SPFolder.ps1

Add-SPTextField.ps1

Add-SPChoiceField.ps1

Add-SPFieldToView.ps1

Set-SPItem.ps1

Add-SPList.ps1

Add-SPListToQuickLaunch.ps1

Set-SPQuickLaunchOrder.ps1

Add-SPCurrencyField.ps1

Add-SPDateTimeField.ps1

Add-SPNoteField.ps1

Add-SPNumberField.ps1

Add-SPYesNoField.ps1

Add-SPUserField.ps1

Add-SPMultipleUserField.ps1

Add-SPMultiChoiceField.ps1

Add-SPLookupField.ps1

Add-SPMultiLookupField.ps1

Add-SPURLField.ps1

Set-SPView.ps1

Add-SPSpite.ps1

Add-SPGroup.ps1

Add-SPUser.ps1

Add-SPSitePermission.ps1

Add-SPImageWebPart.ps1

Add-SPListViewWebPart.ps1

Remove-SPField.ps1

Remove-SPItem.ps1

Remove-SPList.ps1

Remove-SPSite.ps1

Export-SPSite.ps1

Import-SPSite.ps1

Preparing PowerShell for SharePoint and MOSS 2007

2009-10-13T12:45:00.000-04:00

Microsoft PowerShell allows you to write scripts that can use .NET classes, objects, properties and methods. It therefore provides an ideal way of creating script files by calling into the SharePoint and MOSS object model.

First, download Microsoft PowerShell from here and install. PowerShell can then be lanched from the “Start” menu.

The PowerShell execution policy determines if script files can be run – by default they are prohibited for security reasons. Enter the following command to find out about execution policy and signing script files:

get-help about_signing

You can either elect to only run signed scripts (in which case scripts must be signed with a certificate), or to run unsigned scripts from the local file system or to run any unsigned script. For most users, allowing unsigned scripts to run from the local file system is acceptable, so to allow this enter the following commands to set and then retrieve the execution policy (you need to be logged on as administrator):

set-executionpolicy RemoteSigned
get-executionpolicy

Before programming against the SharePoint and/or MOSS 2007 object model the appropriate assemblies must be loaded. The following commands do this:

[System.Reflection.Assembly]::Load(”Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c”)
[System.Reflection.Assembly]::Load(”Microsoft.SharePoint.Portal, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c”)

You can place these commands the file called Microsoft.PowerShell_profile.ps1 in a folder called My Documents\WindowsPowerShell to run commands automatically when you run PowerShell (the folder and the file may not exist and may need to be created).

You can now test calling into the SharePoint object model. The following command gets a reference to a site collection at the given URL:

$spsite=[Microsoft.SharePoint.SPSite](”http://localhost/sites/intranet“)

You can review all the property values for the SPSite object by typing the name of the object variable:

$spsite

You can find an example of creating a script file for chaning a site’s regional settings here.

SharePoint PowerShell for Beginners - continued

2009-10-13T08:25:00.001-04:00

In my first post on PowerShell for SharePoint developers I described how you could use the SPSite and SPWeb object to get information on its object model. In this post I will explain a few methods and properties of SPList.

Perhaps some of you know the featue I wrote last summer to view all properties of a SharePoint list. One of the things that you could inspect with this feature is the fields that are defined on the list. It shows you its name, internal name, id and data type. For more information see my post on the List Properties feature.

Today I will show you how to get this information by using PowerShell.

To get to the list you want to investigate, you need to perform some preliminary tasks:

Load the SharePoint assembly:

[System.Reflection.Assembly]::LoadWithPartialName(”Microsoft.SharePoint”)

Open the SharePoint web:

$siteUrl = "your sharepoint site url"
$webName = "your webname"
$spSite = new-object Microsoft.SharePoint.SPSite($siteurl)
$spWeb = $spSite.OpenWeb($webName)

Instantiate the SharePoint list:

$listName = "your listname"

$spList = $spWeb.Lists[$listName]

The fields of a list are defined in its Fields collection property. You could execute the following but it will return you a long list of all fields with all of its properties.

$spList.Fields

View column properties of a SharePoint list

So if your interested in only a few properties you could first inspect the metadata of the field object. A field is of type SPField. As we are not able to create a new object of type SPField from a default constructor, we will get an instance of the first field of the list. To view the different properties defined on SPField, execute the following statement:

$spList.Fields[0] | gm -membertype property

Following screenshot shows you the result.

So, if you want to view a few properties like display name, internal name, id and data type of all fields on a list, use the following syntax:

$spList.Fields | ft Title, InteralName, Id, TypeAsString

This returns you the requested data in table format. If not all information like f.e. the Id is completely visible, you could customize the columns of the table or use the fl formatter, which stands for format-list.

Add a column to a SharePoint list

The second task is to add a column to a SharePoint list. We will create a field with name "Extra column" and of type string. First of all, you need to know which method you need to execute on the list object and what are the arguments you need to specify.

Execute $spList.Fields.Add to get an overview of the different overloads of the Add mehtod:

As you can see, there are 2 overloads to add a new item to a SharePoint list. The overload we are going to use is the one that needs a column name, a field type and the required boolean. Execute the following:

$spList.Fields.Add("Extra column", "Microsoft.SharePoint.SPFieldType.Text", 0)

This returns you the following error:

As you can see in the error message returned by PowerShell, we didn't specify a correct value for the field type. If you tak a good look at the error message you will notice that PowerShell returns all possible values for that argument in the error message!

Specify boolean values as 0 and 1. If you pass the string "false", it is accepted as "different from false" and your field will be added as a required field.

Following statement will add the column to the list:

$spList.Fields.Add("Extra column", "Text", 0)

In addition, PowerShell returns you the internal name of the column you just added, i.e. Extra_x0020_column

Return to Internet Explorer and browse to the Settings Page of your list. You will see that the column is added to the list:

You can add it to the default view as you want.

In a next post I will explain how you can write a function that adds a column to a SharePoint list. You will be able to use this function for adding columns to each different type of list.

Posted at 6:39 by Karine Bosch

2009-10-13T08:20:00.002-04:00

SharePoint PowerShell for Beginners

This is a first post of a series on how you can use PowerShell on the SharePoint object model and its web services. This post will give you an introduction on how to work with the SPSite and SPWeb objects.

Open a PowerShell command prompt. As we are going to explore the SharePoint object model, you need to have PowerShell installed on a machine where you installed SharePoint.

The first step is to load the SharePoint assembly:

[System.Reflection.Assembly]::LoadWithPartialName(”Microsoft.SharePoint”)

Instantiate an SPSite object:

$siteurl = "http://boske.litwareinc.com"

$mysite=new-object Microsoft.SharePoint.SPSite($siteurl)

Now you have a variable mysite, which contains an instance of type SPSite:

You can explore the content of the mysite variable by executing following command:

$mysite

Or to have the information listed per page:

$mysite | more

To list all the members of the site object:

$mysite | get-member | more

or the shorter notation:

$mysite | gm | more

You can also list only the properties of the site object:

$mysite | gm -membertype property | more

To view the content of a property of the site object:

$mysite.AllWebs

But this shows the whole content of all webs in the site collection. If you want to see only a few properties of each web, you could execute the following:

$mysite.AllWebs | format-table Url, ID, Name, AllUsers

or the shorter version

$mysite.AllWebs | ft Url, ID, Name, AllUsers

To get the webs ordered by the last time that the contents have been changed:

$mysite.AllWebs | sort LastItemModifiedDate | ft Url, ID, Name, LastItemModifiedDate

To loop through all webs of the site object and show the web Url and the Title of each list:

$mysite.AllWebs | foreach { $_.Lists | ft $_.Url, Title}

You should see something similar like this:

You can also execute a methods of objects. Just for fun, I will show you how to execute a CAML query:

$mytestweb = $mysite.OpenWeb("testsite")

$listguid = new-object System.Guid("f0715075-5159-43d7-99b7-3897824fbbff")

$productlist = $mytestweb.Lists[$listguid]

$query = new-object Microsoft.SharePoint.SPQuery();

$query.Query = "Mountain"

$productlist.GetItems($query) | ft Name

You can also view all static members of the SPSite class:

[Microsoft.SharePoint.SPSite] | get-member -static

If you want to execute a static member:

[Microsoft.SharePoint.SPSite]::MaxWebNameLength

I hope you liked the introduction on how to use PowerShell in combination with the SharePoint object model.

PowerShell & SharePoint I

2009-10-12T17:00:00.001-04:00

Recientemente he leído varios artículos acerca del potencial de la PowerShell en combinación con SharePoint y como en alguna ocasión he usado PowerShell, he empezado a investigar un poco acerca de su utilidad en entornos SharePoint.

Espero que este sea el primero de una serie de post dedicados a las posibilidades que ofrece PowerShell en combinación con MOSS.

Para los que no estén familiarizados con que es PowerShell, se podría resumir como un entorno de línea de comandos, con un lenguaje propio de script que permite implementar comandos (cmdlets) y en el que también permite cargar ensamblados .NET.

Una vez tenemos PowerShell instalado, lo ejecutamos, y se presenta una especie de MS-DOS .

1. Cargar la dll de Sharepoint

{System.Reflection.Assembly}::LoadWithPartialName(“Microsoft.Sharepoint”)

2. Obtener un sitio de SharePoint

$siteurl = “http://localhost”

$site = new-object Microsoft.Sharepoint.SPSite($siteurl)

Se puede acceder al contenido de la variable sitio simplemente ejecutando el siguiente comando:

$site

Para obtener todos los miembros de sitio:

$site | get-member

Y podemos mostrar los subsitios de nuestra web en formato de tabla mostrando distintas propiedades:

$site.AllWebs | format-table Url, ID, Name, AllUsers

3. Obtener una lista de un sitio

Primero obtenemos el sitio donde se encuentra la lista y accedemos al objeto SPWeb

$siteUrl = “http://localhost:91”

$spSite = new-object Microsoft.Sharepoint.SPSite

$spWeb = $spSite.OpenWeb()

A partir del objeto SPWeb accedemos a la lista:

$listName =”lista1”

$spList = $spWeb.Lists[$listName]

4. Agregar una columna a una lista

A la lista que anteriormente habíamos obtenido en PowerShell, vamos a añadirle una nueva columna desde PowerShell:

Mediante el comando

$spList.Fields.Add

Accedemos a los posibles valores del método para añadir nuevos campos:

Y con este comando creamos una nueva columna:

$spList.Fields.Add(“Nueva Columna”, “Text”,0)

PowerShell y SharePoint – 2

2009-10-12T16:45:00.004-04:00

Para utilizar a PowerShell en SharePoint, primero es necesario crear una conexión con el ensamblado de SharePoint. Abra la interface de PowerShell y ejecute el siguiente comando:

[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint")

PowerShell devuelve la configuración del ensamblado.

Después de tener el ensamblado instanciado, los comandos normales de SharePoint se pueden utilizar para crear objetos, por ejemplo, para crear un objeto del tipo SPSite use el comando:

$mySite = new-object Microsoft.SharePoint.SPSite("http://NombreServidor")

Y para ver todas las propiedades del objeto, escriba el nombre del objeto (“$mySite”) y Enter:

De forma similar se puede crear un objeto del tipo SPWeb:

$myWeb = $mySite.OpenWeb()

Y ver todas sus propiedades y objetos usando el comando “$myWeb”.

Cuando un objeto o colección de objetos es muy extensa, el resultado se puede redirigir a otro tipo de salida diferente a la pantalla. Por ejemplo, para crear un archivo con todas las configuraciones de todas las Listas en el sitio de nivel superior, use un comando del tipo:

$myWeb.Lists > c:\gavd.txt

O para filtrar el resultado para mostrar solo algunas propiedades, utilice un filtro del tipo:

$myWeb.Lists | ft ID, Title

PowerShell y SharePoint - 1

2009-10-12T16:42:00.001-04:00

PowerShell es un nuevo programa de línea de comandos diseñado para la administración, automatización y manejo programático del sistema Windows y todos los productos de Microsoft. Basado en el framework .NET, permite que los profesionales de TI y los programadores controlen y automaticen la administración de Windows y todas sus aplicaciones.

PowerShell se puede descargar en español desde el sitio de Microsoft http://www.microsoft.com/downloads/details.aspx?displaylang=es&FamilyID=c6ef4735-c7de-46a2-997a-ea58fdfcba63. En Windows Server 2008 está instalado por defecto.

La herramienta se puede utilizar en principio como reemplazo del Símbolo del sistema tradicional, pero permite realizar mucho más que el. PowerShell presenta el concepto de "cmdlet", que consiste en una sencilla herramienta de línea de comandos integrada en el Shell que permite realizar una función específica. Los cmdlets se pueden utilizar por separado o ser combinados para realizar tareas complejas. La instalación por defecto de PowerShell ofrece más de cien cmdlets para realizar tareas básicas, pero el usuario puede crear sus propios cmdlets y distribuirlos a otros usuarios.

Cmdlets se pueden reconocer por el formato de sus nombre: un verbo y un nombre separados por un guion, por ejemplo Get-help, Start-Service. Los cmdlets "get" solo recuperan datos, los "set" crean o modifican datos, los "format" aplican formato a los datos y los cmdlets "out" dirigen la salida a un destino determinado. Para obtener ayuda, cada cmdlet contiene un archivo que se puede ver escribiendo "get-help [NombreCmdlet] -detailed".

Inicie PowerShell y escriba el nombre de un cmdlet, por ejemplo get-culture:

Note que con escribir las primeras letras del comando es suficiente: utilizando "Tab" se puede navegar a lo largo de todos los comandos que comienzan con esas letras.

El operador de canalización ("|") permite conectar un cmdlet con otro, por ejemplo: