Table of Contents

The share folder

The share folder holds everything the server sends to PCs: boot files, Windows images, Linux install files, drivers and workflows. It can get very big.

Choose where it goes

You choose the share folder in the Share folder step of First time setup. The Console suggests a folder called SharpDay Deploy on the data drive with the most free space, for example:

D:\SharpDay Deploy

If the server has no data drive with at least 20 GB free, it suggests the system drive instead.

We suggest you keep the share on its own drive, not the system drive. This keeps Windows and your files apart, which makes upgrades and moves easier.

Which folders you can use

The folder must be:

  • On one of the server's own drives. A network path such as \\server\share does not work.
  • A folder, not a whole drive. D:\SharpDay Deploy works, D:\ does not.
  • On a drive formatted as NTFS or ReFS. The share needs folder permissions, which other formats do not have.
  • Outside the Windows folder and outside C:\ProgramData\SharpDay.
  • New, empty, or a share folder from an older SharpDay Deploy server. If it already has SharpDay Deploy files, the server keeps them and uses them.

The Console warns you, but still lets you go on, if:

  • The drive has less than 20 GB free.
  • The folder is on the system drive and the server has a data drive.
  • The folder is in Program Files.

All the folders inside the share move with it. You do not need to set them one by one.

The server makes the share folder when you finish setup, and only administrators on the server can open it. It makes the folders inside it when the service starts again at the end of setup.

Move it later

The Console has no setting to move the share once setup is done. To move it, edit config.xml.

  1. Stop the SharpDay Deploy Service service. Its service name is SharpDay Deployment. As an administrator, run:

    Stop-Service -Name 'SharpDay Deployment'
    
  2. Move the share folder and everything in it to the new place.

  3. Open C:\ProgramData\SharpDay\SharpDay Deploy\Data\config.xml as an administrator.

  4. Set ShareDirectory to the new folder, for example E:\SharpDay Deploy.

  5. Delete the DriverDirectory, ScriptsDirectory, SDDClientDirectory, OperatingSystems and AutomationsDirectory lines. Without them, these folders follow ShareDirectory. If you leave them in, they still point to the old place.

  6. Start the service again:

    Start-Service -Name 'SharpDay Deployment'
    
Note

If you want one of those folders somewhere else, such as drivers on another drive, keep its line and set it to the folder you want. A line in config.xml always wins over ShareDirectory.

What is inside

Folder What it holds
Boot Files Boot folders that PCs download when they start from the network
iPXE Files iPXE scripts
Unattend Files Answer files for Windows and Linux installs
WinPE Updates Updates for Windows PE boot images
Operating Systems Windows images (WIM), ISO files and Linux install files
Drivers Driver packs and driver catalogs
SDDClient The PE client, its themes and the bootstrapper
SDDClient-arm64 The PE client for Arm PCs
Workflows Your workflows
Downloads Updates the server has downloaded
Scripts Scripts used when you export server data

The server makes these folders for you.

Who can read it

The server keeps most folders for administrators only. PCs read two folders over the network as Windows shares:

  • Drivers
  • Operating Systems

PCs read these shares with a local account called SDDServiceClient. The server makes this account, changes its password each time it starts, and stops it from signing in any other way. You can turn each share off on Boot Files > Services.

If you install Linux over SMB, the server also makes a read-only share called SDDLinux and an account called SDDLinuxReader. They only exist while a Linux install uses SMB.