How to upgrade from 'classic' (all versions) to the Azure-based platform (estimate 2-4 hrs.) - Ready for Office 365/Exch on prem/G Suite

Announcing new options for the Azure-based email signature platform and 'classic' end of support. The 'classic' version got the end of support by 1 Jan 2019. It's time to upgrade. The Azure-based platform is ready for Office 365, Exchange on-premises and G Suite environments. It’s incredible how much and how rapidly technology evolves. We want to thank our 'classic' customers, and we will make sure we support our customers in getting ready for the future and taking maximum advantage of today’s technologies.

You will get a smooth transition from 'classic' to the Azure-based platform. 

• For instance, it's possible to run the Azure-based platform and 'classic' concurrently as you onboard pilot users and prepare for launch.
• A Quick Video Walk-through.
• Explore the Azure-based platform.

In general, the switch to the Azure-based platform is a move toward a less technical setup and a more intuitive browser-based admin interface. For instance, the Azure-based platform includes role-based access control capability which means that IT usually is only involved during the initial setup. Updating email signatures/campaigns is a tasked the marketing/communications teams (no workload in IT).

eMailSignature is re-branded as Xink (as we as company re-branded back in 2014)

You no longer have to maintain everything on premises. Many clients have no installation on servers when upgrading to the latest Azure-based platform.

• The Azure-based platform replaces the 'classic' management console. 
• Your SQL database continues if you want to manage OWA/Mobile email signature with Exchange Server on premises. 
• Sign.exe is replaced by the Xink client which updates Outlook (Win/Mac) and Apple Mail (Mac) during office hours (not only during domain login). Alternatively, you can also apply the signature at the server with Office 365 environment.
• Your company login replace your license key (you can assign a login to the responsible department using role-based access control).

The upgrade is included with current maintenance/support agreement

• You are also licensed to get OWA/Mobile email signature updated with both Exchange Server on-premises and with Exchange online (Office 365). 
• A quick comparison between 'classic' and the Azure-based platform.

1. How to request your login

• Keep 'classic' running (it can run together with the Azure-based platform as you add pilot users).
• Schedule intro meeting or submit a support ticket and request your Xink login.

2. How to upload or copy/paste templates

• We recommend uploading signatures as it will automatically upgrade your HTML and include your images - Learn how.
• Alternatively, open the Azure-based platform and copy templates (copy from HTML source).
  Login to Xink > Signatures menu, click signature, click Source button and paste HTML source.
• Now insert fields from the drop-down (you can rename the standard fields if you prefer).

3. How to add employees

• Learn the different ways to add users, e.g. from Active Directory.

4. How to assign email signatures

• How to assign email signatures to everyone, groups, and individuals.
  
  If your PAs are sending on behalf of the partners/managers:
• How to share other users' default signatures.

5. How to update Outlook (desktop)  

• Outlook (Win/Mac/Citrix/RDS) deployment.

6. How to update mobile devices 

• With Office 365.
• With Exchange Server on premises (if already set up in 'classic,' you reuse your SQL database).

7. How to update Outlook on the web (OWA)

• With Office 365.
• With Exchange Server on premises (you use your existing SQL database).

8. How to stop 'classic' updates

• Stop executing Sign.exe during domain login (typically found in NETLOGON share).
• When you move to Office 365, you can also uninstall eMailSignature (found in add/remove programs) and delete the SQL database (default DB name is eMailSignature).

FAQs when upgrading