hnewman1 Absent Member.
Absent Member.
753 views

How to reliably ensure Force Runs for users

I'm struggling with reliably getting settings to users with the events/schedules available. Here's an example: I have a set of HKCU registry settings that needs to be standardized for all users. I have two requirements:
1. It needs to go to the device immediately after IE10 is installed and the device reboots.
2. It needs to go to all devices at some point, regardless of whether or not the user reboots or logs in.

Device association > Event > User Login works for #1, as long as there is a logout/login or reboot
Device association > Recurring Event > Device Refresh works for #2, as long as the user is logged in

I can't have two different device associations for the same group of devices, so I'm wondering if this is a valid approach:

User association > Event > User Login - handles #1 at the time of logout/login or reboot
Device association > Recurring Event > Device Refresh - handles #2 when the user is already logged in

I hate the idea of cluttering up the bundle list on the ZAA Properties by having two associations, but I can't think of any other way to do this. Any ideas?

Holly Newman, MCNE Sr Systems Engineer Jackson Family Enterprises
Labels (2)
0 Likes
3 Replies
hnewman1 Absent Member.
Absent Member.

Re: How to reliably ensure Force Runs for users

This also raises a separate issue that I've never quite figured out. When dealing solely with HKCU entries (I've learned to separate them from HKLM), what's the value of running as User or as System/write to Current User? I've never figured that one out.

Holly Newman, MCNE Sr Systems Engineer Jackson Family Enterprises
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: How to reliably ensure Force Runs for users

User's may not have full access to all portions of the HKCU Hive.
Generally this is not an issue, but the "Policy" portion of the User
Hive is one example and for obvious reasons.....

On 5/6/2014 3:26 PM, hnewman wrote:
>
> This also raises a separate issue that I've never quite figured out.
> When dealing solely with HKCU entries (I've learned to separate them
> from HKLM), what's the value of running as User or as System/write to
> Current User? I've never figured that one out.
>
>



--
Craig Wilson - MCNE, MCSE, CCNA
Novell Technical Support Engineer

Novell does not officially monitor these forums.

Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: How to reliably ensure Force Runs for users

#1 - Depending on the Settings, Consider a GPO to ensure it is set at
every logon.

#2 - Update All Profiles as Part of the Install.
Create a Script that uses "REG.exe" to load each profile on the PC and
update all local profiles at once. This can even be done when nobody is
logged on. Make sure to also update the "Defaul User" Profile.
This way even FUTURE profiles are updated immediately.
Takes a bit of scripting ability, but nothing too unusual.

On 5/6/2014 2:26 PM, hnewman wrote:
>
> I'm struggling with reliably getting settings to users with the
> events/schedules available. Here's an example: I have a set of HKCU
> registry settings that needs to be standardized for all users. I have
> two requirements:
> 1. It needs to go to the device immediately after IE10 is installed and
> the device reboots.
> 2. It needs to go to all devices at some point, regardless of whether or
> not the user reboots or logs in.
>
> Device association > Event > User Login works for #1, as long as there
> is a logout/login or reboot
> Device association > Recurring Event > Device Refresh works for #2, as
> long as the user is logged in
>
> I can't have two different device associations for the same group of
> devices, so I'm wondering if this is a valid approach:
>
> User association > Event > User Login - handles #1 at the time of
> logout/login or reboot
> Device association > Recurring Event > Device Refresh - handles #2 when
> the user is already logged in
>
> I hate the idea of cluttering up the bundle list on the ZAA Properties
> by having two associations, but I can't think of any other way to do
> this. Any ideas?
>
>



--
Craig Wilson - MCNE, MCSE, CCNA
Novell Technical Support Engineer

Novell does not officially monitor these forums.

Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.