arp -a


You will see a list similar to this:

Interface: 192.168.1.141 --- 0xb
Internet Address Physical Address Type
192.168.1.1 00-40-4c-15-ca-b1 dynamic
192.168.1.6 00-10-ae-1d-e6-2b dynamic
192.168.1.15 00-34-2a-d2-90-e9 dynamic
192.168.1.50 00-23-29-d6-cb-11 dynamic
...


Using this command you can check if SSL v2 is enabled:

openssl s_client -connect www.example.org:443 -ssl2


If SSL v2 is disabled you should get a response like this (this is the response you want to get because SSL v2 should be disabled):

CONNECTED(00000003)
write:errno=104


or

CONNECTED(00000003)
11132:error:1407F0E5:SSL routines:SSL2_WRITE:ssl handshake failure:s2_pkt.c:428:


However, if SSL v2 is enabled the response will be a lot longer and include something like this:

...
Ciphers common between both SSL endpoints:
RC4-MD5 EXP-RC4-MD5 RC2-CBC-MD5
EXP-RC2-CBC-MD5 DES-CBC-MD5 DES-CBC3-MD5
---
SSL handshake has read 1370 bytes and written 364 bytes
---
New, SSLv2, Cipher is DES-CBC3-MD5
Server public key is 2048 bit
...


Here are instructions on how to disable SSL v2 on Windows 2008 servers:
How to disable SSL v2 / enable SSL v3 on Windows 2008

This is what needs to be done to disable SSL v2:

1. Start - Run
2. Type "regedit" and click OK
3. Locate the following key: HKey_Local_Machine\System\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0
4. Right click the "SSL 2.0" key and select Edit > Add key
5. Type "Server" and click Enter
6. Right click Server and select New > Add DWORD (32 bit) value
7. Type "Enabled" as the name and make sure the value is "0"
8. Restart the server

php_value {name} {value}


Here's how to change the memory limit:

php_value memory_limit 256M


Everything will be migrated, including application pools, virtual directories, SSL certficiates etc.

1. Download and install Web Deployment Tool on both source and destination servers: http://www.iis.net/download/webdeploy

2. Backup the IIS configuration on the destination server

cmd
cd C:\Program Files\IIS\Microsoft Web Deploy V2
%windir%\system32\inetsrv\appcmd add backup “PreWebDeploy”


3. Export the configuration from the source server to a zip package

cmd
cd C:\Program Files\IIS\Microsoft Web Deploy V2
msdeploy -verb:sync -source:metakey=lm/w3svc -disableLink:contentExtension -dest:package=C:\Temp\Sites.zip,encryptPassword=P4ssword > C:\Temp\WebDeploySource.log


You can choose any password in the "encryptPassword" variable. Using the "-disableLink:contentExtension" will only move configuration and when you have a lot of data it's probably the way to go.

4. Simulate import on the destination server (optional)

You can use msdeploy to see what would happen if you imported the package from the source server. No changes will be made to the IIS configuration and you can see what would happen in the log file

cmd
cd C:\Program Files\IIS\Microsoft Web Deploy V2
msdeploy -verb:sync -source:package=c:\Temp\Sites.zip,encryptPassword=P4ssword -disableLink:contentExtension -dest:metakey=lm/w3svc -whatif > C:\temp\WebDeployWhatIf.log


5. Import sites to the destination server

cmd
cd C:\Program Files\IIS\Microsoft Web Deploy V2
msdeploy -verb:sync -source:package=c:\Temp\Sites.zip,encryptPassword=P4ssword -disableLink:contentExtension -dest:metakey=lm/w3svc > C:\temp\WebDeployDestination.log


We need to drop all contraints, create a temporary table with the new structure, copy all data to the temporary table, drop the old table and rename the temporary table.

Below is a script that adds the column newcolumn between place and name in a table named mytable.

ALTER TABLE [mytable] DROP CONSTRAINT [PK_mytable]
ALTER TABLE [mytable] DROP CONSTRAINT [DF_mytable_place]
ALTER TABLE [mytable] DROP CONSTRAINT [DF_mytable_name]
 
