[gptalk] Re: Pulling out paths from Group Policy

The actual MSI paths are stored in objects within the GPC with a class of
packageRegistration. So you could absolutely do an LDAP search to pull out
these objects. The path is stored in the attributed called msiFileList.

Darren

-----Original Message-----
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On
Behalf Of Cruz, Jerome L
Sent: Wednesday, January 07, 2009 8:19 AM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: Pulling out paths from Group Policy

Hmmm....

Log onto a DC (for speed, could be done remotely) go to the root of SYSVOL.
Open a CMD prompt and use the Find command to search all files of, say the
VBS extension for your DFS share name(s).

Clunky, but doable.

Also...
If you can't get the GPSI "GYPSY" VIEWER UTILITY mentioned by Darren working
quickly, you can use a GPMC based search. Right+click on a domain and choose
the 'Search...' menu option. The 'Search item' dropdown will be either User
or Computer Configuration. Then choose a 'Value' field of 'Software
Installation' to get a list of GPOs that deploy MSIs. Not as fast as his
tool, but better than nothing to get a list of GPOs that deploy software.
Then you could use other GPMC scripts to run HTML or XML reports for those
GPOs and save them on your hard disk.  Then do a Find against those files
searching for your DFS share names. Again...clunky. Try to get the GPSI tool
to work.

Jerry Cruz | Group Policies Product Manager | Windows Infrastructure
Architecture | CNO | Boeing IT


-----Original Message-----
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On
Behalf Of Darren Mar-Elia
Sent: Wednesday, January 07, 2009 7:58 AM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: Pulling out paths from Group Policy

The script name is stored in the scripts.ini file within SYSVOL, so you
would basically have to write some code to iterate through the
SYSVOL\Policies structure, look for and read each of those files and figure
out if your paths are there.

Darren

-----Original Message-----
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On
Behalf Of Dave Sharples
Sent: Wednesday, January 07, 2009 7:50 AM
To: 'gptalk@xxxxxxxxxxxxx'
Subject: [gptalk] Re: Pulling out paths from Group Policy

Mainly looking for the script name in the GPO - if people really have put
embedded server names inside scripts themselves - then good luck to them :)

>-----Original Message-----
>From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx]
>On Behalf Of Darren Mar-Elia
>Sent: 07 January 2009 15:44
>To: gptalk@xxxxxxxxxxxxx
>Subject: [gptalk] Re: Pulling out paths from Group Policy
>
>Dave-
>Well, you can definitely do it via scripts. For the Software
>Installation
>stuff, you might want to check out my free GPSIViewer utility out on
>GPOGUY.COM. Essentially it dumps all packages in a domain into a GUI
>list
>that shows the package path within the UI. I don't remember off-hand but
>it
>may also have a feature to export the list (you'd think I'd know since I
>wrote it but I don't have it handy at the moment!). As for startup
>scripts,
>are you looking for embedded paths within the actual scripts? If so,
>then
>you'll probably need to write some text parsing to handle that.
>
>Darren
>
>-----Original Message-----
>From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx]
>On
>Behalf Of Dave Sharples
>Sent: Wednesday, January 07, 2009 7:27 AM
>To: gptalk@xxxxxxxxxxxxx
>Subject: [gptalk] Pulling out paths from Group Policy
>
>We use group policy for software installations (both MSI and scripted
>ones),
>we use a DFS share for 4 replicated servers which hold the software
>files.
>What we are looking for is a way of pulling out the GPO's which use a
>specific server name in the path instead of the DFS name (the servers
>are
>being replaced so any GPOs which reference them won't work anymore).
>
>We have ~2000 GPO's so going through each one will probably make me go
>loopy.
>
>Anyone know a better way, would need to look in the Software
>installation
>name and the startup scripts part (both user and machine)
>
>Cheers
>
>Dave
>***********************
>You can unsubscribe from gptalk by sending email to
>gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR
>by
>logging into the freelists.org Web interface. Archives for the list are
>available at http://www.freelists.org/archives/gptalk/
>************************
>
>***********************
>You can unsubscribe from gptalk by sending email to gptalk-
>request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by
>logging into the freelists.org Web interface. Archives for the list are
>available at http://www.freelists.org/archives/gptalk/
>************************
***********************
You can unsubscribe from gptalk by sending email to
gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by
logging into the freelists.org Web interface. Archives for the list are
available at http://www.freelists.org/archives/gptalk/
************************

***********************
You can unsubscribe from gptalk by sending email to
gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by
logging into the freelists.org Web interface. Archives for the list are
available at http://www.freelists.org/archives/gptalk/
************************
***********************
You can unsubscribe from gptalk by sending email to
gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by
logging into the freelists.org Web interface. Archives for the list are
available at http://www.freelists.org/archives/gptalk/
************************

***********************
You can unsubscribe from gptalk by sending email to 
gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by 
logging into the freelists.org Web interface. Archives for the list are 
available at http://www.freelists.org/archives/gptalk/
************************

Other related posts: