Sending User Notifications
For me, when designing user workspaces, user experience is key. In my opinion the system should notify a user when something with the user workspace is wrong.
For example, when a RESONE Workspace UserSetting location or Home folder is not available, the system should notify the user that it is not available and should ask to contact the system administrator. This can be done with a simple message box, but when using Microsoft Windows 10 it is much cooler to use a notification from the Action Center.
To detect if something is wrong, I use a two-step process. First I use the Location & Devices feature from RESONE Workspace. When detecting if the user has a home directory, I create a Zone called NO-HOMEDRIVE with a rule based on Configuration – Files and Folders – File or Folder Exists – Drive H: Does NOT exists.
Second step is to create a Execute Command based on the just created zone. The Execute Command will use a PowerShell script to send the notification.
This is my PowerShell script:
Generally speaking, I use notifications for the following events:
No Home drive
No RESONE Workspace User Settings folder
Inform users using Development/Test environment.
Inform users using Management workstation.
Wrong workstation deployment / OU placement.
A RESONE Workspace BuildingBlock is also provided for your convenience, see Attachments download below.
UPDATE January 13, 2017: I added a Start-Sleep command at the beginning of the script to wait for 60 seconds. Dennis van Dam mailed me the script wasn't working. It turned out, when starting a new session, the toast notification class is not ready at logon. Just wait 60 seconds, or maybe longer, and then display the message. Another solution is not to use the RESONE Workspace Execute Command and create a hidden autolaunched application.