Deploy novell client

For a customer i've set up ZLM, OES and SLED.
- what is the easiest way to distribute the novell client?
currently i have created a rpm bundle, containing all rpm's on the novell client cd.

lowalcohol,
... but to be honest... I do not want the client, I want to use centrally managed login scripts, to map samba/ncp shares...
that is one of the things the Novell client allows you to do. You define the login scripts once in edirectory and the Novell clients, independent where they are, use them when they login. Okay it depends if you have logical structures in edirectory and different sites, then you might need them twice or more times, but it is a perfect solution you can manage from a central point.
So to your question ...
When I check as a sample the SLED 11 Novell client, I see that the installation media is already usable as a installation source.
So one option might be to use a remote execute policy to add it as a zypp source temporarily via "rug sa -t zypp <network path to the client> NWCL" on each client and trigger the installation. The problem is that it is not only a instalaltion of rpm packages, there is a yast module that does all the configuration for the novell client afterwards. I don't know if there is a console command that does all the same. In other cases the configu files must be collected that are touched by yast and then the remote execute policy should do the same.
A second option would be to put all rpms into a bundle and then use the post installation script to make all the additional system configurations that were done via yast.
So far this seem to be the two options you can choose from ...
What do you think ?
Rainer

Similar Messages

Trying to Deploy Novel Client 2 ADM

I am trying to use the Novell Client 2 ADM to limit what my users can do via the Novell Client (we are a public school district.) Specifically, I am trying to disable the Novell Utilities, the Browse To, and the Properties dialogs. When I used the ADM in my Group Policy, and applied it to my users, nothing changed. I then tried to create a bundle to push out the registry edits that would make the changes, I was able to see that the changes took effect, but they took effect on all users who logged in to the computer instead of just to the specific users I wanted.
I know that this is probably an easy fix, but I have been struggling over this for 2 weeks now, and I am no closer to a solution than I was before.
Thank you for any assistance you can provide me.

Billupp,
> I was able to see
> that the changes took effect, but they took effect on all users who
> logged in to the computer instead of just to the specific users I
> wanted.
They are global yes, so you must run the edit for every user that logs
in, always.
Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)
Have an idea for a product enhancement? Please visit:
http://www.novell.com/rms

Windows 7 with MDT - Novell Client / Zen Agent?

Been creating my Windows 7 reference image using Microsoft Deployment Toolkit (MDT - pretty cool). I'm wondering if any of you do the same, and if you do, do you include the Novell Client in the image? what about the zenworks agent? If so, what techniques are you using to install.. etc.
Thanks!

Originally Posted by joebrug
Been creating my Windows 7 reference image using Microsoft Deployment Toolkit (MDT - pretty cool). I'm wondering if any of you do the same, and if you do, do you include the Novell Client in the image? what about the zenworks agent? If so, what techniques are you using to install.. etc.
Thanks!
You can use this during your sysprep process that way it does not matter if it is installed or not.
zac fsg -d
:: THIS WILL ALLOW A NEW GUID TO BE CREATED IN ZEN AFTER REIMAGING
del "C:\Program Files (x86)\Novell\ZENworks\conf\deviceguid"
del "C:\Program Files (x86)\Novell\ZENworks\conf\devicedata"
del "C:\Program Files (x86)\Novell\ZENworks\conf\*.sav"
del "C:\Program Files (x86)\Novell\ZENworks\conf\Guid.txt"

Installing Novell Client fails due to 'untrusted signer'

