21 May Using The New User Portal for MacOS in EPM 2017.3
Starting with EPM 2017.3 SU3, Ivanti released an all-new MacOS Portal Manager app. The app is responsive, has a very native feel, does not require the user to log in or know a URL, and works seamlessly with the Cloud Services Appliance. This is what it looks like when you are done:
Additionally, during Interchange last week Ivanti announced that Workspaces will be retired. If you are currently using Workspaces to provide a software portal for your end users, you may want to test out the new tool and make a plan to transition your Macs to the Portal Manager for your internal App Store.
If you cannot find the app on your devices, you may need to update the core and the agents to 2017.3 SU3 first. If you already have 2017.3 SU3 deployed you may have tried out the app only for it to came up blank. There are just a few steps for you to do on the backend before your users can use this tool.
Enable the Portal Manager on your Macs:
1- Verify your Portal Manager Agent Setting
Even if you already have one, you may want to review the setting this by opening Tools > Configuration > Agent Settings. Open and review your current Portal Manager agent setting. Most of the branding will not apply to the MacOS Portal, but the other settings do apply. Take note of the setting name.
2- Deploy the Portal Manager Agent Setting with a Change Settings task
Note: You MUST run this task against all Macs after deploying the agent before the Portal Manager tool will work. If you re-deploy the agent, this task may need to be run again. Ivanti has promised a fix in a future release.
From the Agent Settings tool, select the Calendar icon from the taskbar and select “Change Settings…”
Next to the Portal Manager item, click on “Keep agent’s current settings” (it’s a drop-down menu) and select your desired Portal Manager agent setting. Save the task, target a test mac and run the task.
3- Test the Portal
Open the Portal Manager menu option on the test mac. If you already had apps published for Workspaces, then you are done. You can continue to publish apps the same way you did for Workspaces.
If you haven’t previously published “Optional” or “Recommended” packages, this will be empty.
4- Schedule Portal Packages
As it is covered on Ivanti’s website, I won’t go into great detail here.
- Configure the Metadata section for Software Distribution Packages as desired
- Schedule the package and in the task Portal Settings set to either Recommended or Optional
- Organize your portal type tasks in a task group (folder) so you remember not to delete them
- Target devices to the task, using queries or groups if possible
- Run the task (this will only place the metadata for the task in the portal)
- On the endpoint, hit the refresh button on the portal to see the task, then run the task