Netware & Microsoft Servers - IS IT POSSSIBLE!!!!!!!

[cardiffdutch]

Hello People,

Here at work we have Netware Servers and some Microsoft Domains - Clients are running Win 9x, Win 2000 and Win XP - I have installed the ePO server on a NT4 Server box and all I can see are the Microsoft Domains - What do I need to do to be able to view these Netware Servers - Network Associates seem to keep avoiding this issue but when we were sold the product we were informed that it would work no problem - I have set up a small purely Microsoft test enviroment, (removed Novell Client) with the NT4 Server and a couple of XP Clients, and I am unable to deploy VirusScan 7.0 to these machines - I was sucessfull in deploying the agent, so they can communicate ok, but I just cant deploy the AV Software.

I need to deploy this to around 700 users and am having trouble getting things straight in just a test enviroment.

I really am starting to pull my hair out, so any help would be greatly appreciated.

Please stop me from making myself bald - Im only 24!!!!!

Many thanks

Cardiff Dutch

 

[FatesWebb]

for netware you must deploy the agent locally. it will then checkin to epo.

you must have a windows domain, and it cannot be a 2k native mode domain yet.. to be able to see the systems in epo. you can manually add systems from a work group, but it will not manually pull them, same with 2k AD native mode.

also for 9x the target machine must have file and print sharing enabled.

for 2k/xp you must have the remote registry service enabled.

for all systems except novel servers you must be able to access the admin$ shares to install the agent.

you should right click on directory and choose search for duplicate computer names. if you have duplicates remove any that have not checked in or checked in most previously.

when pushing the agent out. what works best, and can help you to troubleshoot permissions in the domain, what you can do is disable use epo server credentials, and input .\administrator for the users, and the local admin password for the password. Epo will use the local admin account for the install.

you can install the agent locally by running framepkg.exe /install=agent

framepkg.exe can be found on the server in the db folder.

If I can think of more....

FW

FatesWebb

if you do what I suggested it is not my fault...

 

[AVChap]

Have you added VSE 7.0 into the repository? (Hopefully you should've already done this). If so, under the task tab, edit the deployment task and in the drop-down list select Install in lieu of Ignore.

AVChap

“I have not failed 700 times. I have not failed once.
I have succeeded in proving that those 700 ways will not work.
When I have eliminated the ways that will not work,
I will find the way that will work.”
--Thomas Edison

 

[cardiffdutch]

Thanks for your response guys, it is appreciated.

FATES WEBB, When you say I should manually install the agent for Netware, do you mean on the Servers or on the the clients?

AVCHAP, I had already added the VSE 7.0 to the repository but in the edit deployment task I havent got an option to install in lieu of ignore - I am running 2.5.1.

FATES WEBB & AVCHAP, I have manageed to deploy the AV Software into the samll test enviroment that I have set up but the agent will not deploy to the Win 98 machines - I tried installing it manually, through ePO and via logon script and all fail miserably!!!!

Sorry to bother you, but any ideas????

Cardiff Dutch

 

[FatesWebb]

on the NW servers you must manuall install the nlm.

on the workstations if your not in a windows domain, you must manualy install or install from sms, or script...

as for the agent not installing local on win9x that is unusual, If you installed from a image, it may be something on the image, that is causing a problem.

Since it is 2.5.1 I dont recall just this second if the agent install is silent, but you should be able to get some sort of log from the install. There might be a switch that you run with aginst32.exe that will log the install. with 9x, the agent push is somewhat simple, it pushes out the agent to the admin$ share, and puts it into startup, so a reboot is required for the push install. however since you are installing it locally, you have iliminated this process, and have shown that there is some sort or incompatiblity. either way I think you may need logs!

FW


FatesWebb

if you do what I suggested it is not my fault...