I recently implemented a SCCM OSD solution for a customer who did not have DHCP in place in their environment. The no-dhcp policy was not open for negotiation, so I had to deal with the fact that the IP addresses had to be configured as OSDVariables during deployment.
To make matters worse, all servers had six network cards installed. Some of theese where going to be using four cards, some would use two cards in teams and some would use all six cards -all connected to different networks.
I did consider expanding the MDT2010 database to be able to define OSDAdapter1, OSDAdapter2 and so on but since that would be the only real use for the MDT database in this scenario, I decided to keep all tasks within the configuration manager console and not introduce the customer to an additional product. Thankfully there was not a large amount of servers that were to be set up this way.
I created one collection for each of the server-roles network configurations and inserted the OSDAdapter0DefaultGateway variable and its corresponding value. Then I inserted variables for OSDAdapter_EnableDHCP “false”, OSDAdapter_SubnetMask for each network card. Finaly I inserted the OSDAdapterCount variable with the value 6. This way membership in the correct Collection would ensure the correct network settings were applied to the server during the Windows OS install phase of the Task Sequence.
To do this, create a collection and right click it and select “modify collection Settings”.