• Deployment of Agent 11

    We are in deployment phase of Zen11, especially for the deployment of the Agent to workstations (win7 x64 but no sp1). I have patched the agent with the last cumulative patch 1 that correct the random reboot bug. But I have some questions about the correct deployment method, because I have made many tests and I have encounter some issues and weird things. Here is my concerns:
    What is the difference between the 3 kind of agent, and what is the best to use: network agent, complete agent and agent without the .NET. We have Win7 x64 with no sp1.
    For Windows 7 devices, you should not have to worry about the Agent with .NET included. They should already have .NET 3.5 unless pains were taken to remove it.

    I would recommend the Full Agent w/o the .NET in your case.

    If you had XP in the mix, using the version with .NET could be useful in the event .NET 3.5 SP1 was not installed.

    If I install a EXE package of the agent to a workstation and if at this time the server from which the package was downloaded is closed or not responding, the client machine will not being registered. I've tested it and the server must be online. The FIRST INITIAL connection between the client and the zen server address showed in the Properties seems to be linked. So if the server is down or crash, my client can't register correctly, otherwise I need to manually enter an new server IP with ZAC REG .... But if my client succesfully register the first initial connection, after that the client can communicate with any other zen servers (tested and works well when some of the zen servers are not online). Is there a way to test a zenworks connection before we install a agent?
    You can use the ZCC to rebuild your deployment packages to include the Name/Address of all of your primary servers instead of just the one server that is included by default. This should resolve your issue here.

    It seems that we cannot make an image from a base machine that have already the agent, even if we uninstall it. There's still trace of the agent, and If I proceed anyway with sysprep, the cloned machines will have the same zenworks GUID after reboot..... and pointing to the same registered object. So I have found that a base machine MUST not have already the agent, this way when duplicated, no mess with duplicated objects in zen database. I know about the Agent Cleanup tool, don't know if it's safe to use on a base machine...
    Try Running "zac fsg -delete" or something like that, this should help clear out the old GUID info.

    Also in the ZCC, Check the "Configuration->Registration" tab. Make sure that "Enable Differentiation" is selected.
    You may want to make sure that both Serial Number and Mac Address is included at a minimum and perhaps machine name.

    This will help prevent the duplicates you are seeing.

    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.
    This article was originally published in forum thread: General questions about the deployment of Agent 11 started by dominicm View original post