Defensics_User_Guide

FlexNet Operations 2020 Release 2 SP1User GuideLegal InformationCopyright NoticeCopyright © 2020 Flexera SoftwareThis publication contains proprietary and confidential information and creative works owned by Flexera Software and its licensors, if any. Any use, copying, publication, distribution, display, modification, or transmission of such publication in whole or in part in any form or by any means without the prior express written permission of Flexera Software is strictly prohibited. Except where expressly provided by Flexera Software in writing, possession of this publication shall not be construed to confer any license or rights under any Flexera Software intellectual property rights, whether by estoppel, implication, or otherwise.All copies of the technology and related information, if allowed by Flexera Software, must display this notice of copyright and ownership in full.Intellectual PropertyFor a list of trademarks and patents that are owned by Flexera Software, see https:///legal/intellectual-property.html . All other brand and product names mentioned in Flexera Software products, product documentation, and marketing materials are the trademarks and registered trademarks of their respective owners.Restricted Rights LegendThe Software is commercial computer software. If the user or licensee of the Software is an agency, department, or other entity of the United States Government, the use, duplication, reproduction, release, modification, disclosure, or transfer of the Software, or any related documentation of any kind, including technical data and manuals, is restricted by a license agreement or by the terms of this Agreement in accordance with Federal Acquisition Regulation 12.212 for civilian purposes and Defense Federal Acquisition Regulation Supplement 227.7202 for military purposes. The Software was developed fully at private expense. All other use is prohibited.Book Name:FlexNet Operations User Guide Part Number:FNO-2020R2SP1-UG00Product Release Date:June 2020Last Modified Date 17 June 2020Contents1FlexNet Operations 2020 R2 SP1 User Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Introduction to FlexNet Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 FlexNet Operations Home Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 About Download Management and FlexNet Electronic Software Delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 About FlexNet Usage Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Product Support Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Contact Us. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Part 1: Using FlexNet Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332Packaging Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 About Packaging Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 About Trial Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 About Download Management: FlexNet Electronic Software Delivery Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Working with Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 About Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Viewing Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Creating a Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Reviewing Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Working with Feature Bundles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 About Feature Bundles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Viewing Feature Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Creating a Feature Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Reviewing Feature Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Deploying a Feature Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Working with Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 About Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Viewing Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52FlexNet Operations User Guide FNO-2020R2SP1-UG00Company Confidential3ContentsCreating a Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 FlexNet Publisher Versions for Cross-Version Signature Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Adding Features or Feature Bundles to a Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Linking License Models to a Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Mapping a Product to a Part Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Relating Products to Other Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Mapping a Product to a Product Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Reviewing Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Deploying a Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Reviewing New Product Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Working with Suites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Viewing Suites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Creating a Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Adding Products to a Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Linking License Models to a Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Mapping a Suite to a Part Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Relating Suites to Other Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Deploying a Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Working with Maintenances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Creating a Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Mapping a Maintenance to a Part Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Relating Maintenance to Other Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Managing Part Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Adding Part Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Deleting Part Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Mapping Part Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Importing Part Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Managing Product Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Working with Updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 About Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Updates and Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Viewing Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Creating or Modifying an Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Update Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Update Release From . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Update Release To. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Update Languages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Managing Download Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 About Download Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 About Download Package Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 About Download Package Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 About Physical Distribution and Order Media Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 About Export Compliance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Creating a Download Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Searching for a Download Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004Company Confidential FNO-2020R2SP1-UG00FlexNet Operations User GuideContentsViewing Download Package Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Viewing this Download Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Viewing Where a Download Package Is Used. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Viewing Download Package Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Viewing Emails Related to a Download Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Viewing Download Package Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Viewing Download Packages of a Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Editing Download Package Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Editing a Download Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Editing a Download Package File List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Reidentifying a Download Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Restricting a Download Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Creating an Email Notification for a Download Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Copying Download Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Copying a Download Package with Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Copying a Download Package without Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Managing Download Package Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 About Download Package Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Associating a Download Package to a Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Disassociating a Download Package from a Product. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Associating a Download Package to Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Disassociating a Download Package from Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Managing Download Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 About Files and File Images. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 About File Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 About Aliases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 About File Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Adding Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Searching for Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Viewing File Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Viewing this File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Viewing Where a File Is Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Viewing File Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Viewing Emails Related to a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Viewing File Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Viewing File Downloads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Editing File Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Editing a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Aliasing a File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Uploading a File Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Deleting a File Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Reidentifying a File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Restricting a File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Creating an Email Notification for a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Managing File Associations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 About File Associations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137FlexNet Operations User Guide FNO-2020R2SP1-UG00Company Confidential5ContentsAssociating a File to Download Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Using Associate Where to Copy Associations from Another File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Disassociating a File from a Download Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Managing License Agreements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 About Agreements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Listing Agreements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Creating an Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Viewing an Agreement’s Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Editing an Agreement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Managing Producers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 About Producers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Listing Producers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Creating a Producer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Viewing a Producer’s Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Editing a Producer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Reidentifying a Producer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Deactivating a Producer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Reactivating a Producer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1463Entitling Customers and Activating Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Entitling Customers to Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Entitlement Terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 What is an Entitlement? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 What is an Entitlement Line Item? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 What is a Bulk Entitlement?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 What is an Upgrade? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 What is a Test Upgrade? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 What is an Upsell? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 What is a Test Upsell? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 What is a Renewal? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 What is a Test Renewal? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 What is a Merge? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 What is a Transfer? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Viewing Entitlements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Creating an Entitlement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Configuring an Entitlement Line Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Configuring a Maintenance Line Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Changing the State of a Line Item. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Creating a Bulk Entitlement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Configuring a Bulk Entitlement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 Loading Web Register Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Adding a Web Register Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Deleting a Web Register Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Specifying User-Supplied Web Register Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Bulk Operations: Upgrade, Upsell, or Renew a Product. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Merging Entitlements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 6Company Confidential FNO-2020R2SP1-UG00FlexNet Operations User Guide。

Brett’sX‐Ways Forensics (v15.4) QuickStart GuideThis is a quick guide to getting up and running using X‐Ways Forensics (XWF). There are many features documented in the manual, plus more that may not seem to be documented, but are there in more detail. I suggest signing up for the XWF Support Forum where you will have access for more help and be able to ask questions directly to the XWF community. I do not profess to be an XWF expert and hope that this guide does some justice to what XWF can do. If you truly only had one forensic tool to choose, X‐Ways Forensics would be that one tool.XWF is constantly updated. Each update is typically something that you will find to be a valuable new feature, not just bug fixes. I have not yet seen any forensic program so constantly updated, maintained, and supported directly by a developer that is quickly and personally responsive. There are few forensic software companies that will read your wishlist or request, consider it, and either tell you ‘no thank you’ or ‘implement it’ almost immediately.Some of the features that I find to be ‘neat’….XWF can run from an external device, such as a flashdrive or external drive. It requires the dongle to be plugged into the machine, but the dongle is recognized only as a HID (human interface device), so minimal walking over the system. Because XWF can run from an external device, it does not need to be installed to run. This makes it easy to take an image in an XWF folder that can be run on another machine without having to install XWF on every machine you may move your image for examinations. Simply, on an external drive, your image and complete XWF operating program files can be on the same drive and run on any of your forensic machines without installing XWF everywhere. This also makes it possible to work on a live machine, if need be. If there is cause to work on the live machine, using an external drive, with a XWF programs folder, you have full access to XWF on your live suspect machine and do to it as your wish (image it, examine it, export files, etc…).This QuickStart Guide does not do XWF justice in using the features or capability. However, this will show you how to start up XWF, acquire an image, and run the initial processes so you can begin your examination. It’s not quite ‘push button forensics’, but after a while, you will always find yourself going back to XWF and wondered why you did without it for so long. And yes, you can do an entire exam in XWF and validate findings with another tool.Some of the topics this QuickStart doesn’t go into are that of looking at the MFT, hex views of files, and some other intensive analysis that would not be adequately covered in a QuickStart Guide. XWF is much much more than a “hex editor” and has come a long way since when it was just that.For topics that I do brush upon, a search of that topic in the XWF manual will give more information. Sometimes all you need to know is that a feature exists, then you can figure it out or look it up. Not knowing will cause you to not use XWF for what it can do, because you just may not know. The XWF Manual, is in‐depth, detailed, and can be overwhelming if you skim it. But, it does cover every function you’ll come across.I would highly suggest, that the XWF user acquaint him/herself with the terminology as used by XWF to be better prepared to answer terms such as an “Existing File” as compared to a “Previously Existing File” in the manner that it is meant with XWF, among other terms.As side note to how well XWF works…I was at FLETC sitting between a FTK (v1.x) user and longtime Encase (v5) user. Data carving the same image, XWF (v13) came up with literally hundreds of additional images (photos) than did either FTK or Encase. I don’t know why that happened; only that no one else could explain how XWF could do what neither FTK nor Encase could, at least with those versions.The initial, no case, nothing started, XWF. From here, let’s see how one workflow option can work.Set up your Options‐General so XWF behaves like you want it to behave.Something I also do is to create folders for files I export for specific reasons. A folder for “Docs” or “User Files” and XWF can be directed to put your files in the folder of your choice. Not unlike any other program. XWF will by default export files to its respective case folder.When dealing with lots of various time zones, UTC/GMT can save you some headaches of figuring out what happened when and on which machine. Those are the basic settings, now for a real (test) case…Create a case (File‐Create New Case). This will automatically store in the folder you previously created above. In this example, it will be under my XWF Quick Start folder, Case sub‐folder.Most of these options are self‐explanatory. The logging includes screen captures of your dialog boxes, which is a nice feature to see exactly what your dialog box was set to, just when you hit ‘enter’.You can modify your report settings now, or you can do it later when you are ready to create a report. Simply, choose the fields you want displayed on the report and how you want it to look (3 files per line, more or less?, etc…).To add media or an image (or file), choose File – Add _ _ _.I’m going to add a small flashdrive and choose the Physical Media. Pretend this is a write blocked drive…Now we are getting into XWF. This is where some might get scared away to go back to the easy (and maybe not so detailed) other tools.The legend is very important to look at, especially if you don’t know what a particular color or symbol means.To create an image, XWF is as easy as any other forensic application, but it seems to run a bit faster than others. XWF is a very reliable forensic imager.Easy enough: File – Create Disk ImageSame settings as you see on most forensic tools, choose your format type, compression, hash, encryption, etc…The default location for the image is the sub‐folder you created in the beginning. This keeps it nice and neat to have everything in one place. Don’t forget, you can even have your XWF Program Folder in the same place and run XWF from that folder on an external drive.XWF spins away…Hashes…And is done…Now for the processing.The key factor in XWF is the Snapshot! This button is about the most powerful button in the entire program. If nothing else, remember the Refine Volume Snapshot.Indexing can be configured to what your needs are, which is different from other indexing engines where you may not have that much control. Some configurations will make indexing go faster, or take longer (such as choosing word lengths of 2 and 24).Ok, we let the Snapshot run….Most is done at this point, but if you choose indexing, it will continue some more as seen below.The Directory Browser (Options‐Directory Browser or F5) is another need to know feature of XWF. With this feature, you can control what you see as you examine your files. Some may be important in a case, but not in another, therefore, you can control how much and what you see. As you work in the case, you will be tagging files (responsive/evidence) or hiding others (irrelevant files). In this dialog box, you can choose whether to keep seeing files you tagged or you can choose that tagged files be hidden, at least for the time of the examination, but included in the report later.Oh yes, XWF will pull out eml files from your PST files. You can view the emails individually, but will need Outlook installed on your forensic machine.Ok, maybe the Snapshot and Directory Browser weren’t the only great features…XWF allows you to filter by most of the header columns. In this screenshot, choosing to filter by Type allows you to pick those files types of importance in your case. If you are only looking for Email, you can hide everything and XWF will only show you email files. If you want more specificity, you can even choose the individual file types listing under each Type Folder. This is very fast and very neat. As an example, when used in conjunction with the Directory Browser, you could choose to only look at MS Word documents that are previously existing and nothing else. That list can be quickly exported to a spreadsheet.If you are looking at a live machine, with XWF running on your external drive, you can quickly and easier filter files by file type and export them directly to a folder on your external along with an exported spreadsheet of your selected files and a log file of your actions. In a civil ediscovery case, where you may only need to grab user files on a machine that can’t be shutdown (or isn’t a need to be shut down or allowed to be imaged), you can use the filter feature, select those files of agreed upon relevance (docs, pdfs, email, etc…) and have them exported in mere minutes, logged, metadata intact. Who needs a super duper, fancy pancy, file copying utility when you already have the best thing in your kit?Filtering by Date includes any or all of the above, including Record Update and Initial Creation dates. Not all forensic tools give this ability to filter by every date field.Files can be tagged one at a time or in mass selections by using the Shift of Ctrl keys.“Edit Comment” adds your comment to a file or files of interest. This is very helpful as reminders to either reexamine a file or make notes of your thoughts for later reporting. The comments feature is also a header, so you can create specific comments in which you can sort your data later.As you go through and find files that need to go to your report, just add them using the Report Table Association (right click on the file).Another nice feature about the “right clicking” in XWF is that you can hide files you do not want to see again. Just right click, “Hide” and done. This doesn’t remove the files from the image, just hides them from your view until you want to see them again.If there are files of interest and you want to create a hash set of thesefiles…just “right click” again and Create Hash Set. Using files of interest in oneimage, a hash set can be created and run against a different image.With the “Right Click” of a mouse, you canexport selected files to your location and inthe manner you need.When exporting files, select your target folder (ifusing XWF default case settings, the location willbe in the case folder you created). You canchoose to recover the file(s) using any of theoptions seen. Copy logical or slack, or both, withdirectory structure or not. Extremely simple andquick.The Tools‐Hash Database function allows you to import other hash sets into XWF. This can be NSRL hash sets, or sets created with XWF or other tools (such as a FTK Imager exported hash set). After importing your hash set, such as a set of known files you are looking for, run the Snapshot again to check your files against your new hash set.Searching in XWF is straightforward. The options are simple and multiple terms can be entered for searching at the same time.The results are output in a dialog box.And the file hits are highlighted as surrounded by their context. Any of these can be “tagged” as previously mentioned, or viewed or exported.In this test case, I indexed the image, and therefore, I can search the index, which is much faster than searching the image without indexing. But of course, you have to choose to index first if you know you will be keyword searching, or you index later. Either way, your investigative plan will determine if you need to find specific data fast and first, to keyword search later, or if you can afford to have the image index while you wait.After the index is complete, you can also export your word list that was created.XWF can reconstruct RAIDS. I’ve had nearly 100% success with reconstructing RAIDs with XWF.Under the Options – Security, you have several choices to make. For one example, a Strict drive letter protection will not let you save case data outside of where you chose to store initially (at least not on another drive). If you want to be able to save data outside the defaults, uncheck the Strict drive letter protection box.So your case is done (well, they are never really ever done, but at some point, you need a report). From File‐Create Report, here you go. By this point, you should have been tagging and marking your evidence files to the report, or else, you need to go back and do that now or you won’t have anything in your report.Choose the metadata you want included,whether your want your logo, case log, andother details. Once you hit “Ok”, you’ll get aneditable html report (basic).Here is a report, with 3 files showing on each line. The metadata selected is below each file. Also, a link to the file exists to where the file can be opened if clicked. If the file was a graphic, the graphic would be seen. This entire report can beeasily edited to your liking for ease of review.The activity log, which you can choose to have included or not in your report, contains not only the date and time entries of your work, but also screen shots of every dialog box in which you clicked, “OK”. This is really nice to see just what your settings were when you submitted an action with XWF. In this screen shot above, you can see that I choose the Physical Media of RM4 and pushed “OK”.XWF can really dig into your data. From basic file recovery, data runs, MFT records, and flying from offset to offset, XWF can be used by beginners and the most advanced examiners. With RAM analysis being able to be examined, there really isn’t much that XWF can’t do. And when I thought XWF was at the limit of what was possible, when you throw a tool like F‐Response to work with XWF, you have so much more because you can then touch drives remotely for analysis with two tools to leave you wondering again, “why have I have gone so long without XWF…?” For any tip of the iceberg I touched upon, there are substantial details in the XWF Manual. Stefan does an excellent job at keeping the manual updated and XWF updated to the types of media and operating systems available.Two other fantastic features of XWF are the Registry Viewer and X‐Ways Trace. The Registry Viewer, along with its report, has been greatly enhanced over the past years as well as X‐Ways Trace. However, both of those would also be well fitted with their own “QuickStart Guides”…..And to Stefan, thanks for your forensic tool and also for giving the first U.S. class in Seattle ;)。

