setting up EPO on a Windows 2000 system

[Guest_imported]

does anyone know how to pusy the EPO agent to a Windows 2000 system. Everytime I try I get and error message syaing it can't push out. Is there something you need to change on the 2000 system in order for it to take. Any help will be greatly appreciated.

 

[FatesWebb]

Do you have the service pack?
here is a ton of info on why this could happen...

one reason the Push fails because IPC$, C$, and ADMIN$ have been removed or are non-existent. These are default administrative shares created by the operating system for Network Administration purposes.

To resolve this issue:

Test to see if you can connect to the machines admin$ share:
At a dos prompt type the following: net use \\machinename\admin$ (Where machinename is the client workstation)
If you can map a drive to the admin$, set the NAI ePolicy Orchestrator Server Service to a domain admin account and then stop and restart the service.
If you cannot map the admin$ share, reboot the workstation or remove all policies from the workstation and then reboot. The shares should be created.

____________________________________________________________
The services for ePolicy Orchestrator do not have sufficient privileges to install the agent on an NT workstation in the same domain.

Be sure that the services related to ePolicy Orchestrator are using a domain admin account to log in. These services are:

LDAPDB2
IBM SecureWay Directory v3.1

NAI ePolicy Orchestrator Server

NAI AV informant ePO LDAP Replication

After the services are changed to use the domain admin account, stop them in reverse order of the above listing and then restart them in order.

____________________________________________________________
Open a web browser and try to browse to below locations. The following is to is if there is web server services for Netscape or IIS (none on machine).
http:\\localhost:80
http:\\localhost:81
http:\\10.6.8.4:80 (Specify the IP address of server)
http:\\10.6.8.4:81 (Specify the IP address of server)
If no paged displayed,
customer needs to configure Internet Explorer properties to not use or automatically detect a proxy. (This configuration window can be found under Internet Explorer, Tools, Internet Options, Connections, and LAN Settings.).
Ensure that Microsoft Internet Information Server, Microsoft Proxy, Netscape Internet Server or any other similar product is not installed on the epo server.These Programs by default use ports 80 and 81.
If all ports are open and display a page, Try running POAGINST.EXE on a local machine to see if the ePO server is responding.


Under Control Panel, Services, Set the Service for " NAI ePolicy Orchestrator Server " to a Domain Administrator Account in NT 4 or an Enterprise Administrator account in Windows 2000. ( Note: If pushing across Domains Change the Account to a Domain Administrator Account in that domain.)
Reboot the server

-___________________________________________________________
While ePolicy Orchestrator (ePO) and the ePO Agent will not currently run on NetWare systems, it is possible to use ePO to administer antivirus software on Windows-based desktops within a NetWare environment:

Use a Windows NT 4.0 (SP5 or greater) Primary Domain Controller (PDC). Synchronize the User Name and Password for the NT Domain Admin and Novell Admin.


Authenticate the PDC to the NetWare server, using a NetWare Administrator login.


Install ePolicy Orchestrator using the NetWare Administrator login and apply this account to the ePolicy Orchestrator Server service.


Insure that the Domain Admin account is in the local Administrators group of each workstation.


For Windows 9x machines, insure that User Level security, Microsoft File and Print Sharing, and Remote Administration are enabled.

NOTE: ePO requires the TCP/IP protocol to function. Novell must have IP running as one of its protocols.


ePO can now administer clients on the network. Manual installation of the agent on the client may be needed. Use the POAGINST.EXE file (located locally on the ePO server) to install manually. Once installed, the ePO agent will attempt to connect to the ePO server via the default port assigned as the AgentHTTP port. The agent will first attempt to contact the server using the server's IP address. If that fails, the agent will use name resolution.


FatesWebb

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