Jump to content

Comissha

Members
  • Posts

    12
  • Joined

  • Last visited

Posts posted by Comissha

  1. Our technical support AD credentials have changed passwords and now we are getting hundreds of machines trying to login with the configured AD account PowerShell User Impersonation credentials…locking the technician accounts. These machines are spread out at 19 separate locations and over 600 miles, at remote locations. How do we remotely modify the Runtime PowerShell user credentials on those machines?

    I have tried uninstalling and then  reinstalling, but it absorbs the previous configuration…including the former PowerShell User credentials….I also tried calling tech support but was sent to voicemail. Help!

    Local Setings where credentials were entered:

    301648439_localsettings.JPG.a801b99d0a9e8e68fb415f07d7504366.JPG

    Remote Settings, no ability to enter or modify PowerShell User:

    318821179_remotesettings.JPG.15ac90ec4ef545cc819080f726f4a997.JPG

  2. Having a way to search computers by users would be an amazing feature add. This way, when larger clients call into helpdesk, we could search by that caller and expedite the process. Add to that, the ability to search for all computers that a specific user is logged into.

  3. Maybe someone can shed some light on this.

    Using the PSA system, I have gone several times now into the Service Desk module, selected hardware assets and assigned them to their respective clients. Every 24 hours or so, as I am entering in tickets and trying to assign a hardware asset to those tickets, I am finding that a bulk of the hardware assets are reverting back to my company as the client asignee. I have have to repeatedly go back and re-assign those hardware assets back to the clients. Besides the colosal waste of time, it makes me wonder if any other information is not being retained in the databse.

    Any clue?

    Shawn

×
×
  • Create New...