Services

Windows 7 or Windows 10 and Windows Server
Corporate Build Development

Moving between version of Windows is much easier if some standards are introduced.

Before you can decide what is needed in the new operating system image you must first understand the existing and future requirements.

The process is similar for desktop and server operating systems though more attention to detail may been needed if you want to ensure the users have the smoothest transition between environments

The migration consideration and process is similar for desktop and server operating systems though more attention to detail may been needed if you want to ensure the users have the smoothest transition between environments

A migration project can be a great excuse to rationalise and tidy up the applications and settings in use and also to review licensing

Click the boxes for more information

  • 1

    Discover and Understand

    The first phase is always to discover and understand the existing environment.

    Key Steps:

    • Investigation
      • Which policy, security and other standards apply?
      • What is the current hardware platform, is it supported?
      • Which applications are currently actively in use
        (as opposed to just installed)?
      • Which applications are required and of those which are key?
      • What is the position with licensing, are the applications adequately
        or even over licensed?
      • Upgrade or fresh installation?
      • 64 bit or 32 bit and which edition?
    • Audit of Requirements
      • A full application audit, either automated and/or manual will help to define the requirements
      • Hardware audits will identify the target environment and devices.
    • Compatibility Checks
      • Any required existing or future applications will need to be checked for compatibility with the new version of Windows. Any applications which are not compatible will need a plan of action, for example isolation or virtualisation may be options for incompatible applications

    How KN3 Can Assist With This Phase...

    • Hardware Auditing
    • Application Auditing
  • 2

    Design and Implement

    The second phase is to design, prove and implement a solution.

    Key Steps:

    • Standards Definition
      • Standards for the installation, security and settings need to be defined and documented
    • Automation
      • The installation should be completely automated where possible to avoid human error
      • The upgrade, migration and/or installation process must be thoroughly tested and piloted

    How KN3 Can Assist With This Phase...

  • 3

    Training and Support

    Phase three ensures that your new solution is more easily adopted and supported.

    Key Steps:

    • Training
      • Support personnel will need to be trained on the desktop standards
      • Support personnel may need to be trained on packaging applications to maintain any new application process
      • Support personnel will require training on any new software distribution system
      • End users may need training on the new version of Windows

    How KN3 Can Assist With This Phase...