/bundles/itninjaweb/img/Breadcrumb_cap_w.png

Blog Posts tagged with Hardware

Ask a question

Add a Network Printer via a script

The script below will allow end users to be able to add their own network printer via a automated script.

The script will also prompt the end user if they would like to make it the default printer and it will make this change for them.

On error resume next
Set WshNetwork = CreateObject("WScript.Network")

Dim PrinterName
Dim PrinterDriver
Dim strServer

'Change these for each printer
PrinterName = "Xerox4595"
PrinterDriver = "Xerox 4595 PS"
strServer = "\\YourPrinterLocation\"

StrApp = "Printer Status"

Add_Printer

Sub Add_Printer


msgbox "This program will add the following printer: " & PrinterName & vbcrlf &_
"After choosing OK it may take about a minute for the printer driver to load.", vbokonly + 4096, "Add Printers"


PrinterPath = strServer & PrinterName
WshNetwork.AddWindowsPrinterConnection PrinterPath, PrinterDriver
MsgBox "The following Network Printer has been added: " &_
vbCrLf & PrinterName,vbOKOnly + 4096, "Printer Status"


input =  msgbox ("Would you like to set " & PrinterName & " as your default Printer?", vbyesno + 4096, strApp)
'msgbox input 'for testing

 if input = "6" then
  printer = strServer & PrinterName
 
  WshNetwork.SetDefaultPrinter printer
 
  MsgBox "Your default printer has been successfully set to: " & PrinterName, _
     vbOKOnly + vbInformation + 4096, StrApp
 End if
 
 if input = "7" then
  Wscript.quit
 end if
 
End sub

View comments (1)

HOW TO: Get an alert in case of Inventory Changes on the Kace K1000

There is no real time alert, but we can schedule for a report to be sent out regularly.

 

 

select ASSET_HISTORY.TIME, ASSET.NAME, ASSET_HISTORY.DESCRIPTION

from ASSET

left join ASSET_TYPE on ASSET.ASSET_TYPE_ID = ASSET_TYPE.ID

left join ASSET_HISTORY on ASSET.ID = ASSET_HISTORY.ASSET_ID

where

(ASSET_TYPE.ID = 5

and NOW() < DATE_ADD(ASSET_HISTORY.TIME, INTERVAL 60 DAY)

and ASSET_HISTORY.DESCRIPTION not like '%KB%'

and ASSET_HISTORY.DESCRIPTION not like '%reboot%')

and

(ASSET_HISTORY.DESCRIPTION like 'Found software item%'

or ASSET_HISTORY.DESCRIPTION like '%remove%'

or ASSET_HISTORY.DESCRIPTION like '%change%')

order by TIME DESC

 

 

this one for hardware only.

 

 

select ASSET_HISTORY.TIME, ASSET.NAME, ASSET_HISTORY.DESCRIPTION

from ASSET

left join ASSET_TYPE on ASSET.ASSET_TYPE_ID = ASSET_TYPE.ID

left join ASSET_HISTORY on ASSET.ID = ASSET_HISTORY.ASSET_ID

where

(ASSET_TYPE.ID = 5

and NOW() < DATE_ADD(ASSET_HISTORY.TIME, INTERVAL 60 DAY)

and ASSET_HISTORY.DESCRIPTION not like '%KB%'

and ASSET_HISTORY.DESCRIPTION not like '%reboot%' )

and

(ASSET_HISTORY.DESCRIPTION like 'video controllers changed from%'

or ASSET_HISTORY.DESCRIPTION like 'mac changed from%'

or ASSET_HISTORY.DESCRIPTION like 'processor changed from%'

or ASSET_HISTORY.DESCRIPTION like 'ram total changed from%'

or ASSET_HISTORY.DESCRIPTION like 'registry max size changed from%'

or ASSET_HISTORY.DESCRIPTION like 'ip changed from%'

or ASSET_HISTORY.DESCRIPTION like 'cd devices changed from%'

or (ASSET_HISTORY.DESCRIPTION like '%changed from%' and ASSET_HISTORY.DESCRIPTION like '%disk%')

or (ASSET_HISTORY.DESCRIPTION like '%changed from%' and ASSET_HISTORY.DESCRIPTION like '%bios%')

or (ASSET_HISTORY.DESCRIPTION like '%changed from%' and ASSET_HISTORY.DESCRIPTION like '%ram%')

)

