How to extend the MDT 2010 database with custom settings

  • Article

Add a new column to the settings table (can be done with SQL Management Studio) Capture

 

Give it a name and specify a datatype Capture2

 

Run the following stored procedure against the MDT database

EXECUTE sp_refreshview '[dbo].[ComputerSettings]'
EXECUTE sp_refreshview '[dbo].[LocationSettings]'
EXECUTE sp_refreshview '[dbo].[MakeModelSettings]'
EXECUTE sp_refreshview '[dbo].[RoleSettings]'

Edit the customsettings.ini with the new column

Under the [Settings] section add your column name to the properties line

Capture4

 

Now its possible to add a value to the column you added.

Capture3

 

To test this run: cscript ZTIGather.wsf /inifile:E:\deployshare\CustomSettings.ini from the scripts directory and point to the customsettings.ini file that is configured with the settings to query the MDT database.

 

Capture5

 

Capture6

Now we can see that the property CustomCollection002 is set to C0010000

 

To reference the new value you would use the variable %CustomCollection002%

 

For more information see the section “Extending the Schema of the MDT DB” in “Using the Microsoft Deployment Toolkit.docx” that can be downloaded here: Optional - MDT 2010 Print-Ready Documentation

Comments

  • Anonymous
    October 01, 2010
    Just what i was looking for.  Saves me reading boring MS manuals!!! LOL

  • Anonymous
    July 13, 2011
    I have setup DB etc. and in Database created a Computer entry with serial and under Make and Model an entry for Model. Problem is that when I run litetouch.vbs the model entry seems to overide the computer serial entry made. (For ex. serial number is of a Dell Optiplex 960 and model entry is Dell Optiplex 960.) Surely serial number should get preferance. When I remove the model entry then query runs all conditions associated with serial? How do ensure that if the serial nmber is found that the model query gets disregarded?

  • Anonymous
    July 16, 2011
    You can set the Priority in CustomSettings.ini

  • Anonymous
    July 10, 2014
    Thanks. This helped me in MDT 2013 too

  • Anonymous
    October 26, 2015
    This just resolved an ongoing headache where additional NICs were being applied as Disks during deployment!

  • Anonymous
    January 11, 2016
    The comment has been removed

  • Anonymous
    January 14, 2016
    The comment has been removed

    • Anonymous
      June 09, 2016
      Can you upload the post with screenshot ? i must refresh the mdt database with columns but i dont know howThanks a lot.