Blogs

Desktop Authority - Managing Chrome with Group Policy Templates.

While Desktop Authority can manage Internet Explorer and Firefox by default some may like to manage Chrome. This can be accomplished in Desktop Authority by using the Group Policy templates element under the User Profiles object. Please download the Group Policy templates from Google located here Please unzip the files and follow the steps below. 

 Select Group Policy Templates under the user profile to be modified. Then click the Add button.


Oljbyx.png

            Select the Add/Remove ADM Files button, then click on Import Template Files button.


        YXjQ1e.png


          Next browse to the location of the Chrome ADM template previously downloaded.


         irL5r8.png       


         Next click on Settings to begin configuring the Chrome settings as needed. Expand the tree listed as Templates to find the necessary Chrome configuration settings.


        HUIwZW.png


        Select the fields to edit, this will open up a dialog box to the right. Configure as needed.  

                        

        pWGVqJ.png




        Edit the Validation Logic settings to configure for specific groups as needed and save when all necessary edits are complete.



I hope you find this article useful, please comment/vote with any feedback you may have.

Thanks!

 

 



1

Be the first to comment

Hardware change notification alert - K1000

There are some situations where you might need to get notified if something like RAM amount changes on your devices. 

This article shows an example of how you could accomplish something like this. 

Method 1: MySQL method


  1. Create a new device notification (Reporting > Notifications > Choose Action > New > Device Notification)
  2. Use the default search it makes (doesn't matter since we will be changing in the next step) and click Save
  3. Once created, click the name of your notification, and click "To edit the Notification using this editor, Click Here". To see the list of notifications, click Reporting > Notifications
  4. Paste the MySQL query from below in:

Select Distinct
  A.NAME As "Machine Name",
  A.VALUE1 As 'RAM Before',
  A.VALUE2 As 'RAM After'
From
  ASSET_HISTORY A
Where
  A.FRIENDLY_FIELD_NAME = 'RAM Total' AND
  A.TIME > Date_Sub(Now(), Interval 24 hour)

I have this looking at any RAM changes within the last 24 hours and set it up as a notification, but this could also be done within a report. 

Method 2: Asset History search


If you want a more GUI-friendly way to build something, you can use Settings > History > Asset History Reporting to do advanced searches, that you can then turn into reports/notifications. This will be similar to Method 1 since we will still ultimately use a MySQL query in the end, but this will help you build your notification much easier from scratch. 

TMHUar.png


In this example above, I did an advanced search where Field begins with RAM, and Date is during this quarter, but you can customize it whenever you want. 

Then, you can click Choose Action > Create Report. 

You will then be given the MySQL for the report it would create. 

DhphRK.png

Follow the steps from Method 1 to create a custom notification. 



I hope you enjoyed this article, Please comment/vote for any feedback you have. 

Thanks!


Be the first to comment

How to retrieve a missing field from users previously imported from the AD to the K1000 through Ldap

The scenario is the following: You have already imported all the users into your K1000; however, there is a field that you notice is not being pulled from Active Directory and that you know it does have a value (at least for most users). The problem here is that due to performance issues, the K1000 defines the standard fields based on the first 1000 users imported from AD. Therefore, if none of the first 1000 users have a value in the field in question, the appliance will conclude that for all of remaining users this value is also missing and will not import the attribute.


The solution is the following: Take the main account that was used to retrieve the AD information in the K1000, find it in the AD and fill in data in this field with pertinent information. You may also use the Ldap Browser and select one of the displayed accounts to define the fields in the K1000.


In the figures 1 and 2 below, we took one of these accounts and looked it up in the AD and as we can see the missing field (ipphone) has not value.


Figure 1


cbmDRr.png


Figure 2


NnQ4Dk.png


For this reason, even if you manually type the attribute ipphone (figure 3 below) in order to be included in the values to display you noticed that is not showing within the options to choose from (figure 4 below):


Figure 3


VrPMiu.png



Figure 4


LkRpiN.png



Adding a value in the empty field of the account in the AD (Figure 5 below) and then importing again we will see the desired option in the drop-down menu (Figure 6) and the final results is displayed in the user details of the appliance as it is shown in figure 7


Figure 5


Mi8VFd.png


Figure 6


HUEUsr.png


Figure 7


vGzIZY.png



As we may infer from above the best practice would be to make sure from the very beginning using the Ldap browser option that at least one or more of the accounts retrieved have some sort of value in all the attributes that you want to have displayed for all users.

View comments (1)

PACE Suite 4.1 is coming soon



After introducing full support of App-V 5.1 in version 4.0 (July 7, 2016),

we’ve used the summertime to redesign the user interface of PACE Suite.

You’ll enjoy it.

PACE Suite 4.1 is bringing

a new modern look,
standartized UI controls, and
improved usability.


Just focus on the work results instead of focusing on the tool.

Enjoy the enhanced usability provided by the unified styles for

action buttons, menus, fields, captions, panes and other controls.

Find the available functions in a single structured menu.

Enjoy the new wizards.

Discover new way of managing package resources.


This release is dedicated to AppManagEvent

to be held in Utrecht, Netherlands, on October 7, 2016.


Be the first to comment

K1000 SQL Smart Label notes

I just spent a whole bunch of time trying to get an SQL Smart Label to work, only to find that all it needed was a simple notation change to work, so I thought I'd share it, and maybe others who have encountered Smart Label quirks can add their knowledge in the comments as well.

In the report I was converting to a label, I had
from MACHINE M

and used the alias M in the rest of the query.  The report worked fine in KACE and in MySQL Workbench, but no computers were ever being added to that label.  Long story short, as soon as I removed the alias and used the actual table name instead, the Smart Label worked.

This doesn't appear to affect table aliases in JOIN clauses; only the FROM clause.

(K1000 6.4 SP3)

View comments (1)
Showing 1 - 5 of 3005 results