Install Guide

Mass Deployment

These guides are intended for advanced IT administrators deploying CloudReady in environments with pre-existing mass deployment infrastructure. These guides assume that the reader has previous experience with configuring and using a given mass deployment tool. For organizations planning to install CloudReady on fewer than 100 machines, simply creating multiple USB installers is recommended.
Microsoft Windows Deployment Services (WDS)

PDF Version of these instructions

Scope

These instructions assume that you have already deployed Microsoft Windows Deployment Services (WDS) infrastructure at your site.

Be aware that CloudReady comes in both 32-bit and 64-bit variants. Deploying a 64-bit image to a device with 32-bit processor architecture will result in a device that cannot boot and will need re-imaging.


Requirements


  • A custom CloudReady image for your organization, designed for WDS deployment.  The standard installation files available on my.neverware.com will NOT function for mass deployment.  Please contact support to have one created for you at no charge. The process will generally take 3 business days or less. 
  • A server running Windows Deployment Services.

Process - 1 of 4 - Customize settings for your network


1.  Create a shared network folder on your network and extract the contents of CloudReady_WDS_Tools.zip into it.

2.  From the downloads section of my.neverware.com, download the appropriate image for your WDS deployment.  32 and 64 bit deployable images are available in both UEFI and Legacy-boot variants. Please note, deployable images are not present by default - contact our support team to have them created for you.  Unzip the large (more than 10GB) .bin file into the same shared network folder.

3. Edit the startnet.cmd file and replace the following placeholders:


USERNAME: The username of a domain user that has read permissions to the network share containing the CloudReady files.  For example: administrator


PASSWORD: The password of a domain user that has read permissions to the network share containing the CloudReady files.  For example: p@ssword


DOMAINNAME: Your Windows domain name. For example: neverware.com


\\SERVERNAME\SHARENAME: The network path of the share containing the CloudReady files.  For example: \\wdsserver\deployment\CloudReady


FILENAME.BIN: The name of the large .bin file.  For example: cloudready_deployable_64bit_uefi.bin


4.  Save the startnet.cmd file.



Process - 2 of 4 - Edit the Boot Image


1.  Connect via RDP or another remote access method to the desktop of the server hosting the CloudReady network share.  The following commands cannot be executed on a remote network share.  

2.  Open an administrative command prompt

3.  Via the command prompt, navigate to the folder containing the CloudReady files.  For example: e:\sharedfiles\cloudready

4.  In the command prompt, execute the following command, substituting the actual local path of the folder containing the cloudready files:

imagex /mountrw [your path to cloudready.wim file] 1 [your path to tmp folder]

For example: imagex /mountrw e:\sharedfiles\cloudready\cloudready.wim 1 e:\sharedfiles\cloudready\tmp

5. Allow for the cloudready.wim file to be mounted.  The contents of the cloudready.wim file will be present in the "tmp" subfolder inside the folder containing your CloudCeady files.

6.  Using windows file explorer, copy the startnet.cmd file you modified into the windows\system32 folder inside of temp, overwriting the previous file.  


7.  Close any open explorer windows or files accessing the tmp subfolder. The unmount process in the next step is very particular that no files are in use.


8.  In the command prompt, execute the following command, substituting the actual local path of the folder containing the cloudready files


imagex /unmount /commit [local path to tmp folder]


For example: imagex /unmount /commit e:\sharedfiles\cloudready\tmp


9.  Allow for the image to become unmounted.  The process of editing the boot image is now complete!



Process - 3 of 4 - Enable Boot Image for WDS


  1. Open Windows Deployment Services.
  2. Expand the server that currently hosts your PXE images.
  3. Select boot images.
  4. Right click "Boot Images" and select “Add Boot Image”
  5. Browse to the location of the cloudready.wim file that you previously modified. It is located at [path]\cloudready_boot\cloudready.wim
  6. Click Next
  7. Change the image name to “CloudReady”
  8. Click Next
  9. Click Next
  10.  Click Finish

Process - 4 of 4 - Deploy CloudReady on a Client Machine


  1. PXE boot a client machine.
  2. Select the “CloudReady” boot image from the menu. Deployment will proceed automatically.
  3. After deployment the computer will reboot with CloudReady installed.


Microsoft SCCM

To facilitate large-scale deployments, CloudReady can be deployed using Microsoft System Center Configuration Manager (SCCM).  Neverware provides expert guidance, custom SCCM-deployable disk images an an easily importable SCCM task sequence to customers upon request.  To discuss deploying CloudReady in your organization using SCCM, please contact our sales team.  

Symantec Ghost (formerly Norton Ghost)

PDF version of these instructions


Scope


These instructions assume that you have already deployed Symantec Ghost imaging infrastructure at your site.  This document only covers creation of a Ghost image of a drive containing CloudReady, not the subsequent deployment steps, which are the same as for any other image.

Be aware that CloudReady comes in both 32-bit and 64-bit variants.  Deploying a 64-bit image to a device with 32-bit processor architecture will result in a device that cannot boot and will need re-imaging.    


Requirements

  • A “reference” device installed with CloudReady.  CloudReady must be installed to storage that is smaller than ANY storage device that CoudReady will be mass deployed onto.  Ghost does not have the ability to deploy a CloudReady image onto a storage device smaller than the drive that the image was originally lifted from. An inexpensive 16 or 32GB SSD is useful for this purpose.  
  • A bootable USB environment containing the Ghost executable.  
  • A fast external USB storage device to hold the image (ie, an SSD connected to a USB dock) of at least 8GB capacity, formatted with an NTFS filesystem.

Process

  1. Install CloudReady on a device. Do not boot the device after imaging, as unique data like MAC address is generated on the 1st boot after installation.
  2. Insert and boot from a bootable USB containing the Ghost executable.
  3. Locate the folder containing the Ghost executable and navigate to it via the DOS or WinPE command line.
  4. Type “ghost32.exe -IR -FNF” and press enter. This step tells Ghost to operate in a special “raw” imaging mode that can cope with CloudReady’s non-Windows partitions and filesystem structure.
  5. Once you see the Ghost EULA screen, insert the external USB storage device.
  6. Navigate to Local>Disk>To Image and press enter.
  7. Select the internal drive that Cloudready is installed on, and press enter.
  8. Select your external storage device from the file list. This will likely be towards the bottom of the list, and will show up as “[volume label] NTFS drive”.
  9. Give the image a name and press enter.
  10.  Select “High” from the Compress Image dialogue box that appears. In testing, this results in a ~2GB .GHO file.
  11.  Select yes to the final confirmation dialog box. The process of creating an image will take between 30 and 50 minutes on a laptop with USB 2.0 interfaces.
  12.  Optional but recommended final step: Using the resulting .GHO file and the Ghost bootable USB stick, select Local>Disk>From Image to install the image to a different piece of hardware. Boot the device to verify that the image file works correctly.

FOG Deployment

Scope


This document assumes that you have already deployed FOG infrastructure at your site.  

Be aware that CloudReady comes in both 32-bit and 64-bit variants.  Deploying a 64-bit image to a device with 32-bit processor architecture will result in a device that cannot boot and will need re-imaging.    


Requirements

  • A computer to use for CloudReady image capture.  This can be any certified CloudReady model.  For maximum effectiveness, the hard drive in this device should be as small and fast as possible.  CloudReady can be installed on as little as 16GB of storage.  
  • A destination computer, to be used for testing the process.  This can be any certified CloudReady model.
  • A standard CloudReady USB installer.


Process

  1. On the image capture machine, install CloudReady.  Do not power the computer back on. The image must be captured before first boot.
  2. In your FOG management console, go to Image Management and select Create New Image.
  3. Name the CloudReady image. The standard naming convention is “cloudready_v##_#_64bit” or “cloudready_v##_#_32bit”
  4. Enter a description as you see fit.
  5. Select your storage group.
  6. Operating system should be categorized as “Other ­ (99)”.
  7. Image path should be unchanged.
  8. Image type, select RAW.
  9. Click “Update”.
  10.  Go to the Host Management section and locate your image capture computer.
  11.  Click “edit” for this host.
  12.  Change the “Host Image” to the image you created for CloudReady.
  13.  Click “Update”.
  14.  Click “Basic Tasks” under the Host Menu on the left hand side.  Select “Upload”.
  15.  Verify that “Schedule Instant Deployment” is selected.
  16.  Click “Create upload task for host name”.  You will see a confirmation notification.
  17.  PXE boot the image capture machine that is installed with CloudReady. The capture process is automatic.
  18.  When the capture is complete, the computer will reboot.  You are now able to deploy CloudReady as you would any other OS image in FOG! Verifying on a test machine is recommended before mass deployment.