Support Forum

Thanks,

Whatever you changed solved the problem.

Hello,

This is happening to us too.

Thanks for explaining that. Now that I understand what the "Current" check indicates it makes perfect sense. I'm not sure if there is anything that would make that immediately obvious beyond a tooltip stating something to the effect of "check for updates has run recently" Regardi...

I'm having some issues setting up the new application manager. It works perfectly for sites where every machine at a site are in defined locations, but I have a ton of sites where many of the agents are in home offices and have no way to resolve access to shared files in a central location. I notice...

Scratch that,

It seems to be working suddenly on my system, I'm not sure what changed or why.

After looking at these queries, Both return the data they are supposed to,

However, there is still no attempt to actually run the scripts at the scheduled times.
The AttemptDate and AttemptLog entries on these agents remains null

The scheduler does not seem to be running

It's the scheduling that is failing.

I can see no evidence of the Habitat OS Upgrade script in the agent logs.

The Habitat App Manage Maintenance scripts for the 3rd party updates are being scheduled properly, however. I'm not sure if that uses different scheduler code than the OS upgrade module.

Is it possible to setup permissions so that only certain people have access to tools?

I would like to grant service desk the ability to access some of these tools (namely the Windows 10 Upgrade assistant) without granting them access to SQL (yikes)

I just setup some policies to do windows upgrade and I am also having this same issue.

Upgrade now seems to work without issue.
Scheduling upgrades does not

I am running build 1.0.0.54 of Habitat.

I don't see anything related to Habitat in the LTcErrors.txt