Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Absent Member.
Absent Member.
1234 views

iCM and Zenworks policies

I am so confused. We're having lots of problems with our printers
installing properly. Can someone explain the relationship of iPrint Client
Management (in iManager) and Zenworks policies? Does one override the
other? I read a previous post here, where someone said you could not apply
iCM to workstations. However, we apparently are able to apply iCM policies
to workstation groups.

My preference is to use Zenworks. But it has not been working, so we began
looking at iCM. Printers began installing when we changed the "Ignore iCM
settings on parent containers" box as well as the "Do not update
workstations" box. But it's not consistent. We install printers based on
the workstation, not the user.

We run NW 6.5 SP6, Zen 7, Windows XP. Your assistance is much appreciated.

0 Likes
4 Replies
Absent Member.
Absent Member.

ICM is purely user based. If you can configure ICM for workstation groups,
that is only due to the fact that int he NDS schema, workstation and user
groups are related. However that doesn't cause ICM to work for workstations.
If you want to do workstation based priotner installs, then ZEN is the
only option.


--
Marcel Cox (using XanaNews 1.18.1.6)
0 Likes
Absent Member.
Absent Member.

Marcel Cox wrote:
> ICM is purely user based. If you can configure ICM for workstation
> groups, that is only due to the fact that int he NDS schema, workstation
> and user groups are related. However that doesn't cause ICM to work for
> workstations.
> If you want to do workstation based priotner installs, then ZEN is the
> only option.


Hint: Make zenworks policy schedule "event: When user desktop is
active". That works. Apparently event: user login runs too early and
tries to install iPrint before spooler is ready and fails. IIRC Zenworks
documentation suggest using user login which is not the best choice.

Timo Pietilä
0 Likes
Absent Member.
Absent Member.

Why hasn't iCM been incorporated with WorkstionsGroup? It's possible to
choice WS-Group objects in iManager (Version 2.6.0(20070302_1409)), BUT
not working. After manage WS-Group object and choice printer for install
and take a look in C1 for chosen WS-group object and "Other", attributes
are the same as for User and User-Group objects.
I hope Novell iPrint-team implementing a well-functioning WS-group
assosiation, so soon is possible.
I read in iPrint forum at "ICM is purely user based". Install printer
based on User-Group-ou-o-Object? That’s not a good idea to affiliate
at UserBase level. The best choice would be WorkStation based.


0 Likes
Absent Member.
Absent Member.

If you want that functionality, I suggest you submit an enhancement
request: http://support.novell.com/enhancement
However I think that there will be close to 0 chance to have this
implemented because of the following reasons:

- workstation objects and workstation groups are a nation introduced by
ZENworks. They don't exist in "bare" OES. So if you have workstation
objects and groups, then you necessarily have ZENWorks, and in ZENworks,
you have a functionality equivalent to icm called "printer polcicies"
which can be associated with users and workstations.

- Makeking ICM workstation object or group aware will necessite some extra
development on the client side. In fact, the iPrint client will have to
interface with the ZENworks agent to get workstation object related
information, but at the same time, it should not depend on the ZENworks
agent as it is also supposed to work for people not using ZENworks.

- ZENworks 7 will be the last version to use eDirectory to store
configuraton information. The future of ZENworks will be build around
ZENworks configuration MAnagement for which there will be no more
workstation objects or workstation groups. So you are asking Novell to
make a new development to support add product which is already considered
"legacy" by now.

All in all, why aren't you simply using printer policies?

PS.
The fact that workstation groups are selectable in iManager is not made
that way on purpose, but rather it is a side affect that workstation
groups have a common object class heritage with user groups. iManager will
simply allow you to select any type of group object, whether it makes
sense or not.

--
Marcel Cox (using XanaNews 1.18.1.6)
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.