• WSRNicholsHoHum

    WSRNicholsHoHum

    @wsrnicholshohum

    Viewing 15 replies - 1 through 15 (of 41 total)
    Author
    Replies
    • in reply to: Sort order (VBScript) #980024

      My problem is that the script is written in VBScript which doesn’t seem to support the sort method. It another example of one of the differences between VBScript and VB or VBA.

    • in reply to: Querying Active Directory #980022

      And don’t forget the section:
      ‘ —————————————————————
      ‘ From the book “Active Directory Cookbook” by Robbie Allen
      ‘ Publisher: O’Reilly and Associates
      ‘ ISBN: 0-596-00466-4
      ‘ Book web site: http://rallenhome.com/books/adcookbook/code.html
      ‘ —————————————————————
      Let’s give credit where credit due.

      Glad the link was of use.

    • in reply to: Querying Active Directory #979660

      Robbie Allen’s book “Active Directory Cookbook” is great for this sort of thing. The scripts are available on :

      http://rallenhome.com/books/adcookbook/code.html

      Have a look at script 4.2 Viewing the attributes of a object. It is easy to build that into an ASP page if you want to look up user’s AD attributes regularly (though you should secure that page!)

    • in reply to: CSV Date import (Office 2000) #963081

      The SQL databases I use are MySQL, Access and a Borland DB2. In my experience if the driver won’t translate a normalised date (e.g. 1-Jul-2003) then best bet is to use yyyy-mm-dd hh:mm:ss format. The SQL books I have indicate this is the standard format for most SQL databases. I’ll bow to your greater experience with MS SQL. In VBA and VBScript I tend to use month(), day() and year() a lot so I know exactly what I’m getting out.

      0nly goes to further prove what a pain dates are.

      Thanks again for the feedback

    • in reply to: CSV Date import (Office 2000) #963079

      Thank you for your replies. At least a consistant answer ).

      This only re-emphasises my favouring of writing dates in 28-Jul-05 style, where there is no confusion. Though I’m actually getting to like SQLs standard yyyy-mm-dd hh:mm:ss as at least its a logical progression from large to small and appears to be consistent across platforms.

      I don’t think my user will be so pleased. I’m sure to get the “but it works on so and sos PC”. Hey ho! the fun of life as an IT manager.
      Thanks again – Reggie

    • in reply to: LDAP and Outlook 2000 (2000 Office SP3) #910599

      No problem at all. There is a trial version of MDaemon. You can get it from http://www.altn.com[/url%5D. However, you should be able to replicate the problem without MDaemon. I’m picking the e-mail addresses by storing them in each users details in AD and then using Outlook’s LDAP option to query AD. It works well except if people have large lists on people in the Outlook Contracts list. Then the system tends to come up with the address in the contact list rather than one from LDAP (or both).

    • in reply to: LDAP and Outlook 2000 (2000 Office SP3) #910600

      No problem at all. There is a trial version of MDaemon. You can get it from http://www.altn.com[/url%5D. However, you should be able to replicate the problem without MDaemon. I’m picking the e-mail addresses by storing them in each users details in AD and then using Outlook’s LDAP option to query AD. It works well except if people have large lists on people in the Outlook Contracts list. Then the system tends to come up with the address in the contact list rather than one from LDAP (or both).

    • in reply to: LDAP and Outlook 2000 (2000 Office SP3) #910572

      I don’t get Tools-Options, rather Tools-Accounts. Here these is an option to change the order of LDAP directory queries, but this doesn’t include the Outlook “Contacts” address book. So users still default to the Contacts book before looking at LDAP.

    • in reply to: LDAP and Outlook 2000 (2000 Office SP3) #910573

      I don’t get Tools-Options, rather Tools-Accounts. Here these is an option to change the order of LDAP directory queries, but this doesn’t include the Outlook “Contacts” address book. So users still default to the Contacts book before looking at LDAP.

    • in reply to: LDAP and Outlook 2000 (2000 Office SP3) #910507

      Thanks for the advice. I used it in post 434120 which also explains why I’m no longer looking at changing the permissions at the server.

      Still looking for help with the search order – default is Contact then LDAP. I want to change it to LDAP then Contacts.

    • in reply to: LDAP and Outlook 2000 (2000 Office SP3) #910508

      Thanks for the advice. I used it in post 434120 which also explains why I’m no longer looking at changing the permissions at the server.

      Still looking for help with the search order – default is Contact then LDAP. I want to change it to LDAP then Contacts.

    • in reply to: LDAP authentication – 2003 #910505

      Oh! and I got hold of a copy of ADSI Edit via the XP support tools – complete install. Free download from Microsoft:

      http://www.microsoft.com/downloads….

    • in reply to: LDAP authentication – 2003 #910506

      Oh! and I got hold of a copy of ADSI Edit via the XP support tools – complete install. Free download from Microsoft:

      http://www.microsoft.com/downloads….

    • in reply to: LDAP authentication – 2003 #910501

      I’ve found this article: Microsoft Knowledge Base Article 320528 which covers what I am trying to do. I also found a reference to doing this in Robbie Allen’s book “Active Directory Cookbook” p436 (O’Reilly). As wells as allowing anonymous access, I also have to set permissions on the directory objects. However, some attributes only seem to be available on user objects. That means I cannot set the attribute at the OU level and let it pass down to the users via inheritance. Which leaves me with three options: Set “Read all” for anonymous logon (which I don’t want to do for security reasons), Set the attributes for each user individually (Hard work), or create a script to do it for me (possible, but time consuming and how do I test without risking messing up the directory). So unless someone can suggest another option, I’m giving up on this plan. I’ll stick with things as they are.

    • in reply to: LDAP authentication – 2003 #910502

      I’ve found this article: Microsoft Knowledge Base Article 320528 which covers what I am trying to do. I also found a reference to doing this in Robbie Allen’s book “Active Directory Cookbook” p436 (O’Reilly). As wells as allowing anonymous access, I also have to set permissions on the directory objects. However, some attributes only seem to be available on user objects. That means I cannot set the attribute at the OU level and let it pass down to the users via inheritance. Which leaves me with three options: Set “Read all” for anonymous logon (which I don’t want to do for security reasons), Set the attributes for each user individually (Hard work), or create a script to do it for me (possible, but time consuming and how do I test without risking messing up the directory). So unless someone can suggest another option, I’m giving up on this plan. I’ll stick with things as they are.

    Viewing 15 replies - 1 through 15 (of 41 total)