There are additional controls in place as well. For example, each run can be limited to how many are added as well as the max to allow (1000 in this case). This way the helpdesk is not overloaded with removal requests or questions over what they just won. We can comfortably bring PTG up to where we want it. I have the script running on a weekly basis.
There are a few things its lacking that will go into a new version:
- Ability to blacklist people, VIPs for example, who should not be in here.
- Not re-add anyone who requested out
- If a machine is removed from AD for whatever reason, the person should be removed.
- Support HTML for the user email for logo etc so its prettier.
- Patch Testing Group Users
- Patch Testing Group Computers
There is an EmailToUser.txt text file that is sent to the user when they "win". Customize as your environment needs. The script itself has several variables at the top needing to be customized to your environment. Should be mostly self explanatory but still allows some granular control. Items worth expanding:
- blnTestRun - Test mode to make sure its running correctly before you let it loose.
- blnEmailUser - Allows you to tell the users they won or not.
- blnEmailTestUser - Lets you BCC the helpdesk to the user emails or not.
- strEmailsFromTech and strEmailsFromUser - Lets you use an established "from IT" mailbox but the techs see its coming from the script.
blnTestRun = True 'If True, the computer account and user accounts will not be added to the group. Emails will not be sent to the user either. blnEmailUser = False 'do you want to email the end user that their computer has been added to the patch testing group? Test Run variable has to be set to False otherwise this is skipped. blnEmailTestUser = False 'If set to True then the test email account will receive the indivdual emails as well strPTGNameUser = "PTGTestGroupUsers" 'Name of group to contain user accounts strPTGNameComputer = "PTGTestGroupComputers" 'Name of group to contain user accounts intQuantity = 1000 'maximum number of computer accounts in the group intMaxAddLimit = 50 'maximum number of computer accounts to add each time the script is run intMinBuildDays = 30 'number of days past build date to look at for adding to the group. Make sure that User Device Affinity has had enough time to generate this strEmailFile = ScriptPath()&"\EmailToUser.txt" 'path to the standard email template strSMTPServer = "smarthost.mycompany.com" 'SMTP server to use strEmailsTech = "firstname.lastname@example.org" ' separate with semi-colon and space. Ex: "email@example.com; firstname.lastname@example.org" strEmailFromTech = "PTGScript@mycompany.com" 'From address that goes to email addresses that receive test and summary messages strEmailFromUser = "ITCommunications@mycompany.com" 'From address that users will see strEmailTest = "email@example.com" 'Test email account that will receive the individual emails strEmailSubjectUser = "Your computer has been added to the patch testing group" 'Subject in email that goes out to users strSQLServer = "SCCMDBserver.mycompany.com" 'FQDN of SQL server hosting ConfigMgr database strDB = "CM_DB" 'DB name of ConfigMgr
DownloadThis script is provided as-is, no warranty is provided or implied.The author is NOT responsible for any damages or data loss that may occur through the use of this script. Always test, test, test before rolling anything into a production environment.
You can find the script referenced in this post as well as a sample enduser email here. You will need to tweak them for your environment as shown above.