problems with RMS (960 errors) and driver installation

[Michael Steigman]

Hi all,

I'm testing out the 4.83SP2 and 4.9 clients on 2K SP4 for a potential
rollout and have run into a snag. The newer clients seem to have issues
installing printers (assigned via ZfD 3 group policy). The printer
drivers were added via Nwadmin on a 2KSP2/4.81 machine. When adding
printers by hand, I get the error "You do not have sufficient access to
your machine to connect to the selected printer". On 4.83SP2, it seems
hit or miss (mostly miss) but on 4.9SP1, *no* printers will install.
Printers still install fine on 2KSP2/4.81.

At the same time, I'm coming up against another issue which seems to be
systemic since we've migrated from NDS 8 to eDir 8.6 - the dreaded 960
error (0x0100000A:1223) when trying to upload drivers to the RMS on all
servers. I'm seeing this error when trying to load any driver, even
drivers which have already been uploaded via a previous client version
(someone in the client.winnt-2k-xp forum suggested adding the drivers
from a machine with client version >= 4.83SP2) which seems to rule out
the "bad driver" scenario. Environment details - 5 server tree, all
running 5.1 SP5 with SCMD loaded in migration mode on all servers.
Clients are installed IP only. I have tried deleting/recreating the
broker on one server and that didn't help.

Any ideas on either issue? Are they possibly related? Thanks in advance.

Michael

[Michael Steigman]

For the sake of the archive, I thought I'd add that I solved this
problem by accident. Turns out that one cannot add drivers to RMS as a
member of the Windows "Users" group alone, at least not using 483SP2. I
had changed a DLU policy to put users in both the "Users" and "Power
Users" groups for testing purposes and happened to try to reproduce the
driver upload problem when all the sudden, it worked. Uploading the
drivers from a 483SP2 client in turn, solved the printer installation
problems I was having with the newer clients.