Results 1 to 4 of 4
  1. #1
    New Lounger
    Join Date
    Apr 2016
    Posts
    6
    Thanks
    0
    Thanked 2 Times in 2 Posts

    Screen labels in Exchange Outlook Properties

    We would like to change the screen label text displayed in the "Properties" of user information contained on the "Phone/Notes" tab in the Exchange 2010 Global Address Book. This same data is contained on the "Telephones" tab in "Active Directory Users and Computers". Nobody uses Fax: anymore so we would like to change the display name to Remote: to add the remote office numbers of our employees and reduce confusion. Yes, we could cheat and just tell everybody that the remote office number is actually the fax number but we'd like to avoid that workaround.
    The "Remote:" office number is a phone number so absolutely nothing changes except the screen label the users see on the screen. Is this possible?

  2. #2
    WS Lounge VIP
    Join Date
    Dec 2009
    Location
    Earth
    Posts
    8,203
    Thanks
    49
    Thanked 987 Times in 917 Posts
    I suspect the name is internal to Outlook. The corresponding AD entry is likely to be called "fax" and as such a change there may result in the field not being recognised.
    Try dumping the GAL field names with PowerShell to see what is used.
    https://technet.microsoft.com/en-us/...xchg.160).aspx

    cheers, Paul

  3. #3
    4 Star Lounger
    Join Date
    Jan 2010
    Location
    Fort McMurray, Alberta, Canada
    Posts
    565
    Thanks
    51
    Thanked 70 Times in 68 Posts
    I would caution against doing this.

    Typically, you are dealing with a database with hard-coded field names with an identifying purpose. The client software (Outlook usually) then also handles the fields in a hard-coded manner.

    We have a medical imaging system. Due to an insistent request from the clinicians, we too did this. The medical imaging client software permitted display renaming of fields and so everything looked good, right? Not right. Every time we install a new client, we have to remember to rename the same field, in the same place. The client software does not get this information from the server, it's all client side controlled. It's administrative busy work and it routinely results in Help Desk calls.

    The underlying issue for you is that you are using a fax field for non-fax information. Even though it's still a phone number, it's still a misuse of this field. And that misuse is likely to pop up and bite you at every little turn.

    Exchange has a LOT of phone number fields. The benefit to what you are trying to do is minor and the potential consequences are greater than that.

  4. #4
    4 Star Lounger
    Join Date
    Jan 2010
    Location
    Fort McMurray, Alberta, Canada
    Posts
    565
    Thanks
    51
    Thanked 70 Times in 68 Posts
    I would add that the database in Exchange is a version of Jet. This is the same db engine that Access uses. As such it is a conventional relational database engine, with similar rules to Oracle, DB2 and MS SQL Server.

    My comments above were in relation to conventional relational database engines, so I wanted to check and make sure that Exchange used a similar technology.

    Exchange Database Technologies (Simple Talk)

    Had Exchange used something different (a NoSQL system for instance) then different rules might apply.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •