Technical Requirements & Recommendations
Required Software
Microsoft .NET Framework 4.0
Prerequisites
Compatibility Notes
TLS 1.2 for Older Windows Versions
For systems running Windows 8.0 or earlier (e.g., Windows 7), TLS 1.2 is not enabled by default. To ensure secure communication, follow this article to manually enable TLS 1.2 on these systems. Windows 8.1, Windows 10, and later natively support TLS 1.2 and do not require any additional configuration.
Deploy via Group Policy
To deploy .NET Framework 4 across your network, you must use a startup script. Unlike earlier versions, such as .NET Framework 1.1, it is no longer possible to push out .NET Framework using an MSI file. Follow these steps to deploy .NET framework 4.0 to all x86 and x64 windows based PC's on your network:
- Copy and modify* the startup script below, then save your script asframeworkinstall.bat
*Modify the DeployServer path to suit your environment:
setlocal
REM *********************************************************************
REM Environment customisation begins here. Modify variables below.
REM *********************************************************************
REM Enter the Product Name.
set ProductName=Microsoft .NET Framework 4 Client Profile
REM Set DeployServer to a network-accessible location containing the Office source files.
set DeployServer=\\kbomb.local\netlogon\software
REM Set LogLocation to a central directory to collect log files.
set LogLocation=C:\Windows\Logs
REM *********************************************************************
REM Deployment code begins here. Do not modify anything below this line.
REM *********************************************************************
IF NOT "%ProgramFiles(x86)%"=="" (goto ARP64) else (goto ARP86)
REM Operating system is X64. Check for 32 bit Office in emulated Wow6432 uninstall key
:ARP64
reg query "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432NODE\Microsoft\Windows\CurrentVersion\Uninstall\%ProductName%"if NOT %errorlevel%==1 (goto End)
REM Check for 32 and 64 bit versions of Office 2010 in regular uninstall key.(Office 64bit would also appear here on a 64bit OS)
:ARP86
reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%ProductName%"
if %errorlevel%==1 (goto DeployOffice) else (goto End)
REM If 1 returned, the product was not found. Run setup here.:DeployOffice
start /wait %DeployServer%\dotNetFx40_Full_x86_x64.exe /passive
echo %date% %time% Setup ended with error code %errorlevel%. >> %LogLocation%\%computername%.txt
REM If 0 or other was returned, the product was found or another error occurred. Do nothing.
:End
Endlocal - Copy the saved .bat file into the startup script folder inside the Group Policy Object (GPO). Be sure to use a startup script, not a logon script.

- Link this group policy object to your computer accounts.
- When the workstations refresh their group policy, they will automatically install .NET Framework v4 on the next reboot.

Considerations
- Screensaver & Lock Screen Settings: If you're running the Screensaver and Lock Screen channels, you cannot set the Lock Screen to Slideshow mode as this is not supported in Windows. Doing so will disable the Screensaver and prevent it from functioning as intended.
- Screensaver - Device Power Settings Recommendations
- Adjust the device's power settings to keep the Vibe.fyi Screensaver visible for extended periods when the PC is idle.
- Set the "Turn off the display" option to 30 or 60 minutes. This balances communication reach with energy efficiency.
Group Policy Deployment (Recommended for IT Admins): Configure a Group Policy to restrict user access to Screensaver, Lock Screen, and Background settings during deployment. This prevents users from altering these settings, ensuring uniformity and compliance with deployment standards.
Related Articles
Windows Install Guide: Desktop Player (Intune)
Prerequisites IT / Vibe Admin Read the Technical Requirements & Recommendations guide. Install .Net Framework 4.0 on all target PCs before installing the Vibe.fyi Vibe Desktop Player app. [Learn more] Create the Desktop Channel licences for your ...
Checklist for Desktop Channel Setup
Follow these essential steps to set up a Desktop Channel and display content on the Lock Screen, Background Wallpaper, or Screensaver. This guide covers: ✅ License setup ✅ Playlist creation & content compatibility Step 1 (Optional): Set Up ...
Windows Install Guide: Desktop Player (MSI Deployment)
Prerequisites IT / Vibe Admin Read the Technical Requirements & Recommendations guide. Contact your Vibe Support team to request the latest Vibe Desktop player.msi installer. Install .Net Framework 4.0 on all target PCs before installing the Vibe.fyi ...
Install Guide - Windows
Prerequisites Review the Install Checklist (read the hardware and network requirements before proceeding). MSI/InTune: Contact your Vibe Support team to request the latest Vibe Desktop player.msi installer. If you're upgrading the Vibe.fyi player app ...
Setup Guide - Zoom Rooms
This guide provides detailed steps for configuring Vibe to work on Zoom Rooms compatible devices. Follow the instructions below to ensure proper setup and optimal functionality. Prerequisites Device Compatibility The URL option for digital signage ...