Thursday, March 11, 2010
Deployment Forum HomeDeployment Forum ArticlesDeployment Forum Download LibraryDeployment Forum Member BlogsDeployment Forum Community Forums
Community   »   Forums  
Member Login
StandardLiveID


Register
Forgot Password ?

Guests can view and read messages in the community forums, but you must register and log in to Deployment Forum before you can post messages. Click Register at the top of this page. Before posting messages, please read the forum guidelines at the bottom of this page.

Forums > Deployment Solutions > MDT 2008
Subject: Multisite deployment using MDT Database
Prev Next
You are not authorized to post a reply.

AuthorMessages
ThetruewebsterUser is Offline

Posts:10

Send Message
07/01/2009 9:13 AM  

As a heads up I have upgraded to 2010 beta 2, but the database and most of the major taks are very similiar as to 2008.

Previously in MDT 2008 I was using the location.xml method to deploy to 15 sites with DFS replicating my files around. The only problem was that there was a 10site limit in the XML file so I had to keep 2 WIM boot images current. It wasn't to much of a problem, just annoying.

So this time around I would like to use the database to pick my deployment server. I have been reading the literature but it just seems to keep picking what I have in my default location. I have my DB setup with 1 location in it. And I appear to be hitting the DB i have setup as well. At first I was trying to connect with a domain account but was getting authentication errors since it was using anonymous for some reason. So I setup a local SQL account and am using the ID and PW in the settings files.

Rochester, NY. Default gateway = 192.168.1.2

Here is my custom settings.ini

[Settings]
Priority=LSettings, Locations, LAdmins, MMApps, Default
Properties=MyCustomProperty

[LSettings]
SQLServer=SQL-DS10
DBID=MDTUser
DBPwd=********
Database=MDT
Netlib=DBMSSOCN
Table=LocationSettings
Parameters=DefaultGateway

[Locations]
SQLServer=SQL-DS10
DBID=MDTUser
DBPwd=***********
Database=MDT
Netlib=DBMSSOCN
Table=Locations
Parameters=DefaultGateway

[Rochester, NY]
DeployRoot=\\Production-Share\EndUser$

𖐸.168.1.2]
DeployRoot=\\Production-Share\EndUser$ 

[LAdmins]
SQLServer=SQL-DS10
DBID=MDTUser
DBPwd=**********
Database=MDT
Netlib=DBMSSOCN
Table=LocationAdministrators
Parameters=DefaultGateway

[MMApps]
SQLServer=SQL-DS10
DBID=MDTUser
DBPwd=***********
Database=MDT
Netlib=DBMSSOCN
Table=MakeModelApplications
Parameters=Make, Model
Order=Sequence

[Default]
OSInstall=Y
SkipAppsOnUpgrade=YES
SkipCapture=YES
SkipAdminPassword=YES
SkipProductKey=YES
DeployRoot=\\Fake-share-for-testing\EndUser$

***************

boot.ini

 

Settings]
Priority=LSettings, Locations, LAdmins, MMApps, Default
Properties=MyCustomProperty

[LSettings]
SQLServer=SQL-DS10
DBID=MDTUser
DBPwd=********
Database=MDT
Netlib=DBMSSOCN
Table=LocationSettings
Parameters=DefaultGateway

[Locations]
SQLServer=SQL-DS10
DBID=MDTUser
DBPwd=***********
Database=MDT
Netlib=DBMSSOCN
Table=Locations
Parameters=DefaultGateway

[Rochester, NY]
DeployRoot=\\Production-Share\EndUser$

𖐸.168.1.2]
DeployRoot=\\Production-Share\EndUser$ 

[LAdmins]
SQLServer=SQL-DS10
DBID=MDTUser
DBPwd=**********
Database=MDT
Netlib=DBMSSOCN
Table=LocationAdministrators
Parameters=DefaultGateway

[MMApps]
SQLServer=SQL-DS10
DBID=MDTUser
DBPwd=*************
Database=MDT
Netlib=DBMSSOCN
Table=MakeModelApplications
Parameters=Make, Model
Order=Sequence

[Default]
OSInstall=Y
SkipAppsOnUpgrade=YES
SkipCapture=YES
SkipAdminPassword=YES
SkipProductKey=YES
DeployRoot=\\Fake-share-for-testing\EndUser$


 

DietmarUser is Offline

Posts:205

Send Message
07/28/2009 4:18 AM  
I think what you miss is in the [Settings] part of CS.ini and Bootstrap.ini:

[Settings]
Priority=LSettings, Locations, LAdmins, DefaultGateway, MMApps, Default
Properties=MyCustomProperty

𖐸.168.1.2]
DeployRoot=\\Production-Share\EndUser$

Without this entry the scripts do not look for the part of the default gateway 𖐸.168.2.1]. I think you do not need the part [Rochester, NY].

Hope this helps! (Am I too late? Did you solve the problem?)
Dietmar
ThetruewebsterUser is Offline

Posts:10

Send Message
07/28/2009 1:55 PM  

thank you for the reply. That didn't get it either unfortunately.

