It's been a good 48 hours. (Scarpozzi is happy)

[Scarpozzi]

I was in this rut for a long time here at work. All these things were breaking with my servers and none of the problems had easy solutions... For example, I was trying to create an image for some computer lab managers that would allow authentication from a netware server using Client32 on Windows 2000... But that wouldn't work without prompting the user for an additional windows logon. This problem was just recently fixed by some people at Novell and I found the registry changes that I needed to make.

My primary backup server crashed last week and I wasn't able to really work on it until today because I knew it was going to take a while to wrestle with the corrupt mirrors and unsynchronized partitions... After a couple of hours this afternoon I got that working so backups will run tonight! w00t!!!

One of the brand new Dell Servers (new last July) that I installed had a RAM failure and I had to troubleshoot that... Dell finally sent me the RAM and it's back up and running now. w00t!

Anyhow....I'm just generally happy for the moment because I've only got a couple of things that I'm trying to get working... Then I get to go back to new projects and attempting to build 2 new clusters.

Sorry, I just had to share. Things are good!

 

[Legendary]

Congratulations, although the only part of that I clearly understood was the RAM.

 

[Scarpozzi]

Originally posted by: Legendary
Congratulations, although the only part of that I clearly understood was the RAM.

LOL....there's no point of me typing out how particular Netware Servers are. We're doing a full-scale implementation of Netware 6 here including Portal Services, Netmail, NetStorage, iFolder 2.0, iPrint, upgrading to NDPS from Bindary print queues, and using Apache for Netware to host web pages for all 14,000 users. It's very, umm...fun.

The Backup server that went down was one that's been here longer than me.... It was running NW 4.11 and the volumes were corrupt, so I had to rebuild them....it wasn't any fun because it couldn't load the namespaces properly because of a bunch of backend issues so I had to pretty much give the base-end of the bootstrap an overhaul and import new NLMs from the latest service pack. I'm glad I don't have to do that every day. :disgust:

 

[ROTC1983]

Originally posted by: Legendary
Congratulations, although the only part of that I clearly understood was the RAM.

 

[dmcowen674]

Originally posted by: Scarpozzi
I was in this rut for a long time here at work. All these things were breaking with my servers and none of the problems had easy solutions... For example, I was trying to create an image for some computer lab managers that would allow authentication from a netware server using Client32 on Windows 2000... But that wouldn't work without prompting the user for an additional windows logon. This problem was just recently fixed by some people at Novell and I found the registry changes that I needed to make.

Cool, that is from the old Novell ZEN programming days, still works though

 

[acidvoodoo]

Originally posted by: ROTC1983

Originally posted by: Legendary
Congratulations, although the only part of that I clearly understood was the RAM.

 

[Goosemaster]

HOw would you compare your network as it is going to to be to an MS network? (ADserver, Exchange etc)

 

[Scarpozzi]

Originally posted by: Goosemaster
HOw would you compare your network as it is going to to be to an MS network? (ADserver, Exchange etc)

Microsoft Network will work just as good....however, there are a lot of new toys on Netware 6. The security is pretty high compared to the 'well-known' holes in Microsoft. We can use less servers to do the same amount of work, and the licensing price is about a fourth of what Microsoft would charge to do the same things. I am assuming that we'll have limited problems with the cutover. Everything is running production right now, but we haven't officially switched our MX yet or notified users that the systems are up and running. We're finalizing some things and I'm going to build 2 more clusters for fault tolerance in the very near future.

Ohh yeah....NetWare 6 no longer requires individual server licenses...so you can install as many servers or 2-node clusters as you wish to support your Enterprise. This makes it easy to ensure that you will have fewer bottlenecks.

Cool, that is from the old Novell ZEN programming days, still works though

Actually, ZenWorks isn't running yet. This is just dealing with a straight-up Windows 2000 user profile and forcing AutoLogins on 2000 after a user authenticates with NDS. The difference is that Zenworks isn't handling the profile... The only downside to this scheme is that the default username and password are stored as clear-text in the registry, but that makes no difference since the user can't see it anyway without logging in as Administrator.

 

[Goosemaster]

Originally posted by: Scarpozzi

Originally posted by: Goosemaster
HOw would you compare your network as it is going to to be to an MS network? (ADserver, Exchange etc)

Microsoft Network will work just as good....however, there are a lot of new toys on Netware 6. The security is pretty high compared to the 'well-known' holes in Microsoft. We can use less servers to do the same amount of work, and the licensing price is about a fourth of what Microsoft would charge to do the same things. I am assuming that we'll have limited problems with the cutover. Everything is running production right now, but we haven't officially switched our MX yet or notified users that the systems are up and running. We're finalizing some things and I'm going to build 2 more clusters for fault tolerance in the very near future.

Ohh yeah....NetWare 6 no longer requires individual server licenses...so you can install as many servers or 2-node clusters as you wish to support your Enterprise. This makes it easy to ensure that you will have fewer bottlenecks.

Cool, that is from the old Novell ZEN programming days, still works though

Actually, ZenWorks isn't running yet. This is just dealing with a straight-up Windows 2000 user profile and forcing AutoLogins on 2000 after a user authenticates with NDS. The difference is that Zenworks isn't handling the profile... The only downside to this scheme is that the default username and password are stored as clear-text in the registry, but that makes no difference since the user can't see it anyway without logging in as Administrator.

Interesting...

 

[GoodToGo]

I thought you were getting laid for 48 hours straight, now that would be something to be happy about.