I am trying to update Novell Client on our Windows 7 workstations, using a Zenworks bundle. This method has worked in the past: copy the installation files to c:\temp\zeninstall\clnt2sp3ir5 (including appropriately modified NovellClientProperties.txt and install.ini) and then just launch "setup.exe /ncpf" as secure system user.
This time I noticed that the new client was only partially installed. When viewing Novell Client properties it shows the new version, however, some files are definitely from the previous client version (for example C:\Windows\System32\lgnwnt32.dll).
I dug up c:\windows\inf\setupapi.dev.log and it seems that installation was aborted due to "unsigned driver package":
Code:
sto: Validating driver package files against catalog 'netnvcli.cat'.
!!! sto: Driver package signer is unknown. Assuming untrusted signer. Error = 0x800F0242
!!! ndv: Driver package failed signature validation. Error = 0xE0000242
sto: {DRIVERSTORE_IMPORT_NOTIFY_VALIDATE exit(0xe0000242)} 12:37:47.960
!!! sto: Driver package failed signature verification. Error = 0xE0000242
!!! sto: Failed to import driver package into Driver Store. Error = 0xE0000242
sto: {Stage Driver Package: exit(0xe0000242)} 12:37:48.225
!!! sto: Failed to stage driver package to Driver Store. Error = 0xE0000242, Time = 6521 ms
sto: {Import Driver Package: exit(0xe0000242)} 12:37:49.973
inf: Opened INF: 'c:\temp\zeninstall\novell_client\c2sp3ir5\netnvcli.inf' ([strings])
! inf: Add to Driver Store unsuccessful
! inf: Error 0xe0000242: The publisher of an Authenticode(tm) signed catalog has not yet been established as trusted.
!!! inf: returning failure to SetupCopyOEMInf
<<< Section end 2014/02/11 12:37:51.439
<<< [Exit status: FAILURE(0xe0000242)]
If I run the installation manually, I am prompted at one point about unsigned driver and whether I want to install it. If I answer "yes", the installation is successful.
Looking at Windows' certificate store on our computers, I see under "Trusted Publishers" a certificate issued to Novell, Inc by "Verisign Class 3 Code Signing 2009-2 CA", but that certificate expired on 27.04.2013.
How can I obtain and deploy the certificate that would allow the silent installation of Novell Client 2 SP3 IR5 to proceed? Or am I going about this in an entirely wrong way?

Originally Posted by vatson
I am trying to update Novell Client on our Windows 7 workstations, using a Zenworks bundle. This method has worked in the past: copy the installation files to c:\temp\zeninstall\clnt2sp3ir5 (including appropriately modified NovellClientProperties.txt and install.ini) and then just launch "setup.exe /ncpf" as secure system user.
This time I noticed that the new client was only partially installed. When viewing Novell Client properties it shows the new version, however, some files are definitely from the previous client version (for example C:\Windows\System32\lgnwnt32.dll).
I dug up c:\windows\inf\setupapi.dev.log and it seems that installation was aborted due to "unsigned driver package":
Code:
sto: Validating driver package files against catalog 'netnvcli.cat'.
!!! sto: Driver package signer is unknown. Assuming untrusted signer. Error = 0x800F0242
!!! ndv: Driver package failed signature validation. Error = 0xE0000242
sto: {DRIVERSTORE_IMPORT_NOTIFY_VALIDATE exit(0xe0000242)} 12:37:47.960
!!! sto: Driver package failed signature verification. Error = 0xE0000242
!!! sto: Failed to import driver package into Driver Store. Error = 0xE0000242
sto: {Stage Driver Package: exit(0xe0000242)} 12:37:48.225
!!! sto: Failed to stage driver package to Driver Store. Error = 0xE0000242, Time = 6521 ms
sto: {Import Driver Package: exit(0xe0000242)} 12:37:49.973
inf: Opened INF: 'c:\temp\zeninstall\novell_client\c2sp3ir5\netnvcli.inf' ([strings])
! inf: Add to Driver Store unsuccessful
! inf: Error 0xe0000242: The publisher of an Authenticode(tm) signed catalog has not yet been established as trusted.
!!! inf: returning failure to SetupCopyOEMInf
<<< Section end 2014/02/11 12:37:51.439
<<< [Exit status: FAILURE(0xe0000242)]
If I run the installation manually, I am prompted at one point about unsigned driver and whether I want to install it. If I answer "yes", the installation is successful.
Looking at Windows' certificate store on our computers, I see under "Trusted Publishers" a certificate issued to Novell, Inc by "Verisign Class 3 Code Signing 2009-2 CA", but that certificate expired on 27.04.2013.
How can I obtain and deploy the certificate that would allow the silent installation of Novell Client 2 SP3 IR5 to proceed? Or am I going about this in an entirely wrong way?
You need to install the newest client (that have a never certificate) on a device and then export it from that machine, after that you import it on the devices you want to install the client before running setup.exe.
Thomas

Firewall rule for Novell Client

My company recently purchased McAfee Desktop Firewall and I'm trying to
configure the rules prior to deployment but I'm having trouble getting
the Novell Client to cooperate. I've tried having the firewall "learn"
the client, addresses, ports, protocols, etc. but have had no luck.
My company is running a mix of Win2k/XP computers as well as Win95/98
computers so any assistance in creating a firewall rule to allow the
clients to log in is greatly apprecaited.
Thanks!
Ash

