Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Anonymous_User Absent Member.
Absent Member.
1854 views

experience about life without Novell Client?

Hi,

got anyone a wider experience about OES Infrastructure without Novell
Client and W7 Workstations?

We didn't need absolut highest performance but an absolut stable and
reliable Environment (24h Healthcare).

- Is Performance with CIFS Access to OES NSS Cluster Ressources comparable?
- Is availability comparable (in special Cluster migrations, Filelocking
on Files)

Today we run ~250 XP Workstations on OES2
Cluster/Filesharing/iprint/Zen7 and Groupwise.

Now we are going to ZCM11 and W7/64bit and think about avoid to use the
Novell Client for Windows to reduce complexity and switch on Client Side
to AD-Domain and use OES Infrastructur only for the "Backend".

Most Novell Services (Groupwise/iPrint) are going to auth to AD too, so
why should we use Novell Client and the NCP Protocol anymore?

Is the NCP Protocoll so much better against CIFS in current OES
Implementations (i'm no Expert in this Things).

Regards
Thomas





Labels (1)
0 Likes
8 Replies
kvishwanath1 Absent Member.
Absent Member.

Re: experience about life without Novell Client?

Welcome to Novell CIFS !!

To begin with - "OES Infrastructure without Novell Client on Win 7 is possible by Novell CIFS"

To answer your specific questions,
- Yes, CIFS has Comparable performance improvement w.r.t. Novell Client in recently released versions like OES2SP3,OES11FP0 & Upcoming OES11 SP1.
- CIFS service is a cluster enabled, It works seamlessly on cluster migration, supports cross protocol lock feature across protocols (CIFS, NCP, AFP).


In addition, CIFS supports Distributed File Services(DFS), Dynamic Storage Technology (DST), backup an many more features. Please refer Novell Documentation for more details.

Specific to your infrastructure question of ~250 XP workstations, we have scaled CIFS service up to 4000 connections on single server 3 node cluster setup. Howe ever we are interested to know more details on your setup and infrastructure details further on this.

Thanks,
Vishwa
0 Likes
W_Prindl Absent Member.
Absent Member.

Re: experience about life without Novell Client?

Novell CIFS does work but I'd recommend on testing it, whether it
really fits your needs, before you deploy it. If you only have 250
workstations you could also consider running Novell Samba instead of
CIFS it is limited in scale but IMO much more reliable than Novell
CIFS, but I am not sure about cluster support.

At the moment I have severe authentication issues - sometimes it works
but sometime or fom time to time it simply stops working for some user
- with CIFS on OES11. If you let time pass away it suddenly starts
working again. These issues I did not have with the same data (and
server) on OES2 SP3. So at the moment CIFS is only active on servers,
which are not accessed by ordinary users, but only by admins.

Also IMO the best performance on OES servers you get via NCP and Novell
client. There have been quite a lot of issues with the Win7 NCP-client
in the past, but they are almost all resolved now.
--
W. Prindl


Thomas Reiß wrote:

>Hi,
>
>got anyone a wider experience about OES Infrastructure without Novell
>Client and W7 Workstations?
>
>We didn't need absolut highest performance but an absolut stable and
>reliable Environment (24h Healthcare).
>
>- Is Performance with CIFS Access to OES NSS Cluster Ressources
>comparable? - Is availability comparable (in special Cluster
>migrations, Filelocking on Files)
>
>Today we run ~250 XP Workstations on OES2
>Cluster/Filesharing/iprint/Zen7 and Groupwise.
>
>Now we are going to ZCM11 and W7/64bit and think about avoid to use
>the Novell Client for Windows to reduce complexity and switch on
>Client Side to AD-Domain and use OES Infrastructur only for the
>"Backend".
>
>Most Novell Services (Groupwise/iPrint) are going to auth to AD too,
>so why should we use Novell Client and the NCP Protocol anymore?
>
>Is the NCP Protocoll so much better against CIFS in current OES
>Implementations (i'm no Expert in this Things).
>
>Regards
>Thomas


W. Prindl
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: experience about life without Novell Client?

On 25.04.2012 06:16, kvishwanath wrote:
>
> Welcome to Novell CIFS !!
>
> To begin with - "OES Infrastructure without Novell Client on Win 7 is
> possible by Novell CIFS"
>


[...]

> To answer your specific questions,
> - Yes, CIFS has Comparable performance improvement w.r.t. Novell Client
> in recently released versions like OES2SP3,OES11FP0& Upcoming OES11
> SP1.
> - CIFS service is a cluster enabled, It works seamlessly on cluster
> migration, supports cross protocol lock feature across protocols (CIFS,
> NCP, AFP).
>
>
> In addition, CIFS supports Distributed File Services(DFS), Dynamic
> Storage Technology (DST), backup an many more features. Please refer
> Novell Documentation for more details.


I know this, but in real life there are always pitfalls...

>
> Specific to your infrastructure question of ~250 XP workstations, we
> have scaled CIFS service up to 4000 connections on single server 3 node
> cluster setup. Howe ever we are interested to know more details on your
> setup and infrastructure details further on this.
>


What would you like to know?

Most infos are on my first post.
We get more and more Windows Applikations who need a Windows Server as
Plattform for Services, Shares and Authentication.

In the past we create lokal "system" Accounts on these Applikation
Servers and map there Shares with help of the Loginskripts.
like map use R: \\app-server\files password /user:<systemaccount>

But now we are low on Drive Letters...

So now we think about to bring the Applikation Server and Windows
Workstation into AD-Domain for using same User Accounts/Passworddatabase
and use the UNC Syntax for this kind of Applikations.

Or we use some Applikations/Infrastruktur who use "transparent" Login
with AD Authentication (sp. Citrix) or use this as Authentication Point.

And that's our thoughts about CIFS and Novell Infrastractur in General.

Regards
Thomas
0 Likes
Knowledge Partner
Knowledge Partner

Re: experience about life without Novell Client?

Hi.

On 05.05.2012 12:09, Thomas Reiß wrote:
>
> In the past we create lokal "system" Accounts on these Applikation
> Servers and map there Shares with help of the Loginskripts.
> like map use R: \\app-server\files password /user:<systemaccount>
>
> But now we are low on Drive Letters...
>
> So now we think about to bring the Applikation Server and Windows
> Workstation into AD-Domain for using same User Accounts/Passworddatabase
> and use the UNC Syntax for this kind of Applikations.


I'm royally confused now. Where do you see a difference in using CIFS or
NCP here? It both works exactly the same, nothing stops you from using
UNC paths with NCP too.

CU,
--
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: experience about life without Novell Client?

Am 05.05.2012 13:15, schrieb Massimo Rosen:
> Hi.
>
> On 05.05.2012 12:09, Thomas Reiß wrote:
>>
>> In the past we create lokal "system" Accounts on these Applikation
>> Servers and map there Shares with help of the Loginskripts.
>> like map use R: \\app-server\files password /user:<systemaccount>
>>
>> But now we are low on Drive Letters...
>>
>> So now we think about to bring the Applikation Server and Windows
>> Workstation into AD-Domain for using same User Accounts/Passworddatabase
>> and use the UNC Syntax for this kind of Applikations.

>
> I'm royally confused now. Where do you see a difference in using CIFS or
> NCP here? It both works exactly the same, nothing stops you from using
> UNC paths with NCP too.
>
> CU,


Using of the Novell Client on Windows Workstation, that's the difference.

Why should we use the Novell Client further for Access to Windows
Applikationservers and OES Fileserver, it's another Produkt to support
and maintain with his own Issues?

We would reduce the complexity on Client Site for file Access to
Windowsserver and OES Server and avoid Authentication Issues for example
local Windows Workstation Users (Non AD) to AD Windowsserver.

Regards
Thomas
0 Likes
Knowledge Partner
Knowledge Partner

Re: experience about life without Novell Client?

Hi.

On 05.05.2012 14:15, Thomas Reiß wrote:
> Using of the Novell Client on Windows Workstation, that's the difference.
>
> Why should we use the Novell Client further for Access to Windows
> Applikationservers and OES Fileserver, it's another Produkt to support
> and maintain with his own Issues?


But that wasn't your question, or the reason you're given. You said you
were running out of drive letters because of the Novell Client, and
that's just not the case.

And what you're possibly gaining on the client side, you'll lose on the
server (as you add complexity and another layer there), and
potentionally in functionality.

> We would reduce the complexity on Client Site for file Access to
> Windowsserver and OES Server and avoid Authentication Issues for example
> local Windows Workstation Users (Non AD) to AD Windowsserver.


But that again is an invalid reason really. You don't have to use non-ad
local users today, that's again not related to the question if Novell
Client or not. Nothing stops you from using AD user today, with the
Novell Client.


CU,
--
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
Highlighted
Anonymous_User Absent Member.
Absent Member.

Re: experience about life without Novell Client?

Am 05.05.2012 18:36, schrieb Massimo Rosen:

[...]

>
>> We would reduce the complexity on Client Site for file Access to
>> Windowsserver and OES Server and avoid Authentication Issues for example
>> local Windows Workstation Users (Non AD) to AD Windowsserver.

>
> But that again is an invalid reason really. You don't have to use non-ad
> local users today, that's again not related to the question if Novell
> Client or not. Nothing stops you from using AD user today, with the
> Novell Client.
>


Hmm, ok.

Totally irrelvant here, but isn't (wasn't) a recommended setting to use
the ZCM Management Agent only on a "plain" AD Domain Windows Workstation
without Novell Client _OR_ a Windows Workstation with Novell Client and
dynamic local User?

Looks i'm out of actual Knowledge on that because too much other Projects.

New co-worker knows always Windows Environment only....

Feeling like last dinosaur 8-)

Thx
Thomas



0 Likes
Knowledge Partner
Knowledge Partner

Re: experience about life without Novell Client?

On 07.05.2012 20:35, Thomas Reiß wrote:
> Am 05.05.2012 18:36, schrieb Massimo Rosen:
>
> [...]
>
>>
>>> We would reduce the complexity on Client Site for file Access to
>>> Windowsserver and OES Server and avoid Authentication Issues for example
>>> local Windows Workstation Users (Non AD) to AD Windowsserver.

>>
>> But that again is an invalid reason really. You don't have to use non-ad
>> local users today, that's again not related to the question if Novell
>> Client or not. Nothing stops you from using AD user today, with the
>> Novell Client.
>>

>
> Hmm, ok.
>
> Totally irrelvant here, but isn't (wasn't) a recommended setting to use
> the ZCM Management Agent only on a "plain" AD Domain Windows Workstation
> without Novell Client _OR_ a Windows Workstation with Novell Client and
> dynamic local User?


No. It is/was a (valid) recommendation not to use DLU in an AD
environment, which is logical. That's all. There is no problem with the
Novell Client and/or ZCM in an AD setup (without DLU).

CU,
--
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
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.