I have found some other documentation and tried to update CS and Bootstrap with this but it is not working.

[Settings]
Priority=DefaultGateway, LSettings, Locations, LAdmins, MMApps, Default
Properties=MyCustomProperty

[DefaultGateway]
192.168.1.2=Rochester, NY

[Rochester, NY]
DeployRoot=\\MMCCLURE-XP\EndUser$
*********************************************

Any other thoughts?

ThetruewebsterUser is Offline

Posts:10

Send Message
07/29/2009 10:06 AM  
I think I just figured it out. I removed the DEPLOYROOT from the default and it is now using the gateway options.
Mark AllcockUser is Offline

Posts:380

Send Message
07/31/2009 7:29 AM  

What you should do with your BootStrap.ini is this (an example):

[Settings]
Priority=DefaultGateway,Default

[xxx.xxx.1.2]
DeployRoot=\\Server1\Share$

[xxx.xxx.2.2]
DeployRoot=\\Server2\Share$

[xxx.xxx.3.2]
DeployRoot=\\Server3\Share$

[Default]
OSInstall=Y
etc.......

Give this a go. Obviously I shouldn't have to mention about replacing the x's :D

Mark

DietmarUser is Offline

Posts:205

Send Message
08/05/2009 6:18 AM  
Sometimes I am confused: In the Microsoft Deployment Toolkit Reference on page 60 is no dot near Bootstrap.ini but CustomSettings.ini. But I believe Mark is right! The proof of the pudding is in the eating. :-))

This is what I found on internet (http://www.microsoft.com/technet/desktopdeployment/depprocess/bddscenaad_9.mspx)

[Settings]
…
Priority=MacAddress, DefaultGateway, Default
…
With all other values, this would cause the Zero Touch Installation rules engine to look for a section matching one of the default gateway values of the computer. However, with the DefaultGateway value, special processing is performed: the rules engine will check a DefaultGateway section to find the name of the real section that should be used.

[DefaultGateway]
192.168.0.1=HOUSTON
11.1.1.11=REDMOND
172.28.20.1=REDMOND
…
In this case, the "REDMOND" section would be used for two different default gateway values (11.1.1.11 and 172.28.20.1), while the "HOUSTON" section would be used for the third value (192.168.0.1). Location-specific packages can then be specified in those sections.

[REDMOND]
Packages1=XXX00004-Program name 4
Packages2=XXX00005-Program name 5

[HOUSTON]
Packages1=XXX00006-Program name 6
Packages2=XXX00007-Program name 7
Packages3=XXX00008-Program name 8


@Thetruewebster: I wonder why the priotity do not work. I never had problems with this.
Dietmar
Mark AllcockUser is Offline

Posts:380

Send Message
08/05/2009 7:19 AM  
Just to add to this one more time... There is yet another way you can achieve the same effect using the 'Subsection' method in the rules file. Using Dietmar's sample from above:

[Settings]
Priority=Location, Default

[Location]
Subsection=Subnet-%DefaultGateway%

[Subnet-192.168.0.1]
Packages1=XXX00004-Program name 4
Packages2=XXX00005-Program name 5

[Subnet-11.1.1.11]
Packages1=XXX00006-Program name 6
Packages2=XXX00007-Program name 7
Packages3=XXX00008-Program name 8

[Subnet-172.28.20.1]
Packages1=XXX00004-Program name 4
Packages2=XXX00005-Program name 5

Only problem with this solution is you'll have to double up on certain site which have more than one subnet (something that isn't an issue in Dietmar's example).

Phew! Talk about having a million different solutions for one problem!

Mark
You are not authorized to post a reply.
Forums > Deployment Solutions > MDT 2008 > Multisite deployment using MDT Database



ActiveForums 3.7
Forum Policies
Minimize

These forums are a user-supported community for IT professionals to exchange deployment tips, solutions, and techniques. For the benefit of all Deployment Forum members, please observe the following guidelines when posting to these forums:

  • We reserve the right to remove any message. Our moderators will remove all messages that are not respectful or productive. Profanity, racism, prejudice, and flaming are not tolerated.
  • Do not advertise products or services. Our moderators will remove all advertisements or service announcements. Product and service recommendations from active Deployment Forum members are encouraged, however.
  • Make sure your question isn't already answered. Before posting questions, search the forums. After ensuring that your questions are unique, post them to the most appropriate forum. This will help reduce noise in the forums.
  • Help make the most of each thread. Do not post unrelated messages to a thread. Also, if you've resolved a question outside of these forums, please share the solution with other members by posting it back to the thread.
  • Do not share confidential information. Confidential information includes product keys and addresses. Our moderators will edit any message containing confidential information, so double-check messages and their attachments before posting them.
  • Post messages using only the English language. For the benefit of all Deployment Forum members, please post your messages using the English language.

We hope that you enjoy using this community. Please submit your comments and feedback on the Comments and Feedback page or post them to the Comments, Feedback forum.
Privacy Statement  |  Terms Of Use
© 2007 Jerry Honeycutt