More than 2010 upgrade readiness, this tool is a one stop 2007 best practices analyzer. Most 2007 farms have dozens of small customizations. Get started today because it will require time to take inventory and review the output. The results help build a deep awareness of your system configs. This command is read-only and safe to run in production any time, even during the work day.
So go ahead, RDP over and run “STSADM –O PREUPGRADECHECK” now!
Today I felt the need to step outside of SharePoint a little and wander over to the SQL consoles and learn something new. Bottom line: works the same, just more reliable. SSRS 2008 R2 seems to me to be roughly equal on config options to what we had for SQL 2005. Similar wizard to get it created, similar Central Admin link to give the URL, even the menu names match.
However, the whole thing “feels” more reliable. Once complete I can clearly see the SSRS features on the Site Settings menu. Next, I need to learn BIDS (Business Intelligence Development Studio) to create a report (RDL) and try uploading it for rendering.
Open “Reporting Services Configuration Manager” and follow wizard steps to create SSRS on SQL backend.
When asked use “SharePoint integrated” mode.
It will make a SQL database and IIS website. I used my main SP web application (http://sp2010) so that final URL is http://sp2010/ReportServer/
Open “SharePoint Central Administration”
Navigate to “General Application Settings > Reporting Services Integration”
Type that same URL, choose “Windows Authentication”, and provide a user account.
I’m using DEMOadmin for everything which is not a best practice, but works in DEV systems to avoid any “access denied” messages.
Create desktop shortcut to “C:Program FilesMicrosoft SQL ServerMSRS10_50.MSSQLSERVERReporting ServicesReportServerReportBuilderReportBuilder_3_0_0_0.application”
Click the desktop icon for first install
Enjoy the Report Builder 3.0 application to create .RDL and upload to SharePoint
We now have a User Profile Service Application and 2 Windows services as well as the Forefront Identity product. It gets a bit confusing so I wanted to write a post with my observations in case it helps anyone else out there Googl-ing for answers.
Opening MIISCLIENT.EXE while sync is actively running has been very educational and helpful for me in troubleshooting. Consider it an eventlog for just the profile service. Below you can see my full import creating 141 new records in the database. I used this to confirm the service health as well as get familiar with the FULL and DELTA operations it runs that map to the Full and Incremental we see in Central Administration.
Oh, and there are 3 SQL databases now! [Sync DB], [Social DB], and [Profile DB] are all required. Look at Harbar.net’s incredible Architecture Overview Diagram to learn more about the topology. It’s tedious to get everything configured and connected but once online the new social features are incredibly useful.