Mycom Selection Software: Install

This is an intriguing query because "Mycom" typically refers to MYCOM OSI (a telecom network assurance and orchestration software) or, in a different context, Mycom Japan (a 3D graphics/CAD company).

Since you mentioned "interesting story" with selection software install, I’ll assume you’re talking about a scenario where someone had to choose between multiple software packages (selection) and then install MYCOM OSI’s products — often a complex, multi-step process involving license servers, database schemas, and integration with OSS/BSS systems.

Here’s an interesting real-world–style story based on that premise: mycom selection software install


Step 3: Run the Installer as Administrator

Right-click the installer file and select Run as Administrator. The setup wizard will launch.

Part 7: Frequently Asked Questions (FAQ)

Q1: Can I install Mycom Selection Software on multiple computers with one license?
A: No. Mycom uses node-locked licensing tied to a specific machine’s hardware ID. You need a separate license per PC. However, a “floating license” is available for enterprise sites—contact your Mycom rep. This is an intriguing query because "Mycom" typically

Q2: How long does a typical mycom selection software install take?
A: 30–45 minutes, including driver setup and database initialization. Add another 15 minutes for post-install configuration.

Q3: Do I need to uninstall the old version first?
A: Yes, but use the dedicated uninstaller from the original media. Manually deleting folders will leave orphaned registry entries and break the new install. Step 3: Run the Installer as Administrator Right-click

Q4: The software installs but freezes on startup. What do I do?
A: Likely a corrupt user profile. Create a new Windows user account with admin rights and launch from there. If resolved, migrate your data.

Q5: Is there a silent install option for mass deployment?
A: Yes. Use: Mycom_Setup.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /LOG="C:\Mycom_Install.log" Test on one machine first.


Initial configuration

  1. Log into the application UI using default admin credentials (change immediately).
  2. Configure authentication:
    • Local accounts or integrate with LDAP/Active Directory/SAML if supported.
  3. Set up roles and permissions (Admin, Evaluator, Reviewer, Viewer).
  4. Create or import scoring templates and criteria.
  5. Import initial data (vendors, proposals) via CSV/Excel import tool.
  6. Configure email notifications (SMTP server, from address) for alerts and approvals.
  7. Schedule regular database backups and application health checks.

Part 4: Post-Installation Validation Testing

An install is not complete until you verify functionality. Run these tests immediately after the wizard finishes.

Upgrade notes

  • Always back up DB and application config before upgrading.
  • Review vendor release notes for breaking changes and migration scripts.
  • Apply upgrades first in a test/staging environment, validate, then upgrade production.

System requirements (typical)

  • Operating system: Windows Server 2016 or later / Windows 10+ for single‑user installs
  • CPU: 4+ cores (server), 2+ cores (desktop)
  • RAM: 8 GB minimum (16+ GB recommended for multi‑user)
  • Disk: 20 GB free for application; additional for database
  • Database: MS SQL Server 2016+ or PostgreSQL (as specified by vendor)
  • .NET runtime: .NET Framework 4.7+ or .NET Core/5+ if required
  • Browser: recent Chrome, Edge, or Firefox for web UI
  • Network: TCP/IP access between app server and database server; required ports open
  • Accounts: Admin account with local install privileges; database admin (DBA) account

Key features

  • Multi‑criteria scoring and weight management
  • Side‑by‑side comparison of proposals and vendors
  • Role‑based access and audit trails
  • Import/export of data (CSV/Excel)
  • Reporting and visualization modules

Test 3: Data Transfer to Machine

Send a simple tool offset command to the Mycom controller.

  • Expected: The machine’s control panel acknowledges the change.
  • Failure: CRC error → Verify baud rate matches controller (typically 9600 or 19200).