Desktop authority windows 7




















Archived Forums. Windows Communication Foundation, Serialization, and Networking. Sign in to vote. If Test tries to log in with this setting the error message is this: The same error is observed if you try to connect from another Windows 10 client or a Windows 7 client. Mark Wilson. Monday, January 21, PM. Feel free to let me know if the problem still exists. Best Regards Abraham. Tuesday, January 22, AM. Hi Abraham. Thank you. Look forward to your reply.

Monday, January 28, AM. I considered this a networking issue and this forum has "networking" as a part of the forum name. Monday, January 28, PM. Thanks Abraham. Now, you can lead a horse to the water, but it's up to the horse to take the drink. What forum would you suggest? Change it to Classic-local user authenticate as themselves. Tuesday, January 29, AM. It was already set to Classic. I set it to Guest and nobody could log on.

I set it back to Classic and I'm back to the original problem. View All Solutions. Mirror driver is classified as unknown on Windows 7 workstations.

Email Address. Leave a Comment. Thank you for your feedback for Topic Request. Empfohlener Inhalt. To avoid all of this and protect a Domain Controller from unwanted changes, opt to install Desktop Authority to a Member Server on the network. Feedback Nutzungsbedingungen Datenschutz. Zum Upgraden auf Internet Explorer 11 hier klicken.

Zum Upgraden auf Chrome hier klicken. Chat now with support. Chat mit Support. Live-Hilfe anfordern. Keine Ergebnisse gefunden. View All Solutions. Supported domains Microsoft Windows domain functional level Microsoft Windows R2 domain functional level Microsoft Windows domain functional level Microsoft Windows R2 domain functional level Microsoft Windows Required software applications Web console Manager The following applications are required and will be installed as part of the Desktop Authority installation.

NET Framework version 4. Client side applications Microsoft Windows Installer 3. NET 4. User Account permission requirements For use with Desktop Authority services: One admin level account is required by the Desktop Authority services. My boss wanted this installed to replace group policy, but we could never get it working right.

It requires agents at each site to do things like distribute software, but for some reason the agents would not always sync. Even DA support were left scathing their heads. It is overly complicated in that you will need extensive training to use it, nothing is obvious, and it uses a bunch of ScriptLogic jargon and menu terms that are not necessarily the IT terms people are familiar with.

Good luck getting everyone in your IT department to understand it, most likely you will need to focus on one Desktop Authority expert, and pay them to manage it. DA is like one of those giant vintage clocks the size of a building, with thousands of moving parts, levers, and switches To manage policy, it is much easier to use group policy preferences. To deploy software, I would rather use the old PSexec utility which never fails me.

Lastly, their support techs really get on my nerve. If I call them and ask a specific question, they log on, answer every other question but the one I asked, and make a million changes, then log off with the problem still there. One guy just kept saying go attend DA training classes. I should not have to fly somewhere and take a class just to deploy JAVA or run a simple policy.

I am hoping that our IT manager realizes we don't need this software. The good news is that this product is now managed by Dell, I hope this means it will evolve for the better.

It is a clunky and tedious to use web GUI.



0コメント

  • 1000 / 1000