Simics InstallationGuideSimics Version 3.2Revision1543Date2007-12-13©1998–2007Virtutech ABDrottningholmsvägen14,SE-11242Stockholm,SwedenTrademarksVirtutech,the Virtutech logo,Simics,and Hindsight are trademarks or registered trademarks of Virtutech AB or Virtutech,Inc.in the United States and/or other countries.The contents herein are Documentation which are a subset of Licensed Software pursuant to the terms of the Virtutech Simics Software License Agreement(the“Agreement”),and are being distributed under the Agreement,and use of this Documentation is subject to the terms the Agreement.This Publication is provided“as is”without warranty of any kind,either express or implied, including,but not limited to,the implied warranties of merchantability,fitness for a particular purpose,or non-infringement.This Publication could include technical inaccuracies or typographical errors.Changes are periodically added to the information herein;these changes will be incorporated in new edi-tions of the Publication.Virtutech may make improvements and/or changes in the product(s) and/or the program(s)described in this Publication at any time.The proprietary information contained within this Publication must not be disclosed to others without the written consent of Virtutech.Contents1Introduction5 2Hardware and Software Requirements6 3Installation Overview8 4Linux/Solaris Installation104.1First Installation (10)4.2Academic Users:First Installation (14)4.3Installing License (17)4.4Installing More Packages (17)4.5Uninstalling Simics (17)4.6Installing the Network Interface Helper (17)5Windows Installation195.1First Installation (19)5.2Academic Users:First Installation (20)5.3Installing License (21)5.4Installing More Packages (21)5.5Uninstalling Simics (21)5.6Third-Party Products (22)6Upgrading Simics246.1Upgrading from Simics1.x or2.x (24)6.2Upgrading from Simics3.0 (24)6.3Upgrading between Minor3.2.x Releases (24)7Advanced Installation Options267.1Unix:Add-on Packages Management (26)7.2Windows:Add-on Packages Management (29)7.3Multi-user Installations (31)7.3.1Shared Installations (31)7.3.2Per-user Configuration (32)7.3.3Installation under Configuration Management Systems (32)7.3.4Multi-users Installation on Windows (33)7.4Unix:Installer Options (33)Usage (33)Arguments (33)Options (34)7.5Add-on Manager Options (34)Usage (35)Options (35)8FLEXnet Floating Licenses368.1Overriding License File Location (37)9Workspace Management39 Usage (40)Options (40)10Contact Technical Support42 11Overview of the Simics Directory Structure43Chapter1IntroductionThis document describes how to install and configure the Simics product.It identifies the hardware and software requirements for installing and running Simics and provides in-structions for installation and license configuration.This document should be read by users installing Simics themselves,and all administrators for the Simics product.Chapter2Hardware and Software RequirementsSimics can run on the following platforms:Linux(32-bit)•Host architecture:x86(Pentium II or higher)•OS Version:Red Hat Enterprise Linux WS3or later(1)•Memory:512MB(3)•Disk:Several GB(4)•Third-Party Software:NoneLinux(64-bit)•Host architecture:x86-64•OS Version:SuSE Linux9.3or later(2)•Memory:512MB(3)•Disk:Several GB(4)•Third-Party Software:NoneMicrosoft Windows(32-bit)•Host architecture:x86(Pentium II or higher)•OS Version:Windows2000or later•Memory:512MB(3)•Disk:Several GB(4)•Third-Party Software:WinPcap3.0,TAP-Win32(OpenVPN2.0),MinGW. Sun Solaris(64-bit)•Host architecture:SPARC•OS Version:Solaris8or later•Memory:512MB(3)•Disk:Several GB(4)•Third-Party Software:None(1)Should work also on any compatible Linux distribution.Minimal requirements are GNU libc2.3.x or newer with NPTL and GTK2.2for the GUI.Note that Simics does cur-rently not work with SELinux in enforcing mode.(2)Should work also on any compatible Linux distribution.Minimal requirements are GNU libc2.3.x or newer with NPTL and GTK2.6for the GUI.Note that Simics does cur-rently not work with SELinux in enforcing mode.(3)In general,it helps to have200to300MB plus at least as much memory as what is being used on the simulated machine,in order to avoid swapping.(4)The amount of necessary disk space highly depends on the amount of storage space that will be used in the simulated machine.Simics itself will take between200and300MB, depending on the installed add-on packages.Chapter3Installation OverviewSimics is provided in several packages:•A base package containing Simics Hindsight,i.e.,the Simics execution engine as well as the user interface and the standard models.It also contains Simics Ethernet Networks and Simics Serial Networks.•An add-on package with the Firststeps tutorial machine(a PowerPC-based card).•An add-on package for each simulated system(usually containing a CPU core and various devices).•Some add-on packages for additional functionality,like Simics Model Builder,which contains the DML compiler and relatedfiles.Virtutech customers are provided with encrypted packages,for which decryption keys are sent separately.To install Simics,do the following:1.Download the base package and the add-on packages for which you have a license.Ifsome third-party software is necessary,it will be documented later in this guide(refer to the Third Party Products sections).2.Install the packages.If a key is required,the installer will ask for it at the appropriatetime.3.Set up your license.4.Although it isn’t mandatory,it is usually a good idea to create a workspace whereyou will keep thefiles you are working with,while leaving the Simics installation read-only.It will make upgrading Simics much easier later on.Note:Contrary to the Simics3.0installation process,add-on packages are not installed on top of the Simics installation anymore.Each package stays in its own directory,and Simics is simply instructed to look for add-on packages in various places using the addon-manager program.When installing Simics in a corporate environment,several options are provided for multi-user installations.Refer to chapter7for a complete description.Chapter4Linux/Solaris Installation4.1First InstallationAs a Virtutech customer,you received a mail(or instructions)that describes which packages you should download and where tofind them.If this is not the case,contact Virtutech to obtain this information.1.Start by downloading the packages you want to install.In this example we will as-sume that we are interested in the packages1000(Simics itself)and4005(the Firststeps add-on).joe@computer:˜/simics-download/$lssimics-pkg-1000-3.2.0-linux.tarsimics-pkg-4005-3.2.0-linux.tarThese packages are.tarfiles:when uncompressed,they will create a simics-3.2-install directory with the relevant installationfiles:joe@computer:˜/simics-download/$tar xf simics-pkg-1000-3.2.0-linux.tarjoe@computer:˜/simics-download/$tar xf simics-pkg-4005-3.2.0-linux.tarjoe@computer:˜/simics-download/$ls simics-3.2-installsimics-installation-guide.pdfinstall_simics_common.pminstall-simics.plpackage-1000-3.2.0-linux.packageinfo.tfpackage-1000-3.2.0-linux.tar.gz.tfpackage-4005-3.2.0-linux.packageinfo.tfpackage-4005-3.2.0-linux.tar.gz.tftfdecode-linuxSLA-1.0Thefile simics-installation-guide.pdf is a copy of this manual.The packages themselves are encrypted in the tar.gz.tffiles.The installation program is the script install-simics.pl,which we’ll use in the next step of the installation.2.Run the installation script:joe@computer:˜/simics-download/simics-3.2-install$./install-simics.plFor thefirst installation,the script will start by asking you to read and accept the Simics Software License Agreement(SLA).If you or your company already signed a valid SLA for Simics3.2,you can say so immediately:Have you already signed a custom Simics Software License Agreementwith Virtutech?(y,n)[n]:<ENTER>If you have a valid SLA,the installation will start immediately and you can skip to the next step.If you do not have a valid SLA,you will be asked where your company is located:Is your company located in one of the following areas:USA,Canada,Japan,the European Union?(y,n):yIf your company is not located in any of those areas,you need to contact Virtutech to obtain a custom license agreement before continuing the installation.The installation script will then allow you to read the Simics SLA.It will also point you to afile that you can open and print with almost any text editor to read the SLA at your leisure.Once you read the SLA,you will be asked to accept(by typing“accept”) or decline it.Declining will interrupt the installation process.Accepting will get you to the next installation step.install-simics will now show you the Simics Software License Agreementfor Simics 3.2(revision 1.0).You can also read or print this agreement by opening the file’SLA-1.0’(in the current directory)in any text editor.To continue with the installation and review the terms of the SLA,enter’y’To abort the installation,enter’n’.(y,n)[y]:<ENTER>...Showing the SLA...Do you accept the terms of the SLA?(accept,decline)[decline]:accept3.At this point,you will be asked for the keys necessary to decrypt the packages.Keysare cached automatically once they have been found to be correct,so you should needto perform this step only once(for a given package):->Looking for Simics packages in current directory...Enter a decryption key for package-1000-3.2.0-linux.tar.gz.tf[Abort]:0123456789ABCDEF0123456789ABCDEFEnter a decryption key for package-4005-3.2.0-linux.tar.gz.tf[Abort]:0123456789ABCDEF0123456789ABCDEFNote:These are not the actual keys.4.The script will present a list of packages to install.Simply write the number listedin front of each package you wish to install.In our case,we assume that we want toinstall all packages(Simics and Firststeps):install-simics can install the following packages from the current directory: Number Name Type Version Host File1Simics-Base simics 3.2.0x86-linux package-1000-3.2.0-[...]2Firststeps addon 3.2.0x86-linux package-4005-3.2.0-[...]3All packagesPlease enter the numbers of the packages you want to install,as in"143"Package numbers,or Enter to[Abort]:35.You will be asked for a destination directory.We accept here the default proposition:Enter a destination directory for installation[/opt/virtutech/simics-3.2/]:<ENTER> 6.The script will show you a summary of the installation options before proceeding.Ifyou accept to continue,the installation will be performed:The following packages will be installed in/opt/virtutech/simics-3.2/: package-1000-3.2.0-linux.tar.gz.tf(Simics-Base 3.2.0)with key0123456789ABCDEF0123456789ABCDEFpackage-4005-3.2.0-linux.tar.gz.tf(Firststeps 3.2.0)with key0123456789ABCDEF0123456789ABCDEFDo you wish to perform the installation?(y,n)[y]:<ENTER>->Decrypting package-1000-3.2.0-linux.tar.gz.tf->Testing package-1000-3.2.0-linux.tar.gz->Installing package-1000-3.2.0-linux.tar.gz->Decrypting package-4005-3.2.0-linux.tar.gz.tf->Testing package-4005-3.2.0-linux.tar.gz->Installing package-4005-3.2.0-linux.tar.gz7.If everything was successful,you now have two directories in/opt/virtutech/simics-3.2/called simics-3.2.0and simics-firststeps-3.2.0.The installer will ask you whether you want to install a licensefile to run Simics.This file should have been provided to you by Virtutech.Note that if you havefloating licenses,the configuration is a bit more complex.In that case,refer to chapter8.If you wish to,Simics can automatically install a licensefile in your newly installed Simics.Enter a license file name or Enter to[Skip]:simics-license.lic->Copying simics-license.lic to/opt/virtutech/simics-3.2//simics-3.2.0/licenses 8.The installer will help youfinish the configuration of the packages you installed.Thedefault choice—to configure the Firststeps add-on with the newly installed Simics—is exactly what we want:install-simics has installed the following add-on package:Firststeps 3.2.0/opt/virtutech/simics-3.2//simics-firststeps-3.2.0Do you wish to make these add-on packages available inSimics-Base 3.2.0?(y,n)[y]:<ENTER>->Making add-on package available in Simics-Base 3.2.09.The installer should now summarize the installation and report that everything wassuccessful.You can run Simics directly with the following command:joe@computer:˜$/opt/virtutech/simics-3.2/simics-3.2.0/bin/simics-guiYou can also create a workspacefirst,where you will keep your own modified scripts and thefiles you are working with:joe@computer:˜$/opt/virtutech/simics-3.2/simics-3.2.0/bin/workspace-setupsimics-workspacejoe@computer:˜$cd simics-workspacejoe@computer:˜$./simics-guiIf you are new to Simics,it is probably time to open the Getting Started with Simics manual for some reading and tutorial.You willfind it in the doc/directory of your Simics installation or your workspace,as well as in the Simics on-line help.4.2Academic Users:First InstallationAs an academic user,you have access to a number of Simics packages in your download area.1.Start by downloading the packages you want to install.In this example we will as-sume that we are interested in the Simics-Base package(Simics itself)and the First-steps add-on.joe@computer:˜/simics-download/$lssimics-pkg-simics-base-3.2.0-linux.tarsimics-pkg-firststeps-3.2.0-linux.tarThese packages are.tarfiles:when uncompressed,they will create a simics-3.2-install directory with the relevant installationfiles:joe@computer:˜/simics-download/$tar xf simics-pkg-simics-base-3.2.0-linux.tar joe@computer:˜/simics-download/$tar xf simics-pkg-firststeps-3.2.0-linux.tar joe@computer:˜/simics-download/$ls simics-3.2-installsimics-installation-guide.pdfinstall_simics_common.pminstall-simics.plSLA-academic-1.0SLA-academic-1.0.rtfsimics-base-3.2.4-linux.packageinfosimics-base-3.2.4-linux.tar.gzfirststeps-3.2.2-linux.packageinfofirststeps-3.2.2-linux.tar.gzThefile simics-installation-guide.pdf is a copy of this manual.The pack-ages themselves are in the tar.gz.tffiles.The installation program is the script install-simics.pl,which we’ll use in the next step of the installation.2.Run the installation script:joe@computer:˜/simics-download/simics-3.2-install$./install-simics.plFor thefirst installation,the script will start by asking you to read and accept the Simics Software License Agreement(SLA).Besides showing you the SLA online,itwill point you to afile that you can open and print with almost any text editor to readthe SLA at your leisure.Once you read the SLA,you will be asked to accept(by typing“accept”)or decline it.Declining will interrupt the installation process.Accepting willget you to the next installation step.install-simics will now show you the Simics Software License Agreementfor Simics 3.2(revision 1.0).You can also read or print this agreementby opening the file’SLA-academic-1.0’(in the current directory)in any text editor.To continue with the installation and review the terms of the SLA,enter’y’To abort the installation,enter’n’.(y,n)[y]:...Showing the SLA...Do you accept the terms of the SLA?(accept,decline)[decline]:accept3.The script will present a list of packages to install.Simply write the number listedin front of each package you wish to install.In our case,we assume that we want toinstall all packages(Simics and Firststeps):install-simics can install the following packages from the current directory: Number Name Type Version Host File1Simics-Base simics 3.2.0x86-linux simics-base-3.2.0-linux.tar.gz 2Firststeps addon 3.2.0x86-linux firststeps-3.2.0-linux.tar.gz3All packagesPlease enter the numbers of the packages you want to install,as in"143"Package numbers,or Enter to[Abort]:34.You will be asked for a destination directory.We accept here the default proposition:Enter a destination directory for installation[/opt/virtutech/simics-3.2/]:<ENTER> 5.The script will show you a summary of the installation options before proceeding.Ifyou accept to continue,the installation will be performed:The following packages will be installed in/opt/virtutech/simics-3.2: simics-base-3.2.4-linux.tar.gz(Simics-Base 3.2.4)firststeps-3.2.2-linux.tar.gz(Firststeps 3.2.2)Do you wish to perform the installation?(y,n)[y]:y->Testing simics-base-3.2.4-linux.tar.gz->Installing simics-base-3.2.4-linux.tar.gz->Testing firststeps-3.2.2-linux.tar.gz->Installing firststeps-3.2.2-linux.tar.gz6.If everything was successful,you now have two directories in/opt/virtutech/simics-3.2/called simics-3.2.0and simics-firststeps-3.2.0.The installer will ask you whether you want to install a licensefile to run Simics.This file should have been provided to you by Virtutech.Note that if you havefloating licenses,the configuration is a bit more complex.In that case,refer to chapter8.If you wish to,Simics can automatically install a licensefile in your newly installed Simics.Enter a license file name or Enter to[Skip]:simics-license.lic->Copying simics-license.lic to/opt/virtutech/simics-3.2//simics-3.2.0/licenses 7.The installer will help youfinish the configuration of the packages you installed.Thedefault choice—to configure the Firststeps add-on with the newly installed Simics—is exactly what we want:install-simics has installed the following add-on package:Firststeps 3.2.0/opt/virtutech/simics-3.2//simics-firststeps-3.2.0Do you wish to make these add-on packages available inSimics-Base 3.2.0?(y,n)[y]:<ENTER>->Making add-on package available in Simics-Base 3.2.08.The installer should now summarize the installation and report that everything wassuccessful.You can run Simics directly with the following command:joe@computer:˜$/opt/virtutech/simics-3.2/simics-3.2.0/bin/simics-guiYou can also create a workspacefirst,where you will keep your own modified scripts and thefiles you are working with:joe@computer:˜$/opt/virtutech/simics-3.2/simics-3.2.0/bin/workspace-setupsimics-workspacejoe@computer:˜$cd simics-workspacejoe@computer:˜$./simics-guiIf you are new to Simics,it is probably time to open the Getting Started with Simics manual for some reading and tutorial.You willfind it in the doc/directory of your Simics installation or your workspace,as well as in the Simics on-line help.4.3.Installing License 4.3Installing LicenseIf you skipped the installation of the licensefile during the installation phase,you can install it manually.You should have received a licensefile from Virtutech to be able to use Simics. The licensefile is shipped separately by e-mail and not included in any package.Copy the licensefile to[simics]/licenses and Simics will automatically detect it on start-up.If you have anyfloating licenses you must also start a license server.This is described in section8.4.4Installing More PackagesYou can install more packages at any time using the same steps as above.The easiest way is to install all packages,whenever possible,in the same directory(like/opt/virtutech/ simics-3.2above).The installer will propose a default configuration that should always work with the latest installed version of Simics.If you want to handle the installation differently,you should read the next sections about add-on package management,the installer command-line switches and the addon-manager options.4.5Uninstalling SimicsUninstalling Simics is very simple:you just need to remove the directories that were created for each package during installation.Note the following:•If you delete an add-on package that is still referenced in the add-on packages list of a Simics installation,the add-on package will simply be considered invalid and ignored.The workspace-setup program will however suggest that you update workspaces that were using that add-on package.•If you delete a Simics installation,you will need to reconfigure the workspaces that depended on it by running the workspace-setup program from another Simics in-stallation.4.6Installing the Network Interface HelperSimics provides many ways to connect the simulated network to the real network.They are listed in the Connecting to a Real Network chapter of Ethernet Networks in Simics.For some of them a small helper program,openif,needs to be installed.openif must run with super-user privileges.There are several ways of accomplishing this:•Install openif as setuid root.In the simplest case,it is just a matter of running these shell commands,replacing host with the host type you are running Simics on,for ex-ample,x86-linux:#cd simics-directory4.6.Installing the Network Interface Helper#chown root host/bin/openif#chmod u+s host/bin/openifIf thefile system where Simics is installed does not allow setuid binaries,you can move openif to some location which allows setuid binaries and create a symbolic link which points to the movedfile.To verify that openif has been installed properly,try executing it directly from the shell as an ordinary user.If it complains about root privileges,it does not have the correct permissionflags set and you may need to move it,perhaps to a directory on a local(not networked)file system.Since the openif program allows an unprivileged program to read and send raw pack-ets from the network interface,you may want to restrict access to it.In this case,it can be put in a directory to which access is restricted using the standard Unix mechanisms.Its location then has to be indicated with a symbolic link as above.•If you have the common Unix utility sudo installed,it can be used to run openif from Simics by the means of a small wrapper script.This script would look like:#!/bin/shexec sudo/path/to/openif$*Then use a symbolic link to tell Simics where tofind the script.Note that sudo must be configured to allow the user to run openif as root,without giving a password.•You can also run the entire Simics process connected to a real network as root.This alternative is not recommended,and may cause problems depending on the license model chosen.The source code of openif is available as part of the Simics distribution,open to inspec-tion and modification as needed.Note that allowing unprivileged users to access the raw network device may cause se-curity problems.Therefore it is not recommended to use the real-network connection in an untrusted network environment.A safer solution is to use the port forwarding feature in Simics instead.Chapter5Windows Installation5.1First InstallationAs a Virtutech customer,you received a mail(or instructions)that describes which packages you should download and where tofind them.If this is not the case,contact Virtutech to obtain this information.1.Start by downloading the packages you want to install.In this example we will as-sume that we are interested in the packages1000(Simics itself)and4005(the Firststeps add-on).These packages are.exe installers.2.Run the installer for package1000.You willfirst need to provide a decryption key forthe package.Keys are cached automatically once they have been found to be correct, so you should need to perform this step only once(for a given package).If you provide an incorrect key,or if the package itself was damaged during the down-load process,the installer will warn you at the end of the decryption phase that some-thing went wrong.Check carefully the key you entered and ensure that the download process wasfinished correctly(check thefile size for example).If this doesn’t solve the problem,contact Virtutech on the support forum.3.Once the installer was decrypted successfully,it will simply run through a number ofstandard steps before installing the product itself:•Indicate whether you already signed a custom SLA for Simics3.2or not.If youhave,the installation will directly go two steps further.•If you haven’t signed any custom agreement,the installer will ask you whereyour company is located,in order to check if it is covered by our standard Soft-ware License Agreement(SLA).If the standard agreement does not apply,youwill need to contact Virtutech to obtain a custom SLA.•Read and accept the SLA if you agree with the terms.•Choose an installation directory.•Tell the installer where it canfind the licensefile you received to run Simics.5.2.Academic Users:First Installation4.If you are usingfloating licenses,license installation may be more complex and isexplained in chapter8.5.Once package1000is installed,Simics is ready to run on your computer.However,no simulated architecture is installed,so it will be of limited use.Let us now install package4005.The installation is fairly similar to the previous one:•Enter the correct decryption key.•The Software License Agreement part should be skipped,as the installer knowsthat you already accepted a SLA before.•Choose an installation directory.•Pick-up a Simics installation for registering this add-on package.As you justinstalled Simics before,it should be the only proposition available and you cansimply press Next to continue.6.Simics and the Firststeps packages are now installed on your computer.You can startSimics by simply going to the Start Menu and clicking on Simics.When Simics starts,it will suggest that you create a workspace,to keep your own modified scripts and thefiles you are working with.This is probably a good idea unless you know exactly what you are doing.If you are new to Simics,it is probably time to open the Getting Started with Simics manual for some reading and tutorial.You willfind it in the Start Menu under the Documentation folder,or in the Simics on-line help.5.2Academic Users:First InstallationAs an academic user,you have access to a number of Simics packages in your download area.1.Start by downloading the packages you want to install.In this example we will as-sume that we are interested in the Simics-Base package(Simics itself)and the First-steps add-on.These packages are straight.msi installers.2.Double-click on the installer for the Simics-Base package.It will simply run through anumber of standard steps before installing the product itself:•If you haven’t done so already,read and accept the Simics Software LicenseAgreement.•Choose an installation directory.•Tell the installer where it canfind the licensefile you received to run Simics.3.If you are usingfloating licenses,license installation may be more complex and isexplained in chapter8.5.3.Installing License4.Once the Simics-Base package is installed,Simics is ready to run on your computer.However,no simulated architecture is installed,so it will be of limited use.Let us now install the Firststeps package.The installation is fairly similar to the previous one:•The Software License Agreement part should be skipped,as the installer knowsthat you already accepted a SLA before.•Choose an installation directory.•Pick-up a Simics installation for registering this add-on package.As you justinstalled Simics before,it should be the only proposition available and you cansimply press Next to continue.5.Simics and the Firststeps packages are now installed on your computer.You can startSimics by simply going to the Start Menu and clicking on Simics.When Simics starts,it will suggest that you create a workspace,to keep your own modified scripts and thefiles you are working with.This is probably a good idea unless you know exactly what you are doing.If you are new to Simics,it is probably time to open the Getting Started with Simics manual for some reading and tutorial.You willfind it in the Start Menu under the Documentation folder,or in the Simics on-line help.5.3Installing LicenseYou should have received a licensefile from Virtutech to be able to use Simics.The license file is shipped separately by e-mail and not included in any package.Copy the licensefile to[simics]\licenses and Simics will automatically detect it on start-up.If you have anyfloating licenses you must also start a license server.This is described in section8.5.4Installing More PackagesYou can install more packages at any time using the same steps as above.The installer will suggest a default configuration that should always work with the latest installed version of Simics.If you want to handle the installation differently,you should read the next sections about add-on package management and the addon-manager options.5.5Uninstalling SimicsTo uninstall Simics,just use the Add/Remove Programs control panel.Note the following:•If you delete an add-on package that is still referenced in the add-on packages list of a Simics installation,the add-on package will simply be considered invalid and ignored.The workspace-setup program will however suggest that you update workspaces that were using that add-on.。

