Dual monitor not working in 2012R2 essentials anywhere access

Hi
I tried to connect to 2012R2 Ess anywhere access (Remote portal) from a W7Pro client using two monitors.
Only one monitor gets used though. Can Anywhere Access be configured to enable dual monitor use in RDP sessions?
Many thanks
Rgds
Willem

Hi Willem,
As per my research, dual monitor is supported but for that to get access you need to have Windows 7 Enterprise or Ultimate version. Win 7 Pro client doesn’t support. 
Apart this issue seems more related to Essential Forum, for detail you can ask in our Essential Forum over here for more accurate details.
https://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=winserveressentials
Hope it helps!
Thanks.
Dharmesh Solanki
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Similar Messages

  • Dual monitors not working in bootcamp?

    Recently added 8 more gigs of ram, and after this my video driver shows a triangle with an ! under bootcamp running windows 7,
    i have tried countless times to update the driver to no evail
    even used the bootcamp drivers from the original discs to repair bootcamp and nothing has helped!!
    what can i do?
    before the memory upgrade the monitors worked fine under bootcamp, but now they only show 1 and will not show both!!
    thanks!!
    (possibly a windos 7 issues?)

    The hatter wrote:
    You realize you do need graphic driver, and Nvidia has Windows 7 (32/64), and ATI is suppose to have a universal driver. No mention of what your card is. And I would hope x64.
    Good grief, but please a) don't use Apple drivers, b) always use the "troubleshoot compatibility" for any installer (control+click on the application) before running. Apple is treated as not supported and won't install (now) with build 7077 (after feedback finding it causes errors, love the way their feedback and testing really does work).
    Boot Camp can 'doorstop' in some cases a good installation.
    http://discussions.apple.com/thread.jspa?threadID=1866970&tstart=0
    Use Driver Sweeper and then reinstall the latest compatible driver. And no, dual monitors does work.
    mine is the ati radeon 2600 hd xt and it worked flawlessly up until about 2-4 days ago,
    oh well, xp pro it is then,
    i dont want the headache of dealing with windows 7 beta!
    xp should be fine to use correct?
    will there be any other steps i will need to take in order for everything to function together well?
    thanks

  • Wacom intros5 and dual monitors not working

    I know there are issues with Mavericks, dual monitors & USB, but I have a problem with my Intuos5 tablet: since installing Mavericks it no longer maps to both monitors. Changing settings under monitors and wacom sys prefs does not change anything. It will only map to monitor 1.
    in fact mapping under the wacom sys prefs doesn't seem to work at all.
    Any ideas other than going back to ML or waiting for a new driver?
    Anyone seen behaviour like this?
    Thanks

    The hatter wrote:
    You realize you do need graphic driver, and Nvidia has Windows 7 (32/64), and ATI is suppose to have a universal driver. No mention of what your card is. And I would hope x64.
    Good grief, but please a) don't use Apple drivers, b) always use the "troubleshoot compatibility" for any installer (control+click on the application) before running. Apple is treated as not supported and won't install (now) with build 7077 (after feedback finding it causes errors, love the way their feedback and testing really does work).
    Boot Camp can 'doorstop' in some cases a good installation.
    http://discussions.apple.com/thread.jspa?threadID=1866970&tstart=0
    Use Driver Sweeper and then reinstall the latest compatible driver. And no, dual monitors does work.
    mine is the ati radeon 2600 hd xt and it worked flawlessly up until about 2-4 days ago,
    oh well, xp pro it is then,
    i dont want the headache of dealing with windows 7 beta!
    xp should be fine to use correct?
    will there be any other steps i will need to take in order for everything to function together well?
    thanks

  • Dual monitor not working under Boot Camp on Mac Pro ATI HD 2600 XT

    Recently got a brand new Mac Pro with ATI Radeon HD 2600 XT graphics card.
    On the Mac side (Leopard), everything works perfectly: my second monitor (a plasma screen connected with HDMI to the second DVI of the ATI card via HDMI/DVI adapter) is fully recognized and it works as an extended desktop or in Mirroring mode.
    Under Boot Camp (Windows XP Pro) however, NOTHING: the second monitor always appears in the display properties, but it is grayed out (inactive), and when I try to activate it, it switches back to being grayed out immediately and nothing gets displayed on it.
    After reading all the posts I can find on the topic, I tried the following (in pretty much every possible combination - Thank god for WinClone that allows me to restore the Boot Camp basic install image without having to reinstall Windows from scratch every time):
    a) Bootcamp 2.0 (installed by default by Bootcamp assistant)
    b) Update to Bootcamp 2.1
    1) Windows XP Pro SP2c vanilla install (from my Windows XP pro install disk)
    2) Update to Windows XP SP3 (I tried with and without BC 2.1: both worked -> BC 2.1 didn't seem to be required for SP3 - maybe because this is a mac pro and not a MB or MBP)
    i) ATI drivers installed by default by Boot Camp assistant (BC 2.0) or by BC 2.1
    ii) Latest ATI drivers found on ATI web site specifically under Boot Camp / Mac Pro.
    Note: Interestingly, the catalyst installer worked ok (provided .NET framework 2.0 is installed though), but it seems that the Radeon BootCamp/Mac Pro driver set itself from ATI's web site does NOT include a driver for the HD 2600 XT - so when I install this driver set, it tells me that no compatible hardware was found...
    iii) Latest ATI drivers found under Windows XP (these did include one driver specifically for the Radeon HD 2600 XT)
    NOTHING seems to work. I read posts (most of the from late last year) about ATI Catalyst utility showing a 3rd monitor at some point, but I never got any 3rd monitor showing in any of my many many trials with Catalyst. I have yet to get a single image appear on my plasma under Bootcamp Windows. I don't believe its the hardware because everything works great on the max OS X side.
    I am actually considering switching to an NVidia 8800 GT just to get the dual screen to work under BootCamp/Windows XP because I really need it and I read everywhere that drivers for NVidia are far better than ATI ones.
    Any advice? What should I try next before getting an 8800 ?
    Is there a diagnostic utility that I can use to test my config including the GC?
    Thanks!

    Hi there aside from my laptop I have an iMac 20" with the same HD 2600 XT card. I recently installed the Catalyst 8.6 driver by using a driver mod from driverheaven, I use Vista 32. By installing it this way I got boosted performance and many issues with the bootcamp drivers were fixed. As you may already know the ATI drivers do not install on bootcamped macs usually but the mod tool fixes this. Its unofficial so do so at your own risk but try it out and see if you get the second monitor if not just rollback. Hope this helps and I didn't want to say too much about the 8.6 driver mod because it may not be allowed here but google will provide any answers.

  • Dynadock U3 - Dual monitors not working using Win 7

    So in October i upgraded to Windows 8 when it came out and it didnt work properly with my Dynadock docking station.
    So i downgraded to Windows 7 using a copy i got through my school that didnt have the proper drivers for Satellite laptops.
    So last week i finally got a recovery disk from Toshiba for my laptop and reinstalled windows 7 with all the proper drivers for the laptop.
    After doing this i reinstalled the Toshiba Dynadock Drivers and tried to set it up with my laptop.
    The mouse and keyboard attached to the Dynadock station work properly with the laptop but the external monitor doesnt work at all.
    What can i do to get the external monitor working?
    Btw my BIOS is up to date as is everything else so everything should work properly. it doesnt make any sense....

    Yes it did
    it worked perfectly fine when i originally ran it on windows 7 so i think its a software issue
    but i bought the recovery disk to get my PC back to its state of when i bought it which should be like it was when i originally had it as Windows 7 but it still doesnt work
    also the keyboard and mouse attached to the docking station are a bit glitchy, sometimes it will print out a lot of a letter when i press it once. I hate this and its really getting me annoyed with Toshiba because according to the the technical support i phoned, if i bought the recovery disk, it would get the docking station working properly....
    so now i dished out $38 for a recovery disk for nothing :/
    Message was edited by: AlexB_1

  • [solved] xorg 1.6 - dual-monitor not working any more

    I switched to arch64 and with it came the new xorg 1.6. Now X won't start with the configuaration I used before and I can't figure out what to do about it.
    I want to use two monitors (laptop + external) with an Intel X4500 HD und xf86-video-intel. I found out, that it doesn't like the virtual screen I defined. If I remove that line everything works fine for the laptop-monitor. With the virtual screen defined I get an error in xorg.0.log
    Failed to pin back buffer
    The xorg.conf that worked until now (= my previous arch installation) looks like this:
    Section "ServerLayout"
    Identifier "X.org Configured"
    Screen 0 "Screen0" 0 0
    InputDevice "Mouse0" "CorePointer"
    InputDevice "Keyboard0" "CoreKeyboard"
    EndSection
    Section "Files"
    ModulePath "/usr/lib/xorg/modules"
    FontPath "/usr/share/fonts/misc"
    FontPath "/usr/share/fonts/100dpi:unscaled"
    FontPath "/usr/share/fonts/75dpi:unscaled"
    FontPath "/usr/share/fonts/TTF"
    FontPath "/usr/share/fonts/Type1"
    EndSection
    Section "Module"
    Load "dri"
    Load "dbe"
    Load "record"
    Load "glx"
    Load "dri2"
    Load "extmod"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "kbd"
    EndSection
    Section "InputDevice"
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "Device" "/dev/input/mice"
    Option "ZAxisMapping" "4 5 6 7"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    VendorName "Monitor Vendor"
    ModelName "Monitor Model"
    EndSection
    Section "Device"
    ### Available Driver options are:-
    ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
    ### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
    ### [arg]: arg optional
    #Option "NoAccel" # [<bool>]
    #Option "SWcursor" # [<bool>]
    #Option "ColorKey" # <i>
    #Option "CacheLines" # <i>
    #Option "Dac6Bit" # [<bool>]
    #Option "DRI" # [<bool>]
    #Option "NoDDC" # [<bool>]
    #Option "ShowCache" # [<bool>]
    #Option "XvMCSurfaces" # <i>
    #Option "PageFlip" # [<bool>]
    Identifier "Card0"
    Driver "intel"
    VendorName "Intel Corporation"
    BoardName "Mobile 4 Series Chipset Integrated Graphics Controller"
    BusID "PCI:0:2:0"
    Option "VBEModes" "true"
    Option "EnableAGPDMA"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Card0"
    Monitor "Monitor0"
    SubSection "Display"
    Depth 24
    Modes "1440x900" "1280x1024" "1024x768"
    Virtual 2880 2880 # this line seems to be problematic?
    EndSubSection
    EndSection
    I use "xrandr --output VGA --mode 1280x1024 --left-of LVDS" in .xinitrc to arange the displays.
    So anyone any idea why it won't work?
    Btw: I tried x86-video-intel-legacy. But then X didn't even start
    Last edited by golwin (2009-04-18 21:58:08)

    Ok, I fixed it. Just added
    Option "AccelMethod" "UXA"
    Option "Legacy3D" "False"
    to my device-section in xorg.conf. EXA produces the error above.
    Maybe I'm looking at the wrong point, but could someone give me a hint where I can learn more about UXA/EXA. The problem seems somehow solved, but I'd like to learn more about this and would like to understand what the problem was. Right now I don't even know what makes the difference between UXA and EXA It just works.
    And somehow google doesn't make it a lot clearer for me right now...

  • NVIDIA Dual Monitor not working

    I have two monitors, 1 QNIX 1440p running at 100hz that is properly working, the other, and 1080p Asus at 60hz is running at 1024x768.
    Here is my xorg.conf
    # nvidia-settings: X configuration file generated by nvidia-settings
    # nvidia-settings:  version 331.20  (buildmeister@swio-display-x86-rhel47-05)  Wed Oct 30 18:20:32 PDT 2013
    # nvidia-xconfig: X configuration file generated by nvidia-xconfig
    # nvidia-xconfig:  version 331.20  (buildmeister@swio-display-x86-rhel47-05)  Wed Oct 30 18:20:53 PDT 2013
    #Section "Device"
    #    Identifier    "Device1"
    #    Driver        "nvidia"
    #    VendorName    "NVIDIA Corporation"
    #    Screen        1
    #EndSection
    Section "ServerLayout"
    # Removed Option "Xinerama" "1"
        Identifier     "DualScreen"
        Screen      0  "Screen0" 0 0
        Screen      1  "Screen1" 2560 0
        InputDevice    "Keyboard0" "CoreKeyboard"
        InputDevice    "Mouse0" "CorePointer"
        Option         "Xinerama" "0"
    EndSection
    Section "Files"
    EndSection
    Section "InputDevice"
        # generated from default
        Identifier     "Mouse0"
        Driver         "mouse"
        Option         "Protocol" "auto"
        Option         "Device" "/dev/psaux"
        Option         "Emulate3Buttons" "no"
        Option         "ZAxisMapping" "4 5"
    EndSection
    Section "InputDevice"
        # generated from default
        Identifier     "Keyboard0"
        Driver         "kbd"
    EndSection
    Section "Monitor"
        Identifier     "Monitor0"
        VendorName     "Unknown"
        ModelName      "DFP-3"
        DisplaySize     597    336
        HorizSync       88.8 - 160.0
        VertRefresh     59.5 - 120.0
        ModeLine       "2560x1440" 241.50 2560 2608 2640 2720 1440 1443 1448 1871 +hsync -vsync
        ModeLine       "2560x1440_60" 312.25 2560 2752 3024 3488 1440 1443 1448 1493 -hsync +vsync
        ModeLine       "2560x1440_75" 397.25 2560 2760 3040 3520 1440 1443 1448 1506 -hsync +vsync
        ModeLine       "2560x1440_85" 454.75 2560 2768 3048 3536 1440 1443 1448 1514 -hsync +vsync
        ModeLine       "2560x1440_96" 400.00 2560 2608 2640 2744 1440 1443 1448 1512 +hsync +vsync
        ModeLine       "2560x1440_100" 400.00 2560 2608 2640 2720 1440 1443 1448 1481 +hsync +vsync
        ModeLine       "2560x1440_100" 542.25 2560 2776 3056 3552 1440 1443 1448 1527 -hsync +vsync
        ModeLine       "2560x1440_120" 661.25 2560 2784 3064 3568 1440 1443 1448 1545 -hsync +vsync
    EndSection
    Section "Monitor"
    #    HorizSync       88.8 - 160.0
    #    VertRefresh     59.5 - 120.0
        Identifier     "Monitor1"
        VendorName     "Unknown"
        ModelName      "DFP-0"
    #    HorizSync       28.0 - 55.0
    #    VertRefresh     43.0 - 72.0
        ModeLine       "1920x1080_60" 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -hsync +vsync
        Option         "Enable" "True"
        Option         "DPMS"
    EndSection
    Section "Device"
        Identifier     "Device0"
        Driver         "nvidia"
        VendorName     "NVIDIA Corporation"
        BoardName      "GeForce GTX 660"
        BusID          "PCI:1:0:0"
        Screen          0
    EndSection
    Section "Device"
        Identifier     "Device1"
        Driver         "nvidia"
        VendorName     "NVIDIA Corporation"
        BoardName      "GeForce GTX 660"
        BusID          "PCI:1:0:0"
        Screen          1
    EndSection
    Section "Screen"
    # Removed Option "metamodes" "DVI-I-1: 2560x1440_100 +2560+0, DVI-D-0: 2560x1440_100 +0+0; DVI-I-1: 2560x1440_96 +0+0, DVI-D-0: 2560x1440_96 +2560+0; DVI-I-1: 2560x1440_85 +0+0, DVI-D-0: 2560x1440_85 +2560+0; DVI-I-1: 2560x1440_75 +0+0, DVI-D-0: 2560x1440_75 +2560+0; DVI-I-1: 2560x1440_60 +0+0, DVI-D-0: 2560x1440_60 +2560+0; DVI-I-1: 2560x1440 +0+0, DVI-D-0: 2560x1440 +2560+0"
    # Removed Option "metamodes" "DVI-I-1: 1920x1080 +2560+0, DVI-D-0: 2560x1440_100 +0+0"
        Identifier     "Screen0"
        Device         "Device0"
        Monitor        "Monitor0"
        DefaultDepth    24
        Option         "UseEDID" "False"
        Option         "UseEDIDDPI" "False"
        Option         "UseEDIDFreqs" "False"
        Option         "ExactModeTimingsDVI" "True"
        Option         "ModeValidation" "AllowNonEdidModes, AllowNon60hzmodesDFPModes, NoEDIDDFPMaxSizeCheck, NoVertRefreshCheck, NoHorizSyncCheck, NoDFPNativeResolutionCheck, NoMaxSizeCheck, NoMaxPClkCheck, NoEDIDModes"
        Option         "TwinView" "0"
        Option         "Stereo" "0"
        Option         "metamodes" "DVI-D-0: 2560x1440_100 +0+0"
        Option         "SLI" "Off"
        Option         "MultiGPU" "Off"
        Option         "BaseMosaic" "off"
        SubSection     "Display"
            Depth       24
        EndSubSection
    EndSection
    Section "Screen"
    # Removed Option "metamodes" "DVI-I-1: 1920x1080_60.00 +2560+0"
    # Removed Option "metamodes" "DVI-I-1: 1920x1080_60 +0+0"
        Identifier     "Screen1"
        Device         "Device1"
        Monitor        "Monitor1"
        DefaultDepth    24
        Option         "UseEDID" "False"
        Option         "UseEDIDDPI" "False"
        Option         "UseEDIDFreqs" "False"
        Option         "ExactModeTimingsDVI" "True"
        Option         "ModeValidation" "AllowNonEdidModes, AllowNon60hzmodesDFPModes, NoEDIDDFPMaxSizeCheck, NoDFPNativeResolutionCheck, NoMaxSizeCheck, NoMaxPClkCheck, NoEDIDModes"
        Option         "TwinView" "0"
        Option         "Stereo" "0"
        Option         "metamodes" "DVI-I-1: 1920x1080 +0+0"
        Option         "SLI" "Off"
        Option         "MultiGPU" "Off"
        Option         "BaseMosaic" "off"
        SubSection     "Display"
            Depth       24
        EndSubSection
    EndSection
    Thanks in advance for any help you can give.

    Hi GloW_on_dub,
    Here's the output :
    Screen 0: minimum 8 x 8, current 2480 x 1050, maximum 16384 x 16384
    DVI-I-0 connected primary 1680x1050+0+0 (normal left inverted right x axis y axis) 473mm x 296mm
    1680x1050 60.0*+
    1600x1200 60.0
    1440x900 59.9
    1280x1024 75.0 60.0
    1280x960 60.0
    1152x864 75.0
    1024x768 75.0 70.1 60.0
    800x600 75.0 72.2 60.3 56.2
    640x480 75.0 72.8 59.9
    DVI-I-1 disconnected (normal left inverted right x axis y axis)
    HDMI-0 disconnected (normal left inverted right x axis y axis)
    DP-0 disconnected (normal left inverted right x axis y axis)
    DVI-D-0 connected 800x600+1680+0 (normal left inverted right x axis y axis) 0mm x 0mm
    800x600 60.3*+
    DP-1 disconnected (normal left inverted right x axis y axis)

  • Dual Monitor not working for Mac Pro (Early 2008)

    Upon upgrading from Lion to Mountain Lion yesterday I lost the ability to use my secondary monitor. Checking in System Preferences it indicates that it only sees one monitor, but nothing has changed with my hardware configuration. Is anyone else having this problem?
    Hardware specs:
    Processor  2 x 2.8 GHz Quad-Core Intel Xeon
    Memory  26 GB 800 MHz DDR2 FB-DIMM
    Graphics  ATI Radeon X1900 XT 15 MB
    Software  OS X 10.8 (12A269)

    Not sure if this has any relation to yours, but I thought I would throw it out there...
    After installing Mountain Lion, the secondary monitor for my 27" iMac would not wake up after the computer slept. In the System Preferences, there was only the main display listed. The secondary monitor was visible from a cold boot, but disappeared once the computer slept and was woken up.
    I found that waking the system with the Magic Trackpad would not also wake the second monitor. When I wake the computer by using the keyboard, the second monitor wakes normally! I've repeated this several times... Strange.

  • Mountain Lion 1.8.2 update made my dual monitor stop working on Mac Pro mid 2012

    Just done Apple's update for Mac OS X Mountain Lion to 1.8.2 and after rebooting my dual monitor stopped working.
    If I go on preferences -> Displays it shows me only one of my two monitors, even if I invert the connections the 2nd monitor doesn't shows up and there seems no way to enable it again.
    Any suggestion?
    P.S. I already tried to set from "Best for display" to "Scaled", but after rebooting Mountain Lion 1.8.2 reset it to "Best for display"

    Ok,
    did some extra test here, but first of all my configuration:
    Mac Pro (Mid 2012) with ATI Radeon HD 5870 1GB.
    2 LCD 24" Wide-screen (1st monitor Hyundai W240D and 2nd Monitor HP w2448hc), both LCD worked perfectly until reboot after installing OS X 1.8.2
    After reboot only the 1st monitor wored fine, the 2nd not even listed, so tried to invert cable connections on the 2 miniports on the ATI video card, but nothing changed, still only the 1st monitor working.
    Did a second test, disconnected the 1st monitor and connected ONLY the 2nd and now the second works fine.
    Tried to connect 2nd monitor on a different miniport, and i still works fine.
    Updated my MacBook Pro to 1.8.2 (it as an nVidia card) and connected my 2nd monitor to it and everything works fine, both the laptop LCD and my HP LCD are working fine.
    So it looks like Apple screwed up the ATI driver on the latest 1.8.2, now only ONE miniport is active.
    To all users with the same Mac Pro configuration: hold to update to Mountain Lion 1.8.2 until Apple fix this driver issue.
    More info are on the Console output, so will have to contact Apple on-line support to signal this bug.

  • Seeking a clear description of getting dual monitors to work

    I've spent a long while researching the issue of getting dual monitors to work on a new mac mini - which I will be purchasing as soon as I figure this one out! But I am bamboozled by references to the various types of connections and ports. If anyone has the patience to explain this really simply and clearly, I'd be very grateful.
    Interestingly, the Apple guy on the phone today told me it isn't possible - it's either/or for the display connections. But clearly it IS possible, because there is so much discussion about it here...
    Here's where I confess my technical limitations, and say that I am confused about what I need (to purchase, presumably) to get my two existing monitors to work with the new mini.
    They are presently connected to my PC (soon to be ceremonially consigned... etc) with cables which have regular D-sub connectors at each end. This means they are vga, right? There is no digital connector on either monitor.
    So I am trying to figure out
    a) is it possible to use these two monitors in a dual display setup with a mac mini? If so:
    b) How?! And then;
    c) what leads and/or connectors do I need to buy in order to connect them up?
    Thanks for being here, I hope for some patient guidance.
    Jeff

    Welcome to the Apple Discussions!
    An '09 Mac mini has two video out pots on the rear; a mini-DVI port and a mini-DisplayPort. The Mac mini comes with a mini-DVI to DVI-D adapter. If you use what came in the box with the mini, you need a DVI-D to VGA cable to connect one of your monitors. Otherwise you need a mini-DVI to VGA adapter and a VGA to VGA cable for one monitor. For the other monitor you need a mini-DisplayPort to VGA adapter and a VGA to VGA cable.
    Dah•veed

  • DVI out to external monitor not working anymore

    Hi,
    I have been using my MBP with an external Dell 17" LCD for a dual monitor setup. Suddenly after about 5 months of flawless working, it is not detecting the external display anymore. The display is not at fault - another powerbook detects is as ususal. I tested my MBP with another cinema display and again, it is not detecting it at all. I have tried F7 toggles and "detect display" from system preferences. No use at all.
    Any ideas?
    Should I just take it to the local applestore?
    Thanks.

    I don't know if SMC resetting fixed it or that RAM resetting fixed that issue...but now the MBP recognizes the external display all the time.
    However, it has another issue now -
    http://discussions.apple.com/thread.jspa?threadID=919509&messageID=4377872#43778 72

  • New Dual-Monitor fix work with StageDisplayState.FULL_SCREEN ?

    Hi all,
    The new fix for flash to allow fullscreen video on dual monitors is a great addon.  Is there a way to have this work with the StageDisplayState.FULL_SCREEN command as well? So far its acting as normal.  I assume this may be because its not actual video, but an application that im fullscreening.

    Reset Safari.
    Click Safari in the menu bar.
    From the drop down select "Reset Safari".
    Click "Reset".
    Empty Caches
    Safari > Preference > Advanced
    Checkmark the box for "Show Develop menu in menu bar".
    Develop menu will appear in the Safari menu bar.
    Click Develop and select "Empty Caches" from the dropdown.
    Turn off Extensions if any, and launch Safari.
    Safari > Preferences > Extensions

  • Mavericks and Dual Display not working as documented

    Hi all. Ok..something a little wierder here for my dual display scenario. I have two Samsung Syncmaster 2443 monitors. 15" MBP Retina purchased this year. Running in Clamshell Mode.
    I can get dual monitors happening (extended) but I cannot get the menu bar to come over as well. As mentioned in other posts, I need to tick the box in Mission Control "Displays have seperate spaces". The only problem is, that particular menu item is NOT there. All I have is the other 4 items. So how is it that this menu item does not exist on my installation?
    In this current setup, each time I reboot the display's also get reveresed, which is really annoying. I have to reboot twice to get back to my original layout.
    Any idea's?
    Tks

    you're faking out your machine to THINK it has 2 real displays and you expect Keynote to work? Keynote is THE most intense app I've ever seen for screen drawing. It basically takes over your entire machine to do its work. It doesn't surprise me that that trick doesn't work with it.
    My guess is you're going to have to wait till you have the actual projector and adapter to test your dual screen setup.

  • 2012 R2 Essentials - Anywhere Access will not install. Including Remote Web Access portion.

    After setting up 2012 R2 Essentials, I attempted to go through the dashboard's "Set up Anywhere Access" wizard. I was able to configure a domain name successfully on remotewebaccess.com but when the wizard attempted to enable the "Remote Web
    Access" feature, the wizard flashes a couple of statuses and locks up on verifying and then the entire dashboard crashes. When I go to the event logs, there is only a mention of dashboard.exe having an exception error. I have also delved into the dashboard.log
    file and found the following error where it throws the FATAL crash:
    Dashboard.Forms: !!!!FATAL: Dashboard shutting down due to unhandled exception: The 'Get-WindowsFeature' command was found in the module 'ServerManager', but the module could not be loaded. For more information, run 'Import-Module ServerManager'.
    [11024] 140624.234737.2917: Dashboard.Forms: System.Management.Automation.CommandNotFoundException: The 'Get-WindowsFeature' command was found in the module 'ServerManager', but the module could not be loaded. For more information, run 'Import-Module ServerManager'.
    ---> System.Management.Automation.CmdletInvocationException: Length cannot be less than zero.
    Parameter name: length ---> System.ArgumentOutOfRangeException: Length cannot be less than zero.
    Parameter name: length
    I have launched PowerShell and executed the "Import-Module ServerManager" along with the "Get-WindowsFeature" command and it returns the list of available and installed features. I have also tried rebooting the server and attempting the
    wizard numerous times and all attempts result in the same error above. Does anyone have an idea of what could be causing this? I have searched google, bing, and the technet similar questions but none have a solution that will allow me to use the wizard to
    enable the Remote Web Access feature.

    I had a similar issue, it does appears to be caused by MyMovies 5.
    I removed MM5 but the dashboard would still crash after opening the Anywhere Access tab and when it had been running the 'Updating' status for a bit. going through the dashboard log I found that just under the line about the Get-WindowsFeature error was
    a comment 'atMyMovies.Common... full error as follows:
    [5616] 140701.125213.3686: Dashboard.Forms: !!!!FATAL: Dashboard shutting down due to unhandled exception: The 'Get-WindowsFeature' command was found in the module 'ServerManager', but the module could not be loaded. For more information, run 'Import-Module
    ServerManager'.
    [5616] 140701.125213.3686: Dashboard.Forms: System.Management.Automation.CommandNotFoundException: The 'Get-WindowsFeature' command was found in the module 'ServerManager', but the module could not be loaded. For more information, run 'Import-Module ServerManager'.
    ---> System.Management.Automation.CmdletInvocationException: Could not load file or assembly 'Microsoft.Windows.ServerManager.PowerShell' or one of its dependencies. An argument was out of its legal range. (Exception from HRESULT: 0x80131502) ---> System.IO.FileLoadException:
    Could not load file or assembly 'Microsoft.Windows.ServerManager.PowerShell' or one of its dependencies. An argument was out of its legal range. (Exception from HRESULT: 0x80131502) ---> System.ArgumentOutOfRangeException: Length cannot be less than zero.
    Parameter name: length
       at System.String.Substring(Int32 startIndex, Int32 length)
       at MyMovies.Common.AssemblyResolver(Object sender, ResolveEventArgs args)
       at System.AppDomain.OnAssemblyResolveEvent(RuntimeAssembly assembly, String assemblyFullName)
       --- End of inner exception stack trace ---
       at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadBinaryModule(PSModuleInfo parentModule, Boolean trySnapInName, String moduleName, String fileName, Assembly assemblyToLoad, String moduleBase, SessionState ss, ImportModuleOptions options, ManifestProcessingFlags
    manifestProcessingFlags, String prefix, Boolean loadTypes, Boolean loadFormats, Boolean& found, String shortModuleName, Boolean disableFormatUpdates)
       at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadModuleNamedInManifest(PSModuleInfo parentModule, ModuleSpecification moduleSpecification, String moduleBase, Boolean searchModulePath, String prefix, SessionState ss, ImportModuleOptions options,
    ManifestProcessingFlags manifestProcessingFlags, Boolean loadTypesFiles, Boolean loadFormatFiles, Object privateData, Boolean& found, String shortModuleName)
       at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadModuleManifest(String moduleManifestPath, ExternalScriptInfo scriptInfo, Hashtable data, Hashtable localizedData, ManifestProcessingFlags manifestProcessingFlags, Version version, Version requiredVersion,
    ImportModuleOptions& options, Boolean& containedErrors)
       at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadModuleManifest(ExternalScriptInfo scriptInfo, ManifestProcessingFlags manifestProcessingFlags, Version version, Version requiredVersion, ImportModuleOptions& options)
       at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadModule(PSModuleInfo parentModule, String fileName, String moduleBase, String prefix, SessionState ss, Object privateData, ImportModuleOptions& options, ManifestProcessingFlags manifestProcessingFlags,
    Boolean& found, Boolean& moduleFileFound)
       at Microsoft.PowerShell.Commands.ImportModuleCommand.ImportModule_LocallyViaName(ImportModuleOptions importModuleOptions, String name)
       at Microsoft.PowerShell.Commands.ImportModuleCommand.ProcessRecord()
       at System.Management.Automation.CommandProcessor.ProcessRecord()
       --- End of inner exception stack trace ---
       at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
       at System.Management.Automation.PowerShell.Worker.ConstructPipelineAndDoWork(Runspace rs, Boolean performSyncInvoke)
       at System.Management.Automation.PowerShell.CoreInvokeHelper[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
       at System.Management.Automation.PowerShell.CoreInvoke[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
       at System.Management.Automation.PowerShell.CoreInvoke[TOutput](IEnumerable input, PSDataCollection`1 output, PSInvocationSettings settings)
       at System.Management.Automation.CommandDiscovery.AutoloadSpecifiedModule(String moduleName, ExecutionContext context, SessionStateEntryVisibility visibility, Exception& exception)
       --- End of inner exception stack trace ---
    There was a couple of line before the fatal error suggesting it could be to do with the remote deskop gateway configuration...
       at Microsoft.WindowsServerSolutions.Common.RemoteDesktopConfig.RemoteDesktopConfigLib.IsFeatureAvailable(String featureName)
       at Microsoft.WindowsServerSolutions.Common.RemoteDesktopConfig.RemoteDesktopConfigLib.CheckTSRelatedRolesAvailable()
       at Microsoft.WindowsServerSolutions.Connectivity.Jobs.TsGatewayDiagnosticsJob.OnRun(DiagnosticsResult result, ConnectivityEnvironment environment)
       at Microsoft.WindowsServerSolutions.Connectivity.DiagnosticsJob.RunAndCatch(DiagnosticsResult result, ConnectivityEnvironment environment)
    So I ended up removing the role using server manager, along with the remote access role, and then rebooting the server. I then added the Remote Access role back in by choosing the 'DirectAccess and VPN (RAS)' option.
    When I then ran the dashboard Anywhere Access setup it worked.
    Other issues that seemed to cause the dashboard to crash was when I released the remotewebaccess.com domain name and then added it back in. I had multiple certificates with the same name which seemed to cause an issue. so I released the domain name again,
    went into the certificates MMC and removed any of the goDaddy certificate. then configured the domain name again and the rest of the wizard ran with no issues.
    Hope some of this helps...

  • Activity Monitor not working correctly / not listing processes

    When I open Activity Monitor, it does not display a list of processes. The CPU usage works in the bottom of the window as does the disk usage. None of the other graphs display any graphing/data.
    I have rebooted, relaunched AM and I selected "all processes" but it still doesn't show processes.
    I used the terminal command "top" and can see processes in the terminal window.
    thanks for any assistance,
    Harold
    imac 2.8 dual core/24"/2gb/os10.5.5

    Thanks for the quick reply. I couldn't find the activity monitor preferences file you specified, in the Preferences directory. Here's what I've done: I rebooted from an older backup image on my external drive that I made using superduper. The activity monitor app worked from this disk image. I copied the AM app into my current drive, where it showed as a copy.
    I rebooted, and attempted to use this copy. It wouldn't let me due to file permissions problems of some sort. I opened the current version of AM and now it works.
    I'm not sure what fixed the problem, but Activity Monitory now seems to be working OK.
    thanks,
    Harold

Maybe you are looking for