[Windows Updates Legacy Report - Scope & Scheduled OR Extend the OS Patch Report]

+1 on both alternatives. 

@StevenB  I found that Pulseway have added a new place to add feature requests. When logged in to Pulseway website, go to What's new. There is a green button called "Request Feature".

I took the liberty to add this feature requst. I hope you don't mind.

https://pulseway.featureupvote.com/suggestions/134267/windows-updates-legacy-report-scope-scheduled-or-extend-the-os-patch-report

 

/Kenny

[Can not sign in to Windows Server 2016 Core]

Hi Paul,

Any update on this issue? When can we expect this to be fixed?

We have quite a few Core servers and this issue is problem for us.

[Pushing or copying applications and files to client machines]

+1

[After renaming the Org and Agent Group, new installations are not visible]

Thanks Paul,

That might be the problem. We've asked the Swedish Distributor to add our licenses, but it seems to take awhile =/.

[After renaming the Org and Agent Group, new installations are not visible]

We've used one single installation package which we've distributed via our old RMM. After the systems have been installed we've manually moved them to correct Org/Site/Agent Group.

 

However, pretty much in the midst of this installation, I renamed the Org/Site/Agent group which we used for installation which resulted in that we can see a number of systems (100+) have the Pulseway software installed, but they are not visible in Pulseway. So somehow they are connected to a specific name of Org/Site/Agent Group. 

How can we get those systems visible?

Do we need to recreate the old names of the Org/Site Agent Group? If so, the problem is that I don't have the exact names noted.
I've tried to retrieve the names via the registry, but it seems the Groupname registry entry doesn't exist anymore.

Thanks,

/Kenny