MVP please help - S/W installation order on XP box as part of domain

[Valerie Hough]

Hi,

I have an XP SP2 box with no S/W other than the operating system on it now.
I want to add packages such as .NET, SQL Server Client Utilities, MS Office,
Quick Books, Full Shot, et al.

I plan for this box to join a domain and I would like all the S/W to be
available from both the domain and the XP local account.

Should I install new S/W before or after I join the domain? If the latter,
should I install the S/W while logged in locally or logged in as a member of
the domain?

Obviously SQL Server 2000 Client Utilities have no meaning except in the
context of the SQL Server Database Engine installed on my domain controller,
but a number of the others do.

Thanks in advance.
Valerie Hough

 

[Shenan Stanley]

I have an XP SP2 box with no S/W other than the operating system on
it now. I want to add packages such as .NET, SQL Server Client
Utilities, MS Office, Quick Books, Full Shot, et al.

I plan for this box to join a domain and I would like all the S/W to
be available from both the domain and the XP local account.

Should I install new S/W before or after I join the domain? If the
latter, should I install the S/W while logged in locally or logged in
as a member of the domain?

Obviously SQL Server 2000 Client Utilities have no meaning except in
the context of the SQL Server Database Engine installed on my domain
controller, but a number of the others do.

It makes no difference. The limitation on who can use the software depends
on file permissions for the most part.. Are you saying your domain user
restrictions are too tight for the applications?