Configuring the connection Strings

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.


Back to the Installation Guide

Last edited Nov 3, 2009 at 9:46 PM by MaikKoster, version 1

Comments

No comments yet.