Cloud Perimeter Scans User GuideApril 14, 2022Copyright 2018-2022 by Qualys, Inc. All Rights Reserved.Qualys and the Qualys logo are registered trademarks of Qualys, Inc. All other trademarks are the property of their respective owners.Qualys, Inc.919 E Hillsdale Blvd4th FloorFoster City, CA 944041 (650) 801 6100Table of ContentsAbout this Guide (4)About Qualys (4)Qualys Support (4)Configuring Cloud Perimeter Scanning for EC2 Connectors (5)What you’ll need (5)EC2 Scan Checklist (5)Configure Your New Cloud Perimeter Scan (6)View Scan Results (10)Run Scan Reports (11)Configuring Cloud Perimeter Scanning for Azure Connectors (13)What you’ll need (13)Configure Cloud Perimeter Scan (13)View Azure VM Tracked Host Assets in Host Assets (17)Qualys API support (18)About this GuideAbout Qualys About this GuideThank you for your interest in the Qualys Cloud Platform! This guide tells you how to configure and launch cloud perimeter scans using the UI and API.About QualysQualys, Inc. (NASDAQ: QLYS) is a pioneer and leading provider of cloud-based security and compliance solutions. The Qualys Cloud Platform and its integrated apps help businesses simplify security operations and lower the cost of compliance by delivering critical security intelligence on demand and automating the full spectrum of auditing, compliance and protection for IT systems and web applications.Founded in 1999, Qualys has established strategic partnerships with leading managed service providers and consulting organizations including Accenture, BT, Cognizant Technology Solutions, Deutsche Telekom, Fujitsu, HCL, HP Enterprise, IBM, Infosys, NTT, Optiv, SecureWorks, Tata Communications, Verizon and Wipro. The company is also a founding member of the Cloud Security Alliance (CSA). For more information, please visit Qualys SupportQualys is committed to providing you with the most thorough support. Through online documentation, telephone help, and direct email support, Qualys ensures that your questions will be answered in the fastest time possible. We support you 7 days a week, 24hours a day. Access support information at /support/Configuring Cloud Perimeter Scanning for EC2 ConnectorsWhat you’ll need Configuring Cloud Perimeter Scanning for EC2 ConnectorsWhat you’ll needCloud Perimeter Scanning must be enabledYou’ll need to have these features enabled to run perimeter scans on your cloud environment: 1) Cloud Perimeter Scanning, 2) EC2 Scanning and 3) Scan by Hostname. Please contact your Technical Account Manager or Qualys Support to have features enabled. (Not available to Express Lite.)Manager or Unit Manager privilegesYour account must have a Manager or Unit Manager role.EC2 connector is requiredIf this is your first EC2 scan then we recommend you start by creating an EC2 connector. You’ll do this within the Connector application. A wizard will walk you through the steps.Want to learn more about setting upconnectors? Check out Connector OnlineHelp.Note: Ensure your existing service control policies do not block the required permissions for EC2 connector runs.Configuring Cloud Perimeter Scanning for EC2 ConnectorsEC2 Scan Checklist EC2 Scan ChecklistWe recommend a few steps before scanning.Check EC2 Assets are activatedCheck that your EC2 hosts are activated and have the EC2 tracking method. You can see this in VM on the Host Assets tab and also in AssetView on the Assets tab.Configure Your New Cloud Perimeter ScanGood to Know- Cloud perimeter scans use Qualys External Scanners (Internet Remote Scanners), located at the Qualys Cloud Platform. For accounts on Private Cloud Platforms, your account may be configured to allow internal scanners to be used.- These are DNS or IP -based scans launched using the public DNS or Public IP of the target EC2 instances. If both public DNS and public IP address exist for your EC2 assets, then we will launch a scan on public DNS.- All cloud perimeter scans are scheduled - either for “now” (essentially a one-time scan) or “recurring”. Once saved, you’ll see the scan job on the Schedules list. When the scan starts it will appear on your Scans list.Get StartedGo to Scans > Scans > New > Cloud Perimeter Scan (also on the Schedules tab).Select the EC2 connector you’ve configured.Give your scan a title and select an option profile. Note that cloud perimeter scans typically do not use authentication.Now it’s time to pick your target hosts. Selecting target hosts is an optional step. If you do not specify the platform, region code, vpc id or asset tags, we will create the new cloud perimeter scan job using only the connector.1) Choose a platform option: EC2 Classic, EC2 VPC (All VPCs in region) or EC2 VPC (Selected VPC). Based on your selection you’ll select region(s).2) Select asset tags - these are assets activated for your connector.3) Enter the DNS names for your load balancers to include them in the scan.Note that if no assets are resolved from the connector and for the optional "platform" and "asset tags" selections, the scan is launched on the load balancer DNS names. If no load balancer DNS names are specified, then the scan will fail and get terminated.By default cloud perimeter scans use Qualys External Scanners.For Private Cloud Platforms - Your account may be configured to allow scanner appliances to be used. In this case, choose one or more scanner appliances from the list (use the Build my list option).Tell us when you want the scan to run - Now or Recurring.Note that when you choose Now your scan may not start immediately. We’ll check for new scan requests every few minutes. If a scanner is available and you haven’t reached your concurrent scan limit then we’ll launch the scan. If scanners are not available or you have reached your limit then the scan will be launched at the next opportunity.When you choose Recurring you’ll also set scheduling and notification options. These are the same settings as other scan schedules so they should look familiar.We’ll identify the assets to scan based on your settings.You’ll see these asset counts:Assets Identified / Synced - The number of assets discovered by the connector.Assets Qualified for scan - The number of assets discovered by the connector that also match the selected platform, region, asset tags. We’ll take out the Terminated instances. Assets Submitted to scan - The number of assets that we’ll submit in the scan job. We start with the qualified assets (previous count) and filter out assets that are not activated for VM (for vulnerability scan) or not activated for PC (for compliance scan).When you’re ready, click Submit Scan Job.What happens nextYour new scan will appear on the Schedules list (even if you started it from the Scans tab).When your scan starts it will appear on the Scans list. Like with other scans you can take actions like cancel or pause the scan, view the scan status and download the results. Want to run the scan again? Choose New Scan Job from the Quick Actions menu. We’ll retain certain scan settings from the original scan job and schedule the scan to run Now.Choose View from the Quick Actions menu for any finished scan in your list to see the scan results. You’ll notice the scan type is “Cloud Perimeter - A WS EC2”, you’ll see that Qualys External Scanners were used for the scan, and you’ll see the target DNS names for the assets submitted in the scan job.The Detailed Results and Appendix sections of your scan results show the public DNS name for each scanned asset since cloud perimeter scans are DNS-based.In your scan report template select the EC2 Related Information option on the Display tab. This lets you see EC2 details for each asset in your report, including the public DNS name.Check out this sample report with EC2 related information.Configuring Cloud Perimeter Scanning for Azure ConnectorsWhat you’ll need Configuring Cloud Perimeter Scanning for Azure ConnectorsWe provide the ability to scan public facing virtual machines in your Azure cloud environment using Cloud Perimeter Scanning for VM and PC.Qualys External Scanners (Internet Remote Scanners), located at the Qualys Cloud Platform are used for Perimeter Scanning of Azure virtual machines. For subscriptions on Private Cloud Platforms, your account may be configured to allow internal scanners to be used.These are DNS or IP -based scans launched using the public DNS or Public IP of the target virtual machines. If both public DNS and public IP address exist for your virtual machines, then we will launch a scan on public DNS.What you’ll need- The “Cloud Perimeter Azure VM Scan” feature must be enabled for your subscription. Please reach out to your Technical Account Manager or Qualys Support to enable this feature. You’ll also need these features enabled: Cloud Perimeter Scanning, EC2 Scanning, Scan by Hostname.- Cloud perimeter scans are available for VM and PC modules. Only Managers and Unit Managers have permission to configure cloud perimeter scans.- We allow you to create/update a cloud perimeter scan job through Cloud Perimeter Scan API even if no scan targets are resolved from the provided details. At the time of scan, if no scan targets are resolved from the provided details, the scan will not be launched, and we add the error in the Activity log and Run history of the schedule scan job.Configure Cloud Perimeter ScanAll cloud perimeter scans are scheduled - either for “now” (a one-time scan job) or “recurring”. Once saved, you’ll see the scan job on the Schedules list. When the scan job starts it will appear on your Scans list.1) Create a dynamic tag with Cloud Asset Search filters under “AssetView” app based on your requirements.For example:All running public VMs in your Qualys Subscription: not azure.vm.publicIpAddress is null and azure.vm.state:"RUNNING"All running public VMs in your Azure Subscription: not azure.vm.publicIpAddress is null and azure.vm.subscriptionId: and azure.vm.state:"RUNNING"All running public VMs in a location: not azure.vm.publicIpAddress is null and azure.vm.state:"RUNNING" and azure.vm.location:westusAll running public VMs in a resource group: not azure.vm.publicIpAddress is null and azure.vm.state:"RUNNING" and azure.vm.resourceGroupName:testRG2) Now, lets start scanning. Go to VM/VMDR for a vulnerability scan (or PC for a compliance scan) and choose New > Cloud Perimeter Scan. You'll also see this option on the Schedules tab.3) In the Cloud Information tab, select the Azure icon to scan the Azure VM machines and click Continue.Note: While updating the scan, you cannot change the Provider. We populate the values you selected at the time of creating the scan in Scan option profile settings.4) Go to the Scan Details tab and give the scan a name and select the option profile and priority.5) Go to the Target Hosts tab to select the public facing Azure VM machines on which you want to run the Cloud Perimeter scan. From the Connectors drop-down, select an Azure connector.The Connector drop-down lists the connectors that you have configured in Connectors Application. Select asset tags to further filter the Azure VM assets fetched from the Azure connector.Note: The selected asset tag will scope the selected connectors assets and will not scan assets from under other connectors or non-connector based assets.For load balancers, manually add the DNS names of internet facing load balancers. For Azure VM scan, we do not support pulling load balancer DNS names from the CloudView module.6) Go to the Scanner and Schedule & Notification tabs to select the External/Internal scanner and schedule the scans.Note: By default, the external scanner appliance is selected. If internal scanner is enabled for cloud perimeter scan in your subscription, only then we allow you to select an internal scanner for the scan.7) Go to the Review tab. In the Target Hosts section, we will show you:- how many public facing Azure VM assets are fetched from the connector,- assets that are qualified for the scan and- out of the qualified assets, how many assets are activated in VM on which the scan will be launched.8) Finally, submit the scan job.The VM assessment results from Azure perimeter scans will be tracked to the virtual machine ID tracked asset. As a part of the scan option profile, the scanner tries to reach out the IPs and try to get to the virtual machines.Configuring Cloud Perimeter Scanning for Azure ConnectorsView Azure VM T racked Host Assets in Host Assets View Azure VM Tracked Host Assets in Host AssetsGo to Assets > Host Assets > Filters to search for the Azure VM tracked assets.Click the info button to view the cloud provider name (which is Azure for Azure VM assets), cloud service name (VM for Azure VM assets), and resource ID for the Azure Virtual Machine in the Host Information screen. The Cloud Asset Metadata tab shows the metadata information for the host.Qualys API SupportQualys API SupportThe Qualys API provides support for cloud perimeter scan jobs in these ways:- Use the Cloud Perimeter Scans API (/api/2.0/fo/scan/cloud/perimeter/job) to create and update scan perimeter scan jobs. You can schedule a scan for now or schedule it to start at a later time or on a recurring basis. Cloud perimeter scans are available for VM and PC modules. Only Managers and Unit Managers have permission to configure cloud perimeter scans.- Use the Schedule Scan List API (/api/2.0/fo/schedule/scan/?action=list) to show cloud perimeter scan jobs. When you include cloud details in the XML output, the cloud details will show scan type "Cloud Perimeter" for cloud perimeter scans.- Use the Fetch Scan Results API (/api/2.0/fo/scan/?action=fetch) to fetch scan results for cloud perimeter scan jobs using the API.Refer to the Qualys API (VM, PC) User Guide to learn more about these APIs, including available input parameters and API samples.。

