NCSU OIT Integration Services

Sigh. Novell has releasd Service Pack #5 for Client-32 4.91

http://download.novell.com/Download?buildid=qmMAWSRy5q4~

We'll need to test this against our NDPS stuff to see if it fixes anything.

If you read way far down in the list of things addressed, it does mention

Ndppnt.dll from 4.91 SP4 breaks NDPS printer installs

Last week nds02ps crashed a bit, and had trouble crashing on automatic restart.  I think the issue was that when the ndps broker and manager were loading too soon after startup, we ran out of memory or cpu or karma and the box would crash.

 I've added the command DELAY 120 just before loading the broker/manager, so we should wait 2 full minutes after a reboot to actually start the print system.  Hopefully, this delay will help the box survive a reboot.

So this is a little late for the first blog entry given the amount of e-mail and face-to-face discussions going on in this topic, but XP SP3 breaks NDPS printing in a pretty horrible way.

In short, after installing a new ndps printer, it will work until the workstation is rebooted, at which point jobs will get spooled, but sit on the local machine forever, never reaching the server and certainly never printing.

Here are the release notes for the "MinApps" kit, released August 2, 2008

The applications "Pidgin" and WinSCP are not installed in this image as originally intedned. Pidgin fails with an MSI 1602 error, and WinSCP tries to write to C:\ and won't install as a non-administrator. We'll fix these in the NAL.

There is a problem with IZArc in this image in that it tries to do a repair with any folder operation.  We'll remove this IZArc in the wolfprep script to correct this. 

To install this application, use

There's some problems with the NoApps kit just released and VMWare, which possibly could catch other types of machines as well.

As part of the Sysprep preparation process, the machine has all of it's network adapters removed, so that when sysprep unpacks a new machine it can do a clean plug and play detection.  Unfortunately, the loopback adapter used by AFS is neither plug and play nor properly restored via the MSI self healing magic.

We've had some more problems with nds10ps, which is a virtual server hosted on winvhost00.

As part of trying to fix things, we've upgraded the vmware server on winvhost00 from 1.04 to 1.06, and installed the newest vmware tools on all the guest OSes. The guests are scripts01, scripts02, printsync and nds10ps

So I've finally figured out why dynamic local user failed as soon as I installed Zen Agent 7.0.168.6000

Turns out, it removes the C:\Program Files\Novell\Zenworks entry from the path. It also depends on this to work. OMG.

Novell has a TID that suggests running
PATHMAN /as C:\Program Files\Novell\Zenworks

to make sure the entry gets written properly. So, having replaced the ACU with home grown code, we must now proceed to write more and more of the install logic.

So, Kevin's been bearing the brunt of nds10ps suddenly deciding it doesn't want to keep timesync.

Looking over  

http://www.nag.ncsu.edu/nag/timesync/index.html

 I've changed nds10ps to NOT use the :123 port indicating that it should use NTP for time syncronization, but just listed the server names in the configured sources list, so NW will use it's own, magical sync protocol.

So I wanted to gather my notes regarding what we need to do to murder UNI04NT.

Tomcat on port 8080

I met with Tony and Bill on friday to discuss how we can transistion the SLP services and servers to their team. 

The plan is that Bill will bring up a new VM to which we will assign the same IP addresses and SLP/Replica configuration that SLP-625 uses, so we can decommision it and reduce our servers in Poe Hall, and own one less NW 6.0 server.