In early 2021 Ivanti started moving their Ivanti Cloud Customers for Ivanti Neurons, Ivanti Service Manager (HEAT ITSM), and Ivanti Asset Manager (ITAM) to Azure Data Centers. The new data centers are below:
FFZ Frankfurt, Germany (Europe East)
IRZ Ireland (Europe West)
NSZ New South Wales, Australia
TTZ Toronto (Canada)
NVZ North Virginia (Americas East)
WAZ Washington (Americas West)
Click your data centre to see Ivanti Maintenance Notifications!
Upcoming Data Centre Moves:
Oregon (ORE) Scheduled to be moved August 2021 to Washington (WAZ) and North Virginia (NVZ).
If you have any questions about your scheduled date or the necessary changes for this move, please consult ISM/IAM Cloud Initiative 2021 FAQ Guide or contact us at SaasORE@ivanti.com.
All VPN customers, please check for communication from VPNORE@ivanti.com to discuss the necessary VPN related changes.
For all other questions, please contact Ivanti Global Support.
The Ivanti Status Cloud Page is a great way of staying on top of notifications. Only snag is that there isn’t an easy way to see landscape specific updates for your Data Centre.
For example if your Ivanti Cloud tenant is in Frankfurt Landscape (FFZ), you still see all Landscape on the status page. Sure you could subscribe to email alerts for your landscape only, but lets face it, email isn’t a productivity tool, so I’ve gone ahead and created status pages that filter the rss feed, for Frankfurt, Australia APAC, London UK, Ireland, Toronto Canada, North Virginia USA East, and Washington USA West
For Ivanti Maintenance Notifications specific to your tenants click and book mark the following:
A very frequently asked question when implementing Ivanti Service Manager (HEAT) evolves around the “Waiting for Resolution” Incident Status. What is its significance, should it be used, and how does it effect SLAs?
The “Waiting for Resolution” Status is typically used when a break/fix (Incident) has been completed but the ticket hasn’t been updated yet.
For example if there is a P1 Incident that has been resolved, setting the Status to “Waiting for Resolution” may prove to be rather useful to stop the SLA clock while gathering all incident resolution details from the SDAs and Task Owners, without getting penalized.
Remember that the SLA Clock is driven by the Incident Status and Waiting for Resolution pauses the SLA clock.