

Instructions for recreating the PackageBuilder user on a Community Connect 4 network.
Explains why you are unable to build computers with the default assignments after a CC4.3 to CC4.5 upgrade.
... ("This product cannot be assigned because it is missing one or more constituent packages ."), but all constituent packages are in fact present.
Describes a workaround on how you can export a CC4 package to a network or removable drive if you are getting an error message.
Explains the process to import an MSU file into the RM Management Console (RMMC).
Provides a download for the RM Stale Package Detector tool.
Describes an issue with the OR expression causing package dependencies to be ignored.
Provides a repository health check tool for use on CC4 multi-site networks.
Describes an issue where CC4 package installations may not continue if a computer restarts after installing a package that contains an unexpected reboot.
CC4 package installation fails because Windows Installer is currently installing or configuring another package.