Deployment Solution

 View Only
  • 1.  RDEPLOY: The Operation was cancelled

    Posted Jan 05, 2009 11:56 PM
    hi,

    I am trying to deploy an image to a laptop but it does not deploy, i receive the following message in the DS console 'RDEPLOY: The Operation was cancelled'

    I have tried 2 laptops of different models with different images but i cant get past this stage.

    The deployment is at a remote site and i have setup local PXE boots. I don't seem to have this problem at a different remote site.

    Can any please help?


  • 2.  RE: RDEPLOY: The Operation was cancelled

    Posted Jan 06, 2009 01:43 AM
    Are you actually pushing an image across the WAN? Your networking team must really love you! What happens if you do the image locally, do you still get the same problem? It's possible your networking team has a bandwidth limit or someone could be canceling it on the other side as well.


  • 3.  RE: RDEPLOY: The Operation was cancelled

    Posted Jan 06, 2009 04:25 AM
    Hi,

    I am not going over the WAN - i have PXE redirects setup for each location. Each location has an 'Images' folder share.

    Everything works fine where the DS server is located and one remote site works ok too.


  • 4.  RE: RDEPLOY: The Operation was cancelled

    Posted Jan 07, 2009 11:01 AM
    i have this same issue intermittently


  • 5.  RE: RDEPLOY: The Operation was cancelled

    Posted Jan 07, 2009 11:36 PM
    I am still investigating my issue because it is on a remote site.

    But try the following : -

    Check the RD*.log. The RD.log can be found in the RDEPLOY folder on your server.

    Format the harddisk to NTFS then try to redeploy

    One of my RD*logs reported problems with the gigbit card on the remote server where the images are stored. I am going to try an alternative but this i have yet to test when i go to the remote site.

    If any of the above helps or you find you own solution please let us know.

    Kind Regards


  • 6.  RE: RDEPLOY: The Operation was cancelled

    Posted Jul 13, 2009 04:33 PM
    Take a look at this kb.altiris.com/article.asp
    I was having that same error poppingup today and this KB was the solution. The mapping was wrong in my boot disk, not sure who messed with it yet, and that was causing the error.