Prepare MSI for deployment

1. Read the checklist
   
2. Required - Update the SITE_URL, enable the relevant channels and enter the auth codes
   
3. Update other MSI command variables as required. NB: Yes and No values are case sensitive and must be written as shown below.

Note: if no switch is specified (i.e. SS_WAIT_MIN="5"), the default value shown in the list below will be applied.

Troubleshooting Notes: Switch names are case sensitive and must be in all capital letters, while Switch values are not case sensitive.

1. Vibe.fyi player app
   
1. SITE_URL (required) - Enter the unique Vibe.fyi Screensaver URL provided by your Vibe support team.
   
2. RANDOM_START: To ensure variety and prevent the same slide (e.g. Slide 1) from always appearing first, the Wallpaper Background and Screensaver slides can start at a random position. This setting can be enabled or disabled (Yes/No). Default = Yes
3. SYNC_INTERVAL_MIN: The number of minutes between synchronising slide updates for screensaver, desktop wallpaper and lock screen. Default = 30 
   
4. HIDE_SETTINGS: Enter Yes or No to show or hide your Desktop Player Settings. Default =Yes
   
5. DISABLE_APP_CLOSE: Enter Yes or No to disable/enable the ability to close the Desktop Player app. Default = No
6. AUTO_LOAD: Enter Yes or No to load the app upon startup of your device. Default = Yes
   
7. OVERWRITE_USER_SETTINGS  (optional) - Used for upgrades only. This parameter determines whether any user settings, which have been manually changed by the user, will be overwritten. Default = Yes
   
   
2. Windows Screen Saver Settings
   
1. SS_WAIT_MIN: Set the wait time in minutes before the screensaver will activate. Default = 5 
2. SS_ON_RESUME: Enter Yes or No to configure whether the "On resume, display logon screen" setting is enabled. Default = Yes
   
   
   
3. Power Options - The Console Lock Display Off Timeout in Advanced Power Options determines how long the display stays on after the computer is locked, with a default of 1 minute. To ensure the screensaver activates while the lock screen is active, set the WAIT_ times longer than SS_WAIT_MIN. The difference between these times controls how long the screensaver displays before the screen turns off. 
1. CONSOLE_LOCK_TIMEOUT: Enter Yes or No to show or hide your Vibe.fyi Screensaver content when the lock screen is activated. Default = Yes
2. WAIT_PLUG: Set the display to turn off after 'X' seconds when plugged in. Default =1800
   
3. WAIT_PLUG_LOCK: Set the display to turn off when the screen is locked after 'X' seconds when plugged in. Default = 1800
   
4. WAIT_BATT: Set the display to turn off after 'X' seconds on battery. Default = 600 
   
5. WAIT_BATT_LOCK: Set the display to turn off when the screen is locked after 'X' seconds on battery. Default = 600
   
   
4. Screensaver
   
1. ENABLE_SS (optional): Yes/No to Enable/Disable the screensaver. Default = No
2. SS_LOGO (optional): The Vibe.fyi logo displays briefly when the Screensaver starts. To customise the logo, provide a secure public URL to your desired logo (e.g., https://public_website_address/logo_file_name.png). The logo must be in PNG format. Once specified, the application downloads the logo and stores it locally at: C:\Users\[username]\AppData\Roaming\VibeScreensaver\custom\logo_remote.png
3. SS_AUTHCODE: Enter your unique Screensaver AUTH CODE.
   
4. DISABLE_SS_INFOBAR: Whether the information bar is disabled or not (Yes/No). Default = No
5. SS_INFOBAR_SYNC_SEC: The number of seconds between information bar syncs. Default = 30
   
   
5. Background Wallpaper
   
1. ENABLE_BG: Enter Yes/No to Enable/Disable the Background Wallpaper. Default = No
2. BG_AUTHCODE: Enter your unique Background Wallpaper AUTH CODE.
3. BG_IMAGE_INTERVAL_SEC: The number of seconds between the background image changing. Default = 30
   
   
6. Lock Screen
1. ENABLE_LS: Enter Yes/No to Enable/Disable the lock screen functionality. Default = No
2. LS_AUTHCODE: The AUTH code for the Lock screen images
   
3. LS_TIMEOUT_MIN: The number of minutes that the lock screen will display for before the PC goes to sleep. Default = 60

Deploy via Intune

1. Login to https://intune.microsoft.com and open Apps
2. Under 'By platform', click Windows
   
3. Click + Add
   
   
   
   
   
   
4. Under App type, select Other / Line-of-business app
   
   
   
5. In the Add App screen, click select app package file, select the MSI file provided (e.g. Vibe Desktop Player.1.X.X.quiet_mode_only.msi), then click OK.)
   
   
6. Under App Information
   
1. Name - Vibe Desktop Player
2. Description - Vibe Desktop player setup wizard application push
   
3. Publisher - Vibe.fyi Limited
   
4. Command-line arguments - /quiet
   
   

   Ensure that there is space after each Variables when configuring Command-line argument in Intune. Missing spaces between variables can cause errors in the deployment or execution process.
   
   Correct way
   
   Wrong 
   
   
5. All other settings can stay default
   
6. Click Next
   
   
   
   
7. Under Assignments (Required), add a group or select all devices (this will depend on your organisations Intune setup), then click Next
   
   
   
8. Review App creation and click Create. This should now push out on the next Intune Policy sync.
9. After installing the Vibe.fyi Vibe Desktop Player app, the target PCs need to be restarted for the changes to take effect. Please schedule a restart via Group Policy / Intune.
   
   

Microsoft .Net Framework 4.0

Required: Please install .Net Framework 4.0 on all target PCs before installing the Vibe.fyi Vibe Desktop Player app.

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:

1. Copy and modify* the startup script below, then save your script as frameworkinstall.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

1. 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.
   
2. Link this group policy object to your computer accounts.
3. When the workstations refresh their group policy, they will automatically install .NET Framework v4 on the next reboot.
   

Custom Logo

To use a custom logo, apply the SS_Logo switch during MSI deployment, or follow the manual steps outlined below after installation.

Logo Design Guidelines

Create your logo as a transparent PNG file and save it as logo.png.

1. The custom logo should be a square PNG file with a maximum size of 567 x 567 px and a transparent background.
   
2. For reference, the default Vibe logo measures 567 x 158 px.

Adding Your Logo

Option 1: Default Folder

Manually copy the logo.png file to the following directory:

C:\Users\<username>\AppData\Roaming\VibeScreensaver\custom\

Option 2: Custom Folder Location

If you prefer a custom location for the logo, set it using the following registry value:

HKEY_CURRENT_USER\SOFTWARE\VibeScreenSaver\CustomLogo

This can be done either manually or via Group Policy.

Info 

If you wish to manually Update Auth Codes in the Registry

Please update the following registory - \HKEY_CURRENT_USER\Software\VibeDesktopPlayer

• ApiAuthCode = Screensaver Auth Code
• LockScreenApiAuthCode = Lock Screen Auth Code
• DesktopBackgroundApiAuthCode = Desktop Auth Code
  

Troubleshooting Notes

Check Your Command Lines! Ensure the following guidelines are followed:

• MSI Switch names (i.e. SS_WAIT_MIN) : Case sensitive and must be in UPPERCASE.
• Switch values (i.e. Yes / No) : Not case sensitive. 
  

Ensure there are no existing Group Policies that might override the above settings, as any active Group Policies will take precedence over changes made during the Vibe Desktop Player installation