By Tim Hall
After receiving a verification on my phone I get this nasty gram.
.Net 4.0 install was blocked because a later version was already installed. So I don't think it is a .net version issue.
Any help would be appreciated.
I blocked out the server name to keep it annonymous
I blocked out the server name to keep it anonymous. Also, please ignore the localhost:8443 page. It is irrelevant as far as I know.
By Canadian Dental Services
I recently did a clean upgrade to Windows 10 on 2 WKSTs previously running Windows 7 with Pulseway installed. I am now at a loss as to how to re-add these units to my Pulseway instance.
I see they are still showing up in the “Deployment Successful” tab under “Discovery & Deployment”.
Is there a way to re-add these units without manually installing the Pulseway app on these WKSTs?
I had installed Pulseway and then wanted to delete it but I was not able to find Pulseway in the control panel uninstall feature and so I tried manually uninstalling files but that also did not work. I tried running the .msi installer again but an error came up saying that Pulseway is already installed but it still was not showing up. Please help me with this.
After playing around in my trial account for a bit, I have a few suggestions regarding policy configuration.
Allow the creation of policies that inherit settings from other policies and track which settings were overridden. This would allow MSPs to create one or two "Global" policies (Servers/Workstations) as a base, and then create individual policies (for each client) that inherit settings from those global policies. Allow overrides to policy settings on specific systems, track which systems have policy overrides in place, and allow reverting the overrides to the policy defaults. Allow attaching scripts/tasks to policies to run during on-boarding (as in, when the Pulseway agent is initially installed). Instead of having separate Patch Management policies, group those settings with the System policies so they can be applied all at once. Alternatively, allow attaching Patch Management policies to System policies.
Would love a way to silently install and run Dell command update utility to Dell endpoints to keep drivers up to date, as Dell are frequently rolling out driver updates.
Has anyone been able to make this work for them?
I've looked into it and found some sample scripts on reddit to try and edit and test. the problem I have is getting dell command update to install first, then getting the configuration file out to the required computers that need it, then running the update silently.
If someone has managed to get this working, I would love to see how you did it, or kindly ask for some sample scripts to work with?
Any assistance would be greatly appreciated.