Use sysprep for new sid – Win2k3 R2

Just used sysprep to generate new sid for Win2K3 R2 x64, after shutting down vmware guest in ESX3.5U2 cluster, and after cloning this Win2k3 R2 guest. First download the sysprep, install it, it should be in c:\windows\system32\deploy.cab. Doubleclick to extract files in it to another folder, say c:\sysprep. It would have sysprep.exe file in it. Run it and choose “Reseal” with Shutdown option set to “Reboot”.

Save the output from psgetsid.exe for the old sid, and do the same thing after new sid generated, we could see the difference between these sids ..

Upgrade SQL Server 2005 Evaluation Edition to SQL Server 2005 Enterprise Edition

This is Win2K3 Standard 64bit SP2, with SQL 2005 Evaluation Edition (everything checked and installed) SP2, with all latest patches. Even though Microsoft says this upgrade is doable, it is really painful & buggy.

http://msdn.microsoft.com/en-us/library/ms144259(SQL.90).aspx

This one is needed, otherwise RS_Server (Report Server) will fail with “UpgradeAdvisor returned -1″:

Copy the BPAClient.dll file from the following location C:\Program Files(x86)\Microsoft SQL Server\90\Setup Bootstrap\BPA\bin to C:\Program Files(x86)\Microsoft SQL Server\90\Setup Bootstrap\BPA.

Refer: http://blogs.msdn.com/sqlserverfaq/archive/2009/07/15/upgrade-advisor-returns-error-while-upgrading-an-instance-of-sql-server-2000-to-sql-server-2005.aspx

start /wait setup.exe /qb INSTANCENAME=MSSQLSERVER UPGRADE=SQL_Engine,Analysis_Server,RS_Server,SQL_DTS,Notification_Services,Client_Components ADDLOCAL=ALL SKUUPGRADE=1

Refer: http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/de61447c-9f78-41de-82b4-9f469c8593c5

http://sql-articles.com/index.php?page=articles/eval2entupgrage.html

Note:

ADDLOCAL=ALL is not enough to cover everything, the UPGRADE part also needs to include other components, there are more hints on this from template.ini file under installation ‘Server’ folder.

So now, everything should work for the upgrade, but after this is done, when starting the client application, it would fail saying some report file can’t be found. in this case, go ahead and apply SQL 2005 SP2, things would be fine after that ..