Install MSDE on New System

I currently have a WinXP system which has MSDE installed. I am replacing
that system with a new one and I want to install MSDE and then move a copy
of all my current DBs. I have MS Office 2003 and I plan to install MSDE from
those CDs. To move copies of the DBs I plan to Detach them at the old
system, copy the DB to the new system and attach it there (and attach it
back on the old system as well - just to be safe)
Is that a reasonable approach or is there a better way?
Wayne
hi Wayne,
Wayne Wengert wrote:
> I currently have a WinXP system which has MSDE installed. I am
> replacing that system with a new one and I want to install MSDE and
> then move a copy of all my current DBs. I have MS Office 2003 and I
> plan to install MSDE from those CDs. To move copies of the DBs I plan
> to Detach them at the old system, copy the DB to the new system and
> attach it there (and attach it back on the old system as well - just
> to be safe)
> Is that a reasonable approach or is there a better way?
> Wayne
it's a reasonable approach ... you can go on..
just a note... if you use SQL Server standard logins, please verify orphaned
user, that's to say users no longer in sync with their respective logins...
this sync is established on the sid column of database..sysusers and
master..syslogins, and where NULL is returned you have orhpaned users
problems.. so please check
http://msdn.microsoft.com/library/de...ca-cz_8qzy.asp
for sp_change_users_login system stored procedure synopsis and
http://www.sqlservercentral.com/colu...okenlogins.asp
Neil Boyle article for further info..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks. Will do!
Wayne
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3cdnj9F6l0itoU1@.individual.net...
> hi Wayne,
> Wayne Wengert wrote:
> it's a reasonable approach ... you can go on..
> just a note... if you use SQL Server standard logins, please verify
orphaned
> user, that's to say users no longer in sync with their respective
logins...
> this sync is established on the sid column of database..sysusers and
> master..syslogins, and where NULL is returned you have orhpaned users
> problems.. so please check
>
http://msdn.microsoft.com/library/de...ca-cz_8qzy.asp
> for sp_change_users_login system stored procedure synopsis and
> http://www.sqlservercentral.com/colu...okenlogins.asp
> Neil Boyle article for further info..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>

Install MSDE 2000 on WinXP home failed