Excellent, thanks!!
> For NetWare connectivity over IP, you need ports TCP,UDP 524 and 427
> which are NCP over IP and SLP.
>
>
> --
> Edison Ortiz
> Novell Product Support Forum SysOp
> (No Email Support, Thanks !)

Novell Client 2 after sysprep

During my image process I have sysprep run a batch file which installs several programs. Included are the Novell Client 2 (2nd to last install) and the ZAA (last install). Everything seems to deploy correctly and the system reboots. What I have noticed is that the Novell client doesn't not default as the primary login shown. The system seems to want to boot into windows automatically and throws up a ZAA login dialog.
Did I miss a registry setting that would cause this? The client should autosetup the tree/context/server but even that seems to be missing.
Thanks
Rich

Originally Posted by rhuhman
During my image process I have sysprep run a batch file which installs several programs. Included are the Novell Client 2 (2nd to last install) and the ZAA (last install). Everything seems to deploy correctly and the system reboots. What I have noticed is that the Novell client doesn't not default as the primary login shown. The system seems to want to boot into windows automatically and throws up a ZAA login dialog.
Did I miss a registry setting that would cause this? The client should autosetup the tree/context/server but even that seems to be missing.
Thanks
Rich
why not just have the client on the image itself? we originally had it as a layer, but then added it to image with zen agent to speed things up a bit.

About novell client install

Hi All
my customer have some branch office in Eu & US, there are some OES File Server, he want to perform data migration to windows server (OES and Windows File Server on the same branch office), but Default NSM Engine Server on Aisa. I want to ask if I install Novell client on windows File Server...the migration-Data traffic only keep on branch office local LAN or still return to Engine Server through WAN(VPN) ?
thanks!!
wyld

On 12/4/2013 2:16 AM, wyldkao wrote:
>
> HI
> I re-read admin guide...the novell client indeed install on Engine
> Server, but I find it said
> ==>"If Agents are deployed as a part of a Novell Storage Manager
> installation, these agents are individually used for migration if the
> Novell Client is installed on them. In order for an agent to participate
> in a migration, the server that has the agent installed must also have
> the Novell Client installed."
>
> If my Engine / Agnet locate in different location (leased line), I
> should install Novell client on Windows File Server let it receive
> command from Engine and direct copy data from OES Server , right ?
>
> wyld
>
>
Yes, it would be best to install the Novell Client and an Agent on that
server.
-- NFMS Support Team

Zenworks patch deployment without Client

OK, so I want to use Zenworks to deploy Windows patches to networked
scanners
with PC's attached to them. These PC's are not equipped with the company
standard images, therefore do not have Novell Client. I'd like to deploy
patches to these PC's without having to install Novell Client, due to a
management decided security issue. I am stuck as to where to begin. I was
told
to research the possibility of using an FTP connection in place of Novell
Client and Application Launcher. Preferably I'd like to still use Zen4
Applications to push out patches like I do for the user's workstations,
but
any and all suggestions are welcome.
Thanks!

jma,
> Applications to push out patches like I do for the user's workstations,
> but
Just to add to what Timothy said.
You could push the Novell client via a AD login script or batch file. You
can distribute the ZFD Agent this way also.
You do not need the Novell client to use Desktop management to deploy
software and such. This is were the middle tier server will come into
play. With just the zfdagent and the MiddleTier server, you can manage a
pure MS environment easily.
You will probably want to look at patch management to really manage
patches in a proper way. This again does not require the Novell client,
but simply a patch agent.
Jared Jennings
Data Technique, Inc.
Novell Support Forums Sysop
Check out Novell WIKI
http://wiki.novell.com/index.php/IManager

I have installed the agent 10 or 15 times and one installation hasfailed, no error appeared during the installation but I am havinginconsistent issues with my ethernet card not working here and there. Werebooted and can log into Novell client but th

