Lync screen sharing doesn't work in Windows 10 Technical Preview (9879 Build)

Why Lync screen sharing doesn't work in Windows 10 Technical Preview?
It works well Windows 8.1, but why not in Windows 10?

Hi PriTeddy,
Thanks for your feedback.
As Paul Adare said, Microsoft has noticed such issue, they are listed in following blog:
http://blogs.windows.com/bloggingwindows/2014/11/12/new-build-available-to-the-windows-insider-program/
Some known problems:
As with the last build, you’re getting hot-off-the-presses code which means there are a few issues. We’ll be publishing WU updates shortly to fix the first two, but the remainder will not be fixed for 9879.
•In some cases you may get a black screen when trying to log-in or unlock. The only option is to hold the power button to hard reboot.
•You will be unable to connect to Distributed File System network locations.
•Some systems may see disk growth of 20GB+ due to driver install duplication. On systems with low disk space this can block setup and cause a rollback to the previous build.
•Skype calls will disconnect and Music will stop playing if those apps are minimized.
•There are several known issues with screen sharing with Lync.
Let’s wait for next builds.
Alex Zhao
TechNet Community Support

Similar Messages

  • OS X Screen Sharing doesn't work after Mavericks Upgrade

    I have upgraded my 3x machines to Mavericks and Screen Sharing no longer works.  I have tried this with and without firewalls on.  File Sharing works but Screen Sharing will say connecting for a LONG time and then say that it's not enabled and to go turn it on...
    help?
    - MacMini - late 2009
    - MacMini - mid 2011
    - MBA - mid 2012
    I have seen a couple people talk about this as well, but wasn't the same thing..

    I believe this is the easiest way to resolve any screensharing issues in MacOSX: Solution: Reset the computer list in Screen Sharing. To acomplish that install OnyX. By the way a great tool for your Mac maintenance.
    Go to Cleaning>Misc. and
    check My Computers list in Screen Sharing.
    Press Execute and wait until it finish.
    Restart your computer.
    I hope this helps.

  • Screen sharing doesn't work on headless mini

    I have a headless Mac Mini that has been running 10.5 and 10.6 for years and I've never had any problems with screen sharing.
    I now update to Lion and as soon as there's no screen attached I can no longer use Screen Sharing!
    There is absolutely no way I can have a screen perminently attached to the machine.
    Any ideas of how to fix this behaviour?
    I've tried rebooting with no screen attached and that just hung the server at boot time.

    I've found a work around.
    Connect the screen and then connect to the machine via Screen Sharing
    Then change Screen Sharing from Hardware display to Virtual display.
    Then you can disconnect the screen and Screen Sharing continues to work. (At least so far)

  • Screen sharing doesn't work without a gateway

    I'm back from a short trip and find that my gateway died in the meantime.
    I have a LAN with quite a few Macs, some of them being Mac minis used as servers with no attached screens.
    I can't use screen sharing anymore on my LAN to control any Mac that has not been set up to use my failover gateway. Only the Macs whose network set up has been changed to fully use the failover gateway can be controled. Unfortunately, this gateway and has limitations not allowing me to use it with every Mac/iPad etc. here. If I set up a Mac to use the failover gateway, but with no internet access allowed, that Mac remains uncontrolable with screen sharing.
    So I'd like someone more experienced to answer these questions:
    - How is it that an operational gateway with a working internet access is mandatory for LAN screen sharing ?
    - Are authentication services responsible for the troubles here ?
    Help would be greatly appreciated,
    JM

    While I understand the terms, I do not yet fully understand what your IP network looks like.
    By "usual gateway", are you referring to a hardware device — commonly called a "gateway router" — that's been replaced here, or to the IP gateway settings present within most (all?) hosts on an IP network?
    IP needs a gateway for traffic outside of the subnet.  That commonly includes DNS traffic, either from the DNS server(s) on your LAN, or for IP hosts that are communicating more directly.  This can also include determining the source of in-bound IP traffic, as that involves DNS translations.
    Swapping gateway routers can also sometimes require flushing the ARP caches, depending on what hardware and software is involved.  (Normally the new device will broadcast that on the LAN and thus update the caches, but sometimes things get a little wonky.)  This if it's at the same address.  If it's at different addresses, then the DHCP server, DHCP clients and static-addressed hosts all need to be updated.
    In general (and because I'm not certain of your configuration), I prefer to avoid using Macs as IP routers, as they're expensive for and comparatively clumsy at that task.  I prefer to use dedicated devices for that, and often preferanly including an embedded VPN server as I'd mentioned earlier.
    Again, I'm not clear about your configuration, so the above might not address your question.

  • Screen Sharing doesn't work after updating to Remote Desktop 3.6.1

    Hi everyone!
    I hope others can help.  We just noticed this at two different schools today after upgrading to 3.6.1.  We upgraded Admin and Client Apple Remote Desktop to ARD 3.6.1 today and now we cannot share our screens with the clients.  It turns black, hangs, then returns the client to its original desktop. 
    We tried from a 3.5.1 admin machine, and it still works fine as it used to.
    We feel like the issue is 3.6.1, but cannot find any support for the issue online. 
    Other troubleshooting steps:
    1) emptied user and system Caches
    2) restarted all units
    3) tried 3.6.1 admin to 3.5.1 clients, no luck
    4) tried 3.6.1 admin to 3.6.1 clients, no luck
    5) checked for loops in the network, nothing.
    We can perform most other tasks like controlling the clients and copying files, but not screen sharing.
    Thank you for your help!

    All right!  Total workaround here, and no fix, but at least we're able to Screen Share in ARD now.  This is how we downgraded to 3.5.1 Admin in Apple Remote Desktop.  The only hiccup that may not work for most is that you must have an older Remote Desktop file on hand. (hopefully from a computer that was not upgraded which was our case).
    Here is what we did...
    1) Login as an admin.
    2) Throw out the Remote Desktop app (in Applications)
    3) From another computer, drag in an old Remote Desktop app into your Applications folder
    4) Throw out the "RemoteManagement" folder inside System/Library/CoreServices
    5) From support.apple.com/downloads, download Remote Desktop 3.5.1 (both the Client and Admin installers).
    6) Run the Admin install first, then the Client Install.
    I did the above steps in two schools in a different order, but I wrote it this way to make it more streamlined.  I never had to re-enter the Serial # or anything.  Once I did the steps above, it just worked again.
    Hope this helps you! 

  • Screen Sharing Doesn't Work

    Hi!
    I am having problems getting screen sharing to work. When starting a session I get an error message saying iChat is unable to start screen sharing.
    Using the same computer with the same settings I can connect to some systems, but most systems won't allow me to connect.
    In all cases, Enable Screen Sharing is checked. All systems are running iChat 4.x. All systems are running the same operating system. All systems are connected via hard-wire Ethernet.
    What do I need to do to get iChat screen sharing to work? Connection Doctor does not show any results until AFTER a session has started.
    We are able to connect via messaging with no problems.
    Thanks,
    Larry

    Hi,
    Welcome to the    Discussions
    The Connection Doctor gives a shortened form of the Error message.
    The Pop up (Send to Apple) has a Reveal Triangle next to the word Details.
    In here will be a Longer Log with the Error code number at the end of the first main paragraph.
    The Main issue with Screen Sharing is that it uses a Random port.
    iChat uses 20 ports at iChat 4 and 5
    Port 5190
    On TCP (to Login to AIM) and to Plain IMs and ON UDP to send Direct IMs including File Sending and Pics in Chats.
    Some modems and routers cannot handle this dual use and we suggest changing the Login port to 443 (it helps with some Logging in issues and some Video chats)
    Ports 5220, 5222, 5223 on TCP for Jabber and GoogleTalk Buddy Lists.
    Ports 5297, 5298, 5353 on UDP and 5298 on TCP for Bonjour Buddy Lists.
    Ports 5678 On UDP for Sending/Receiving the Visible Invite to A/V chats
    Ports 16393-16402 On UDP (Ten Ports)
    (iChat 2 and 3 uses a wider range of ports (2) that can be read here which is where the Jabber and Bonjour ports are listed)
    See this Article for iChat 4 up which only lists the changes to the A/V ports
    You will notice that the later Article does not mention Screen Sharing.
    This tends to mean you cannot "Set" the port in Port Forwarding due to it's random nature.
    This may mean your Buddies do not have the port "open" for it.
    Using UPnP which gives control to the App about which ports (and when) are opened.
    There is also and Issue in Leopard with iChat 4.x with Internet Sharing (System Preferences > Sharing).
    This can not be On. It effects all chats that involve A/V, which includes the Audio Chat with Screen Sharing.
    9:31 PM Monday; October 26, 2009
    Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"

  • Screen Sharing Doesn't Work (Leopard to Leopard)

    Does anyone know which things to click on in System Preferences to make Screen Sharing work? We've tried multiple ways but no luck as of yet. Should it be an Administrator? Is Allowing All Users a good thing? Once allowed, can people access EVERYTHING, including software programs and hidden files & folders etc.
    So which way is the best way to at least make it work for now, and then... which is best for security purposes further down the road?
    Cheers!

    Help viewer is your, usually underrated, friend
    Type "screen sharing" in its search field and take your pick.

  • Screen sharing doesn't work in Yosemite

    Screen sharing gives this message on my iMac :
    Process:          
    Screen Sharing [46463]
    Path:             
    /Volumes/*/Screen Sharing.app/Contents/MacOS/Screen Sharing
    Identifier:       
    com.apple.ScreenSharing
    Version:          
    Build Info:       
    RemoteDesktop-3009915~3
    Code Type:        
    X86 (Native)
    Parent Process:   
    ??? [1]
    Responsible:      
    Screen Sharing [46463]
    User ID:          
    502
    Date/Time:        
    2015-01-27 13:31:28.148 +0100
    OS Version:       
    Mac OS X 10.10.1 (14B25)
    Report Version:   
    11
    Anonymous UUID:   
    7E87A766-A68F-42AB-5776-3EC4CEE0DBC9
    Sleep/Wake UUID:  
    E9049456-0F35-432F-A16C-0C7313FDA6B0
    Time Awake Since Boot: 1300000 seconds
    Time Since Wake:  
    3100 seconds
    Crashed Thread:   
    0
    Exception Type:   
    EXC_BREAKPOINT (SIGTRAP)
    Exception Codes:  
    0x0000000000000002, 0x0000000000000000
    Application Specific Information:
    dyld: launch, loading dependent libraries
    Dyld Error Message:
      Library not loaded: /System/Library/PrivateFrameworks/ScreenSharing.framework/Versions/A/ScreenShar ing
      Referenced from: /Volumes/*/Screen Sharing.app/Contents/MacOS/Screen Sharing
      Reason: no suitable image found.  Did find:
        /System/Library/PrivateFrameworks/ScreenSharing.framework/Versions/A/ScreenShar ing: mach-o, but wrong architecture
    Binary Images:
    0x8fe0c000 - 0x8fe3fe03  dyld (353.2.1) <EBFF7998-58E8-32F5-BF0D-9690278EC792> /usr/lib/dyld
    0x92b00000 - 0x92b00fff  com.apple.Carbon (154 - 157) <5A078967-8437-3721-A6B1-70CC00461D7B> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
    0x9323b000 - 0x933ffff3  com.apple.QuartzCore (1.10 - 361.11) <9CED60CF-9B7F-3288-A7E9-3AE087F9E076> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
    0x9376c000 - 0x939e8ff3  com.apple.security (7.0 - 57031.1.35) <4721C22E-D6C2-3202-B80D-5E67169466D2> /System/Library/Frameworks/Security.framework/Versions/A/Security
    And a similar message on my MacBook Pro

    same here on a 2010 macbook pro. i routinely use screen sharing to access that MBP from a 2010 mac pro. but ever since installing lion on the MBP (now 10.7.1), i'm asked for my "Kerberos password" -- and i've never even heard of such a thing.
    so far, googling this has not led to anything helpful.
    i love my macs, but stuff like this that impedes our productivity is a monumental drag (to say the least).

  • Screen Sharing no longer working

    Hello, everyone.  I have developed an issue with screen sharing on my MacBook Pro running OX 10.6.8, and I cannot seem to resolve it.  Perhaps I am missing something.  I realize this is a long post, but I am trying to be as complete as possible with my description of the problem and the steps I have taken to try to resolve it.
    Screen sharing is of particular importance to me because I use it to control a Mac Mini that has my entire iTunes library. The Mac Mini is running OS 10.6.8.
    Ordinarily, I would open Finder, click on the Mac Mini under "Devices," then "Share Screen" in the upper right corner of the Finder window. I enter my name and password in the login box, and I am controlling my Mac Mini within seconds.
    Within the last few days, however, I have been unable to complete the connection. The first sign that something was wrong was when it took almost five minutes just for the login window to appear.  Then, after I entered my login information, the "Connecting..." gear began spinning. It never gets any farther than that.  I have even tried waiting as long as 45 minutes for the connection to complete before giving up, which requires restarting my computer, since force-quitting Screen Sharing doesn't work.
    First, I tried re-booting my Mac Mini a few times, with no success.  I also tried re-booting my MacBook Pro both in normal and safe mode, followed by repairing permissions and checking the volume structure (Disk Utility found no errors). I even tried running the full suite of Onyx scripts.
    To isolate the issue, I took two other computers in my house, one running OS 10.7.4 and the other running OS 10.8, and they connected perfectly. All computers are on the same wireless network (although the Mac Mini connects to the same network through ethernet).  Therefore, the issue has to be with my MacBook Pro.
    Does anyone have any ideas as to how to resolve this issue?  Thanks in advance for any assistance you can provide.

    I too was running a Mac Mini with Server 10.6.8. Using it as a Netboot server was working just fine, but I wanted to look up the version of something on the mini. Connecting over screen sharing hung all day yesterday, so today I hooked up a keyboard, mouse, and display to look up the information from the mini. Turning off and restarting the shared services, restarting the mini, deleting keychains, attempting to get a screen share from a Finder connection... all hung at the "Connecting..." dialogue. I found this thread and signed out of MobileMe on the mini, and on the iMac I was using to connect. The connection went through at last, and now it's re-establishing without a hitch.

  • Adding features to Windows Technical Preview

    Why serial code not work with Windows Technical Preview evalution copy Build 9879?
    Add features to Windows Technical Preview and asks for serial key, two different serial key but not work.

    Hi,
    Where did you get the product key? Online purchase is not available at this moment (my region is set to US), and please note that the product key for "Add feature" is not the same key for activating system.
    If you have any feedbacks on Windows 10 Technical Preview, please click the search botton in the left bottom of the screen, type "Windows Feedback", then submit your feedback.
    Regards.
    Yolanda Zhu
    TechNet Community Support

  • Screen sharing no longer works.

    I cannot use screen sharing between my laptop and mini, although I used to be able to do so, after I "updated" to Lion. However, I can use file sharing, showing that wireless (airport) connection is working. This seems to be an Apple network problem.  I tried the solutions posted (signing out of MobileMe, restarting my laptop), but Screen Sharing comes up, the "Connecting" window shows and then goes away, while the network/(my laptop name) window stays on. Laptop also shows up in the sidebar. Trying for Screen Sharing help gets me a message: "Topic currently unavailable." Is there a solution that does not involve connecting the two computers with an Ethernet cable?

    Is Firewall turned off on both machines?

  • Lumia 920 - internet sharing doesn't work: Connect...

    Hello all,
    I'm experiencing a serious problem with the lumia 920. It seems impossible to share my internet connection. Something I normally use for several hours a day. If this problem can't be fixed soon, ill be forced to swithc back to iphone or htc.
    Problem description:
    When turning "internet sharing" on:
    Connection not shared - There is no cellular data connection to share right now. Check your cellular settings and signal, and try again.
    Important remarks
    Belgium - cellular provider is Mobistar
    I can browse, sync email, etc over the provider's network ans send and receive MMS.
     Provider does not block internet sharing. Have always used this.
    OS Version 8.0.10211.204
    Firmware revision: 1232.5957.1308.0002
    Access point :
     Nokia Access Point version:3.4.1.7 - db 2.0.0.100 - lib 1.2.0.7
     The default access point provided in the Nokia Access Point app does not work: can't even browse.
     Using a manually added APN:
     Data type (default / LTE) tried both. Everything keeps working - except internet sharing...
     APN pro.web.be  (for professional subscribers)
    MMS APN mms.be
    MMSC address: https://mmsc.mobistar.be
    What have i tried to remedy the situatiuon?
     updated the Nokia Access Point app
     changed language to spanisch using OTA update (silly, but read on a forum this might help)
     soft reset of the phone (often!)
     deleted the manually created access point
     Hard reset of my phone
    I'm interested, of course, in any tips to solve this serieus bug / issue / problem.
    (my best guess is that Nokia tries to help their customers with the Access point app, but fails to do so).
    Please, if any of you experience the same problem please respond to this post so we can get an idea about how big of a problem this is.

    Hi,
    I had the same problem. But I let it go after weeks of corresponding with Mobistar.
    Yesterday I went to a Mobistar shop, the guy tried lots of thing I already tried (different apn's, ...).
    Then he told me the it's a problem with business clients. They have to use the apn web.pro.be, where internet sharing doesn't work (he doesn't know why).
    But, that if I call to Mobistar and ask to activate apn mworld.be on my telephone number, it should work.
    Today I called Mobistar Business (you can find the helpdesk number on your invoices), asked to activate mworld.be to have internet sharing access on a windows phone.
    Half an hour later, using mworld.be as apn i have internet access, and I can share my internet connection.
    regards,
    Stijn

  • ITunes 9 Home Sharing does not work on Windows 7 x64

    iTunes 9 Home Sharing does not work on Windows 7 x64.
    Getting the following error message:
    Home sharing could not be activated because this computer is not authorized for the account "iTunes account." Please authorize this computer and try again.
    This is a bug since my computer is authorized in iTunes and there is only 2 computer authorized for my iTunes account, so I have 3 more left till I should get this message.
    I've just upgraded my iPhone to OS 3.1 using it this morning.
    Please advise.
    Environment: Windows 7 x64, HP TouchSmart tx2-1020us Notebook
    Ivan Farkas
    <edited by host>

    I am using Windows 7 x64.
    I am running iTunes 9.0.2.25
    I am running Mcafee.
    I can see and play music from the iTunes installation on my Windows 7 machine, but I CANNOT access the library to copy songs from this computer to other computers on my network.
    YES, I have enabled "Home Sharing" using my iTunes account. NO, I have not authorized more than 5 computers on this account.
    I believe this to be a Windows 7 related issue, as Home Sharing worked as advertised when I was using Vista (before I upgraded to Windows 7).
    I CAN set up Home Sharing on two other (host) computers in my home network and it works. These computers are XP and a MacBook Pro. I CANNOT access my Windows 7 machine x64 to COPY music from one autorized library to another. Please help!!!
    P.S. - I have attempted to get this to work by turning OFF my McAfee firewall. Windows firewall is disabled.
    Message was edited by: turcott

  • My i pod nano first generation doesn't work with windows 8

    My i pod nano first generation doesn't work with windows 8

    Howdy yvesmd,
    Thanks for using the Apple Support Communities.
    If your iPod nano is not being recognized in iTunes on your Windows computer, then I'd like you to please follow the directions in the link below.
    Apple - Support - iPod - iPod nano Troubleshooting
    Cheers,
    Alex H.

  • TS3704 How are you supposed to fix "The feature you are trying to use is on a network resource that is unavailable" alert appears when you remove Apple software in Windows if it doesn't work on Windows 8 or 8.1???

    How are you supposed to fix "The feature you are trying to use is on a network resource that is unavailable" alert appears when you remove Apple software in Windows if it doesn't work on Windows 8 or 8.1???

    See Troubleshooting issues with iTunes for Windows updates. You may have to uninstall what you can, reboot and delete the named folders, then reinstall.
    tt2

Maybe you are looking for