Dear all,
During install MSDE 2000 on WINXP HOME edition, not complete and then
rollback, could anyone can help?
Thanks.
Below attached error.log content.
2004-12-23 16:47:36.38 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
2004-12-23 16:47:36.38 server Copyright (C) 1988-2002 Microsoft
Corporation.
2004-12-23 16:47:36.38 server All rights reserved.
2004-12-23 16:47:36.38 server Server Process ID is 3808.
2004-12-23 16:47:36.38 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$TL_MSDE\LOG\ERRORLOG'.
2004-12-23 16:47:36.42 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2004-12-23 16:47:36.44 server SQL Server configured for thread mode
processing.
2004-12-23 16:47:36.44 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2004-12-23 16:47:36.45 spid3 Warning ******************
2004-12-23 16:47:36.45 spid3 SQL Server started in single user mode.
Updates allowed to system catalogs.
2004-12-23 16:47:36.46 spid3 Starting up database 'master'.
2004-12-23 16:47:36.61 server Using 'SSNETLIB.DLL' version '8.0.766'.
2004-12-23 16:47:36.64 spid5 Starting up database 'model'.
2004-12-23 16:47:36.91 spid3 Server name is 'DLINK\TL_MSDE'.
2004-12-23 16:47:36.91 spid3 Skipping startup of clean database id 5
2004-12-23 16:47:36.91 spid3 Skipping startup of clean database id 6
2004-12-23 16:47:36.91 spid3 Starting up database 'msdb'.
2004-12-23 16:47:36.92 server SQL server listening on 169.254.159.200:
1104.
2004-12-23 16:47:36.92 server SQL server listening on 219.76.249.145: 1104.
2004-12-23 16:47:36.92 server SQL server listening on 127.0.0.1: 1104.
2004-12-23 16:47:36.92 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2004-12-23 16:47:36.92 server SQL Server is ready for client connections
2004-12-23 16:47:37.11 spid5 Clearing tempdb database.
2004-12-23 16:47:38.16 spid5 Starting up database 'tempdb'.
2004-12-23 16:47:38.23 spid3 Warning ******************
2004-12-23 16:47:38.23 spid3 Attempting to change default collation to
Chinese_Taiwan_Stroke_CI_AS.
2004-12-23 16:47:41.78 spid3 Clustered index restored for
master.sysdatabases.
2004-12-23 16:47:41.93 spid3 Non-clustered index restored for
master.sysobjects.
2004-12-23 16:47:42.09 spid3 Non-clustered index restored for
master.sysobjects.
2004-12-23 16:47:42.13 spid3 index restored for master.syscolumns.
2004-12-23 16:47:42.23 spid3 index restored for master.systypes.
2004-12-23 16:47:42.25 spid3 index restored for master.sysusers.
2004-12-23 16:47:43.50 spid3 index restored for master.sysproperties.
2004-12-23 16:47:43.57 spid3 index restored for
master.sysfulltextcatalogs.
2004-12-23 16:47:43.76 spid3 index restored for master.sysxlogins.
2004-12-23 16:47:43.79 spid3 index restored for master.sysdevices.
2004-12-23 16:47:44.19 spid3 index restored for master.sysservers.
2004-12-23 16:47:45.66 spid3 index restored for master.syslanguages.
2004-12-23 16:47:45.71 spid3 index restored for master.syscharsets.
2004-12-23 16:47:45.75 spid3 index restored for master.sysfilegroups.
2004-12-23 16:47:46.05 spid3 index restored for master.spt_values.
2004-12-23 16:47:46.06 spid3 index restored for
master.MSreplication_options.
2004-12-23 16:47:46.08 spid3 index restored for
master.spt_datatype_info_ext.
2004-12-23 16:47:46.09 spid3 index restored for master.spt_datatype_info.
2004-12-23 16:47:46.15 spid3 Non-clustered index restored for
tempdb.sysobjects.
2004-12-23 16:47:46.15 spid3 Non-clustered index restored for
tempdb.sysobjects.
2004-12-23 16:47:46.15 spid3 index restored for tempdb.syscolumns.
2004-12-23 16:47:46.15 spid3 index restored for tempdb.systypes.
2004-12-23 16:47:46.16 spid3 index restored for tempdb.sysusers.
2004-12-23 16:47:46.16 spid3 index restored for tempdb.sysproperties.
2004-12-23 16:47:46.16 spid3 index restored for
tempdb.sysfulltextcatalogs.
2004-12-23 16:47:46.18 spid3 index restored for tempdb.sysfilegroups.
2004-12-23 16:47:46.35 spid3 Non-clustered index restored for
model.sysobjects.
2004-12-23 16:47:46.35 spid3 Non-clustered index restored for
model.sysobjects.
2004-12-23 16:47:46.45 spid3 index restored for model.syscolumns.
2004-12-23 16:47:46.46 spid3 index restored for model.systypes.
2004-12-23 16:47:46.52 spid3 index restored for model.sysusers.
2004-12-23 16:47:46.52 spid3 index restored for model.sysproperties.
2004-12-23 16:47:46.52 spid3 index restored for
model.sysfulltextcatalogs.
2004-12-23 16:47:46.54 spid3 index restored for model.sysfilegroups.
2004-12-23 16:47:46.76 spid3 Non-clustered index restored for
msdb.sysobjects.
2004-12-23 16:47:46.77 spid3 Non-clustered index restored for
msdb.sysobjects.
2004-12-23 16:47:46.79 spid3 index restored for msdb.syscolumns.
2004-12-23 16:47:46.79 spid3 index restored for msdb.systypes.
2004-12-23 16:47:46.80 spid3 index restored for msdb.sysusers.
2004-12-23 16:47:46.80 spid3 index restored for msdb.sysproperties.
2004-12-23 16:47:46.80 spid3 index restored for msdb.sysfulltextcatalogs.
2004-12-23 16:47:46.80 spid3 index restored for msdb.sysfilegroups.
2004-12-23 16:47:46.83 spid3 index restored for msdb.sysjobschedules.
2004-12-23 16:47:46.84 spid3 index restored for msdb.syscategories.
2004-12-23 16:47:46.84 spid3 index restored for msdb.systargetservers.
2004-12-23 16:47:46.84 spid3 index restored for
msdb.systargetservergroups.
2004-12-23 16:47:47.96 spid3 index restored for msdb.sysalerts.
2004-12-23 16:47:47.96 spid3 index restored for msdb.sysoperators.
2004-12-23 16:47:47.97 spid3 index restored for
msdb.syscachedcredentials.
2004-12-23 16:47:47.97 spid3 index restored for msdb.logmarkhistory.
2004-12-23 16:47:48.00 spid3 index restored for msdb.sysdtscategories.
2004-12-23 16:47:48.00 spid3 index restored for
msdb.sysdbmaintplan_databases.
2004-12-23 16:47:48.01 spid3 index restored for msdb.mswebtasks.
2004-12-23 16:47:48.01 spid3 index restored for msdb.sysdownloadlist.
2004-12-23 16:47:48.01 spid3 index restored for msdb.sysjobs.
2004-12-23 16:47:48.02 spid3 index restored for msdb.sysjobsteps.
2004-12-23 16:47:48.57 spid3 Default collation successfully changed.
2004-12-23 16:47:49.07 spid3 Recovery complete.
2004-12-23 16:47:49.07 spid3 SQL global counter collection task is
created.
2004-12-23 16:47:49.10 spid3 Warning: override, autoexec procedures
skipped.
2004-12-23 16:47:56.63 spid3 SQL Server is terminating due to 'stop'
request from Service Control Manager.
Hi
Excuse my English
I've got this problème.
Carefull if several install/uninstall...
Carefull if several servers connected with two instances with same name...
See http://support.microsoft.com/default...en-us;320873#3
for a clean uninstallation.
JCH
kpler a écrit :
> Dear all,
> During install MSDE 2000 on WINXP HOME edition, not complete and then
> rollback, could anyone can help?
> Thanks.
> Below attached error.log content.
>
> 2004-12-23 16:47:36.38 server Microsoft SQL Server 2000 - 8.00.760
> (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
> 2004-12-23 16:47:36.38 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2004-12-23 16:47:36.38 server All rights reserved.
> 2004-12-23 16:47:36.38 server Server Process ID is 3808.
> 2004-12-23 16:47:36.38 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL$TL_MSDE\LOG\ERRORLOG'.
> 2004-12-23 16:47:36.42 server SQL Server is starting at priority class
> 'normal'(1 CPU detected).
> 2004-12-23 16:47:36.44 server SQL Server configured for thread mode
> processing.
> 2004-12-23 16:47:36.44 server Using dynamic lock allocation. [500] Lock
> Blocks, [1000] Lock Owner Blocks.
> 2004-12-23 16:47:36.45 spid3 Warning ******************
> 2004-12-23 16:47:36.45 spid3 SQL Server started in single user mode.
> Updates allowed to system catalogs.
> 2004-12-23 16:47:36.46 spid3 Starting up database 'master'.
> 2004-12-23 16:47:36.61 server Using 'SSNETLIB.DLL' version '8.0.766'.
> 2004-12-23 16:47:36.64 spid5 Starting up database 'model'.
> 2004-12-23 16:47:36.91 spid3 Server name is 'DLINK\TL_MSDE'.
> 2004-12-23 16:47:36.91 spid3 Skipping startup of clean database id 5
> 2004-12-23 16:47:36.91 spid3 Skipping startup of clean database id 6
> 2004-12-23 16:47:36.91 spid3 Starting up database 'msdb'.
> 2004-12-23 16:47:36.92 server SQL server listening on 169.254.159.200:
> 1104.
> 2004-12-23 16:47:36.92 server SQL server listening on 219.76.249.145: 1104.
> 2004-12-23 16:47:36.92 server SQL server listening on 127.0.0.1: 1104.
> 2004-12-23 16:47:36.92 server SQL server listening on TCP, Shared Memory,
> Named Pipes.
> 2004-12-23 16:47:36.92 server SQL Server is ready for client connections
> 2004-12-23 16:47:37.11 spid5 Clearing tempdb database.
> 2004-12-23 16:47:38.16 spid5 Starting up database 'tempdb'.
> 2004-12-23 16:47:38.23 spid3 Warning ******************
> 2004-12-23 16:47:38.23 spid3 Attempting to change default collation to
> Chinese_Taiwan_Stroke_CI_AS.
> 2004-12-23 16:47:41.78 spid3 Clustered index restored for
> master.sysdatabases.
> 2004-12-23 16:47:41.93 spid3 Non-clustered index restored for
> master.sysobjects.
> 2004-12-23 16:47:42.09 spid3 Non-clustered index restored for
> master.sysobjects.
> 2004-12-23 16:47:42.13 spid3 index restored for master.syscolumns.
> 2004-12-23 16:47:42.23 spid3 index restored for master.systypes.
> 2004-12-23 16:47:42.25 spid3 index restored for master.sysusers.
> 2004-12-23 16:47:43.50 spid3 index restored for master.sysproperties.
> 2004-12-23 16:47:43.57 spid3 index restored for
> master.sysfulltextcatalogs.
> 2004-12-23 16:47:43.76 spid3 index restored for master.sysxlogins.
> 2004-12-23 16:47:43.79 spid3 index restored for master.sysdevices.
> 2004-12-23 16:47:44.19 spid3 index restored for master.sysservers.
> 2004-12-23 16:47:45.66 spid3 index restored for master.syslanguages.
> 2004-12-23 16:47:45.71 spid3 index restored for master.syscharsets.
> 2004-12-23 16:47:45.75 spid3 index restored for master.sysfilegroups.
> 2004-12-23 16:47:46.05 spid3 index restored for master.spt_values.
> 2004-12-23 16:47:46.06 spid3 index restored for
> master.MSreplication_options.
> 2004-12-23 16:47:46.08 spid3 index restored for
> master.spt_datatype_info_ext.
> 2004-12-23 16:47:46.09 spid3 index restored for master.spt_datatype_info.
> 2004-12-23 16:47:46.15 spid3 Non-clustered index restored for
> tempdb.sysobjects.
> 2004-12-23 16:47:46.15 spid3 Non-clustered index restored for
> tempdb.sysobjects.
> 2004-12-23 16:47:46.15 spid3 index restored for tempdb.syscolumns.
> 2004-12-23 16:47:46.15 spid3 index restored for tempdb.systypes.
> 2004-12-23 16:47:46.16 spid3 index restored for tempdb.sysusers.
> 2004-12-23 16:47:46.16 spid3 index restored for tempdb.sysproperties.
> 2004-12-23 16:47:46.16 spid3 index restored for
> tempdb.sysfulltextcatalogs.
> 2004-12-23 16:47:46.18 spid3 index restored for tempdb.sysfilegroups.
> 2004-12-23 16:47:46.35 spid3 Non-clustered index restored for
> model.sysobjects.
> 2004-12-23 16:47:46.35 spid3 Non-clustered index restored for
> model.sysobjects.
> 2004-12-23 16:47:46.45 spid3 index restored for model.syscolumns.
> 2004-12-23 16:47:46.46 spid3 index restored for model.systypes.
> 2004-12-23 16:47:46.52 spid3 index restored for model.sysusers.
> 2004-12-23 16:47:46.52 spid3 index restored for model.sysproperties.
> 2004-12-23 16:47:46.52 spid3 index restored for
> model.sysfulltextcatalogs.
> 2004-12-23 16:47:46.54 spid3 index restored for model.sysfilegroups.
> 2004-12-23 16:47:46.76 spid3 Non-clustered index restored for
> msdb.sysobjects.
> 2004-12-23 16:47:46.77 spid3 Non-clustered index restored for
> msdb.sysobjects.
> 2004-12-23 16:47:46.79 spid3 index restored for msdb.syscolumns.
> 2004-12-23 16:47:46.79 spid3 index restored for msdb.systypes.
> 2004-12-23 16:47:46.80 spid3 index restored for msdb.sysusers.
> 2004-12-23 16:47:46.80 spid3 index restored for msdb.sysproperties.
> 2004-12-23 16:47:46.80 spid3 index restored for msdb.sysfulltextcatalogs.
> 2004-12-23 16:47:46.80 spid3 index restored for msdb.sysfilegroups.
> 2004-12-23 16:47:46.83 spid3 index restored for msdb.sysjobschedules.
> 2004-12-23 16:47:46.84 spid3 index restored for msdb.syscategories.
> 2004-12-23 16:47:46.84 spid3 index restored for msdb.systargetservers.
> 2004-12-23 16:47:46.84 spid3 index restored for
> msdb.systargetservergroups.
> 2004-12-23 16:47:47.96 spid3 index restored for msdb.sysalerts.
> 2004-12-23 16:47:47.96 spid3 index restored for msdb.sysoperators.
> 2004-12-23 16:47:47.97 spid3 index restored for
> msdb.syscachedcredentials.
> 2004-12-23 16:47:47.97 spid3 index restored for msdb.logmarkhistory.
> 2004-12-23 16:47:48.00 spid3 index restored for msdb.sysdtscategories.
> 2004-12-23 16:47:48.00 spid3 index restored for
> msdb.sysdbmaintplan_databases.
> 2004-12-23 16:47:48.01 spid3 index restored for msdb.mswebtasks.
> 2004-12-23 16:47:48.01 spid3 index restored for msdb.sysdownloadlist.
> 2004-12-23 16:47:48.01 spid3 index restored for msdb.sysjobs.
> 2004-12-23 16:47:48.02 spid3 index restored for msdb.sysjobsteps.
> 2004-12-23 16:47:48.57 spid3 Default collation successfully changed.
> 2004-12-23 16:47:49.07 spid3 Recovery complete.
> 2004-12-23 16:47:49.07 spid3 SQL global counter collection task is
> created.
> 2004-12-23 16:47:49.10 spid3 Warning: override, autoexec procedures
> skipped.
> 2004-12-23 16:47:56.63 spid3 SQL Server is terminating due to 'stop'
> request from Service Control Manager.

installation (instance name)

I am trying to install SqlServer PE on a WinXP desktop.
But I reach "install name" window where I am asked: "for a default
installation leave default checked..." and "to install a named instance clear
the default checkbox..." etc.
But the Default checkbox is grayed and I can just install a named instance.
What do I miss? I think it is not a user problem because I tryed with 2
different users (one is Administrator).
thanks in advanced for any feedback.
Hi
If Setup detects an already installed default instance, it will not let you
select the check box.
Maybe you have an instance of MSDE installed.
Look in Control Panel > Services to see if you have MSDE or SQL server
already installed.
Regards
Mike
"Francesco" wrote:

> I am trying to install SqlServer PE on a WinXP desktop.
> But I reach "install name" window where I am asked: "for a default
> installation leave default checked..." and "to install a named instance clear
> the default checkbox..." etc.
> But the Default checkbox is grayed and I can just install a named instance.
> What do I miss? I think it is not a user problem because I tryed with 2
> different users (one is Administrator).
> thanks in advanced for any feedback.
|||Correct. After the instance installation I have MSSQLSERVER and
MSSQL$my_instance. I suppose the first service is the engine that somebody
else installed previously... I'll try to remove the engine and start again.
Thanks.
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> If Setup detects an already installed default instance, it will not let you
> select the check box.
> Maybe you have an instance of MSDE installed.
> Look in Control Panel > Services to see if you have MSDE or SQL server
> already installed.
> Regards
> Mike
> "Francesco" wrote:

installation (instance name)

I am trying to install SqlServer PE on a WinXP desktop.
But I reach "install name" window where I am asked: "for a default
installation leave default checked..." and "to install a named instance clear
the default checkbox..." etc.
But the Default checkbox is grayed and I can just install a named instance.
What do I miss? I think it is not a user problem because I tryed with 2
different users (one is Administrator).
thanks in advanced for any feedback.Hi
If Setup detects an already installed default instance, it will not let you
select the check box.
Maybe you have an instance of MSDE installed.
Look in Control Panel > Services to see if you have MSDE or SQL server
already installed.
Regards
Mike
"Francesco" wrote:
> I am trying to install SqlServer PE on a WinXP desktop.
> But I reach "install name" window where I am asked: "for a default
> installation leave default checked..." and "to install a named instance clear
> the default checkbox..." etc.
> But the Default checkbox is grayed and I can just install a named instance.
> What do I miss? I think it is not a user problem because I tryed with 2
> different users (one is Administrator).
> thanks in advanced for any feedback.|||Correct. After the instance installation I have MSSQLSERVER and
MSSQL$my_instance. I suppose the first service is the engine that somebody
else installed previously... I'll try to remove the engine and start again.
Thanks.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> If Setup detects an already installed default instance, it will not let you
> select the check box.
> Maybe you have an instance of MSDE installed.
> Look in Control Panel > Services to see if you have MSDE or SQL server
> already installed.
> Regards
> Mike
> "Francesco" wrote:
> > I am trying to install SqlServer PE on a WinXP desktop.
> > But I reach "install name" window where I am asked: "for a default
> > installation leave default checked..." and "to install a named instance clear
> > the default checkbox..." etc.
> >
> > But the Default checkbox is grayed and I can just install a named instance.
> > What do I miss? I think it is not a user problem because I tryed with 2
> > different users (one is Administrator).
> > thanks in advanced for any feedback.

installation (instance name)

I am trying to install SqlServer PE on a WinXP desktop.
But I reach "install name" window where I am asked: "for a default
installation leave default checked..." and "to install a named instance clea
r
the default checkbox..." etc.
But the Default checkbox is grayed and I can just install a named instance.
What do I miss? I think it is not a user problem because I tryed with 2
different users (one is Administrator).
thanks in advanced for any feedback.Hi
If Setup detects an already installed default instance, it will not let you
select the check box.
Maybe you have an instance of MSDE installed.
Look in Control Panel > Services to see if you have MSDE or SQL server
already installed.
Regards
Mike
"Francesco" wrote:

> I am trying to install SqlServer PE on a WinXP desktop.
> But I reach "install name" window where I am asked: "for a default
> installation leave default checked..." and "to install a named instance cl
ear
> the default checkbox..." etc.
> But the Default checkbox is grayed and I can just install a named instance
.
> What do I miss? I think it is not a user problem because I tryed with 2
> different users (one is Administrator).
> thanks in advanced for any feedback.|||Correct. After the instance installation I have MSSQLSERVER and
MSSQL$my_instance. I suppose the first service is the engine that somebody
else installed previously... I'll try to remove the engine and start again.
Thanks.
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> If Setup detects an already installed default instance, it will not let yo
u
> select the check box.
> Maybe you have an instance of MSDE installed.
> Look in Control Panel > Services to see if you have MSDE or SQL server
> already installed.
> Regards
> Mike
> "Francesco" wrote:
>

Install Client Management Tool in WinXP Professional with SQL2005 CTP

SQL server 2005 was installed successfully with SQL2005 CTP CD(Enterprise edition). However, I tried to install Client Management Tool in my WinXP Professional desktop, it stated that incompatibility of OS. Does it mean that I can only install client management tool in WinXP profession with CTP for other editions except enterprise one? Thanks in advance.

Yep, you hit a bug. We've fixed this. The work around is to pull down one of the other Editions.

Dan