UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21. Read more.
UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21.Read more.
Absent Member.
Absent Member.
1837 views

Agent Deployment Package Confg - Multiple Primary Servers

I have a few questions about ZENworks 11 agent deployment/configurations.

1. Is there a best practices for agent deployment in environments where there are two or more primary servers?

2. What is the proper agent deployment pkg config for a environment where there are two or more primary servers?

3. Should the agent packages have all the primary servers added in the deployment package?

4. Is there a consequence of if all of the primary servers are not in the package?

5. Is there a way to configure the default agents to have all of the DNS/IP configs for each primary server without doing it manually? Each time you rebuild the packages with the command line strings novell-zenworks-configure -c CreateExtractorPacks -Z and novell-zenworks-configure -c RebuildCustomPacks -Z overwrite these config changes when run.
Labels (2)
0 Likes
4 Replies
Absent Member.
Absent Member.

Hi

Actually a good question. If any out there thinks or know that they have the ultimate way to do this, I would also like to know it 😉

To answer your questions, I can tell you what i've done (we have 4 pri's)

I've only selected one primary server in the deployment pkg. (one deployment pkg for the internal net and one for the external)
Then when the clients finished installing they should get the correct server informations from the network environment/locations.

I have not noticed any problems with only one of our primary servers configured in the pkg.

Don't know about the command line string, I make the pkg in ZCC 😉

-- Niels I have always liked... Cowabunga! If you find this post helpful, please show your appreciation by clicking on the star below. A member must be logged in before s/he can assign reputation points.
0 Likes
Micro Focus Expert
Micro Focus Expert

None of that is necessary.

This info is simply to allow for the Agent to connect to the Zone on
Install.

Once it contacts the Zone on Install, it will use the Location Rules
defined in the Zone and get a list of all valid servers based on the
rules defined in the zone.


On 4/25/2011 5:36 PM, psloat wrote:
>
> I have a few questions about ZENworks 11 agent
> deployment/configurations.
>
> 1. Is there a best practices for agent deployment in environments where
> there are two or more primary servers?
>
> 2. What is the proper agent deployment pkg config for a environment
> where there are two or more primary servers?
>
> 3. Should the agent packages have all the primary servers added in the
> deployment package?
>
> 4. Is there a consequence of if all of the primary servers are not in
> the package?
>
> 5. Is there a way to configure the default agents to have all of the
> DNS/IP configs for each primary server without doing it manually? Each
> time you rebuild the packages with the command line strings
> -novell-zenworks-configure -c CreateExtractorPacks -Z- and
> -novell-zenworks-configure -c RebuildCustomPacks -Z- overwrite these
> config changes when run.
>
>



--
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.
--
Please give a hearty thumbs up to any post you find helpful!
To find articles by Craig Wilson simply follow the link: Craig Wilson's Tips!
0 Likes
Absent Member.
Absent Member.

Yep, simple then 😉

-- Niels I have always liked... Cowabunga! If you find this post helpful, please show your appreciation by clicking on the star below. A member must be logged in before s/he can assign reputation points.
0 Likes
Absent Member.
Absent Member.

psloat,

>3. Should the agent packages have all the primary servers added in the
>deployment package?


Another option would be to use an L4 configuration. Then if one of the
primary's is down or something like that the Agent install will not fail.

--
Jared Jennings
Senior Systems Engineer, Computer Integrated Services (CIS)
http://www.ciscony.com

My Blog and Wiki with Tips, Tricks, and Tutorials
http://jaredjennings.org
Twitter@ jaredljennings
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.