The FrontEnd has been writen using ASP.Net MVC. Due to this it requires the .Net Framework 3.5 SP1 to be installed on the webserver. It has been written to run on IIS7 (Windows Server 2008) but also runs on IIS6 with some modifications in the configuration without any problems.

So test the FrontEnd you first need to follow these steps:
  • Download the files from this codeplex site
  • Extract the content of the zip file into a folder on your Webserver
  • Add an Application to IIS and point it to this folder
  • Configure the connection string to point to your MDT Database
  • Configure the Virtual Directory for Wildcard mapping (IIS 6 only)
  • That's it

Two steps probably need some further information:

First the connection String. Open the web.config file in the root of your virtual Directory. Search for the section <connectionStrings>...</connectionStrings>. You should find two Entries ("MDTEntities" and "SCCMEntities") there similar to this:

    <add name="MDTEntities" connectionString="metadata=res://*/MDT.csdl|res://*/MDT.ssdl|res://*/MDT.msl;provider=System.Data.SqlClient;provider connection string=&quot;Data Source=YourSQLServer;Initial Catalog=YourMDTDatabase;User ID=YourMDTDBAdminAccount; Password=YourMDTDBAdminAccountPassword;MultipleActiveResultSets=True&quot;" providerName="System.Data.EntityClient" />
    <add name="SCCMEntities" connectionString="metadata=res://*/MDT.csdl|res://*/MDT.ssdl|res://*/MDT.msl;provider=System.Data.SqlClient;provider connection string=&quot;Data Source=YourSCCMDBServer;Initial Catalog=YourSCCMDatabase;User ID=YourSCCMDBReaderAccount; Password=YourSCCMDBReaderAccountPassword;MultipleActiveResultSets=True&quot;" providerName="System.Data.EntityClient" />

These connection strings are rather long and not that easy to read. But important are only 4 settings:
  • YourSQLServer / YourSCCMDBServer
  • YourMDTDatabase / YourSCCMDatabase
  • YourMDTDBAdminAccount / YourSCCMDBReaderAccount
  • YourMDTDBAdminAccountPassword / YourSCCMDBReaderAccountPassword

simply replace these values with ones appropiate to your environment (if hope they are self-explanatory enough :-) )

The Account for the MDT Database need to have read and write permission as it makes changes to the Database. The SCCM Account does only need Read access so dbreader is more then enough. Currently you could limit this to SELECT permission on vPackage and v_Program in case you need to have it even more secure. The SCCM Connection string is only used to search for packages on the SCCM Server. So if you don't want to use this feature you can simply skip this connection string.

Second, the configuration for IIS6. To get it running on IIS6 you need to enable wildcard mapping for this website. To enable this simply follow these steps:
  • Open IIS Manager
  • Right click your App or Virtual Directory
  • Choose Properties
  • On the Directory Tab click on Configuration
  • Under Wildcard application maps click on Insert (NOT Add)
  • Enter C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll as value for Executable (Or C:\Windows\Microsoft.NET\Framework64\v2.0.50727\aspnet_isapi.dll for the 64 Bit dll. Thanks to Jason Scheffelmaer for this tip.)
  • Uncheck(!) Verify that the file exists
  • OK - OK
  • You are done!

After this you should be able to open the website and access the configured database. If there are any issues you most probably have a wrong connection string or the permission to the database is not set correctly. Currently there is not really good Troubleshooting implemented into the Front End. This is one of the To-Do'ss for the close future. (does anybody have some good "Best-Practice" on how to implement Error handling, troubleshooting/Tracing into a webapplication?)

Last edited Oct 16, 2009 at 6:34 PM by MaikKoster, version 10


No comments yet.