Page 434 of 726« First...102030...432433434435436...440450460...Last »

The Seniority Index feature in the Hierarchical Address Book does not work as expected in Exchange Server 2010

Consider the following scenarios.

Scenario 1

  • You install Microsoft Exchange Server 2010 on a member server.
  • You install the Hierarchical Address Book feature (HAB).
  • You create a mailbox for a user on the member server.
  • The user starts Microsoft Outlook 2010 or Microsoft Office Outlook 2007.
  • The user clicks the Organization tab in the Address Book.

In this scenario, information is displayed in HAB as expected. However, sorting on the Seniority Index component does not work.

Scenario 2

  • You install Microsoft Exchange Server 2010 Service Pack 1 (SP1) on a member server.
  • You install the Hierarchical Address Book feature (HAB).
  • You create a mailbox for a user on the member server.
  • The user starts Microsoft Outlook 2010 or Microsoft Office Outlook 2007.
  • The user opens the Address Book.

In this scenario, the Organization tab is not displayed as expected.

To resolve this issue, install Microsoft Exchange Server 2010 Service Pack 2 (SP2). For more information about Exchange Server 2010 SP2, visit the following Microsoft website:
For more information about how to install HAB, see the following articles in the Microsoft Knowledge Base:
973788 

(http://support.microsoft.com/kb/973788/en-us/
)
How to extend the Active Directory schema for the Hierarchical Address Book (HAB) on an Exchange Server 2010 server
973994 

(http://support.microsoft.com/kb/973994/en-us/
)
How to enable the Hierarchical Address Book feature in Microsoft Exchange Server 2010

Read more here:
The Seniority Index feature in the Hierarchical Address Book does not work as expected in Exchange Server 2010

Tuning the Performance and Scalability of ASP Web Applications

This article provides some generic information about possible performance-enhancement settings that may be helpful to tune Internet Information Server (IIS) 5.0. The default settings for Internet Information Services 5.0 are adequate for most uses. When you host sites serving a large number of users, tuning the parameters listed in the “More Information” section of this article may help to increase performance. All changes should be verified on a test computer before you make changes to a production computer.

AspProcessorThreadMax

The AspProcessorThreadMax metabase property specifies the maximum number of worker threads per processor that IIS creates. The setting can dramatically influence the scalability of your Web applications and the performance of your server in general. Because it defines the maximum number of ASP requests that can run simultaneously, this setting should remain at the default unless your ASP applications are making long-running calls to external components. By default, AspProcessorThreadMax is set to 25.

AspRequestQueueMax

The AspRequestQueueMax metabase property specifies the maximum number of concurrent ASP requests that are permitted into the queue. Any client browsers attempting to request ASP files when the queue is full are given an HTTP 500 “Server too busy” error message. By default, AspRequestQueueMax is set to 3000.

AspQueueConnectionTestTime

IIS places all ASP requests into a queue. If the request has been queued for longer than the number of seconds specified by the AspQueueConnectionTestTime metabase property, ASP checks to determine whether the client is still connected before it executes the request. If the client is no longer connected, the request is not processed and is deleted from the queue. You can use the AspQueueConnectionTestTime metabase property to make sure that IIS does not waste time processing a request that has been abandoned by the user. By default, AspQueueConnectionTestTime is set to 3.

AspScriptEngineCacheMax

The AspScriptEngineCacheMax property specifies the maximum number of scripting engines that ASP pages will keep cached in memory. By default, AspScriptEngineCacheMax is set to 125.

AspSessionTimeOut

The AspSessionTimeOut property specifies the default amount of time (in minutes) that a session object is maintained after the last request associated with the object is made. AspSessionTimeOut can be used to tune your ASP applications. Because session objects consume some memory resources, limiting the lifetime of an individual session with this property makes your applications more scalable. By default, AspSessionTimeOut is set to 20.

WARNING: Modifying the metabase incorrectly can cause serious problems that may require you to reinstall IIS 5.0. Microsoft cannot guarantee that problems resulting from incorrectly modifying the metabase can be resolved. Modify the metabase at your own risk.

Run the Adsutil.vbs utility from the <%SYSTEMDRIVE%>inetpubadminScripts
directory. For example, to reconfigure the AspRequestQueueMax metabase property, type the following command:

adsutil.vbs set w3svc/AspRequestQueueMax 
				

Where is the number of requests that ASP should use per processor.

Note: For all entries, these settings change the value at the Master WWW Properties level, where they are inherited by all new Web applications and all existing applications that have not explicitly set a different value.

For additional information, click the article numbers below
to view the articles in the Microsoft Knowledge Base:

300672 

(http://support.microsoft.com/kb/300672/EN-US/
)
HOW TO: Create a Metabase Backup in IIS 5
238583 

(http://support.microsoft.com/kb/238583/EN-US/
)
How to Tune the ASPProcessorThreadMax
233477 

(http://support.microsoft.com/kb/233477/EN-US/
)
PRB: Session.Timeout Has a Max of 24 Hours

See more here:
Tuning the Performance and Scalability of ASP Web Applications

How to upload files to a Web server by using ASP

Article ID: 299692 – Last Review: January 4, 2012 – Revision: 7.0

This article was previously published under Q299692

For a Microsoft Visual Basic .NET version of this article, see 315832 

(http://support.microsoft.com/kb/315832/
)
.

This article describes how to enable your Web server to
receive file transfers from Microsoft Active Server Pages (ASP) pages by using
a server-side Microsoft COM+ component.

NOTE: Microsoft Support boundaries for Visual Basic 6 development have changed. For more information, please see http://msdn.microsoft.com/en-us/vstudio/ms788708.
(http://msdn.microsoft.com/en-us/vstudio/ms788708)

Requirements

  1. Microsoft Windows 2000 with Microsoft Internet Information
    Server 5.0 (IIS) installed and configured
  2. If your development computer is a different computer than
    the server, you must have a valid network or Internet connection to the server that
    hosts the ASP pages.

Microsoft Visual Basic 6 Project Setup and Code

  1. Start Visual Basic, and then start a new ActiveX DLL
    project.
  2. Name the project
    ASPFileUpload.
  3. Change the name of Class1 to
    File.
  4. On the Project menu, click References.
  5. In the References dialog box, click to select the following options, and then click OK:
    • Visual Basic For Applications
    • Visual Basic runtime objects and procedures
    • Visual Basic objects and procedures
    • OLE Automation
    • COM+ Services Type Library
    • Microsoft Active Server Pages Object Library
    • Microsoft Scripting Runtime
  6. On the Project menu, click ASPFileUpload Properties.
  7. In the Project Properties dialog box, click to select Unattended Execution and Retained In Memory, and then click OK.
  8. Paste the following code to File.cls:
    Option Explicit
    
    Const ERR_INVALID_FILENAME = vbObjectError + 1000
    Const ERR_INVALID_TARGET = vbObjectError + 1001
    Const ERR_FILE_EXISTS = vbObjectError + 1002
    Const ERR_UPLOAD_CALLED = vbObjectError + 1003
    Const VB_ERR_PATH_NOT_FOUND = 76
    
    Private m_objContext As ObjectContext
    Private m_objRequest As ASPTypeLibrary.Request
    
    Private m_strTarget As String
    Private m_strFileName As String
    Private m_blnOverWrite As Boolean
    Private m_blnUploaded As Boolean
    Private m_lngTotalBytes As Long
    
    'All other form elements go here.
    Private m_formCol As Scripting.Dictionary
    
    Implements ObjectControl
    
    Private Function ObjectControl_CanBePooled() As Boolean
      ObjectControl_CanBePooled = False
    End Function
    
    Private Sub ObjectControl_Activate()
      Set m_objContext = GetObjectContext()
      Set m_objRequest = m_objContext("Request")
      Set m_formCol = New Scripting.Dictionary
    End Sub
    
    Private Sub ObjectControl_Deactivate()
      Set m_objContext = Nothing
      Set m_objRequest = Nothing
      Set m_formCol = Nothing
    End Sub
    
    Public Sub Upload()
    
      Const DEFAULT_CHUNK_SIZE = 262144 '256kb
    
      Dim bytBeginOfChunk() As Byte
      Dim bytEndOfChunk() As Byte
      Dim bytBeginOfName() As Byte
      Dim bytEndOfName() As Byte
      Dim bytBeginOfFile() As Byte
      Dim bytEndOfFile() As Byte
      Dim bytBeginOfValue() As Byte
      Dim bytEndOfValue() As Byte
      Dim bytName() As Byte
      Dim bytValue() As Byte
      Dim bytThisChunk() As Byte
      Dim bytFileName() As Byte
      Dim lngBeginOfChunk As Long
      Dim lngEndOfChunk As Long
    
      Dim lngBeginOfAttribute As Long
      Dim lngEndOfAttribute As Long
      Dim lngBeginOfValue As Long
      Dim lngEndOfValue As Long
      Dim blnEndOfData As Boolean
      Dim lngChunkSize As Long
      Dim lngBytesLeft As Long
      Dim lngFileNum As Long
      Dim strFileName As String
    
      On Error GoTo UploadErr
    
      If Uploaded Then
        Err.Raise ERR_UPLOAD_CALLED, App.Title, "The Upload method has already been called."
      End If
    
      bytBeginOfChunk = StrConv("-----------------------------", vbFromUnicode)
      bytEndOfChunk = StrConv("-----------------------------", vbFromUnicode)
    
      bytBeginOfName = StrConv("name=", vbFromUnicode) & ChrB(34)
      bytEndOfName = ChrB(34)
    
      bytBeginOfFile = StrConv("filename=", vbFromUnicode) & ChrB(34)
      bytEndOfFile = ChrB(34)
    
      bytBeginOfValue = ChrB(13) & ChrB(10) & ChrB(13) & ChrB(10)
      bytEndOfValue = ChrB(13) & ChrB(10) & StrConv("-----------------------------", vbFromUnicode)
    
      'Initialize the chunk size.
      If m_objRequest.TotalBytes <= DEFAULT_CHUNK_SIZE Then
        lngChunkSize = m_objRequest.TotalBytes
      Else
        lngChunkSize = DEFAULT_CHUNK_SIZE
      End If
    
      'Get the chunk from the request object.
      bytThisChunk = m_objRequest.BinaryRead(CVar(lngChunkSize))
    
      'Initialize the value.
      lngBeginOfChunk = 1
    
      'Repeat until the end of the data.
      Do While Not blnEndOfData
        'Begin the chunk.
        lngBeginOfChunk = InStrB(lngBeginOfChunk, bytThisChunk, bytBeginOfChunk) + UBound(bytBeginOfChunk)
    
        'Get name of the item.
        lngBeginOfAttribute = InStrB(lngBeginOfChunk, bytThisChunk, bytBeginOfName) + UBound(bytBeginOfName) + 1
        lngEndOfAttribute = InStrB(lngBeginOfAttribute, bytThisChunk, bytEndOfName)
        bytName = MidB(bytThisChunk, lngBeginOfAttribute, lngEndOfAttribute - lngBeginOfAttribute)
    
        'Get the value of the item.
        lngBeginOfValue = InStrB(lngEndOfAttribute, bytThisChunk, bytBeginOfValue, vbBinaryCompare) + UBound(bytBeginOfValue) + 1
        lngEndOfValue = InStrB(lngBeginOfValue, bytThisChunk, bytEndOfValue, vbBinaryCompare)
    
        If lngEndOfValue = 0 Then
          'The item extends the past current chunk.
          bytValue = MidB(bytThisChunk, lngBeginOfValue, lngChunkSize)
        Else
          'The item value exists in the current chunk.
          bytValue = MidB(bytThisChunk, lngBeginOfValue, lngEndOfValue - lngBeginOfValue)
        End If
    
        If UCase(StrConv(bytName, vbUnicode)) = "FILE" Then
          lngBeginOfAttribute = InStrB(lngBeginOfChunk, bytThisChunk, bytBeginOfFile, vbBinaryCompare) + UBound(bytBeginOfFile) + 1
          lngEndOfAttribute = InStrB(lngBeginOfAttribute, bytThisChunk, bytEndOfFile, vbBinaryCompare)
    
          bytFileName = MidB(bytThisChunk, lngBeginOfAttribute, lngEndOfAttribute - lngBeginOfAttribute)
    
          If UBound(bytFileName) < 0 Or UBound(bytValue) < 0 Then
            Err.Raise ERR_INVALID_FILENAME, App.Title, "Invalid File Name."
          End If
    
          If Me.Target = "" Then
            Err.Raise ERR_INVALID_TARGET, App.Title, "Invalid Target."
          End If
    
          'Use the original file name.
          If Me.FileName = "" Then
    
            'Trim the path from the file name.
            While InStrB(1, bytFileName, StrConv("", vbFromUnicode), vbBinaryCompare) > 0
              bytFileName = MidB(bytFileName, InStrB(1, bytFileName, StrConv("", vbFromUnicode)) + 1)
            Wend
    
            'Set the property.
            Me.FileName = StrConv(bytFileName, vbUnicode)
    
            'Convert the byte to Unicode.
            strFileName = Me.Target & Me.FileName
    
          Else
            strFileName = Me.Target & Me.FileName
          End If
    
          'Check for overwrite.
          If Me.OverWrite Then
            'This is the hack check. Make sure that wildcard characters cannot be used.
            If Not InStr(1, strFileName, "*") Then
              If FileExists(strFileName) Then
                Kill strFileName
              End If
            Else
              Err.Raise ERR_INVALID_FILENAME, App.Title, "The specified file name appears to be invalid."
            End If
          Else
            If FileExists(strFileName) Then
              Err.Raise ERR_FILE_EXISTS, App.Title, "The file already exists."
            End If
          End If
    
          lngFileNum = FreeFile
    
          Open strFileName For Binary Access Write As #lngFileNum
    
          'Write the file to the destination directory.
          Put #lngFileNum, , bytValue
    
          'This chunk is empty. Therefore, get a new chunk.
          lngBytesLeft = m_objRequest.TotalBytes - lngChunkSize
    
          'Start the chunking machine.
          Do While lngBytesLeft > 0
    
            'Get a new chunk.
            bytThisChunk = m_objRequest.BinaryRead(CVar(lngChunkSize))
    
              lngEndOfValue = InStrB(1, bytThisChunk, bytEndOfValue, vbBinaryCompare)
    
              If lngEndOfValue > 0 Then
                'The item value exists in the current chunk.
                bytThisChunk = MidB(bytThisChunk, 1, lngEndOfValue - 1)
              End If
    
              'Append the chunk to the file.
              Put #lngFileNum, , bytThisChunk
    
              lngBytesLeft = lngBytesLeft - lngChunkSize
    
              If lngBytesLeft < lngChunkSize Then
                lngChunkSize = lngBytesLeft
              End If
            Loop
    
            Close #lngFileNum
    
            TotalBytes = FileLen(strFileName)
    
         ' Exit Do
         Else
          If UCase(StrConv(bytName, vbUnicode)) = "SAVEAS" Then
           Me.FileName = StrConv(bytValue, vbUnicode)
          Else
           'form field other than file, such as textboxes
           If UBound(bytValue) > 0 And UBound(bytName) > 0 Then
            m_formCol.Add StrConv(bytName, vbUnicode), StrConv(bytValue, vbUnicode)
           Else
            m_formCol.Add StrConv(bytName, vbUnicode), ""
           End If
          End If
         End If
    
        'Get the next chunk.
        lngBeginOfChunk = lngEndOfValue
    
        If InStrB(lngBeginOfChunk, bytThisChunk, bytBeginOfName, vbBinaryCompare) = 0 Then
          blnEndOfData = True
        End If
      Loop
    
      Uploaded = True
    
      Exit Sub
    
    UploadErr:
    
      If Err.Number = VB_ERR_PATH_NOT_FOUND Then
        Err.Raise ERR_INVALID_TARGET, App.Title, "The Target specified does not exist."
      Else
        Err.Raise Err.Number, Err.Source, Err.Description
      End If
    End Sub
    
    Public Property Get Form() As Collection
        Set Form = m_formCol
    End Property
    Public Property Get FileName() As String
      FileName = m_strFileName
    End Property
    
    Public Property Let FileName(ByVal strNewValue As String)
      If Uploaded Then
        Err.Raise ERR_UPLOAD_CALLED, App.Title, "The Upload method has already been called."
      Else
        m_strFileName = strNewValue
      End If
    End Property
    
    Public Property Get OverWrite() As Boolean
      OverWrite = m_blnOverWrite
    End Property
    
    Public Property Let OverWrite(ByVal blnNewValue As Boolean)
      If Uploaded Then
        Err.Raise ERR_UPLOAD_CALLED, App.Title, "The Upload method has already been called."
      Else
        m_blnOverWrite = blnNewValue
      End If
    End Property
    
    Private Property Get Uploaded() As Boolean
      Uploaded = m_blnUploaded
    End Property
    
    Private Property Let Uploaded(ByVal blnNewValue As Boolean)
      m_blnUploaded = blnNewValue
    End Property
    
    Public Property Get Target() As String
      Target = m_strTarget
    End Property
    
    Public Property Let Target(ByVal NewValue As String)
      If Uploaded Then
        Err.Raise ERR_UPLOAD_CALLED, App.Title, "The Upload method has already been called."
      Else
        m_strTarget = NewValue
      End If
    End Property
    
    Private Function FileExists(ByVal FileName As String) As Boolean
      On Error GoTo FileExistsErr
    
      FileLen FileName
      FileExists = True
      Exit Function
    
    FileExistsErr:
      If Err.Number = VB_ERR_PATH_NOT_FOUND Then
        FileExists = False
      End If
    End Function
    
    Public Property Get TotalBytes() As Long
      TotalBytes = m_lngTotalBytes
    End Property
    
    Private Property Let TotalBytes(ByVal NewValue As Long)
      m_lngTotalBytes = NewValue
    End Property
    

  9. Compile the project

ASP Code

  1. Paste the following code to an editor such as Notepad or
    Microsoft Visual Interdev, and then save it as
    PostFile.asp:
    <%@ Language=VBScript %>
    
    
    
    
    

  2. Copy the following code to an editor such as Notepad or
    Visual Interdev, and then save it as UploadFile.asp:
    <%@ Language=VBScript %>
    <%
      '//////////////////////////////////////////////////////////////////////////////////
      '//  ASPFileUpload.File API
      '//
      '//  Properties
      '//     FileName
      '//       - Read/Write
      '//       - The file will be saved with this file name.
      '//       - This property can only be set before calling Upload.
      '//       - If no value is specified, the original file name
      '//       - in the HTTP post will be used.
      '//
      '//     OverWrite
      '//       - Read/Write
      '//       - This property can only be set before calling Upload.
      '//       - If set to false and if the destination file exists, an error
      '//       - is raised. The default value is False.
      '//
      '//     Target
      '//       - Read/Write
      '//       - The file will be written to this folder.
      '//       - This property can only be set before calling Upload.
      '//       - There is no default value for this property and it is required.
      '//
      '//      Form
      '//        - ReadOnly
      '//        - Scripting.Dictionary object
      '//        - Can access a specific item by using aspfileupload.Form("item").
      '//        - Acts like the asp form collection.
      '//        - Can enumerate all values in a collection with for each.
      '//        - Only filled after the Upload method is called.
      '//
      '//  Methods
      '//     Upload
      '//       - This method parses the HTTP Post and writes the file.
      '//
      '//  Other
      '//    - ASPFileUpload requires COM+
      '//    - Any call to the Request.Form() collection will cause the Upload
      '//      method to fail as the method references the Binary contents of the
      '//      Request object through the Request.BinaryRead method.
      '//    - Also, if you access a variable in the Request collection without
      '//      specifying the subcollection that it belongs to, the Request.Form collection
      '//      may be searched. This causes an error in the Upload method.
      '//
      '//////////////////////////////////////////////////////////////////////////////////
    
      Dim strMsg 'As String
    
     ' On Error Resume Next
      dim fuFile
      set fuFile = server.CreateObject("aspFileupload.file")
      'Set the destination folder.
      fuFile.Target = "C:TEMPAspFileUpload"
      fuFile.Upload
    
      If Err.number = 0 Then
        strMsg = fuFile.FileName  & " was uploaded successfully."
      Else
        strMsg = "An error occurred when uploading your file: " & Err.Description
      End If
      for each o in fuFile.Form
    	Response.Write o  & "
    " next Response.Write fuFile.Form.item("text1") & " : " & fuFile.Form.item("text2") ' Response.Write Request.Form("test") set fufile = nothing %> <%=strMsg%>

Set Up the Server

  1. Create a folder on the Web server that will receive the
    uploaded files, such as
    C:TEMPAspFileUpload.
  2. Copy the ASPFileUpload.dll file to the Web server, and then
    register it by using the following command at the command prompt:

    regsvr32 PathToDLLASPFileUpload.dll

  3. Apply file permissions (Write access) for the users who you want to be able to upload the files.
  4. Click Start, point to
    Settings, and then click Control
    Panel
    .
  5. In Control Panel, click Administrative
    Tools
    , and then click Component Services to open
    Component Services in the Microsoft Management Console (MMC).
  6. Expand the Component Services node, the
    Computers node, the My Computer node, and the
    COM+ Applications node.
  7. Right-click the
    node, point to New, and then click
    Application.
  8. In the Install or Create a New Application dialog box, click Create an empty application,
    name the application, make sure that you click to select Server
    application
    , and then click Next.
  9. In the Set Application Identity dialog
    box, click This User, and then type the credentials for the
    appropriate user account. The user account must have Write access to the folder
    that will receive the uploaded file.
  10. Click Finish.
  11. Expand the node that you have just created for this
    application.
  12. Right-click the nod, point to New, and
    then click Component.
  13. Click Install new components,
    and locate the folder where you have saved and registered the .dll file, click
    the file, click Next, and then click
    Finish.
  14. Copy the Postfile.asp file and the Uploadfile.asp file to
    your Web root folder. By default, the Web root folder is
    C:InetpubWwwroot.
  15. Edit the target folder of Uploadfile.asp to reflect the
    folder that you created in step 1. The target folder assignment is located in
    the following line of code:
    fuFile.Target = "C:TEMPAspFileUpload"
    					

Upload a File

  1. In a Web browser, open the Postfile.asp page at the
    following URL:

    http://YourWebServer/Postfile.asp

  2. Select a file that you want to upload, and then click
    Upload.
  3. Check your upload folder. The file that you uploaded appears in this folder.

Troubleshooting

  • If you do not type a file name, and if you try to submit
    the Postfile.asp page, you receive a generic, server-side error message. You
    may want to modify the code to provide a more friendly error message on either
    the client side or on the server side.
  • If you require high volume upload capacity, Microsoft
    recommends that you buy or build a compiled, multithreaded component that can
    more efficiently handle the load than this Visual Basic component.
  • A potential security risk exists whenever you allow users
    to upload files to your Web server. This is especially true if your server is
    on the Internet, and if you allow anonymous uploads. You must correctly
    configure Windows permissions and IIS user authentication to make sure that you
    give users only the access that they require. This is important so that you do not
    allow users a way to gain access by bypassing the security controls of your
    system.


APPLIES TO
  • Microsoft Active Server Pages 4.0
  • Microsoft Internet Information Services 5.0
kbaspobj kbcodesnippet kbconfig kbdeployment kbfile kbfso kbGuidelines kbhowto kbsample kbscript kbsecurity kbserver kbsetup kbwebserver KB299692

Other Resources

Other Support Sites

Community

Get Help Now

Article Translations

View original post here:
How to upload files to a Web server by using ASP

How To Dynamically Include Files in Active Server Pages

Since Active Server Pages (ASP) pages are compiled and executed before
being sent to the client (as static HTML), trying to use a variable in
place of a file name in a Server Side Include () fails. To include a file in your ASP page, you could include
code similar to the following that reads in a file and displays it.
<% ' The name of the file to display was passed by a form using GET method

      infil = Request.QueryString("file")

      If infil <&>"" then

         set fso = Server.CreateObject("Scripting.FileSystemObject")
         set fil = fso.OpenTextFile(infil)

         outstring = fil.ReadAll

         ' PRE tags preserve the format of the file

         Response.write "
" & outstring & "

"

End If
%>

The dynamically included file may contain any client-side code you wish,
including HTML and JavaScript. However, ASP will NOT process server-side
script in the file. This is because all the ASP code has already run when
it includes the file and the server will not go back to read anything for
server-side processing again.

For additional information, please see the following article in the
Microsoft Knowledge Base:

172024 

(http://support.microsoft.com/kb/172024/EN-US/
)

INFO: Server Side Include Directives Not Processed by ASP

Original post:
How To Dynamically Include Files in Active Server Pages

Meeting attendees may be unable to see application sharing in Live Meeting 2007 if the meeting presenter’s computer is configured to use more than one monitor

Meeting attendees may be unable to see application sharing in Microsoft Office Live Meeting 2007 if the meeting presenter’s computer is configured to use more than one monitor.
Currently, Live Meeting 2007 does not support the configuration of multiple monitors on a computer that is used to perform application sharing.
To let the meeting attendees see application sharing in Live Meeting 2007, the presenter must perform application sharing on the primary monitor. To do this, the presenter may have to disable the second monitor or the third monitor.

For more information about how to use multiple monitors in Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:

307873 

(http://support.microsoft.com/kb/307873/
)

How to configure and use multiple monitors in Windows XP

Read the article:
Meeting attendees may be unable to see application sharing in Live Meeting 2007 if the meeting presenter’s computer is configured to use more than one monitor

Error message when you try to upload a .pdf file to a meeting in Live Meeting 2007: "Live Meeting cannot automatically import this document into a Live Meeting resource"

When you try to upload a Portable Document Format (.pdf) file to a meeting in Microsoft Office Live Meeting 2007, you receive the following error messages:

“Live Meeting cannot automatically import this document into a Live Meeting resource.”

“To import this document, you must open it in its native application and print the document, choosing ‘Microsoft Office Live Meeting Document Writer’
as the printer. You can then import the .mdi file into your Live Meeting.”

This issue may occur if Adobe Acrobat Reader 7.0 is installed on the computer.
To work around this issue, follow these steps:
  1. Open the .pdf file in Adobe Acrobat Reader 7.0.
  2. On the File menu, click Print.
  3. In the list of printers, click Microsoft Office Live Meeting Document Writer, and then click OK. The Save As dialog box appears.

    Note You can accept the default file name and storage location. Or, you can change these values. Do not change the default Microsoft Document Imaging Format (*.mdi) file type.

  4. Click Save. You can close the .pdf file when the conversion is completed.

    Note The new file will have an .mdi file name extension. Additionally, the file icon will show the image of a scanner. The original .pdf file will not be overwritten.

  5. Log on to the Live Meeting 2007 conference center as an organizer.
  6. On the My Home page, click the name of the meeting that you want to edit under Upcoming Meetings to display the Meeting Details page.
  7. On the Meeting Details page, click Join As Presenter under Actions to start the Live Meeting 2007 console.
  8. In the Live Meeting 2007 console, click Share Document to view on the Share menu. Or, click Import a document on the toolbar.
  9. In the Files of Type list, click Microsoft Office Document Image Format Files.
  10. Locate the folder in which you saved the new .mdi file, click the .mdi file, and then click Open to upload the .mdi file to the meeting in Live Meeting 2007.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

More:
Error message when you try to upload a .pdf file to a meeting in Live Meeting 2007: "Live Meeting cannot automatically import this document into a Live Meeting resource"

You may be unable to upload a PowerPoint presentation to a meeting in Live Meeting 2007 if the presentation contains slides that were made by using the Live Meeting 2005 Add-in for PowerPoint

When you try to upload a PowerPoint presentation that is created by using the Live Meeting 2005 Add-in for PowerPoint to a Microsoft Office Live Meeting 2007 meeting, you may receive the following error message:

Uploading PowerPoint files that were created using the Microsoft Office Live Meeting 2005 Add-in for PowerPoint is not supported with this version of Live Meeting. Remove the Live Meeting resource slides from the file, and then try again to upload it.

This issue occurs because the Live Meeting 2007 console does not support uploading PowerPoint presentations that include Live Meeting slides that are created by using the Live Meeting 2005 Add-in for PowerPoint.
To resolve this issue, use one of the following methods.

Method 1

Use the Live Meeting 2005 Add-in for PowerPoint to convert the presentation to an .lmp file. Then, upload the converted file to a meeting by using the Live Meeting Web interface. To do this, follow these steps:

  1. Open the presentation in PowerPoint.
  2. On the Live Meeting Presentation menu, click Export.
  3. In the Export dialog box, select .lmp from the Save as type list.
  4. Log on to the conference center Live Meeting Manager.
  5. Under the Manage section, click Meetings.
  6. On the Manage Meetings page, click the meeting for which you want to upload the PowerPoint presentation. The Meeting Details page appears.
  7. On the Meeting Details page, under the Actions section, click Upload Files.
  8. Click Browse to locate and select the .lmp file that you saved in step 3.
  9. Click Upload.

    The PowerPoint presentation that contains special slides are uploaded to the meeting. These special slides may include Poll slides, Web slides, or other slides.

Method 2

Use the Live Meeting console to manually create and add the Live Meeting slides to an existing PowerPoint presentation. These slides may include Poll slides, Web slides, or other slides.

To create and add Live Meeting slides to an existing PowerPoint presentation by using the Live Meeting console, follow these steps:

  1. Remove all the Live Meeting slides from the PowerPoint presentation.
  2. Join the meeting as a presenter.
  3. In the content pane, click Share, click Add File to Meeting, and then click Upload File (View Only) to upload the PowerPoint presentation.
  4. In the content pane, click the PowerPoint presentation to which you want to add a collaborative slide, and then click Thumbnails.
  5. In the thumbnails pane, right-click the thumbnail directly above the point where you want to insert the slide, click Insert New Slide, and then click the type of slide that you want to add. The slide is added under the pointer.

    Note The types of slides that you can select include Whiteboard, Poll, Text, Web, and Screen Snapshot.

Link:
You may be unable to upload a PowerPoint presentation to a meeting in Live Meeting 2007 if the presentation contains slides that were made by using the Live Meeting 2005 Add-in for PowerPoint

Troubleshooting basics for Lync Online and Office Communicator in a dedicated Business Productivity Online Suite environment

Article ID: 2649420 – Last Review: January 4, 2012 – Revision: 2.0

Summary

This document describes the troubleshooting basics for Microsoft Lync Online and Microsoft Office Communicator in a dedicated Business Productivity Online environment.

More Information

Initial response process

  1. Make sure that the Office Communications Server (OCS) escalation template is completely filled out.
  2. Verify that the .uccapilog files and the .etl log files are provided.
  3. If the template and the files that are mentioned in step 1 and step 2 are not provided, the SR will be rejected. However, there are some exceptions: 
    • Contacts and ACL restore requests
    • Lync Online Archiving Retrieval requests, if a completed template is supplied
    • Manual provisioning, if a completed manual provisioning template is supplied
    • CWA/OWA Lync IM issues

Process to follow for common scenarios

  • For Lync Online and for Office Communicator archiving retrieval requests, view the following article:  
    2649373 

    (http://support.microsoft.com/kb/2649373/
    )
    How to retrieve archived conversations from Lync Online in a dedicated Business Productivity Online Suite environment
  • For manual provisioning requests, view the following article:
    2643097 

    (http://support.microsoft.com/kb/ 2643097/
    )
    Communicator or Lync SIP address issues make manual provisioning necessary in a dedicated Business Productivity Online Suite environment

  • For OWA/CWA issues, view the following article:
    2617097 

    (http://support.microsoft.com/kb/2617097/
    )
    You cannot start or receive a Lync chat through OWA in a dedicated Business Productivity Online Suite environment
  • If you are unsure about how to collect the log files, refer to the following articles:
    • For Office Communicator
      (http://office.microsoft.com/en-us/communicator-help/sign-in-to-communicator-HA010289983.aspx)
    • For Lync Online
      (http://office.microsoft.com/en-us/communicator-help/set-logging-options-HA102758576.aspx?CTT=1)


Initial troubleshooting process

  1. Compare the Active Directory Domain Services (AD DS) attributes from the source AD DS and the managed AD DS.

    The following source AD DS attributes have to match their respective attributes in the managed AD DS:

    • The Object SID in the source AD DS has to match the msRTCSIP-OriginatorSid in the managed AD DS.
    • The Extensionattribute(xx) value as indicated in the MMSSPP provisioning interfaces document has to match in both source and managed AD DS. You can obtain a copy of this document from your Technical Account Manager (TAM).

      Note
       The Extensionattribute that your company uses is determined during the deployment of Microsoft Online Services. Refer to your TAM if you are unclear about which attribute to use.
    • The Mail attribute has to match in both the source and managed AD DS.
  2. Open the .UCCAPILOG file in Notepad, and verify that the user is using the minimum supported version of Office Communicator or of Lync:
    • For Office Communicator: The minimum supported version is 3.5.6907.206.

      Collapse this imageExpand this image

    • For Lync: The minimum supported version is 4.0.7577.314.

      Collapse this imageExpand this image



APPLIES TO
  • Microsoft Business Productivity Online Dedicated
  • Microsoft Business Productivity Online Suite Federal
  • Microsoft Office Communicator 2007
  • Microsoft Office Communicator 2007 R2

Other Resources

Other Support Sites

Community

Get Help Now

Original post:
Troubleshooting basics for Lync Online and Office Communicator in a dedicated Business Productivity Online Suite environment

How to extend the Active Directory schema for the Hierarchical Address Book (HAB) on an Exchange Server 2010 server

Article ID: 973788 – Last Review: January 4, 2012 – Revision: 4.0

This article describes how to implement the Active
Directory Domain Services (AD DS) schema changes that are required to support
the Hierarchical Address Book (HAB) feature in Microsoft Exchange Server 2010.

The HAB is an add-in for Exchange Server 2010 and for
Microsoft Outlook 2010 beta. To use the HAB, you must extend the AD DS schema
in the Active Directory forest in which you installed Exchange Server 2010. In order to extend the AD DS schema, you must belong to the Schema Admins
group. The schema classes and attributes that are added to AD DS for the HAB
are compatible with all languages and versions of Exchange server. The HAB
schema extensions for Exchange Server 2010 will also be compatible with
future versions of Exchange server.

To install the HAB Active
Directory add-in, follow these steps:

  1. 1. The LDIFDE tool is required to implement the schema
    changes. The LDIFDE tool is installed when the remote administration tools for
    Windows Server 2008 server are installed. To install the remote administration
    tools, follow these steps on the server:

    1. Click Start, and then click
      Run.
    2. Type ServerManagerCmd -i
      RSAT-ADDS
      in the Open field, and then click
      OK.
  2. Copy the following schema change script to a text file that
    is named “schema_file.txt” for later use. Make sure that the first line of the
    file is blank.
    dn: CN=ms-DS-Phonetic-Display-Name,DC=X
    changetype: ntdsSchemaAdd
    adminDescription: ms-DS-Phonetic-Display-Name
    adminDisplayName: ms-DS-Phonetic-Display-Name
    attributeID: 1.2.840.113556.1.4.1946
    attributeSecurityGuid:: VAGN5Pi80RGHAgDAT7lgUA==
    attributeSyntax: 2.5.5.12
    isSingleValued: TRUE
    lDAPDisplayName: msDS-PhoneticDisplayName
    mapiId: 35986
    name: ms-DS-Phonetic-Display-Name
    oMSyntax: 64
    objectCategory: CN=Attribute-Schema,DC=X
    objectClass: attributeSchema
    rangeLower: 0
    rangeUpper: 256
    schemaIdGuid:: 5JQa4mYt5UyzDQ74endv8A==
    searchFlags: 5
    showInAdvancedViewOnly: TRUE
    systemFlags: 16
    systemOnly: FALSE
    
    dn: CN=ms-DS-HAB-Seniority-Index,DC=X
    changetype: ntdsSchemaAdd
    adminDescription: Contains the seniority index as applied by the organization where the person works.
    adminDisplayName: ms-DS-HAB-Seniority-Index
    attributeID: 1.2.840.113556.1.4.1997
    attributeSecurityGuid:: VAGN5Pi80RGHAgDAT7lgUA==
    attributeSyntax: 2.5.5.9
    isMemberOfPartialAttributeSet: TRUE
    isSingleValued: TRUE
    lDAPDisplayName: msDS-HABSeniorityIndex
    mapiId: 36000
    name: ms-DS-HAB-Seniority-Index
    oMSyntax: 2
    objectCategory: CN=Attribute-Schema,DC=X
    objectClass: attributeSchema
    schemaIdGuid:: 8Un03jv9RUCYz9lljaeItQ==
    searchFlags: 1
    showInAdvancedViewOnly: TRUE
    systemFlags: 16
    systemOnly: FALSE
    
    dn: CN=ms-Exch-HAB-Root-Department-Link,DC=X
    changetype: ntdsSchemaAdd
    adminDescription: ms-Exch-HAB-Root-Department-Link
    adminDisplayName: ms-Exch-HAB-Root-Department-Link
    attributeID: 1.2.840.113556.1.4.7000.102.50824
    attributeSyntax: 2.5.5.1
    isMemberOfPartialAttributeSet: FALSE
    isSingleValued: TRUE
    lDAPDisplayName: msExchHABRootDepartmentLink
    mapiId: 35992
    name: ms-Exch-HAB-Root-Department-Link
    oMSyntax: 127
    oMObjectClass:: KwwCh3McAIVK
    objectCategory: CN=Attribute-Schema,DC=X
    objectClass: attributeSchema
    linkID: 1092
    schemaIdGuid:: f/ewOgOh9UeAbUpAzOY4qg==
    searchFlags: 0
    
    dn: CN=ms-Exch-HAB-Root-Department-BL,DC=X
    changetype: ntdsSchemaAdd
    adminDescription: ms-Exch-HAB-Root-Department-BL
    adminDisplayName: ms-Exch-HAB-Root-Department-BL
    attributeID: 1.2.840.113556.1.4.7000.102.50826
    attributeSyntax: 2.5.5.1
    isMemberOfPartialAttributeSet: FALSE
    isSingleValued: FALSE
    lDAPDisplayName: msExchHABRootDepartmentBL
    mapiId: 35995
    name: ms-Exch-HAB-Root-Department-BL
    oMSyntax: 127
    oMObjectClass:: KwwCh3McAIVK
    objectCategory: CN=Attribute-Schema,DC=X
    objectClass: attributeSchema
    linkID: 1093
    schemaIdGuid:: jIKVD70qh0CwJo98xedSpA==
    searchFlags: 0
    
    dn: CN=ms-Org-Group-Subtype-Name,DC=X
    changetype: ntdsSchemaAdd
    adminDescription: ms-Org-Group-Subtype-Name
    adminDisplayName: ms-Org-Group-Subtype-Name
    attributeID: 1.2.840.113556.1.6.47.2.3
    attributeSyntax: 2.5.5.12
    isMemberOfPartialAttributeSet: TRUE
    isSingleValued: TRUE
    lDAPDisplayName: msOrg-GroupSubtypeName
    mapiId: 36063
    name: ms-Org-Group-Subtype-Name
    oMSyntax: 64
    objectCategory: CN=Attribute-Schema,DC=X
    objectClass: attributeSchema
    rangeUpper: 128
    schemaIdGuid:: RFjt7cOzw0Gp5omEtSt/mA==
    searchFlags: 17
    
    dn: CN=ms-Org-Is-Organizational-Group,DC=X
    changetype: ntdsSchemaAdd
    adminDescription: ms-Org-Is-Organizational-Group
    adminDisplayName: ms-Org-Is-Organizational-Group
    attributeID: 1.2.840.113556.1.6.47.2.1
    attributeSyntax: 2.5.5.8
    isMemberOfPartialAttributeSet: TRUE
    isSingleValued: TRUE
    lDAPDisplayName: msOrg-IsOrganizational
    mapiId: 36061
    name: ms-Org-Is-Organizational-Group
    oMSyntax: 1
    objectCategory: CN=Attribute-Schema,DC=X
    objectClass: attributeSchema
    schemaIdGuid:: C1a3SQdHoEqifOF6Cco/lw==
    searchFlags: 16
    
    dn: CN=ms-Org-Other-Display-Names,DC=X
    changetype: ntdsSchemaAdd
    adminDescription: ms-Org-Other-Display-Names
    adminDisplayName: ms-Org-Other-Display-Names
    attributeID: 1.2.840.113556.1.6.47.2.4
    attributeSyntax: 2.5.5.12
    isMemberOfPartialAttributeSet: TRUE
    isSingleValued: FALSE
    lDAPDisplayName: msOrg-OtherDisplayNames
    mapiId: 36064
    name: ms-Org-Other-Display-Names
    oMSyntax: 64
    objectCategory: CN=Attribute-Schema,DC=X
    objectClass: attributeSchema
    rangeUpper: 128
    schemaIdGuid:: JF+QjxOkWkOO0TU4XsF59w==
    searchFlags: 17
    
    dn: CN=ms-Org-Leaders,DC=X
    changetype: ntdsSchemaAdd
    adminDescription: ms-Org-Leaders
    adminDisplayName: ms-Org-Leaders
    attributeID: 1.2.840.113556.1.6.47.2.2
    attributeSyntax: 2.5.5.1
    isMemberOfPartialAttributeSet: TRUE
    isSingleValued: FALSE
    lDAPDisplayName: msOrg-Leaders
    mapiId: 36062
    name: ms-Org-Leaders
    oMSyntax: 127
    oMObjectClass:: KwwCh3McAIVK
    objectCategory: CN=Attribute-Schema,DC=X
    objectClass: attributeSchema
    linkID: 1208
    schemaIdGuid:: kGdb7lgzqEGT8hNM4h84Ew==
    searchFlags: 16
    
    dn: CN=ms-Org-Leaders-BL,DC=X
    changetype: ntdsSchemaAdd
    adminDescription: ms-Org-Leaders-BL
    adminDisplayName: ms-Org-Leaders-BL
    attributeID: 1.2.840.113556.1.6.47.2.5
    attributeSyntax: 2.5.5.1
    isMemberOfPartialAttributeSet: FALSE
    isSingleValued: FALSE
    lDAPDisplayName: msOrg-LeadersBL
    mapiId: 36060
    name: ms-Org-Leaders-BL
    oMSyntax: 127
    oMObjectClass:: KwwCh3McAIVK
    objectCategory: CN=Attribute-Schema,DC=X
    objectClass: attributeSchema
    linkID: 1209
    schemaIdGuid:: 7Y6lr5imfkGfVvrVQlLF9A==
    searchFlags: 0
    
    dn:
    changetype: ntdsSchemaModify
    replace: schemaUpdateNow
    schemaUpdateNow: 1
    -
    
    dn: CN=Organizational-Person,DC=X
    changetype: ntdsSchemaModify
    add: mayContain
    mayContain: msDS-HABSeniorityIndex
    -
    
    dn: CN=Organizational-Person,DC=X
    changetype: ntdsSchemaModify
    add: mayContain
    mayContain: msDS-PhoneticDisplayName
    -
    
    dn: CN=ms-Exch-Organization-Container,DC=X
    changetype: ntdsSchemaModify
    add: mayContain
    mayContain: msExchHABRootDepartmentLink
    -
    
    dn: CN=Group,DC=X
    changetype: ntdsSchemaModify
    add: mayContain
    mayContain: location
    -
    
    dn: CN=Group,DC=X
    changetype: ntdsSchemaModify
    add: mayContain
    mayContain: thumbnailPhoto
    -
    
    dn: CN=Group,DC=X
    changetype: ntdsSchemaModify
    add: mayContain
    mayContain: msDS-HABSeniorityIndex
    -
    
    dn: CN=Group,DC=X
    changetype: ntdsSchemaModify
    add: mayContain
    mayContain: msDS-PhoneticDisplayName
    -
    
    dn: CN=Group,DC=X
    changetype: ntdsSchemaModify
    add: mayContain
    mayContain: msOrg-GroupSubtypeName
    -
    
    dn: CN=Group,DC=X
    changetype: ntdsSchemaModify
    add: mayContain
    mayContain: msOrg-IsOrganizational
    -
    
    dn: CN=Group,DC=X
    changetype: ntdsSchemaModify
    add: mayContain
    mayContain: msOrg-Leaders
    -
    
    dn: CN=Group,DC=X
    changetype: ntdsSchemaModify
    add: mayContain
    mayContain: msOrg-OtherDisplayNames
    -
    
    dn: CN=Mail-Recipient,DC=X
    changetype: ntdsSchemaModify
    add: mayContain
    mayContain: msDS-HABSeniorityIndex
    -
    
    dn: CN=Mail-Recipient,DC=X
    changetype: ntdsSchemaModify
    add: mayContain
    mayContain: msDS-PhoneticDisplayName
    -
    
    dn: CN=Top,DC=X
    changetype: ntdsSchemaModify
    add: mayContain
    mayContain: msOrg-LeadersBL
    -
    
    dn: CN=Top,DC=X
    changetype: ntdsSchemaModify
    add: mayContain
    mayContain: msExchHABRootDepartmentBL
    -
    
    dn:
    changetype: ntdsSchemaModify
    replace: schemaUpdateNow
    schemaUpdateNow: 1
    -

  3. If your domain controller server is running Windows Server
    2008, go to step 7. For domain controller servers that are running versions of
    Windows that are earlier than Windows Server 2008, the LDIF command requires
    the RootDSE entry. In this case, follow steps 4 through 6.
  4. To write the RootDSE entry to a file, run the following
    command that specifies the server name of the domain controller:
    LDIFDE -f domain_data.txt -s server_name -p BASE
  5. Open the domain_data.txt file
    that you created in step 4, and search for the string that is called “schema.”
    Copy the following text from that section, starting from “CN=schema,” and save it. This text contains the
    RootDSE entry and is used to import the HAB schema extension in step 6. For
    example, the text may resemble the following string in which
    Contoso is used as a placeholder:
    CN=Schema,CN=Configuration,DC=Contoso-dom,DC=Contoso,DC=com
  6. For domain controller servers that are running versions
    Windows that are earlier than Windows Server 2008, run the following command on
    the domain controller server to import the HAB schema extension. This command
    specifies the RootDSE file that you saved in step 5.
    LDIFDE -i -f schema_file.txt -c DC=X 
  7. For Windows Server 2008 only, run the following command on the domain controller server
    to import the HAB schema extension.
    LDIFDE -i -f schema_file.txt -c DC=X #SchemaNamingContext

    Note: The schema changes described in this article have been included in Exchange Server 2010 SP1



APPLIES TO
  • Microsoft Exchange Server 2010 Coexistence
  • Microsoft Exchange Server 2010 Enterprise
  • Microsoft Exchange Server 2010 Standard
kbinfo kbsurveynew kbhowto kbexpertiseadvanced KB973788

Other Resources

Other Support Sites

Community

Get Help Now

Article Translations

Link:
How to extend the Active Directory schema for the Hierarchical Address Book (HAB) on an Exchange Server 2010 server

Audio does not work in Breakout Rooms (BORs)

Audio does not work in Live Meeting Break-Out Rooms (BORs).
Either the meeting configuration is incorrect or the audio bridge does not support BORs.
Meeting Configuration:
1. The meeting must be configured for telephone conferencing (PSTN) only; it cannot be configured for computer audio (VoIP) or hybrid (combination of telephone and computer audio).
2. An Audio Conferencing Provider must be selected; the Conferencing Provider cannot be “Other”.
3. Join Conference (Call Me) must be enabled.
4. All meeting participants need to use the Join Conference feature to have Live Meeting call their phone instead of dialing into the audio bridge.

Collapse this imageExpand this image

Collapse this imageExpand this image

Audio Bridge:
1. The audio bridge must be from an Audio Conferencing Provider certified to support BORs.
2. The audio bridge itself needs to support BORs. If in doubt, ask your Audio Conferencing Provider if the audio bridge/participant code/leader code combination supports Break-Out Rooms.

More:
Audio does not work in Breakout Rooms (BORs)

Page 434 of 726« First...102030...432433434435436...440450460...Last »

Recent Comments

    Archives

    Categories