Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a small Windows network (~30 machines) and I need to deploy SQL Server 2005 Reporting Services. Because I use SQL Server Standard Edition and not Enterprise, I am forced to use Windows Authentication to the users.

I am a Linux admin, and have near zero knowledge on Active Directory. As deep as my shallow knowledge goes, I think that I would need to invest in a domain server, a mirrored backup of that domain server. I think that I need to change every computer to use this domain too, and if the domain server goes down, every computer will be unavailable.

Is there a easier way to deploy Windows Authentication so that users can access Reporting Services from their computers without changing the infra-structure that much?


share|improve this question
I see your edit, and it does not change my answer at all. You've had 4 months to try - any success? Any failures? Relevant new information? – mfinni Jun 23 '10 at 2:08
Whoops - so sorry. I thought your edit was recent. – mfinni Jun 23 '10 at 2:08

Yes. Windows Authentication just means that the Windows accounts on the server are what's used for SQL logins, instead of SQL-only accounts defined within SQL Server Management Studio. If the SQL server isn't in a domain (your existing case), then it will use the local Windows accounts (found with Computer Management, Users and Groups.)

You don't need to become a Windows expert to admin an MS SQL server, but you should definitely read up on the SQL Server documentation and maybe get a few hardcopy books if you're wading into this particular pool.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.