For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Stephen_Fisher_'s avatar
Stephen_Fisher_
Historic F5 Account
May 07, 2009

Checkbox to authorize Big3d Update is not visible

Posted By gbunting on 05/01/2009 12:47 PM

 

Also, I noticed that when I ran the discovery wizard, the checkbox to authorize Big3d Update was not visible until I clicked on show powershell script.

 

 

 

 

Glen~

 

 

Thanks for posting your issue. Can you attach a screenshot of the Discovery Wizard pane where you cannot see the checkbox to authorize Big3d update?

 

 

What screen resolution are you running?

 

 

Thank you,

 

Stephen
management
microsoft
scom

4 Replies

  • gbunting's avatar
    gbunting
    Icon for Nimbostratus rankNimbostratus
    May 11, 2009
    SFisher,

     

     

    Attached is the screenshot of the Authorize Big3d Update not visible and then after I click Show Powershell script it is partially visible.

     

     

    Thanks,

     

     

    Glen
  • Stephen_Fisher_'s avatar
    Stephen_Fisher_
    Historic F5 Account
    May 11, 2009
    Glen,

     

     

    Thank you for the screenshots.

     

     

    Can you tell me a bit more about your display settings?

     

    - screen resolution

     

    - display font

     

    - normal or high DPI?

     

    - normal or large fonts?

     

     

    Thanks!

     

    Stephen
  • gbunting's avatar
    gbunting
    Icon for Nimbostratus rankNimbostratus
    May 11, 2009
    Stephen,

     

     

    The screen resolution is 1680x970 16 bit colors, Larger scale (120DPI). I'm not sure what the font size is as this is an RDP connection to to a windows 2008 server, but I'm guessing it's large font.

     

     

    Thanks,

     

     

    Glen
  • Stephen_Fisher_'s avatar
    Stephen_Fisher_
    Historic F5 Account
    May 11, 2009
    Glen,

     

     

    Thanks for the info on your display. We have identified the display bug ~ exposed by the 120 DPI setting. We don't have a good workaround for you, other than to change to 96 DPI for the moment. We should have a fix in our next release in a couple weeks.

     

     

    Thanks for narrowing down the issue,

     

    Stephen