PXE Boot a client to connect to a Remote Desktop Session Host/Terminal Server Farm via SCCM 2007

Hi all,
we've got a bunch of old desktops which are destined for disposal but i was wondering if we couldn't use them as disk-free clients to connect to our Remote Desktop farm. I did some digging and have managed to put together an iso which will boot
the machine into WinPE and then connect to our farm. However, since it's an iso i have to use either a cd or usb for this to work. (This is pretty much what i did: http://www.iammacgyver.com/2011/02/easy-rdp-60-from-winpe-30-simple-boot.html) 
What i want to do is to advertise the boot.wim to the client via SCCM so that it boots via PXE and then picks up the WinPE image and connect to the RD farm. I've imported the boot.wim file into SCCM under Boot Images and created an empty Task Sequence
with the boot.wim as its Boot Image. I then advertised this Task Sequence to a collection which contains the old desktop clients. The machine PXE boots ok and loads up WinPE but rather than launch a remote desktop connection, it trundles through the normal
WinPE stages and once it's finished 'Preparing Network Connections' it simply ends and the client reboots.
Is what i'm trying actually possible?
Can anyone tell me why the ISO works yet pushing the boot.wim out as a Boot Image doesn't? I know the boot.wim file (which is the same one present in the ISO) is ok since the client boots into WinPE fine when PXE booted so why doesn't the remote
desktop session conenction launch? How is booting from the ISO different from booting from the PXE boot.wim file?
Slightly long winded problem so many thanks in advance to anyone who can pass some info my way!

It doesn't work because importing it into ConfigMgr injects binaries and the task sequence engine along with the process to launch the engine thus suppressing whatever you've got configured.
Perhaps you could use a pre start command (pre-execution hook in 2007 parlance) to launch your RDP process though.
Jason | http://blog.configmgrftw.com | @jasonsandys

Similar Messages

  • I can not connect to my newly installed local host cf server 9:

    I can not connect to my newly installed local host cf server 9:
    Oops! Firefox could not connect to 127.0.0.1:8500
    Suggestions:
    Try reloading: 127.0.0.1:8500/CFIDE/administrator/monitor/index.cfm
    Search on Google:
    can you help? same message with all 127.0.0.1:8500
    urls, data or server admin....
    Forta I 8/Edition files work with CF SERVER 9?

    I have the same problem, on my primary computer (Windows XP Pro , but the cause may be different from what 123polis123 had.
    It seems that the installer installed the Enterprise Multiserver configuration instead of the built in server.
    Note that I installed sucessfully on my laptop (Windows XP Home), using the same install parameters.
    I chose the "Server configuration" which has a self contained server tunning a single instance with an embedded JEE server.  After running though all the installation screens, before proceeding with the actual installation, the installer reported the following:
    Installation Type:
      Server configuration
    Licensing:
      Developer Edition
    Installation Directories:
      Product: C:\ColdFusion9
      Web root: C:\ColdFusion9\wwwroot
    Server Information:
      Web Server: Built-in web server
      Port: 8500
      ODBC Services: installed
      Search Services: installed
      ColdFusion Solr Search Services: installed
      Microsoft .Net version: v 2.0.50727
      .NET Java Port: 6085
      .NET Client Port: 6086
      Documentation: installed
      RDS: enabled
    Disk Space Information (for Installation Target):
      Required: 1,089,069,939
      Available: 7,387,262,976
    The installation proceeded without a hitch, except at the end when the browser is supposed to come up with the admin configuration page it can't find the server.  Port 8500 is open. I fiddled around awhile to see what the problem was.  I installed on the other computer which went fine - the only difference is that the .NET version is 1.1.4322.   I then re-installed, without uninstalling, on the problem computer.  When the installer got to the screen where I select the server configuration, Enterprise Multiserver configuration was selected and it was not possible to select onything else.   I uninstalled and re-installed.  Same thing happened.
    The processes running included: k2admin.exe, k2index.exe, k2server.exe and CFDotNetsvc.exe.   The processes on the sucessful install included cfp.exe and cfupdate.exe.
    Note that I had installed Eclipse and the CFEclipse plugin before installing CF9.

  • Difference between Terminal server connection and MSTSC remote desktop connection

    Hi everyone , Wats the main difference between Terminal server connection and MSTSC remote desktop connection? Well both are used to connect a server remotely. right!
    Are there any much difference between them?

    RDP is a protocol and MSTSC is the RDP client.
    In the situation you are referring to, you use MSTSC (RDP Client) in both cases, but when you connect to a client PC (Windows 7, Windows XP, etc) you can only connect if nobody is using that PC at the moment, if you connect to a server you can work along with
    some other users. Server OS supports 2 connections by default, if you want more people you need Remote Desktop Services and RDS licenses.
    Thanks,
    сила в справедливости

  • I have an Ipad 2 and here is what I am trying to accomplish.  On my laptop I connect to a remote desktop connection to access a shared program we use for reporting.  How do I set up my Ipad to access this remote server?  Thanks for the help.

    I have an Ipad 2 and here is what I am trying to accomplish.  On my laptop I connect to a remote desktop connection to access a shared program we use for reporting.  How do I set up my Ipad to access this remote server?  Thanks for the help.

    Close ... before going for a specific Cisco app ... lets find out some details:
    Host we need more details:
    What is your server environment (Windows Server, or Mac OS X Server, or Linux)?
    What security is implemented in your environment - as what is restricted (RDP for all or specifc credentials on all machines? Are you part of local admin group to the server you wish to connect)?
    Does your environment Support CISCO IPSec connection? If so use Settings> VPN and IPSec tab to enter VPN details, if not then go with above suggestion. IF your restricted to RSA then either built in VPN settings or 3rd party app for RSA would suffice.
    Finally, there are many RDP applications out there I use "Mocha RDP Light" (free minimal ads when launched not when connecting).

  • Windows 8 crashes when trying to connect to a Remote Desktop or a VPN

    Hello, 
    When trying to perform a connection to a remote desktop or a VPN the application crashes (either MSTSC.exe or Explorer.exe). I've noticed this happens when credentials are about to be asked (same happens when trying to access a restricted folder on a network
    machine).
    Useful PC specs:
    - i7 3770k, 16GB Ram, GTX460 (2x-SLI) (Intel HD 4000 on board)
    > All latest drivers and Windows updates installed.
    > Ran Memory Diagnostic. No errors.
    Event Log:
    Faulting application name: mstsc.exe, version: 6.2.9200.16384, time stamp: 0x50108ae1
    Faulting module name: DUI70.dll, version: 6.2.9200.16384, time stamp: 0x50108e6a
    Exception code: 0xc0000005
    Fault offset: 0x00000000000027ee
    Faulting process ID: 0x994
    Faulting application start time: 0x01cdf16f9b46e882
    Faulting application path: C:\WINDOWS\system32\mstsc.exe
    Faulting module path: C:\WINDOWS\system32\DUI70.dll
    Report ID: dadcc27c-5d62-11e2-bf13-bc5ff4390e7a
    Faulting package full name: 
    Faulting package-relative application ID: 
    WinDbg: (RDP Crash dump with procdump)
    Loading unloaded module list
    This dump file has an exception of interest stored in it.
    The stored exception information can be accessed via .ecxr.
    (994.1118): Access violation - code c0000005 (first/second chance not available)
    dui70!DirectUI::Element::_SetValue+0xe:
    000007fe`c5be27ee 488b01          mov     rax,qword ptr [rcx] ds:00000000`00000000=????????????????
    0:000> .ecxr
    rax=000007fec5cbbd80 rbx=000000989f3afa28 rcx=0000000000000000
    rdx=000007fec5cbbd80 rsi=00000000fffffffd rdi=00000098a3e805b0
    rip=000007fec5be27ee rsp=000000989f23a8b0 rbp=0000000000000000
     r8=0000000000000001  r9=000000989f3afa28 r10=0000000000000000
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=00000098a1d29401
    iopl=0         nv up ei pl nz na pe nc
    cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010200
    dui70!DirectUI::Element::_SetValue+0xe:
    000007fe`c5be27ee 488b01          mov     rax,qword ptr [rcx] ds:00000000`00000000=????????????????
    0:000> !analyze -v
    *                        Exception Analysis                                   *
    GetPageUrlData failed, server returned HTTP status 404
    URL requested: http://watson.microsoft.com/StageOne/mstsc_exe/6_2_9200_16384/50108ae1/dui70_dll/6_2_9200_16384/50108e6a/c0000005/000027ee.htm?Retriage=1
    FAULTING_IP: 
    dui70!DirectUI::Element::_SetValue+e
    000007fe`c5be27ee 488b01          mov     rax,qword ptr [rcx]
    EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff)
    ExceptionAddress: 000007fec5be27ee (dui70!DirectUI::Element::_SetValue+0x000000000000000e)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 0000000000000000
    Attempt to read from address 0000000000000000
    DEFAULT_BUCKET_ID:  NULL_POINTER_READ
    PROCESS_NAME:  mstsc.exe
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    EXCEPTION_PARAMETER1:  0000000000000000
    EXCEPTION_PARAMETER2:  0000000000000000
    READ_ADDRESS:  0000000000000000 
    FOLLOWUP_IP: 
    dui70!DirectUI::Element::_SetValue+e
    000007fe`c5be27ee 488b01          mov     rax,qword ptr [rcx]
    MOD_LIST: <ANALYSIS/>
    NTGLOBALFLAG:  0
    APPLICATION_VERIFIER_FLAGS:  0
    FAULTING_THREAD:  0000000000001118
    PRIMARY_PROBLEM_CLASS:  NULL_POINTER_READ
    BUGCHECK_STR:  APPLICATION_FAULT_NULL_POINTER_READ
    LAST_CONTROL_TRANSFER:  from 000007fec5be7db8 to 000007fec5be27ee
    STACK_TEXT:  
    00000098`9f23a8b0 000007fe`c5be7db8 : 00000098`9f23a950 00000098`00000004 00000098`9f23a954 00000098`9f3afa28 : dui70!DirectUI::Element::_SetValue+0xe
    00000098`9f23a930 000007fe`b5378a73 : 00000098`a3f11208 00000098`9f23aa70 000007fe`b5418c58 000007fe`c4dc20f5 : dui70!DirectUI::Element::SetLayoutPos+0x98
    00000098`9f23a970 000007fe`b53a5f7e : 00000098`a3f154d0 000007fe`b533bd54 00000098`a3ea80e0 00000000`00000000 : authui!UserList::_OnEnumerationSyncReply+0x689
    00000098`9f23af80 000007fe`b5332670 : 00000098`a3f111f0 000007fe`b53212d1 00000098`a3f153a0 00000000`00000001 : authui!CCredDialog::UIJobEvent+0x15e
    00000098`9f23afc0 000007fe`b533cf1b : 00000000`00000000 00000000`00000000 00000000`00000000 000007fe`cae3545f : authui!CEnumerationSyncReplyJob::DeferredExecute+0x20
    00000098`9f23b000 000007fe`b533cfbc : 00000098`a3f111f0 00000000`00000001 00000000`00000000 00000098`0000029e : authui!CDeferredUIThreadJob::Do+0x37
    00000098`9f23b030 000007fe`b53a7f42 : 00000098`a1d29350 00000000`000e0602 00000000`00000002 00000000`000e0602 : authui!CCredentialJobQueue::_ProcessJobs+0x69
    00000098`9f23b070 000007fe`b53a7e76 : 00000000`00000000 00000000`00000000 00000000`00008003 00000000`00000000 : authui!CCredDialog::DialogProc+0xa2
    00000098`9f23b0d0 000007fe`c86ab3b9 : 00000000`00000001 00000098`9f23b241 00000000`00008003 00000000`00000000 : authui!CCredDialog::s_DialogProc+0x66
    00000098`9f23b100 000007fe`c86ab108 : 00000098`9f9522d0 00000000`00000000 00000000`00008003 00000000`00000000 : user32!UserCallDlgProcCheckWow+0x135
    00000098`9f23b1d0 000007fe`c86ab02e : 00000000`00000000 00000000`000e0602 00000000`00008003 000007fe`c4dc120b : user32!DefDlgProcWorker+0xb8
    00000098`9f23b2a0 000007fe`c869171e : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : user32!DefDlgProcW+0x56
    00000098`9f23b2e0 000007fe`c86914d7 : 00000098`9f9522d0 00000098`9f23b4e0 000007f7`f30de800 000007fe`cae31b95 : user32!UserCallWinProcCheckWow+0x13a
    00000098`9f23b3a0 000007fe`c86be067 : 00000098`9f9522d0 00000098`9f9522d0 00000098`9f9522d0 00000000`00000001 : user32!DispatchMessageWorker+0x1a7
    00000098`9f23b420 000007fe`c86bc641 : 00000098`9f9522d0 00000098`9f9522d0 00000000`00000000 00000000`0000c000 : user32!IsDialogMessageW+0x242
    00000098`9f23b4b0 000007fe`c86bb8a3 : 00000000`00000000 00000000`000909fc 000007fe`b53a7e10 00000098`9f3a6cd0 : user32!DialogBox2+0xfc
    00000098`9f23b540 000007fe`c86bb936 : 000007fe`b5320000 00000000`000909fc 000007fe`b53a7e10 000007fe`b53a7df8 : user32!InternalDialogBox+0x113
    00000098`9f23b5a0 000007fe`c86bbc1b : 00000000`00000000 000007fe`b5320000 00000098`9f3a6cd0 00000098`9f3a6cd0 : user32!DialogBoxIndirectParamAorW+0x56
    00000098`9f23b5e0 000007fe`b53a7c91 : 00000000`00000000 00000000`00000000 00000098`9f3a6cd0 00000098`9f3a6cd0 : user32!DialogBoxIndirectParamW+0x1b
    00000098`9f23b620 000007fe`b539d0d0 : 00000098`a1d29350 00000000`00000000 00000098`9f3ec310 000007fe`b7d77987 : authui!CCredDialog::Dialog+0x151
    00000098`9f23b670 000007fe`b7d6d268 : 10458c33`00000029 00000098`9f23b800 00000098`9f3ebac0 000007fe`b7d6d370 : authui!CCredUI::CredUIPromptForWindowsCredentialsW+0x1dc
    00000098`9f23b700 000007fe`b7d6d503 : 00000098`00000003 00000000`00000000 00000098`9f23ba10 00000098`9f3ebac0 : credui!CredUIPromptForWindowsCredentialsWorker+0x310
    00000098`9f23b850 000007fe`ac10c4fd : 00000098`9f3ebac0 00000098`9f23baa0 00000098`9f23ba10 00000098`9f23ba28 : credui!CredUIPromptForWindowsCredentialsW+0x17b
    00000098`9f23b8f0 000007fe`ac0a0a85 : 00000000`00000000 00000098`00000000 00000000`00000000 00000000`00000000 : mstscax!CTscCredentialsQueryUi::PromptForCredentialsNew+0x159
    00000098`9f23b9c0 000007fe`ac09e8e8 : 00000098`9f362f38 00000000`00000000 00000000`00000000 00000098`a0fed860 : mstscax!CTscCredsAssistant::PromptForTsCredentials+0x4e5
    00000098`9f23d050 000007fe`ac0a13f7 : 00000098`9f351050 00000000`00000000 00000000`00000000 00000098`a0f24d50 : mstscax!CTscCredsAssistant::AcquireTsCredentials+0x8f4
    00000098`9f23d770 000007fe`ac0716fb : 00000098`a0f24d50 00000098`a0f24d50 00000000`00000000 00000000`00000000 : mstscax!CTscCredsAssistant::OnSecurityLayerNegotiationComplete+0x1af
    00000098`9f23e000 000007fe`ac179428 : 00000098`00000002 00000098`a0f5fee0 00000098`a0f5fee0 00000000`00000001 : mstscax!CUI::OnSecurityLayerNegotiationComplete+0x11f
    00000098`9f23e060 000007fe`ac179594 : 00000098`a0f1c540 00000000`00000000 00000000`00000000 00000000`00000000 : mstscax!CTSThread::RunQueueEvent+0x104
    00000098`9f23e0b0 000007fe`ac17baf2 : 00000098`a0f1c540 000007fe`c8691742 00000098`a0f1bf30 00000000`00000000 : mstscax!CTSThread::RunAllQueueEvents+0xcc
    00000098`9f23e110 000007fe`ac17bb28 : 00000098`a0f1bf30 00000000`00000000 00000000`00000000 00000000`00000000 : mstscax!CTSThread::OnNotifyThreadEventQueue+0xa6
    00000098`9f23e150 000007fe`abefb451 : 00000000`00000000 00000000`00000000 000061f5`6df98991 ffffffff`ffffffff : mstscax!CTSThread::OnNotifyThreadMessage+0x20
    00000098`9f23e180 000007fe`c869171e : 000007fe`c8691742 00000000`00000000 00000000`00035090 00000098`9f919f70 : mstscax!PAL_System_Win32_ThreadWndProc+0x19
    00000098`9f23e1b0 000007fe`c86914d7 : 00000098`9f94fb70 00000098`9f23e320 000007f7`f30de800 000007fe`abefb438 : user32!UserCallWinProcCheckWow+0x13a
    00000098`9f23e270 000007fe`c86bc6c4 : 00000098`9f950eb0 00000098`9f950eb0 00000000`00000001 00000000`0000c000 : user32!DispatchMessageWorker+0x1a7
    00000098`9f23e2f0 000007fe`c86bb8a3 : 00000000`00000000 00000000`000909fc 000007f7`f331d518 000007fe`c81931b2 : user32!DialogBox2+0x219
    00000098`9f23e380 000007fe`c86bb936 : 000007f7`f32c0000 00000000`000909fc 000007f7`f331d518 00000000`000909fc : user32!InternalDialogBox+0x113
    00000098`9f23e3e0 000007fe`c86bbbe9 : 000007f7`f32c0000 00000098`9f23e4e0 00000000`000909fc 00000000`00000000 : user32!DialogBoxIndirectParamAorW+0x56
    00000098`9f23e420 000007f7`f331d788 : 00000000`000909fc 00000098`9f23e570 00000098`9f23e4e0 ffffffff`ffffffff : user32!DialogBoxParamW+0x69
    00000098`9f23e460 000007f7`f331ce9e : 00000098`a0efedc0 000007f7`f32c7ab0 000007f7`f333b420 00000000`00000000 : mstsc!CDlgBase::CreateModalDialog+0x168
    00000098`9f23e500 000007f7`f32e2604 : 00000098`a0efedc0 00000098`9f23ead0 000007f7`f32c7ab0 00000000`00000000 : mstsc!CDlgBase::DoModal+0x12
    00000098`9f23e540 000007f7`f32dbd6b : 00000098`9f4ec3e0 00000098`9f4ec3e0 000007f7`f32c7ab0 000007f7`f333b420 : mstsc!CDefaultContWndExt::OnConnectionIssued+0xec
    00000098`9f23e9d0 000007f7`f3302bd9 : 000007f7`f32cbb00 000007f7`f32cbb00 00000000`00000000 00000098`a0f1f350 : mstsc!CContainerWnd::StartConnection+0x4d7
    00000098`9f23ee70 000007f7`f3301feb : 00000000`000909fc 00000000`00000111 00000000`000c09be 00000000`00000001 : mstsc!CMainDlg::DialogBoxProc+0xbb9
    00000098`9f23f1b0 000007fe`c86ab3b9 : 00000000`00000001 00000098`9f23f331 00000000`00000111 00000000`00000000 : mstsc!CMainDlg::StaticDialogBoxProc+0x63
    00000098`9f23f1f0 000007fe`c86ab108 : 00000098`9f919f70 00000000`00000000 00000000`00000111 00000000`00000001 : user32!UserCallDlgProcCheckWow+0x135
    00000098`9f23f2c0 000007fe`c86ab02e : 00000000`000c09be 00000098`9f23f500 00000000`00000111 000007fe`cae31b95 : user32!DefDlgProcWorker+0xb8
    00000098`9f23f390 000007fe`c869171e : 00000000`00000001 00000000`00000000 00000000`00000000 000007fe`c8be1535 : user32!DefDlgProcW+0x56
    00000098`9f23f3d0 000007fe`c86d22f9 : 00000000`000c09be 00000000`00000111 00000000`80000000 00000000`00000000 : user32!UserCallWinProcCheckWow+0x13a
    00000098`9f23f490 000007fe`c869487a : 00000000`00000000 00000000`00000000 00000000`00000001 00000098`9f919f70 : user32!SendMessageWorker+0xa72
    00000098`9f23f540 000007fe`c86bbdd3 : 00000000`00090a12 00000098`9f919f70 00000000`000909fc 00000000`000909fc : user32!SendMessageW+0x10a
    00000098`9f23f5a0 000007f7`f3312409 : 00000098`a0ef0080 00000098`a0ef0080 00000000`00000000 00000000`03260475 : user32!IsDialogMessageW+0x40b
    00000098`9f23f630 000007f7`f3312a07 : 000007f7`f32c0000 00000098`9f312374 000007f7`f333b420 000007f7`00000000 : mstsc!TSCMain+0x695
    00000098`9f23f6e0 000007f7`f33319c9 : 00000098`9f313100 00000000`00000000 00000000`00000000 00000000`00000000 : mstsc!WinMain+0x42f
    00000098`9f23f750 000007fe`c8fe167e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : mstsc!ATL::AtlWinModuleTerm+0x375
    00000098`9f23f810 000007fe`cae53501 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x1a
    00000098`9f23f840 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x1d
    STACK_COMMAND:  ~0s; .ecxr ; kb
    SYMBOL_STACK_INDEX:  0
    SYMBOL_NAME:  dui70!DirectUI::Element::_SetValue+e
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: dui70
    IMAGE_NAME:  dui70.dll
    DEBUG_FLR_IMAGE_TIMESTAMP:  50108e6a
    FAILURE_BUCKET_ID:  NULL_POINTER_READ_c0000005_dui70.dll!DirectUI::Element::_SetValue
    BUCKET_ID:  X64_APPLICATION_FAULT_NULL_POINTER_READ_dui70!DirectUI::Element::_SetValue+e
    WATSON_STAGEONE_URL:  http://watson.microsoft.com/StageOne/mstsc_exe/6_2_9200_16384/50108ae1/dui70_dll/6_2_9200_16384/50108e6a/c0000005/000027ee.htm?Retriage=1
    Followup: MachineOwner
    Any ideas what could be the problem and how to resolve this?

    Further proof it's something with credentials/authentication. I found a valid workaround, but I think this one's on Microsoft to actually fix.
    I opened up Remote Desktop Connection, put in my username and clicked the Save Credentials box. Then I edited all the other settings. Saved the RDP connection to my desktop. Then I edited it with notepad, and added the password value. I found a blog that
    provides a program that'll hash the password for you. I used it so I can say its safe:
    http://www.remkoweijnen.nl/blog/2007/10/18/how-rdp-passwords-are-encrypted/
    I put the hashed password in, saved the file. Then used it to connect and it worked. So by bypassing RDP having to ask for credentials, it didn't crash since it doesn't ask. Kind of inconvenient if you have many computers you have to connect in to. But for
    those in a bind this will work for you.
    This one worked for me, no update or installation of software before it broke, but had a "wife-poweroutage" (cable taken out) I'm just not in the mood to reinstall for this. But the above fixed it for me. Thank you!

  • Problems with PXE boot for clients

    Hi,
    I have an environment where I have clients on av VLAN connected to a Cisco 2960X (WS-C2960X-48LPD-L ) with layer 3 configuration. The clients do a PXE boot to get configuration. The thing is that this does not work on all switches. The switches have the exact same configuration, the only thing that differs is Hardware Board Revision Number. (That I can find..) The ones that works has 0x05 and the ones that doesn´t work has 0x12. The PXE server is connected on a different VLAN in the same switch.
    I have configured spanning-tree portfast on the interfaces. I have ip-helper on the VLAN. The PXE server is also the DHCP server.
    Any suggestions?
    Regards,
    Carina

    It seems NIC teaming was configured really incorrectly in this case. Different switches require different configuration with specific settings on the Windows Server side. Sometimes incorrect configurations work when network traffic is low but start behaving
    funny when it increases. The reason behind this is Windows hosts sending back answers to its peers via different physical links, and the switch doesn't expect it and drops "incorrect" frames.
    You can find detailed description of different teaming modes here:
    http://www.aidanfinn.com/?p=14004
    If you use LACP, be sure to set up port channel on Cisco switches or LACP trunk on HP switches. Otherwise you might want to use the Switch Independent mode.
    Evgeniy Lotosh
    MCSE: Server infractructire, MCSE: Messaging

  • Windows 8.1 pro Remote App crashes connecting to 2012 Remote Desktop Web Access published application

    Using 2012 Remote Desktop Web access to gain access to published applications. The workstation was a Windows 8.1 (home) upgraded to Windows 8.1 Pro with the Media Center add on. Launching the url to the login page for the RDW works fine. When the app is
    clicked on to launch the Remote App crashes. How do I get it to properly connect. Other Windows 8.1 pro workstations work. Although none were upgraded from the 8.1 (home) Here is the event.
    Faulting application name: mstsc.exe, version: 6.3.9600.16384, time stamp: 0x5215e2b5
    Faulting module name: ntdll.dll, version: 6.3.9600.17031, time stamp: 0x530895af
    Exception code: 0xc0000005
    Fault offset: 0x0000000000065e8e
    Faulting process id: 0xab4
    Faulting application start time: 0x01cf5f2ed029e83f
    Faulting application path: C:\Windows\System32\mstsc.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: 21a471d6-cb22-11e3-8263-a0886933dd25
    Faulting package full name:
    Faulting package-relative application ID:

    More info.
    The computer is brand new HP.
    Windows 8.1 pro with media center
    processor Intel i7-4700mq - 12gig ram -64bit
    Full windows touch support with 10 touch points 
    The computer is connecting to a 2012 Server hosted on Microsoft's Azure platform. Trying to access applications hosted by this server with Remote Desktop Web services. The computer can RDP using just the mstsc.exe to other computers and to the server with
    no problem.
    The computer presents the following msg box  Body: Remote Desktop Connection has stopped working. I have tried the following to resolve this and narrow the scope:
    -Created a new user account for the computer with admin rights, rebooted and logged in as the new user.
    -Tried a different user account for the portal, that does work. The user does not show up as connected.
    -All MS updates were loaded.
    -Added these changes to the registry to keep alive the connection: HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Gateway\Transports\Rpc-----HttpKeepAliveTimeout=dword:00000001
    And HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client----RDGClientTransport=dword:00000001
    Loaded this update http://support.microsoft.com/kb/2919394/EN-US
    -Removed all printers
    -Removed Antivirus
    -Added the server to HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default
    -Disabled everything in MSCONFIG startup
    -Ran sfc /scannow as administrator - no integrity violations
    Any suggestions?

  • Connection Errors to Remote Desktop from OSX after Domain name change

    We have an issue using Microsoft Remote Desktop from Macs in our school. All was well until we changed the domain name of our RDS servers and installed a new wildcard certificate. Connections work perfectly in Windows 7/8 and also iOS on iPads, but we cannot
    get any Macs to connect having tried OSX 10.7 and 10.9. The error message says the connection failed to load but seems to add a spurious end to the connection string - TS/en-US/Default.aspx - but we cannot trace where this is being picked up.
    We can get to the site in a web browser and sign in to receive the "browser not supported" message in Safari so traffic is obviously getting to the severs.
    Has anyone else had a similar issue? We have spent days poking around with DNS etc but can't seem to make any progress here.

    Hi Jeremy,
    I have tried removing connections and also re-installing the App. We have been using this App since January with no real issues until we made our domain name change - I really don't understand why it works fine in Windows and iOS but not OSX. We are doing
    nothing different to what we have done from day 1.
    Log file from our old connection when it was working looked like this:
    [2014-Mar-24 10:41:43] RDP (0): Final rdp configuration used: redirectcomports=1
    server port=3389
    use multimon=1
    redirectdrives=1
    promptcredentialonce=1
    authentication level=0
    full address=rdsfarm.xxxxxxx.internal
    session bpp=16
    prompt for credentials on client=1
    redirectprinters=1
    drivestoredirect=*
    alternate shell=||OpenMind
    gatewayusagemethod=2
    alternate full address=rdsfarm.xxxxxx.internal
    workspace id=rdsgw.xxxxxxx.internal
    allow font smoothing=1
    redirectposdevices=0
    audiocapturemode=1
    gatewaycredentialssource=0
    remoteapplicationname=OpenMind 2.0
    devicestoredirect=*
    remoteapplicationmode=1
    remoteapplicationprogram=||OpenMind
    enablecredsspsupport=1
    redirectsmartcards=1
    redirectclipboard=1
    span monitors=1
    gatewayprofileusagemethod=1
    gatewayhostname=rds.xxxxxxx.sch.uk
    remoteapplicationcmdline=
    The log file looks very different now, all I am getting is:
    [2014-Jun-17 10:26:41] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Jun-17 10:26:41] RDP (0): lo0 af=18  addr= netmask=
    [2014-Jun-17 10:26:41] RDP (0): lo0 af=30 (AF_INET6)  addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Jun-17 10:26:41] RDP (0): lo0 af=2 (AF_INET)  addr=127.0.0.1 netmask=255.0.0.0
    [2014-Jun-17 10:26:41] RDP (0): lo0 af=30 (AF_INET6)  addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Jun-17 10:26:41] RDP (0): gif0 af=18  addr= netmask=
    [2014-Jun-17 10:26:41] RDP (0): stf0 af=18  addr= netmask=
    [2014-Jun-17 10:26:41] RDP (0): en0 af=18  addr= netmask=
    [2014-Jun-17 10:26:41] RDP (0): en1 af=18  addr= netmask=
    [2014-Jun-17 10:26:41] RDP (0): en1 af=30 (AF_INET6)  addr=fe80::21f:5bff:feb8:3f72%en1 netmask=ffff:ffff:ffff:ffff::
    [2014-Jun-17 10:26:41] RDP (0): en1 af=2 (AF_INET)  addr=192.168.0.65 netmask=255.255.255.0
    [2014-Jun-17 10:26:41] RDP (0): fw0 af=18  addr= netmask=
    [2014-Jun-17 10:26:41] RDP (0): --- END INTERFACE LIST ---
    [2014-Jun-17 10:26:41] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Jun-17 10:26:41] RDP (0): client version: 8.0.24875
    [2014-Jun-17 10:26:41] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Jun-17 10:26:41] RDP (0): correlation id: 9f18df13-7c84-dc4b-a780-e6b77a280000
    [2014-Jun-17 10:26:41] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Jun-17 10:26:41] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Jun-17 11:44:15] RDP (0): *** Application terminated ***
    [2014-Jun-18 09:51:37] RDP (0): *** Application terminated ***
    [2014-Jun-19 12:00:19] RDP (0): *** Application terminated ***
    [2014-Jun-19 12:15:32] RDP (0): *** Application terminated ***
    [2014-Jun-19 12:16:21] RDP (0): *** Application terminated ***

  • Yosemite 10.10.1 Update - Can no longer connect to Windows Remote Desktop

    I use Mac's VPN to create a PPTP VPN connection to our Windows Server at work.  I access the Server using the Microsoft Remote Desktop App from the App Store (v 8.0.10).  After upgrading to Yosemite, I could get the VPN to connect but could not get the Microsoft App to connect to the Server.  I fixed this problem by deleting the VPN Connection and setting it up new from scratch.  It worked fine until the 10.10.1 upgrade.  Now it no longer works and my previous fix does not work.  I also noticed that I totally lose internet connectivity when the VPN is connected - Safari and Outlook Windows app show no internet connection.
    Microsoft App error is :
    Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
    Please help this has broken with both Yosemite updates and now I am up a creek and unable to work remotely.
    Thanks,

    I've only one hint to you, cause I've mot on Mac-Server.
    With 10.7 Apple have switched from Samba (maybe due to licence problems with GPL based stuff) to a own protocol called "XSMB"
    This had caused problems with some NAS systems too.
    Eventually someone have a glue to solve that, as several users have problems with SMB shares since that.
    Lupunus

  • SharePoint site connection with Office Professional Plus 2013 on Terminal Server

    Hi,
    Background info:
    We use multiple Office 365 E3 subscriptions (12 now) and also have an Windows Server 2008 R2 Terminal Server.
    The users may install Office 365 Pro Plus on their local machines and are able to connect to SharePoint online with the Office applications. Now not everyone has a PC so they log in to one of the two Windows Server 2008 R2 Terminal Servers. I do
    however want one big happy family working with SharePoint so I installed Office Professional Plus 2013 and tweaked the Group Policies so that the start up screen and movie arent beeing showed.
    When I log in with my test user on the Terminal Server (who has a E3 subscription) I miss the feature to add a location (to connect to the SharePoint site). I just do not have that feature. When I log in with my domain administrator account who also
    has an E3 subscription, I am able to add a connection.
    There is SO much info on the web about Office 365/Terminal Servers etc but I am not able to find what I was looking for.
    Question:
    What do I need to do so our Domain Users who log in to the Windows Server 2008 R2 Terminal Server are able to open/save files directly to the SharePoint site? How do I add the SharePoint location as shown in the image:

    Hi,
    SharePoint would not exist when Office 2013 initial installed.  After you save a file to a SharePoint library for the first time, you can click
    Save as you do for any file. Please try the following steps:
    1) Add the document (Word file) to a document library on a SharePoint 2013 site
    2) Click on the file within the SharePoint document library.
    3) Click open in Excel
    4) Save the file
    5) Close Excel
    6) Open Excel, select new Blank Workbook, File, Save As, "SharePoint" should now appear.
    Regards,
    George Zhao
    TechNet Community Support

  • Migrating Clients from SCCM 2007 to SCCM 2012 R2 via SCCM 2007 PACKAGE

    I can migrate sccm clients from sccm 2007 to sccm 2012 using sccm 2007 package with sccm 2012 client?
    Thanks!
    Atenciosamente Julio Araujo

    Thanks for help me Peter and Torsten but this documentation says:
    "You cannot upgrade Configuration Manager 2007 clients to System Center 2012 Configuration Manager by using this method.
    In this scenario, use automatic client upgrade, which automatically creates and deploys a package that contains the latest version of the client."
    I Need migrate clients from sccm 2007 to sccm 2012 r2 and
    I thought ofcreate a package in sccm 2007 with a sccm 2012 client.
    Atenciosamente Julio Araujo

  • Set up extended mode multi displays using remote desktop session via thin client device

    I am configuring a Dell WYSE T10 terminal device. I should be able to use 2 monitors in extended desktop mode, but can only get it to work in span mode. I attempted to use RDS on my windows 7 desktop with 2 monitors and connect to server (Server 2008),
    and am getting the same issue.  Am I missing a setting in the RDP configuration, or do I have a deeper issue?

    Hi,
    Open remote desktop connection, under display tab, check the option use all my monitors for the remote session.
    Hope this helps.

  • Issue connecting through Microsoft Remote Desktop Mac - Yosemite 10.10.2 - Remote Desktop Mac 8.0.13

    Hi there,
    Recently at my office I have noticed an issue when I attempt to remote in using my MacBook Air. I can remote in using my iPhone & iPad, just not the MacBook.
    I am able to add a Remote Resource but when I attempt to connect, I just get a white screen rather than a security warning like I do on both my iPhone & iPad. Does anyone have any solutions for this? It appears to be an OS problem.
    Unsure if Microsoft is aware of this?
    ANY help would be much appreciated.

    Hi,
    Can you run other application properly on your MacBook Air?
    Never seen this kind of issue before. For a try check with other MAC device and verify the result. Also can reinstall the app. For further research please collect log as below.
    Microsoft Remote Desktop>About Microsoft Remote Desktop>Send log via email
    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]

  • Win XP Client Cannot Connect to Mac OS X 10.4.4 Server but Win 2000 Can

    Anyone run into this problem? Just basic Apple/Windows stand alone, no domain or interaction with other Windows Servers. User can log on fine with Windows 2000 client, but same user cannot connect with Windows XP client on same network.
    Any workarounds out there?
    Mac G4 MDD, 1GB RAM, 80MB main drive, 400GB data Mac OS X (10.4.4)

    I had trouble with a WinXP client a while back, and
    only vaguely rememeber things I did to fix it. I'm
    thinking it's the Win system, not the Mac. On the win
    machine, try deselecting the box "Enable IEEE 802.1x
    authen. for this network" in the Properties >
    Authentication tab for your network
    interface.
    Thank you for the suggestion. It worked!

  • PXE boot problem: guest VM DHCP request packets not able to reach DHCP server

    Hi Gurus,
      I'm wondering if anyone could help me with this problem. I wanted to install Linux on Oracle VMs using PXE. I set up a DHCP server and the OVM running RHEL6.4 box. The DHCP server worked fine since other PHYSICAL servers could get IPs from this DHCP server. However, DHCP requests from Oracle VMs was not able to reach the DHCP server. So I suspect this is a VM-specific issue.
    If I type in "dhcp net0" on gPXE prompt on the OVS machine(sappire), I can see the requests were being sent from the OVS server (sapphire):
    gPXE> dhcp net0
    DHCP (net0 00:21:f6:00:00:00) .............................................Connection time out (0x4c106035)
    Could not configure net0: Connection time out (0x4c106035)
    gPXE>
    [root@sapphire ~]# tcpdump -i any -n udp dst portrange 67-68
    tcpdump: WARNING: Promiscuous mode not supported on the "any" device
    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
    listening on any, link-type LINUX_SLL (Linux cooked), capture size 96 bytes
    20:47:25.606400 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:21:f6:00:00:00, length: 387
    20:47:25.606549 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:21:f6:00:00:00, length: 387
    20:47:25.606559 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:21:f6:00:00:00, length: 387
    ^C
    12 packets captured
    14 packets received by filter
    0 packets dropped by kernel
    But if I snoop the same on the RHEL6.4 server running DHCP server and OVM, no request can be seen:
    [root@bluestone Desktop]# tcpdump -i any -n udp dst portrange 67-68
    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
    listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
    ^C
    0 packets captured
    0 packets received by filter
    0 packets dropped by kernel
    OVS(sapphire) and OVM(bluestone) are located in the same subnet:
    [root@bluestone network-scripts]# ifconfig -a
    eth0      Link encap:Ethernet  HWaddr 00:14:22:72:7C:27 
              inet addr:192.168.2.48  Bcast:192.168.2.255  Mask:255.255.255.0
              inet6 addr: fe80::214:22ff:fe72:7c27/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:106795 errors:0 dropped:0 overruns:0 frame:0
              TX packets:122056 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:59173975 (56.4 MiB)  TX bytes:25362955 (24.1 MiB)
    [root@sapphire ~]# ifconfig -a
    10049df2fc Link encap:Ethernet  HWaddr 8A:C5:05:83:AF:C9 
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:80 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:33200 (32.4 KiB)  TX bytes:0 (0.0 b)
    eth0      Link encap:Ethernet  HWaddr 00:1A:64:64:DA:64 
              inet addr:192.168.2.202  Bcast:192.168.2.255  Mask:255.255.255.0
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:37664 errors:0 dropped:0 overruns:0 frame:0
              TX packets:38939 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:4537897 (4.3 MiB)  TX bytes:23127790 (22.0 MiB)
    eth0:0    Link encap:Ethernet  HWaddr 00:1A:64:64:DA:64 
              inet addr:192.168.2.212  Bcast:192.168.2.255  Mask:255.255.255.0
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
    [root@sapphire ~]# brctl show
    bridge name    bridge id        STP enabled    interfaces
    10049df2fc        8000.8ac50583afc9    yes        tap7.0
                                tap7.1
                                vif7.0
                                vif7.1
    I turned off iptables and SELinux on the DHCP server, the issue still remained.
    Any help will be highly appriciaited.
    Thanks in advance,
    Alex

    Hi,
    - Do you install Oracle VM Server (OVS) on an emulated environment like Oracle VM VirtualBox ? if yes so you can't do it.
    - Don't forget to configure the Virtual Machines Network and also to add this network to this Virtual Machine.
    I hope this can help you
    Best Regards

Maybe you are looking for