---
title: "Intune Deployments (Pre-activation only)"
canonical: "https://support.stardock.com/space/SHC/2588835961/Intune%20Deployments%20(Pre-activation%20only)"
format: markdown
---
# Stardock Product Deployment Guide for Microsoft InTune

## Overview

This guide provides step-by-step instructions for deploying Stardock products (Start11, Fences, etc.) through Microsoft Intune using silent **activation **scripts. This does not cover the installation of the product itself as it is assumed that it will be installed already or at a later time.  This documentation is primarily for clients wishing to activate early and then then deploy the product via [scripted installation](https://support.stardock.com/space/SHC/1352531974/Silent+Installation+&+Activation). If activation in pre-done, and an image (meaning full Windows and all apps will be deployed, the preactivation - that deposits a license.sig to \ProgramData\Stardock\[stardockProduct] will be overwiritten. 

## Prerequisites

- Microsoft Intune tenant with appropriate permissions
- Valid Stardock product licenses
- Basic PowerShell knowledge

## Package Contents

**Start11 v2**  
[https://cdn.stardock.us/support/uploads/Start11_v2_ActivationOnly.zip](https://cdn.stardock.us/support/uploads/Start11_v2_ActivationOnly.zip)

**Fences 6**  
[https://cdn.stardock.us/support/uploads/Fences_6_ActivationOnly.zip](https://cdn.stardock.us/support/uploads/Fences_6_ActivationOnly.zip)

Each deployment package contains:

- **ActivateProduct.ps1** – Main activation script (requires credential editing)
- **SASUpgrade.exe** – Stardock activation executable
- **Default.spak** – Product-specific configuration file
- **IntuneWinAppUtil.exe** – Microsoft packaging tool
- Supporting DLL files

## Product-Specific Information

### .spak Files

Each Stardock product requires its unique .spak file:

- **Start11v2:** Copy from `C:\Program Files (x86)\Stardock\Start11\default.spak`
- **Fences6:** Copy from `C:\Program Files (x86)\Stardock\Fences\default.spak`
- **Other products:** Copy from respective installation directories

### Product IDs Reference

| Product | Product ID | Product Name |
| --- | --- | --- |
| Start11v2 | 2674 | Start11 |
| Fences6 | 2688 | Fences6 |

## Setup Instructions

### Step 1: Prepare the Script

1. Extract the deployment package to a working directory.
2. Open `ActivateProduct.ps1` in a text editor.
3. Update the following variables with your credentials:
4. Verify the product-specific variables match your target product:

### Step 2: Create Intune Package

1. Open Command Prompt or PowerShell as Administrator.
2. Navigate to your working directory.
3. Run the packaging command:
4. The tool will create `ActivateProduct.intunewin` in the Output folder.

### Step 3: Upload to Intune

1. Sign in to Microsoft Endpoint Manager admin center.
2. Navigate to **Apps > All apps > Add**.
3. Select **Windows app (Win32)** from the app type dropdown.
4. Click **Select app package file**.
5. Browse and select your `ActivateProduct.intunewin` file.
6. Click **OK**.

### Step 4: Configure App Information

Fill in the required fields:

- **Name:** [Product Name] Activation (e.g., "Fences6 Activation")
- **Description:** Brief description of the deployment
- **Publisher:** Stardock Corporation
- **Install command:** `powershell.exe -ExecutionPolicy Bypass -File ActivateProduct.ps1`
- **Uninstall command:** `echo "Manual uninstall required"`

### Step 5: Configure Requirements

Set minimum requirements:

- Operating system architecture: 64-bit
- Minimum operating system: Windows 10 1709 or later

### Step 6: Configure Detection Rules

**CRITICAL:** Set up file detection rule:

- **Rules format:** Manually configure detection rules
- **Rule type:** File
- **Path:** `C:\ProgramData\Stardock\[ProductName]`
  - For Fences6: `C:\ProgramData\Stardock\Fences6`
  - For Start11: `C:\ProgramData\Stardock\Start11`
- **File or folder:** `license.sig`
- **Detection method:** File or folder exists

### Step 7: Assign to Groups

1. Configure assignments based on your deployment strategy.
2. For testing, assign to a small pilot group first.
3. Monitor deployment status before broader rollout.

## Troubleshooting & Support

### Automated Log Collection

The deployment script automatically creates comprehensive troubleshooting logs in:

`C:\ProgramData\Stardock\[ProductName]\Logs\`

**Examples:**

- Fences6: `C:\ProgramData\Stardock\Fences6\Logs\`
- Start11: `C:\ProgramData\Stardock\Start11\Logs\`

### Collected Log Files

Each deployment creates timestamped logs:

1. **SasLog_copy_[timestamp].txt** – Stardock activation service log
  - Contains activation attempt details and error codes
  - Copied from `%LOCALAPPDATA%\Stardock\[ProductName]\SasLog.txt`
2. **IntuneLog_copy_[timestamp].log** – Intune management extension log
  - Contains deployment pipeline and execution details
  - Copied from `C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\`
3. **activation_log_[timestamp].log** – Script execution log
  - Contains timestamped script output and status messages

### Getting Support

If you encounter deployment issues and need assistance:

1. Locate the logs directory: `C:\ProgramData\Stardock\[ProductName]\Logs\`
2. Zip the entire Logs directory – this contains all necessary troubleshooting information.
3. Provide the complete zip file when contacting support.

**Do not send individual log files** – the complete Logs directory provides the full context needed for effective troubleshooting.

### Common Issues

1. **"Install Pending" Status:** Usually indicates detection rule path mismatch.
2. **Activation Failure:** Check credentials, network connectivity, and SasLog for specific error codes.
3. **Package Corruption:** Recreate the `.intunewin` file.
4. **Detection Rule Errors:** Verify the path exactly matches the product name (case-sensitive).

### Manual Verification Steps

1. Check for `license.sig` file in `C:\ProgramData\Stardock\[ProductName]\`
2. Review logs in the centralized Logs directory.
3. Test script manually via PowerShell if needed:

## Security Considerations

- Store deployment packages securely (contains license keys).
- Use appropriate Intune security groups for deployment.
- Consider using Azure Key Vault for credential management in production.
- Logs may contain sensitive information – handle appropriately.

## Notes

- Each product requires its own unique deployment package.
- The IntuneWinAppUtil.exe tool is provided by Microsoft and included for convenience.
- Test deployments thoroughly in a lab environment before production rollout.
- Allow 15–30 minutes for initial deployment processing in Intune.
- The centralized logging feature significantly simplifies client support.

---

For technical support, provide the complete `C:\ProgramData\Stardock\[ProductName]\Logs\` directory. Contact your Stardock representative or IT administrator for additional assistance.