Novell Client 4.91 SP5 w/Wise
[font="microsoft sans serif"]I am new to packaging and am having a problem packaging the Novell Client 4.91. My first go round was with SP4; gave up and went to SP5 but I am having the same issue. I create the MSI using Wise then boot up a cleanly-imaged XP machine. Using Windows Explorer I navigate to the Wise Share Point/Project/Novell_Project and double-click the MSI. I then reboot the machine; you can see the original Windows login blip and then I wait for more than 5 minutes before I get the Novell login prompt. After entering the user ID and password everything appears to work fine... except that the PC shutdown takes forever as well. If I re-image the machine back to clean XP and install the Novell Client using the Novell-distributed EXE, everything works fine, no delays at start-up or shutdown. Obviously something is breaking during the repackaging. Does anyone have any clue what might be breaking?
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
jcarri06
14 years ago
Dadman,
If you're new to packaging, you're probably starting with the wrong application to get your feet wet :). I haven't touched the Novell client in years, but considering how critical it is, how it binds itself to the OS, and how there is a very likely chance you'll have to call support at some point in time and they won't even try to touch it until you install with their installer, I wouldn't even bother packaging this. Instead, I would look for the recommended deployment method that Novell has (maybe it's an MSI itself...although I doubt it) and go with that.
Good luck
- J
If you're new to packaging, you're probably starting with the wrong application to get your feet wet :). I haven't touched the Novell client in years, but considering how critical it is, how it binds itself to the OS, and how there is a very likely chance you'll have to call support at some point in time and they won't even try to touch it until you install with their installer, I wouldn't even bother packaging this. Instead, I would look for the recommended deployment method that Novell has (maybe it's an MSI itself...although I doubt it) and go with that.
Good luck
- J
Posted by:
anonymous_9363
14 years ago
Whilst the above may well be good advice, some persistence - as well as what I regard as proper packaging practice - may pay off.
For *ANY* captured app, I always recommed that you:
- install your MSI
- start a lightweight snapshot tool like Ziif-Davis's In Control or InstallWatc and take a 'Before' snapshot
- Remove any registry flags that indicate the app is installed (to prevent any 'Repair/Remove/Modify' prompt)
- Run the vendor set-up stub over the top
- Take an 'After' snapshot
- Add any relevant changes to your package
- Re-test, as above
For *ANY* captured app, I always recommed that you:
- install your MSI
- start a lightweight snapshot tool like Ziif-Davis's In Control or InstallWatc and take a 'Before' snapshot
- Remove any registry flags that indicate the app is installed (to prevent any 'Repair/Remove/Modify' prompt)
- Run the vendor set-up stub over the top
- Take an 'After' snapshot
- Add any relevant changes to your package
- Re-test, as above
Posted by:
joedown
14 years ago
I would think twice before attempting to capture this software. It is made up of a setup.exe and some msi's depending on what options you select. The best method is to use Novell's answer file to deploy the client. This will provide a consistent unattended installation. Have a look at the acu.cfg and acu.ini files.
Posted by:
dadman53
14 years ago
Management wants everything to be packaged through Wise... no exceptions, and this is the most prevalent piece of software in the company so this is why I started with it. But here is another rub... corporate and our two largest divisions have been on Novell & GroupWise for years. Another acquired division is on MS-AD and Exchange. We don't have the $ to convert the entire corporation to MS-AD and Exchange at this time, so they want a clean PC image that they can deploy to any division. Hence the need/desire/whatever to create a Wise MSI. You are correct in stating that this app is a bear to start with.
All this stuff was a lot easier on the mainframe with SMP/E...
All this stuff was a lot easier on the mainframe with SMP/E...
Posted by:
jcarri06
14 years ago
Have you considered consulting with Novell in regards to what their support stance would be? I'm sure if management becomes aware that you could potentially lose support on those installations along with a risk assessment they may realize they're taking the wrong approach. Also, the grand majority of people here would agree that you want to package everything possible into msi format...but to say that everything CAN/SHOULD be repackaged is a huge overstatement. Joe's post above states the installation contains MSIs. Assuming this is correct, recapturing an MSI is a big no-no as well.
Send your management to this forum to ask :).
If you end up packaging it, good luck! we'll try to help where at all possible, but it'll all likely be "theory helping" more than actual since I doubt anyone has repackaged Novell :).
Send your management to this forum to ask :).
If you end up packaging it, good luck! we'll try to help where at all possible, but it'll all likely be "theory helping" more than actual since I doubt anyone has repackaged Novell :).
Posted by:
sumanlavu
14 years ago
Did anybody successful in repackaging NOVELLCLIENT 4.91SP5 if so please guide me ...
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.