Call Manager install fails

[mgaffney]

Thanks for your suggestions.

I tried going into Configure ShoreTel Manager, but because I'm not connected to the server yet, this option, unfortunately, is greyed out.

I exported and deleted both of the registry keys you had suggested, and that brought me back to the initial setup screen, which will be good for future reference! However, as before, when I go into the setup, enter in the correct username, password and server name and click Next, the operation looks to be performing an authentication, and it times out every time - this happens regardless of if I use the NetBIOS name or IP address of the server.

Can you think of another registry key I might be able to delete/override so I can get this authentication to take place? I've been constantly stuck at this point, on this one machine, forever, and I've tried uninstalling and reinstalling the software countless times.

Thanks to anyone who can help me!

[Jlorenz]

the issue is your logging in as a domain administer, you simply cannot do this. If you log in as local administer it has to be ADMINISTRATOR Only

Not a user with administration rights. you ran the gpresults under the wring name, you should had done that under the users log in credentials, you issue is still your GP Policy.

It was suggested to retool the OS, that would be the worst case scenario but suggested at this moment., Cleaning the registry is going to be a proverbial needle in the haystack. Your best bet is to log in as the Local Admin

Uninstall the Call Manager
Before reboot, go to regedit
HKLM\SOFTWARE\Shoreline Teleworks\Shoreware
and delete anything Shoreware and Shoreline

Reboot

Log in as Local Admin (Administrator) not a user with admin, not a domain admin

Install the product (If it fails Retool the OS) if it does not
Reboot
Log in as the Local Administrator again
Finish the install by putting the Users Name (The Normal User of That PC) and password along with the IP of the ShoreTel Server

If you are able to get to that point, reboot, Log into the PC as the User and launch PCM.

If it failes you will need to then run gpresults as the user, and adjust the gpo to allow that user to run PCM

[mgaffney]

I went ahead and uninstalled the software, deleted the registry key you mentioned, logged in as a Local Administrator, and reinstalled the software. When I did this, I tried running the software logged in as the local Admin, but using the username, password and server name for the user I've been having problems with. When I did this (both with his account and with mine), everything worked fine, without any problem.

When I logged back into our domain as the user, and tried to use ShoreTel, I was unable to, so I deleted the two keys mentioned before (HKLM/Shoreline Teleworks/Shoreware Client and HKCU/Software/Shoreline Teleworks), launched ShoreTel again, and tried going in again - this put me right back where I was, where I was freezing trying to contact the server.

After doing this, I tried copying the registry keys from my machine (which I knew worked), logged off and back on, and tried using everything again. I was able to get in, so then I changed my login to his name from mine, and the extension associated with that line to his from mine.

One other thing I had to do was run tpinstall.exe from command line (from another post - with "-i" switched on, I believe. Once this was done, everything seemed to be fine...

At that point, whenever I tried to go into the ShoreTel client on that machine, it looks like I can make outgoing and take incoming calls, but the client seems to be bouncing back and forth between online and offline. I also notice that the instance in the taskbar of ShoreTel has an exclamation point, although I'm still able to send and receive calls.

I'm about a hair away from rebuilding this machine, but I'm really confused as to why:
1) Everything works fine when I'm not logged in to the domain.
2) Everything worked okay briefly for being logged in, but then the settings go from online to offline and back.

If it helps at all, I've tried resetting the user's profile as well.

[Jlorenz]

The GPO for that login is your issue, you proved this by launching the program as local admin and it ran. I do not know what else I can tell, you accept you should do a gpresults on a machine that works and the machine that doesn't and go through the Policies.

Good Luck

[WalkaboutTigger]

I am entirely unclear as to why a user, who is in the local administrators group on a machine would be unable to apply a computer policy any differently than as the local machine administrator.

Can someone point me to an in-depth explanation of this issue?