DOCSLIB.ORG

Dell Hybrid Client Version 1.X Conversion and Upgrade Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Dell Hybrid Client Version 1.x Conversion and Upgrade Guide March 2021 Rev. A01 Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2020 2021 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners. Contents Chapter 1: Introduction................................................................................................................. 4 Chapter 2: Supported platforms for Dell Hybrid Client conversion................................................ 5 Supported management software...................................................................................................................................6 Chapter 3: Dell Hybrid Client 1.0 or 1.1 to Dell Hybrid Client 1.5 upgrade........................................7 Chapter 4: Convert Dell Wyse 5070 devices to Dell Hybrid Client................................................. 12 Dell Wyse 5070 Conversion ............................................................................................................................................12 Adding Dell Hybrid Client images to repository.....................................................................................................13 Creating Hybrid Client image policies......................................................................................................................14 Scheduling the image policy...................................................................................................................................... 14 Chapter 5: Convert Dell Generic Client to Dell Hybrid Client........................................................ 16 Chapter 6: Upgrade from Dell Hybrid Client version 1.0 to 1.1.......................................................17 Install the application using public cloud Wyse Management Suite.......................................................................17 Install the application using on-premises Wyse Management Suite......................................................................18 Download the installation file from Dell support site ................................................................................................18 Chapter 7: Dell OptiPlex and Latitude conversions....................................................................... 19 Chapter 8: Frequently asked questions........................................................................................20 Chapter 9: Contacting Dell.......................................................................................................... 23 Contents 3 1 Introduction Dell Hybrid Client is a desktop solution by Dell that follows the Software-as-a-Service (SaaS) model of software delivery. It provides a hybrid operating environment that enables you to access virtual, cloud, or local applications and resources seamlessly. It encompasses the cloud and storage aggregation for maintaining security and simplicity. You must use a management software to configure, operate, and update devices that are powered by Dell Hybrid Client, thereby eliminating the need for IT support to visit the physical devices. You can manage the devices by using Wyse Management Suite Pro. Wyse Management Suite offers process automation and helps lower costs for large deployments of devices that are powered by Dell Hybrid Client. Using secure HTTPS-based communication and Active Directory authentication for role-based administration, Wyse Management Suite keeps your devices up to date. The Wyse Management Suite mobile application enables administrators to view critical alerts, notifications on the dashboard, and send real-time command. This guide contains instructions to convert the devices running Windows 10 IoT Enterprise LTSB, Windows 10 IoT Enterprise LTSC, ThinLinux 2.x, and ThinOS 8.6 to Dell Hybrid Client using Wyse Management Suite Pro 3.x or later. This guide also provides information to upgrade the devices running Ubuntu 18.04 or 20.04 to Dell Hybrid Client using Wyse Management Suite Pro 3.x or later. The target audience for this guide is enterprise customers with administrator privileges. 4 Introduction 2 Supported platforms for Dell Hybrid Client conversion Table 1. Supported platforms and configurations for DHC 1.5 Configuration Platform Operating System Processor Memory Storage Wyse 5070 Intel Celeron Dual Core Windows 10 IoT Enterprise LTSB, Windows 10 IoT Intel Pentium Quad 32 GB eMMC/SSD and 64 Enterprise LTSC, Dell Hybrid Core GB SSD Client 1.0 and Dell Hybrid Wyse 5070 Intel Pentium Quad Client 1.1 Extended Core OptiPlex 7070 Ultra 8th Generation Intel Ubuntu 18.04 and Windows 8 GB and higher Core i3/i5/i7 10 OptiPlex 3090 Ultra 11th Generation Intel Ubuntu 20.04 + Dell Client Core i3/i5 32 GB eMMC/128 GB and Agent Enabler and Windows 10 OptiPlex 7090 Ultra 11th Generation Intel higher capacity SSD or HDD Core i3/i5 /i7 Latitude 3320 11th Generation Intel Core i3/i7 Table 2. Supported platforms and configurations for DHC 1.1 Platform Configuration Operating System Processor Memory Storage Wyse 5070 Intel Celeron Dual 4 GB and higher 16 GB or higher capacity ThinLinux 2.x and ThinOS Core SSD or eMMC 8.6 Intel Pentium Quad Core Wyse 5070 Extended Intel Pentium Quad Core Wyse 5070 Intel Celeron Dual 4 GB and higher 32 GB eMMC and 64 GB Windows 10 IoT Enterprise Core SSD LTSB and Windows 10 IoT Enterprise LTSC Intel Pentium Quad 64 GB SSD Core Wyse 5070 Extended Intel Pentium Quad 64 GB and 128 GB SSD Core OptiPlex 7070 Ultra 8th Generation 64 GB and 128 GB SSD Ubuntu 18.04 and Windows Intel Core i3/i5/i7 10 Topics: • Supported management software Supported platforms for Dell Hybrid Client conversion 5 Supported management software Table 3. Supported management software for DHC 1.5 Supported environment Management software Wyse Management Suite Edition Pro Version 3.2 and later Table 4. Supported management software for DHC 1.1 Supported environment Management software Wyse Management Suite Edition Pro Version 3.1 and later 6 Supported platforms for Dell Hybrid Client conversion 3 Dell Hybrid Client 1.0 or 1.1 to Dell Hybrid Client 1.5 upgrade Prerequisites ● Download the Dell Hybrid Client 1.5 - Image upgrade addon package from the Drivers and Downloads section of the Dell Hybrid Client product page or the respective hardware product pages at www.dell.com/support. ● Download the ISO image corresponding to your platform model: ○ Dell Hybrid Client 1.5 - ISO Conversion Image for Wyse 5070 ○ Dell Hybrid Client 1.5 - ISO Conversion Image for 7070 Optiplex Ultra ● Extract the ISO file from the downloaded zip file. Steps 1. Go to Groups & Configs and click the device group, DHC-DEV-GRP, where the Dell Hybrid Client 1.0 or 1.1 devices are registered. You can rename the device group. 2. Create two device subgroups. For example, DhcUpgradeStageNotify and DhcUpgradeStageUpgrade inside the device group, DHC-DEV-GRP. You can rename both the device subgroups. Figure 1. Device sub-groups 3. Copy the image upgrade add-on DHCImageUpgradeAddon.tar.gz and image upgrade iso file DellHybridClient_1.5_750_5070.iso or DellHybridClient_1.5_750_7070.iso corresponding to the platform model to the Wyse Management Suite local repository—<RepoPath>\repository\hybridClientApps>. For example, C: \WMSRepo3\repository\hybridClientApps. Dell Hybrid Client 1.0 or 1.1 to Dell Hybrid Client 1.5 upgrade 7 Figure 2. Wyse Management Suite local repository 4. Move the devices to be converted to the subgroup, DhcUpgradeStageNotify. Figure 3. DhcUpgradeStageNotify 5. Select the subgroup, DhcUpgradeStageNotify and send notifications to the devices in the group using SendMessage in Wyse Management Suite for user data backup. An administrator can confirm that all the SendMessage alerts are successful on the Events tab. 8 Dell Hybrid Client 1.0 or 1.1 to Dell Hybrid Client 1.5 upgrade Figure 4. SendMessage 6. Once the defined number of days for user data backup elapses, the administrator can move the devices which have received the notification to the subgroup, DhcUpgradeStageUpgrade. Figure 5. DhcUpgradeStageUpgrade 7. Go to Apps & Data and create the advanced app policy, DHC1.5 Upgrade for the subgroup, DhcUpgradeStageUpgrade to install Image upgrade add-on and the ISO conversion image respectively. Check the Enable app dependency option to ensure that the image add-on is installed first followed by the ISO image. NOTE: You must create the app policy for operating system subtype Ubuntu 18.04. Dell Hybrid Client 1.0 or 1.1 to Dell Hybrid Client 1.5 upgrade 9 Figure 6. Install Image upgrade add-on and the ISO conversion image 8. If you have not configured the policy to apply on check-in, you can create the job for the DHC1.5 Upgrade app policy to install the add-on on the devices in the subgroup DhcUpgradeStageUpgrade. Figure 7. DhcUpgradeStageUpgrade group 9. Once the job is successful the devices will upgrade to Ubuntu 20.04 with Dell Hybrid Client 1.5 and re-register to the subgroup, DhcUpgradeStageUpgrade. 10 Dell Hybrid Client 1.0 or 1.1 to Dell Hybrid Client 1.5 upgrade Figure 8. Upgrade successful Dell Hybrid Client 1.0 or 1.1 to Dell Hybrid Client 1.5 upgrade 11 4 Convert Dell Wyse 5070 devices
Recommended publications
  • Ubuntu Kung Fu

    Ubuntu Kung Fu

    Prepared exclusively for Alison Tyler Download at Boykma.Com What readers are saying about Ubuntu Kung Fu Ubuntu Kung Fu is excellent. The tips are fun and the hope of discov- ering hidden gems makes it a worthwhile task. John Southern Former editor of Linux Magazine I enjoyed Ubuntu Kung Fu and learned some new things. I would rec- ommend this book—nice tips and a lot of fun to be had. Carthik Sharma Creator of the Ubuntu Blog (http://ubuntu.wordpress.com) Wow! There are some great tips here! I have used Ubuntu since April 2005, starting with version 5.04. I found much in this book to inspire me and to teach me, and it answered lingering questions I didn’t know I had. The book is a good resource that I will gladly recommend to both newcomers and veteran users. Matthew Helmke Administrator, Ubuntu Forums Ubuntu Kung Fu is a fantastic compendium of useful, uncommon Ubuntu knowledge. Eric Hewitt Consultant, LiveLogic, LLC Prepared exclusively for Alison Tyler Download at Boykma.Com Ubuntu Kung Fu Tips, Tricks, Hints, and Hacks Keir Thomas The Pragmatic Bookshelf Raleigh, North Carolina Dallas, Texas Prepared exclusively for Alison Tyler Download at Boykma.Com Many of the designations used by manufacturers and sellers to distinguish their prod- ucts are claimed as trademarks. Where those designations appear in this book, and The Pragmatic Programmers, LLC was aware of a trademark claim, the designations have been printed in initial capital letters or in all capitals. The Pragmatic Starter Kit, The Pragmatic Programmer, Pragmatic Programming, Pragmatic Bookshelf and the linking g device are trademarks of The Pragmatic Programmers, LLC.
  • An User & Developer Perspective on Immutable Oses

    An User & Developer Perspective on Immutable Oses

    An User & Developer Perspective on Dario Faggioli Virtualization SW. Eng. @ SUSE Immutable OSes [email protected] dariof @DarioFaggioli https://dariofaggioli.wordpress.com/ https://about.me/dario.faggioli About Me What I do ● Virtualization Specialist Sw. Eng. @ SUSE since 2018, working on Xen, KVM, QEMU, mostly about performance related stuff ● Daily activities ⇒ how and what for I use my workstation ○ Read and send emails (Evolution, git-send-email, stg mail, ...) ○ Write, build & test code (Xen, KVM, Libvirt, QEMU) ○ Work with the Open Build Service (OBS) ○ Browse Web ○ Test OSes in VMs ○ Meetings / Video calls / Online conferences ○ Chat, work and personal ○ Some 3D Printing ○ Occasionally play games ○ Occasional video-editing ○ Maybe scan / print some document 2 ● Can all of the above be done with an immutable OS ? Immutable OS: What ? Either: ● An OS that you cannot modify Or, at least: ● An OS that you will have an hard time modifying What do you mean “modify” ? ● E.g., installing packages ● ⇒ An OS on which you cannot install packages ● ⇒ An OS on which you will have an hard time installing packages 3 Immutable OS: What ? Seriously? 4 Immutable OS: Why ? Because it will stay clean and hard to break ● Does this sound familiar? ○ Let’s install foo, and it’s dependency, libfoobar_1 ○ Let’s install bar (depends from libfoobar_1, we have it already) ○ Actually, let’s add an external repo. It has libfoobar_2 that makes foo work better! ○ Oh no... libfoobar_2 would break bar!! ● Yeah. It happens. Even in the best families distros
  • Downloads." the Open Information Security Foundation

    Downloads." the Open Information Security Foundation

    Performance Testing Suricata The Effect of Configuration Variables On Offline Suricata Performance A Project Completed for CS 6266 Under Jonathon T. Giffin, Assistant Professor, Georgia Institute of Technology by Winston H Messer Project Advisor: Matt Jonkman, President, Open Information Security Foundation December 2011 Messer ii Abstract The Suricata IDS/IPS engine, a viable alternative to Snort, has a multitude of potential configurations. A simplified automated testing system was devised for the purpose of performance testing Suricata in an offline environment. Of the available configuration variables, seventeen were analyzed independently by testing in fifty-six configurations. Of these, three variables were found to have a statistically significant effect on performance: Detect Engine Profile, Multi Pattern Algorithm, and CPU affinity. Acknowledgements In writing the final report on this endeavor, I would like to start by thanking four people who made this project possible: Matt Jonkman, President, Open Information Security Foundation: For allowing me the opportunity to carry out this project under his supervision. Victor Julien, Lead Programmer, Open Information Security Foundation and Anne-Fleur Koolstra, Documentation Specialist, Open Information Security Foundation: For their willingness to share their wisdom and experience of Suricata via email for the past four months. John M. Weathersby, Jr., Executive Director, Open Source Software Institute: For allowing me the use of Institute equipment for the creation of a suitable testing
  • Multi Software Product Lines in the Wild

    Multi Software Product Lines in the Wild

    AperTO - Archivio Istituzionale Open Access dell'Università di Torino Multi software product lines in the wild This is the author's manuscript Original Citation: Availability: This version is available http://hdl.handle.net/2318/1667454 since 2020-07-06T10:51:50Z Publisher: Association for Computing Machinery Published version: DOI:10.1145/3168365.3170425 Terms of use: Open Access Anyone can freely access the full text of works made available as "Open Access". Works made available under a Creative Commons license can be used according to the terms and conditions of said license. Use of all other works requires consent of the right holder (author or publisher) if not exempted from copyright protection by the applicable law. (Article begins on next page) 27 September 2021 Multi Software Product Lines in the Wild Michael Lienhardt Ferruccio Damiani [email protected] [email protected] Università di Torino Università di Torino Italy Italy Simone Donetti Luca Paolini [email protected] [email protected] Università di Torino Università di Torino Italy Italy ABSTRACT 1 INTRODUCTION Modern software systems are often built from customizable and A Software Product Line (SPL) is a set of similar programs, called inter-dependent components. Such customizations usually define variants, with a common code base and well documented variabil- which features are offered by the components, and may depend ity [1, 6, 19]. Modern software systems are often built as complex on backend components being configured in a specific way. As assemblages of customizable components that out-grow the expres- such system become very large, with a huge number of possible siveness of SPLs.
  • Indicators for Missing Maintainership in Collaborative Open Source Projects

    Indicators for Missing Maintainership in Collaborative Open Source Projects

    TECHNISCHE UNIVERSITÄT CAROLO-WILHELMINA ZU BRAUNSCHWEIG Studienarbeit Indicators for Missing Maintainership in Collaborative Open Source Projects Andre Klapper February 04, 2013 Institute of Software Engineering and Automotive Informatics Prof. Dr.-Ing. Ina Schaefer Supervisor: Michael Dukaczewski Affidavit Hereby I, Andre Klapper, declare that I wrote the present thesis without any assis- tance from third parties and without any sources than those indicated in the thesis itself. Braunschweig / Prague, February 04, 2013 Abstract The thesis provides an attempt to use freely accessible metadata in order to identify missing maintainership in free and open source software projects by querying various data sources and rating the gathered information. GNOME and Apache are used as case studies. License This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported (CC BY-SA 3.0) license. Keywords Maintenance, Activity, Open Source, Free Software, Metrics, Metadata, DOAP Contents List of Tablesx 1 Introduction1 1.1 Problem and Motivation.........................1 1.2 Objective.................................2 1.3 Outline...................................3 2 Theoretical Background4 2.1 Reasons for Inactivity..........................4 2.2 Problems Caused by Inactivity......................4 2.3 Ways to Pass Maintainership.......................5 3 Data Sources in Projects7 3.1 Identification and Accessibility......................7 3.2 Potential Sources and their Exploitability................7 3.2.1 Code Repositories.........................8 3.2.2 Mailing Lists...........................9 3.2.3 IRC Chat.............................9 3.2.4 Wikis............................... 10 3.2.5 Issue Tracking Systems...................... 11 3.2.6 Forums............................... 12 3.2.7 Releases.............................. 12 3.2.8 Patch Review........................... 13 3.2.9 Social Media............................ 13 3.2.10 Other Sources..........................
  • Gstreamer Past – Present - Future

    Gstreamer Past – Present - Future

    GStreamer Past – Present - Future Wim Taymans ([email protected]) 26 oct 2010 – GStreamer Conference Cambridge, UK Overview Past ● Started in early 1999 by Eric Walthinsen – Based on OGI reseach – Ideas from DirectShow – C, G(tk)Object ● State of multimedia on linux was very poor back then – Xanim† (vlc 1999, Ogle† 1999, xine† 2000, mplayer 2000, ffmpeg 2000, ...) – No codec libraries ● Make something that can compete with Quicktime (1991) /DirectShow†(1996) Use cases ● Music players (Rhythmbox, Songbird,..) ● Video players (Totem, Webkit,...) ● Streaming servers (Axis, UbiCast, Flumotion, RTSP, DLNA server...) ● Transcoding (Arista, Transmageddon, …) ● Media capture (Cheese, N900, …) ● Audio editing (Jokosher, ..) ● Video editing (PiTiVi, …) ● VoIP (Empathy, Tandberg, ...) ● Desktop, embedded History ● 0.0.1 – Jun 1999 (POC) ● 0.1.0 – Jan 2001 ● 0.2.0 – Jun 2001 ● 0.3.0 – Dec 2001 ● 0.4.0 – Jul 2002 (in gnome, very rough) ● 0.6.0 – Feb 2003 (audio works ok) ● 0.8.0 – Mar 2004 (video works okish) ● 0.10.0 – Dec 2005 (redesign, maturity) – Currently 0.10.30 ● 1.0 - ??? Stats ● large community – 30+ core developers – 200+ contributers ● Core 205K LOC ● Plugins +1M LOC ● Estimated cost +$60M ● Many contributers work for companies nowadays – Many fulltime Overall commits per month Core commits per month plugins-good commits per month overall lines of code Core lines of code Plugins-good lines of code Some Features ● Fully multithreaded ● Advanced trick mode playback ● Video editing support ● Top notch RTP/streaming support ● Extensive,
  • Make the Switch: Novell's Guide to the Novell® Linux® Desktop

    Make the Switch: Novell's Guide to the Novell® Linux® Desktop

    Make the Switch: Novell's Guide to the Novell® Linux® Desktop Novell Training Services www.novell.com COURSE 3056 AUTHORIZED COURSEWARE 106-001301-001 Make the Switch Novell Linux Desktop (c) 2004 Novell Inc. Proprietary Statement Copyright 2004 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express prior consent of the publisher. This manual, and any portion thereof, may not be copied without the express written permission of Novell, Inc. Novell, Inc. 1800 South Novell Place Provo, UT 84606 Disclaimer Novell, Inc. makes no representations or warranties with respect to the contents or use of this manual, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes in its content at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc. makes no representations or warranties with respect to any of its software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of its software at any time, without obligation to notify any person or entity of such changes. This Novell Training Manual is published solely to instruct students in the use of Novell networking software. Although third-party application software packages are used in Novell training courses, this is for demonstration purposes only and shall not constitute an endorsement of any of these software applications.
  • Pipewire Slides

    Pipewire Slides

    PipeWire Wim Taymans Principal Software Engineer FOSDEM 2019 1 PipeWire | Wim Taymans What is it Multimedia sharing and processing engine 6 PipeWire | Wim Taymans The multimedia stack App Browser Skype GStreamer VLC Ardour Pulseaudio JACK wayland V4l2 bluetooth alsa va-api DRM Kernel 7 PipeWire | Wim Taymans PipeWire App Session Manager GStreamer VLC App1 App2 JACK Wayland PipeWire Daemon V4l2 bluetooth alsa va-api DRM Kernel 8 PipeWire | Wim Taymans Features ● Exchange media with devices and other apps ● Zero copy, shared memory, memfd, dmabuf, eventfd ● Security per application ● Visible objects (R), methods (WX), .. ● RT capable, low latency (<1.5ms) ● All media types + generic control streams ● Simple JACK-like scheduler + feedback loops ● Extensible: types, protocol, ... ● External session manager implements policy 21 PipeWire | Wim Taymans Session manager ● Setup of devices ● DSP processing, effects, mixers, .. ● Security of clients ● What they can see, default permissions ● Management of links/nodes in the graph ● What nodes and effects to link to (profiles, roles, ..) ● Suspend of idle devices, volume restore, … ● The things you want to configure 22 PipeWire | Wim Taymans V4l2 capture/sharing Client1 Client2 ... To screen PipeWire-0 V4l2 bluetooth alsa va-api DRM Kernel 23 PipeWire | Wim Taymans Video capture ● Systemd socket activation in Fedora 29 ● Gstreamer pipewiresrc ● Device Monitor ● Autovideosrc → Should work in cheese 24 PipeWire | Wim Taymans 25 PipeWire | Wim Taymans Wayland screen sharing Mutter Screen Recording Remote
  • Debian and Ubuntu

    Debian and Ubuntu

    Debian and Ubuntu Lucas Nussbaum lucas@{debian.org,ubuntu.com} lucas@{debian.org,ubuntu.com} Debian and Ubuntu 1 / 28 Why I am qualified to give this talk Debian Developer and Ubuntu Developer since 2006 Involved in improving collaboration between both projects Developed/Initiated : Multidistrotools, ubuntu usertag on the BTS, improvements to the merge process, Ubuntu box on the PTS, Ubuntu column on DDPO, . Attended Debconf and UDS Friends in both communities lucas@{debian.org,ubuntu.com} Debian and Ubuntu 2 / 28 What’s in this talk ? Ubuntu development process, and how it relates to Debian Discussion of the current state of affairs "OK, what should we do now ?" lucas@{debian.org,ubuntu.com} Debian and Ubuntu 3 / 28 The Ubuntu Development Process lucas@{debian.org,ubuntu.com} Debian and Ubuntu 4 / 28 Linux distributions 101 Take software developed by upstream projects Linux, X.org, GNOME, KDE, . Put it all nicely together Standardization / Integration Quality Assurance Support Get all the fame Ubuntu has one special upstream : Debian lucas@{debian.org,ubuntu.com} Debian and Ubuntu 5 / 28 Ubuntu’s upstreams Not that simple : changes required, sometimes Toolchain changes Bugfixes Integration (Launchpad) Newer releases Often not possible to do work in Debian first lucas@{debian.org,ubuntu.com} Debian and Ubuntu 6 / 28 Ubuntu Packages Workflow lucas@{debian.org,ubuntu.com} Debian and Ubuntu 7 / 28 Ubuntu Packages Workflow Ubuntu Karmic Excluding specific packages language-(support|pack)-*, kde-l10n-*, *ubuntu*, *launchpad* Missing 4% : Newer upstream
  • Bootable Linux CD / PXE for the Remote Acquisition of Multiple Computers

    Bootable Linux CD / PXE for the Remote Acquisition of Multiple Computers

    Bootable Linux CD / PXE for the remote acquisition of multiple computers Dennis Cortjens [email protected] REPORT 5th of July, 2014 Abstract In the field of digital forensics the acquisition of multiple computers in large IT infrastructures have always been a complex and time consuming task. Especially when one doesn't know which computer to investigate and therefore needs to acquire them all. Triage software has increased the efficiency in cases like this. The software gives an indication which computers to acquire, but one still needs to disassemble and acquire storage devices of the specific computers on the crime scene. In this study two concepts of automated remote acquisition of multiple computers are researched and tested on performance. One of the concepts (based on iSCSI) is developed into a proof concept, called the Remote Acquisition Boot Environment (RABE). Although it is not yet feasible for the remote acquisition to succeed the traditional method of acquiring computers, it could make the remote acquisition a time efficient solution in the near future. Acknowledgement I would like to thank the Netherlands Forensic Institute's digital technology team for their hospitality and pleasant and stimulating work environment. I want to extend my gratitude to Zeno Geradts and Ruud Schramp for their trust and support. Contents 1 Introduction 3 1.1 Problem . .3 1.2 Position . .3 1.3 Scope . .3 1.4 Hypothesis . .4 2 Background 4 2.1 Bootable Linux CD . .4 2.2 Preboot eXecution Environment (PXE) . .5 2.3 Network File System (NFS) . .6 2.4 Internet Small Computer System Interface (iSCSI) .
  • The Sensory Evaluation of Dairy Products

    The Sensory Evaluation of Dairy Products

    The Sensory Evaluation of Dairy Products Second edition Stephanie Clark l Michael Costello l MaryAnne Drake l Floyd Bodyfelt Editors The Sensory Evaluation of Dairy Products Second edition 13 Editors Stephanie Clark Michael Costello Washington State University Washington State University Pullman, WA Pullman, WA USA USA [email protected] [email protected] MaryAnne Drake Floyd Bodyfelt North Carolina State University Oregon State University Raleigh, NC Corvallis, OR USA USA [email protected] [email protected] [email protected] ISBN: 978-0-387-77406-0 e-ISBN: 978-0-387-77408-4 DOI: 10.1007/978-0-387-77408-4 Library of Congress Control Number: 2008936131 # Springer ScienceþBusiness Media, LLC 2009 All rights reserved. This work may not be translated or copied in whole or in part without the written permission of the publisher (Springer Science+Business Media, LLC, 233 Spring Street, New York, NY 10013, USA), except for brief excerpts in connection with reviews or scholarly analysis. Use in connection with any form of information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed is forbidden. The use in this publication of trade names, trademarks, service marks, and similar terms, even if they are not identified as such, is not to be taken as an expression of opinion as to whether or not they are subject to proprietary rights. Printed on acid-free paper springer.com Preface Cheese blocks are prepared for sensory assessment by graders at anAmerican Cheese Society Cheese Competition The Sensory Evaluation of Dairy Products is intended for all persons who seek a book entirely devoted to the sensory evaluation of dairy products and modern applications of the science.
  • Food Analysis Fourth Edition

    Food Analysis Fourth Edition

    Food Analysis Fourth Edition edited by S. Suzanne Nielsen Purdue University West Lafayette, IN, USA ABC II part Compositional Analysis of Foods 6 chapter Moisture and Total Solids Analysis Robert L. Bradley, Jr. Department of Food Science, University of Wisconsin, Madison, WI 53706, USA [email protected] 6.1 Introduction 87 6.2.1.4 Types of Pans for Oven Drying 6.1.1 Importance of Moisture Assay 87 Methods 90 6.1.2 Moisture Content of Foods 87 6.2.1.5 Handling and Preparation of 6.1.3 Forms of Water in Foods 87 Pans 90 6.1.4 Sample Collection and Handling 87 6.2.1.6 Control of Surface Crust Formation 6.2 Oven Drying Methods 88 (Sand Pan Technique) 90 6.2.1 General Information 88 6.2.1.7 Calculations 91 6.2.1.1 Removal of Moisture 88 6.2.2 Forced Draft Oven 91 6.2.1.2 Decomposition of Other Food 6.2.3 Vacuum Oven 91 Constituents 89 6.2.4 Microwave Analyzer 92 6.2.1.3 Temperature Control 89 6.2.5 Infrared Drying 93 S.S. Nielsen, Food Analysis, Food Science Texts Series, DOI 10.1007/978-1-4419-1478-1_6, 85 c Springer Science+Business Media, LLC 2010 86 Part II • Compositional Analysis of Foods 6.2.6 Rapid Moisture Analyzer Technology 93 6.5.4 Infrared Analysis 99 6.3 Distillation Procedures 93 6.5.5 Freezing Point 100 6.3.1 Overview 93 6.6 Water Activity 101 6.3.2 Reflux Distillation with Immiscible 6.7 Comparison of Methods 101 Solvent 93 6.7.1 Principles 101 6.4 Chemical Method: Karl Fischer Titration 94 6.7.2 Nature of Sample 101 6.5 Physical Methods 96 6.7.3 Intended Purposes 102 6.5.1 Dielectric Method 96 6.8 Summary 102 6.5.2 Hydrometry 96 6.9 Study Questions 102 6.5.2.1 Hydrometer 97 6.10 Practice Problems 103 6.5.2.2 Pycnometer 97 6.11 References 104 6.5.3 Refractometry 98 Chapter 6 • Moisture and Total Solids Analysis 87 6.1 INTRODUCTION (d) Glucose syrup must have ≥70% total solids.