DOCSLIB.ORG

Mastering Windows XP Registry

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Mastering Windows XP Registry Mastering Windows XP Registry Peter Hipson Associate Publisher: Joel Fugazzotto Acquisitions and Developmental Editor: Ellen L. Dendy Editor: Anamary Ehlen Production Editor: Elizabeth Campbell Technical Editor: Donald Fuller Electronic Publishing Specialist: Maureen Forys, Happenstance Type-O-Rama Proofreaders: Nanette Duffy, Emily Hsuan, Laurie O'Connell, Yariv Rabinovitch, Nancy Riddiough Book Designer: Maureen Forys, Happenstance Type-O-Rama Indexer: Ted Laux Cover Designer: Design Site Cover Illustrator: Sergie Loobkoff Copyright © 2002 SYBEX Inc., 1151 Marina Village Parkway, Alameda, CA 94501. World rights reserved. The author(s) created reusable code in this publication expressly for reuse by readers. Sybex grants readers limited permission to reuse the code found in this publication or its accompanying CD-ROM so long as the author is attributed in any application containing the reusable code and the code itself is never distributed, posted online by electronic transmission, sold, or commercially exploited as a stand-alone product. Aside from this specific exception concerning reusable code, no part of this publication may be stored in a retrieval system, transmitted, or reproduced in any way, including but not limited to photocopy, photograph, magnetic, or other record, without the prior agreement and written permission of the publisher. First edition copyright © 2000 SYBEX Inc. Library of Congress Card Number: 2002100057 ISBN: 0-7821-2987-0 SYBEX and the SYBEX logo are either registered trademarks or trademarks of SYBEX Inc. in the United States and/or other countries. Mastering is a trademark of SYBEX Inc. Screen reproductions produced with FullShot 99. FullShot 99 © 1991-1999 Inbit Incorporated. All rights reserved.FullShot is a trademark of Inbit Incorporated. TRADEMARKS: SYBEX has attempted throughout this book to distinguish proprietary trademarks from descriptive terms by following the capitalization style used by the manufacturer. The author and publisher have made their best efforts to prepare this book, and the content is based upon final release software whenever possible. Portions of the manuscript may be based upon pre-release versions supplied by software manufacturer(s). The author and the publisher make no representation or warranties of any kind with regard to the completeness or accuracy of the contents herein and accept no liability of any kind including but not limited to performance, merchantability, fitness for any particular purpose, or any losses or damages of any kind caused or alleged to be caused directly or indirectly from this book. This book is dedicated to my students at FPC. Perhaps the hardest part of their education is putting up with me. I expect a lot, and they give it. Acknowledgments An acknowledgments section is always hard to write; there are just so many people who have helped. An author's greatest fear is forgetting someone, so I always start off by saying thanks to everyone. If I didn't list you, please don't hate me! Thanks go to Ellen Dendy, of course, who served as acquisitions and developmental editor for this book. Ellen Dendy also helped greatly by providing critical direction whenever needed. (Of course, if you don't like this book, the blame falls on me and only me!) Thanks to the Sybex editorial staff, especially Anamary. Thanks also to Elizabeth Campbell, production editor, for her skillful work and management; to Maureen Forys, electronic publishing specialist, for her expert and speedy layout skills; and to Nanette Duffy, Emily Hsuan, Laurie O'Connell, Yariv Rabinovitch, and Nancy Riddiough, proofreaders, for their proficient proofreading of the pages. Don Fuller served well as our technical editor. It was Don's job to make sure that I told no lies, made no mistakes. Jerold Schulman (JSI, Inc.) maintains the web page at http://www.jsiinc.com/reghack.htm. He provided a lot of expert hints for this book. If you need assistance with your Windows XP installation, check out Jerold's web pages for his tips, tricks, and registry hacks. Special thanks to Laura Belt at Adler & Robin Books. Laura is the person who makes this a business and not a hobby. Thanks to Barry and Marcia Press for their input on the book's contents. Barry asked for a number of things to be covered, and I've covered as many as I could. Thanks to the ExpertZone (and my team members who put up with my slow responses), and everyone at Microsoft who helped, too. Of course, I would be remiss if I didn't thank my family, especially my wife, Nang, who has supported me through thick and thin, and the folks at CMC and MCH who made sure that I survived the experience. This book is dedicated to my students at FPC. Perhaps the hardest part of their education is putting up with me. I expect a lot, and give it. Introduction The registry has evoked emotions from terror to mystery. Few Windows XP users consider the registry their friend. After all, think of it: The registry is the heart and soul of the Windows XP operating system. The registry is everything-it is the brain of the operating system. Damage the registry, and Windows XP quickly develops brain damage and needs major surgery. This is it-the only book on the Windows XP registry that you will need. Now, I won't kid you; there are a few other books on the Windows registry. Every current version of Windows uses a similar registry structure, but we do find that there are sufficient differences between them make it difficult for one book to cover everything well. Will you need another book or tool besides this book? Maybe not. But I do recommend that you get Microsoft's Windows XP Resource Kit, too; it has a lot of good utilities that you will find invaluable. The Windows XP Resource Kit also has a lot of good non-registry stuff. This book covers the Windows XP registry from A to Z. I've covered the standard stuff, from things that most of us should know to things that are not documented at all and are probably only known by a very few first-rate system administrators. Who Is This Book For? This book is valuable to all Windows XP users. Even users of Windows NT 4 and 2000 and Windows 95/98/Me may find good information in this book, though it is primarily oriented toward Windows XP. This book is intended for: • General users who use Windows XP at their desks and are responsible for their own computer(s). Typically, these users don't have responsibility for other users' computers, though they may help their friends out from time to time. • System administrators who are responsible for an organization's computers (and perhaps thousands of Windows XP installations). Administrators will be presented with virtually every conceivable problem over a given period of time. Whatever can go wrong will; Murphy's Law is applied double to system administrators. • Help desk staff who support users, even if they don't usually administer the system. Help desk staff roam throughout the organization, providing help and assistance as needed. All help desk people are going to find this book very useful. If you are a user who wants to get the most out of your Windows XP installation (either Home Edition, Professional, or one of the upcoming .NET Server versions), this book is a very good starting point. Think of it this way: If you are a system administrator, this book is one of the tools that you will need to manage and administer your Windows XP network. Manning the help desk? If so, having this book close at hand can save you lots of time and effort. Overview of the Contents This book is made up of four major sections. Part I: Registry Basics In Part I, "Registry Basics," I discuss ways to avoid problems, do backups, and restore the registry, and I cover some of the tools that are used with the registry. The first chapter, "What Is a Registry—and Why?," introduces the registry. You'll learn about the registry's major sections, called hives. This chapter also tells you about the registry's history. Tip The fastest way to access the registry is to use RegEdit.exe, which comes with Windows XP. To access RegEdit.exe, simply click the Start button, then click Run. Type RegEdit in the dialog box and press Enter. The RegEdit window will appear. Chapter 2 is called "Readme.1st: Preventing Disaster!" It jumps right into one of the most important topics in this book: how to avoid getting into trouble. Most Windows XP disasters are registry related, and they are also preventable. Registry problems often arise because we don't have a good backup of the registry, and something comes along and damages it. Once damaged, the registry can be very difficult to recover. Chapter 3, "Anatomy of the Registry: The Blood, Gore, and Guts," is an in-depth analysis of what's in the registry. Each major hive is covered in detail. We'll discuss the way the hives relate to each other, along with how Windows XP manages users in the registry. Tools, tools, and more tools. Chapter 4, "Registry Tools and Tips: Getting the Work Done," takes a close look at the registry tools that are included with Windows XP. The Registry Editor is covered, as well as the Backup utility and the registry software that is included in the Windows XP Resource Kit. In Chapter 5, "Policies: Good for One, Good for All," you learn all about policies in Windows XP. Policies affect specific computers, users, and groups. Part II: Advanced Registry Stuff In this second part of the book, I cover OLE (Object Linking and Embedding), some history of the win.ini and system.ini files, how to remove excess baggage from the registry, registry programming interfaces, and the Performance Monitor entries.
Load more

Recommended publications
  • Tadiran-Coral-Voicemail-User-Guide-Steadfasttelecom.Com .Pdf
    Coral Message Center (CMC) User Guide Version 2.1 for Windows The flexible way to communicate . © 2002-2003 Active Voice LLC To access your mailbox from inside your organization All rights reserved. First edition 2003. 1. Call the voice messaging system. 1 for Yes, 2 for No, PhoneBASIC, Repartee, TeLANophy, 2. When the system greets you, enter: ViewCall, and ViewMail are trademarks of Active Voice, LLC. Personal ID ______________________________________________________ All other brands and product names used in this docu- ment are trademarks of their respective owners. Security code (if required) ___________________________________________ Licensed under one or more of the following patents: U.S. Nos. 4,994,926; 5,291,302; 5,459,584; 4,696,028; To access your mailbox by computer 4,809,321; 4,850,012; 4,922,526; 4,935,958; 4,955,047; 1. Launch Mailbox Manager. 4,972,469; 4,975,941; 5,020,095; 5,027,384; 5,029,196; 5,099,509; 5,109,405; 5,148,478; 5,166,974; 5,168,519; 2. When the system greets you, enter: 5,249,219; 5,303,298; 5,309,504; 5,347,574; 5,666,401; 5,181,243; 5,724,408; and Canadian No. 1329852. Host name_______________________________________________________ Extension _______________________________________________________ Security Code _____________________________________________________ For assistance, call: Name___________________________________________________________ Extension _______________________________________________________ Contents Introduction ii Changing your mailbox setup 21 Using quick message actions and shortcuts 47 Setting up your mailbox .......................................iv Working with the Mailbox Manager ....................22 Changing your security code..............................24 Quick message actions ...................................... 48 Checking and leaving messages 1 Changing your recorded and spelled names......25 Shortcuts...........................................................
    [Show full text]
  • Investigating Powershell Attacks
    Investigating PowerShell Attacks Black Hat USA 2014 August 7, 2014 PRESENTED BY: Ryan Kazanciyan, Matt Hastings © Mandiant, A FireEye Company. All rights reserved. Background Case Study WinRM, Victim VPN SMB, NetBIOS Attacker Victim workstations, Client servers § Fortune 100 organization § Command-and-control via § Compromised for > 3 years § Scheduled tasks § Active Directory § Local execution of § Authenticated access to PowerShell scripts corporate VPN § PowerShell Remoting © Mandiant, A FireEye Company. All rights reserved. 2 Why PowerShell? It can do almost anything… Execute commands Download files from the internet Reflectively load / inject code Interface with Win32 API Enumerate files Interact with the registry Interact with services Examine processes Retrieve event logs Access .NET framework © Mandiant, A FireEye Company. All rights reserved. 3 PowerShell Attack Tools § PowerSploit § Posh-SecMod § Reconnaissance § Veil-PowerView § Code execution § Metasploit § DLL injection § More to come… § Credential harvesting § Reverse engineering § Nishang © Mandiant, A FireEye Company. All rights reserved. 4 PowerShell Malware in the Wild © Mandiant, A FireEye Company. All rights reserved. 5 Investigation Methodology WinRM PowerShell Remoting evil.ps1 backdoor.ps1 Local PowerShell script Persistent PowerShell Network Registry File System Event Logs Memory Traffic Sources of Evidence © Mandiant, A FireEye Company. All rights reserved. 6 Attacker Assumptions § Has admin (local or domain) on target system § Has network access to needed ports on target system § Can use other remote command execution methods to: § Enable execution of unsigned PS scripts § Enable PS remoting © Mandiant, A FireEye Company. All rights reserved. 7 Version Reference 2.0 3.0 4.0 Requires WMF Requires WMF Default (SP1) 3.0 Update 4.0 Update Requires WMF Requires WMF Default (R2 SP1) 3.0 Update 4.0 Update Requires WMF Default 4.0 Update Default Default Default (R2) © Mandiant, A FireEye Company.
    [Show full text]
  • Common Tasks
    Common Tasks • Browser Settings for Internet Explorer, on page 1 • Browser Settings for Firefox, on page 2 • Sign In to Finesse Desktop, on page 3 • Accept Security Certificates, on page 4 • Accept Certificates for Live Data Gadget, on page 6 • Accept Certificates for Multi-session Chat and Email, on page 7 • Sign Out of the Finesse Desktop, on page 7 • Live Data Reports, on page 8 • View My History, on page 9 • View Context Service Data, on page 10 Browser Settings for Internet Explorer If Internet Explorer is used to access the Finesse desktop, certain settings must be configured in the browser to ensure all features of Finesse work properly. 1. Disable pop-up blockers. Finesse does not support Compatibility View. Make sure the desktop is not running in Compatibility View. 2. Configure the following privacy and advanced settings: a. From the browser menu, select Tools > Internet Options. b. Click the Privacy tab. c. Click Sites. d. In the Address of website box, enter the domain name for the Side A Finesse server. e. Click Allow. f. In the Address of website box, enter the domain name for the Side B Finesse server. g. Click Allow. h. Click OK. Common Tasks 1 Common Tasks Browser Settings for Firefox 3. You must enable the following security settings to allow users to sign in: • Run ActiveX controls and plug-ins • Script ActiveX controls marked as safe for scripting • Active scripting To enable these settings: a. From the Internet Explorer browser menu, select Tools > Internet Options. b. Click the Security tab. c. Click Custom level.
    [Show full text]
  • Microsoft Windows 95 Reviewer’S Guide
    1 CHAPTER 10 Systems Management Windows 95 is the first version of Windows expressly designed for manageability. The design ensures that management of the Windows 95 PC is accessible both locally and remotely via a privileged network manager. Network security is used to determine administrator-privileged accounts using pass-through security. Windows 95 also provides for PC users to be logically separated from the underlying configuration of their PCs so that the PC and user configurations and privileges can be managed independently. As a result, network managers can allow users to “rove” on the network—that is, log on from virtually any PC on the network and then operate from a desktop that has the correct settings and network privileges. The logical separation also means that a single PC can be shared by multiple users, each with a different desktop configuration and different network privileges. Given the proliferation of PCs connected to corporate networks, the Windows 95 PC must be able to participate in any network-wide management schemes. Windows 95 is designed to meet various network management criteria by providing built-in support for several of the key network management standards. With this infrastructure built into Windows 95, network management applications will be able to provide tools for network managers to keep PCs and networks running more efficiently and cost effectively. Open management interfaces are key to the management implementation in Windows 95. Where a standard exists, Windows 95 implements an enabling technology to embrace the standard—for example, an SNMP agent is supplied to enable remote management of Windows 95 PCs via any number of third-party SNMP consoles.
    [Show full text]
  • Hacks, Cracks, and Crime: an Examination of the Subculture and Social Organization of Computer Hackers Thomas Jeffrey Holt University of Missouri-St
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by University of Missouri, St. Louis University of Missouri, St. Louis IRL @ UMSL Dissertations UMSL Graduate Works 11-22-2005 Hacks, Cracks, and Crime: An Examination of the Subculture and Social Organization of Computer Hackers Thomas Jeffrey Holt University of Missouri-St. Louis, [email protected] Follow this and additional works at: https://irl.umsl.edu/dissertation Part of the Criminology and Criminal Justice Commons Recommended Citation Holt, Thomas Jeffrey, "Hacks, Cracks, and Crime: An Examination of the Subculture and Social Organization of Computer Hackers" (2005). Dissertations. 616. https://irl.umsl.edu/dissertation/616 This Dissertation is brought to you for free and open access by the UMSL Graduate Works at IRL @ UMSL. It has been accepted for inclusion in Dissertations by an authorized administrator of IRL @ UMSL. For more information, please contact [email protected]. Hacks, Cracks, and Crime: An Examination of the Subculture and Social Organization of Computer Hackers by THOMAS J. HOLT M.A., Criminology and Criminal Justice, University of Missouri- St. Louis, 2003 B.A., Criminology and Criminal Justice, University of Missouri- St. Louis, 2000 A DISSERTATION Submitted to the Graduate School of the UNIVERSITY OF MISSOURI- ST. LOUIS In partial Fulfillment of the Requirements for the Degree DOCTOR OF PHILOSOPHY in Criminology and Criminal Justice August, 2005 Advisory Committee Jody Miller, Ph. D. Chairperson Scott H. Decker, Ph. D. G. David Curry, Ph. D. Vicki Sauter, Ph. D. Copyright 2005 by Thomas Jeffrey Holt All Rights Reserved Holt, Thomas, 2005, UMSL, p.
    [Show full text]
  • Internet Explorer 9 Features
    m National Institute of Information Technologies NIIT White Paper On “What is New in Internet Explorer 9” Submitted by: Md. Yusuf Hasan Student ID: S093022200027 Year: 1st Quarter: 2nd Program: M.M.S Date - 08 June 2010 Dhaka - Bangladesh Internet Explorer History Abstract: In the early 90s—the dawn of history as far as the World Wide Web is concerned—relatively few users were communicating across this Internet Explorer 9 (abbreviated as IE9) is the upcoming global network. They used an assortment of shareware and other version of the Internet Explorer web browser from software for Microsoft Windows operating system. In 1995, Microsoft Microsoft. It is currently in development, but developer hosted an Internet Strategy Day and announced its commitment to adding Internet capabilities to all its products. In fulfillment of that previews have been released. announcement, Microsoft Internet Explorer arrived as both a graphical Web browser and the name for a set of technologies. IE9 will have complete or nearly complete support for all 1995: Internet Explorer 1.0: In July 1995, Microsoft released the CSS 3 selectors, border-radius CSS 3 property, faster Windows 95 operating system, which included built-in support for JavaScript and embedded ICC v2 or v4 color profiles dial-up networking and TCP/IP (Transmission Control support via Windows Color System. IE9 will feature Protocol/Internet Protocol), key technologies for connecting to the hardware accelerated graphics rendering using Direct2D, Internet. In response to the growing public interest in the Internet, Microsoft created an add-on to the operating system called Internet hardware accelerated text rendering using Direct Write, Explorer 1.0.
    [Show full text]
  • Powershell Delete Registry Key Remote Computer
    Powershell delete registry key remote computer In Use PowerShell to Edit the Registry on Remote Computers, I talked cmdlet to find and delete the registry key on all remote servers that are. There is a pre powershell registry tool called reg. It will perform registry operations on remote computers. REG DELETE /? REG DELETE. I am trying to create a PowerShell script that deletes two keys on a remote computer. (One key in the code below) I have successfully created a. The Remove-RegistryKey cmdlet is used to delete registry keys and values on the local or a remote computer. I'm working on remotely modifying an autologin key value on batches of {Remove-ItemProperty -Path "HKLM:\Software\Microsoft\Windows Solution: $Computers = Get-Content "C:\"$Path me with a powershell script that can modify registry key on a list of remote computers Basically, I need to modify a product name in add/remove programs list. Then I need to find out whether I got the admin permission on the remote machines. Lastly, remove the specified reg keys. #Read the machine. Deleting Specific Remote Registry Entry - Powershell playing about with trying to write a script to delete a specific software GPO deployed to a remote computer. $Items = $Keys | Foreach-Object {Get-ItemProperty $_. $RegistryKeyValue = $ue($RegistryKeyName) Write-output "Attempting to delete $RegistryKeyName on $Computer `r ". Powershell: Delete Registry Key On Remote Server To run a script on one or many remote computers, use the FilePath parameter of the. I am having trouble changing registry keys. I know the trouble is Set-ItemProperty does not support connections to remote computers.
    [Show full text]
  • Dell Server Administrator Installation Version 7.4 Release Notes
    Server Administrator Installation and Management 7.4.0 Release Notes Version 7.4.0 Release Date: March 2014 Previous Version 7.3.0 Importance RECOMMENDED: Dell recommends applying this update during your next scheduled update cycle. The update contains feature enhancements or changes that will help keep your system software current and compatible with other system modules (firmware, BIOS, drivers and software). What’s New • Intel and Broadcom SNMP Agents 64-bit versions are available as part of the 64-bit server administrator installer. • srvadmin-cm RPM 64-bit version is available as part of the 64-bit Linux installer stack for all supported Linux flavors. Installation • To install Server Administrator on Windows Server 2008 R2 SP1 Core and Windows Server 2012 Core, Windows-on-Windows (WOW) mode must be enabled. • On Microsoft Windows operating systems, run setup.exe from the SYSMGMT\srvadmin\windows directory of the DVD or the software package. Note: This step is not necessary if the DVD runs automatically. • On the Red Hat Enterprise Linux and SUSE Linux Enterprise Server operating systems, to perform an Express Install, execute srvadmin-install.sh -x from the SYSMGMT/srvadmin/linux/supportscripts directory For more information on installation instructions, including silent installation options, see the Server Administrator Installation Guide. User Notes for Supported Windows Operating Systems In the Prerequisite Checker screen, you may get the following message: An error occurred while attempting to execute a Visual Basic Script. Please confirm that Visual Basic files are installed correctly. This error occurs when the Prerequisite Checker calls the vbstest.vbs (a Visual Basic [VB]) script to verify the installation environment and fails for some reason.
    [Show full text]
  • Resolving Issues with Forms
    C1261587x.fm Page 265 Thursday, November 15, 2001 3:51 PM Resolving Issues with Forms In 1988, Alan Cooper demonstrated a prototype called Ruby to Bill Gates. Ruby provided a form designer that allowed you to drag and drop controls, then known as gizmos, to quickly and easily create composite forms—such as dialog boxes, entry forms, and report forms. Microsoft took Cooper’s Ruby product and combined it with Basic to create Microsoft Visual Basic 1. Microsoft has since shipped a version of Ruby with every version of Visual Basic, versions 1 through 6. With every version, that is, until Visual Basic .NET. Visual Basic .NET provides a new forms package called Windows Forms. Although the Windows Forms package was designed using the same basic prin- ciple as Ruby—it is a form designer that allows you to drag and drop controls and set properties—it was never meant to be an extension of, nor to be com- patible with, Ruby. Therefore, there are fundamental differences between the two forms packages that affect the way you create Visual Basic applications. This chapter focuses on some of the fundamental differences between the Ruby and Windows Forms packages. Specifically, it discusses issues that the Upgrade Wizard does not handle for you. Before we get into the differences, however, let’s look at what Windows Forms and Ruby have in common. Similarities in Form Structure When you create a new project in Visual Basic .NET, you will find yourself at home in the environment. The way you create and design forms is the same in Visual Basic .NET as it is in Visual Basic 6.
    [Show full text]
  • Oracle Grid Infrastructure Installation Guide for Linux
    Oracle® Grid Infrastructure Installation Guide 11g Release 2 (11.2) for Microsoft Windows x64 (64-Bit) E24169-04 May 2012 Oracle Grid Infrastructure Installation Guide, 11g Release 2 (11.2) for Microsoft Windows x64 (64-Bit) E24169-04 Copyright © 2007, 2012, Oracle and/or its affiliates. All rights reserved. Primary Authors: Janet Stern, Douglas Williams Contributing Authors: Mark Bauer, Jonathan Creighton, Reema Khosla, Barb Lundhild, Saar Maoz, Markus Michalewicz, Philip Newlan, Hanlin Qian Contributors: Karin Brandauer, Barbara Glover, Sujatha Srinivasa Gopalan, Shivanand Hiremath, Yingwei Hu, Wei Huang, Scott Jesse, Sameer Joshi, Alexander Keh, Jai Krishnani, Jifeng Liu, Fangya Lu, Anil Nair, Mohammed Shahnawaz Quadri, Sudhe Sampath, Vishal Saxena, Janelle Simmons, Malaiarasan Stalin, Richard Strohm, Preethi Subramanyam, Preethi Vallam, Zhiqiang Yang This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S.
    [Show full text]
  • Tracking Computer Use with the Windows® Registry Dataset Doug
    Tracking Computer Use with the Windows® Registry Dataset Doug White Disclaimer Trade names and company products are mentioned in the text or identified. In no case does such identification imply recommendation or endorsement by the National Institute of Standards and Technology, nor does it imply that the products are necessarily the best available for the purpose. Statement of Disclosure This research was funded by the National Institute of Standards and Technology Office of Law Enforcement Standards, the Department of Justice National Institute of Justice, the Federal Bureau of Investigation and the National Archives and Records Administration. National Software Reference Library & Reference Data Set The NSRL is conceptually three objects: • A physical collection of software • A database of meta-information • A subset of the database, the Reference Data Set The NSRL is designed to collect software from various sources and incorporate file profiles computed from this software into a Reference Data Set of information. Windows® Registry Data Set It is possible to compile a historical list of applications based on RDS metadata and residue files. Many methods can be used to remove application files, but these may not purge the Registry. Examining the Registry for residue can augment a historical list of applications or provide additional context about system use. Windows® Registry Data Set (WiReD) The WiReD contains changes to the Registry caused by application installation, de-installation, execution or other modifying operations. The applications are chosen from the NSRL collection, to be of interest to computer forensic examiners. WiReD is currently an experimental prototype. NIST is soliciting feedback from the computer forensics community to improve and extend its usefulness.
    [Show full text]
  • Vmware Vrealize Configuration Manager Installation Guide Vrealize Configuration Manager 5.8
    VMware vRealize Configuration Manager Installation Guide vRealize Configuration Manager 5.8 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document, see http://www.vmware.com/support/pubs. EN-001815-00 vRealize Configuration Manager Installation Guide You can find the most up-to-date technical documentation on the VMware Web site at: Copyright http://www.vmware.com/support/ The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: [email protected] © 2006–2015 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed at http://www.vmware.com/go/patents. VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies. VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com 2 VMware, Inc. Contents About This Book 5 Preparing to Install VCM 7 Typical or Advanced Installation 7 VCM Installation Configurations 8 Create VCM Domain Accounts 8 VCM Account Configuration 9 VCM Administrator Account 10 VCM User Accounts 10 Service Accounts 10 Network Authority Account 11 ECMSRSUser Account 12 SQL Server Permissions and Constructs 12 Gather Supporting Software
    [Show full text]