order by TIME DESC

 

and this is for software changes only.

 

select ASSET_HISTORY.TIME, ASSET.NAME, ASSET_HISTORY.DESCRIPTION

from ASSET

left join ASSET_TYPE on ASSET.ASSET_TYPE_ID = ASSET_TYPE.ID

left join ASSET_HISTORY on ASSET.ID = ASSET_HISTORY.ASSET_ID

where

(ASSET_TYPE.ID = 5

and NOW() < DATE_ADD(ASSET_HISTORY.TIME, INTERVAL 60 DAY)

and ASSET_HISTORY.DESCRIPTION not like '%KB%'

and ASSET_HISTORY.DESCRIPTION not like '%reboot%'

and ASSET_HISTORY.DESCRIPTION not like '%mac%'

and ASSET_HISTORY.DESCRIPTION not like '%user%'

and ASSET_HISTORY.DESCRIPTION not like '%ip changed%'

and ASSET_HISTORY.DESCRIPTION not like '%video controller%'

and ASSET_HISTORY.DESCRIPTION not like '%domain changed%'

and ASSET_HISTORY.DESCRIPTION not like '%ram total changed%'

and ASSET_HISTORY.DESCRIPTION not like '%registry max size%'

and ASSET_HISTORY.DESCRIPTION not like '%name%')

and

(ASSET_HISTORY.DESCRIPTION like 'Found%'

or ASSET_HISTORY.DESCRIPTION like '%remove%'

or ASSET_HISTORY.DESCRIPTION like '%change%')

order by TIME DESC

View comments (6)

How to prevent tickets from reopening when machines are deleted from inventory

The Service Desk ticketing system is, by default, associated with the Inventory section of the KBOX. This
becomes a problem for when customers need to remove inventoried items based on system refresh,
license availability or decommission purposes. The problem is if an item in inventory is removed, tickets
associated with these systems automatically reopen, causing a ruckus of email attention to agents
assigned to these systems in the past. The way to avoid this problem is to change the association
between the Service Desk and the rest of the KBOX by associating with Assets and not Inventory. To do
this, follow these steps:

  1. Navigate to Inventory>select system listed and scroll to bottom and expand asset information.

  2. Choose edit this asset and click Save. Make sure it lists asset detail information for the system.

  3. Next, associate the help desk to the assets instead of the default association for inventory.
    Help Desk>Configuration>queues>select each queue required>Customize Field and Layouts.
  4. Scroll down to Ticket Layout - label Machine as Hidden under Permissions.






  5. Then go to an available custom field. (example: custom_1). Give it the 'Machine' name and give it the
    same permissions you had set for the original Machine name. Save.

  6. Then scroll down to Custom Fields and choose the exact same custom field as in Tticket Layout. (example:
    custom_1). Field type=single select.

For Select Values, put in a query to for the location of the computer assets and then save. The most common query provided is:

query: SELECT ASSET.NAME FROM ASSET LEFT JOIN ASSET_TYPE on
ASSET.ASSET_TYPE_ID=ASSET_TYPE.ID WHERE ASSET_TYPE.NAME='computer'

Once established, any system inventoried after the fact will not generate a reopening of a ticket if ever deleted.  If an inventory of systems is already established and a Help Desk has been present, a machine deletion will only trigger tickets created prior to the above procedure to reopen.  

IMPORTANT:

IF the KBOX is setup with ORGs then the query will need to reflect the ORG it is in.

This process may strip computer information from the closed tickets.  If this is a problem, run a report of all systems currently associated to gain system information prior to following these steps.

