Related Tips & Info

ZENworks knows the difference!

MigrationDeletedUser
0 Likes

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.









Click to view.


Labels:

How To-Best Practice
Comment List
Parents
  • 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?
  • in reply to MigrationDeletedUser
    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
Comment
  • in reply to MigrationDeletedUser
    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
Children
Related
Recommended

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.