As promised, more info on ProfileUnity.
Before the first part was published I contacted LiquidwareLabs to verify my findings, it’s only fair to check with them.
They pointed me to something I wrote about the filter they use to control which user gets which configuration.

 At first I thought all configuration settings are in one view, they pointed out that’s not the case.
You can set more than one filter and create configurations for each filter.

After you created this filter you go to Configuration management to create a configuration for these users.
Here, again you create a configuration per user logon scenario, the names here don’t have to match the names you used with the filters.
I used almost the same names.

If you open one of the configuration sets you’ll see all the settings like described before.
This configuration set can be based on group membership if wanted, I would work from the filter management if possible to keep a good overview.

Let’s pick something new, it’s possible to set the Internet Proxy for users.

Like all other configuration options you can create one here.
When creating the Internet proxy configuration settings you have a choice (I love choices).

You can set this setting globally or per configuration management set.
As you can see all filters are listed, I think that’s not that clear. I could set a proxy in the configuration set for terminal servers but connect it with the standard windows user.
It’s easy to misconfigure this, it would be nice if they can connect a configuration set to a filter on a higher level.
Also the global settings, aren’t global anymore if I specify them in a configuration set, I haven’t tested how ProfileUnity works with multiple filters that are valid for one logon scenario.
I would create a global logon configuration and one for each specific logon scenario.

 Anyway, I drifting again….
Good option, Internet Explorer proxy settings.

 Last one for now.. Inventory

 How many of us haven’t ran into it at least once, you need to migrate but the customer has no clue about the desktops currently deployed.
No asset management, no complete or accurate software overview. With ProfileUnity you could create a simple inventory and run it on all desktops.

When creating a configuration set you can choose to upload an XML file or use a reporting server.

The reporting server here is the server where the management console is running on.
In the menu you’ll find an option for inventory.

After the users has been logged on the menu item Inventory gives you details about the configuration of the desktop.
The details when you click are like below. There are no applications for it’s a test desktop


4 thought on “LiquidwareLabs ProfileUnity – Part2”
  1. I really like what you write here, very insightful and smart. One issue though, I'm running Firefox on Fedora and some of your site structure are a little wonky. I know it's not a popular setup, but it is still something to keep an eye on. Just giving you a heads up.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.