View comments (3)

Not a Big Fan of Optiplex 760 so Far. 0_o

Someone come in here and tell me that I shouldn't be so very angry at this particular computer model. I know computers aren't sentient (yet), but my first interactions with this computer have not been pleasant. Initially it seems that the system can't handle Windows 7 without a BIOS update (machine came refurbished with A02 BIOS, the current version is A13), and so I put together a Vista PE environment to try to update the BIOS, and now it is having issues installing this updated BIOS. I have tried repeatadly with the same error.

See:
http://itninja.com/question/update-dell-optiplex-760-bios

http://itninja.com/question/optiplex-760-has-very-strange-slow-behavior


Out of vengeance I was able to update the BIOS of a Optiplex 740 with no issue at all. Ugh. 

 

View comments (3)

FAQ: Information about Driver Install Frameworks Tools

 

This article provides answers to frequently asked questions about Driver Install Frameworks (DIFx) tools, which simplify installation of driver packages and eliminate most end-user manual steps for installing a driver.

This information applies for the following operating systems:
Windows Server 2008 R2
Windows 7
Windows Server 2008
Windows Vista
Windows Server 2003
Windows XP
Windows 2000

On This Page

 General Issues General Issues
 Driver Package Installer (DPInst) Driver Package Installer (DPInst)
 Driver Install Frameworks for Applications Driver Install Frameworks for Applications

 

General Issues

What are the currently available Driver Install Frameworks Tools?

The following tools are currently available:

  • Driver Install Frameworks for Applications (DIFxApp)

  • Driver Package Installer (DPInst)

  • Driver Install Frameworks API (DIFxAPI)

Where can I find the DIFx tools?

The most recent version of the DIFx tools is included in the latest release of the WDK.

How do I get help with the DIFx Tools?

What is DIFxAPI?

The Driver Install Frameworks API (DIFxAPI) exposes functions for preinstalling, installing, and uninstalling driver packages that meet DIFx requirements; associating driver packages with applications when the package is installed; logging events that are related to preinstallation, installation, and uninstallation; and retrieving the INF file path for a preinstalled driver package from the driver store.

Can I redistribute DPInst , DIFxApp, and DIFxAPI?

You may redistribute these tools as described in the license agreement that ships with the tools.

Can I use InstallShield or Wise with DIFx Tools?

Do DPInst and DIFxApp support 64-bit drivers?

The DIFx tools support drivers for x86-based systems, x64-based systems, and Itanium-based systems.

Are signed drivers required with DPInst and DIFxApp?

These tools do not explicitly require your drivers to be signed. However, we recommend driver signing as a way to increase the reliability and stability of the operation system. You can sign drivers through two methods:

How do I disable the signing requirement?

By default, DPInst allows only signed drivers to be installed and requires that all of the files that are listed in the INF for copying are actually present. To disable this mode and apply the driver-signing policy that is in effect for the operating system on the target system, use one of the following:

  • < legacyMode /> line in the XML file

  • /lm command line switch

This switch disables the additional Windows Vista and Windows Server 2008 requirements that are built into DPInst and enables vendors who are shipping drivers only for Windows 2000, Windows XP, or Windows Server 2003 to take advantage of DPInst. Unsigned drivers are accepted and installed according to the policy setting for the underlying operating system. INFs that reference files that cannot be found in the source media generate only a warning in the log without causing the installation to fail.

How do I disable the requirement for signed drivers for testing purposes?

To do this, attach a kernel debugger to the system and set the _DFX_INSTALL_UNSIGNED_DRIVER environment variable to 1.

When this variable is set, DPInst does not verify that the package is signed and does not check for the presence of a catalog file for the package.

This option has been kept for backward compatibility. The legacy mode flag that was described earlier on this page is the recommended way to disable the requirement for signed drivers.

What if my customer adds my hardware before installing my software?

The Windows PnP manager searches for a driver that is compatible with your hardware. If the Windows PnP manager finds a driver that is compatible with your hardware, that driver is installed automatically. In this situation, when your customer installs your software, the DIFx tools check to determine whether your driver is a better match for your device than the driver that was previously installed. If your driver is a better match than the previously installed driver, the DIFx tools update the driver to your driver.

Note that DPInst and DIFxApp both have an optional flag that forces the driver to be updated to your driver regardless of whether it is a better match for your device. However, this flag works only in quiet installation mode. If this flag is used, the DIFx tools always update the driver to your driver.

If the Windows PnP manager does not find a driver that is compatible with your hardware, the DIFx tools install your driver for the device when your customer installs your software.

Is localization supported in version 2.0 of the tools?

Yes. Starting with Version 1.1 of the DIFx tools, these applications are localized to support 22 languages. The languages are:

Chinese (People's Republic of China) Italian (Italy)
Chinese (Taiwan) Japanese (Japan)
Czech (Czech Republic) Korean (Korea)
Danish (Denmark) Norwegian (Bokmål) (Norway)
German (Germany) Dutch (Netherlands)
Greek (Greece) Polish (Poland)
English (United States) Portuguese (Brazil)
Spanish - Modern Sort (Spain) Portuguese (Portugal)
Finnish (Finland) Russian (Russia)
French (France) Swedish (Sweden)
Hebrew (Israel) Turkish (Turkey)

 

DPInst 1.0 and DIFxApp 1.0 do not support localization.

Can I Use DPInst, DIFxApp, and DIFxAPI on Windows Vista or Windows 7?

Yes. DPInst, DPFxApp, and DIFxAPI can be used on Windows Vista and Windows 7.

Driver Package Installer (DPInst)

How can I use DPInst to silently deploy drivers in my enterprise?

DPInst supports quiet installation through the /q (quiet) flag on the command line or the <quietInstall/> line in the XML file.

The quietInstall flag works in combination with the presence of an end-user license agreement (EULA) page and the suppressEulaPage flag. If the XML files require a EULA and the EULA is not suppressed, the quiet installation will become a wizard-guided installation.

For more information, see Driver Package Installer (DPInst).

Do DPInst and DIFxApp update phantom devices?

Yes, they update phantom devices.

Can I use DPInst from my setup to remove a driver during the setup uninstallation routine?

The current version of DPInst supports uninstallation of a driver package through the /u (uninstall) flag on the command line.

Driver Install Frameworks for Applications

I use InstallShield in my installation package. Can I still use DIFxApp?

Yes, InstallShield works with DIFXApp. For more information, check the InstallShield Web site.

Can I suppress the "plug in hardware" prompt from the MsiCleanupOnSuccess function of DIFxApp?

Currently the only way to suppress this prompt is to opt for a silent installation by using the /q switch with Msiexec. However, that also suppresses any other dialog box that could appear during the installation. In a silent installation, if DIFxApp encounters a code path where it cannot proceed without showing UI, it fails.

For example, DIFxApp cannot proceed without showing UI if DIFxApp needs to display an unsigned driver prompt. This is a critical prompt, and during a silent installation DIFxApp fails because it cannot display the prompt.

However, as another example, DIFxApp can proceed if a request for the "Plug in hardware" prompt occurs. The "Plug in hardware" prompt is not a critical prompt, so DIFxApp just suppresses it and continues during a silent installation.

Does the message at the end of installation that cautions that the hardware is unplugged actually scan for hardware IDs? Or does this message just assume that the hardware isn't plugged in because a "software first" installation has just completed?

DIFxApp checks to determine whether the hardware is connected.

Is the message that advises users to plug in the hardware controlled by a public property? Can I opt to avoid this pop-up message during a full UI installation and display my own custom dialog box?

Unfortunately, you cannot replace this pop-up message with a custom dialog box.

Be the first to comment
Showing 1 - 5 of 48 results

Top Contributors

Talk About Asset Management