Skip to content
Endpoint security renewing? Compare Falcon Complete
Menu

Enterprise engineering

Get the Microsoft foundations right before you build anything on top of them.

Kritical works on Windows infrastructure and the services business applications depend on, including Active Directory, hybrid identity and platform migration. Engage us for an assessment, a defined change, or help resolving a technical issue that's been quietly costing you for months.

What you get: the dependency map behind the symptom.

A server issue may depend on name resolution, time, authentication, certificates, networking or application assumptions. We scope an assessment that follows those dependencies rather than treating each symptom in isolation, establishing the current configuration, service owners and recent changes before choosing a remediation path. The administrators and application owners who will verify the result inherit the operating procedures, not a black box.

Network cabling / patch panel room

Directory and platform changes, planned around what breaks.

Active Directory, Group Policy and hybrid identity changes can affect users and applications across an organisation. We define the affected identities, trust relationships, service accounts and authentication paths before implementation. Migration planning addresses coexistence, access continuity and the work required from application owners, including dependencies that aren't documented in the directory itself.

Why Kritical for Windows and Active Directory.

A project can include server lifecycle work, hardening, configuration assessment or repeatable administration. We agree the desired state, approved exceptions and validation method.

Continuity planned around your account

We aim to provide continuity through a consistent lead or delivery group where the agreed scope and service model support it. Your proposal sets out the contact model, cover and handover arrangements that apply.

Automation that's reviewable, not a black box

Change is made rerunnable where appropriate, with credentials handled through the agreed access model and output that helps an operator understand partial failure.

Verification against the services people use

Not just a server that starts. We test authentication, application access, administration and the relevant recovery scenarios.

Citrix and application publishing.

Published applications sit on top of directory, name resolution, licensing and network paths, so we look at the whole chain when users say the app is slow or won't open.

Citrix environments

Design, migration and fault-finding for Citrix delivery, from the published application through to the servers beneath it.

Application publishing for remote and multi-site users

Publishing applications to users at other sites and remote workers.

How it's priced, and what handover looks like.

A scoped assessment or change is quoted in writing before work starts. Handover can include configuration records, change scripts, operating instructions and unresolved dependencies. We clarify who maintains the environment afterwards and how vendor support, backup and incident response fit into that responsibility.

  1. First call

    We confirm which services and symptoms are in scope and what evidence we need to start tracing dependencies.

  2. The agreed first phase

    A scoped assessment covering the dependency map and a recommended remediation or migration path, priced in writing.

  3. Get a quote

    Send the systems and constraints involved and we quote the work.

Explore the relevant technologies.

Use these guides to see which technologies can help with the job in front of you.

Microsoft

Microsoft

Workplace, identity, cloud and business applications, connected to a clear implementation or support requirement.

Questions before you enquire

Can you work on an existing Active Directory environment?

Yes. Assessment and remediation can be scoped around the current environment, including hybrid dependencies and application authentication.

Can you help with a separation or migration?

Yes. The scope needs to establish identity ownership, coexistence, application dependencies, access requirements and an agreed cutover and recovery approach.

Do you cover Microsoft 365 as well?

Describe the cloud and on-premises services involved. We can identify the Microsoft 365 and identity work needed and include the relevant interfaces in the scope.

What if the problem has already been misdiagnosed once?

Common, and part of why the assessment starts from dependencies rather than the last theory. We re-establish the baseline rather than assuming the previous diagnosis was right.

Will this disrupt users during business hours?

The plan sets out expected interruptions and a maintenance window before implementation is approved. Nothing changes in production without that agreed first.

Can you review our environment without making any changes first?

Yes. An assessment can be scoped purely as read-only discovery: current configuration, service owners, recent changes and dependency mapping, with no change made until a remediation plan is agreed separately.

What about legacy servers we can't easily replace?

We assess what's supportable, what needs isolation or compensating controls, and what needs replacement, rather than defaulting to a wholesale rebuild.

Let’s define the next step.

Tell us what you want to achieve, what you have today and when it matters.

Discuss your Microsoft infrastructure