I have installed the agent 10 or 15 times and one installation has failed, no error appeared during the installation but I am having inconsistent issues with my ethernet card not working here and there. We rebooted and can log into Novell client but the login prompt did not appear for ESM client or the icon was not in the systray. Everything seems to work, besides at times (a couple times today) it terminates his ethernet card/connection. I would re-image his computer but he has several applications and it would take several hours, so I am hoping someone has an idea to fix this issue. So I was trying to figure out why he did not get the prompt to login and why it's not in the systray and it appears to not have completed the install? I checked the add/remove programs, its not listed within their, I also checked the registry and found nothing for endpoint within their, but the files are within c:\program files\novell\zenworks endpoint security.
I have also tried uninstalling it but that fails due to it "not being installed", and it will not reinstall over itself either.
I did notice that stuninstdrv.exe is running in task manager. Any help would be great...
Windows xp sp3
ESM 3.5.154
Thanks,
Andy

If you are searching the registry, check for the "Senforce" string. It should be at HKLM\Software\Senforce
Try running the install program for the ZSC with the following command line:
setup.exe /V"STUNINSTALL=1"
If you've specified an uninstall password, try this one instead:
setup.exe /V"STUNINSTALL=1 STUIP=password"" (please note the double quote at the end)
Let me know if that helped you.
Daniel
>>>
From: Andy_DeWees<[email protected] du>
To:novell.support.zenworks.endpoint-security-management
Date: 2/5/2009 12:52 PM
Subject: I have installed the agent 10 or 15 times and one installation hasfailed, no error appeared during the installation but I am havinginconsistent issues with my ethernet card not working here and there. Werebooted and can log into Novell client but the login prompt did not appearfor ESM client or the icon was not in the systray. Everything seems towork, besides at times (a couple times today) it terminates his ethernetcard/connection. I would re-image his computer but he has severalapplications and
I have installed the agent 10 or 15 times and one installation has failed, no error appeared during the installation but I am having inconsistent issues with my ethernet card not working here and there. We rebooted and can log into Novell client but the login prompt did not appear for ESM client or the icon was not in the systray. Everything seems to work, besides at times (a couple times today) it terminates his ethernet card/connection. I would re-image his computer but he has several applications and it would take several hours, so I am hoping someone has an idea to fix this issue. So I was trying to figure out why he did not get the prompt to login and why it's not in the systray and it appears to not have completed the install? I checked the add/remove programs, its not listed within their, I also checked the registry and found nothing for endpoint within their, but the files are within c:\program files\novell\zenworks endpoint security.
I have also tried uninstalling it but that fails due to it "not being installed", and it will not reinstall over itself either.
I did notice that stuninstdrv.exe is running in task manager. Any help would be great...
Windows xp sp3
ESM 3.5.154
Thanks,
Andy

CSA & Novell Client

We run a Novell network and our primary authentication client is the Novell client. I've setup CSAMC v6 and have been tuning for the past couple of days.
I seem to have a problem with the Novell client login script. Whenever I login, the search drives don't map. I get:
FS-TBRHSC-ZEN
LOGIN-LGNWNT32.DLL-890: The specified server is unknown.
LOGIN-LGNWNT32.DLL-430: The following drive mapping operation could not be completed.
[ROOT S16:=Z:=FS-TBRHSC-ZEN\SYS:PUBLIC]
The error code was 8884.
I've opened up TCP/524 and TCP/427 to all of our Novell servers with no results. I thought it might be ephemeral ports to I opened them up as well.
This is really frustrating the heck out of me. Does anyone have a solution?
Ryan

I have tuned Novell in CSA 4.0, and upgarded the rules to 6.0 and they seem stable. Please e-mail me at dhudson at hanover dot com, and I will send you na export of my Novell tuning...

Novell Client for Linux 2 beta & VMWare - bridged only?

OpenSUSE 11.1 with Novell Client for Linux 2.0 SP2 beta.
OpenSUSE is installed as a VMWare Workstation guest using NAT. When attempting to use contextless login, the Novell Client hangs. If you disable contextless login and then browse to the right context, you can login OK.
If you change the virtual NIC from NAT to Bridged, contextless login works fine. If at all possible, we need to use Bridged instead of NAT (long story).
Any idea what could be the problem? From what I can tell, SLP, DA, etc are set correctly, but I could be wrong.
Thanks.

