locked
Cannot uninstall agent in DPM Administrator console RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    In trying to set up a client agent, I have run into a scenario where I cannot uninstall the agent from within the DPM admin console.

    Setting up the DPM 2010 server went without problems.  However, when I attempted to install the agent on the workstation it failed every time.  I was able to install the agent by doing a manual install on the workstation and then attaching from the DPM admin console.  I then set up a protection group and started to do backups.  However, this then set up a situation where there were two agents connected to the DPM server.  One (untrusted) was connected to the prtection group and seemed to be working OK.  The other, in the same domain as the DPM server was unprotected.

    The workstation is a domain member, but I normally run on a local account (left over from when I set the machine up for NT).  I RDPed over to the DPM Server machine to try the install.  The install from the server failed, but a local agent install and attach from the server worked.  I was this scenario where I got the (unstrusted) agent working.

    However, now that I'm trying to clean things up to do a "correct" install, I cannot uninstall the protected agent; even after stopping the protection group.  I was able to uninstall the agent associated with the  (domain) workstation agent.  Even after uninstalling the DPM agent software from the workstation, I still cannot uninstal the agent in the DPM admin console.

    At this point, I don't see much I can do except uninstall the DPM server software and install it all over; and hope everything gets cleaned up properly by the server uninstall.

    Tuesday, April 19, 2011 12:27 AM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi Alex.

    > you can't uninstall an agent from the console when it is protected.

    At the time I wanted to do the uninstall, there was no protection group associated with the client/agent.

    I suspect the real problem was I did a manual install of the agent on a domain workstation, while logged into a local account.  This seems to have resulted in the DPM admin console believing there were two "agents" on the workstation.  One being reported a part of the domain and the other also being reported but "untrusted".  Note these two did not initially appear, it seems only after a sync was attempted that the two appeared.  (I can't say for certain, as it occurred overnight, and I was not monitoring the systems.)

    I was not able to try thr PS script as I uninstalled/installed the DPM server software to clear it out.  I've been trying to get DPM deployed now for about a week, and after having only marginal success I've taken to using a bigger hammer than might be necessary to get the task (at hand) accomplished.

    I have spent a lot of time reading various DPM pages, TechNet and otherwise, but there hasn't been a lot of helpful information.  I guess the scenario I'm trying to cover wasn't envisioned by the developers :-)

    - Mark

    Tuesday, April 19, 2011 2:00 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Mark,

     

    when you uninstall the agent did you leave the "uninstall agents" screen open? it should present with a popup asking you if you want to remove the record from the DPM db.

    you can also use the follwoing powershel script: remove-productionserver.ps1 this is located in C:\Program Files\Microsoft DPM\DPM\bin

     

    kind regards,

    Alex Smits


    • Edited by Alex_Smits Tuesday, April 19, 2011 1:47 PM
    • Proposed as answer by Troy Werelius Tuesday, August 9, 2011 4:53 PM
    Tuesday, April 19, 2011 12:42 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    >  it should present with a poopup asking you if you want to remove the record from the DPM db.

    The uninstall never got this far for the protected client; the "Uninstall" menu item was disabled.  It did, however, appear for the unprotected client.

    The basic problem was the uninstall menu option for the protected client was disabled (greyed out).  Previously, I did manage to (once) get the unstall option to be enabled by recreating a protection group for the client, doing a client refresh, and then stopping (deleting) the protection group.  Going back, the uninstall menu item had then been enabled.  However, this latest time, this scenario did not work even after attempting seveal times.

    Tuesday, April 19, 2011 1:33 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Mark,

    that makes sense, you can't uninstall an agent from the console when it is protected.

    did you try the ps1 script?

    kind regards,

    Alex Smits

    Tuesday, April 19, 2011 1:49 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi Alex.

    > you can't uninstall an agent from the console when it is protected.

    At the time I wanted to do the uninstall, there was no protection group associated with the client/agent.

    I suspect the real problem was I did a manual install of the agent on a domain workstation, while logged into a local account.  This seems to have resulted in the DPM admin console believing there were two "agents" on the workstation.  One being reported a part of the domain and the other also being reported but "untrusted".  Note these two did not initially appear, it seems only after a sync was attempted that the two appeared.  (I can't say for certain, as it occurred overnight, and I was not monitoring the systems.)

    I was not able to try thr PS script as I uninstalled/installed the DPM server software to clear it out.  I've been trying to get DPM deployed now for about a week, and after having only marginal success I've taken to using a bigger hammer than might be necessary to get the task (at hand) accomplished.

    I have spent a lot of time reading various DPM pages, TechNet and otherwise, but there hasn't been a lot of helpful information.  I guess the scenario I'm trying to cover wasn't envisioned by the developers :-)

    - Mark

    Tuesday, April 19, 2011 2:00 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Pardon my input but the problem seems to be with the "untrusted/workgoup" area of adding servers. DPM seems to think everything on the uninstall/removal side is Active Directory only.

    I have a simular issue with a workgroup server that was manually added to DPM2010. The server no longer exists but the console shows is as unavailable.  It was installed with the local account settings created when adding a server in a workgroup.

    I have run the script Remove-ProductionServer.ps1 to remove it but that fails saying it cannot find the server in AD. Where is the script to remove a workgroup server from the SQL database because the script Remove-ProductionServer.ps1 is for an Active Directory computer and not one that was added from a workgroup. 

    The uninstall option is not available.  I have reinstalled the agent and added it back to the console, still no uninstall.  I have created a protection group for the server and that works fine but it still won't let me remove (uninstall) the server from the console even after I remove all protection groups that the workgroup server is protected by. It seems to be a major bug if you can add one but then not be able to remove it because it is not in Active Directory, this clutters up the console.

    Friday, July 15, 2011 5:11 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

     

    same problem here. Has somebody an answer to this issue? Its not possible to delete the Agent (non Domain Server) from the DPM2010 Mangement Console.

    Tuesday, January 10, 2012 11:38 AM
  • Question
    Sign in to vote
    2
    Sign in to vote
    When running the remove-productionserver.ps1 script you have to add the FQDN of the server agent you want to remove.  Worked fine for me.
    Tuesday, July 3, 2012 11:55 AM