Unity Computing

[jaklein]

Here's a "sticky" topic to keep track of known issues with WolfPrep, so folks don't have to read through miles of listserver archives to determine if an issue has been reported.

These are not in order of priority.

The Administrator password is NOT set reliably.
In the active directory environment, we'll have one or more domain groups in the local Administrators group. This will allow remote management of who can log in as an admin, and allow us to randomize and disable the local Admin account.

Work is currently in progress to no longer use Novell's Dynamic Local User facility to initiate the WolfPrep process, which will eventually allow us to not have a Wolfprep password "well known" in the wild.

Some devices, notably audio, don't have autoinstallable drivers
WolfPrep only looks at the "vendor + device" PnP codes, and doesn't use or understand the "subvendor + subdevice" info describing what subordinate devices are attached to a generic "glue" chip. Nothing a complete rewrite can't fix.

As we look to replace Zen imaging with partimg we'll likely use the factory mode in sysprep more completely. Work needs to be done to see what sort of networking capabilities are available in factory mode.

Another growth area is support for multiprocessor PC's. It should be possible to detect a multiprocessor PC during the linux install phase, and overwrite the uniprocessor HAL.dll with a multiprocessor one.

We don't have access or space on the Zen imaging server
Work is in progress to eliminate the concept of an "imaging" server, and allow installation from any (SMB) network server (even if it's a Mac )

We can't manage our own templates
Work is in progress to bring up a beta of the long awaited "WolfPrep web mangement" page.

I'm sure I've omitted your favorite anti-feature, which is why this is being presented in a forum -- so you can comment and set the record straight!