Originally Posted by Thorsten Kampe
* mlazovjp (Mon, 14 Dec 2009 18:56:02 GMT)
> OpenSUSE 11.1 with Novell Client for Linux 2.0 SP2 beta.
>
> OpenSUSE is installed as a VMWare Workstation guest using NAT. When
> attempting to use contextless login, the Novell Client hangs. If you
> disable contextless login and then browse to the right context, you can
> login OK.
>
> If you change the virtual NIC from NAT to Bridged, contextless login
> works fine. If at all possible, we need to use Bridged instead of NAT
> (long story).
>
> Any idea what could be the problem? From what I can tell, SLP, DA, etc
> are set correctly, but I could be wrong.
Use NAT only if you need NAT - otherwise use bridged.
Thorsten
I was afraid that someone was goign to say something like that :)
We use port security hardware on our network, which will disable a port on the switch if it detects multiple MAC addresses on the same port. A virtual machine's bridged networking sets port security off and disables the port, so we have had to resort to NAT for all virtual machines. We can ask for exceptions to be made for a subset of our lab computers, but that is not an ideal solution.
Not only is that extra overhead for us to manage these exceptions, but we will not be able to realize our long-term goal of providing the virtual machine to our students to use on their personal notebooks since we cannot provide them port security exceptions.
I am still having problems grasping the reason that a contextless lookup (via LDAP, I assume) would misbehave while coming from a NATted connection but a bridged connection works fine on the exact same virtual machine. Shouldn't the communication between the VM and the LDAP server work properly either way??

Novell Client 2.0 SP1(IR6) - TID 7008266 - Service/eDir Auth

Shaun et. al.,
I like what I'm seeing in the Novell Client 2.0 SP1 (IR6) release notes.
Tree or Server Not Found on login immediately after powerup is supposedly fixed with this release (a big problem with us).
Can you confirm that TID 7008266 is part of Novell's solution to the issues posed by installing as a Dynamic Administrator / System Account?
(mapping drives, etc).
pitcherj

Well, I think the efforts are completely disconnected.
The Client2 Efforts are nothing to do with ZCM.
I'm aware of the Interactive Services Detection defect and this would
not relate to that in any way. Nor would the Dynamic Administrator
inherit any rights defined by the Client2 Feature.
In regards to the SYSTEM process, it may but I have not tested nor do I
believe anyone in the ZENworks group has done so. However, I think it
would stand a decent chance of working. Of course it would require the
use of a UNC Path, and not drive letters.
On 4/7/2011 12:36 PM, pitcherj wrote:
>
> Craig,
>
> I realize it's not DIRECTLY related to Dynamic Administrator, but I do
> have a SR in with Novell on this (the interactive services detection
> dialog, etc) and they said they were working on an alternate solution
> that would potentially allow users to see the UI of an installer.
>
> (Currently I have to make sure to start the ui0detect service since
> most of the time that service is not active on our user's workstations,
> so they have no way to view the progress of an installer other that the
> ZENwork progress bar)
>
> pitcherj
>
>
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.

WWW Location of the Novell Client for XP supporting IP Gateway Services

When connecting Windows XP workstations to the SBS 6.0 server through the
Novell Client 4.9SP1a for Windows XP, there are no services within 4.9
for IP Gateway included. As many of you know, by using BorderManager as
the Firewall/NAT/IP/IPX Gateway to access the Internet, all workstations
accessing the Internet need the IP Gateway service installed with the
client. The Novell Client CD-ROM shipped with the Novell SBS 6.0 media
has clients for Windows NT/2000 (outdated) but none are compatible for
Windows XP (it appears that Novell had not updated their Novell SBS 6.0
media since they started shipping it). In addition, the online
documentation included with the media is outdated (e.g. BorderManager 3.6
docs for BorderManager 3.7 being shipped) and do not mention anything
about configuring Windows XP clients for Novell IP Gateway services.
I have thoroughly looked within Novell's Support site the past few weeks
for:
+ The original Novell Client 4.9 (prior to support packs) to see if that
version of the client has IP Gateway services included (file not found or
listed).
+ Previous Novell Clients for Windows XP to see if those versions support
IP Gateway services. (Support Pack versions only are listed, but no
original versions, and do not contain Novell IP Gateway services).
+ Any instructions or tips for configuring the Novell IP Gateway services
within the Novell Client 4.9 or earlier versions for Windows XP(documents
are non-existent).
All of the above leads the following question:
Can someone please direct me to the location to where the proper
Novell Client for Windows XP supporting Novell IP Gateway services?
Since Windows XP has been around for a few years now, one would think
Novell would have developed a client for it that possesses Novell IP
Gateway services by now to be used with BorderManager. Correct? If so,
where is it? In addition, one would think Novell would include the media
supporting the current software they are shipping, not outdated ones.
(Or at least, ensure their outsourced sales services are doing so.) In
addition, one would also think Novell would at least provide the
necessary tools/files necessary to at least to have the ability to
install their products out of the box - instead of forcing their
consumers to purchase unnecessary additional support services for
something they should have included within their media package or website
at the start.
Nevertheless, I appreciate any input where to find the appropriate Novell
Client for Windows XP supporting Novell IP Gateway services.
Thanks,
EricV

