Mini Monitor Auto Start (Task Scheduler)

[Davey126]

Many of my systems have multiple user accounts and with fast user switching enabled. I like the monitor to display for each user to help track memory hogs. On Vista/Win 7 I typically have to modify the scheduled task so the mini-monitor will launch when each user logs on:

 - General:  Under security options change account to the built-in group "Users" (default is creator's credentials)
 - Settings: Allow new instance to run in parallel

Minor grumble that can wait for a future release. The one gotcha is if someone unticks/ticks the autostart option in Cleanmem the changes mentioned above need to be reapplied.

[Shane]

For vista and newer my program uses mini_monitor_set_startup.exe to make the task schedule.

I could change that exe to make the changes you want then let you have the exe before any next release, since unless I find a reason to make an update might be a while.

But I also have to take into account other users of the program. Will they want it load for each user or just their own account?

One thing you could do instead, since if a user unticks the start up option. Do the old school trick. Put a shortcut into the all users start up folder lol.
But their is one side effect and why I don't do that. if UAC is enabled it will pop up asking for permission to run it every time. Thats why I went the task scheduler path

Shane

[Davey126]

These are general purpose desktops so UAC is always enabled! 
 
Another option is to make the changes previously suggested but modify the default trigger so the task only launches with a specific user vs any user. That way only one TS tab needs to be manually tweaked if the monitor is to be launched for all users. You might consider adding this as a subchoice under autostart (current or all users). Keeps novice users away from TS which is a good thing.
 
Using the startup folder or a registry key is NG for the reasons you outline (already thought of that!)

No need to provide a custom mini_monitor_set_startup.exe. I try to stick with production versions unless actively participating in a beta program. Life is already too complicated. 

[attachments over 25 days old deleted by admin]

[Shane]

Just remind me to update the exe after I get the new program under way. I will forget otherwise lol. Then you can use and test it and we know it will be in the next version of cleanmem when ever I need to make one

Shane

[Shane]

I must not being seeing something. I decided to go ahead and do this now. Checking my windows 7 it is set by default at log on of any user. I think the only setting I need to change is to allow more than one instance to run.

The mini monitor uses very little resources, I dont see a problem with more than one running.

Let me see if I can set that setting real fast in the exe

Shane

[Shane]

Crap that was an easy change lol

Give this a try.

Replace the one you have now with this one.
Then open the mini monitor and uncheck the run at startup, this will remove the TS entry.
Then recheck it and it will make the new one.

Should be log on for any user and to allow more than one instance.

Shane

[attachments over 25 days old deleted by admin]

[Davey126]

Got part of it; settings tab is good. Two other changes:
 
 1) set account to 'Users' (a built-in group on XP/Vista/Win7) on the general tab (see snip)
 2) set trigger to 'Specific User' by default to mirror current operation of v2.0.2

Even though v2.0.2 has 'any user' for a trigger the user account specified on the general tab effectively limited it to the account that established the autostart option.

With the suggested changes only the trigger tab needs to be modified if a admin/user wants the monitor to start when any account logs on. I would hesitate making this the default without an accompanying GUI change or announcement.  Lots of people probably like the way it works now (monitor only launches on user account that set autostart option).

[attachments over 25 days old deleted by admin]

[Shane]

1) set account to 'Users' (a built-in group on XP/Vista/Win7) on the general tab (see snip)
 2) set trigger to 'Specific User' by default to mirror current operation of v2.0.2

1. The mini monitor needs admin rights, the users group would have that. So having it run as the admin who installed it would work better wouldn't it?

But of course it is set to only run when the user logs on. If I change it to run logged on or not would require the password if one is set, and thus more user interaction.

Wondering if it is worth the change and should keep it manual like you have it?
The settings flag is a good change as one less thing a user needs to change.

Otherwise I think leaving it as the admin account who made it and simply changing it to run weather logged in or not would do the trick.

I don't have multiple accounts so I will need you test

Shane

[Evan]

The mini monitor needs admin rights, the users group would have that.

No, the "Users" group is not a part of the administrators group. That's the concern I believe.

Evan

[Shane]

bah! I meant wouldn't.
What is with me and spelling lately.

Shane

[Davey126]

With 'at logon of any user' and 'run a new instance in parallel' then the account really needs to be set to 'users' or 'administrators' to avoid multiple instances of CM running in whatever user space is specified on the general tab. Administrators is probably the better choice as the task will simply be ignored by accounts with standard permissions (no prompts).

As an aside I set up most secondary users as admins with UAC enabled on Win 7. This triggers a simple yes/no prompt on certain actions that prevents most nasties from taking root (pause and think why you got that prompt). Of course the user can still screw themselves with an inappropriate response but so far that has not been a problem for my customers. Vista can be set up in a similar manner but requires a registry hack to tame UAC. That's why the 'user' group context (vs administrators) on scheduled jobs works for me. By default all administrators are members of the users group.

[Davey126]

bah! I meant wouldn't.
What is with me and spelling lately.

lol ... I actually read it that way even with the missing word! There's a workaround - see my previous post.

[Shane]

But what this comes down to is from the stand user point of view.
For an admin what you want makes sense.

But as the default for cleanmem. Is it the right way to go for everyone else?

Shane

[Shane]

Davey,

If your up to testing I almost have Drive Speedometer done

I cheated. I copied the cleanmem mini monitor code, start yanking everything I didn't need out and now I am almost done and I just start a couple of hours ago.

Saved me a TON of recoding lol

Just have to finish up some parts and it is ready to test

I also could think of anything to make a pro version as it is a pure hard drive speed monitor. So it will be totally free

Email me if you want to test it.

Shane

[Davey126]

But what this comes down to is from the stand user point of view.
For an admin what you want makes sense.

But as the default for cleanmem. Is it the right way to go for everyone else?

I am definitely with you with regard to limiting complexity and not tailoring solutions to specific needs. That said, I believe what I am proposing (could be wrong) does neither and actually simplifies the overall config from a development, admin and standard user perspective.

Let's summarize the proposed TS changes and benefits:

1) use 'administrators' (built in group on all contemporary versions of Windows) on the general tab
      benefit: task can be executed by any administrator; task will be ignored by all other/standard users (no UAC prompts)
2) change trigger to 'specific user' and default to invoker of the autostart option
      benefit: restricts autostart to current account (like today) yet makes it easy to change if desired (manually or via script)
3) allow multiple/parallel instances of job on settings tab
      benefit: permits autostart of monitor from multiple user accounts

With this setup only the trigger tab needs to be modified if an admin wants the monitor to launch on multiple accounts. A simple/obvious change that avoids messing with more obscure TS tabs/settings. It also paves the way for a simple GUI tick box that allows the user to specify whether autostart is applicable to the current user account or all accounts with admin permissions. Now that would be sweet (but not required)!