SharePoint 2010 ...

Parar una granja SharePoint 2010 / How to stop a SharePoint´s farm

2011-09-07T20:09:00.000+02:00

Pues he aquí la questión.

A veces hay que parar la granja y no deseas reiniciarla, solo pararla, por ejemplo para hacer alguna modificación en el servidor SQL. El reinicio de granja ha de ser ordenado y lleva tiempo, en caso de tener muchos servidores, de modo que esta opción no es siempre la más deseada.

Después de investigar Microsoft nos facilita una pequeña guía, a la que le añado la funcionalidad de "inactividad/quiesce" que teníamos en SharePoint 2007, la cual no aparece en 2010 pero si que disponemos de ella vía línea de comando o PowerShell (de esto hablare otro día).

* Paso 1

Modo inactividad. Que significa el modo inactividad o quiesce? Según MS "Suspende provisionalmente la capacidad de la granja de servidores para aceptar nuevas sesiones que son esenciales para representar los formularios de InfoPath en un servidor"

En mi caso no dispongo de infopath, pero lo introduzco en el proceso de parada para asegurar que si algún día dispongo de dicho servicio estaré cubierta.

No se dispone de esta característica a través de la consola de administración, pero si podemos a través de línea de comando:

stsadm -o quiescefarm -maxduration minutos-de-inactivividad

Ejemplo: para 10 minutos seria “stsadm -o quiescefarm –maxduration 10”

Si se desea consultar el estado actual de inactividad: stsadm -o quiescefarmstatus

Lo que he descubierto es que no vale esperar a que los minutos que configuraste en maxduration se terminen, la granja permanecerá en modo inactivo hasta que ejecutes otro comando para activarla:

stsadm -o unquiescefarm

*Paso 2

Se deben parar los servicios listados abajo en aquellos servidores que alojen la Central de Administración:

•    SharePoint 2010 Administration
•    SharePoint 2010 Timer
•    SharePoint 2010 Tracing
•    SharePoint 2010 User Code Host
•    SharePoint 2010 VSS Writer
•    SharePoint Foundation Search V4
•    World Wide Web Publishing Service

Son todos servicios a parar desde services.msc, desde la propia consola de Windows. Algunos no estarán en uso, pero los que si lo están hay que pararlos.

* Paso 3. Parada del IIS en los servidores que alojen la Central de Adminstración : iisreset /stop

Para el arranque de la granja utilizamos el orden inverso:

Paso 3 > Arranque del IIS (iisreset /start)

Paso 2 > Activar los servicios de Windows

Paso 1 > Activar la granja (quiescefarm)

Para hacer esto mas fácil y ágil en granjas (si es un standalone es más rápido) he creado un sencillo script en .bat que Para la granja contemplando los pasos anteriores.

> Documentación técnica/Links:

http://technet.microsoft.com/en-us/library/cc512723.aspx#Stop

http://technet.microsoft.com/es-es/library/cc262797(office.12).aspx

SharePoint 2010 Installaction - Prerequisites software and downloads...

2011-04-30T16:13:00.000+02:00

Source Link: http://technet.microsoft.com/en-us/library/cc262485.aspx#section4

The preparation tool installs the following prerequisites:

• Web Server (IIS) role

• Application Server role

• Microsoft .NET Framework version 3.5 SP1

• SQL Server 2008 Express with SP1

• Microsoft Sync Framework Runtime v1.0 (x64)

• Microsoft Filter Pack 2.0

• Microsoft Chart Controls for the Microsoft .NET Framework 3.5

• Windows PowerShell 2.0

• SQL Server 2008 Native Client

• Microsoft SQL Server 2008 Analysis Services ADOMD.NET

• ADO.NET Data Services Update for .NET Framework 3.5 SP1

• A hotfix for the .NET Framework 3.5 SP1 that provides a method to support token authentication without transport security or message encryption in WCF.

http://go.microsoft.com/fwlink/?LinkId=136730

http://www.microsoft.com/downloads/details.aspx?FamilyID=c411b91e-4dab-4550-915c-e119204d0732&displaylang=en

• Windows Identity Foundation (WIF)

Clustering, command line

2009-11-18T21:23:00.003+01:00

Useful commands to check the health of the cluster:

cluster node
cluster resource
cluster group
cluster netint

Cluster, configuring the printer spool

2009-09-04T23:04:00.005+02:00

When you start to configure the printer spool in a cluster you might follow the Microsoft doc about it, it's easy to follow and you'll avoid failures in the future.

http://support.microsoft.com/kb/197046

Basically you will have to add the spooler as a group resource into de cluster, but not using the standard one called "Group resource" but creatinga a new one with another name.

The drivers must be installed in some places:
- In the cluster itself (the lcoation is the network resource og the resource group)
- In every node of the cluster: It means that you will install the printer drivers in as much as servers are part of the cluster

And take into account the LPT port, becasue is a local port.

Windows, command > Process

2009-09-04T22:52:00.007+02:00

Here some notes about the usefull command line.

If you have a process that is using a high amount ofthe resources, as CPU time or memory, some workaround is to find which files/drives is using. Once you'll have the PID (you can get it from task manager) just query it using Tlist:

Tlist PID

Ie> Tlist 1885

It will appear the path that started the process and some files associated.

For getting a list of the current process just run:

Tlist
Tasklist

Not rights to access through Terminal services?

2009-02-10T08:41:00.006+01:00

The error message below it´s quiet typical when you try to connect using Terminal services:

"To log on to this remote computer you must be granted the Allow log on throught Terminal Services right. By default the Remote Desktop Users group have this right"

Possible solution:

Open this policy and drill down under Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment.

Here look for policy called "Allow logon through Terminal Services". There should appear "Administrators" and "Remote desktop users" and we should be as part of, at least, one of these groups.

Please check aswell that you have enabled to allow the remotely connection :

My Computer select "Properties" and click on "Remote" Tab. Now you have to select "Allow users to connect remotely to this computer" .

sueño o realidad?

2009-02-09T19:06:00.002+01:00

Gracias Maitena!

Bloquear un sitio / Lock a Site collection

2009-02-09T18:50:00.006+01:00

Lock or not lock.. this is not the question !!

Si necesitas bloquear un sitio en sharepoint puedes utilizar la linea de comandos, rápida y efectiva, y además revisar que se hayan aplicado los cambios a traves de comando o por el interface.

Por que? Puedes bloquearlo para que sólo se disponga de acceso a lectura antes de realizar una copia de seguridad.

Esta opcion sólo sirve para bloquear una collection de sitios, no un subsitio.

-----------------------------

If you need to lock a site collection use the powerfull command-line, stsadm. Just be aware that it´s working for a whole site collection but not for a subsite.

Why? you´ll need this feature before backing up a site collection to avoid inconsistence.

Check the current status of the url:

stsadm -o- getsitelock -url http://portal.trainer.com

or open the url in a IE and check if the options in the right menu are available.

Lock:

stsadm -o setsitelock -url http://portal.trainer.com -lock readonly

Unlock:

stsadm -o setsitelock -url http://portal.trainer.com -lock none

More: http://technet.microsoft.com/en-us/library/cc262811.aspx

Moments

2009-02-09T18:27:00.004+01:00

Here my face when someone destroy my job, when I don´t get to resolve this tiny question that don´t let me to progress, here myselft just from time to time,why not?

From every experience you learn something, just Be positive! open your eyes!

Sharepoint–MOSS 2007 - How to move a site from one place to anoter

2009-02-06T19:13:00.004+01:00

Do you want to move your site under another site? Then follow these steps and enjoy!

Note:As usual follow up all the logical steps to protect your production environment.Be wise.

Method used: Import/export

Properties of import/export: GUIDs are not preserved (alerts, workflows, and some properties are lost with the stsadm import/export process ) but security user features are saved (not in backup)

Note that import/export does not include some site settings, such as Recycle Bin state and alerts.

Why import/export and not backup/restore? Because the second one only works from a root site, it´s not working for a site collection only.

Ie. We´re going to follow an example for understanding better the idea, prepared?

We want to move our site http://portal/sites1/Commercial under http://portal/sites12

Prerequisites

Assuming you have access to the server as an admin, use STSADM.EXE (strong & powerfull sharepoint command-line) to export and then import the site collection into the new location.

Check the amount of free space counting the sites:

C:\Program Files\Common Files\Microsoft Shared\Web Server tensions\12\BIN>stsadm.exe -o enumsites -url http://portal/site1

Procedure

- Create an empty web:

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN>stsadm -o createweb -url http://portal/sites12/Commercial

Operation completed successfully.

- Export our original site:

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN>stsadm -o export -url http://portal/sites01/Commecial -filename c:\exportsite1.cmp -includeusersecurity -versions 4 -quiet

Log file generated:

c:\exportsite1.cmp.export.log

Operation completed successfully.

Check the export´s log located in the same folder than the log and check the size. If there´s ony few kb instead og some Mb.. check the account your´re using to connect on the application server.

Log checked: 0 errors.

Explication of every flag:

–includeusersecurity : It ensures that the archived content or site will have the same permission requirements as the original.

-quiet: Recommended. Suppresses the output of export progress information to the display window. The final export status (“Operation completed successfully.”) will still be displayed.

-version 4: ensures that all content regardless of version will be included in the archive.

-Import the original site to the new location:

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN>stsadm -o import -url http://portal/sites12/Commercial -filename c:\exportsite1.cmp -includeusersecurity -quiet

Log file generated:

c:\exportsite1.cmp.import.log

Operation completed successfully.

Ending

The last step would be to delete the originl site after checking that the new emplace works properly.To avoid any mistake I would keep the old site collection locked (only read access) for some time and after I would delete it. It´s only a recommendation.

Possible issues:

Has been imported only the structure and the lists and document library are missing?? Please check the account you used to connect on the WSS server

Who could be there ...

2007-09-30T00:38:00.002+02:00

Have a nice day

2007-09-30T00:26:00.005+02:00

Because the past was yesterday, the future is tomorrow and the present is a gift ;-)

Sencillamente una ventana desde la que mirar cosas. Bienvenid@.