In article <cb60c.5596$[email protected]>, wrote:
> As many of you know, by using BorderManager as
> the Firewall/NAT/IP/IPX Gateway to access the Internet, all workstations
> accessing the Internet need the IP Gateway service installed with the
> client.
>
This is simply not correct. Novell has not been providing IP gateway
functionality within Client32 for a long time, because it is not needed,
and it had serious limitations.
I haven't had a client using IP Gateway for many years now, and I have a
*lot* of BorderManager clients.
The alternative to IP Gateways is a combination of proxies and NAT w/filter
exceptions.
Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***

Novell Client for Linux on OpenSUSE 12.1

Hello everyone,
I'm looking for some information on getting the last release (2.0 SP2) of the Novell Client for Linux to install and run on OpenSUSE 12.1. Has anybody been able to do this yet?
Thanks

Yep,
However, openSUSE 12.1 comes with kernel 3.1.x . Come on guys, I would do it myself if I had the source code...
Originally Posted by W_Prindl
But it installs nice on SLED 11.2 , which also uses a 3.x (3.0.x)
kernel.
But the SLED 11.2 Novell Client version is 3.0.0-0.18.20.7 and this is
not available as a seperate download.
W. Prindl
Simon Flood wrote:
>On 16/03/2012 14:46, SylvainL wrote:
>
>>I'm looking for some information on getting the last release (2.0
>>SP2) of the Novell Client for Linux to install and run on OpenSUSE
>>12.1. Has anybody been able to do this yet?
>
>I believe the current Novell Client for Linux will not install on
>openSUSE 12.1 because of the move to using kernel 3.x.
>
>I've asked my contacts at Novell but in the meantime you should be
>able to install the ncpfs package and use ncpmount.
>
>HTH.

Login intermittently slow with ZCM agent AND Novell client

We continue to struggle with intermittently slow logins in our environment. In testing, we noticed that logins are very fast (10-20 seconds) when only the Novell Client is installed, and very fast (~10 seconds) when only the ZCM agent is installed. However, when they are both installed, logins slow down, sometimes to 1.5 minutes or longer.
We have checked DNS and rDNS, and they are both configured properly. SLP is working properly as demonstrated by the fast logins when only the client is installed. We use LDAP for user lookup, and it also works very fast to resolve user names (~ 1 second).
We are using ZCM 10.3.1, and the client is fully patched as well (both Novell Client 2 and 4.91)
Are there any specific settings (for the ZCM agent or the client itself) that might address this issue?

My apologies, I told you to remove the wrong thing.
I should have said NMAS instead of CASA.
I am just so used to saying CASA when talking about ZCM.
In regards to NMAS, you could simply rename "NWSSO.DLL" as a test.
If NMAS is installed which is tested by the existence of this DLL, then
a certain NMAS call is always made, which in some cases can take a long
time.
On 11/9/2010 12:06 PM, dshofkom33 wrote:
>
> craig_wilson;2042688 Wrote:
>> Try removing CASA from the device and see if that makes a difference.
>> A TID will be out on the issue soon.
>>
>> On 10/5/2010 4:36 PM, kjhurni wrote:
>>>
>>> Hmm, I will have to try that. I've only observed that with ZCM
>>> installed (with Novell Client 4.91 SP5 on XP) that the login time
>> goes
>>> from about 12-15 seconds to about 50-70 seconds.
>>>
>>> But I've not tried "just" the ZCM agent.
>>>
>>>
>>
>>
>> --
>> 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 removed CASA and now I cannot sign into ZCM. I get the "unable to
> login to network because the login credentials are incorrect" Windows
> Security Message. Any ideas?
>
>
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.

Deploy novell client

Similar Messages

Maybe you are looking for