Capacity Market Platform (CMP):CMP Access User Guide - Symantec Endpoint Protection Troubleshooting forGoogle ChromeDate30/11/2018Version 0.1DisclaimerWhilst every effort is made to provide information that is useful and care has been taken in the preparation of the information, EirGrid and SONI give no warranties or representations, expressed or implied, of any kind, with respect to the contents of this guide, including without limitation, its quality, accuracy and completeness.Copyright NoticeCopyright EirGrid plc 2018, all rights reserved. The entire publication is subject to the laws of copyright. No part of this publication may be reproduced or transmitted in any form or by any means, electronic or manual, including photocopying without the prior written permission of EirGrid plc.The Oval160 Shelbourne RoadBallsbridgeDublin 4D04 FW28IrelandCapacity Market Contact DetailsIf you have any questions in relation to this document please contact us using the details below:Email Correspondence:************************Phone Correspondence:1800 726772 (ROI) or 0800 0726772 (NI)+353 (1) 2370584 (International)CMP –CMP Access User Guide –Symantec Endpoint Protection Troubleshooting for Page 2Table of ContentsDisclaimer (2)Copyright Notice (2)Capacity Market Contact Details (2)Purpose of this Document (4)Accessing CMP INT for the 2019/2020 T-1 Mock Auction using Google Chrome (5)Accessing CMP for 2019/2020 T-1 Capacity Auction using Google Chrome (8)CMP –CMP Access User Guide –Symantec Endpoint Protection Troubleshooting for Page 3Purpose of this DocumentThe purpose of this document is to provide troubleshooting information to participants who may experience issues when accessing the Capacity Market Platform (CMP) via Google Chrome due to the use of Symantec Endpoint Protection. The guide provides step by step guidance which should enable participants to access both CMP environments for both the Mock 2019/2020 T-1 Capacity Auction as well as the 2019/2020 T-1 Capacity Auction.CMP –CMP Access User Guide –Symantec Endpoint Protection Troubleshooting for Page 4Accessing CMP INT for the 2019/2020 T-1 Mock Auction using Google Chrome1.Type the CMP INT environment URL https:// in your browser:2.Click on “Advanced”:CMP –CMP Access User Guide –Symantec Endpoint Protection Troubleshooting for Page 53.Click on “Proceed to (unsafe)”:4.Select your Digital Certificate:CMP –CMP Access User Guide –Symantec Endpoint Protection Troubleshooting for Page 65.CMP will open the login page and you should be able to log in as usual:CMP –CMP Access User Guide –Symantec Endpoint Protection Troubleshooting for Page 7Accessing CMP for 2019/2020 T-1 Capacity Auction using Google Chrome The following steps should be used when you see the following screen when opening CMP via https:///Please follow the steps below:1.Close all windows and restart Google Chrome:CMP –CMP Access User Guide –Symantec Endpoint Protection Troubleshooting for Page 82.Open Google Chrome again and click on the three dots that are in the uper right side ofthe page:3.Click on “New incognito window”:CMP –CMP Access User Guide –Symantec Endpoint Protection Troubleshooting for Page 94.Google Chrome will open a new incognito window :5.Type CMP URL and select your Digital Certificate:CMP –CMP Access User Guide –Symantec Endpoint Protection Troubleshooting for Page 106.Google will open again the page below:7.Click on “Advanced”:CMP –CMP Access User Guide –Symantec Endpoint Protection Troubleshooting for Page 118.Then click on “Proceed to ”:9.CMP will open the login page and you should be able to log in as usual:CMP –CMP Access User Guide –Symantec Endpoint Protection Troubleshooting for Page 12。

