# In Your local Network 1. Download and install Imaging Server.\ Supported platforms for the Imaging Server: * Windows 8.1, 10, 11 * Windows Server 2012 R2, 2016, 2019, 2022 Windows Server 2012 R2 or above is required to take advantage of WDS. 2. Configure Imaging. * Use Windows Deployment Services (WDS)\ Select this option to utilize advanced features such as PXE booting and have access to existing images and driver repository. Imaging Server will automatically configure the Windows Deployment Service Role at the end of the setup. * Proceed without Windows Deployment Services\ Select this option to proceed without Windows Deployment Services. PXE booting is not supported in this setup, and images and drivers already set up in WDS are not accessible. You will need a Windows installation media (.iso file or DVD) at the end of the setup process. 3. Create a Local User Account to allow managed computers to communicate with this server and secure a Network Share. 4. Specify the Image Repository Location to hold images. It is recommended to choose a location with enough free space to hold multiple OS installation images. 5. Add Images (.iso or .wim files) and Drivers (.inf files). {% hint style="info" %} After setting up the Imaging Server, you need to provide Volume License .iso file (with boot.wim and install.wim files) as the first image to be added. Without the boot.wim file, Imaging will not work. {% endhint %} ## Adding Images Complete the following steps to add images. 1. Launch Imaging Server. 2. Click *Images*. 3. Select one from these options: * Automatically Download Windows 11 ISO from Microsoft\ When this option is selected, click *Next* to start the download automatically from Microsoft. * Manually Choose any Other Existing ISO File\ When this option is selected, click *Next*, then click *Browse* and select the .iso file. 4. Click *Next*. 5. Select the images you want to add to the server and click *Next*. 6. To change your selection, click *Back*. To add the selected images to the server, click *Next*. 7. Add *OEM Drivers*. Click Continue to add OEM drivers, or *Skip* to continue adding images. 8. You can edit the image name and description of the images by clicking the pencil icon under Action. Click X to cancel any changes, or click the save icon after editing. 9. You can delete the images by clicking the delete icon under Action. 10. To add another image, click *Add Image*. ## Creating Cloud Images Cloud Images are images exported from the Imaging Server and hosted on a publicly available server (for example, HTTP/S or SFTP servers). Complete the following steps to create Cloud Images. 1. Launch Imaging Server. 2. Click *Images*. 3. Select the image you want to create a Cloud Image of and click *Create Cloud Image*. 4. Specify the folder for creating the Cloud Image ZIP Archive, then click *Next*. 5. After the Cloud Image ZIP Archive has been created, you have the option to: * Use HTTP/S Server To use this option, cloud images must be uploaded to a publicly accessible web server or cloud storage provider that supports HTTP/S endpoint (make note of where the images are located in your cloud storage). In the *Cloud Image ZIP Archive URL* field, enter the URL where the cloud image was uploaded, then click *Register Cloud Image*. * Upload to SFTP Server If selecting this option, cloud images will be automatically picked up and uploaded to the SFTP server. Provide the *SFTP Server Name, SFTP User Name*, and *SFTP Password*, then click *Upload and Register*. {% hint style="info" %} Click *Open Folder* to view the list of existing cloud images in the local directory. Click *Cancel* to view the list of images that have been added to the utility. Note that clicking *Cancel* will bring you to the images list page and any changes or progress made are not saved. {% endhint %} {% hint style="info" %} You can store multiple images in the same server, however each image must have its own link {% endhint %} {% hint style="info" %} After the Cloud Image ZIP archive has been registered, it will appear as an image under *Cloud Images* in the Cloud console and can be used to create a Cloud Deployment Package. {% endhint %} ## Registering Existing Cloud Images You can choose to register existing cloud images if you want to upload the images to a different HTTP/s location, different SFTP server or to register the images in a different Imaging Server. {% hint style="info" %} You can only register cloud images that have been created through the Faronics Imaging solution. {% endhint %} Complete the following steps to register existing Cloud Images. 1. Launch Imaging Server. 2. Click *Images*. 3. In the image list page, click *Register Existing Cloud Image* and select the image zip package you want to register. Click *Open*. 4. After selecting the Cloud Image ZIP Archive to be registered, you have the option to: * Use HTTP/S Server To use this option, cloud images must be uploaded to a publicly accessible web server or cloud storage provider that supports HTTP/S endpoint (make note of where the images are located in your cloud storage). In the *Cloud Image ZIP Archive URL* field, enter the URL where the cloud image was uploaded, then click *Register Cloud Image*. * Upload to SFTP Server If selecting this option, cloud images will be automatically picked up and uploaded to the SFTP server. Provide the *SFTP Server Name, SFTP User Name*, and *SFTP Password*, then click *Upload and Register*. {% hint style="info" %} After the Cloud Image ZIP archive has been registered, it will appear as an image under *Cloud Images* in the Cloud console and can be used to create a Cloud Deployment Package. {% endhint %} ## Adding Drivers Complete the following steps to add drivers. 1. Launch Imaging Server. 2. Click *Drivers*. 3. Click *Browse* and select the folder where the driver packages are located. 4. Click *Next*. 5. Select the driver packages you want to add and click *Next*. 6. Select *Add Tags* if preferred and specify the tags separated by commas. 7. To change your selection, click *Back*. To add the selected drivers to the server, click *Next*. 8. You can delete the driver packages by clicking the delete icon under Action. 9. To add another driver, click *Add Driver*. ## Creating Cloud Drivers Cloud Drivers are driver packages stored on HTTP/S or SFTP servers. Complete the following steps to create Cloud Drivers. 1. Launch Imaging Server. 2. Click *Drivers*. 3. Select the drivers to be included in the Cloud Driver group and click *Create Cloud Drivers*. 4. Specify the folder for creating the Cloud Driver Group ZIP Archive, then click *Next*. 5. After the Cloud Driver Group ZIP Archive has been created, you have the option to: * Use HTTP/S Server To use this option, cloud driver groups must be uploaded to a publicly accessible web server or cloud storage provider that supports HTTP/S endpoint (make note of where the driver groups are located in your cloud storage). In the *Cloud Driver Group ZIP Archive URL* field, enter the URL where the cloud driver group was uploaded, then click *Register Cloud Driver Group*. * Upload to SFTP Server If selecting this option, cloud driver groups will be automatically picked up and uploaded to the SFTP server. Provide the *SFTP Server Name, SFTP User Name, SFTP Password* and *Cloud Driver Group Name*, then click *Upload and Register*. {% hint style="info" %} Click *Open Folder* to view the list of existing cloud driver groups in the local directory. Click *Cancel* to view the list of cloud driver groups that have been added to the utility. Note that clicking *Cancel* will bring you to the drivers list page and any changes or progress made are not saved. {% endhint %} {% hint style="info" %} You can store multiple driver groups in the same server, however each driver group must have its own link. {% endhint %} {% hint style="info" %} After the Cloud Driver Group ZIP archive has been registered, it will appear as a driver group in the Cloud console and can be used to create a Cloud Deployment Package. {% endhint %} ## Driver Tags You can edit or remove tags for a single or multiple drivers. When creating tags for a single driver select the driver then click *Edit Tags*. Specify the tags separated by commas, then click *Save*. When creating tags for multiple drivers select the driver then click *Append Tags*. Specify the tags separated by commas, then click *Save*. The specified tags will be appended to all selected drivers. ## USB Media Creator Complete the following steps to create a bootable USB drive. 1. Launch Imaging Server. 2. Click *USB Media Creator*. 3. Select the *Deployment Package* and *Policy*. 4. Select *Target USB Drive* if creating a bootable USB flash drive, or 5. Select *USB Creator Package Path:* and specify the folder in the local computer to create the *Installation Media Creator Package*. 6. Select *Use Product Key Stored in UEFI Firmware*. When selected, the product key embedded in the UEFI firmware will be detected and automatically included in the installation media. 7. Click *Edit* to configure the partitions, assign the volume labels and partition sizes. In addition to the EFI and Windows system partition, up to 2 more partitions can be configured. All partitions will be formatted using NTFS. 8. Click *Start*. {% hint style="info" %} The created USB Media Package (.exe file) contains the policy and package that was selected during the package creation. You can use the USB Media Package to create a USB bootable media on any computer by launching the .exe file from the package and selecting a USB drive. {% endhint %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.faronics.com/deep-freeze-cloud/using-deep-freeze-cloud-console/imaging/setting-up/in-your-local-network.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.