1 Verified for Windows Server 2003 Test Specification VERSION 1.0 April 23, 2003 Microsoft Corporation
2 ii This document is provided for informational purposes only and Microsoft makes no warranties, either express or implied, in this document. Information in this document is subject to change without notice. The entire risk of the use or the results of the use of this document remains with the user. The names of companies, products, people, characters, and/or data mentioned herein are fictitious and are in no way intended to represent any real individual, company, product, or event, unless otherwise noted. Complying with all applicable copyright laws is the responsibility of the user. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in a written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. Microsoft, MSDN, Windows, and the Windows logo are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Other product and company names mentioned herein may be the trademarks of their respective owners Microsoft Corporation. All rights reserved.
3 iii Welcome The Verified for Windows Server 2003 Test Specification was developed by Microsoft to identify applications that run successfully on Windows Server This specification will help software developers by defining the minimum requirements for applications to operate on Windows Server In contrast with the Application Specification for Microsoft Windows 2003 (Certified Applications), this specification does not include features that make applications more robust and manageable, nor does it include features to make applications easier to use or work with the latest technologies. Top reasons your customers will benefit from an application that meets this compatibility specification: The application will install onto Microsoft Windows Server 2003 by means of a robust installation that helps minimize conflicts among shared components. The application will run on Microsoft Windows Server 2003 and is unlikely to cause Microsoft Windows Server 2003 to become unstable. Customers will be able to cleanly uninstall the application. The application meets basic security requirements for Windows Server 2003.
4 iv Checklist for Windows Server 2003 Verification Windows Fundamentals 1.1 Perform primary functionality and maintain stability 1.2 All kernel-mode drivers installed by the application pass verification testing on Windows Server All device or filter drivers included with the application have passed Windows HCT testing 1.4 Perform Windows version checking correctly 1.5 Client components and administrative tools Install/Uninstall 2.1 Do not attempt to replace files that are protected by Windows File Protection 2.2 Non-proprietary files are not overwritten with older versions 2.3 Do not require a reboot inappropriately 2.4 Properly support Add/Remove Programs 2.5 Uninstall correctly Security 3.1 GINA updates and CSPs 3.2 Run in a highly secure configuration 3.3 No additions or modifications are made to the secure desktop 3.4 Compatible with Virus scanning of I/O write to files 3.5 Services running as LocalSystem do not present a UI Reliability 4.1 Appropriate Resource Use 4.2 Do not cause services to become unavailable Please note that the Verified for Windows Server 2003 test is only open to final-release versions of commercially available products. The commercial availability of products will be verified during the test.
5 v Contents Welcome...iii Checklist for Windows Server 2003 Verification...iv Contents...v Windows Fundamentals...1 Install/Uninstall...4 Security Services...7 Reliability...9
7 Windows Fundamentals 1 Windows Fundamentals Summary of Windows Fundamental Requirements Customer Benefits Customers can be confident that a compliant product will execute on Windows Server 2003 and will not adversely affect the reliability of the operating system. Requirements 1.1 Perform primary functionality and maintain stability 1.2 All kernel-mode drivers installed by the application pass verification testing on Windows Server All device or filter drivers included with the application have passed Windows HCT testing 1.4 Perform Windows version checking correctly 1.5 Client components and administrative tools How to Comply with Windows Fundamental Requirements 1.1 Perform primary functionality and maintain stability The application must perform its primary functions without compromising the stability of the operating system or the application. The application may not crash, or cause the operating system to crash while its primary functionality is exercised. Applications will be tested on a computer with two processors, or a processor supporting hyper threading. Both types of systems are recognized by the Operating Systems as dual-processor or multi-processor. A crash is any failure within the server application that either causes data loss or forces unscheduled downtime of the server or service. In contrast a crash within a client component or utility component is considered to be an application failure that prevents the user from continuing. A failure within a server component or service will not be considered a crash if it meets both of the following conditions: a) does not cause loss of data, b) does not force shutdown or unscheduled downtime for any server or service. A failure within a client component or tool will not be considered a crash if it meets all 3 of the following conditions: a) does not cause loss of data, b) displays information that would allow a typical user to understand what went wrong and how to avoid the problem in the future c) allows the user to continue running the application or close it. Example: If the application creates, edits, and saves multi-page documents, it must not crash or stop responding, and it must not lose the user's data when he or she creates, edits, saves, or opens documents up to the maximum size that you specify.
8 2 Windows Fundamentals Example: If the application displays information about the folders on the user s hard drive, it must not crash or destroy data if the user performs, in any order, any of the menu functions in the application, such as creating new folders, moving them, or renaming them. Users must be able to use system features supported by Windows Server 2003 with the application. Example: Windows Server 2003 supports mice with more than three controls (buttons). The application must not crash, stop responding, or lose data when the user presses any button or uses any control, such as a wheel, on a supported mouse. Example: The application must not expect Windows Server 2003 system files or temporary folders to be on any particular drive letter by default or have any maximum or minimum size. Windows Server 2003 may be installed on drive letters other than C or D. The C or boot drive can be quite small, under 100 megabytes (MB). Example: File and printer names can be long, and Windows supports Latin and non-latin in these names. The application must not crash or lose data if a user attempts to use long file or printer names. Example: If the application uses devices, it must not crash if a device is not installed. For example, if a user tries to print when a Printer, Fax, or other output device is not installed, the application must degrade gracefully. 1.2 All kernel-mode drivers installed by the application pass verification testing on Windows Server 2003 Poorly written kernel-mode drivers have the potential to crash the system. Therefore, it is critical that any application that includes kernel-mode drivers, such as backup, copy protection and compact disc (CD) burning products, be thoroughly tested to minimize this risk. Note that requirement 1.3 identifies additional requirements for specific types of device and filter drivers. If the application includes any kernel-mode drivers, each of these drivers must pass validation testing under the Windows Driver Verifier Manager tool (Verifier.exe). With Driver Verifier installed on your kernel-mode components, Driver Verifier must not report any stop error messages, or otherwise cause system instability while the system and your application are fully exercised. 1.3 All device or filter drivers included with the application have passed Windows HCT testing If the product includes drivers for hardware devices or filter drivers for categories accepted by the Windows Hardware Quality Labs (WHQL), these drivers must pass the related tests provided in Windows Hardware Compatibility Test (HCT). The following types of drivers must pass WHQL testing prior to submission for the Verified for Windows Server 2003 test: Hardware Drivers Anti-Virus Drivers Storage Adapter Drivers (e.g. SCSI, Fibre channel, RAID Controller, RAID/Multipath IO) Network Adapter Drivers (e.g. Ethernet [all types from 10/100 MHz to 2GB], Token Ring, FDDI) Additional types as WHQL develops more tests
9 Windows Fundamentals 3 Note: Tests for these drivers are arranged through WHQL. Additional information is available at For certain categories of drivers, Windows Server 2003 will present a warning to end users if they attempt to install a driver that does not have a digital signature from Microsoft. For any drivers that are accepted by the Windows Hardware Quality Labs, the component must be digitally signed by Microsoft. Note: Additional information is available at Proof of WHQL testing for all required device and filter drivers included in the application must be submitted to VeriTest. At no point during testing may any warnings appear about unsigned drivers. 1.4 Perform Windows version checking correctly The application must verify that the operating system meets the minimum version requirements for the application or display a message to the user when blocking installation or execution that the application is not designed for the later Windows version. The application must pass the High Version Lie test with Microsoft s Application Verifier tool (AppVerifier). Note: For more information on AppVerifier, search on AppVerifier in the MSDN library: 1.5 Client components and administrative tools Server applications can include components that are installed separately, possibly onto separate machines. This could include client components (components that might be executed by nonadministrator users on a machine other than the server), and administrative tools. If these components are included in the product being verified, they must also meet the same standard.
10 4 Install/Uninstall Install/Uninstall Summary of Installation Requirements Customer Benefits Customers can be confident that a compliant product will install onto Windows Server 2003 without corrupting any third party applications installed on the system. Requirements 2.1 Do not attempt to replace files that are protected by Windows File Protection 2.2 Non-proprietary files are not overwritten with older versions 2.3 Do not require a reboot inappropriately 2.4 Properly support Add/Remove Programs 2.5 Uninstall correctly How to Comply with Install/Uninstall Requirements 2.1 Do not attempt to replace files that are protected by Windows File Protection The application must not attempt to replace any files that are protected by Windows File Protection (WFP). To ensure that the application does not invoke WFP, it should call SfcIsFileProtected when installing any file that it did not create. The Windows Installer service does this automatically. Protected files include the following files that ship on the Windows Server 2003 product CD: Most.SYS,.DLL,.EXE,.OCX,.manifest, and.cat files. The following fonts: Micross.ttf, Tahoma.ttf, Tahomabd.ttf, Dosapp.fon, Fixedsys.fon, Modern.fon, Script.fon, and Vgaoem.fon. Note: Some redistributable files, such as specific versions of Microsoft Foundation Classes (MFC) DLLs, are installed by Windows Server 2003 and are protected by WFP. Protected files form the core of the operating system and it is essential for system stability that the proper versions be maintained. These files can only be updated through service packs, operating system upgrades, Quick Fix Engineering (QFE) hot-fixes, and Windows Update. Applications cannot replace them, and attempting to replace these files by any means other than those listed above will result in the files being restored by the Windows File Protection feature (see the subsection About Windows File Protection, below). If the application requires newer versions of these components, it must update these components by using a Microsoft Service Pack that installs the required versions or in the case of assemblies install an updated version of the assembly. Example: When Microsoft publishes an update to DirectX, it will be provided in a package (either a Windows service pack or its own service pack). An application including the updated DirectX must use the package install and not attempt to directly install files from the package. Installing individual files is not allowed. Any attempts to do so would be prevented by Windows File Protection and would result in a poor user experience.
11 Install/Uninstall 5 About Windows File Protection Windows File Protection is a feature of Windows Server 2003 that prevents the unauthorized replacement of essential system files. WFP runs as a background process on Windows Server 2003 and monitors the files listed earlier in this section. When WFP detects that a protected file has been changed, it restores the original. No Windows File Protection messages may appear at any time during the installation of the application, or while exercising its primary functionality. Note: Attempting to install components that are under Windows File Protection but have not yet been installed on the system will cause Windows File Protection to install the components. This is correct behavior and not a failure of this requirement. Note: Application Verifier 2.5 and later makes testing for this requirement much easier and more reliable Non-proprietary files are not overwritten with older versions On occasion, applications install files that are sourced from third parties. In such instances, it is possible that newer versions of these same files have already been installed on the computer by another application. Therefore, if your application installs non-proprietary files, you must ensure it does not overwrite files already present on the computer with older versions. The application s installation program must properly check to ensure that the latest file versions are installed. Installing an application must never regress any files that you do not produce or that are shared by applications that you do not produce. Replacing a file with another language version of the same file is equally inappropriate. 2.3 Do not require a reboot inappropriately In Windows Server 2003, very few installation situations require a reboot. Reboots are unwelcome by customers and, in some situations, can make deploying applications difficult. The application must not require or suggest an unnecessary reboot during or after installation or after application uninstall. Using a deployment package based on Windows Installer (MSI) makes meeting this requirement much easier. Some situations that require a reboot Installing a Windows Service Pack or authorized system redistributable may require a reboot. However, do not assume that a reboot is required after installing a Service Pack. Installing a Graphical Identification and Authentication dynamic link library (GINA) requires a reboot. However, applications that install a replacement GINA are not eligible to participate in the Verified for Windows Server 2003 program, as per requirement 3.1 below. Situations that do not require a reboot Reboot is not required for DLL installation, replacement or registration. Updating a service component. If the user or other applications will experience any resource unavailability, you must warn the user that certain services will be stopped while they are updated. Replacing an existing file that is in use by an application. You must give the user information about any open applications that have loaded the resource files you are updating so that the user can shut down the application and release those files, allowing file replacement to occur without a reboot. For applications based on the Windows Installer (MSI), this work is all done for you.
12 6 Install/Uninstall If you do require a reboot, and you are certain it is for a valid reason, you must prompt users and allow them the option of deferring the reboot. If your application requires a reboot, and you have determined it for a valid reason, you must provide technical justification to the test lab for why Windows has to be rebooted in your case. This usually only requires a paragraph or so, but saying we are installing a driver or we are installing a <class> driver is not acceptable. 2.4 Properly support Add/Remove Programs The user must be able to uninstall applications from the Add or Remove Programs item in the Control Panel. The application must supply your product s name and the location of your application s uninstaller, so that the Add or Remove Programs item can obtain information about the application as needed to support uninstall. You can write this information directly to the registry during install or, if you are using an installation system based on the Windows Installer service, you can set these values by using properties in the Windows Installer-based package. When does this apply? This requirement is not applicable for an application that does not install that is, if it executes without installing any components, writing to the registry, modifying the system, or leaving any files on the system other than user created files 2.5 Uninstall correctly The application s uninstaller must correctly and fully remove the application. Except as noted later in this section, the application must remove the following: All non-shared application files and folders. Shared application files whose reference-count (refcount) reaches zero. Registry entries, except for keys that the application created to be specifically shared by other programs and could compromise those applications if removed. All shortcuts from the Start menu that the application created at the time of installation. The uninstaller itself (unless it is a shared component). It is acceptable to leave log files that support might need after the fact in order to diagnose issues. User preferences may be considered user data and left behind, but an option to do a completely clean removal or have documentation on a simple method to completely clean up is highly recommended In general, all user data should be left on the system after removal. If your application removal is about to remove user data, the user must be prompted for confirmation.
13 Security Services 7 Security Services Summary of Installation Requirements Customer Benefits Applications must meet basic security requirements for Windows Server Requirements 3.1 GINA updates and CSPs 3.2 Run in a highly secure configuration 3.3 No additions or modifications are made to the secure desktop 3.4 Compatible with Virus scanning of I/O write to files 3.5 Services running as LocalSystem do not present a UI How to Comply with Security Services Requirements 3.1 GINA updates and CSPs An incorrectly written Graphical Identification and Authentication dynamiclink library (GINA) can break Smart Card authentication on the PC. Cryptographic Service Providers (CSPs) also have the potential to disrupt smart card login on the system. Testing for these components is beyond the scope of the Verified for Windows Server 2003 test. Applications that include these components are not eligible to participate in the Verified for Windows Server 2003 program, and should consider other programs such as Certified for Windows Server In order to comply with this requirement, installation of the application may not cause any changes or additions to be made to the registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\GINADLL or any sub-key or value. 3.2 Run in a highly secure configuration Applications must be able to perform all primary functions in a highly secure configuration. A highly secure configuration is a system with the predefined security template HISECWS.INF applied. This security template is included with Windows Server 2003 in the windows\security\templates folder. To meet this requirement, applications must be able to perform all primary functions on a system with HISECWS.INF applied. 3.3 No additions or modifications are made to the secure desktop The secure desktop is a tightly controlled User Interface presented in the below situations: The change password dialog. The locked computer screen.
14 8 Security Services The UI presented when no user is logged on. The Security dialog on a domain member computer when the CTRL+ALT+DEL keys are pressed. Most applications make no changes to the secure desktop. The standard UI on the secure desktop can only be modified when adding to or replacing the GINA, but it is possible for services to add dialogs or Windows to the secure desktop. Because the secure desktop is running in a high access context, testing modifications or additions to the secure desktop is beyond the scope of the Verified for Windows Server 2003 test. Therefore, applications that make additions or modifications to secure desktop are not eligible to participate in the Verified for Windows Server 2003 program. The secure desktop will be visually examined for any additions or modifications to ensure compliance with this requirement. 3.4 Compatible with Virus scanning of I/O write to files Many device conflicts and application stability issues are exposed when the application runs on a system with kernel mode active virus scanning. Applications must be able to perform all primary functionality while a virus scanner s kernel mode service is actively scanning all files for viruses at full detection mode. The reverse is also true: the kernel mode active virus scanning service must not be disrupted when applications perform their primary functionality. It is good for applications to also perform correctly while a user mode virus scanning utility is used to scan one or more files, but that is not part of this requirement. Any application interactions with an active virus scanner service must be appropriate and must be handled gracefully. If active virus scanning has any effect on an application s functionality, the application must ensure that the benefits of the interaction and the options for the user are both clear. When does this apply? This requirement applies as described above for all applications other than virus scanners. A virus scanner must be fully qualified as defined by WHQL standards. Also, a virus scanner runtime must operate correctly on a system with an active file management service running and with an active firewall. 3.5 Services running as LocalSystem do not present a UI Services running as LocalSystem must not present a User Interface. When a Window is displayed, the associated message queue allows other processes or users to send it any Windows message which may allow hostile code to be introduced and executed in the process providing the UI. If the process is LocalSystem, the hostile code would execute at LocalSystem instead of the level of the originating user or process. Application Verifier 2.5 and later makes testing for this easy.
15 Reliability 9 Reliability Summary of Reliability Requirements Customer Benefits Applications must work reliably in the Windows environment. Requirements 4.1 Appropriate Resource Use 4.2 Do not cause services to become unavailable How to Comply with Reliability Requirements 4.1 Appropriate Resource Use The heap, critical sections, and handles can be misused which results in less reliable applications and failures with subtle circumstances that impact customers but may not be easily reproduced. Each of these items are easily tested to ensure they are not misused. Your application must be able to perform all of its primary and secondary functionality with no critical errors while running under AppVerifier configured to detect heap corruptions, invalid locks usage (critical section use), and invalid handle usage. 4.2 Do not cause services to become unavailable Services are software components managed via the Service Control Manager (SCM), and often provide resources to multiple applications and other components. Your application and application installer must not cause Windows services or services created by others to become unavailable even temporarily (such as a reset). This requirement also applies to any third party service installed or configured by your application or application installer. Requirement 1.1 above already mandates that your application maintain stability of the system, and this is just a further clarification of one aspect of this. Unless you inform the administrator and await guidance on scheduling the shutdown or reset, the only services your application may shutdown or reset are services that are clearly part of your application and are owned by you. To ensure compliance with this requirement, the event log will be examined for service shutdown events to determine if any third party services were being stopped that wasn t scheduled by the administrator.
VERITAS Backup Exec 9.1 for Windows Servers Quick Installation Guide N109548 Disclaimer The information contained in this publication is subject to change without notice. VERITAS Software Corporation makes
1 Selected Windows XP Troubleshooting Guide To locate lost files: Compiled by: Jason M. Cohen Check these locations to locate lost files: The My Documents folder Click Start, and then click My Documents.
VERITAS Backup Exec TM 10.0 for Windows Servers Quick Installation Guide N134418 July 2004 Disclaimer The information contained in this publication is subject to change without notice. VERITAS Software
Core Protection for Virtual Machines 1 Comprehensive Threat Protection for Virtual Environments. Installation Guide e Endpoint Security Trend Micro Incorporated reserves the right to make changes to this
1 Windows 8 Upgrade Assistant User Guide Laplink Software, Inc. For technical support issues or questions, please visit: http://www.laplink.com/contact For other inquiries, please see contact details below:
Windows Small Business Server 2003 Upgrade Best Practices Microsoft Corporation Published: May 2005 Version: 1 Abstract To ensure a successful upgrade from the Microsoft Windows Small Business Server 2003
Module 8: Implementing Group Policy Contents Overview 1 Lesson: Implementing Group Policy Objects 2 Lesson: Implementing GPOs in a Domain 12 Lesson: Managing the Deployment of Group Policy 21 Lab: Implementing
www.novell.com/documentation System Planning, Deployment, and Best Practices Guide ZENworks Application Virtualization 9.0 February 22, 2012 Legal Notices Novell, Inc., makes no representations or warranties
CA ARCserve Backup Patch Manager for Windows User Guide r16 This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation
Chapter 5: Fundamental Operating Systems IT Essentials: PC Hardware and Software v4.1 Chapter5 2007-2010 Cisco Systems, Inc. All rights reserved. Cisco Public 1 Chapter 5 Objectives 5.1 Explain the purpose
SOS Suite Installation Guide rev. 8/31/2010 Contents Overview Upgrading from SOS 2009 and Older Pre-Installation Recommendations Network Installations System Requirements Preparing for Installation Installing
Intel Entry Storage System SS4000-E Software Release Notes March, 2006 Storage Systems Technical Marketing Revision History Intel Entry Storage System SS4000-E Revision History Revision Date Number 3 Mar
Symantec Backup Exec TM 11d for Windows Servers Quick Installation Guide September 2006 Symantec Legal Notice Copyright 2006 Symantec Corporation. All rights reserved. Symantec, Backup Exec, and the Symantec
Pearl Echo Installation Checklist Use this checklist to enter critical installation and setup information that will be required to install Pearl Echo in your network. For detailed deployment instructions
ZENworks 11 Support Pack 4 Full Disk Encryption Agent Reference May 2016 Legal Notice For information about legal notices, trademarks, disclaimers, warranties, export and other use restrictions, U.S. Government
Sage 100 ERP Installation and System Administrator s Guide This is a publication of Sage Software, Inc. Version 2014 Copyright 2013 Sage Software, Inc. All rights reserved. Sage, the Sage logos, and the
Mobility Services Platform 3.1.1 Software Installation Guide Mobility Services Platform 3.1.1 Software Installation Guide 72E-100159-04 Revision D January 2008 2007 by Motorola, Inc. All rights reserved.
INFUSION BUSINESS SOFTWARE Installation and Upgrade Guide 27/01/2016 Published by Infusion Business Software Ltd All Rights Reserved Copyright Infusion Business Software Ltd 2012 Copyright No part of this
Step-by-Step Guide to Securing Windows XP Professional with Service Pack 2 in Small and Medium Businesses 2004 Microsoft Corporation. All rights reserved. This document is for informational purposes only.
Installing and Upgrading to Windows XP Although Windows XP was released many years ago, you will still see it in the field and might need to install it as well, or upgrade older Windows computers to XP.
Part 3 QUESTION 101 You are the administrator of your company's network. A user named Tom in the Art department wants to update his Windows 2000 Professional computer so that he can view graphics at the
MGC WebCommander Web Server Manager Installation and Configuration Guide Version 8.0 Copyright 2006 Polycom, Inc. All Rights Reserved Catalog No. DOC2138B Version 8.0 Proprietary and Confidential The information
Microsoft Dynamics Microsoft Dynamics CRM Adapter for Microsoft Dynamics GP May 2010 Find updates to this documentation at the following location. http://go.microsoft.com/fwlink/?linkid=162558&clcid=0x409
Dell Statistica 13.0 2015 Dell Inc. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or
Why alone is not enough CenterTools Software GmbH 2011 Copyright Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise
Contents Getting Started...1 Check your Computer meets the Minimum Requirements... 1 Ensure your Computer is Running in Normal Sized Fonts... 7 Ensure your Regional Settings are Correct... 9 Reboot your
4 Backing Up and Restoring System Software In this Chapter... Planning a Backup Strategy, 4-3 Preparing for Disaster Recovery, 4-4 Creating Boot Recovery Diskettes, 4-5 Making a Full Backup Tape, 4-8 Restoring
HP ProtectTools Embedded Security Guide Document Part Number: 364876-001 May 2004 This guide provides instructions for using the software that allows you to configure settings for the HP ProtectTools Embedded
Universal Management Service 2015 UMS 2015 Help All rights reserved. No parts of this work may be reproduced in any form or by any means - graphic, electronic, or mechanical, including photocopying, recording,
Integrate Microsoft Windows Hyper V EventTracker v7.x Publication Date: Aug 9, 2014 EventTracker 8815 Centre Park Drive Columbia MD 21045 www.eventtracker.com Abstract Hyper-V in Windows Server 2008 and
Getting Started with Ascent Xtrata 1.7 10300582-000 Revision A Copyright Copyright 2006 Kofax Image Products, Inc. All Rights Reserved. Printed in USA. The information contained in this document is the
Imaging Computing Server User Guide PerkinElmer, Viscount Centre II, University of Warwick Science Park, Millburn Hill Road, Coventry, CV4 7HS T +44 (0) 24 7669 2229 F +44 (0) 24 7669 0091 E email@example.com
Intel Matrix Storage Console Reference Content January 2010 Revision 1.0 INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE,
FAS Asset Accounting FAS CIP Accounting FAS Asset Inventory SQL Server Installation & Administration Guide Version 2011.1 2011 Sage Software, Inc. All rights reserved. Published by Sage 2325 Dulles Corner
SQL Server Setup Guide for BusinessObjects Planning BusinessObjects Planning XI Release 2 Copyright 2007 Business Objects. All rights reserved. Business Objects owns the following U.S. patents, which may
Enterprise Server Application Sentinel for SQL Server Installation and Configuration Guide Application Sentinel 2.0 and Higher August 2004 Printed in USA 3832 1097 000 . Enterprise Server Application Sentinel
Dynamics AX Microsoft Dynamics AX 4.0 Microsoft Dynamics ISV Software Solution Test Guidelines May 23, 2007 The information contained in this document represents the current view of Microsoft Corporation
Installing Windows Rights Management Services with Service Pack 2 Step-by- Step Guide Microsoft Corporation Published: October 2006 Author: Brian Lich Editor: Carolyn Eller Abstract This step-by-step guide
Software License Registration Guide When you have purchased new software Chapter 2 Authenticating a License When you would like to use the software on a different PC Chapter 3 Transferring a License to
Notes: STATISTICA VERSION 9 STATISTICA ENTERPRISE INSTALLATION INSTRUCTIONS FOR USE WITH TERMINAL SERVER 1. These instructions focus on installation on Windows Terminal Server (WTS), but are applicable
Product Guide for Windows Home Server Microsoft Corporation Published: January, 2009 Version: 1.1 This his Product Guide provides an overview of the features and functionality of Windows Home Server software.
KofaxExpress 3.1.0 Installation Guide 2012-05-01 2008-2012 Kofax, Inc., 15211 Laguna Canyon Road, Irvine, California 92618, U.S.A. All rights reserved. Use is subject to license terms. Third-party software
Password Manager Windows Desktop Client EmpowerID provides an extension that allows organizations to plug into Password Manager to customize the Windows logon experience beyond that supplied by the standard
: Managing, Maintaining, and Troubleshooting, 5e Chapter 3 Installing Windows Objectives How to plan a Windows installation How to install Windows Vista How to install Windows XP How to install Windows
Xerox Multifunction Devices Customer Tips March 15, 2007 This document applies to these Xerox products: X WC 4150 X WCP 32/40 X WCP 35/45/55 X WCP 65/75/90 X WCP 165/175 X WCP 232/238 X WCP 245/255 X WCP
Getting Started with Vision 6 Version 6.9 Notice Copyright 1981-2009 Netop Business Solutions A/S. All Rights Reserved. Portions used under license from third parties. Please send any comments to: Netop
Setup Guide Software Version V1.0 Ipswitch, Inc. Ipswitch, Inc. 81 Hartwell Ave Lexington, MA 02421 Phone: 781-676-5700 Web: http://www.ipswitch.com Copyrights The information in this document is subject
TANDBERG MANAGEMENT SUITE 10.0 Installation Manual Getting Started D12786 Rev.16 This document is not to be reproduced in whole or in part without permission in writing from: Contents INTRODUCTION 3 REQUIREMENTS
SolarWinds Migrating SolarWinds NPM Technical Reference Copyright 1995-2015 SolarWinds Worldwide, LLC. All rights reserved worldwide. No part of this document may be reproduced by any means nor modified,
Symantec Backup Exec 12.5 for Windows Servers Quick Installation Guide 13897290 Installing Backup Exec This document includes the following topics: System requirements Before you install About the Backup
IBM Client Security Solutions Client Security User's Guide December 1999 1 Before using this information and the product it supports, be sure to read Appendix B - Notices and Trademarks, on page 22. First
2824B: Implementing Microsoft Internet Security and Acceleration Server 2004 Microsoft Virtual PC Classroom Setup Guide Information in this document, including URL and other Internet Web site references,
Intel Unite Solution Standalone User Guide Legal Disclaimers & Copyrights All information provided here is subject to change without notice. Contact your Intel representative to obtain the latest Intel
Legal Notes Unauthorized reproduction of all or part of this guide is prohibited. The information in this guide is subject to change without notice. We cannot be held liable for any problems arising from
PREREQUISITE GUIDE JUNE 21, 2006 ION EEM 3.8 Server Preparation This document details the server configuration required for an ION EEM installation. This document can and should be used by the your company
Diamond II v2.3 Service Pack 4 Installation Manual P/N 460987001B ISS 26APR11 Copyright Disclaimer Trademarks and patents Intended use Software license agreement FCC compliance Certification and compliance
CSG Windows Support Policy This document describes the policies for service and support of computers running Microsoft Windows used by faculty and staff in the departments of Computer Science, Mathematics
Windows Operating Systems Basic Security Objectives Explain Windows Operating System (OS) common configurations Recognize OS related threats Apply major steps in securing the OS Windows Operating System
Juris Installation / Upgrade Guide Version 2.7 2015 LexisNexis. All rights reserved. Copyright and Trademark LexisNexis, Lexis, and the Knowledge Burst logo are registered trademarks of Reed Elsevier Properties
Windows BitLocker Drive Encryption Step-by-Step Guide Microsoft Corporation Published: September 2006 Abstract Microsoft Windows BitLocker Drive Encryption is a new hardware-enhanced feature in the Microsoft
User Manual Copyright Rogev LTD Introduction Thank you for choosing FIXER1. This User's Guide is provided to you to familiar yourself with the program. You can find a complete list of all the program's
Getting Started rp5800, rp5700 and rp3000 Models Copyright 2011 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Microsoft, Windows, and Windows
Windows 2003 Server Installation Guide Revision 2.0 April 14, 2011 Licenses This manual is the exclusive property of Prometric, Inc. This manual is licensed for use with restrictions to authorized centers
Deploying Microsoft RemoteFX on a Single Remote Desktop Virtualization Host Server Step-by-Step Guide Microsoft Corporation Published: October 2010 Abstract This step-by-step guide walks you through the
Installation Guide Manuals for This Product Manuals for this product have the following structure. Read the manual according to your purpose for using this product. Disc Guides with this symbol are PDF
IBM Rapid Restore PC powered by Xpoint - v2.02 (build 6015a) User s Reference Guide Internal IBM Use Only This document only applies to the software version listed above and information provided may not
2X SecureRemoteDesktop Version 1.1 Website: www.2x.com Email: firstname.lastname@example.org Information in this document is subject to change without notice. Companies, names, and data used in examples herein are fictitious
System 800xA Tools System Version 6.0 Power and productivity for a better world TM System 800xA Tools System Version 6.0 NOTICE This document contains information about one or more ABB products and may
Getting Started Symantec Mail Security for Domino About Symantec Mail Security for Domino Symantec Mail Security for Domino is a complete, customizable, and scalable solution that scans Lotus Notes database
Omgeo OASYS Workstation Installation Guide Version 6.4 December 13, 2011 Copyright 2011 Omgeo LLC. All rights reserved. This publication (including, without limitation, any text, image, logo, compilation,
Contents About This Guide... 4 Signature Manager Outlook Edition Overview... 5 How does it work?... 5 But That's Not All...... 6 And There's More...... 6 Licensing... 7 Licensing Information... 7 System
CHAPTER 3 Installing Windows XP Professional After completing this chapter, you will be able to: Plan for an installation of Windows XP Professional. Use a CD to perform an attended installation of Windows
Lab Answer Key for Module 6: Configuring and Managing Windows SharePoint Services 3.0 Table of Contents Lab 1: Configuring and Managing WSS 3.0 1 Information in this document, including URL and other Internet
Linux Integration Services Version 3.2 for Hyper-V (Windows Server 2008, Windows Server 2008 R2, Microsoft Hyper-V Server 2008, and Microsoft Hyper-V Server 2008 R2) Readme Microsoft Corporation Published: