Known Limitations
Lanview is designed for local Windows device management and administration. This page summarises product boundaries that administrators should understand before planning deployment.
Product scope
Lanview is intended for managing Windows devices through installed Lanview components on a local area network.
Lanview is not a cloud-hosted device management service, a browser-only management portal, a full Mobile Device Management platform, a full vulnerability scanner or a Security Information and Event Management system.
Windows and network dependencies
Some Lanview features depend on Windows and network configuration outside Lanview.
Examples include:
- Windows firewall rules.
- Windows Remote Desktop Protocol availability.
- Wake-on-LAN network support.
- Windows services and event logs.
- Windows Update behaviour.
- Local device permissions and operating system policy.
Lanview can help administer or report on these areas where features exist, but it does not replace the underlying Windows or network requirements.
Installation boundaries
Installer behaviour can vary by component and version. Administrators should review installer documentation before deployment, especially for service startup, network ports, firewall planning and repair or upgrade behaviour.
Inventory and status data
Inventory and status pages show data collected or refreshed by Lanview. They should be treated as management information, not a guarantee of real-time device state in every situation.
Package deployment boundaries
Package validation can identify package issues before deployment, but it does not guarantee installation success on every endpoint. Results should be reviewed after deployment.
Server movement and recovery
Server movement and recovery should be planned carefully. Use documented backup, restore and support guidance for your version instead of improvising file copies or manual state changes.