Windows IT Pro is the authoritative and independent resource for windows nt, windows 2000, windows 2003, windows xp. Features a collection of resources and magazines for windows IT professionals.
  
  
  Advanced Search 


July 2002

Using Qchain


RSS
Subscribe to Windows IT Pro | See More Hotfixes Articles Here | Reprints | Or get the Monthly Online Pass—only $5.95 a month!
Main Article    Managing Security Hotfixes

Download the Code Here

Microsoft released qchain.exe in 2001. This utility, which works with Windows 2000 and Windows NT, lets you chain hotfixes (i.e., install multiple hotfixes one after another without having to reboot in between). In the past, chaining was difficult because you had to install fixes in a specific order so that the update procedure wouldn't overwrite new system files with earlier versions. The problem with chaining was that the last hotfix applied "won." To address that problem, Qchain manages the file-replacement process by recording files in the registry's Pending File Rename queue. Qchain analyzes the contents of the Pending File Rename subkey and applies only the most current version of the files of all applied patches.

Listing A shows sample code that illustrates how to use Qchain in a script to deploy hotfixes. The first three lines of the sample script apply three hotfixes. The -z switch applies the hotfix without rebooting; -m applies the hotfix in unattended mode, without administrative intervention; and -q applies the hotfix in quiet mode, hiding the extract and copy actions that take place. If you're applying patches manually, you might want to leave out the -q switch to view the progress of the hotfix.

The fourth line in the script runs Qchain and specifies a file in which to log Qchain's results. The sample code puts the log file in the Logs directory on a server named Fschicago and specifies a unique filename based on the computer name and the date the script ran. Because you're likely to run Qchain at a later date, a unique log name prevents you from overwriting older logs. Finally, the Shutdown utility (from the Microsoft Windows 2000 Server Resource Kit or the Microsoft Windows NT Server Resource Kit) performs a local reboot of the machine by using the /l and /r switches. The /l switch performs a logoff; the /r switch performs a clean shutdown and a restart.

End of Article



Reader Comments

You must log on before posting a comment.

If you don't have a username & password, please register now.




Top Viewed ArticlesView all articles
Friday at PASS Europe 2006

Kevin talks about the closing day of the event and shares a funny Microsoft film. ...

PsExec

This freeware utility lets you execute processes on a remote system and redirect output to the local system. ...

Escape From Yesterworld

Kevin points you to the funniest SQL Server website ever! ...


Windows OSs Whitepapers Why SaaS is the Right Solution for Log Management

Related Events Windows, Unix, Linux Interoperability

Check out our list of Free Email Newsletters!

Windows OSs eBooks Understanding and Leveraging Code Signing Technologies

A Guide to Windows Certification and Public Keys

SQL Server Administration for Oracle DBAs

Related Windows OSs Resources Become a VIP member of the Windows IT Pro community!
Get it all with the VIP CD and VIP access. A $500+ value for only $279!

Subscribe to Windows IT Pro!
Solve your toughest technical problems with our experts and access 10,000 + articles online. 30% off

Monthly Online Pass - Only $5.95!
Get instant access to 10,000+ articles from Windows IT Pro Magazine!

TechNet Virtual Labs
Evaluate and test Microsoft's newest products.


Windows IT Pro Home Register FAQ for Windows WinInfo News
Europe Edition About Us Contact Us/Customer Service Media Kit Affiliates / Licensing  
SQL Server Magazine Office & SharePoint Pro Windows Dev Pro IT Job Hound ITTV
IT Library Technology Resource Directory Connected Home Windows Excavator Windows SuperSite 
 
 Windows IT Pro is a Division of Penton Media Inc.
 Copyright © 2008 Penton Media, Inc., All rights reserved. Terms and Use | Privacy Statement | Reprints and Licensing