colesy

Comments

  • Well sure.. we could have done it that way too... In all seriousness, I had no idea we could do that... The only things we found on this topic basically said there was nothing you could do. The SQL command was easy enough, but thanks for sharing this.
    in WHD clients marked as inactive after manual AD sync Comment by colesy February 2017
  • I didn't have to use the IP. Did you try with the fully qualified name, and not just the server name? My suspicions with those that had to use the IP are running a version of web help desk that isn't a domain memeber. For example, we are running the vmware appliance, and as long as we used the FQDN for server name it…
    in Discovery Connections: SCCM Comment by colesy January 2017
  • I'm not sure what the constraints are. If user is in sync and currently inactive reactivate. We ran into an issue where all 15,000+ users were marked inactive. We thought we were going to have to manually activate them all 100 at a time. It turns out you can just ran a simple SQL command on the WHD clients table that…
    in WHD clients marked as inactive after manual AD sync Comment by colesy February 2017
  • Found this link which did it for me. I needed to add the connect SQL under securables for the account we created. http://itproguru.com/expert/2014/09/how-to-fix-login-failed-for-user-microsoft-sql-server-error-18456-step-by-step-add-sql-administrator-to-sql-management-studio/
    in Discovery Connections: SCCM Comment by colesy January 2017
Avatar