DOCSLIB.ORG

Creating a Custom Windows to Go Device

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Creating a Custom Windows to Go Device Creating a Custom Windows To Go Device One of the great features in Windows 8 Enterprise is Windows To Go. This feature allows you to take your Windows 8 install anywhere with you and run it from any PC with compatible hardware and the ability to boot from USB. This allows you to use the same PC from home or work, and makes working remotely a snap! You can install all of your management apps on one PC, then with a VPN or remote connection, have the same applications and manageability that you would as if you were sitting in your office. You can also create Windows To Go pen drives and essentially keep a bunch of “computers” in your desk drawer! This is a great option when rolling out Windows 8 in an enterprise without needing to overwrite an old PC, it also presents a lot of great testing opportunities! Microsoft only supports Windows To Go on a select list of certified devices. You can find that listing on their website: http://www.microsoft.com/en-us/windows/enterprise/products-and- technologies/devices/windowstogo.aspx Creating a Windows To Go device is pretty simple. All that you need is a system running Windows 8 Enterprise and the Windows 8 Enterprise installation media. Then you can simply open the control panel, click on the Windows To Go option, select your pen drive and wait for the magic wizard to complete. However, that only provides you a base Windows 8 image to work with. I am writing this to aid you in creating a custom Windows To Go image that can be easily pumped out to multiple pen drives. Like any deployment you need a pristine system that you will use to configure your Windows 8 image and a technician PC that you will use to push out your Windows To Go pen drives. We will assume that you have already created your Windows 8 image, installing all of your desired applications and Windows Updates. Items you will need: PC to be used as your Pristine Windows 8 Machine PC to be used as your Technician Windows 8 Machine Pen Drive to be used as a bootable Windows 8 PE drive o At least 1GB USB Hard Drive for capturing your Windows To Go image o At least the same size as your Pristine Windows 8 Install Pen Drive to be used as your Windows To Go Pen Drive, meeting Microsoft’s certification specs. Steps: Creating your pristine Image Creating a bootable Windows 8 PE Pen Drive Capturing the image from your pristine system Creating the custom Windows To Go Pen Drive Creating your pristine image: Once you have the pristine computer completely setup and tested you want to sysprep the system. You can use an unattended file, but for this example we will just use a generic sysprep command: Run Command Prompt or PowerShell as an administrator from the C:\Windows\System32\Sysprep directory and run the following command to sysprep and shutdown the PC: CMD: sysprep.exe –oobe –generalize –shutdown PowerShell: .\sysprep.exe –oobe –generalize –shutdown Once the system has been shut down you will need to capture an image of it and then push that image to your Windows To Go pen drive. Creating a bootable Windows 8 PE Pen Drive: In keeping this in line with all things Microsoft we will use the Windows 8 Assessment and Deployment Kit (ADK). This used to be called the Windows Automated Installation Kit (WAIK) in previous version of Windows. You will need to install the Deployment Tools and Windows PE and then create a bootable Pen Drive to boot your pristine system with in order to capture the image. Install Windows ADK onto your technician PC: You can download this from the following website: http://www.microsoft.com/en-us/download/details.aspx?id=5753 Once downloaded you can start the installation by running the adksetup.exe From the ‘Select the features…’ screen you need to select the Deployment Tool and Windows Preinstallation Environment (Windows PE) features. Once the installation is complete you are ready to start creating your bootable Windows 8 PE Pen Drive. Start the Deployment and Imaging Tools Environment as an Administrator. Now we are going to add in some packages to the Windows PE image. This isn’t necessary, but it does add in some extra features to your PE image. Create a C:\WinPE_amd64 folder. Copy the winpe.wim file from C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64 to the C:\WinPE_amd64 folder created above. Create a C:\Mount folder to mount the PE image to. Mount the boot image using the following command in the Deployment Tools and Imaging Environment window: o imagex /mount C:\WinPE_amd64\winpe.wim 1 C:\Mount Add the following components to the boot image by running the following commands: (I found this easier to do by creating and executing a batch file) o cd /d "C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs" dism /image:C:\Mount /add-package /packagepath:"WinPE- Scripting.cab" dism /image:C:\Mount /add-package /packagepath:"en- us\WinPE-Scripting_en-us.cab" dism /image:C:\Mount /add-package /packagepath:"WinPE- WMI.cab" dism /image:C:\Mount /add-package /packagepath:"en- us\WinPE-WMI_en-us.cab" dism /image:C:\Mount /add-package /packagepath:"WinPE- MDAC.cab" dism /image:C:\Mount /add-package /packagepath:"en- us\WinPE-MDAC_en-us.cab" dism /image:C:\Mount /add-package /packagepath:"WinPE- HTA.cab" dism /image:C:\Mount /add-package /packagepath:"en- us\WinPE-HTA_en-us.cab" dism /image:C:\Mount /add-package /packagepath:"WinPE- NetFx4.cab" dism /image:C:\Mount /add-package /packagepath:"en- us\WinPE-NetFx4_en-us.cab" dism /image:C:\Mount /add-package /packagepath:"WinPE- PowerShell3.cab" dism /image:C:\Mount /add-package /packagepath:"en- us\WinPE-PowerShell3_en-us.cab" dism /image:C:\Mount /add-package /packagepath:"WinPE- DismCmdlets.cab" dism /image:C:\Mount /add-package /packagepath:"en- us\WinPE-DismCmdlets_en-us.cab" Commit the changes to the boot image: o imagex /unmount /commit C:\Mount Now we need to copy the newly edited winpe.wim file back over the original file located here: C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64 o I would recommend renaming the original file to winpe.wim.orig or similar. Now you need to create a working copy of the Windows PE files, from here you can specify x86, amd64 or arm to suite your needs (for this example I chose amd64): Run the following command from the Deployment and Imaging Tools Environment as an Administrator. o Copype amd64 C:\WinPE_amd64 Install the unpacked Windows PE files to the USB Flash drive, specifying the drive letter (in my case, G:\): o MakeWinPEMedia /UFD C:\WinPE_amd64 G: Now you have a bootable Windows 8 PE pen drive to boot your pristine computer from. Capturing the image from your pristine system: Boot your Pristine PC from your newly created Windows 8 PE pen drive. Now you need to record the drive letters of your Pristine Computer and External Hard Drive. In my case my Pristine drive was F:\ and my External Hard Drive was D:\ From the Windows 8 PE command prompt run the following to capture your image: DISM /Capture-Image /ImageFile:D:\WindowsToGo.wim /CaptureDir:F:\ /Name:”Windows To Go” Now wait for the image to be created on your external hard drive, this may take a while so feel free to browse the Spiceworks Community from your technician PC! Once the image capture is complete you can shut down your Pristine PC by typing exit into the command prompt. Creating the custom Windows To Go Pen Drive: Start off by plugging your Windows To Go Pen Drive and the external hard drive containing your Prinstine Image ‘WindowsToGo.wim’ file into your Technician PC. Open a command prompt as an administrator and prepare your Windows To Go Pen Drive for creation: Start a command prompt as an administrator Start Disk Part by typing diskpart into the command line Now you need to identify your Pen Drive, type list disk into Disk Part and locate the disk with the same amount of space as your Windows To Go Pen Drive, in my case it was Disk 2. Type in the following commands to create a new partition: o select disk 2 clean create partition primary select partition 1 active format quick fs=ntfs assign exit Now you need to apply the Pristine image on your external hard drive to your Windows 2 Go Pen Drive: o Run the following command to apply the image: DISM /Apply-Image /ImageFile:G:\WindowsToGo.wim /Index:1 /ApplyDir:F:\ o This step is going to take a while, so feel free to cook up some bacon and surf the Spiceworks Forums! Now you need to setup the boot configuration so that it will boot as a Windows To Go device: o F:\Windows\System32\bcdboot F:\Windows /f ALL /s F: Now you should create a SAN policy that will prevent the Windows To Go device from automatically bringing any internally connected disks online. This adds extra security by preventing access to local internal discs by default. However, they can still be seen from Disk Management. Put the following into a san_policy.xml file in the root of the Windows directory on the Windows To Go device: o <?xml version='1.0' encoding='utf-8' standalone='yes'?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="offlineServicing"> <component xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" language="neutral" name="Microsoft-Windows-PartitionManager" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" > <SanPolicy>4</SanPolicy> </component> <component xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" language="neutral" name="Microsoft-Windows-PartitionManager" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" > <SanPolicy>4</SanPolicy> </component> </settings> </unattend> o Run the following command to apply the policy: .
Load more

