A startup script runs during a system’s initial boot up; it is applied to a system using a group policy. Startup scripts run under the context of the local computer’s SYSTEM account.
What is a startup script?
Why use a Startup Script for ConfigMgr?
To check configuration settings and the state of services that the ConfigMgr client agent depends on for successful operation as well as install the client agent if it is not installed or functioning properly.
Why use a Startup Script instead one of the built-in methods to install the client agent?
A startup script avoids most common DNS issues, firewall issues, and other connectivity issues that are common when a central system attempts to touch all of the clients. It also adds the health/configuration checks mentioned above to check for (and correct some) dependencies as well as report on systems still having issues.
Does this replace ccmeval in ConfigMgr 2012 or does ccmeval in ConfigMgr 2012 replace the need for this script?
- Fixed two typo bugs.
- Renamed script file to not include the version number.
- Updated CacheSize checking so that a default value is no longer forced during client agent install, reinstall, or during any run of the script if the option is omitted from the configuration file or set to zero.
- Updated log file handling when moving the log file to ccm/logs. If a log file for the script already exists in ccm/logs, it will be renamed to include the date and time and then the new log will be copied in.
- Added pre-requisite checks to prevent the script from performing any checks or installing the client agent
- Corrected elapsed time calculation for the final log message
- Updated error handling when checking for admin shares