Handy Software Lab Products FAQ

This paper provides system administrators with the best practices for configuring Point and Print security on Windows Vista client computers in environments where print servers and client computers might have different versions of Windows.

This white paper explains many of the print features delivered with Windows 2003 that help ensure enterprise-grade reliability, manageability, security, and agility for print services.

The printing subsystem was among the many areas of Windows 2000 and Windows Server 2003 that substantially changed from previous versions of Windows NT. This document describes the Point and Print feature, which lets users print to a network printer without having to manually install a new driver.

See how the printing subsystem in Windows Server 2003 has been enhanced to better server your network.

The Active Directory service in Windows Server 2003 provides a method for publishing shared printers that makes it easy to search for printers by location or capabilities.

Get step-by-step instructions for creating and configuring a highly available print server utilizing a typical single quorum device multi-node server cluster using a shared disk on servers running the Microsoft Windows Server 2003 Enterprise Edition, and Windows Server 2003 Datacenter Edition, operating systems.

Learn how connectivity enhancements in Windows Server 2003 have a substantial impact on the performance and scalability of a print server.

Learn how the Windows printing model provides flexibility to support a wide variety of operating system versions and printer driver languages.

Read about the different methods available to system administrators for performing print server consolidations in Windows Server 2003.

Learn how to automate many printer configuration functions using scripts and the printui.dll. This paper describes the basic functions provided by printui.dll and how they can be used in common system administration tasks.

See the complete list of all technical articles you'll find on the Windows Server 2003 Web site, organized by technology.

Consult this brief and informative white paper to learn about the advantages of using a print server instead of direct printing with Microsoft Windows operating systems.

The Microsoft Windows Server 2003 Resource Kit Tools are a set of tools to help administrators streamline management tasks such as troubleshooting operating system issues, managing Active Directory, configuring networking and security features, and automating application deployment.

This online seminar focuses on the advanced features of Windows printing services. Best practices for printing with Active Directory and Microsoft Cluster Service are covered in detail.

Windows Print Migrator version 3.1 provides full backup, restore, and migration functionality for Windows NT-based servers running Windows NT 4, Windows 2000, and Windows Server 2003.

Learn more about Print Services in Windows Server 2003 and how greater print performance and better print server manageability lead to a lower total cost of ownership.

File Services in Windows Server 2003 provide standardized infrastructure services that streamline the development of core server management and file services.

This site includes links to a wide range of documents about Windows 2000 Print Services, including Active Directory and printing, highly available print servers, as well as upgrading and migrating to Windows NT 4.0 print servers.

This webcast gives an overview of Windows Server 2003 command-line tools and scripts, and does not cover every available tool. Scenarios demonstrate how command-line tools can automate administration of Active Directory®, management of printers and print queues, and remote information-gathering by help desk personnel.

Get the best printer drivers for your printing environment. The paper is designed for systems integrators, administrators, and architects who are planning, deploying, or managing Windows print servers.

Learn how to locate and use a suitable substitute print driver for computers based on x64 architecture should a certified print driver not be available.

This paper discusses the different aspects of IPP and recommended deployment methods. The paper is designed for systems integrators, administrators, and architects who are planning, deploying, or managing Windows print servers.

Windows NT supports the central installation of printer drivers for various client platforms. These include MIPS, Alpha, Power PC, and also Windows 95/98 clients. This article describes how to do this for Windows NT 4.0.

This article describes the updated TCP/IP printing components that are available in Windows NT Server 4.0 Service Pack 3 (SP3).

Microsoft Cluster Server has the ability to create and host print server functionality. This article documents the procedure for correctly setting up a print spooler on a cluster.

When you make a connection to a Windows 2000 Internet print server using the "Connect to an Internet Printer" option in the Add Printer Wizard, the port is automatically installed as an HTTP printer port.

You can use the Microsoft cluster service to create and host print server functions. Windows 2000 Server configuration steps have been improved over those in Windows NT Server 4.0, Enterprise Edition.

Windows 2000 Server offers an alternative to Line Printer Remote (LPR) ports when you want to print to network print devices over TCP/IP. The new port monitor is called Standard Port Monitor (SPM). SPM is installed by default when TCP/IP is installed in Windows.

To set up a clustered print server, you need to configure only the Spooler resource in Cluster Administrator and then connect to the virtual server to configure the ports and print queues. This is an improvement over previous versions of Windows Clustering in which you had to repeat the configuration steps on each node in the cluster.

This article describes how to troubleshoot printing issues that are specific to Windows Server 2003-based server clusters.

With Windows 2000 Server, you can have separate printer properties for the local computer and client computers. This article describes where to set these properties for all connecting clients and how to set properties local to the server.