But it doesn't work. Only the values with DHCPScopes0... are processed. The ones prefixed with DHCPScopes1... are ignored.
From: [email protected] [mailto:[email protected]] On Behalf Of Chris Nackers Sent: Friday, October 04, 2013 12:54 PM To: [email protected] Subject: RE: [MDT-OSD] RE: MDT2012 - CustomSettings.ini and DHCPScopes Ok, so you are incrementing the values, assuming it accepts them, that should work... Could be 001 vs 1 maybe? Chris Nackers Microsoft MVP - Enterprise Client Management Email: [email protected]<mailto:[email protected]> Nackers Consulting Services, LLC From: [email protected] [mailto:[email protected]] On Behalf Of Marable, Mike Sent: Friday, October 04, 2013 11:08 AM To: '[email protected]' Subject: RE: [MDT-OSD] RE: MDT2012 - CustomSettings.ini and DHCPScopes I used to, but I stumbled on the DHCP scope options in CS.ini and that just seemed "cleaner". Using the built-in functionality of MDT looked like a better solution. The documentation I've found online says that variable "DHCPScopes" is used to define the number of scopes. Then (and here is where I could be wrong) the different "DHCPScopes#...." options would be used to define the options for each scope. "DHCPScopes0..." would be the first scope and then "DHCPScopes1..." would be the second. Mike From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of CESAR.ABREG0 . Sent: Friday, October 04, 2013 11:45 AM To: [email protected]<mailto:[email protected]> Subject: Re: [MDT-OSD] RE: MDT2012 - CustomSettings.ini and DHCPScopes Have you tried scripting them? http://www.windowsnetworking.com/kbase/WindowsTips/WindowsServer2008/AdminTips/Network/CreatingaDHCPScopeusingaBatchFile.html On Fri, Oct 4, 2013 at 7:59 AM, Chris Nackers <[email protected]<mailto:[email protected]>> wrote: The scope variables are first value set wins... Chris Nackers Microsoft MVP - Enterprise Client Management Email: [email protected]<mailto:[email protected]> Nackers Consulting Services, LLC From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Marable, Mike Sent: Friday, October 04, 2013 9:48 AM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] MDT2012 - CustomSettings.ini and DHCPScopes I'm working on expanding my lab build-out using MDT. I'm trying to set up the DHCP server with 2 scopes. I define the first DHCP scope in CustomSettings and it worked fine. But when I try to add the second scope the build completes but only the first scope is present. I'm sure I have to be overlooking something simple. Here is the snippet of the CS.ini ; DHCP Configuration DHCPServerOptionRouter=192.168.1.1 DHCPServerOptionDNSServer=192.168.1.2 DHCPServerOptionDNSDomainName=demo.lab DHCPScopes0SubnetMask=255.255.255.0 DHCPScopes0IP=192.168.1.0 DHCPScopes0Name=192.168.1.0/24<http://192.168.1.0/24> DHCPScopes0StartIP=192.168.1.100 DHCPScopes0EndIP=192.168.1.150 DHCPScopes0OptionLease=691200 DHCPScopes1SubnetMask=255.255.255.0 DHCPScopes1IP=192.168.2.0 DHCPScopes1Name=192.168.2.0/24<http://192.168.2.0/24> DHCPScopes1StartIP=192.168.2.100 DHCPScopes1EndIP=192.168.2.150 DHCPScopes1OptionLease=691200 DHCPScopes=2 What am I missing? Thanks Mike Marable Application Programmer/Analyst Lead Enterprise Device Engineering and Management MCTS, MCITP, MCSA [Profile<https://www.mcpvirtualbusinesscard.com/VBCServer/MikeMarable/profile>] -------------------------------------------- "The difficult we do at once. The impossible takes a little longer." -US Army Corps of Engineers [Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: win7logoTiny] UMHS Windows 7 Everywhere by December 2013<https://processmgt.mcit.med.umich.edu/sites/mcit/customer/applicationsoftware/Pages/Windows7.aspx> ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
<<inline: image001.png>>
