locked
Public hardware voip phones in active directory, best practice RRS feed

  • Question

  • Hello to all,

    I’m new here in this community.

    We are test-driving the OCS2007 beta in our test environment.

     

    I have a question regarding the AD integration of Voip Objects in our native 2003R2 domain.

    Our AD domain is a single domain with one Headquarter and 12 sites.

     

    Or Test organisation is divided in several root Ou’s for hardware like PC’s and Laptops

    And Root Ou’s for user objects.

     

    Something like this:

    Domain : test, OU=users, OU=north,OU=mainbuilding

    Domain: test, OU=workstations, OU=Laptops

    The default administration, servers, dc’s is unaltered.

     

    In the OCS scheme the hardware Voip phones in public area’s like meeting-rooms and Flex-workspaces requires a Voip number and a object id.

    The Voip number field can be used as a source for OCS or a LDAP application to build contact lists or phone books.

     

    What is the best practice for stand alone objects especially public IP phones.

    What is the best place to store the public Voip phones in our Ad scheme as a OU.

     

    Help is much appreciated

     

    Best regards

    Chris

     

     

    Wednesday, October 3, 2007 7:59 PM