Email Signatures from AD
Can someone please help me with the following question. Is it possible to setup email signatures from AD to apply to all users, so it would pull there details though to the signature but we can maintain from a central location. All suggestions welcome. Thanks Michael
July 9th, 2010 7:36pm

Hi , Kindly read it and do it. So, the first thing we need to do is connect to the client's user object in the active directory. This is surprisingly easy to do. First of all, we will create an object that points to the ADSystemInfo object. This object will give you some basic information about the currently logged in user. The information in here is useful, but in our case it does not contain everything we need. What we can do, however, is use the ADSystemInfo.UserName property to open a connection to the active directory LDAP database, which is where the information we are after is held. So the first part of the script will look like this: 'create the objects and set the initial vars Set WshShell = WScript.CreateObject("WScript.Shell") Set FileSysObj = CreateObject("Scripting.FileSystemObject") Set objADSysInfo = CreateObject("ADSystemInfo") Set UserObj = GetObject("LDAP://" & objADSysInfo.UserName) You have probably seen the first two lines before; they are creating objects (the shell and file system objects) we will use later. The third and fourth lines are what we are using to connect to the active directory. First we are using the ADSystemInfo , and then, using the UserName property of that object, we can create a new object that binds to the client's user in the active directory. Now that we have done that, we have access to all the information for the client, and we can use this information in our email signature. Next, the script will use our shell object to build some paths to where we are going to save the new signature file: strAppData = WshShell.ExpandEnvironmentStrings("%APPDATA%") SigFolder = StrAppData & "MicrosoftSignatures" strQuteChr = chr(34) SigFile = SigFolder & UserObj.sAMAccountName & ".htm" These lines are just using the system environment variable APPDATA so that we know where to build the signature file. We then create an easy to remember variable for the double quote character, and set the name/path of our signature file to be the user's account name in the default signature folder. I hope with this you will get done. Regards. Shafaquat Ali. M.C.I.T.P Exchange 2007/2010, M.C.I.T.P Windows Server 2008, M.C.T.S OCS Server 2007 R2, Phone: +923008210320
Free Windows Admin Tool Kit Click here and download it now
July 9th, 2010 9:35pm

Version of Exchange would be of some assistance here. Without knowing that, the best answer is third party tool. Lots of those around - personally I have exclaimer in more than one location, which will pull the information from the domain. It also provides a GUI for the configuration of the signature panel. If you are using Exchange 2007/2010 it may well be possible to do something with the transport rules to pull the information from the domain. Simon.Simon Butler, Exchange MVP. http://blog.sembee.co.uk , http://exbpa.com/
July 10th, 2010 5:57pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics