Target Display Mode not working iMac 27(2012) Bootcamp to iMac 27(2013)

Hi All,
I recently purchased an iMac 27" 2013 which replaced my iMac 27" 2010.
===============
PREVIOUS SETUP
===============
(1) iMac 27" 2012 - Running Windows 8.1
(2) iMac 27" 2010 - Running OS X Mavericks
(1)+(2) were connected with a Mini-Display-Port cable.
(1) was using (2) as external display while (2) was set to Target Display Mode using CMD+F2
==============
CURRENT SETUP
==============
(1) iMac 27" 2013 - Running Windows 8.1
(2) iMac 27" 2012 - Running OS X Mavericks
(1)+(2) are connected with Thunderbolt cable.
(1) can't use (2) as external display anymore becuase CMD+F2 has no effect anymore on (2) in this scenario.
If (1) and (2) are both running OS X all works as expected.
I am aware about the support hint from Apple where they state TDM is not working under Bootcamp.
And I agree, while booted into Windows Bootcamp this machine can't serve as external display. Makes sense because TDM is baked into OS X display drivers.
Anyone had the same experience and came to a soltuion?
Thanks,
Martin

"Apple has no plans to implement a client driver for Windows since there is no Thunderbolt SW stack available for Windows like there is for Display Port."
That is a little bit funny since Gigabyte and other big companies have said that 2014 is the year that they are going to implement Thunderbolt in many motherboards.
"GIGABYTE 7 series motherboards are the very first to offer fully certified dual onboard Thunderbolt™ ports. Capable of connecting up to 12 devices plus 3 digital displays simultaneously with breathtaking data transfer speeds that can transfer 1TB of data in only five minutes, GIGABYTE Thunderbolt™ motherboards offer the fastest connection interface on the desktop PC."
Have you asked Apple about that? I dont understand why Apple is crippling Thunderbolt on their devices...

Similar Messages

2010 iMac Target Display Mode not working

I'm trying to use my 27" 2010 iMac with OS X 10.7.5 as the display for my Power Mac G4 using Target Display Mode, but command+F2 doesn't do anything. I have it hooked up from the G4 using a DVI -> Mini Displayport adapter into the iMac. I've tried having the G4 plugged into the iMac, shutting both down, booting the G4 first and then the iMac. I've tried repairing my disk permissions on the iMac. I'm using an Apple keyboard and have tried both a wireless and USB keyboard, still no luck. Is what I'm attempting impossible or am I doing something wrong?

Target Display is working on the iMac, but by default, the MacBook Air uses the external display (in this case, the iMac) as an extended display, so you have to drag the windows to the right of the display of your MacBook Air and they will appear on your iMac.
If you want to show the same on both MacBook Air and iMac displays, see "Video mirroring" > http://support.apple.com/kb/HT5019

MacBook Air to iMac Target Display Mode not working

