/build/static/layout/Breadcrumb_cap_w.png

K1000 5.5 smart labels - not working correctly?

I'm trying to make a smart label the same way I'd make one in the past. I'm specifying either wired or wireless for a certain IP range, which has always worked...then either any machine containing 'mac' in the name to differentiate apple machines, or by doing pc name containing "WSiMacRM185" so I make labels for each room of iMacs. This would typically work in the past on 5.4 for me.

Any ideas?


2 Comments   [ + ] Show comments
  • Cannot see the screenshot. - dugullett 11 years ago
  • I am having the same issue.

    When trying to test a smart Label using the below example k1000 will either freeze or do nothing.


    Example smart machine label below:

    Software titles /// does not contain /// Adobe Reader

    OR

    Software titles /// contains /// Adobe Reader

    AND

    Software version /// != /// 11.0.03

    This use to work fine on the older version (5.4). The purpose of the above is to ensure that adobe reader 11.0.03 is installed on the client. I also took it once step further.

    Acrobat has issues when reader installs so I made a smart label called “Has Acrobatâ€. I tried to add:

    AND

    Label Names /// does not contain /// Has Acrobat

    Testing or creating a smart label seems to talk longer or in the above case just bombs out. I close the browser in order to access the k1000 again. I used IE 10, Chrome, Firefox on windows 8. - carminus 11 years ago

Answers (0)

Be the first to answer this question

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