Monday, August 18, 2014

Apply Network Settings in a task sequence - Part 2

Part 1: http://larslohmann.blogspot.dk/2014/08/apply-network-settings-in-task-sequence_11.html

Part 2: This one

Part 3: Will be available later

Part 4: Will be available later

OSDAdapter0EnableDHCP

Set this to True to enable Dynamic Host Configuration Protocol (DHCP) for the adapter (obtain an IP address automatically). Setting it to False will disable DHCP (Use the following IP address).

Result in Windows:

image

Task Sequence example:

OSDAdapter0EnableDHCP=False

image

OSDAdapter0IPAddressList

Comma-delimited list of IP addresses for the adapter. This property is ignored unless EnableDHCP is set to false. If you enter two subnet masks you must also enter two IP addresses.

OSDAdapter0IPAddressList and OSDAdapter0SubnetMask must therefor match in numbers if this is not the case you will get error 0x8000FFFF.

image

image

Result in Windows (one IP address and subnet mask used):

image

Task Sequence example (one IP address and subnet mask used):

OSDAdapter0IPAddressList=10.10.10.209

image

Result in Windows (two IP addresses and subnet masks used):

image

Task Sequence example (two IP addresses and subnet masks used):

OSDAdapter0IPAddressList=10.10.10.220,10.10.10.230

image

OSDAdapter0SubnetMask

Comma-delimited list of subnet masks. This property is ignored unless EnableDHCP is set to false. If you enter two IP addresses you must also enter two subnet masks.

OSDAdapter0IPAddressList and OSDAdapter0SubnetMask must therefor match in numbers.

Result in Windows (one subnet mask an IP address used) :

image

Task Sequence example (one subnet mask an IP address used):

OSDAdapter0SubnetMask=255.255.255.0

image

Result in Windows (two subnet masks and IP addresses used) :

image

Task Sequence example (two subnet masks and IP addresses used) :

OSDAdapter0SubnetMask=255.255.255.128,255.255.255.128

image

OSDAdapter0Gateways

Comma-delimited list of IP gateway addresses. This property is ignored unless EnableDHCP is set to false. I will ignore that we are able to add more than one gateway in this example.

Result in Windows:

image

Task Sequence example:

OSDAdapter0Gateways=10.10.10.1

image

 

Stay tuned for part 3.

Monday, August 11, 2014

Apply Network Settings in a task sequence - Part 1

This is the first post were I will take a closer look at the variables available to set network card settings in a task sequence.

The variables are available both in MDT and in plain SCCM OSD, they can be set in many places, for example directly in the task sequence, as variable set on the computer or a collection, in MDT customsettings.INI, in the MDT database, by a script and more.

Here is an example were a variable is set on the SCCM collection:

image

The first thing we need to be aware of is that all variables are indexed with the number of the NIC in question, in the easiest example with only one NIC in action the variables will all start with OSDAdapter0 to identify the first (and only) NIC.

If working with for example 2 network cards we will need variables starting with OSDAdapter0 for the first and OSDAdapter1 for the second, and so it continues.

We can easily find the actually number of adapters in the computer using WMI (Win32_NetworkAdapterConfiguration).

Please note that in order for standalone MDT to work with more than one NIC specified in customsettings.ini, you need to add the variables for OSDAdapter1.. to ZTIGather.xml (only OSDAdapter0 has been pre defined).

Another importing thing is that all NIC you want to configure using variables, must have link active or some settings won’t work.

I will assume only one NIC in all examples.

You will be able to find all network variables available here http://technet.microsoft.com/en-us/library/hh273365.aspx (Apply Network Settings Task Sequence Action Variables).

Before we can start setting the different values, we also need to be aware of the variable OSDAdapterCount, this variable should be set to the number of network cards in the computer so in this example one.

If you don’t set OSDAdapterCount all the other OSDAdapter values we set will be ignored, so remember this value!

All OSDAdapter values must be defined before the task sequence step Apply Network Settings if you set them directly in the task sequence.

image

So now we should be ready to start setting some real network options, stay tuned for part 2.

Monday, August 4, 2014

0x41301 as result of a scheduled task

when running a scheduled task you might get the error 0x41301

image

This error simply means that the  task is still running, this might indicate that there is a problem with the task and that it never ends, or that you must be a bit more patience.

Monday, July 28, 2014

Speed up loading the PXE boot image on SCCM 2012 R2

When loading the WINPE boot image with PXE from your distribution point, you might be able to speed up the boot time by increasing the TFTP block size.

In my test scenario the boot time was one minute faster after the change, and this is often a part of the OSD installation where we are actively waiting, so faster boot time are more than welcome.

On the Distribution point with PXE support find the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\DP

Create a new DWORD value RamDiskTFTPBlockSize and use the values 4096, 8192 or 16384 depending on what gives you the best performance in tests.

Start with the value 16384 decimal.

image

image

After changing/adding the value restart Windows Deployment Services Server.

image

And then test to see if the boot time is faster.

image

Please note that you might find older hardware that wont work with larger TFTP block sizes, so test carefully.