Sunday, December 16, 2018

Exchange Management Shell or the Exchange Management Console: Connecting to remote server failed with the following error message: The WinRM client received an HTTP status code of 403 from the remote WS-Management service

If the available solutions that you Googled do not solve the problem, you can try the following.

1. Use Internet Explorer to access the same URL as stated which is http://yourIISserver/PowerShell.  It should give more information on why the console is having issues accessing it.

2. Once you know why IIS is rejecting the access, check IIS log in C:\inetpub\logs\LogFiles\ for more detail by looking for the keyword 'PowerShell'

In my case, the issue was because the server was using IPv6 address which is not in my list of allowed IP addresses.



The above error is IIS related. Basically the console has problems accessing PowerShell via IIS. While the cause may not be the same for you, the steps above may shed more light into it.

Tuesday, May 22, 2018

Installing Issabel (Elastix 4) UC PBX on HP ProLiant DL380p Gen8

If you do not already know, Issabel is the continuation of Elastix UC PBX since the latter was taken over by 3CX and has since been killed off. So if you are looking for an upgrade of Elastix 2.5 or the shortlived Elastix 4, then Issabel is what you are looking for

If you have trying to install Issabel on HP Proliant DL380p Gen8 through USB drive and have failed miserably like I did, then you need to install it using iLo

Sometimes the iLo remote control hangs so all you need to do is the start of the installation through iLo, keep that session open by not closing any window etc, then finish up the installation directly on the server itself with a traditional monitor/keyboard etc.


Migrating Openfire server

1. Install new Openfire server on the new server.

2. Start the new Openfire once to ensure it can run

/etc/init.d/openfire start

3. Access the setup page to ensure it can run properly

http://x.x.x.x:9090

4. Shutdown both old and new Openfire server

/etc/init.d/openfire stop

5. Copy over the 3 files/folders from the old server to the new server

scp /opt/openfire/conf/openfire.xml x.x.x.x:/opt/openfire/conf
scp -r /opt/openfire/embedded-db x.x.x.x:/opt/openfire/
scp -r /opt/openfire/resources/security x.x.x.x:/opt/openfire/resources

6. On the new server, make sure the copied files/folders have the correct permissions. If the new server files/folders owners are different from the old one, make sure the permission on the new server is consistent with the owner on the new server by comparing with the permission structure on the old server

eg. chown uuuu:gggg embedded-db

7. Start Openfire on the new server.

8. Run the following command if you face errors.

tail -f /opt/openfire/logs/error.log