Deploying WPSecure Personalization Packages using Intune
WPSecure Personalization Packages allow you to customize various aspects of your organization’s devices, such as the desktop wallpaper, screensaver, and Outlook signature. These packages can be deployed using Intune.
Step 1: Opening the Packager
You can launch the Windows Personalization Packager from the start menu. You will be presented with the ‘Terms of Use and Service’ page upon opening the application. Please take a moment to review it. If you want to try the Packager before purchasing a subscription, you can click on the ‘Click on this link to try the demo’ button in the screen’s top right corner.
If you have already purchased a subscription, you can access the full version of the Personalization Packager by clicking on the ‘Click here to agree to the terms and start the application’ button.
You can log in using your subscription’s email address and password. If you do not know or remember your password, click the “Forgot your password” link. A password reset email will be sent to the email address if such a subscription exists. If you have logged in before and your access token has not expired, the authentication will happen silently and the authentication box will not appear.
A successful login process should land you on the following Screen. All the action concerning the Windows Personalization Packager happens on this Screen. The layout is simplistic, and the process is self-explaining.
Step 2: Preparing the desktop background images
The Packager allows you to open one or more images in JPG format from a selected folder. The packager only allows up to 90 desktop background images of varying dimensions and orientations. The size of each image cannot exceed 10 MB. Image Width and Height cannot be a decimal/fraction. The images folder will look similar to the image below.
Step 3: Importing Desktop background images
Click the ‘Import desktop background images from folder‘ button. This enables you to import multiple images in JPG format from a selected folder.
Choose one or more files to import. ‘Select all‘ to import all JPG files. Please refrain from altering the images after import or in preview mode. Doing so will result in a fatal error and cause the process to fail. If one or more items should fail import, the following screen will report the failed item. You can understand the problem better by looking at the log file in the following location.
%temp%\wpsecure-packager.log
After the import process completes, scroll up and down to check for any warnings or errors. Click the “Close the notification panel and return to application” button to view the imported personalization list.
Click each item to preview it.
Note: Please refrain from altering the items while in preview mode. Doing so will result in a fatal error and cause the process to fail.
Step 4: Importing Microsoft Outlook signature
There are two types of Microsoft Outlook signatures: a ‘New message’ signature and a ‘Reply message’ signature. The total file size of each Outlook signature and its assets cannot exceed 10 MB.
New message signature: A new message signature is used when composing a new Microsoft Outlook message. It should include a ‘wpsecure_new.htm’ HTML file and optionally include a ‘wpsecure_new.txt’ Text file and an optional ‘wpsecure_new_files’ directory that contains resource files like images, CSS, etc.
Reply message signature: A reply message signature is used when replying to an email message. It should include a ‘wpsecure_reply.htm’ HTML file and optionally include a ‘wpsecure_reply.txt’ Text file and an optional ‘wpsecure_reply_files’ directory that contains resource files like images, CSS, etc.
Use placeholders like {{last_name}}, {{email_address}}, or {{job_title}} in the ‘wpsecure_new.htm’, ‘wpsecure_new.txt’, ‘wpsecure_reply.txt’, and ‘wpsecure_reply.txt’ files to automatically load user-specific data at runtime. The WPSecure Outlook signature engine replaces the placeholders with the information in the registry corresponding to each placeholder. If the Key path does not exist create it. For example, the placeholder {{last_name}} will be replaced by the following registry entry.
| Key path | HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\wpsecure\signature |
| Name | last_name |
| Value | John Doe |
| Type | REG_SZ |
Step 5: Importing Windows screensaver
The file size of the screensaver file must be at most 20 MB. The file extension is .scr
Regarding input quality for the screensaver, it’s important to ensure that the images or videos used are of high resolution and quality. This will help to create a visually appealing and professional-looking screensaver.
There are several tools available that can be used to create custom screensavers for Windows. One way to create a screensaver is to use the built-in tool in Windows 10. You can arrange your desired screensaver photos in a folder of your choice, then access the Personalize applet by right-clicking anywhere on the desktop. From there, you can select the Lock Screen tab and then go to Screen Saver settings. In the window that opens, select Photos from the dropdown menu and configure the settings according to your preferences.
Another option is to use a third-party tool such as Canva or Adobe Spark. These tools offer a range of templates and design elements that can be used to create custom wallpapers and screensavers. With these tools, you can easily upload your own images or choose from a library of stock images to create a unique and personalized screensaver.
Step 6: Create a personalization package
Use this button to export the personalization package to a folder. The selected destination folder has to be empty. The personalization package creation process creates two folders: general_install and intune_install.
The general_install folder contains installation files for deployment via enterprise software management tools like Microsoft Endpoint Configuration Manager (SCCM). Run the ‘wpsecure-install.exe’ to install the personalization package. More details regarding the enterprise installation and uninstallation process are in the ‘documentation.html’ file.
The intune_install folder contains the ‘wpsecure-install.intunewin’ file that can be uploaded to the Microsoft Endpoint Device Management portal (Intune). The command-line for this is identical to the general install.
The process also creates a ‘documentation.html’ file that provides all the information required to deploy the personalization package, like package version, install command line, uninstall command line, and detection methods.
Step 7: Create an Intune app and assignments
The intune_install folder contains the ‘wpsecure-install.intunewin’ file to be uploaded to the Microsoft Endpoint Device Management portal (Intune).
The ‘documentation.html’ file provides all the information required to deploy the personalization package, like package version, install command line, uninstall command line, and detection methods.
The following screenshots show areas in the ‘documentation.html’ file used to set up the application in Microsoft Intune.
Go to the Endpoint Manager portal
Browse to Apps / All Apps and click Add
Select Windows app(Win32) from the App type drop list.
On the App Information pane click Select App package file and select the previously created .intunewin file and click Ok
Select the ‘wpsecure-install.intunewin’ file in the intune_install folder.
Copy and paste the Install and Uninstall command lines from the ‘documentation.html’ file and click Next.
Select Operating System architecture as 64-bit and minimum operating system as “Windows 10 20H2” and click Next.
On the detection rules page, choose “Manually configure detection rules.” Click on Add.
Select the rule type as File and copy the path from the ‘documentation.html’ file. Choose the Detection method as String (version) and Operator as “Greater than or equal to”. The value will be the version number of your Personalization package.
Click Next on Dependencies and Next on Supersedence and make the necessary assignments. That’s it, you are all set to receive the Personalization package.
