Deployment Solution

 View Only
  • 1.  Dagent loses hostname and port number

    Posted Dec 10, 2010 11:04 AM

    I finally figured out how to image a windows 7 machine with rdeploy, now I'm having another weird issue.. I have the dagent installed on the base image and it is working fine.. I sysprep the image and pull it up. I then deploy it to another machine and when it comes out of sysprep the dagent isn't on and has lost the hostname and port number, if I run the dagentconfig on the machine and type the hostname and port number in then it fine. But I've tried different machines and images all with the same result, all imaged machines lose the port number and host name for the dagent... Now something strange though, on the first unit I used to the create the image the dagent is fine when it comes out of sysprep. Only units that I push the image down to lose the hostname. Any idea?

     



  • 2.  RE: Dagent loses hostname and port number

    Posted Dec 19, 2010 09:29 AM

    Has the post configuration option been been enabled or not?

    SK.



  • 3.  RE: Dagent loses hostname and port number

    Posted Jan 21, 2011 10:14 PM

    I'm having the exact same problem. After imaging a computer the hostname is blank and port has a 0 in it.  I do a post configuration. No sure how that could affect it.



  • 4.  RE: Dagent loses hostname and port number

    Posted Feb 11, 2011 09:41 PM

    I figured out the problem. Either uncheck post configuration or at the post configuration screen fill in the server name or ip and the port. Works like a charm.



  • 5.  RE: Dagent loses hostname and port number

    Posted Feb 14, 2011 09:33 AM

    @Mr Gadget

    Thanks for posting your feedback with SK suggested solution.  Hopefully it helped KCSC Admin.



  • 6.  RE: Dagent loses hostname and port number

    Posted Feb 15, 2011 01:20 PM

    If the machine that is being targeted by the distribute disk image job is already known to the DS, the post configuration will obtain its TCPIP stack details from its database records and then apply them to the targeted machine after image deployment.

    If the machine is not known to the DS, post configuration will not find any data to apply, so the machine is left without a TCPIP stack.