Setting up Windows 3.x for LANDesk client deployment.

[Chanly Bob]

Has anyone tried to setup LANDesk clients on Windows 3.1? If so, what protocols and services did you use? What tricks did you have to do to make it work? I have no problems with Windows 95 and NT. In the Windows 3.1 environment, when I logged onto the Novell server it runs the inventory scan, but not everything is loaded. I noticed that it created a folder "LDCLIENT", but I don't see any programs installed in the Windows 3.1 Applications folder. Anyone have any ideas? Thanks.

Chanly Bob
Technical Support
Willamette Industries, Inc.
Corporate Headquarters

[Francis Tourillon]

I have setup an environment with Win3.x, 95 and NT clients (LDMS6.1).
Most of my problems are related to Win3.x client only and mainly with metering.
Remote control and inventory are now fine.

Using Novell deployment and metering relay. IPX all the way.

I am not using the wizard to set the novell service center. Everything is manual
(I hate wizards, other that myself!!!)

So check out the clntcfg.ini file on your service center and/or core and edit
all lines that need tweeking (icons, .INI modif, registry...)

You will see the sun shine

-
Francis
to...@cam.org

[Mark Walford]

We are having 'issues' with deployment of WIN 3.1 clients (NOT 3.11) and have devised some fixes along the way.
I'm curious to know if anyone else is running Windows locally on each machine or from a Netware server. We are running Windows from the server (a legacy of the early days of our LANs - not recommended) and this presents a few problems.
If you try and deploy Landesk using the login script utilising the CCLOADER utility, you will see problems with the CCLOADER.INI containing a UNC path which 3.1 clients can't resolve. The only way around this was to create a Wininstall job to deploy the utilities.
Also, we are finding that certain files such as LDCLIENT and LDAPPL are written to the C: drive of each client. In our environment this may not be best practise, but we have no idea how to control the way files are placed during installation.
The other issues are as yet unidentified but are causing strange things to happen during remote control and inventory scans.
This thread is a good oppurtunity to share knowledge and problems for us unfortunates who have to deal with a large legacy base of WIN 3.1 clients. Our aim is to migrate from WIN 3.1 to NT 4.0 Workstation, but we need to capture the exisiting client configs first.
Is there anybody out there ??

[Francis Tourillon]

We are lucky enough to have all win3.1 and win3.11 running locally.
Some have netware vlm client and some client32 or intranetware clients.

Metering under win3.x is a headache. Still have a GPF problem related to printer
drivers and metering. I am working with Intel premium support to solve this issue.

I am not using include or exclude groups in NDS to deploy clients. I wrote a
program (run form login script also) that does this job of starting clntcfg.exe
or wscfg32.exe and is flexible enough to allow global upgrade/rollback as well
as targeted/selected upgrade/rollback. For example, we may not deploy metering
to 386 pc's because this agent slows down older pc's so much. But with pentiums,
no problems.

Good luck with network win3.x!

-
Francis
514-238-9581