Introduction to the Cireson Control Center
Purpose and Audience
Prerequisites and Assumptions
Minimum Requirements for the Cireson Control Center
Installing the Prerequisites for the Cireson Control Center
Account and group requirements
Remote Manage Requirements
Downloading the Cireson Control Center
Installing the Cireson Control Center
Overview of the Control Center Installer
Providing access to SQL for the Control Center
Running the Control Center Installer
Post Installation Configuration of the Cireson Control Center
Verifying the Control Center is Working
Installing The Control Center Client
Installing Commence for the Cireson Control Center
Discovering the EndPoint Address of the Control Center server
Configuring Commence with the EndPoint Address of the Control Center server
Downloading and installing SDelete
Verify Anonymous Authentication to the Commence installation directory
Verify Your ConfigMgr Distribution Points are PXE-enabled
Create a Boot Image for Commence
Customize the Commence Boot Image
Distributing the Commence Boot Image
Creating the Commence Task Sequence
Customizing the Commence Task Sequence
Deploying the Commence Task Sequence
Granting access to Commence
Backup and Restore of the Cireson Control Center
Backing up the Control Center
Restoring the Control Center
Upgrading from Previous Versions of the Cireson Control Center
Upgrading the Control Center
Post Upgrade Procedure
Appendix A - Enabling the Windows Remote Management Service
Appendix B - Converting from the Trial to the Licensed Version of the Control Center
Appendix C - Extracting the Cireson Control Center Installation Files
Appendix D – Preparing an Offline Installer to install the Cireson Control Center
Frequently Asked Questions
2.x and Earlier
True Control Center Installation Guide
Direct link to topic in this publication:
Control Center v3.1.1 (3.1.0) Release Notes
There was an issue with upgrading to 3.1.0 in some customer environments. We released 3.1.1 to resolve this issue and as a result all upgrades from 3.0.6 should be to 3.1.1. If you upgraded to 3.1.0 and had issues please contact email@example.com. If you did not experience issues with upgrading to 3.1.0 you are stable and there is no need to upgrade to 3.1.1. Sorry for any issues this may have caused. Thanks!
New User Management features implemented, accessible from the users view context menu.
New deployment grids in the User Management, and Device Management flyouts. You can now see deployment status for the target device.
Flyouts can now be stacked, and quickly flipped between using the stack switcher.
Active Directory integration has been improved and now you can see a users AD properties in the User Management summary tab.
Active Directory groups, discovered through CM Group Discovery, are now shown for the user in the User Management flyout.
Device processes now show the memory and CPU utilization of each process after pulling client data.
Version information is now available in the bottom left above the Cireson logo so that you can easily tell us how much you love each version.
Grid filtering the Device Management tabs has been fixed. You can now filter and sort (correctly) to your heart's content.
You had to be a sharpshooter to click the proper portion of the Device Management 'pull' button, now even your grandma could hit it. (no offense to your grandma...)
There was an issue with Local actions in Device Management, not passing the proper path to the App Launcher. We've provided counseling and their communication is now much improved.
Resolved a few notification issues in the Device Management view, so they are a bit friendlier now when they talk back to you.
Fixed an issue where you were adding a new security group, and AD groups weren't invited to dropdowns party. We've made sure they feel included now.
Some analysts were able to access the Device Management view for computers that weren't in their scope. This has been resolved across the board.