Cool Solutions

ZENworks knows the difference!



By:

May 7, 2010 5:13 pm

Reads: 4064

Comments:3

Score:0

If you have ZENworks apps that set configuration settings for your XP and 2000 workstations, you may want to prevent those apps from changing the settings on Windows 7 workstations.

To do this, modify the ZENworks Apps on their “Availability” tab so that it will read the registry key named “HKLM/Software/Microsoft/Windows NT/CurrentVersion/ProductName”

It will either read “Microsoft Windows XP”, “Microsoft Windows 2000″, or it will have one of the various flavors of windows 7.

The best way I’ve found to filter it is to require the key to fit XP or 2000 and anything else is excluded from running the App, as shown below.

Also, I set an environment variable in my login script to match the 10.xx portion of the user’s IP address, then I require my zen apps to read that variable and if it is not 0A11 (10.17 in hex), then my user is on a machine outside of my local lan (using a machine at a remote site) and in that case I also prevent the zen app from firing. This prevents the possibility that one of my users might visit another site, login to one of their workstations, and the workstation wind up re-configured with our locally preferred settings.

VN:F [1.9.22_1171]
Rating: 0.0/5 (0 votes cast)

Tags: , , , , ,
Categories: Uncategorized

Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

3 Comments

  1. By:lhaeger

    Two questions:

    1. Afaik, ZFD7 (as of your screenshot) does not support Win7 anyway. Why do you need to filter apps then?

    2. There’s an “Operating System” requirement that allows filtering by OS version number, why bother re-inventing that through multiple regkey requirements?

    VN:F [1.9.22_1171]
    Rating: 0.0/5 (0 votes cast)
    • By:dmichael

      Q1. Why? Because certain configuration settings that one might need for XP, may need to be different for Windows 7, or may need to be applied differently. If you have Zen apps that currently apply certain settings to XP (but not 2000) based on “Windows Version >= XXXX”, then that app will try to apply those same settings to Windows 7, sometimes with unfavorable results. Identifying Windows 7 as such, while still locked into Zen 7 (2 more months till I switch to Zen 10!) enables me to filter the few Win7 workstations so that they won’t try to apply those changes.

      Q2. The OS version number filtering in Zen 7 is based on a number that can vary based on Service Pack Level, OEM vs. Retail, Home vs. Pro, etc. It worked for XP because I could say “where Windows Version >= xxxxx” which would get all XP but nothing prior. Now that there are multiple flavors of 7 whose version numbers (plural) will be different, it is just easier for me to read the value from the registry key.

      To each his own. Actual mileage may vary.
      8^D

      VN:F [1.9.22_1171]
      Rating: 0.0/5 (0 votes cast)
      • By:spond

        I think what lhaeger meant was why bother checking for Windows 7, since ZDM7 does not run on Windows 7, so there never can be a problem like that

        VN:F [1.9.22_1171]
        Rating: 0.0/5 (0 votes cast)

Comment

RSS