I went through this tutorial, and while everything went smoothly through most of the article, at the end, when I deployed the report, it fell down. It does not want to use the Windows Authentication I chose, I get an error opeing the report; and I did not get the pretty interface to navigate to the report like the one pictured, but cannot figure out what's different between my environment and the article's.

I'd like to know if these issues can be helped now, or will be addressed in a subsequent article.

Thanks,
Chris

It seems that Reports Server can't use Windows Authentication, because Reports Server appears to pass it the authentication for the web server, not the authentication from the IE user hitting the site. If I use the "The credentials supplied by the user running the report" option, I cna specify a user ID and PW when runnign the report. I had hoped to use "Windows NT Integrated Security" and, since this is an Intranet site, added to my Intranet sites list in IE, have IE pass my NT login info to the web server and it pass that info to the SQL Server for seemless authentication. I guess this is a little too much to expect though, but we can put a man on the moon....

I did find the other area you spoke of, with the pretty interface and report menu. This does look like it may be a useful tool, once I learn more about it and can articulate its usefulness and features to others in my organization. I will have to figure out a better authentication method though, but I hate to go with SQL standard security.

Thanks
Chris

Forgive me for being thick, but where/how can I get the client component?

I have a CD for Reporting Services (from the Microsoft Action Pack) and have installed on my server to try it out. But I haven't found anything anywhere for installing a client component. I also looked at the link in the article which is for a trial version. Since I have a CD, I don't know if that'll help.

Please, a simple answer for a simple person

Kevin

I thought this was a great start.  I took it and made some slight modifications to include the run duration and the start time for each job.  Then I created a subscription to email me every morning so I don't have to go out and look at every one of my servers every morning, I just have to check my email. 

Thanks for putting this out there.