Mail routing using Gmail Gsuite Split delivery method

How to achieve split delivery using G suite ( gmail ) “Route Services”

If your organization uses an external mail server for storage and message delivery, such as a Microsoft®Exchange server, incoming messages are first processed by the Gmail server, such as filtering for spam, and then routed to the external server. You use the split delivery method to route the messages to either the Gmail server or an external server. You use the dual delivery method to route the messages to both the Gmail server and an external server.

You can also route incoming messages to a catch-all address, to additional recipients, and to a non-Gmail mailbox. follow the link for “howto”




How to repair Exchange 2010 database edb file

Exchange 2010 unmount database repair procedure:

Command to soft repair the Exchange EDB (database file)
# eseutil /mh   .\exchange1.edb

Command to hard repair edb file
# eseutil /m /l /d  .\exchange1.edb

full content of above site:

Resolve Exchange 2010 Error Unable to Mount Database

To deal with this Exchange 2010 issue: unable to mount the database, it is important to first understand the role of Transaction logs.

A transaction log is the life-and-blood for an Exchange Server, helping it retain smooth functioning on the server. Each and every transaction made to the server is being written in these log files, which are then committed to the database. Until the transaction is not saved in the database, it remains the system memory and the transaction logs.

If any crash occurs during this event, then you lose the content from the memory during the reboot, because it was not completely saved on to the exchange database files. This is why, transaction logs are the robust recovery mechanism to safely restore the data to an Exchange database in a consistent state.

This below mentioned error message is displayed in Exchange 2010, when you are unable to mount a database from a backup:

Error Message:
Exchange is unable to mount the database that you specified. Specified database: d1cdba46-6f79-46f2- ba14-3ae2fa8aad43; Error code: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005,ec=-2147467259)


Microsoft has provided Eseutil utility to verify whether or not the database is in clean shutdown state. If isn’t in a clean shutdown state, then this inbuilt utility may help you to fix up the issues and bring the database into consistency. And if the data is in consistent state, then using the below mentioned resolution, you can restore the data successfully from the backup.



Removal of log file is one of the common reasons, due to which the database may fail to mount. To resolve the issues, it is important to first perform a consistency check.


Verify and Repair Inconsistent Database Using Soft Repair

Eseutil tool can be of great help in performing soft recovery. This method is useful to re-mount database after an abrupt stop.

The user will now be able to mount the database successfully. However, if not then verify the consistency of transaction logs.

Verify and Repair Database Logs Using Hard Repair

Eseutil tool is even helpful in performing hard repair recovery to test the database for any damaged pages. If there are any, then the tool will delete them. This recovery method uses Restore mode (/c) in Eseutil tool to mount a database from online backup.

However, if you are still unable to mount the database, then try using a reliable third-party Exchange Server Recovery tool to efficiently restore data in any condition of damage – even where Eseutil tool fails to deliver the desired result. Kernel for Exchange Server is an advanced recovery tool to repair corrupt Exchange database files, without requiring log files or Exchange services. EDB to PST converter tool even allows you to restore EDB files directly to live Exchange Server and to Office 365 mailbox.



VirtualBox installation on Ubuntu droplet of DigitalOcean

# sudo apt-get install dkms
#wget -q -O- | sudo apt-key add –
#sudo sh -c ‘echo “deb trusty contrib” >> /etc/apt/sources.list.d/virtualbox.list’
#sudo apt-get install virtualbox-4.3

#apt-get install xfce4 xfce4-goodies tightvncserver


#/usr/bin/vncserver -depth 16 -geometry 1024×768 :0 < to active machine use that <<< DOWNLOAD THIS FILE IN YOUR WINDOWS DESKTOP TO REMOTE ACCESS

NOW Running<< this ip for VPS ::5900 << this port to access

RDP licensing server enable procedure

1. The graphical management tools for RDS Session Host Management are disabled when not oprerating a Domain (why?). The fall back is configuration via group policy:

Local Computer Policy -> Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Licensing
Use the specified RD license servers = <server IP>
Set the Remote Desktop licensing mode = Per User

This got us to a stage where Licensing diagnostics looked good and no related local errors showed up in the server logs but remote sessions were still refused, leading to…

2.  Force-removing the RDS licensing time-bomb registry entry:

computer\hkey_local_machine\system\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod

RegEdit alone couldn’t do it. It had to actually be run under highest privileges with the help of Sysinternals: psexec -s -i regedit.exe

After another reboot things seem to be working now. However, I am somewhat suspicious that this only hacked the time bomb but did not actually activate the CAL licenses (none show used in RD License Manager).
Anyway, hope this helps someone not to waste hours.