We help IT Professionals succeed at work.

Installing SQL Server 2005 Analysis Services on Windows 2003 Server (Workgroup or Domain?)

Last Modified: 2013-11-16

I will install a Windows 2003 Server Enterprise Edition with SP2.

I will install a Sql Server 2005 SP2 including the Analysis Services and all the others services, with all the tools and examples on that Windows 2003 Server.

I have a notebook (client) with a Windows XP HOME SP3.

I want to connect my notebook as client with the remote Analysis Services on the Windows 2003 Server using my LAN.

Here my questions:

1) The Windows 2003 Server can be a Workgroup or it must be a Domain Controller?

2) What user account I must to set for the SQL Server Database Services, Analysis services, Reporting Services, Notification Services, Integration Services and Browse Services, in order to allow remote connections?  (Domain User, Local System, Network Service, Local Service, etc.).

3) My XP Home will be able to connect to the remote Analysis Services on the Windows 2003 Server, or I will need to upgrade to XP Professional?
(I know that the XP Home Edition can not be joining to a domain).

I will appreciate any comments about it.

Thanks in advance,

Watch Question

Awarded 2007
Top Expert 2008
This one is on us!
(Get your first solution completely free - no credit card required)


Thanks KCTS:

After all the tests that I have made this weekend, now I can confirm that, Windows XP Home can connect with a remote Analysis Services. (Against which Microsoft says).

Following the steps that I made:

Install Windows 2003 Server Enterprise SP2 as a Workgroup. (If installed as a domain controller, the Windows XP Home client will not connect with this remote instance).

Install Sql Server 2005 SP2 and use Local System Account for every service.

Enable remote connections for the Analysis Services using the SQL Server Surface Area Configuration, (some Sql Server versions have disabled the remote connections as default).

Be sure that the Analysis Services are listening in the 2383 port. (Try Telnet MyServer 2383 from the client).

On Windows 2003 Server, create an account with the same name and the same password as the Windows XP Home Client, and include it account into the Sql Server 2005 MS OLAP Users Group. (Remember that Windows XP Home cannot connect to a domain controller).

When try the connection from the Windows XP Home client, (because the name and password of the client user are the same that a member user of the OLAP group), the connection will be done without problems.

Ok, thats all.

Thanks for your comment.



Thanks for your comments.
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.