Home > Uncategorized > Networking: WMI Filtering for Group Policy Object Application or WMI for FQDNing some properties

Networking: WMI Filtering for Group Policy Object Application or WMI for FQDNing some properties

You can use the adsysteminfo in a VBScript to find the FQDN of some objects (such as a computername or username). Check out these other properties.

The syntax would be:
set o = createobject(“adsysteminfo”)
o.username
o.computer

I’m trying to figure out a way to get software packages to deploy per-department (OU) while leaving that GPO linked to each OU, but not applying (after first deployment).
Maybe if we roll it out, applying to another OU nightly until all OUs are covered, this will work.

I did notice that if you remove the link of a GPO, the OU/PCs in OU are “aware” of the software installation policy, but if you re-link the GPO the packages will redeploy. This is not a practical way, as you may want to upgrade, or install packages, using the package removal options.

The WMI Filters function of GPO application may help. I’m interested in finding out if you can make WMI Filters self-aware of an FQDN (say, the computer’s).

Advertisements
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: