Set FSO = CreateObject("Scripting.Filesystemobject") 'sOutputfile = sSignaturePath & strSigName & ".htm" SOutputfile = sSignaturePath & sUserName & ".htm" SSignaturePath= sUserProfile & "\Microsoft\Signatures\" SUserProfile = WshShell.ExpandEnvironmentStrings("%appdata%") 'sUserProfile = WshShell.ExpandEnvironmentStrings("%UserProfile%") Set WshShell = CreateObject("Wscript.Shell") 'Lets Save the signature file to disk to the profile - we are aiming for the Outlook signature path Xsl.load "\\iservices\netlogon\signature.xsl" 'strXSL="\\iservices\netlogon\signature.xsl"
We keep it in the same path as the script, but it could be stored anyway. Set xsl = CreateObject("Microsoft.XMLDOM") Set xml = CreateObject("Microsoft.XMLDOM") 'WScript.Echo "LDAP user objects:" & rsAD.RecordCount 'for testing Set rsAD = CreateObject("ADODB.Recordset") 'Execute the query to get our objects from Active Directory. SAttributes = "givenname,sn,ipPhone,telephonenumber,mail,Streetaddress,l,st,postalcode,co,mobile,company,facsimileTelephoneNumber,title,department,"TimeOut" ) = 30 ' seconds SFilter = "(samaccountname=" & sUsername & ")" 'what do we want to find - well our details.
Set com = WScript.CreateObject( "ADODB.Command" ) Set conAD = WScript.CreateObject( "ADODB.Connection" ) 'Alright - we are now prep'd to do a little search to get our adspath. Set cont = GetObject(sPrefix & "rootdse") 'Wscript.Network knows the Netbios Domain, but we might not know our DNS domainname Set WshNet = WScript.CreateObject("WScript.Network") 'What we do know, is who we are (samaccountname) and that must be unique within a domain 'We cannot assume that the AdsSecurity.DLL is available on the client to retrieve our DN 'We need to get details from attributes that are only available from the LDAP provider Set oShell = WScript.CreateObject ("WSCript.shell")ĭim strSigName, strXSL 'store values hereįor Each varArg in ObjArgs intCount=intCount+1 If (intCount=1) then msgbox varArg strSigName=varArg End If If (intCount=2) then 'msgbox varArg strXSL=varArg End IfĬonst REGSIGKEY = "HKCU\Software\Microsoft\Office\10.0\Common\MailSettings\NewSignature"ĭim WshShell, WshNet, rsAD, Com, ConAD, f ' will create a new signature called _Official using signature.xsl for format ' usage: signature.vbs _Official signature.xsl Note from : use command parameters without switches to launch script It would be nice if you drop me a mail With If you know where I made the mistake - pls let me know ' this should be converted to in HTML - but it will be a space in the ' There is one thing about the output HTML that I don't understand. I basically only use it for strings and longs. ' If you ask yourself why I sometimes use a hungarian notation, ' There isn't any error checking included, which might be a good ' for your Outlook version - see buttom for more details. ' I tried to make it as generic as possible, but modifications in
' you get your user Information in XML form. ' work), you can easily modify it and use some database or whereever ' for sure that if the user can log onto the network that script will ' If AD isn't your first choice (well it should be, because you know
#SET UP SIGNATURE IN OUTLOOK WINDOWS#
' from Windows NT 4.0 (which DsClient & IE 6.0) and above. ' It is designed to work on any windows machine that has ADSI, WSH ' create Outlook HTML signatures based on a XSL template. ' COMMENT: This script will extract Active Directory user information and ' AUTHOR: Tim Bosinius, Tractebel Gas Engineering GmbH Suddenly it gives us the following error: We are having difficulties with the scrept that previous IT guy created. I`m just wondering if someone can help me with this.
0 kommentar(er)
