Call Pilot Reporter Install 1

[pbxNewb]

OK, I've read all the similiar posts but don't see anything similiar to my issue. I'm trying to install the Reporter onto my web server, the same one that currently hosts the MyCallPilot. MyCallPilot works great, always has. When I install the reporter (from the physical media), it completes, restarts IIS services, and thats it. I can't find it anywhere, the install directory doesn't even exist. But if I run the installer again, it asks to repair or remove, so it is definitely there somewhere but where? I removed it, specified my own install directory, and same story. Where is it hiding? It has no errors in the install process, and seems to be doing allot of tasks during that time with a progress bar.

Anyone have any ideas? I've rebooted the server after the install, and still cannot find it. If it were installed, I should be able to get to it from a web browser right? by going to

http://<IP

of web server>/CPMGR/cprpt

When I try that, I get a page can't be displayed, and an error about setting up a webpage in IIS on the server. My CallPilot manager works just fine too. Does it install it to the actual CallPilot server instead? I tried

http://<IP

of callpilot>/CPMGR/cprpt and have same result, no page. Maybe my address is wrong and its something simple? This is CallPilot 5 BTW. Let me know, thanks!

 

[asodoma]

How about this after the IP? cpmgr/login.asp

 

[KCFLHRC]

The Call Pilot Reporter and Call Pilot manager is the same software. When you install the Call Pilot Manager PEP on the Call Pilot Server it is a PEP in conjunction with the latest SU. When you install the same software on a standalone web server it doesn't see the Call Pilot Installation so it installs Reporter. Not sure what you mean by you are installing it on the same server with MyCallPilot. The key here is it is a standalone server, with no other crap loaded on it.

 

[pbxNewb]

Just to clarify, the CallPilot Manager works just fine, never had any trouble accessing that. Its CallPilot reporter that I am trying to make run. CallPilot Manager is on the CallPilot server, "My CallPilot" interface is on a seperate web server. Are you saying that if I have CallPilot Manager (which you would have to have installed to access the system) that Reporter is there as well? On the physical install applications disc, There is a "MyCallPilot" folder (which I installed from a long while ago), and a CallPilot Reporter installation folder.

Where should I be running the CallPilot Reporter install files from, the seperate web server, or the actual Callpilot server (Nortel hardware)? Once installed, how do I access it via web interface? Let me know if you need any additional info. Thanks!

 

[KCFLHRC]

Call Pilot Manager is nothing more than your web interface to administer CP. When you install the latest PEPS in the Call Pilot Server you will have the latest SU and the latest Call Pilot Manager which is the C PEP. The C PEP is Call Pilot Reporter when installed on a stand alone server. When the C PEP is installed on the CP Server then it is Call Pilot Manager. It's the same software. You run the MSI file.

 

[KCFLHRC]

If you look at the README file for the Call Pilot Manager PEP it explains it all.

 

[pbxNewb]

I think thats what I was missing. I'm looking at the install guide, and see that the CP manager can be installed on a stand alone web server along with MyCallPilot. I did not install the system originally and just assumed CallPilot Manager had to be running directly on the CallPilot server.

I am in the process of copying the disc to a network share and will try to install Callpilot manager on the web server. Can it be installed in 2 different locations (the web server and the CallPilot server) at the same time without affecting Callpilot? If its just a web interface, it shouldn't matter....

 

[KCFLHRC]

Once again, it's the same software. When it's installed on the CP server it is Call Pilot Manager only. When installed on the standalone server it is Call Pilot Manager and Reporter. There is no way to install reporter on the CP server. It see's the CP software is loaded and only installs the manager on the CP server.

 

[KCFLHRC]

Also keep in mind that whatever Call Pilot Manager software you use they have to match in both servers. You aren't suppose to run 2 different versions.

 

[pbxNewb]

As usual, you guys rock! I have it all up and working. I installed CallPilot manager onto the seperate web server, making sure to check the "callpilot reporter" check box at the beginning of the install. Once it was installed, I could not access the login page. Some more searching on this site, and I came across the answer to that as well. I followed the instructions below, and it is all up and running perfectly now. I'm now using it as single login address for two seperate CallPilot 5.0 servers, and the reporter and app. builder (if installed locally) work great!

To configure a customer-provided Windows Server 2003 with SP2 for use with CallPilot Manager/Reporter (pre 5.0/SU02)
1. Open Start > Administrative Tools > Component Service.
2. On the left pane of Component Services, go to Component Services > Computers > My Computer > DCOM Config > CallPilot Reporter.
3. Open Security tab in CallPilot Reporter properties.
4. Under Launch and Activation Permissions click Customize, and then click Edit.
5. Add NETWORK group with Remote Activation and Local Activation permissions granted.
6. Add NETWORK SERVICE group with Local Launch and Local Activation permission granted.
7. Click Ok.
8. Click Ok again.
9. Open Start > Administrative Tools > Local Security Policy.
10. On left pane of Local Security Settings go to Local Policies > Security Options.
11. On the right pane click on DCOM: Machine Launch Restrictions in Security Descriptor Definition Language (SDDL) syntax.
12. In DCOM: Machine Launch Restrictions in Security Descriptor Definition Language (SDDL) syntax window click on Edit Security… button.
13. Add NETWORK group with Remote Activation and Local Activation permissions granted.
14. Click Ok.
15. Click Ok again.
16. Reboot the server to full service.