THIS SCRIPT WILL FORCE THE MACHINE TO RESTART. IF THAT IS NOT THE BEHAVIOR THAT IS DESIRED REMOVE THIS LINE FROM THE JOINDOMAIN.PS1 FILE: Restart-Computer -Force
THIS SCRIPT WILL DELETE ITSELF ONCE IT HAS RUN ON THE CLIENT MACHINE LOCALLY.
**Example**: For the user, please use full path like e.g. "domain\\username"
Save changes and associate the Fileset to either Windows 10 or 11 client machines! # Adding A Printer for All Users (Windows) The task at hand seems simple enough...install a printer for a Windows user for a printer on a Print Server. In our example, I'll use a print share called BigDill on a print server named Arkone. Easy, right? A quick web search for "powershell add printer" takes me to the add-printer cmdlet, and it is pretty easy to use for a print server. The command looks like this (don't use this example!): ```powershell import-module printmanagement add-printer -ConnectionName \\arkone\BigDill ``` I tested it locally outside of FileWave in the PowerShell ISE and it worked fine. I ran the command, and it added the printer for me. So, I created a fileset for the exact same thing and tried it out. The result: **nothing whatsoever**. The script seemed to run fine, but the user logged in didn't see a new printer! So, why did this happen? For two important reasons: 1. The Add-Printer cmdlet is great, but it **ONLY** adds a printer for the current user 2. When FileWave runs a script, it is always run under the context of the ***System*** account When I investigated further by opening a command prompt as system, I found that in fact my fileset had run fine, and added the printer, but only for the system account.**Testing Scripts for Use in FileWave** Review our KB [Script Best Practices](https://kb.filewave.com/books/filewave-general-info/page/script-best-practices "Script Best Practices") which demonstrates the use of psexec to run scripts on Windows as if they were run through FileWave (as System User and 32bit).
So, a little more research was required, and PowerShell in this instance is not the answer. Instead, we are going to use a command-line utility in a batch file called printui.exe. PrintUI can be used in many ways: [Microsoft PrintUI Documentation](https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/rundll32-printui) We won't get into all of the options of this command here, but printui can add a printer globally for all users using the /ga command line option (/gd is a global delete if you happen to want to add a removal script as well). So our new batch file (Activation Script) code looks like this: ```text @echo off printui /ga /n\\arkone\BigDill exit 0 ``` And our results, in this case, were excellent...the printer is added for every user at their next login. (Given this, you may want to make this a reboot fileset) And, for completeness' sake, if we wanted to add a post-uninstallation script to "clean-up" if this fileset were removed, we could do: ```text @echo off printui /gd /n\\arkone\BigDill exit 0 ``` ## Related Content - [Script Best Practices](https://kb.filewave.com/books/filewave-general-info/page/script-best-practices "Script Best Practices") # Create local admin accounts on Windows ## Description Need to manage local admin accounts on your Windows devices? FileWave has you covered. Below is the recipe with Fileset to create your local admin account with username, password and full name. In addition, if needing to remove the local admin account, there is a removal script included. ## Ingredients - FW Admin - [Create Local Admin (Win).fileset.zip](https://kb.filewave.com/attachments/458) ## Directions 1. Download and unzip the Fileset 2. Import into your server via FileWave Admin 3. Highlight the Fileset and select "Scripts" for this Fileset 4. Select the create\_admin.ps1 to open the script properties[](https://kb.filewave.com/uploads/images/gallery/2025-05/z14tpdmUAzWPceCJ-createlocaladminwindows1.png) 5. Enter in your local admin Username, Password and Full Name for the desired account[](https://kb.filewave.com/uploads/images/gallery/2025-05/o0TrOjg4xVqrx9UA-createlocaladminwindows2.png) 6. Repeat the process for the remove\_admin.ps1 and enter in the desired Username to removeThe remove\_admin.ps1 script environment variable needs to match the Username found on the machine or in the create\_admin.ps1. If it does not match it will not successfully remove the admin account.
[](https://kb.filewave.com/uploads/images/gallery/2025-05/9nhmtCVgR3ZSi3H7-createlocaladminwindows3.png) 7. Close the Script window to Save 8. Assign to a test device 9. Perform a Model Update to deploy Confirmation of local admin created, you may open the Windows Settings > Accounts > Other Users to view the newly created local admin account.[](https://kb.filewave.com/uploads/images/gallery/2025-05/qgG47jNZwddxGLMb-createlocaladminwindows4.png) ## Notes Both scripts will output their executed tasks for detailed logging. These logs may be found in: ``` C:\ProgramData\FileWave\Logs\ ``` The create\_admin script log will be labeled: **CreateLocalUser\_FromEnv.log** **[](https://kb.filewave.com/uploads/images/gallery/2025-05/65j9SWZh97u34Mva-createlocaladminwindows8.png)** The remove\_admin script log will be labeled: **RemoveLocalUser\_FullCleanup.log** **[](https://kb.filewave.com/uploads/images/gallery/2025-05/4OM4U2Shyj17QGbg-createlocaladminwindows6.png)** The create admin script will skip if there is an username already exists. [](https://kb.filewave.com/uploads/images/gallery/2025-05/szix0dZGuPB2GaXD-createlocaladminwindows5.png) ## Related Content - [How to Create Local User Accounts on macOS](https://kb.filewave.com/books/macos/page/how-to-create-local-user-accounts-on-macos-1015) # Deploy SSL Certificates (Windows) Deploy SSL certificates to Windows "Trusted Root Certification Authorities" certificate store for use in secure services such as web content filters. ## Step-by-step guide - Download, unzip, and import the following Fileset Template into FileWave Central - [Windows - Install SSL Certificate.fileset.zip](https://kb.filewave.com/attachments/121) - Import the desired SSL certificate into the Fileset's "\\temp\\ssl\\" directory and delete "placeholder.pem". - Select the "install\_ssl.bat" file, click "Edit Text", and replace "placeholder.pem" with the full file name of the newly uploaded certificate. This script will add the desired SSL certificate to the Windows "Trusted Root Certification Authorities" certificate store for both the Local Machine (-enterprise) and the Current User (-user).
- Associate and deploy the Fileset to a test machine and verify the installation on the Windows machine. - Open "**certlm.msc**" for the Local Machine (-enterprise) Certificate Store or "**certmgr.msc**" for the Current User (-user) Certificate Store via Windows Run dialog (Win + R) or Command Prompt. - Navigate to "Trusted Root Certification Authorities>Certificates" and verify the name of the newly added certificate. **Additional Information** More information and options for the "certutil" program can be found on [Microsoft Docs](https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/certutil).
## Related articles - [APNs Certificate Creation & Renewal on Windows Computers](https://kb.filewave.com/books/certificates/page/apns-certificate-creation-renewal-on-windows-computers "APNs Certificate Creation & Renewal on Windows Computers") # Installing Windows Fonts ### Description Windows font installation is not as simple as adding files to a folder. As well as copying files, the registry requires editing. The following Fileset will add Fonts to Windows systems.TTF The Fileset has been tested with TTF on Windows Pro 10, 1803 and 1903
Registry EditingThis Fileset edits the Windows registry. Follow instructions carefully to ensure only the required Font files exist in the suggested folder.
### Information Download and import the Fileset, then ensure to edit appropriately, as per the directions, for desired fonts ##### [Windows Instal Fonts.fileset.zip](https://kb.filewave.com/attachments/107) ### Description The Fileset consists of: - An Activation Script - A folder to provide the fonts; with a placeholder file  #### Adding Fonts - Select the Fonts in a macOS Finder or Windows Explorer Window - Drag them into the Fileset folder Windows > Temp > Fonts - Select the Fonts folder in the Fileset, choose Get Info > Verification and set Ignore At Verify; Apply to Enclosed - Remove the 'placeholder.remove' file Example, Monsterrat Font:  #### Deployment On Association and Activation, the script will: - Copy ALL files from C:\\Windows\\Temp\\Fonts to C:\\Windows\\Fonts (if they do not already exist) - For each file copied, a registry entry will be created (if one does not yet exist) - Finally the script will remove each file from the temporary directory: C:\\Windows\\Temp\\Fonts #### Changing Temporary Folder Should a different temporary folder be desirable: - Drag the fonts to the desired location in the Fileset - Change the Launch Argument to match: InstalFonts.ps1 > Get Info > Executable  As always, test on appropriate devices before deploying en masse. # Local Group Policy Object Utility (Windows EXE) ## What Local Group Policy Object Utility or LGPO.exe is a new command-line utility to automate the management of local group policy. It replaces the no-longer-maintained LocalGPO tool that shipped with the Security Compliance Manager (SCM), and the Apply\_LGPO\_Delta and ImportRegPol tools. ## When/Why Many of the features help import required settings to your devices meeting organization policies for security compliance. Features: - Import settings into local group policy from GPO backups or from individual policy component files, including Registry Policy (registry.pol), security templates, and advanced auditing CSV files. - Export local policy to a GPO backup. - Parse a Registry Policy (registry.pol) file to readable "LGPO text" directly to the console or redirected to a file which can edited and imported into local policy. - Build a new Registry Policy (registry.pol) file from "LGPO text". - Enable group policy client side extensions for local policy processing. ## How The zip file contains the LGPO installer: [LGPO.zip](https://kb.filewave.com/attachments/442) LGPO.exe v3.0 - Local Group Policy Object utility LGPO.exe has four modes: 1. Import and apply policy settings; 2. Export local policy to a GPO backup; 3. Parse a registry.pol file to "LGPO text" format; 4. Build a registry.pol file from "LGPO text". To apply policy settings, use the LGPO.exe commands below, where one or more of the following (each of which can be repeated): ``` /g path import settings from one or more GPO backups under "path" /m path\registry.pol import settings from registry.pol into machine config /u path\registry.pol import settings from registry.pol into user config /s path\GptTmpl.inf apply security template /a[c] path\Audit.csv apply advanced auditing settings; /ac to clear policy first /t path\lgpo.txt apply registry commands from LGPO text /eSync Computer Name With FileWave 13.2.3+, FileWave will automatically disable "Sync Computer Name" when a client is manually renamed (right-click>Rename) via the FileWave Admin. This Fileset is made possible by a result of this change.
# Storing the BitLocker volume keys using a Custom Field Use a FileWave Custom Field to store the volume keys for your BitLocker volumes. This can be helpful if you don't have another way to escrow the volume keys. The Custom Field outlined in this article will get the volume key for every volume so if there is an encrypted C: and D: you would see both reported by this field. ## Adding the Custom Field 1. Download the following Custom Field export: [BitLocker Key Custom Field.customfields](https://kb.filewave.com/attachments/120) 2. Import the downloaded file into "FileWave Admin>Assistants>Custom Fields>Edit Custom Fields>Import". 3. Save changes within Custom Fields dialog. 4. Associate Custom Field with desired Windows devices via "right-click>Edit Custom Field(s) Associations". 1. A Windows-based Smart Group is very helpful to quickly associate Custom Field 2. Smart Group criteria: "Client OS Platform \[equals\] Windows"  **Here is the script from the Custom Field:** ```powershell # FileWave client will execute this script. The output will be used as the value of the custom field. # # Below is an example of how to read the value of one ENVIRONMENT VARIABLE in your script: # $my_var = $Env:ENV_VAR_NAME # # Identify all the Bitlocker volumes. $BitlockerVolumers = Get-BitLockerVolume # For each volume, get the RecoveryPassowrd and display it. $BitlockerVolumers | ForEach-Object { $MountPoint = $_.MountPoint $RecoveryKey = [string]($_.KeyProtector).RecoveryPassword if ($RecoveryKey.Length -gt 5) { Write-Output ("$MountPoint,$RecoveryKey") } } exit 0 ``` ## Assigning the Custom Field to devices 1. Save changes within Custom Fields dialog. 2. Associate Custom Field with desired Windows devices via "right-click>Edit Custom Field(s) Associations". - A Windows-based Smart Group is very helpful to quickly associate Custom Field - Smart Group criteria: "Client OS Platform \[equals\] Windows" 3. Alternatively you could assign the field to all devices since only Windows devices will run the script. ## Results  ## Related articles - [Securing FileWave Server on the Internet for Remote Device Management](https://kb.filewave.com/books/filewave-server/page/securing-filewave-server-on-the-internet-for-remote-device-management "Securing FileWave Server on the Internet for Remote Device Management") # Upgrade Windows 10 and 11 ### Description Although Software Updates are available as standard catalogue, Feature Updates are not. The following method may be used to update Windows devices using Feature Updates, e.g. 1909, 21H1. Last tested upgrading 20H2 to 21H1 #### Ingredients - Latest [Windows 10 ISO](https://www.microsoft.com/en-us/software-download/windows10ISO) or [Windows 11 ISO](https://www.microsoft.com/en-us/software-download/windows11) – If downloading from a Windows 10 device, please use the steps linked [here](https://www.howtogeek.com/427223/how-to-download-a-windows-10-iso-without-the-media-creation-tool/) to access the appropriate ISO download page. - Following Fileset Recipe:| ↓ Windows |
|---|
| [Windows - Feature Upgrade.fileset.zip](https://kb.filewave.com/attachments/113) |
Microsoft may change these options with differing versions. For example, there is a new argument /EULA which has been introduced for Windows 11, whilst the /DynamicUpdate argument has additional options available since Windows 10, 2004.
Examples could include Dynamic Updates or Compatibility (which have been included in the provided Fileset) Dynamic Updates (DynamicUpdate): [https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-setup-command-line-options#dynamicupdate](https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-setup-command-line-options#dynamicupdate)  Compatibility (Compat): [https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-setup-command-line-options#compat](https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-setup-command-line-options#compat) Defining Dynamic Updates is optional (Microsoft default values will be applied if not supplied), but where warnings are received, if Compatibility is not defined, the Fileset will fail to instal the update.
1. Upload the provided Fileset using FileWave Admin 2. Upload the downloaded ISO into the same folder as the Placeholder within the Fileset; approximately 5GB in size. (The .placeholder\_windows\_iso file may be removed). **Ensure the ISO has the same name as the below screenshot: 'Windows\_Upgrade.iso"**  3. Select "FeatureUpgrade.ps1" from the Fileset contents and click "Get Info" from the top menu bar.  4. Select the "Executable" tab within the "Get Info" window.  5. Modify the "Launch Arguments" as desired and click "Apply" to save changes. Remove any unwanted or add any additional arguments from Microsoft's above KB. Please consider the following: - Launch Arguments as a bare minimum: - /auto upgrade - /quiet - Launch Arguments for Windows 11: - /auto upgrade - /quiet - /noreboot - /eula accept - /dynamicupdate disable - /copylogs C:\\Temp\\win11upgradelogs - **IMPORTANT NOTE:** Compat mode will be required if warnings prevent the installer from completing. More details on Windows 11 Launch Arguments here: [Windows 11 Setup Command Line Options](https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-setup-command-line-options?view=windows-11) 6. Associate Fileset to machines and wait patiently for the upgrade to complete. #### Testing When testing, consider disabling the Reboot option in the Fileset properties, such that the Windows interface is still available during the initial process of the upgrade. Windows Task Manager will show "Modern Host Setup" process whilst upgrade is in progress. Timings will vary depending upon chosen options, device usage and network bandwidth. It could take 30-40 minutes or more before the device shows the Windows Update blue screen; as the update prepares the device and other possible updates. It should also be expected that the device may reboot multiple times.It could also be possible to have the ISO available via a network mount and adapt the script to mount the shared ISO rather than pushing the ISO via FileWave.
#### User Experience Due to the nature of how Microsoft Feature Updates work, there can be a substantial amount of time between the launch of the update and the device continuing to the Blue Updates Screen. Where the Reboot option is selected for the Fileset, this wait will not commence util the user accepts the update. As such the FileWave user prompt may be on the screen for a lengthy period of time. If the reboot option is not selected, although the user will not be impacted by this preliminary stage of the Feature Upgrade, once completed, the user will suddenly be dropped out of their user session, without warning, for the installation and reboots to take place. # Notify Users with a dialog (Windows) ## Description The provided Fileset is an example of notifying users, in particular here, a message regarding Fileset status when downloading and installing new Filesets.  The Fileset is designed to: - Create a continual running service that monitors Fileset changes - Where Fileset changes occur, begin monitoring the FileWave Client log file - If a number of preset text strings are found in the log file, send this to the Notification Centre - Lastly, where another preset text is found, stop monitoring the log file The service has been built to be actioned automatically by the user logging in. Where Filesets are disassociated, each has a pre-uninstallation script to ensure the services should also be removed. ## Ingredients - Provided Fileset:| ↓ Windows |
| [](https://kb.filewave.com/attachments/152) |
| **Example Wallpaper Fileset** |
| [](https://kb.filewave.com/attachments/475) |