WPSecure wallpaper deployment has been designed for side by side deployment of wallpaper versions. This feature enables organizations to change a message, introduce a new message or have different messages for varying working groups within the organization. The WPSecure campaign manager controls this function.
The WPSecure campaign manager is used to create a ‘wpsecure.campaigns‘ file. Depending on your system architecture, the ‘wpsecure.campaigns‘ file has to be generated and placed in the following location. ‘wpsecurecc.exe‘ command is used to automate this process. ‘wpsecurecc.exe‘ command is installed with ‘WPsecure campaign manager” (Download here). More information regarding ‘wpsecurecc.exe‘ is available at the bottom of this page.
To edit or create a ‘wpsecure.campaigns‘ file, launch “WPSecure campaign manager” from the start menu.
After you launch the campaign manager; you’ll be presented with an informational screen. Read it and click the button at the bottom of that window to move to the next page.
Campaign schedules and details are added to the next page.
Click on the “Click to add new campaign” button to add a new campaign. Use the “Click to remove selected items” button to select and remove an item.
Use the “Click to generate a new campaign file” button to save all your campaigns into the ‘wpsecure.campaigns‘ file. You can edit a ‘wpsecure.campaigns‘ file by importing the file using the “Click to import old campaign file” button.
The ‘wpsecure.campaigns‘ file has within it a list of campaigns with the following details.
1) Campaign Number (ID): Campaign number is the title or name of the campaign. Each item in the ‘wpsecure.campaigns‘ file will be assigned a campaign number. If WPSecure wallpaper history recording is enabled, the campaign number associated with the WPSecure wallpaper package will also be recorded. The campaign number should be a number between 1 and 99999999.
2) WPSecure Package Version: This is the version number corresponding to the WPSecure wallpaper package. A WPSecure wallpaper package version can be a member of multiple campaigns. The maximum version number is 255.255.65535.65535.
3) Campaign Priority: If a scheduling conflict should arise, the campaign priority (1 -highest priority, 99999999 – lowest priority) will be used to make a decision on which WPSecure wallpaper package version to pick. If multiple WPSecure wallpaper packages have the same campaign priority then the highest WPSecure wallpaper package version would be picked. The campaign priority should be a number between 1 and 99999999.
4) Campaign group number (ID): This value creates a relationship between the user (employee) and a campaign (campaign number). The WPSecure wallpaper loader automatically picks all the campaigns associated with the current user’s “Campaign group number/ID“. The campaign group ID /number is set both in the ‘wpsecure.campaigns‘ file and in the Current Users Registry as seen in the image below. Use group policy or PowerShell scripts to deploy this setting to users. This setting can be based on the employee’s department, business unit, group membership, geography, or something else. The campaign group number should be a number between 0 and 99999999.
If the above registry setting is absent/incorrect or not matching with the entries in the campaign list within the ‘wpsecure.campaigns‘ file then the campaign group number/ID is set to 0 (Zero).
If WPSecure wallpaper history recording is enabled, the campaign group number associated with the WPSecure wallpaper package will also be recorded.
5) Campaign Start and End days: As the name indicates these are the start and end days of the campaign. The start and end days cannot overlap with another campaign that has the same WPSecure wallpaper package version and campaign group number.
Automating campaign file deployment:
‘wpsecurecc.exe‘ command is used to automate this process. ‘wpsecurecc.exe‘ command is installed with ‘WPsecure campaign manager” (Download here).
Copy the file ‘wpsecurecc.exe‘ to the desired location. Copy the ‘wpsecure.campaigns‘ file to the same location.
‘wpsecurecc.exe‘ will only be run as administrator; When run, ‘wpsecure.campaigns‘ file is copied to ‘WPsecure’ folder within program files.
Using the above automation you can deploy the ‘wpsecure.campaigns‘ file using SCCM or Intune.
The workflow:
WPSecure wallpaper loader will initialize during the following triggers.
- At login.
- At unlock.
- After a WPSecure wallpaper package version is installed.
- After a WPSecure wallpaper package version is uninstalled.
When the WPSecure wallpaper loader is initialized it does the following.
- Checks if WPSecure loader is enabled in the registry. If disabled, exits immediately without altering the current wallpaper setup.
- Identifies a list of locally installed WPSecure wallpaper package versions. If no WPSecure wallpaper packages are installed, sets the default windows wallpaper.
- Verifies the existence of the ‘wpsecure.campaigns‘ file. If absent, loads the highest locally installed WPSecure wallpaper package version.
- If the ‘wpsecure.campaigns‘ file exists, the WPSecure loader reads the file and stores all the campaigns in memory.
- The WPSecure loader process creates a shortlist of all the campaigns based on the machine time/date and the current user’s campaign group number assignment.
- If multiple campaigns are available for a user. A second shortlist is created based on the campaign priority.
- If multiple campaigns are available for a user. A third shortlist is created based on the WPSecure wallpaper package version.
Please note: WPSecure wallpaper packages will work without the ‘wpsecure.campaigns‘ file. If ‘wpsecure.campaigns‘ file is not used the latest version of the locally installed WPSecure wallpaper package will be used.
