Todd Miller's idea is excellent. That would reduce the ability for end users
to impact the system negatively overall, but still get you the information
you need.

 

The only part I'm rusty on is: how do you grant "Authenticated Users" access
to only a specific "WMI element" (I'm assuming that "WMI element" means "WMI
class" or "instance of a WMI class")?

 

Cheers,

Trevor Sullivan

 

From: [email protected] [mailto:[email protected]]
On Behalf Of Todd Edwards
Sent: Wednesday, November 6, 2013 8:31 AM
To: mssms
Subject: Re: [mssms] SCCM Internet Explorer Homepage Report

 

I like both of those ideas as I am getting to much feedback from DCM. I
might go the route of collecting the information with a script and
populating it into a HKLM key. I will post back with the results of what I
end up doing.

 

On Tue, Nov 5, 2013 at 7:02 PM, Sherry Kissinger <[email protected]
<mailto:[email protected]> > wrote:

My suggestion, similar to this,
http://www.mnscug.org/blogs/sherry-kissinger/249-pstfinder, via inventory.
First script to make a custom wmi location, then a second one to copy the
hkcu value into that custom wmi, and a mof edit to pull it into the db.

My experience with dcm and hkcu is that it works...sorta. you get too much
info back so finding the forest for the trees makes it harder to know the
answer to whatever question you were trying to get answered.

 

"Miller, Todd" <[email protected] <mailto:[email protected]> >
wrote:

You might have to shift the data into the machine space in some way - either
into WMI or HKLM.  

 

You could have a startup script create a HKLM key someplace and then grant
authenticated users write access to the HKLM location.  Then have a logon
script that would write the data into HKLM.  Then a mof edit could collect
the instances in the Key you created.

 

You could also do the same idea, but with WMI entries and granting the edit
rights to Authenticated Users to that particular WMI element.

 

I asked a similar question a week or two ago - I was looking for machines
where the logged in user had a "Cryptolocker" registry key in HKCU present.
I never found a simple solution in DCM even though it seems like DCM should
have been able to show me machines where any user had that Key path
existing.  I eventually gave up.  The above idea is a little rube goldbergy,
but I think it would work fine.

 

From: [email protected] <mailto:[email protected]>
[mailto:[email protected]
<mailto:[email protected]> ] On Behalf Of Todd Edwards
Sent: Tuesday, November 05, 2013 3:49 PM
To: mssms
Subject: [mssms] SCCM Internet Explorer Homepage Report

 

Is there a way for SCCM to collection the HKCU values for each users for
their IE homepage? Would DCM work? I know the extending the mof wouldn't
work because it is HKCU. I have a powershell script that detects the value,
but I'm not sure how I could use it in SCCM.

 

Any help would be great.

 

Todd Edwards

Application Engineer

ConfigMgr MCTS 07&12

 

 

  _____  

Notice: This UI Health Care e-mail (including attachments) is covered by the
Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential
and may be legally privileged.  If you are not the intended recipient, you
are hereby notified that any retention, dissemination, distribution, or
copying of this communication is strictly prohibited.  Please reply to the
sender that you have received the message in error, then delete it.  Thank
you. 

  _____  

 

 

 

 



Reply via email to