Frequently Asked Questions

Questions, answered

Everything you need to know about our packaging services and process. Can't find an answer? Get in touch.

What types of applications do you package?

We handle:

  • MSI / MSIX / EXE / PKG
  • Scripts (PowerShell, Batch Script)
  • Complex setups requiring custom actions
  • Deployment - Intune
What formats do you support?
  • MSI
  • MSIX
  • IntuneWin
  • PKG
Do you provide custom scripting as part of packaging?

Yes. We develop and integrate custom scripts (PowerShell, PSADT) for pre-install, post-install, detection, configuration, and cleanup tasks.

How do you ensure the package is reliable and secure?
  • We package in isolated test environments.
  • Every package goes through installation, uninstallation, and upgrade testing.
Can you customize packages for SCCM or Intune deployment?

Yes, we provide deployment-ready configurations including:

  • Silent switches for SCCM or Intune deployment
  • Detection rules for Intune (file, registry, or MSI product code)
  • Application name
How long does it take to package an application?
  • Simple package: 1 - 2 days
  • Medium package: 2 - 3 days
  • Complex package: 3 - 4 days.
What details do you need from the client to start packaging?
  • Source installer files (EXE/MSI/PKG)
  • Installation instructions or documentation
  • Target OS details (Win 10/11, macOS)
  • Deployment tool (SCCM, Intune, etc.)
Do you support deployment?

Yes. We provide support for:

  • Uploading packages to Microsoft Intune, SCCM, or other deployment systems.
  • Configuring detection rules, requirements, and assignments.
What if the application fails in UAT?

We perform root-cause analysis and repackage or update the installer at no extra cost.

What deliverables will I receive?
  • Final package (MSI / IntuneWin / MSIX)
  • Deployment command set (Install / Uninstall / Detection)
  • Log files (installation/uninstallation)
  • Release notes
Do you work remotely or on client infrastructure?

We offer both options:

  • Remote packaging via secure VPN or cloud test environment.
  • On-premises packaging (if required for restricted environments).
Do you provide a sample package or demo?

Yes. We can package one sample application free or at a nominal cost to demonstrate our process and quality.

How do you handle dependencies or prerequisites?

We include dependency handling in the packaging process.

If your application requires .NET, Visual C++ Redistributable, or Java, we bundle it in the package or create separate package and add as a dependency in deployment tool.

How do you maintain version control for packages?

We maintain version control through a structured release naming convention e.g., VendorName_AppName_AppVersion_R1, VendorName_AppName_AppVersion_V1.0.

Can you repackage legacy or vendor applications that don’t support silent install switches?

Yes.

Do you perform user acceptance testing (UAT)?

No. User has to perform UAT. After QA, we support client-side UAT to confirm that the packaged application works as expected in the environment (SCCM or Intune).

What makes your packaging service different?

Our strengths include:

  • Competetive price
  • Fast turnaround time
  • Detailed testing & validation
  • Custom scripting (PSADT, PowerShell)
  • Documentation and logs for every package
  • Intune and SCCM deployment
  • Flexible engagement models (per app or monthly)
Do you offer training or knowledge transfer?

Yes. We can provide training sessions or documentation for your internal team on MSI/MSIX packaging, PSADT scripting, and Intune app onboarding.

How is complexity determined?

Complexity is calculated based on factors like the number of configurations, executables (EXEs/MSIs), and custom actions (e.g., registry add, file copies) etc... We will confirm the complexity level with you before any work begins.

Can you migrate the applications?

Yes. We can migrate the applications from SCCM to Intune, Windows 10 to windows 11, DSM Ivanti to Intune etc.