I would like to connect my MacBook Air (13") with my iMac (27") to use the latter as an external display with Target Display Mode.
I followed instructions from a number of posts (http://support.apple.com/kb/PH14264), and connected the two with thunderbolt cable and hit Command-F2 -- the iMac goes black and MacBook stays the same. One post suggested dragging windows over to the iMac as an extended display, and I was able to drag Safari totally off-screen, presumably onto the other display, but the iMac still appeared black
Other issue is that hitting Command-F2 again doesn't do anything. I could only get the iMac out of TDM when I unplugged the thunderbolt cord.
I have a brand new Macbook Air and iMac along with new thunderbolt cable (all purchased at Apple Store in 2014). Would appreciate any help, thanks!

Additional twist to this...
Tried to troubleshoot and reset the System Management Controller (SMC) per http://support.apple.com/kb/HT3964
When I hit Command-F2, one window from my MacBook will display on the iMac (it was Safari a few times, Outlook once), but neither keyboard/mouse can DO anything in that screen. That window also disappears from the MacBook. And I can only return after unplugging thunderbolt (not command-F2).
Help please

Target Display Mode - Connecting pre-Thunderbolt Macbook Air to Thunderbolt iMac.

I want to use Target Display Mode in order to display my late-2010 Macbook Air (pre-Thunderbolt) to a Thunderbolt-based iMac. Is there an adapter solution to connect, say, a mini display port + USB port on the MB Air to the iMac Thunderbolt port, such that TDM would work?

Depends upon the situation. Take a look at this blog:
http://blog.macsales.com/10899-target-display-mode-and-thunderbolt

HT1661 Target disc mode not working

My target disc (Macbook Pro) shows the firewire icon but nothing shows up on the host (PowerMac). I've tried several different ways and enabled it to show up in preferences. I don't have any other firewire device plugged in. I'm using a brand new cable. Thanks

cherylfromvenice wrote:
The cord was a very inexpensive one I got on Amazon. Could that be it?
It's certainly possible. Anything else you could try it on?
Also, there is only about 4MB of storage left on the host hard drive, though that shouldn't keep the target drive from showing up.
4MB??? I've never seen a situation like this, but I suspect it could indeed prevent the Target from showing up. The Host needs some overhead to make things work.
I'm running 10.4.11 on the host and Snow Leopard on the target.
I was going to suggest running Software Update on the Host, but with only 4MB of space, it couldn't install anything anyway.
The target is so full it won't show me anything but Safari, not even the finder, but it is going into target mode every time no problem.
Well, that kills my other idea. I was going to suggest switching Host and Target around.
At this point, I'd suggest getting some external storage so you can offload at least 10-15GBs (ideally, you never want to go under 15% free space available). Then try again.

Range Filter Mode not working and throws error in Power View (SharePoint 2013)

Hi,
I am using two filters in my power view report.
One for the contact type group and one for year.
First I select multiple contact type group for the first filter and everything works fine.
Then I try to select the year using the range filter and I get this error:
System.ArgumentException: The name 'Year' was specified twice, at index 0 and index 1. Duplicate names are not allowed.
Parameter name: keys[1]
at Microsoft.Data.Common.CommandTrees.ExpressionBuilder.Internal.EnumerableValidator`3.Validate(IEnumerable`1 argument, String argumentName, Int32 expectedElementCount, Boolean allowEmpty, Func`3 map, Func`2 collect, Func`3 deriveName)
at Microsoft.Data.Common.CommandTrees.ExpressionBuilder.Internal.EnumerableValidator`3.Validate()
at Microsoft.Data.Common.CommandTrees.ExpressionBuilder.Internal.ArgumentValidation.ValidateGroupBy(DbGroupExpressionBinding input, IEnumerable`1 keys, IEnumerable`1 aggregates, DbExpressionList& validKeys, ReadOnlyCollection`1& validAggregates)
at Microsoft.Reporting.QueryDesign.ExpressionTrees.ExpressionBuilder.Internal.QueryExpressionBuilder.GroupBy(QueryGroupExpressionBinding input, IEnumerable`1 groupItems, IEnumerable`1 aggregates)
at Microsoft.Reporting.QueryDesign.QueryDefinitionModel.Internal.QdmExpressionBuilder.QdmGroupBy(IEnumerable`1 expressions)
at Microsoft.Reporting.QueryDesign.QueryDefinitionModel.Internal.QdmExpressionBuilder.QdmFilter(IGrouping`2 predicates)
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
at Microsoft.Reporting.QueryDesign.QueryDefinitionModel.Internal.QdmExpressionBuilder.QdmFilters(IEnumerable`1 filterConditions)
at Microsoft.Reporting.QueryDesign.QueryDefinitionModel.Internal.FilterQueryFactory.AddRowCount(QueryBuilder queryBuilder, Group group, EntitySet entity, IEnumerable`1 rowCountFilterContext)
at Microsoft.Reporting.QueryDesign.QueryDefinitionModel.Internal.FilterQueryFactory.CreateValueWithCountQuery(QueryBuilder queryBuilder, List`1 columns, IEdmFieldInstance fieldInstance, FilterCondition availableValueFilter, FilterCondition activeValueRetentionFilter,
GroupReference& groupRef)
at Microsoft.Reporting.QueryDesign.QueryDefinitionModel.Internal.FilterQueryFactory.CreateValueListQuery(EntityDataModel model, IEdmFieldInstance fieldInstance, Int32 topCount, FilterCondition availableValueFilter, FilterCondition activeValueRetentionFilter,
IEnumerable`1 exclusionPathSegments, ValueListQuerySchema& schema)
at Microsoft.Reporting.AdHoc.DataStructureManagement.Filtering.Internal.FilterValueQueryFactory.CreateFilterValuesQuery[TFilterMode](TFilterMode filterMode, Int32 maxRowCount, FormulaFilterCondition availableValueFilter, FormulaFilterCondition
activeValueRetentionFilter, ValueListQuerySchema& schema)
at Microsoft.Reporting.AdHoc.DataStructureManagement.Filtering.Internal.ListFilterMode.ListDataLoader.<LoadDataImpl>d__15.MoveNext()
at Microsoft.Reporting.AsyncEnumerator.AsyncEnumeratorBase.MoveNextChecked()
at Microsoft.Reporting.AsyncEnumerator.AsyncEnumeratorBase.ResumeIterator(Boolean synchronous)
at Microsoft.Reporting.AsyncEnumerator.AsyncEnumeratorBase.BeginExecuteCore(IEnumerator`1 asyncMethod)
at Microsoft.Reporting.AsyncEnumerator.AsyncEnumeratorImpl.BeginExecute(Func`2 asyncMethod)
at Microsoft.Reporting.AsyncEnumerator.BeginExecute(Func`2 asyncMethod, AsyncCallback userCallback, Object userState, AsyncEnumeratorSettings settings)
at Microsoft.Reporting.AdHoc.DataStructureManagement.Filtering.Internal.FilterMode.DataLoader`1.BeginLoadData(AsyncCallback userCallback, Object userState)
at Microsoft.Reporting.AdHoc.DataStructureManagement.Filtering.Internal.FilterMode.DataLoader`1.LoadDataAsync()
at Microsoft.Reporting.AdHoc.DataStructureManagement.Filtering.Internal.FieldFilter.LoadDataAsyncCore()
at Microsoft.Reporting.AdHoc.DataStructureManagement.Filtering.Internal.FilterManager.OnEditCompleted()
at Microsoft.Reporting.AdHoc.DataStructureManagement.Filtering.Internal.PageFilterManager.OnEditCompleted()
at Microsoft.Reporting.AdHoc.DataStructureManagement.Filtering.Internal.FilterManager.OnEditCompleted(EventArgs args)
at Microsoft.Practices.Prism.Events.EventSubscription`1.InvokeAction(Action`1 action, TPayload argument)
at Microsoft.Practices.Prism.Events.EventSubscription`1.<>c__DisplayClass2.<GetExecutionStrategy>b__0(Object[] arguments)
at Microsoft.Practices.Prism.Events.EventBase.InternalPublish(Object[] arguments)
at Microsoft.Practices.Prism.Events.CompositePresentationEvent`1.Publish(TPayload payload)
at Microsoft.Reporting.AdHoc.DataStructureManagement.Internal.TransactionManager.EditEventAggregator.Exit()
at Microsoft.Reporting.AdHoc.DataStructureManagement.Internal.TransactionManager.EditEventAggregator.SelectionManager_SelectionResumed(Object sender, EventArgs e)
at Microsoft.Reporting.Util.RaiseEvent(EventHandler eventHandler, Object sender, EventArgs eventArgs)
at Microsoft.Reporting.AdHoc.Shell.Regions.Canvas.Internal.SelectionManager.ResumeSelectionChanges()
at Microsoft.Reporting.AdHoc.Shell.Regions.Canvas.Internal.SelectionManager.<.ctor>b__3(Object s, EventArgs e)
at Microsoft.Reporting.Util.RaiseEvent(EventHandler eventHandler, Object sender, EventArgs eventArgs)
at Microsoft.Reporting.AdHoc.DataManagement.Internal.DataManager.set_HandleRdmChanges(Boolean value)
at Microsoft.Reporting.AdHoc.DataManagement.Internal.DataManager.UndoManager_SuspendRdmHandlingChanged(Object sender, StateChangedEventArgs`1 args)
at Microsoft.Reporting.Util.RaiseEvent[TEventArgs](EventHandler`1 eventHandler, Object sender, TEventArgs eventArgs)
at Microsoft.Reporting.AdHoc.Shell.Services.UndoManagement.Internal.UndoManager.<.ctor>b__0(Object sender, StateChangedEventArgs`1 args)
at Microsoft.Reporting.Util.RaiseEvent[TEventArgs](EventHandler`1 eventHandler, Object sender, TEventArgs eventArgs)
at Microsoft.Reporting.AdHoc.Shell.Services.UndoManagement.Internal.UndoManagerApiProperties.set_SuspendDataManagerRdmHandling(Boolean value)
at Microsoft.Reporting.AdHoc.Shell.Services.UndoManagement.Internal.UndoManagerHasOpenUndoGroupStateImpl.OnUndoGroupCommitting(UndoGroup undoGroup)
at Microsoft.Reporting.AdHoc.Shell.Services.UndoManagement.Internal.UndoManagerHasOpenUndoGroupStateImpl.HandleUndoGroupStateChanged(Object sender, EventArgs args)
at Microsoft.Reporting.Util.RaiseEvent(EventHandler eventHandler, Object sender, EventArgs eventArgs)
at Microsoft.Reporting.AdHoc.Shell.Services.UndoManagement.Internal.UndoGroup.HandleStateEnteredEvent(Object sender, EventArgs args)
at Microsoft.Reporting.Util.RaiseEvent(EventHandler eventHandler, Object sender, EventArgs eventArgs)
at Microsoft.Reporting.AdHoc.Shell.Services.UndoManagement.Internal.UndoGroupCommittingStateImpl.EnterState()
at Microsoft.Reporting.AdHoc.Shell.Services.UndoManagement.Internal.UndoGroup.SetState(UndoGroupStateImpl nextState)
at Microsoft.Reporting.AdHoc.Shell.Services.UndoManagement.Internal.UndoGroupOpenStateImpl.Commit()
at Microsoft.Reporting.AdHoc.Shell.Services.UndoManagement.Internal.UndoGroup.Commit()
at Microsoft.Reporting.AdHoc.DataStructureManagement.Internal.TransactionManager.CompleteTransaction(Transaction transaction, Boolean completedSuccessfully)
at Microsoft.Reporting.AdHoc.DataStructureManagement.Internal.TransactionManager.Transaction.Dispose()
at Microsoft.Reporting.AdHoc.DataStructureManagement.Internal.TransactionalObject.ExecuteInTransaction(Action action)
at Microsoft.Reporting.AdHoc.DataStructureManagement.Filtering.Internal.ValueAndOperatorConditionFilterMode.CreateRangeFilterCore(IList`1 rangeConditions)
at Microsoft.Reporting.AdHoc.DataStructureManagement.Filtering.Internal.NumericRangeFilterMode`1.CreateRangeFilter(FilterValueAndOperator[] rangeConditions)
at Microsoft.Reporting.AdHoc.Shell.Regions.Canvas.Internal.RangeFilterViewModel`1.<get_UpdateRangeBoundsCommand>b__0(Nullable`1 adjType)
at Microsoft.Practices.Prism.Commands.DelegateCommand`1.<>c__DisplayClass6.<.ctor>b__2(Object o)
at Microsoft.Practices.Prism.Commands.DelegateCommandBase.Execute(Object parameter)
at Microsoft.Practices.Prism.Commands.DelegateCommandBase.System.Windows.Input.ICommand.Execute(Object parameter)
at Microsoft.Reporting.Windows.Common.Internal.RangeSlider.FireCommand()
at Microsoft.Reporting.Windows.Common.Internal.RangeSlider.Thumb_DragCompleted(Object sender, DragCompletedEventArgs e)
at System.Windows.Controls.Primitives.Thumb.RaiseDragCompleted(Boolean canceled)
at System.Windows.Controls.Primitives.Thumb.OnLostMouseCapture(MouseEventArgs e)
at System.Windows.Controls.Control.OnLostMouseCapture(Control ctrl, EventArgs e)
at MS.Internal.JoltHelper.FireEvent(IntPtr unmanagedObj, IntPtr unmanagedObjArgs, Int32 argsTypeIndex, Int32 actualArgsTypeIndex, String eventName, UInt32 flags)
If I select List Filter mode and try to achieve this it works fine no issue but when I use range filter this weird problem occurs. Can't I select multiple values using Range Filter Mode ? Isn't that's what it is intended to do ? Is it a known bug ? Any kind
of prior experience or help would be much appreciated.
Vivek Kamath

This looks like it could be a bug. You could file an issue at
http://connect.microsoft.com and include a repro. If this is blocking your business, you could also contact support services and if it is determined to be a defect in a Microsoft product, the support is free.
Brad Syputa, Microsoft Power BI This posting is provided "AS IS" with no warranties.

15 inch early 2011 Macbook Pro to Mid 2010 27 inch Imac Target Display Mode

Hi Guys
I have a early 2011 15" Macbook Pro with thunderpolt port aswell
as a Mid 2010 27" iMac with MiniDisplay port.
I am trying to use the iMac as a second screen for my Macbook.
Both has Mountain Lion on them.
I have both Thunderbolt to Thunderbolt aswell as miniDisplay to MiniDisplay
cables.
I can't get target display mode to work.
The thunderbolt cable doesn't work at all.
The MiniDisplay does seeem to work to an extend but not completeley.
When i plug in the MiniDisplayPort cable to both machines then
the Macbook pro screen becomes blue which means secondary monitor detected.
iMac screen becomes blank. Sometimes i have enough time to see in system preferences that
the Macbook pro actually has a secondary monitor.
But just as it turned blue on the Macbook pro and black on the iMac. It turns blue again
and the iMac returns to it's Desktop.
The exact same happens when i Press Command + F2 on iMac keyboard.
Any help or ideas?

I have a 13"macbook air and a Dec. 2012 iMac 27". Out of the blue it stopped working in Target Display Mode. Switching cables doesn't help, and the iMac and MBair are connect to power. I can see the iMac screen in Share Screen mode on the MB air.
This seems to be an issue, I have encountered eg. in MacRumours:
Jan 11, 2013, 10:17 AM
#5
martinm0
macrumors 6502
Join Date: Feb 2010
I have the same issue with my 2012 27" iMac (3.4, 680MX). When I initiate Target Display mode the iMac goes black and never comes back up. On the laptop I can see the display in Display Preferences, but its as if the backlight doesn't come on in TD mode. (I even did screen sharing into the laptop and can see both displays there.
Anyway, called Apple and they determined its an issue and I have to send in for a replacement.
Anyone else with a 2012 iMac (21.5 or 27), can you please test out Target Display mode and let us know if things are working or not?

Use iMac in Target Display Mode with a Power Mac G4

I would like to connect my Power Mac G4 MDD (Model = http://support.apple.com/kb/SP63) to the new iMac (27 inch, Mid 2010) in Target Display Mode. That is, I want the new iMac to be the display for my Power Mac G4. Has anybody done this (including using the iMac 27 inch, Late 2009, which can also do this)? In a general sort of way, this sort of thing is described on this support page: http://support.apple.com/kb/ht3924.
The problem: The iMac requires a Mini Displayport connection. The PowerMac has ADC and DVI-I display connections and also came with an adapter for converting DVI-I to VGA. How can I convert/adapt to get the appropriate Mini Displayport connection?
Gefen makes a converter (http://www.gefen.com/kvm/dproduct.jsp?prod_id=8913) that will convert DVI-D to Mini Displayport, but the description explicitly says that it will work with DVI-D only while my PowerMac has DVI-I. I know that these are two different, incompatible connections.
Is there another converter that works with DVI-I? Or is there a way to adapt from DVI-I to DVI-D? Or how about a VGA or ADC to Mini Displayport converter?
Thanks.

japamac-
Thanks so much for your reply. You're right on target for what I'm looking for and that article is VERY helpful! If you don't mind, I do have a couple more questions/clarifications.
1) First, I think that I didn't read the Wikipedia reference concerning DVI (http://en.wikipedia.org/wiki/DigitalVisualInterface) closely enough. It includes the following paragraph. If I understand it and what you said, it shouldn't be a problem to connect the male DVI-D of the converter into the female DVI-I socket of my Power Mac. Right?
+The long flat pin on a DVI-I connector is wider than the same pin on a DVI-D connector, so it is not possible to connect a male DVI-I to a female DVI-D by removing the 4 analog pins. It is possible, however, to connect a male DVI-D cable to a female DVI-I connector. Many flat panel LCD monitors have only the DVI-D connection so that a DVI-D male to DVI-D male cable will suffice when connecting the monitor to a computer's DVI-I female connector.+
2) I'm not clear on the difference between the Altona AT-DP200 and the Gefen converter. The Gefen converter is somewhat less expensive, so I'm trying to figure out what the downside is. The article you mentioned says that the ATP-DP200 "doesn't scale images", but that seems to only be an issue if I'm trying to connect other devices (PS3, Blu-ray), not if I just want to connect my Power Mac.
The description of the Gefen converter includes the following drawbacks:
+The only major drawback to Gefen's solution is no support for VGA devices or HDCP. A minor gripe would be the fact that the Gefen device only accepts one input resolution and only outputs one resolution (1920 x 1200 at 60 Hz). These limited options aside, the Gefen device looks like it could do the basic trick of transforming a DVI signal to Mini DisplayPort so that you could use your 27" iMac for a few more purposes, provided that the input signal carries the required 1920 x 1200 resolution.+
I'm not clear on what the practical impact of those limitations would be. I don't think the the lack of support for VGA devices or HDCP is an issue for my application. But I'm wondering about the statement that it only accepts one input resolution and outputs only one resolution (1920 x 1200) and the need for the input signal to carry 1920 x 1200. I take it, first of all, that the Power Mac can supply that input resolution. And, what is the impact of the device only having that resolution output to the iMac screen? That is, how would that look on the screen, ugly or okay? Finally, would the Altona device provide a better looking output on the iMac screen because it can apparently handle different resolutions? The manufacturer's description says, "Resolutions: all resolutions up to 1920x1200 (It is Important to select one of the resolutions that display
is capable of displaying, refer to your display’s users manual)."
Thanks again.

Broken Graphics card Target Display mode

I have a 2009 iMac that now has a faulty graphics card, the computer crashes once photoshop runs.
I don't have the mac at the moment to test, but could I still get target display mode to work?
How well does the mac need to run before TDM can work?. If I power it up, sometimes it won't get any further than the apple logo, can it work then?
Thanks
Matt

I purchased a Belkin AV360 and it did not work with Target Display Mode on my new mid 2011 iMac.
After a bit of searching on why it didn't work I've found all sorts of articles on this issue with older display port devices not working with target display mode on the new Thunderbolt macs. I sure hope this can be resolved with a firmware update, or by someone (Belkin/Kanex) making a new Thunderbolt compatible adapter.
And I don't know if anyone has confirmed it yet since the feature is so hard to take advantage of now, but I'm hoping this years iMac at least accepts 1080P signals in addition to 720P and the native panel resolution. It would be worth the wait for an adapter if it accepts 1080P as well, which would make it at least more future proof since everything has gone to 1080P so rapidly.
I was really counting on my new iMac doubling as a TV/Console display in my room - it was part of what justified the high price of the investment and the convenience of the all-in-one design. I would be very pleased if Apple can help resolve this.

10.7.2 breaks Target Display Mode

You might find that Target Display Mode stops working after you update to 10.7.2 The solution, discovered by JohnAtBurn in https://discussions.apple.com/thread/3363289, is to use Disk Utility to repair permissions. (This may be the first time repairing permissions has actually fixed anything.)

Tight VNC Viewer runs on Windows 7 and is used to connect to PCs running VNC such as Mac OS X with Screen Sharing enabled. Tight VNC has never been installed on the Mac OS X box.
The only difference between when this worked and when it stopped working is the 10.7.2 update which seems to have broken VNC.

How to switch to Target Display Mode under BootCamp?

Hi there,
I am running Windows 7 x64 under bootcamp and want to be able to switch to target display mode.
I can achieve this when running OS/X by hitting Command-F2.
Is there a way to switch to target display mode from within Windows 7 under bootcamp?
I would like to do this so that I can easily switch to target display mode whilst using Windows without having to restart my machine.
Any help would be appreciated.
Cheers,
Bardman

Windows does not have a Target Display mode.

Target Dispay Mode - How to activate it under Bootcamp

I recently bought a brand new iMac 27 inches mac. I occasionally I run Windows 7 under boot camp. I have the latest drivers updated (Boot camp 3.1) and the iMac runs perfect under Windows 7. My only questions is that I need to activate "TARGET DISPLAY MODE" under windows. Under Mac OS X you press command+F2 but that does not work under Windows. I tried every single key combination. How can I activate "TARGET DISPLAY MODE" under Boot Camp?

Hi all,
at the moment Target Display Mode only works in OSX http://support.apple.com/kb/HT3924
Maybe future BootCamp Drivers will enable this feature in BootCamp as well.
But only Apple knows.
Regards
Stefan

Target Display Mode: Lenovo T420 DisplayPort to iMac (2nd screen) does not work

Configuration:
- Laptop Lenovo T420, DisplayPort, Windows 8.1
- DisplayPort cable, Adapter to Mini DisplayPort
- iMac (Intel, 27-inch, Mid 2011) as 2nd screen, connected via Mini DisplayPort Adapter, Mavericks OSX 10.9.1
Problem:
- iMac does not start Target Display Mode
- Even cannot be forced via Cmd + F2 or Cmd - Shift - F2
Test:
- Lenovo via DisplayPort cable to 2nd screen works fine
- Can switch between PC only, Duplicate, Extend display
Question:
- What is wrong?
- What can be done to idenify the root cause?
Kind regards, Marcel.

Hello Marcel,
It sounds like you are wanting to use the iMac in Target Display mode with your PC. Target Display mode is a feature that is supported from one Mac to another Mac according to this article:
OS X Mavericks: Use another Mac as a display
http://support.apple.com/kb/PH14264
Target Display Mode lets you use a Mac as the external display for another, “primary” Mac.
Thank you for using Apple Support Communities.
Cheers,
Sterling

Dec 2012 iMac using bluetooth keyboard will not exit Target Display Mode

Hi! I have a new 27" iMac that I would like to use as a second monitor for my work laptop a late 2011 15" MBP. iMac is on 10.8.3 and Mac Book Pro on 10.7.5. Connected via a thunderbolt cable.
I can toggle on Target Display Mode using the command-F2 keys on my bluetooth keyboard connected to the iMac. If I understand directions correctly, I should use the same keys and keyboard to toggle off – but it doesn't work. I'm able to work around by putting MBP to sleep, which exits the iMac out of TDM.
I can use the work around, but...
1) it's annoying.
2) If I can't use the bluetooth keyboard to toggle, it would be nice to connect it to the MBP for use while in TMD. Unfortunately, the bluetooth keyboard is undiscoverable, presumably because it's still connected to the iMac.
I wonder:
Am I doing something wrong trying to toggle out of TMD using bluetooth keyboard?
or
Is there a way to enter iMac into TMD without using keyboard command? Maybe System Preferences?
Thanks for your help in advance!

Here's the solution: I had the same problem using my 27" iMac as an external display. The issue is, when you go to Target Display mode, your target computer, the iMac 27" locks the screen with your password.
To switch off TDM, type your password in on the iMac keyboard and press the enter key.
Now press COMMAND - F2 and the displays with switch back to two separate displays. :-)
I had to think like a computer to figure that out but it makes sense.
I also have the disappearing mouse pointer and have not figured that one out. I did all the software updates and I did not have this problem until I upgraded to Lion. It is definitely a software issue. I might have to open a case with Apple support. Not happy.
Derrick

No backlight in Target Display Mode on 2012 27" iMac

I am trying to use my new 2012 iMac 27" as an external display for my mid 2011 Mac Mini with Target Display Mode. At first it seems like it's not working when switching as I hit Command + F2 and the screen changes to black. But after shining a flashlight onto the monitor I can see the desktop and dock of my Mac Mini operating system. Mouse control and everything else works, it's just the backlight doesn't light up when connected to the Mac Mini. But hitting Command + F2 again brings it back to the iMac and a normal functioning backlight.
I'm assuming this is a bug in the new iMac because I had a late 2011 iMac 27" (previous generation) hooked up to this same Mac Mini and Target Display Mode worked perfectly between the two. It was even the same exact Thunderbolt cable. I have re-tested the Mac Mini and plugged it into another monitor with a DVI to Mini Display port adapter and it has worked fine. Has anybody else experienced this behavior?

HI - i had this problem too. see my previous post above. I spent weeks on the phone to apple support.
from memory:
1. I had to reinstall the OS (from a download) - but this failed to work
2. So... I had to perform a complete reinstall of the operating system (and wipe all user data)
3. and then restore all my user data.
Everything has worked seamlessly since then - which to me indicates it's a s/w problem and possibly one with something in my user profile? I just reliased I did not try and create a new user and try TDM using that. This would've proved it was a user profile problem or not.. I had one small ocassion where the screen went blank a week ago, but I just quickly pulled the TB cable out and put it back in again - and it was all ok.
So in essence I've been runing OK now since I did the reinstall and restored the user data.
Richard

Target Display Mode not working iMac 27(2012) Bootcamp to iMac 27(2013)

Similar Messages

Maybe you are looking for