Cross-Platform OS Deployment via Protocol Translation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

System administrators face challenges in installing MAC OS X on MAC computers using Windows servers, as existing solutions are not compatible due to differences in packaging formats and data transmission protocols between Windows' Preboot Execution Environment (PXE) and Apple's NetBoot technology.

Innovation Solution

A method is developed to deploy a native OS image on a target client using a non-native distribution server, where the OS image is converted and packaged into a non-native format, unpacked, and deployed using System Imaging Utility, with SCCM Proxy creating an OS image package and task sequence, allowing deployment via NetBoot service on a Windows server.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If Windows server with PXE technology is used to deploy OS, then Windows-based deployment infrastructure is available, but MAC OS X cannot be installed on MAC computers due to protocol incompatibility

Engineering Contradiction:
Improvecross-platform deployment capabilityVSAvoiddeployment compatibility
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a protocol translation layer that acts as an intermediary between Windows PXE infrastructure and Apple NetBoot requirements. This translation layer converts PXE protocol communications into NetBoot-compatible formats, enabling Windows servers to deploy MAC OS X images to MAC clients without requiring native Apple hardware or software.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent transforms the deployment protocol parameters by converting data packets between PXE and NetBoot formats. This includes changing protocol identifiers, packet structures, and communication sequences to match NetBoot specifications while maintaining the underlying Windows server infrastructure.

Inventive Principle:
Principle #35Parameter changes

2Ease of manufacture

If Apple NetBoot utility is used to install MAC OS X, then native MAC deployment is achieved, but Apple hardware and software must be available which are not always accessible

Engineering Contradiction:
Improvedeployment accessibilityVSAvoiddeployment infrastructure requirements
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent makes the Windows server perform multiple functions: it serves both as a PXE boot server for Windows clients and as a NetBoot server for MAC clients. This universal deployment infrastructure eliminates the need for separate Apple hardware while maintaining compatibility with both platforms.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Productivity

If OS image is converted to non-native format for deployment, then network delivery is enabled across platforms, but conversion and packaging steps are required

Engineering Contradiction:
Improvenetwork delivery efficiencyVSAvoidimage processing complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent performs OS image conversion and packaging into NetBoot format in advance, before deployment. This preliminary processing creates ready-to-deploy image packages that can be efficiently distributed over the network without requiring real-time conversion during the actual deployment process.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9910678B1NetBoot for installation of a non-native OS on a target host
Publication Date: 2018.03.06 PARALLELS INT GMBH
  • US9910678B1 patent drawing
  • US9910678B1 patent drawing
  • US9910678B1 patent drawing

AI summary

A method for installation of a native OS on a host using non-native utilities. A native OS image is deployed on a native target client system using a non-native distribution server. The OS image is converted and packaged into a non-native format and provided to the target client. The OS image is unpacked and de-converted back to a native format and deployed on the target client. The client agent runs System Imaging Utility to acquire the OS image from the reference partition. The created OS image is pushed to the non-native file sharing system, and then the SCCM Proxy is asked to create an OS image package and a task sequence in the SCCM for this package. When the OS image is placed into the SCCM, the client agent reboots back to the reference partition.