How to Make the Provisioning Services Server Client Coexist with Third-party Network Drivers

How to Make the Provisioning Services Server Client Coexist with Third-party Network Drivers

book

Article ID: CTX117395

calendar_today

Updated On:

Description

This article describes how to run the Provisioning Server client on a target device along with third-party network applications that also occupy the network device driver stack.

Background

In the Windows Driver Model (WDM), systems manage a device through a linked stack of layered device drivers. The driver stack might consist of the device manufacturer-provided function driver and the third-party-provided filter drivers, which enhance the device's functions. Interference might occur among the drivers when more than one third-party drivers are installed on the stack. This is because each of the drivers can be installed with no knowledge of the others. Also, the interference can be caused by the order of driver presence on the stack or by registry settings that conflict among the products.

To minimize such possibilities, the Provisioning Server client's filter driver has been implemented as a standard Network Driver Interface Specification (NDIS) intermediate driver, sitting between an NDIS protocol driver and NDIS Network Interface Card (NIC) driver on the network device driver stack. To the upper protocol driver it presents an interface that looks like an NDIS NIC driver, while to the lower NIC driver it looks like a standard NDIS protocol driver. Thus, it should be able to function with other drivers that support the standard NDIS interface.

However, exceptions do exist if the other product does not fully conform to the standard or requires a special configuration right above the NIC driver. The Provisioning Server client might not work properly in such situations. Typical examples include (but are not limited to) some antivirus software and Virtual Private Networking (VPN) software. In such cases, vary the installation order to work around the possible interference.


Instructions

Note: Citrix recommends installing the third-party product before installing the Provisioning Server client in most cases. If this is not successful, you might have to reverse the installation order.

Complete the following steps on the master target device before creating the virtual disk image:

  1. Install the third-party software which must coexist with the Provisioning Server client.

  2. Restart the computer, if necessary.

  3. Install the Provisioning Server client software.

  4. Restart the computer.

  5. Run the image builder to create the virtual disk image.

  6. Boot up in Private Image Mode and confirm the target device and third-party product are working.

Issue/Introduction

This article describes how to run the Provisioning Server client on a target device along with third-party network applications that also occupy the network device driver stack.

Additional Information

Citrix Documentation - Requirements and considerations for manufacturer's NIC teaming