Clustering, command line

Useful commands to check the health of the cluster:

cluster node
cluster resource
cluster group
cluster netint

Cluster, configuring the printer spool

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

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?

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" .

Bloquear un sitio / Lock a Site collection

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

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

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