Windows 2008 R2 proxy can't deploy to Windows 7 workstations

I'm trying to use a Windows 2008 R2 server as a proxy deployment agent. I have assigned a handful of Windows 7 workstations to the proxy to deploy agents. The workstations comply with the agent requirements, i.e. Simple file sharing turned off, Windows file
  • Additionally: I had some issues after the agent was deployed on this Windows 2008 server. The server began the shutdown process, but behaved strangely. The zenworks server (OES11 SP1/SLES 11 SP2) crashed around the time I would have expected the Windows proxy to start communicating with it to register after the first boot-up after the installation.
  • Additionally: I had some issues after the agent was deployed on this Windows 2008 server. The server began the shutdown process, but behaved strangely. The zenworks server (OES11 SP1/SLES 11 SP2) crashed around the time I would have expected the Windows proxy to start communicating with it to register after the first boot-up after the installation.
  • ZENworks 11.2.2 with December PRU installed and baselined.
  • Clearing the zmd-messages.log and restarting the task, I see an irrecoverable error in the zenuserdaemon: [DeviceGuid] [] [Irrecoverable error!!! Error in creating Device session.] There are two of these events, I'm not sure if they are related.
  • Also struggling to deploy Knowledge Base Files [3.6.A.2.16] on the same server. Not sure if this is related to the previous post.
  • For Troubleshooting, Try using "PSEXEC" to remotely start any process on
    the target box from the server using the same credentials supplied to ZCM.

    This uses the same underlying technology.
    Until that works, something is amiss in the setup.

    Of course, Deployment Tasks to deploy the agent is something I always
    consider a means of last resort when all other options are not available
    due to the large number of configuration changes required to even allow
    the feature to work.

    Novell or MS Login Scripts.
    ZDM7 or AG GPOs etc...
    are all simpler.

    At least in my mind, the ZCC tool is better at finding straggling
    devices that trying do mass deployments.

    On 12/26/2012 7:46 PM, ElliottRScott wrote:
    >
    > Also struggling to deploy Knowledge Base Files [3.6.A.2.16] on the same
    > server. Not sure if this is related to the previous post.
    >
    >



    --
    Craig Wilson - MCNE, MCSE, CCNA
    Novell Knowledge Partner

    Novell does not officially monitor these forums.

    Suggestions/Opinions/Statements made by me are solely my own.
    These thoughts may not be shared by either Novell or any rational human.
  • Funny, I've had success with this during my initial testing. I deployed to a WinXP box and a Win 7 box w/out problems.

    The psexec worked with the credentials I'm using for zen... It would help if I could better understand what the error, "Can't contact target", meant. This has to be feedback from some instruction being executed. Any insight?
  • I think it means just what it says.
    Perhaps the Device's IP changed between scan and deployment.
    Perhaps the Device was off or even too asleep to accept the remote
    install task.



    On 12/27/2012 11:26 AM, ElliottRScott wrote:
    >
    > Funny, I've had success with this during my initial testing. I deployed
    > to a WinXP box and a Win 7 box w/out problems.
    >
    > The psexec worked with the credentials I'm using for zen... It would
    > help if I could better understand what the error, "Can't contact
    > target", meant. This has to be feedback from some instruction being
    > executed. Any insight?
    >
    >



    --
    Craig Wilson - MCNE, MCSE, CCNA
    Novell Knowledge Partner

    Novell does not officially monitor these forums.

    Suggestions/Opinions/Statements made by me are solely my own.
    These thoughts may not be shared by either Novell or any rational human.
  • I think it means just what it says.
    Perhaps the Device's IP changed between scan and deployment.
    Perhaps the Device was off or even too asleep to accept the remote
    install task.



    On 12/27/2012 11:26 AM, ElliottRScott wrote:
    >
    > Funny, I've had success with this during my initial testing. I deployed
    > to a WinXP box and a Win 7 box w/out problems.
    >
    > The psexec worked with the credentials I'm using for zen... It would
    > help if I could better understand what the error, "Can't contact
    > target", meant. This has to be feedback from some instruction being
    > executed. Any insight?
    >
    >



    --
    Craig Wilson - MCNE, MCSE, CCNA
    Novell Knowledge Partner

    Novell does not officially monitor these forums.

    Suggestions/Opinions/Statements made by me are solely my own.
    These thoughts may not be shared by either Novell or any rational human.