I’ve been busy on CMWT this weekend.  Fixing bugs and bolting on some missing parts, but I have also spent about half the effort improving features.  In addition to the coding itself, I’ve decided to split the source code and download packages under separate Git repositories to keep things cleaner.  As part of this, for the long-term, I will maintain up to three (3) version downloads including the current/latest.  Older packages will be removed as the next new version is posted.

cmwt_2016-12-10-01

cmwt_2016-12-10-02cmwt_2016-12-10-03

What’s New / Changed

Bug fixes

  • Collections and Collection properties
  • Devices and Device property reports
  • Software reports
  • Reports
  • Site Hierarchy / Status reports
  • CSS mapping
  • ADO functions
  • ADSI/LDAP functions
  • Table column sorting
  • Device Management Tools (for IE only)
  • AD Tools reports (and secure LDAP ADO connections)

Feature Updates

  • Page layout (UI/UX)
    • Grouping of tiles
    • Link Names (labels)
  • Home page
  • Sidebar
    • Help link
  • Search
  • AD Users
  • AD Groups
  • AD Computers
  • AD OU Browsing
  • Site Logs / Log Viewer
  • Operating Systems Deployment
    • Boot Images

New Features

  • Custom Reporting tools (still in development)
    • The Reports landing page is being deprecated in favor of moving the reports to the landing pages which are most relevant (e.g. software reports linked from the software page)
  • Active Directory
    • Group Policy Object reports**
    • AD User – > Computer Logins by Profile mapping

** requires the GPMC to be installed on the CMWT host

Notes

  • To use the new Custom Reports you must first create them using the new Report Builder form (“Direct SQL Query” form)
    • You can also run the cmwt_db_sqlreports.sql script to insert sample reports to get started (recommended!)
  • Make sure users (if they are not Administrators in SCCM and the SCCM SQL database) are granted db_datareader rights (e.g. CM_PS1)
  • Make sure users are granted db_datareader and db_datawriter rights on the CMWT database.
  • Make sure the AD Tools user account (specified in the _config.txt file) has permissions to modify user accounts in AD.  Best practice is to delegate by OU in order to isolate sensitive accounts from be accidentally modified.

Upgrade an Existing CMWT installation

  • Make a copy of _config.txt
  • Unzip the package into the CMWT folder
  • Restore the backup copy of _config.txt
  • Refresh the web page (F5)

New Installation

  • Read the Installation Guide included in the ZIP package.  It’s under the “docs” subfolder.

Download

  • Go HERE – Download CMWT-2016-12-10-01.zip
Advertisements

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s