Recommended publications
  • Ironkey™ Workspace W200
    IRONKEY™ WORKSPACE W200 WINDOWS TO GO CERTIFIED Depend on the Microsoft-certified Windows To Go solution that delivers a true Windows 10 or 8.1 desktop embedded on a trusted IronKey USB flash drive. BENEFITS Affordably deliver a full Windows desktop that boots from USB and uses the DEPLOY AN AFFORDABLE MOBILE available host system resources. ™ WORKSPACE PC ON A STICK SOLUTION Rely on IronKey’s portable desktop Balancing the demands of growing workforces with the restrictions of tight budgets expertise and proven dependability in a can make it difficult to properly equip employees, contractors, field personnel and sleek, rugged new chassis. teleworkers with a mobile computing environment you can trust. Now there’s Equip users to work anywhere using your IronKey Workspace W200 PC on a Stick drives for Windows To Go. Offering an IT-managed corporate desktop image. ultra-affordable alternative to a laptop with a savings of up to 95%, these IronKey drives give mobile workers a full Windows desktop image, including the ability to Protect portable desktops with full disk run all applications directly from the USB device or safely access Office 365, Citrix, encryption and password authentication VPN or other SaaS clients from an IT-managed environment. leveraging Microsoft BitLocker or other third-party software encryption MOBILIZE ACROSS THE ENTERPRISE technology. With IronKey Workspace W200 drives, mobile workers run a complete Windows 10 Completely bypass the host computer or Windows 8.1 Enterprise workspace from a USB 3.0 flash drive on any and any local viruses or loggers for a clean compatible PC, tablet or Mac.
    [Show full text]
  • Supporting Operating System Installation | 3
    cc01SupportingOperatingSystemInstallation.indd01SupportingOperatingSystemInstallation.indd PagePage 1 08/10/1408/10/14 4:334:33 PMPM martinmartin //208/WB01410/XXXXXXXXXXXXX/ch01/text_s208/WB01410/XXXXXXXXXXXXX/ch01/text_s Supporting Operating LESSON 1 System Installation 70-688 EXAM OBJECTIVE Objective 1.1 – Support operating system installation. This objective may include but is not limited to: Support Windows To Go; manage boot settings, including native virtual hard disk (VHD) and multi-boot; manage desktop images; customize a Windows installation by using Windows Preinstallation Environment (PE). LESSON HEADING EXAM OBJECTIVE Using a Troubleshooting Methodology Viewing System Information Using the Event Viewer Supporting Windows To Go Support Windows To Go Creating and Deploying a Windows To Go Workspace Drive Booting into a Windows To Go Workspace Managing Boot Settings Manage boot settings, including native virtual hard disk (VHD) and multi-boot Using BCDEdit and BCDBoot Configuring a Multi-Boot System Manage boot settings, including native virtual hard disk (VHD) and multi-boot Configuring a Native VHD Boot File Manage boot settings, including native virtual hard disk (VHD) and multi-boot Understanding VHD Formats Installing Windows 8.1 on a VHD with an Operating System Present Installing Windows 8.1 on a VHD Without an Operating SystemCOPYRIGHTED Present MATERIAL Managing Desktop Images Manage desktop images Capturing Images Modifying Images using DISM Customizing a Windows Installation by Using Windows PE Customize a Windows
    [Show full text]
  • Understanding Windows 10 – a Guide to Help Get You Started Settings
    Understanding Windows 10 – A Guide to Help Get you Started By Jim Hillier – July 14, 2015 https://davescomputertips.com/understanding-windows-10-a-guide-to-help-get-you-started/ Following an initial perusal of Windows 10 it appeared that Microsoft included a lot of changes merely for the sake of change, presumably to help expand the gap between Windows 8 and Windows 10. However, after spending more time working with the new operating system you will realize that statement is incorrect, and here’s why. Settings – The Windows 10 Nerve Center At the very heart of Windows 10 is the ―Settings‖ menu which provides the interface for managing how the operating system displays and behaves. Consequently, a number of previously easily accessible settings/options have been moved into the Settings menus for the sake of centralization. While this may well now force users to dig a little deeper in order to locate a particular setting, I can appreciate the logic behind it, everything in one place, and no fragmentation. Finding “Screen Resolution in Windows 10 For example: Accessing ―Screen Resolution‖ settings has long been a simple matter of selecting the option from the desktop right click menu. Now, in Windows 10, one needs to take a rather more convoluted path: 1. Click Start and then Settings 2. Click System, then click Display(the Display tab should open by default) 3. Click ―Advanced display settings‖ There it is! Adding Desktop Shortcuts to System Locations in Windows 10 This is another setting location that has changed and integrated into the all, encompassing Settings menu.
    [Show full text]
  • Portable Workplace Bootable USB 3.0 Windows to Go Drives
    Portable Workplace Bootable USB 3.0 Windows To Go Drives MICROSOFT-CERTIFIED WINDOWS TO GO DRIVES SPECIFICATIONS Hardware-encrypted Secure Portable Workplace and unencrypted Portable Workplace from PNY are Microsoft-certified Windows To Secure Portable Workplace Go drives that securely boot your custom Windows 8, 8.1, and 10. Usable Capacities (IDEMA) 32 GB, 64 GB, 128 GB, 256 GB PNY Windows To Go drives are not slow virtual machines. They Dimensions (L × W × H) 95.3 × 24.5 × 9.8 mm boot a native operating system using your computer hardware PERFORMANCE but never access or alter the host computer’s hard drive. USB USB 3.0 Super Speed Enterprise users can enjoy the mobility of a pocket-sized Windows Sequential Max Read Up to 240 MB/s (100 GB) To Go drive with access to all their enterprise network resources. Enterprise IT can rest assured that remote access to valuable Sequential Max Write Up to 240 MB/s (100 GB) resources is by authentic users running the corporate Windows ELECTRICAL image—even when booted from untrusted computers. Operating Voltage Vcc=3.3 to 5 VDC Power Consumption ~300mA @ 3.3 VDC SECURE HARDWARE ENCRYPTION Humidity 90%, noncondensing Secure Portable Workplace provides military-grade XTS-AES 256 ENVIRONMENTAL hardware encryption over the entire drive, providing the ultimate Operating Temperature 0° C ~ 70° C protection of the operating system, applications, and data storage. Always-on, tamper-proof hardware encryption prevents data at Storage Temperature -20° C ~ 85° C rest on SecurePortable Workplace from being accessed, deleted, Operating Humidity 5 to 98% or modified.
    [Show full text]
  • How to Use the Sysprep Tool to Automate Successful Deployment of Windows XP Page 1 of 5
    How to use the Sysprep tool to automate successful deployment of Windows XP Page 1 of 5 How to use the Sysprep tool to automate successful deployment of Windows XP This article was previously published under Q302577 Article ID : 302577 On This Page Last Review : April 14, 2005 INTRODUCTION Revision : 2.2 MORE INFORMATION Requirements for running the Sysprep tool Prepare a reference computer for Sysprep deployment Create the Sysprep.inf answer file Sysprep.inf answer file format and parameters Use the Setup Manager tool to create the Sysprep.inf answer file Sysprep parameters REFERENCES INTRODUCTION This step-by-step article describes how to use the System Preparation Tool (Sysprep) to automate the successful deployment of Microsoft Windows XP. Sysprep is a tool that is designed for system administrators, Original Equipment Manufacturers (OEMs), and others who must automatically deploy the Windows XP operating system on multiple computers. After you perform the initial setup steps on a single computer, you can run the Sysprep tool to prepare the sample computer for cloning. MORE INFORMATION Requirements for running the Sysprep tool Before you can use the Sysprep tool, your computer hardware and related devices must meet the following requirements: • The reference and destination computers must have compatible HALs. For example, Advanced Programmable Interrupt Controller (APIC)–based MPS (multiprocessor systems) must use the same APIC HAL. A standard HAL Programmable Interrupt Controller (PIC)–based system is not compatible with either the APIC HAL or the MPS HAL. • The reference and destination computers must have the same Advanced Configuration and Power Interface (ACPI) support.
    [Show full text]
  • Windows 10 Iot Enterprise LTSB 2016 for Dell Wyse 5470 All-In-One Thin Client Release Notes Notes, Cautions, and Warnings
    Windows 10 IoT Enterprise LTSB 2016 for Dell Wyse 5470 All-in-One Thin Client Release Notes 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. © 2019 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. 2019 - 12 Rev. A01 Contents 1 Release summary..........................................................................................................................5 Priority and recommendations.............................................................................................................................................5 2 Compatibility............................................................................................................................... 6 Build details.............................................................................................................................................................................6 Connection brokers............................................................................................................................................................... 6 Supported languages.............................................................................................................................................................6
    [Show full text]
  • Copyrighted Material
    Exam MD-100 COPYRIGHTED MATERIAL c01.indd 07/04/2019 Page 1 Chapter Windows 10 1 Installation MICROSOFT EXAM OBJECTIVES COVERED IN THIS CHAPTER: ✓ Deploy Windows 10 ■ Configure language packs; migrate user data; perform a clean installation; perform an in-place upgrade (using tools such as MDT, WDS, ADK, etc.); select the appropriate Windows edition; troubleshoot activation issues. ✓ Manage updates ■ Check for updates; troubleshoot updates; validate and test updates; select the appropriate servicing channel; configure Windows update options. c01.indd 07/04/2019 Page 3 This book is for exam MD-100, and this is the fi rst of two Windows 10 exams (MD-100 and MD-101) for the Microsoft 365 Certifi ed: Modern Desktop Administrator Associate. If you are using both of the Sybex books for the Microsoft 365 Certifi ed: Modern Desktop Administrator Associate certifi cation, you will notice that many of the topics in Chapter 1 are the same in both books. The reason for this is that no matter what test you take, the process for installing Windows 10 is the same. Let me be the fi rst to welcome you to Windows 10 and the beginning of a new journey. But as with the start of any journey, we must take our fi rst steps. The fi rst step for this exam is to learn about the Windows 10 installation process. It is important that you understand the different versions of Windows 10 and which one is right for you and your organization. In this chapter, I will show you the many different features of Windows 10, and then I will describe each edition.
    [Show full text]
  • Download Deploying Windows 7, Essential Guidance
    FROM THE Windows® 7 Resource Kit Mitch Tulloch, Tony Northrup, Jerry Honeycutt, Ed Wilson, and the Windows 7 Team at Microsoft I Chapter 3 Deployment Platform .............................................. 85 I Chapter 4 Planning Deployment ............................................ 113 I Chapter 5 Testing Application Compatability ........................... 139 I Chapter 6 Developing Disk Images ......................................... 179 I Chapter 7 Migrating User State Data ...................................... 223 I Chapter 8 Deploying Applications .......................................... 247 I Chapter 9 Preparing Windows PE ........................................... 273 I Chapter 10 Confi guring Windows Deployment Services .............. 293 I Chapter 11 Using Volume Activation ........................................ 335 I Chapter 12 Deploying with Microsoft Deployment Toolkit ........... 355 DEPLOYING WINDOWS 7 83 Chapter 3 Deployment Platform n Tools Introduction 85 n Windows 7 Deployment Terminology 87 n Platform Components 89 n Deployment Scenarios 99 n Understanding Setup 101 n Basic Deployment Process 105 n Microsoft Deployment Toolkit Process 107 n Summary 110 n Additional Resources 111 uilding on technology that the Windows Vista operating system introduced, Windows 7 Bdeployment technology has evolved significantly since Windows XP Professional . For example, it supports file-based disk imaging to make high-volume deployments quicker, more efficient, and more cost effective . The Windows 7 operating system also provides
    [Show full text]
  • Windows Could Not Finish Configuring the System...Restart 10-11-17 8:53 AM
    Windows could not finish configuring the system...restart 10-11-17 8:53 AM United States (English) Sign in Search Windows with Bing Home Windows 7 Windows Vista Windows XP Library Forums Windows Client TechCenter > Windows 7 IT Pro Forums > Windows 7 Installation, Setup, and Deployment > Need Help with Forums? (FAQ) Windows could not finish configuring the system...restart My Forum Links Ask a question Search Forums: Search Windows 7 Installation, Setup, and Deployment Forum Sign In To Forums Forums Home Windows could not finish configuring the Browse Forums Users system...restart flicknstock Sunday, January 11, 2009 6:13 AM Not sure what happened, but I keep getting the error: Windows could not finish configuring the system. To attempt to resume configuration, restart the 0 computer. Sign In to Vote I tried to boot in safe mode and it gave me the same error. Any thoughts on what to try or is this a lost cause? I can't remember all the stats of the computer since it is a backup one, but it does surpass all the requirements. Reply Quote Related Topics Answers = Unanswered = Answered flicknstock Tuesday, January 13, 2009 4:12 AM Windows could not finish configuring the system... restart failure Vista is stuck on the "configuring updates" After formatting the hard drive and re-installing everything I was able to get past my issue. My guess is that some file was left from the random files previously on the HD and win7 wasn't able screen... 0 to format it correctly. Sign In to Vote In case anyone else needs...I used GParted to format the drive.
    [Show full text]
  • Optimizing Windows 10, Build 2004, for a Virtual Desktop Role
    Optimizing Windows 10, Build 2004, for a Virtual Desktop role Written by Robert M. Smith, Program Manager, Azure Global Customer Engineering Date Created: May 12, 2020 Date Updated: July 08, 2020 Date Published: tbd Contributors: Tim Muessig, Senior Premier Field Engineer; Narklis Engler, Principal Program Manager Version 1.2 Document Change History Version Changes 1.0 Adding verbiage for Windows Virtual Desktop, and Windows 10 build 2004 specifically 1.1 Additional updates for 2004 1.2 Final pass, updated group policy, services, tasks, and added info about Storage Sense for disk cleanup. Introduction This article is intended to provide suggestions for configurations for Windows 10, build 2004, for optimal performance in Virtualized Desktop environments, including Virtual Desktop Infrastructure (VDI) and Windows Virtual Desktop (WVD). All settings in this guide are suggested optimization settings only and are in no way requirements. The information in this guide is pertinent to Windows 10, version 2004, operating system (OS) build 19041. The guiding principles to optimize performance of Windows 10 in a virtual desktop environment are to minimize graphic redraws and “effects”, background activities that have no major benefit to the virtual desktop environment, and generally reduce running processes to the bare minimum. A secondary goal is to reduce disk space usage in the base image to the bare minimum. With virtual desktop implementations, the smallest possible base, or “gold” image size, can slightly reduce memory utilization on the host system, as well as a small reduction in overall network operations required to deliver the desktop environment to the consumer. No optimizations should reduce the user experience.
    [Show full text]
  • My Passport® Enterprise Portable Hard Drives
    My Passport® Enterprise Portable Hard Drives Your workspace anwhere. Secure work environment Capacity and performance for Windows® To Go Fast and easy setup My Passport Enterprise is designed for Windows To Go and allows you to boot your Windows 8 corporate workspace onto any PC certified for use with Windows 7 or Windows 8 operating systems. The compact design and 500 GB of storage capacity gives employees and contractors the ability to work in a secure environment at home, while traveling or on-site from a managed PC. My Passport Enterprise Portable Hard Drives Product Features Fast and easy setup Specifically designed to support Drive encryption protects your data Run the WD Compass utility with existing Windows Windows To Go Windows To Go supports BitLocker® drive tools and the Windows 8 corporate desktop My Passport Enterprise is specifically designed encryption. Data on the My Passport Enterprise environment can be provisioned onto the for Windows To Go, a feature within Windows 8 separates itself from the host PC’s internal hard My Passport Enterprise drive. WD Compass Enterprise edition, offering portability, reliability and drive to avoid any accidental data disclosure. instantly improves the provisioning time of protection for the road warrior. It leaves no traces of data on the host computer so Windows To Go on your My Passport Enterprise your information is secure and it allows IT to provide and installation time can be completed in minutes. Plug-and-play solution for an imaged version of Windows 8 that reflects the IT professionals Windows 8 corporate desktop environment. Capacity and performance for The easy setup process allows IT professionals to Windows To Go provision the Windows 8 corporate environment to On-the-go, ultra small.
    [Show full text]
  • Conference 2017
    Conference 2017 Learning to Live with Windows 10 What we’ve learned at UVic Where the journey started • Early adopters of Windows 10 in Fall 2015 • Limited deployment in Spring 2016 with version 1511 • Moved to Windows 10 on all standard computers purchased after June 2016 Conference 2017 Learning to Live with Windows 10 2 Where we are today • All standard computers deployed with version 1607 1 • /3 of our managed fleet are using Windows 10 Conference 2017 Learning to Live with Windows 10 3 A few common terms first Term Description A new Windows 10 release that contains additional features and Upgrade capabilities, released two to three times per year. Packages of security fixes, reliability fixes, and other bug fixes that are released periodically, typically once a month on Update Tuesday Update (sometimes referred to as Patch Tuesday). With Windows 10, these are cumulative in nature. The windows servicing branch is one of four choices: Windows Insider, Current Branch, Current Branch for Business, or Long-Term Servicing Branch Branch. Branches are determined by the frequency with which the computer is configured to receive feature updates. A ring is a groups of PCs that are all on the same branch and have the Ring same update settings. Rings can be used internally by organizations to better control the upgrade rollout process. Source: https://technet.microsoft.com/de-de/itpro/windows/manage/introduction-to-windows-10-servicing Conference 2017 Learning to Live with Windows 10 4 What did we learn During the build process • Don’t try to
    [Show full text]