This document explains how to prepare for, use, and maintain the Enterprise system.

User Information

Overview

• The Enterprise kiosk is an industrial computer housed in a protective enclosure next to the pipe-cutting machine.

• As of 2026, Enterprise runs Windows 11 Professional.

• Enterprise is a Windows application that runs on the kiosk computer. The computer uses an Intel i7 or better processor.

• The Enterprise application enables you to:

  • Design parts or import them from supported CAD systems. Contact Enterprise for the current list of supported and planned connections.

  • Send designs to the machine.

  • Schedule work as Scheduled Parts.

  • Assess cut times and pipe use for a job or other group of work.

  • Nest Scheduled Parts on pipes.

  • Load nested pipes to the pipe-cutting machine.

  • Automatically track cut parts through the machine.

• The Enterprise application uses Microsoft SQL Server to store pipe designs, planning, nesting, and cut-status information.

  • SQL Server provides advantages over traditional file storage. You will learn about these advantages as you learn the system.

• If you purchased one or more remote licenses, you can run the application from computers on your company LAN, away from the kiosk. Remote users cannot load the machine, change machine settings, clear the machine, or otherwise control it.

General layout of a complete system

This diagram shows the most common configuration for using Enterprise.

A connection must be established between the Enterprise computer and the machine computer. Enterprise uses this connection to write the files required to cut parts to a shared folder. The computers can use a direct Ethernet connection or a network share for which both computers have read and write access.

Some machines use instruction files such as G-code or JSON files. Others connect directly to the machine through supported protocols.

Enterprise provides two Ethernet ports: one on the side of the protected enclosure and one on the USB-C hub. Use one port to connect Enterprise to the company network and the other to connect Enterprise to the plasma cutter.

Getting Started Sequence

Before the kiosk arrives

You cannot install or run the application without access to the SQL Server on the kiosk. Complete these steps before the kiosk arrives:

• Give this document to your IT department and encourage them to read sections 1 and 2.

• Drop a CAT5/6 line to where the Enterprise kiosk is going to be installed.

Kiosk Arrival

Once your kiosk is online, you can begin using it before the pipe-cutting machine is fully set up and running.

• Plug it in and start it up. You can run it in your office or wherever.

• Discuss joining the kiosk computer to your domain with your IT department.

• If you licensed remote seats,

  • Enterprise must be on the domain. This process is discussed in section 2.

  • You can install the Enterprise app on your own computer and run it from there.

• Once your IT department allows the kiosk to be connected to the internet, Enterprise can update and support the system as needed. This is especially useful during the first month or so of starting up.

• If you licensed importers, you can also work with Enterprise Support to optimize them.

Ongoing maintenance after kiosk setup

• Enterprise will advise you when new software releases are available.

• If needed, you can coordinate with Enterprise on the best time to update the software (so you have no downtime). It can typically be done in the evening after work.

• Whenever a new version is installed on the server, there may be new features. You will find these in new training videos that are built into the system.

• If you have remote licenses, those users will need to update their revisions as well.

Training

• The app includes training videos on the Training tab of the main window.

• Enterprise provides one or two initial training sessions.

  • Training is most effective when the machine is operational so users can immediately apply what they learn.

  • A Enterprise trainer will schedule an online meeting with you. Reserve a meeting room and include all users, especially machine operators.

  • Training typically takes two to four hours and can be divided into multiple sessions. Users should become familiar with the system for several days before requesting additional training.

    • A follow-up session is often useful about two weeks later, after users are more familiar with the system.

Remote programming from another computer

• With a remote license, you can run the Enterprise application in the same way as at the kiosk, except that you cannot load or otherwise control the machine.

  • Talk to your IT person about getting set up for remote use.

• Whenever the kiosk system is updated, install the new version on each remote computer.

• You can install the Enterprise application on multiple computers connected to the same LAN as the PYPESERVER kiosk. Concurrent use is limited to the number of remote licenses you purchased. The kiosk license is permanent and cannot be checked out elsewhere.

Installing Enterprise on a remote computer

Your computer must be on the same LAN as the PYPESERVER computer so it can reach the database and software license.

• In File Explorer, verify that Enterprise appears on your LAN.

• If you cannot see \\PYPESERVER on the LAN, check the following:

  • PYPESERVER is connected to the LAN.

  • PYPESERVER has been joined to the domain, if required by your network.

  • The PYPESERVER firewall permits the required connections. Domain-joining tools may enable the firewall automatically.

  • Contact your IT department or see the firewall section for more information.

• Navigate to the latest release folder at \\PYPESERVER\PypeServer Staging.

• Copy PypeServerAppSetup.exe from that folder to your computer.

• Double-click PypeServerAppSetup.exe to install the application. The application will look for \\PYPESERVER to find the SQL Server databases and licenses it requires.

  • If your company renamed \\PYPESERVER, you will be prompted to locate the SQL Server through a dialog. You need to locate the SQL Server only once.

Help with remote installation

See section Online help using TeamViewer.

Reporting

Enterprise contains canned reports for Part and Pipe Cut Lists, Metal Burned, and Assembly. The built-in report designer can be used to customize these reports and create new ones.

You can connect Microsoft Excel to the Enterprise SQL database to create custom reports. A training video explains how to create a read-only connection.

• The tutorial shows how to connect Excel to the Enterprise data source in read-only mode.

• After connecting, users can build reports in Excel as needed.

• Users can connect directly to Parts, Scheduled Parts, and Pipes data.

• Contact your IT department for help using data exposed through a SQL view.

You can also export the current Enterprise grid view to Excel. The export contains only visible columns and rows.

Getting help

If something is not working correctly or seems unnecessarily difficult, contact us:

• Phone: 425-333-7736 (USA); support hours are 9:00 a.m. to 5:00 p.m. PT.

• Email: support@pypeserver.com

• Or you can open a support ticket at: https://pypeserver.atlassian.net/servicedesk/customer/portal/1

Online help using TeamViewer:

If you need online support for your remote seat installation, then at your remote seat, install either TeamViewer QuickSupport, or TeamViewer Host. You can get this at TeamViewer (https://www.teamviewer.com/en-us/download/windows/). Scroll down to find QuickSupport or Host. Once installed, you can provide the connection ID and password to Enterprise so we can join you on your computer to provide support.

Information to provide

When contacting Enterprise for help, provide the following information so we can respond quickly:

• Your name

• Company name

• Email address and phone number

• If applicable:

  • The Part ID, Scheduled Part ID, or Pipe ID associated with the problem

  • A description of the problem

  • The steps that led to the problem

• If the problem is a bad cut, take pictures and email them to support@pypeserver.com.

Leave the kiosk online so Enterprise Support can investigate.

CAD connectivity

• Enterprise supports connections to outputs and REST/HTTP services from numerous CAD systems. Contact Enterprise to discuss solutions for your CAD-to-machine workflow.

IT Information

General Topology

This diagram expands the topology shown in section 1. It shows data moving from CAD systems to multiple cutting machines.

Enterprise computer overview

Enterprise is a Windows .NET application. Multiple instances can run on computers within a LAN. Because the application frequently exchanges data with SQL Server, running it outside the LAN can create performance problems. Contact Enterprise to discuss specific scenarios.

Out of the box:

• As of 2026, the Enterprise kiosk includes an Intel i7 or better computer running Windows 11 Professional with standard network adapters.

• Software:

  • Windows 11 Professional

  • .NET Framework 4.8

  • SQL Server 2022 Express. SQL Server 2019 and SQL Server 2017 remain supported for legacy installations.

• The kiosk computer is named PYPESERVER, although you can rename it if necessary. If you rename it, direct each client Enterprise app to the new computer name once.

• The local user account is MachineOp. It has local administrator rights. Leave this account on the system for Enterprise Support.

• You can add other local or domain users to the computer as needed.

Kiosk enclosure and hardware

• Enclosure:

  • The kiosk computer is housed in a dust-sealed enclosure. Operating the computer with the enclosure open will significantly shorten hardware life.

• Monitor:

  • The monitor has a minimum resolution of 1080p. It uses standard VESA mounts and can be replaced with an HDMI monitor. The system supports 4K monitors.

• Keyboard and Mouse:

  • The kiosk includes a standard keyboard and mouse. You can replace them with preferred models.

• The kiosk hardware is covered by a one-year warranty.

The licensing system

Enterprise uses the CodeMeter security system from WIBU. As of 2026, the supported runtime version is CodeMeter 8.40. Licenses are stored in a file-based container or a hardware dongle on the Enterprise kiosk.

• The CodeMeter license server is a WIBU service that runs on the operating system where the license container or dongle is located.

  • It is preinstalled on the kiosk.

• Remote use:

  • A remote seat checks out its license from the kiosk license server.

  • The application requires continuous connections to SQL Server and the CodeMeter license server. Offline operation, caching, and proxy operation are not supported.

• You can install the remote application in as many locations as you want.

Enterprise on other computers

• The Enterprise client app is the same application that runs on the kiosk.

• For remote use, the app prevents users from loading the machine or changing machine settings.

• To run Enterprise on other computers on the network, join the PYPESERVER computer to your local domain.

• After the PYPESERVER computer is joined to the domain and the required firewall rules are configured, it should be visible on the network.

• Once it is visible, copy PypeServerAppSetup.exe from the kiosk to each computer on which you want to run the application.

  • PypeServerAppSetup.exe is located at \\PYPESERVER\PypeServer Staging.

  • You can install the application on any number of computers, but the number of concurrently running instances cannot exceed the number of remote licenses.

  • Remote licenses are checked out from the Enterprise kiosk, so remote computers must remain connected to it through the LAN.

  • The client app does not cache Enterprise part or cut data locally. Keep the Enterprise kiosk computer running whenever remote users are using Enterprise.

  • The kiosk license is fixed to the kiosk, so remote users cannot check it out accidentally.

Remote system requirements

• Windows 11 Professional

• Recommended hardware:

  • Intel i7 recommended; Intel i5 acceptable. Intel i3 performance may be inadequate.

  • Use a solid-state drive for the operating system to improve overall performance.

    • Solid-state drives can fail without warning. Store important user data in a managed backup location.

  • Use 802.11ac or better network connectivity with latency below 10 ms. A wired connection is preferred for production use.

Running Enterprise remotely over a WAN or VPN

Enterprise generally does not perform acceptably over high-latency WAN or VPN connections. Latency, rather than bandwidth, is the limiting factor because the application performs many small, incremental exchanges with SQL Server.

Why latency matters

Streaming video sends data primarily in one direction. Interactive applications may issue hundreds of small requests to a server. At 1 ms of LAN latency, 1,000 sequential requests add about one second of delay. At 100 ms of VPN latency, the same requests can add about 100 seconds. Even 50 to 100 requests can add 5 to 10 seconds.

One solution for high-latency connections

Place a dedicated computer on the same low-latency network as the Enterprise computer, and allow remote users to access it through an IT-approved remote-access tool. This configuration is generally easier to maintain and performs more reliably than running Enterprise directly across a high-latency connection.

License not found

Refer to The licensing system for information about license allocation.

If Enterprise displays a license-not-found message on a remote computer, contact Enterprise Support or check the following probable causes:

1. For a new installation in which all software is current:

   1. Confirm that the PYPESERVER computer appears in the network list.

   2. Configure the firewalls on both computers to allow the CodeMeter license server. See Firewalls and security.

2. The message appears when all remote licenses are checked out by other users.

   1. In rare cases, a Enterprise process may remain running after its window closes. Check the last computer that ran the application and end the remaining process.

   2. To see which computers have licenses checked out, run Enterprise Licenses from the Enterprise folder on the Start menu.

3. A remote license may have expired. Enterprise reports this condition during startup.

4. Confirm that the CodeMeter license dongle or file-based container is available to the kiosk and that its host service is running.

5. In CodeMeter 8.40, open CodeMeter Control Center and configure the license server by computer name. If name resolution is unavailable, use the server's IPv4 address.

6. Update the remote Enterprise application if it uses an older CodeMeter access component.

7. If the CodeMeter license server is stopped on the PYPESERVER kiosk, open CodeMeter Control Center and start the CodeMeter service.

Performance reliability and support

Windows Update

Windows Update is disabled by default on the delivered Enterprise computer so the customer's IT team can configure and manage its own update policies.

IT teams may apply Windows updates according to company policy. Schedule updates during planned maintenance, verify that current backups are available, and test Enterprise after updating. As of 2026, delivered systems include an Original Config restore point for initial recovery.

Firewalls and security

• Firewalls on Enterprise kiosks are off by default.

• The PypeServerAdmin and PypeServerDB SQL databases contain the primary sensitive data on a Enterprise kiosk.

• Troubleshooting notes:

  • When first connecting remote seats, please turn off the Kiosk firewall. Adding firewall features beforehand makes debugging difficult.

• TeamViewer:

  • Enterprise uses TeamViewer for remote support on the kiosk (and for users we can start remote Teamviewer sessions). If you're running any sort of network traffic sniffer, you might see this, though it is unlikely to trigger a false-positive, as TeamViewer is well known.

  • We recommend you leave unattended access enabled at the Kiosk while it is getting set up. After things stabilize, you can shut it off as desired.

    • We ask that you DO NOT uninstall TeamViewer-just shut off. That way if you need support later, you can easily enable it.

Configuring firewall access

If the Enterprise kiosk uses an active firewall, configure the following items:

Enable TCP IP

TCP/IP is enabled by default on delivered systems.

In SQL Server Configuration Manager, enable TCP/IP.

Restart the SQL Server service after changing this setting.

Allow remote connections

Remote connections are enabled by default on delivered systems.

In SQL Server Management Studio, open the server properties and enable Allow remote connections to this server.

Create three inbound rules

These rules are not preconfigured by Enterprise.

SQL Server 2022 Express and named instances can use dynamic ports. When dynamic ports are enabled, allow the SQL Server application through the firewall instead of relying only on a fixed database port. SQL Server 2019 and SQL Server 2017 remain supported for legacy installations.

In Windows Defender Firewall with Advanced Security, create two inbound application rules and one inbound port rule for the following:

• SQL Server

  • C:\Program Files\Microsoft SQL Server\MSSQL16.PYPESERVER\MSSQL\Binn\Sqlservr.exe

  • The instance folder may differ if SQL Server was installed with a different instance name or location.

• SQL Server Browser

  • C:\Program Files (x86)\Microsoft SQL Server\90\Shared\sqlbrowser.exe

• Distributed Transaction Coordinator service

  • This service uses the RPC port 135 for inbound traffic

Create the two application rules as follows:

1. Open the Start menu, select Run, enter WF.msc, and select OK.

2. In Windows Defender Firewall with Advanced Security, right-click Inbound Rules and select New Rule.

3. In Rule Type, select Program, and then select Next.

4. In Program, select This program path. Browse to the SQL Server executable, select Open, and then select Next. The default SQL Server 2022 path is C:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER\MSSQL\Binn\Sqlservr.exe.

5. In Action, select Allow the connection, and then select Next.

6. In Profile, select the profiles for which the rule should apply, and then select Next.

7. In Name, enter a name and description for the rule, and then select Finish.

Create the RPC port rule as follows:

1. Open the Start menu, select Run, enter WF.msc, and select OK.

2. In Windows Defender Firewall with Advanced Security, right-click Inbound Rules and select New Rule.

3. In Rule Type, select Port, and then select Next.

4. In Protocol and Ports, select TCP, select Specific local ports, and enter 135.

5. In Action, select Allow the connection, and then select Next.

6. In Profile, select the profiles for which the rule should apply, and then select Next.

7. In Name, enter a name and description for the rule, and then select Finish.

Allow the CodeMeter license server through the firewall

This configuration is separate from SQL Server and is required for remote seats to access licenses on the Enterprise kiosk.

Enterprise uses WIBU CodeMeter 8.40. A remote Enterprise application must be able to find and check out a license from the CodeMeter license server running on the PYPESERVER kiosk.

CodeMeter communication uses TCP/IP. The default CodeMeter port remains 22350.

When a firewall is active, open port 22350 for TCP and UDP. If the firewall filters by application, allow the CodeMeter.exe service located in %ProgramFiles(x86)%\CodeMeter\Runtime\bin.

Some antivirus products include firewall functions. Contact the product vendor if you are unsure how to create the required exception.

• If the kiosk's host name or network configuration changes, restart the kiosk and remote computer before testing CodeMeter connectivity.

• Alternatively, configure the remote computer to use the kiosk's static IPv4 address.

SQL Server

The Enterprise kiosk is delivered with SQL Server 2022 Express. SQL Server 2019 and SQL Server 2017 remain supported for legacy installations.

Performance

SQL Server 2022 Express is appropriate for typical Enterprise deployments. For higher user counts or larger workloads, consult Enterprise before selecting SQL Server Standard or another edition.

Data backup

Back up Enterprise data every day to storage outside the kiosk.

• For minimal data loss, use resilient storage such as RAID 1 or RAID 10 on a managed SQL Server host.

• Enterprise database growth is modest in server terms, so complete backups are generally practical and inexpensive.

• Back up the following manufacturing-related information:

  • The SQL databases "PypeServerAdmin" and "PypeServerDB"

• By default, Enterprise uses SQLBackupAndFTP to schedule database backups. It backs up PypeServerAdmin and PypeServerDB to the SSD and to a separate removable drive connected to the kiosk.

• Store current backups both on-site and off-site.

Database growth

Databases typically grow between 5 and 20 Megabytes per year.

Relocating the SQL Server

Performance considerations

• If the SQL Server or LAN is unavailable, the connected cutting machines cannot use Enterprise.

• Enterprise Support requires administrative access to the databases and an approved remote-access method when diagnosing server issues.

• Network latency between Enterprise and SQL Server must remain low. Latency above 4 ms may degrade performance. See Running Enterprise remotely over a WAN or VPN.

• If the server uses a firewall, create inbound rules that allow Enterprise to reach SQL Server. See Configuring firewall access.

• Support for customer-managed database relocations is billed hourly because it is outside the standard warranty and support package.

Required services

1. SQL Server 2022

   • SQL Server 2019 and SQL Server 2017 are supported for legacy installations. Earlier versions are not supported.

2. SQL Server Browser on the server

3. Microsoft Distributed Transaction Coordinator, when required by the installation

   • Configure SQL Server to start this service when required.

   • This service requires inbound RPC port 135.

• Remote seats require Network DTC Access on both the kiosk and the remote computers.

Using the dcomcnfg.msc tool

1. Open the Windows Run dialog, enter dcomcnfg.msc, and select OK.

2. Navigate to Component Services > Computers > My Computer > Distributed Transaction Coordinator > Local DTC.

3. Right-click Local DTC and select Properties.

4. On the Security tab, enable the following settings:

   • Network DTC Access

   • Allow Remote Clients

   • Allow Inbound

   • Allow Outbound

   • No Authentication Required

   • Enable XA Transactions

   • Enable SNA LU 6.2 Transactions

Using PowerShell

1. Right-click Start and select Windows PowerShell (Admin) or the approved elevated PowerShell host.

2. Select the appropriate configuration below, paste the command into the elevated PowerShell window, and run it.

Kiosk/SQL Server

Set-DtcNetworkSetting -AuthenticationLevel "NoAuth" -InboundTransactionsEnabled $true -OutboundTransactionsEnabled $true -LUTransactionsEnabled $true -RemoteClientAccessEnabled $true -XATransactionsEnabled $true

Remote Seat

Set-DtcNetworkSetting -AuthenticationLevel "NoAuth" -InboundTransactionsEnabled $true -OutboundTransactionsEnabled $true -LUTransactionsEnabled $true -XATransactionsEnabled $true

Allow DTC through the firewall on both systems

netsh advfirewall firewall set rule group="Distributed Transaction Coordinator" new enable=yes

Enable-NetFirewallRule -DisplayGroup "Distributed Transaction Coordinator"

Relocation steps

These steps assume Windows Authentication. Enterprise also supports SQL Authentication for workgroup scenarios.

Follow these steps:

1. Do not add legacy SQL Server startup parameters by default. If identity-value gaps are a concern, consult Enterprise before changing SQL Server 2022 settings.

2. Enable TCP/IP on the server.

3. Allow remote connections.

4. Turn off the server firewall temporarily for diagnosis, or create the required inbound rules.

   • The firewall guidance in this document targets SQL Server 2022. Adjust legacy SQL Server 2019 or SQL Server 2017 installations for their configured ports and instance paths.

5. Copy PypeServerDB and PypeServerAdmin to the new server.

• Use the database names PypeServerDB and PypeServerAdmin.

• Use these exact database names because Enterprise does not remap them.

6. Grant the required users read and write access to both databases.

7. Stop the SQL Server service on the Enterprise kiosk.

   • Do not uninstall SQL Server from the kiosk. If the external server becomes unavailable or additional diagnosis is required, the databases can be restored to the kiosk.

   • See the "Configure Database Backups" step for some further simple failover processes.

8. From the Enterprise kiosk, use SQL Server Management Studio under the intended Windows user account to confirm access to the new server and both databases.

   • Test write access to PypeServerDB.dbo.SystemConfigInfo by making an approved temporary change, and then restore the original value.

   • If the server is inaccessible, temporarily disable its firewall for diagnosis. Re-enable it after the required inbound rules are configured.

9. Redirect the Enterprise application to the new SQL Server location.

   • Complete this step on the kiosk and every remote seat. Start Enterprise and allow up to one minute for it to report that the databases are unavailable. Follow the prompts to open the database-location dialog with administrator privileges.

• Use Windows Authentication. Select the server and test the connection. If the test fails, see Installing Enterprise on a remote computer.

• SQL Authentication: Contact Enterprise if your environment requires it.

10. Grant read-only access to approved users and services that require reporting or integration data.

11. Configure and test database backups.

    • Consider backing up the databases to the PYPESERVER kiosk as part of a documented failover plan. If the external server or network fails, an administrator can restore the latest approved backup to the kiosk and redirect the application.

SQL read access

For reporting

PypeServerDB provides a primary SQL view for reporting.

• See Reporting in the User Information section.

• Contact Enterprise if you need data presented through an additional supported view.

ERP and other connections

Enterprise can provide SQL views for approved data-integration requirements.

• Query these views with read-only credentials as needed.

• Contact Enterprise to discuss specific integration requirements.

Failover planning

Data backup

Data loss is the primary failover risk. A disk failure can result in the loss of all changes made since the most recent backup.

• If this risk is unacceptable, use managed disk mirroring or another current storage-redundancy solution.

Hardware backup

If approximately 30 minutes of downtime is acceptable after a hardware failure, maintain compatible replacement hardware and a documented recovery procedure.

• Enterprise can provide a second compatible computer configured to replace the kiosk computer when necessary.

• Maintain a current bare-metal image and tested database backups. After a drive failure, restore the image, restore the latest database backup, and verify the system before returning it to production.

For machines with serial communications

For 2026 installations, keep a supported, optically isolated USB-to-serial adapter as a spare. Select an industrial-grade adapter with current Windows 11 drivers and the connector type required by the machine.

Disk imaging

Maintain a current bare-metal image of the Enterprise Windows computer and test the recovery procedure periodically.

Multiple-machine configuration

If more than one cutting machine uses Enterprise:

• Provide a kiosk for each machine's local operating requirements.

• Both machines can use one SQL Server when the network and server meet Enterprise requirements.

• Rename the kiosk that does not host SQL Server to PYPESERVER2 or another approved machine-specific name.

• Set the SQL Server service on the non-server kiosk to Manual or Disabled, as specified in the implementation plan.

• Redirect the non-server kiosk to the designated SQL Server. Enterprise Support can assist with this change.

Virtual machines

Enterprise Site and Seat roles are supported on Microsoft Hyper-V and Azure hosts. Validate network latency, storage, and GPU requirements before deployment. See the Enterprise in Azure knowledge-base article for current instructions.

TeamViewer Access

The system arrives pre-configured with TeamViewer installed, with remote access by Enterprise using 2-factor authentication bound to specific Enterprise machines. It is recommended that you leave this access in place during the initial phases of setup and use so that Enterprise can offer support, make updates, update licenses, and consult as needed.

Once stabilized you are welcome to turn off TeamViewer remote access so that Enterprise can only get access when you allow it. However, it is strongly recommended that you do not uninstall TeamViewer, as this will adds work to gaining access later, delay support, and typically require the use of temporary, less secure passwords that are not enforcing 2 factor authentication bound to specific Enterprise machines. The recommended way to turn off remote access is from the TeamViewer Options window as follows:

And per your request, Enterprise support can turn that off on the way out after a support session.

Implementation sequence

Before arrival

• Install a wired Category 5e or better network connection at the planned kiosk location.

Machine arrival

• Connect the required network cables.

• If your organization uses a domain, join the PYPESERVER kiosk to it.

See the FAQ entry about programming before the machine is fully set up.

Ongoing maintenance

• Configure and routinely test the data-backup system.

• Monitor solid-state-drive health and replace drives according to the manufacturer's current recommendations and your IT policy.

Enterprise updates

• Request current builds during a planned production lull.

  • Enterprise can download current builds to the kiosk and apply required SQL Server updates. If SQL Server has been relocated, coordinate the database portion of the update with Enterprise.

  • Install each new application version on the kiosk and all remote seats.

• Enterprise targets one major release each year and contacts customers when significant releases are available.

Windows Update

• Windows Update is disabled by default so the customer's IT team can configure its own update policies. Schedule updates during planned maintenance, confirm that current backups are available, and notify Enterprise if an update causes a problem.

Warranties and annual license fees

• The Enterprise kiosk hardware is under warranty for one year from delivery.

• Annual license fees are required to run the Enterprise application. Fee types are as follows:

  • Designer

  • Designer remote seat

  • Enterprise

  • Enterprise remote seat

  • Importers (various types)

  • G-Code support

  • Other features as released

• Actual fees are listed in the applicable product quotation.

Frequently Asked Questions

Startup

Q: Can we complete training before the machine is fully set up?

A: Yes. Training is most effective when the machine is installed and ready to use. Operators should also spend time learning the application's basic functions before the session.

General use

Q: Should I stop the Enterprise app when I am not using it?

A: No. The app must remain running while the pipe-cutting machine is operating so it can collect cut-status information and exchange information with the kiosk.

Licensing

Q:

Can I install the remote application on more computers than I have licenses?

A: Yes. You can install it on any number of computers.

Q: Can I run Enterprise offline or away from the network?

A: No. Enterprise requires continuous access to SQL Server and the CodeMeter license server.

IT-related questions

Q: Can I connect the kiosk to the LAN wirelessly when a wired connection is difficult to install?

A: A wired connection is required for remote-seat deployments. Plasma cutting and nearby welding can disrupt wireless communications, and remote seats require continuous access to SQL Server and the CodeMeter license server.

• If you do not use remote seats, the kiosk requires a network connection only for support and updates.

Q: Where are the licenses stored?

A: Licenses are stored in a CodeMeter file-based container or hardware dongle on the computer running the license server. The kiosk normally hosts this service, although your IT department may configure an approved alternative.

Q: Can we connect through a VPN when we need to run Enterprise outside our LAN?

A: See Running Enterprise remotely over a WAN or VPN.