Replacing a CHR Instance Without Losing Site Identity

This guide covers Replacing a CHR instance. Start with the checks below. Then compare your result with the example before changing a live service. Replacing a virtual router requires a controlled inventory update. Track device identity, licensing, addresses and billing connections instead of treating a new VM as an invisible substitute.

Replacing a CHR instance: practical checks

1. Record the original and replacement instance identifiers.
2. Review CHR licensing procedures and application router records separately.
3. Test one subscriber before retiring the old management entry.

Replacing a CHR instance: a working example

A cloned or rebuilt instance may have different identifiers or addresses. Update the handover so technicians and the billing application are not attempting to manage the retired VM.

First, write down the starting state and the expected result. Then make one controlled change. Next, compare the result with the example above. Finally, record what changed and who should follow up. Keep private account details out of shared notes.

Where LinkDesk fits

LinkDesk is a separate billing application, not a CHR licence or virtual hosting service. A proposed virtual deployment needs a tested application-to-router path, suitable infrastructure and a separate decision about the RouterOS licence.

For the tool or product details behind this guide, see MikroTik CHR licensing guide. The checklist and example above are WayaDesk’s operating guidance.