CREATE TABLE tmp_mytable (
[item_id] [int] IDENTITY(1,1) NOT NULL,
[place] [int] NOT NULL,
[newcolumn] [nvarchar](255) NOT NULL,
[name] [nvarchar](255) NOT NULL,
CONSTRAINT [PK_mytable] PRIMARY KEY CLUSTERED
(
[item_id] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY]
 
ALTER TABLE [tmp_mytable] ADD CONSTRAINT [DF_mytable_place] DEFAULT ((1)) FOR [place]
ALTER TABLE [tmp_mytable] ADD CONSTRAINT [DF_mytable_name] DEFAULT ('') FOR [name]
ALTER TABLE [tmp_mytable] ADD CONSTRAINT [DF_mytable_newcolumn] DEFAULT ('newvalue') FOR [newcolumn]
 
SET IDENTITY_INSERT dbo.tmp_mytable ON
IF EXISTS(SELECT * FROM [mytable])
EXEC('INSERT INTO [tmp_mytable] (item_id, place, name)
SELECT item_id, place, name FROM [mytable] WITH (HOLDLOCK TABLOCKX)')
SET IDENTITY_INSERT dbo.tmp_mytable OFF
 
DROP TABLE mytable;
EXECUTE sp_rename N'tmp_mytable', N'mytable', 'OBJECT';


If you don't care about the placement you can add a column to the end of the table using this command:

ALTER TABLE mytable ADD newcolumn [nvarchar](255) NOT NULL CONSTRAINT DF_mytable_newcolumn DEFAULT 'newvalue'


After searching for solutions I found that the easiest way would be to export pst file from Outlook including all data from the old server and import it to the new. Exporting the pst using exmerge would also work out but for some reason it's not working on the old Windows 2003 server. Most users suggest using the Import-Mailbox cmdlet but it's not available in Exchange Server 2010. This is the error message I got:

[PS] C:\Windows\system32>Import-Mailbox -Identity username -FilePath \\server\share\file.pst
The term 'Import-Mailbox' is not recognized as the name of a cmdlet, function, script file, or operable program. Check
the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:15
+ Import-Mailbox <<<< -Identity username
+ CategoryInfo : ObjectNotFound: (Import-Mailbox:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException


Looks like Import-Mailbox has been replaced with a new command: New-MailboxImportRequest.

This is how I managed to import the ost using Exchange Management Shell:

New-MailboxImportRequest -Mailbox username -FilePath \\server\share\file.pst


To see a list of import requests and the status of each of them use the Get-MailboxImportRequest cmdlet:

[PS] C:\Windows\system32>Get-MailboxImportRequest

Name Mailbox Status
---- ------- ------
MailboxImport domain/Users/username InProgress


To see current status of a single import including percentage completed use the Get-MailboxImportRequestStatistics cmdlet:

[PS] C:\Windows\system32>Get-MailboxImportRequestStatistics -Identity username\MailboxImport

Name Status TargetAlias PercentComplete
---- ------ ----------- ---------------
MailboxImport InProgress username 5


There has been an I/O Error: Error #2038

The reason is that IIS 7 and greater has a request limit of 28.6 MB. The limit can be raised to 100 MB using the following commands:

cd C:\Windows\System32\inetsrv
appcmd set config -section:requestFiltering -requestLimits.maxAllowedContentLength:104857600


You can also do this in the IIS Manager:

1. Open the IIS Manager
2. From the server home tree item, open the Request Filtering item
3. Click Edit Feature Settings... on the right
4. Set the Maximum allowed content length (Bytes)

1. Write a file 2x the size of the RAM to make sure we get the real write rate. In this example the RAM of the server is 1 GB so I'm writing a 2 GB file (8KB * 250000 = 2GB). You can adjust the number of blocks to make it suitable for the amount of RAM in your system .

time sh -c "dd if=/dev/zero of=ddfile bs=8k count=250000 && sync"


2. Write a new file equal to the amount of RAM in the system to flush out the data cached with last action (8KB * 125000 = 1GB).

dd if=/dev/zero of=ddfile2 bs=8K count=125000


3. Test the read speed

time dd if=ddfile of=/dev/null bs=8k


Turns out the problem is that the default locale was set to one not supporting those characters. To fix it, change the default locale to a better match or set the locale manually using the setlocale function:

setlocale(LC_ALL, 'is_IS');