AXIS Perimeter Defender Requirements User ManualThis document explains the prerequisites and guidelines for implementation of the AXIS Perimeter Defender automated intrusion detection system.Scenario requirementsAXIS Perimeter Defender is suitable for detecting humans or vehicles intruding a sterile zone.A sterile zone is an area where humans or vehicles are not expected.AXIS Perimeter Defender is intended for the following scenarios:•Perimeter protection of industrial sites or critical infrastructures•Zone protection of sensitive facilities,storage sites,recycling sites,or any outdoor private areas•Peripheral protection of stores,warehouses,company buildings or private housesPrerequisites for effective implementationFor AXIS Perimeter Defender to perform most effectively,the following prerequisites are needed:•Humans or vehicles to be detected are fully visible(from feet to head)in the image during at least2seconds and are not obscured by other fixed or moving objects.•Humans or vehicles to be detected are moving on a horizontal plane or a slight slope.•The camera has a fixed field of view.•The level of illumination and camera settings should be sufficient to provide enough contrast between humans or vehicles and the background.We recommend at least50lux in the whole detection area when using an Axis day-and-nightcamera with artificial lighting.-When using external IR spots,the recommended Maximum Detection Distance is80m(260ft).The IR spot should have a maximum distance greater than twice the Maximum Detection Distance.-When using built-in IR light,the Maximum Detection Distance is limited to maximum20m(66ft)depending on the camera and the environment.•To avoid interference from insects,we do not recommend using the camera’s built-in IR light(especially cameras with sunshield).•Small camera vibrations are tolerated but maximum performances are reached for cameras which are not subject to vibrations.•The minimum frame rate is8fps(note that simultaneous views of the camera video stream through the Axis web server can reduce the frame rate to below8fps).•For physical installation requirements,we recommend using the AXIS Perimeter Defender Camera Placement Tool.The tool takes into account both Axis cameras and AXIS Perimeter Defender requirements.Supported devices•For a list of compatible Axis devices,go to /products/axis-perimeter-defender/download•To download Design tool for AXIS Perimeter Defender,which includes technical features of supported devices,go to /products/axis-perimeter-defender/downloadSupported VMS and3rd party systems•AXIS Perimeter Defender is compatible with all VMS and3rd party systems that support native AXIS output interfaces •AXIS Perimeter Defender is fully integrated with Genetec,Milestone and Eboo•AXIS Perimeter Defender generates an XML data stream providing alarms and metadata(for example a2D bounding box surrounding the detected objects).A fully documented protocol allows3rd party systems to seamlessly integrate with this XML data stream.Do you want more information?Go to /products/axis-perimeter-defender/downloadNetwork and system requirements•Cameras running AXIS Perimeter Defender must be reachable from the computer running the AXIS Perimeter Defender Setup Interface through HTTP.•Bandwidth of the connection to the camera must be sufficient.A good3G connection should be sufficient.•AXIS Perimeter Defender Setup Interface(only required during the setup phase)requires:-Windows®7or Windows®8-Intel®Core TM2Duo processor or better-at least2GB RAM of memory-at least1024x768screen resolutionHow to mount the cameraCamera setup overview1Tilt2Field of view3Distance4Maximum detection distance5Minimum detection distance6Camera height7Detection zoneMinimum pixel sizeThe Maximum Detection Distance is the maximum distance from where the application can detect a human or a vehicle.It corresponds to the maximum distance from which the pixel size in the image of a standing person(1.7m height)is less than a certain pixel size value,called Minimum Pixel Size.The Minimum Pixel Size is a percentage of the image height and depends on the camera type and the AXIS Perimeter Defender functions.Visible light cameras-The Minimum Pixel Size is10%of the image height(*).For example,if the height of the visualized image is576pixels,a human or a vehicle will be correctly detected up to a distance from which the height of a standing person becomes less than57pixels.Thermal cameras-The Minimum Pixel Size is7%of the image height(*).When the Long Range function is enabled,the Minimum Pixel Size is4%of the image height.When using corridor format,the indicated percentages are related to the width of the image rather than the height. Maximum pixel size•The height of a human must be at maximum60%of the image height.•The pixel surface of a vehicle must be at maximum35%of the image surface.Tilt and roll angle•The camera must be sufficiently oriented towards the ground so that the center of the image is under the horizon line.The side view of a person to be detected must be sufficient:Minimum Detection Distance>camera height/2.For thermal images,the camera must be significantly tilted towards the ground to minimize the amount of sky appearing in the image.•The roll angle of the camera must be nearly equal to zero.1Object height,tilt angle,and roll angle are suitable.2The human height is less than10%of the image height(7%for thermal cameras).3The center of the image is above the horizon line.4The camera’s roll angle is too big.Mounting heightTo reach certain detection distances,besides the requirement of a minimum pixel size,the camera must be placed at a minimum height.There is no maximum camera height as long as other requirements,especially the tilt angle,are met.Camera Height Maximum Detection Distance2m(6.6ft)110m(33ft)2.5m(8ft)220m(66ft)3m(10ft)100m(330ft)4m(13ft)200m(650ft)5m(16ft)300m(1000ft)6m(20ft)500m(1600ft)1.Minimum mounting height for indoor cameras.2.Minimum mounting height for outdoor cameras.User Manual Ver.M3.4 AXIS Perimeter Defender Requirements Date:October2017©Axis Communications AB,2016-2017Part No.T10094240。