Connect. Secure. Manage.
Cisco ISE Upgrade Services
Prepare Cisco ISE upgrades with compatibility checks, configuration protection, maintenance sequencing and post-change authentication tests.
Devices supported
across the UK
Client locations
supported
Traffic handled
at peak time
Average
response time
Average response is not a resolution time or a contractual guarantee. Support scope and response commitments are agreed for each engagement.
Cisco ISE upgrade services plan changes to a platform that users may need just to reach the network. We check node roles, endpoints and network devices before choosing the supported upgrade path. Recovery material is prepared in advance. After the change, we test real access as well as the health of the ISE platform.
Defined trust
Make access boundaries explicit rather than relying on an assumed internal network.
Controlled access
Connect identity, policy and network enforcement to the services people actually use.
Evidence for change
Test the intended security outcome and retain useful operational records.
Establish the reason and target
An upgrade may address a security advisory, a support deadline, a platform need or a feature needed by the customer. We identify that reason before selecting a target release. The newest available software is not automatically the appropriate destination for every estate; compatibility and support needs still need checking.
We record the current release, patches, node roles, licences and integrations. The assessment includes supported compute resources, endpoint components and any external systems that rely on ISE interfaces. A change affecting certificate handling, client provisioning or an integration may require coordination outside the network team even when the server upgrade itself appears straightforward.
Standards & partnerships
Confidence in the team behind your network.
Cisco Partner
Cisco Meraki
Cyber Essentials
Cyber Essentials PlusMCI Network Services is operated by Proxar Ltd. Certifications apply to the certified legal entity and the scope of its certificates. View accreditation information
Verify the supported upgrade path
The source and target versions determine the permitted sequence and prerequisites. We consult the relevant Cisco guidance and identify any intermediate steps, resource changes or migration needs. The project does not assume that every rollout can be upgraded directly or that an appliance replacement follows the same process as a software patch.
Readiness checks also examine current health. Replication problems, failed backups, inconsistent certificates or storage pressure should be understood before the upgrade begins. Otherwise the change can expose a current weakness and make recovery more complicated. We separate prerequisite remediation from the upgrade window so that the customer can approve both clearly.
A useful starting point
Not sure where to start?
Bring the requirement. We will help you define the engineering work.
Prepare usable recovery material
We find the setup, service data, certificates and keys that require protection, together with the supported backup and restore procedures. The recovery plan states which material is included in each backup and which must be handled separately. Credentials and encryption keys are kept through an approved secure process rather than embedded in a change document.
Rollback is assessed honestly. A failed upgrade may require restoration or rebuilding rather than a simple downgrade command. We set out the conditions for stopping, the recovery location and the likely service impact of the available route. The customer should know those boundaries before agreeing the window, especially when authentication supports many sites.
Different environments. The same care.
Built around the work
your network supports.
Finance, banking and the wider private sector. We start with the systems and people that depend on your connections.
Finance & banking
Market-data paths, routing and provider coordination on clients’ behalf.
Financial-market services ↗Offices & multi-site teams
Reliable access between people, workplaces and business applications.
Office network design ↗Data centres & cloud
Network boundaries, workload connections and operational ownership.
Data centre networks ↗Sequence nodes and access dependencies
The node order follows the supported procedure for the actual rollout. We consider policy-service capacity while nodes are unavailable and check how switches and wireless systems choose an alternate server. The presence of a secondary node is not enough if the access devices never use it or the remaining capacity is inadequate.
Changes to administration and monitoring roles are planned separately from client authentication checks. We check which functions may be unavailable at each stage and who communicates that condition. A pause between stages allows the team to confirm the expected state instead of continuing automatically after the first apparent success.
Test a meaningful access sample
Post-change validation includes representative wired and wireless authentications, the intended authorisation results and any important guest or admin workflows. We use a test matrix prepared before the window so that the same functions can be compared before and after the upgrade.
Certificate-based access, non-supplicant exceptions and posture workflows may reveal issues that a simple username test misses. We also check that logging and operational views remain useful. An authentication service that processes requests but no longer supplies expected evidence to support staff is not fully handed back to normal operation.
Observe the first operating period
Some problems appear only when users return, certificates renew or scheduled jobs run. We agree a post-change observation period and the measures to review, such as failures by endpoint type or an unusual increase in policy exceptions. The customer receives an escalation route for issues attributable to the change.
Temporary workarounds are recorded with an owner and removal criteria. We do not leave broad access exceptions in place merely to make the upgrade appear successful. Where a client or integration requires separate remediation, the report identifies that dependency and distinguishes it from the completed server work.
Close the change with updated records
The final package records versions, completed steps, test outcomes, remaining limitations and the status of recovery material. Documentation and monitoring references are updated to reflect the new rollout. MCI can provide a single upgrade engagement or incorporate lifecycle work into an agreed Cisco ISE support scope, with responsibility for future advisories, patches and compatibility reviews stated clearly.
Technical references
- Cisco ISE support, compatibility and upgrade documentation — Cisco / Cisco Meraki
Talk to a specialist
What does your network need next?
Tell us what you are planning, changing or trying to improve. We will help define a practical next step and the engineering scope.
+44 203 196 6566Choose option 1
sales@proxar.co.ukUK-wide service.
Most of our engineers are based in Kent, with a focus on London, Sussex, Essex and Berkshire.
Existing customers should use their agreed support and escalation channels. This form is for service enquiries, not a monitored emergency ticket.
Tell us what you need.
A short outline is enough. Please do not include passwords or sensitive network details.
Thank you. Your enquiry has been submitted.
Please check your name, email and message, then try again.
Your form session expired. Please try again.
Please wait a minute before sending another enquiry.
We could not submit your enquiry. Please call or email us instead.