The Deployment Guys

Helping to deploy your world automagically...

Clustering the MDT Database

Clustering the MDT Database

  • Comments 1
  • Likes

Sometimes for availability purposes, it is necessary to ensure the MDT database is clustered to allow failover in case of a server failure or maintenance event. There are a few things that you want to keep in mind when you decide to do this:

1. The SQL Browser service is NOT cluster-aware. This means if you put the database on a named instance of SQL, when clients request a connection to the SQL Cluster IP, the node IP will respond. This makes the Windows Firewall in Vista, Win7 and even Windows PE regard the traffic as unsolicited and hence blocks it. You can add an exception to all of your Full OS clients, however WinPE does not allow you to customize the firewall and you would have to shut the entire firewall off – this is not recommended.  The best way to resolve this is to ensure that the MDT Database is on the DEFAULT INSTANCE and does not need to use the SQL Browser service.

2. MDT Authentication share. In order to check windows authentication to the SQL Server, MDT attempts to connect to a Windows Share on the box. In a cluster, you can set this share up as a cluster resource. Ensure that the cluster resource fails over with the MDT database, i.e. is part of the same group. Also make sure that the network access account has access to the share and DB Reader access to the database. If you are not using windows authentication, ensure that you include DBID and DBPW fields in your queries.

3. Use the Cluster name in CustomSettings.ini. In the CustomSettings.ini file, ensure that the name you use for the SQLServer property in each query is the cluster name – do not specify an Instance Name.

4. Named Pipes – Ensure that you have named pipes set up on your SQL Server.

Note that this post covers clustering the MDT database only. You can follow LTI – Following Daniel’s excellent advice on clustering the resource of the Distribution Share http://blogs.technet.com/deploymentguys/archive/2008/03/31/up-ping-the-uptime-of-your-lite-touch-server.aspx you can ensure that this resource is also on the same group as the MDT Database.

Happy clustering :).

Disclaimer: The information on this site is provided "AS IS" with no warranties, confers no rights, and is not supported by the authors or Microsoft Corporation. Use of included script samples are subject to the terms specified in the Terms of Use.

This post was contributed by Aly Shivji a consultant with Microsoft Services - U.S. East Region.

  • I'm trying to get MDT 2010 Update 1 to read from a SQL 2008 SP1 cluster. So far, I've created a SQL user and gave it read access to the MDT2010 database. I've even disabled the WinPE firewall ...still no dice.

    This is what i have for entries in my customsettings.ini...maybe I'm missing something:

    -------------------

    [Settings]

    Priority=CSettings, Default

    [Default]

    DoCapture=NO

    ComputerBackupLocation=NONE

    BDEInstallSuppress=YES

    [CSettings]

    SQLServer=SQLServer

    Instance=SQL_instance

    DBID=MDTReader

    DBPWD=*******

    Database=MDT2010

    Netlib=DBNMPNTW

    SQLShare=MDTLogs$

    Table=ComputerSettings

    Parameters=UUID, AssetTag, SerialNumber, MacAddress

    ParameterCondition=OR

    -----------------  

    Any help or suggestions would be greatly appreciated.

    Thanks

    kevin

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment