Monthly Archives: June 2011

Why did Windows 7 pick THAT driver ?


Today I stumbled against the following Blog. Which perfectly answers one important question of my (and my customers) .

“How do make Windows pick the correct driver?”

The secret behind this is called ranking, ranking occurs when drivers are added to the driver store and that happens of course when we deploy a new Windows 7 machine and drivers are injected. When using MDT in a LiteTouch configuration, the LiteTouch script will do a Plug and Play scanning of the hardware and the use the information the get the correct drivers from the MDT out-of box drivers folder. Now, MDT cant really “know” if that particular driver is the perfect driver so it will copy all drivers to the \Drivers folder on the machine to be deployed. But if you use Driver Groups or any other method that will “filter” the drivers the script would then only copy the one and only driver need.

Well that’s in the perfect word and since that does not exist we will get multiple drivers copied down to the \Drivers folder and then when MDT (using DISM in a offline mode) pushes those drivers into the OS there will be scenarios when we are going to have drivers that have the same PNP number and Windows must choose the correct one and now its time for ranking. In the best of worlds, when all the vendors created perfect drivers and everyone is always running the latest and the greatest this would not be a problem. But in the reality not all vendors have a perfect .inf file, in fact some of them are uglier then others and they does not even work.

Before we go into details on how that work, you might want to know how to “see” this, well that is not a secret there is of course a log file for that and the logical name for that is c:\Windows\inf\ and here is a sample where it just happens to be two drivers to pick from: (This log files has been modified and shortened just to show you)

Original and full Source:


SCA Advanced Client Deployment SCCM 2007

Deploy System Center Advisor

The System Center Advisor environment consists of a web service and on-premise software (a gateway to communicate with the service, and one or more agents to collect and analyze data). Perform the following steps to deploy Advisor in your environment:

  1. Review the System Center Advisor System Requirements.
  2. Read the Planning Considerations for System Center Advisor to build a topology that matches your environment. If you have a firewall in your environment, review the Firewall Information for System Center Advisor.
  3. Create an Account and Download the On-Premise Softwareand download the gateway and agent setup wizard.
  4. Install the gateway and agent. Use one of the following methods:
  5. Register a gateway(if this did not occur during gateway installation).
  6. Authorize Agents to Access the Gatewayif you choose to limit access to the gateway during gateway installation.
  7. Configure the Gateway and Agent. (Optional)
  8. If you run into any issues, review Advisor Deployment Troubleshooting.

I completed the first 3 steps.

I was wondering how I could speed up the agent deployment to the whole environment. We have configuration Manager 2007. The SCA documentation states we can install the agent using command line.

Lets deploy the SCA On-Premise software Using SCCM 2007.

  1. Create a configuration Manager Package.
    The data source contains the on-Premise software.
    The Certificate is stored on a network Share: \share\RegistrationCert.pfx”>\\<server>\share\RegistrationCert.pfximage
  2. Do not forget to copy the package to your distribution points.
  3. Create packages
    1. Install Advisor Agent Silent No Reboot

    Install SCA Agent silent no reboot with installation logs in c:\temp\advisorLog.txt using <Gatewayserver FQDN> as gateway.

    Command Line:
    AdvisorSetup.exe “/l*v c:\temp\AdvisorLog.txt /qn INSTALL_AGENT=YES GATEWAY_SERVER=<SERVER FQDN>”


  5. Install Gateway Agent Silent No reboot

    Install SCA gateway silent no reboot with installation logs in c:\temp\advisorLog.txt. Certificate is placed on a dedicated share.

    Command Line:
    AdvisorSetup.exe “/l*v c:\temp\AdvisorLog.txt /qn INSTALL_GATEWAY=YES REG_CERT_PATH=\\<file server\Advisor_sources\Certificates\RegistrationCert.pfx”


  • Create Advertisements to deploy the agent / Gateway
    I deployed the agent to scom1.vbox.local and the gateway to SCSM1.vbox.local
  • Open and check the servers page. All targeted servers should appear within 24 h.
  • All System Center Advisor Install parameters

    System Center Advisor Usage

    C:\> AdvisorSetup.exe /?

    Installs System Center Advisor.

    AdvisorSetup.exe [MSIstring=] [/?]

    MSIstring= A string of MSI installation parameters, enclosed in quotes. This string can include standard MSI parameters, such as /qb as well as custom properties specific to Advisor. For standard MSI parameters, type MSIexec.exe /? You can specify the following custom installation parameters for Advisor by setting [PROPERTY=value].

    • INSTALL_AGENT Indicates whether to install the agent. Value can be either YES or NO.
    • INSTALL_GATEWAY Indicates whether to install the gateway. Value can be either YES or NO.
    • INSTALL_LOCATION A string that identifies the installation directory. If no directory is specified, the default is %programfiles%\System Center Advisor.
    • REG_CERT_PATH A string that identifies the directory where the registration certificate is located.
    • PROXY_SERVER A string that identifies the DNS name for the proxy server the gateway should use to access the Internet. If you specify this parameter, you must also specify the PROXY_PORT.
    • PROXY_PORT An integer that identifies the port for the proxy server. If you specify this parameter, you must also specify the
    • GATEWAY_SERVER A string that identifies the DNS name of the gateway server that the agent will use.
    • DO_NOT_REGISTER Instructs setup to skip registration of the gateway. Value can be either YES or NO.
    • SECURE_AGENT_ACCESS Determines whether to restrict access to the gateway to pre-authorized agents only. Value can be either YES or NO.

SCOM R2 Admin Resource Kit Available


The System Center Operation Manager 2007 Administration Resource Kit provides the following features to aid in management group administration:

  • Scheduled Maintenance Mode – Ability to schedule and manage maintenance mode in the management group.
  • Clean Mom – Helps remove all installed R2 components.
  • MP Event Analyzer – MP Event Analyzer tool is designed to help a user with functional and exploratory testing and debugging of event based management pack workflows like rules and monitors.

Feature Summary:

  • Ability to schedule Maintenance mode for “run once”, daily, weekly, and monthly schedules
  • Ability to removal all OpsMgr 2007 R2 files from a system
  • Ability to debug event based management pack workflows


System Requirements

  • Supported Operating Systems:Windows Server 2008;Windows Server 2008 R2;Windows Server 2008 R2 SP1;Windows Server 2008 Service Pack 2
  • Other Software:System Center Operations Manager 2007 R2


  1. Download and unpack the binaries
  2. Open the Schedule Maintenance Mode v1.3 document and follow the instructions.

Original source:

You can Download here: