I strongly recommend that you check it out if you have any interest in writing your own scripts and don’t want to mess with vbs or, god forbid, batch files. I’d just like to interject here that AutoIt is a VERY powerful and little known scripting language which I have used to write all kinds of utilities in the past. Once you have your signature templates setup, just configure a GPO to run the script at logon and it will silently create HTML, RTF, and plain-text signatures for each user. This makes it much easier to go back and make changes to your signatures on the fly instead of having to dig back down into the script and XML documents to make a simple change. The OWA support is more than I wanted though, and the XML approach was a bit tedious IMO, so I modified his script so that you basically create your html, rtf, and plain-text sigs as individual files and it modifies them for each user using the data stored in AD. Why reinvent the wheel anyway? Josh’s original script used some XML files and ExCmd to create your custom signatures and even pushed your signature out to OWA. I could have easily coded this myself, but his post HERE saved me most of the effort. It doesn’t make sense to create signatures for each employee by hand, and I can’t really trust users to follow directions in an e-mail telling them what signature they have to use, so what we have here is a completely automated way to push out a standardized company signature to your Outlook 2003 users leveraging the information you have in Active Directory.īig credit goes out to joshiieeii over at the AutoIt Script forums.
Well, apparently 10 bucks a user isn’t cheap enough for some people, so I had to figure out a cheaper (read: FREE) way to push out standard signatures to our users.
0 kommentar(er)
