Ctrl-Alt-Delete via Remote Desktop

If you are logged into a remote server and you want to send a "ctrl-alt-delete" to that server, then you can press ctrl-alt-end and this will give you the desired effect.

SBS 2003 to SBS 2008 Migration

So another SBS 2003 to SBS 2008 migration down and many more yet to come. Have learnt a few extra bits and pieces in order to aid in a successfully SBS migration. It is a bit long winded and can chew up a few extra hours, but in my opinion you need to play SBS migrations safely otherwise you could loose your domain


Required Items:
1) Latest SBS 2003 to SBS 2008 Migration guide
2) A Test server, Desktop and the new SBS 2008 server
3) Latest exchange 2007 service pack
4) Latest Windows/SBS service pack
5) USB drive for migration answer file

Before the Test Migration:
1) Pray to Jesus (I'm serious)
2) Download the latest Microsoft SBS 2003 to SBS 2008 migration document and memorise it.
3) Make sure the SBS 2003 source server is up to date with Microsoft updates.
4) Fix all AD Journal Wrap errors on the source server.

Test Migration Phase: 
1) Take a backup of the server using the product Shadow Protect  and restore the image to a test server (Follow the HIR instructions on the shadow protect site to the absolute letter).
2) If feasible take a backup of a desktop/laptop and restore it to a test Desktop/Laptop aswell.
3) Uninstall any anti virus clients you have on the source test server (disabling them isn't enough).
4) Perform at least one reboot of the server before commencing.
5) Perform a test migration up to the phase of decommissioning
6) Log into the test laptop/desktop and verify it can access domain resources.
7) Complete the decommissioning phase
8) Create a checklist of things which need to be done during and after the migration based on your experiences from the test migration (this is critical and will help you later on).

During Migration:
1) Pray again
2) If you are planning to change the remote access name of the server, this could affect VPN's and phone syncing. Make sure you let the end users know.
4) Halt mailflow - You want all emails to go through to the new server. If you are paranoid about loosing emails during the migration, then set-up a secondary MX.
3) Take another backup of the server right before migration. Restore the image to your test server again and perform the migration off your test server. This will give you the perfect fall back position if the migration fails. (Make sure your real source server is turned off......)
4) Follow every step of the Microsoft SBS 2003 to SBS 2008 document and tick each section as you go right up to the part you get the green light to move files and migrate exchange mailboxes.
5) Install the latest exchange 2007 and Windows service pack.
6) Run Microsoft updates on the SBS 2008 server.
7) Perform all the steps up to the decommissioning of the source server. I would probably recommend leaving the source server in production for atleast a week. Generally this will give you enough time to make sure every computer has logged into the network and nothing is amiss.

If you were using batch scripts to map network drives, then there are .vbs scripts available which will disconnect old drive mappings and reconnect the new ones (Ive found that sometimes batch scripts dont do a good job of removing old mapped network drives).

Here is a example vbs script I have used:

***************************

On Error Resume Next

Set objSysInfo = CreateObject("ADSystemInfo")
Set objNetwork = CreateObject("Wscript.Network")

'removes mapped drive G
objNetwork.RemoveNetworkDrive "G:", True, True

'creates maped drive G
objNetwork.MapNetworkDrive "G:", "\\servername\sharename"
**************************


To save some time with printers, it might be a good idea to add a printer remove/add section to the login script. I have yet to do this, but looking forward to finding out.