Moving to Surface Pro 3: Guidance on Test cases & App Comptability

Hi all,
I am working on a project to roll out Surface Pro 3 with Windows 8.1 from Windows 7 64-bit laptops for close to 100 users. The office has a full-fledged LAN/wireless, external connectivity through VPN with Windows Domain Controllers and many
applications.
I see there are 2 main parts with regards to testing. One is to test the standard windows features including network connectivity and the second is application remediation.
Can you share any test cases for standard windows features that you may have used in similar upgrades?
For checking application compatibility, is Application Compatibility Toolkit (ACT) sufficient to assess the need for any application remediation?
Thanks in advance,
Avinash

Hi Avinash,
The Microsoft Application Compatibility Toolkit (ACT) can be used to reduce the cost and time in resolving application compatibility issues and it can be used to quickly deploy Windows and Windows updates.
Here is a link for reference of using Application Compatibility Toolkit:
Application Compatibility Toolkit (ACT)
http://msdn.microsoft.com/en-us/library/windows/desktop/dd562082(v=vs.85).aspx
Best regards 

Similar Messages

  • Mouse and Touchpad settings Windows 8.1 and Surface Pro 3

    I have a Surface Pro 3 running Windows 8.1.   I noticed that I can no longer use the right or left clicks when using the touch pad on the Surface Pro 3 keyboard. 
    When I go to PC Settings - PC and devices - Mouse and Touchpad I only see the section for the Mouse, touchpad does not display.
    This is occurs with a domain user account.  If I log in as a domain admin (different account) the touchpad settings now appear.  Does anyone have any thoughts?
    If I make the original user and admin or domain admin the results don't change, the touchpad settings still do not display.

    Hi,
    It's hard to troubleshoot since I have no specific Surface pro to do a test.
    Based on your description, when you add the promblematic user account to domain administrator group, the touchpad setting still not appear.
    I suggest you recreate a new local user either admin or standard to check if it could get the correct setting.
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Using Bitlocker Data Recovery Agent (DRA) on Surface Pro 3

    We currently have the Data Recovery Agent (DRA) configured in our Bitlocker Policy for our Windows 7 Systems, and it works fine. In situations where the Recovery Key for the computer object was not backed up to AD correctly for whatever reason or the computer
    object was deleted, our HelpDesk can connect the encrypted drive to another system, and then use the certificate for the DRA to unlock the drive.
    I'm wondering if the BitLocker DRA Certificate unlock method will work for Surface Pro 3 devices, in the case that that their computer object and normal BitLocker recovery key is deleted or missing in AD for whatever reason. Seeing as how our helpdesk can't
    easily remove the internal HD from a Surface Pro 3 (I think only MS can do this?), I'm wondering if this BitLocker recovery option is still an option for Surface Pro 3's and if it is not then if there is another recommended option for Surface Pro 3's and/or
    other Windows 8.1 Tablets used in an enterprise environment.

    noctlos wrote:
    Using linux-3.18 and -3.19 kernels, with wayland/weston v. 1.7. In its own tty, i try to run weston, and I get the following stderr:
    Could anyone help me to figure this out? Thanks.
    Seems that the problem lies in libinput. Maybe you can report that upstream. I suggest you recompile libinput with debug info and do not strip the binaries to obtain better backtraces.
    Edit:
    I have also tried running `swc-launch -- velox`, and get the following error:
    Running on /dev/tty2
    velox: error while loading shared libraries: libinput.so.5: cannot open shared object file: No such file or directory
    Server exited with status 127
    Restoring VT to original state
    So, perhaps I am having some libinput trouble. Does this seem correct?
    Well, that's a different problem. libinput has several soname bumps because of API and ABI incompatibility. You have to rebuild swc against the newest libinput. (Although I'm not sure if swc developer updated the code to new API)
    Edit 2:
    Just to tack this on here for `gnome-session --session=gnome-wayland --debug`
    I'm not expert on this, it may be related to libinput problem. If you don't include GDK_BACKEND=wayland environment variable when launching gnome-wayland.
    Last edited by jdbrown (2015-03-01 08:04:39)

  • Problem on Surface Pro 2

    I've had no luck with power BI on a Surface Pro 2.  I installed the app from the store.  When I open it, it just goes to a blank blue screen.
    I try to uninstall by pressing and holding and pressing uninstall.  The startup icon is gone, but when I go to the store, it says the app is installed.  Please help, this is tremendously frustrating.  How do a force and uninstall so I can
    update?  

    Yup, that is how I tried to uninstall.  I click uninstall and seems to work.  If I go to the store it shows install.  When I reboot the power BI icon is back on my home screen.
    Ace,
    It looks like we need to take this offline with you to troubleshoot it. Please email me. It's edprice at Microsoft.
    Thanks!
    Ed Price, Power BI & SQL Server Customer Program Manager (Blog,
    Small Basic,
    Wiki Ninjas,
    Wiki)
    Answer an interesting question?
    Create a wiki article about it!

  • How to read a password protected pdf on a surface pro 2?

    Has anyone been able to successfully open a password protected PDF on a Surface Pro 2?  The Adobe Reader app doesn't work on the surface pro 2 with protected PDFs.

    Use Adobe Reader XI, the regular Adobe Reader for any Windows system.

  • Move CC from Win 7 laptop to Surface Pro 3 Win 8.1

    Hello all,
    I subscribe to the full CC and I am going to be moving files from a Win 7 laptop to a Win 8.1 Surface Pro 3 in the next week or so and I was wondering...The laptop is my secondary or mobile production machine and it's also used in training adult photography students.  I would prefer to NOT disable the Adobe applications on the laptop prior to completing install and testing on the new machine.  I do understand the license is for two machines but my questions are these.  If the laptop is not powered up and running, would I be able to activate the applications on the new machine to be sure that they function as expected?  Or would I need to test them in the trial mode?  If this is the case, is there any functionality that is not operational while in the trial?  Are there any 'GOTCHAs' in doing this that I should know about from Adobe?
    Advice and direction is appreciated!
    Tony...
    di Sogno Photography

    Tony you can install and activate the software included with your Creative Cloud membership on up to two computers.  You can find additional details regarding the activation process at Activation & deactivation help - http://helpx.adobe.com/x-productkb/policy-pricing/activation-deactivation-products.html.

  • Press and hold on a Surface pro touch screen

    Hi,
    I am having some problems with my Surface Pro, trying to control a relay 'press-and-hold'. When I connect a mouse to the Tablet, Windows registers the left mouse up and down events perfectly, allowing the user to control the relay exactly the way I intended, but when I use the touch screen with either the stylus pen or my finger it only seems to press the LabVIEW on release.
    Does anyone have a solution for this problem?
    Chris

    Jeff-P wrote:
    I just tested this on my touchscreen laptop and got a similar behavior. Windows doesn't seem to be registering the left click when you touch the screen until you release. My guess is that this is related to the press+hold for right click functionality on Windows. When I touch and hold for over a second, I get a right click, but when I touch and hold for a shorter time, I get a left click that only registers when I take my finger off. This is consistent with the way that the Windows UI handles touch as well (test the start button for an example).
    Interestingly, if I change the mechanical action of the LabVIEW boolean to 'Switch Unit Released' I can't actually toggle the button ever because the press and hold does not register as a left click, and eventually registers as a right click.
    Jeff Peacock 
    Product Support Engineer | LabVIEW R&D | National Instruments | Certified LabVIEW Architect 
    Actually, this is expected behavior.  Try clicking a button on any Windows app, then, while holding down the button, move off of it.  The button does not register as pressed.  This feature has saved me any number of times. 
    edit:
    Or do you mean it doesn't even depress the button?
    Bill
    (Mid-Level minion.)
    My support system ensures that I don't look totally incompetent.
    Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

  • Can't PXE boot a Surface Pro 3 after already successfully imaging it

    hey guys. To try to eliminate a lot of the initial question that come up with this issue, I figure I will start with established info.  Our SCCM environment is healthy, and all images, drivers and apps are distributed to all of our DP's. We can image
    PC's and laptops with no issue at all. We use network PXE booting.  Using a 64 bit boot image. Needed drivers are injected into the boot image. Firmware on the Surface was updated.  Using the Surface NIC dongle. THis dongle was only used to image
    this Surface Pro 3 tablet one time. There is no record of the MAC of the dongle in SCCM since I deleted the Surface out, to make it an unknown again.
    So, with a lot of trial and error, I was finally able to get this tab to PXE boot, and then successfully image. Was testing out the new windows 8.1 image I had built.
    Since it ewas successful I wanted to add all of our apps to the TS and test them out in imaging. Well, I can no longer get this thing to PXE boot. It shows trying to Start PXE over IPv4, then just skips to IPv6, then boots up into windows.
    I have delted the secure keys form ther BIOS, then reloaded them.  I have tried hte full shut down method (Holding Volume Up and Power for 15 seconds, then waiting for 10 seconds or longer, then trying to PXE boot. I am getting a valid connection fro
    mthe dongle.
    Nothinhg I try works. Its tries to PXE boot over IPv4, but never gets there.  But I can PXE boot any of our PC's or Laptops,m so its just an issue with this damn Surface Pro 3.
    ANy advice?

    So I finally got our server guy to enable the logging and get that smspxe.log file to be accessible. So here is the info from the log, when I attempt to PXE boot the Surface. I see the last 2 lines where it ignores the request, I just don't know why its
    ignoring it.
    PXE::CNotifyTimer::TimerSignalFunc SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
    PXE::CNotifyTimer::ProcessTimer SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
    Potentially missed device 50:1A:C5:FE:D6:E9 SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
    Cleared Old Devices: 1 / 1 SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
    PXE::CBootImageManager::PerformMaintenenceTasks SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
    PXE::CBootImageManager::PurgeOldImages SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
    Purging old images: 0 SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
    PXE::CNotifyTimer::Init SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
    PXE::CNotifyTimer::CancelTimer SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
    PXE::CNotifyTimer::RegisterTimeout SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
    [172.028.000.223:67] Recv From:[172.028.011.002:67] Len:347 1ad0230 SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
    ============> Received from client: SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
    DHCP message:
     Operation: BootRequest (1)
     Hardware Address type: 1
     Hardware Address Length: 6
     Hop Count: 1
     Transaction ID: 24038353
     Seconds Since Boot: 0
     Client IP Address: 000.000.000.000
     Your IP Address: 000.000.000.000
     Server IP Address: 000.000.000.000
     Relay Agent IP Address: 172.028.011.002
     Hardware Address: 50:1a:c5:fe:d6:e9:
     Magic Cookie: 63538263
     Options:
        Type = 53 DHCP Message Type: 1=DHCPDiscover
        Type = 57 Max DHCP Message Size: 05b8
        Type = 55 Paramerter Request List: 0102030405060c0d0f111216171c28292a2b3233363a3b3c4243618081828384858687
        Type = 97 UUID: 0068745ee6b94c0e21b76054522b6a7e02
        Type = 94 UNDI: 010310
        Type = 93 Client system Arch: 0007
        Type = 60 ClassIdentifier: PXEClient:Arch:00007:UNDI:003016 SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
    <============ SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
    ProcessMessage: Context:0241DF40  dTime:0 SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: DHCP Discover received. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    [172.028.000.223:67] Recv From:[172.028.011.003:67] Len:347 159d1f0 SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
    ============> Received from client: SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
    DHCP message:
     Operation: BootRequest (1)
     Hardware Address type: 1
     Hardware Address Length: 6
     Hop Count: 1
     Transaction ID: 24038353
     Seconds Since Boot: 0
     Client IP Address: 000.000.000.000
     Your IP Address: 000.000.000.000
     Server IP Address: 000.000.000.000
     Relay Agent IP Address: 172.028.011.003
     Hardware Address: 50:1a:c5:fe:d6:e9:
     Magic Cookie: 63538263
     Options:
        Type = 53 DHCP Message Type: 1=DHCPDiscover
        Type = 57 Max DHCP Message Size: 05b8
        Type = 55 Paramerter Request List: 0102030405060c0d0f111216171c28292a2b3233363a3b3c4243618081828384858687
        Type = 97 UUID: 0068745ee6b94c0e21b76054522b6a7e02
        Type = 94 UNDI: 010310
        Type = 93 Client system Arch: 0007
        Type = 60 ClassIdentifier: PXEClient:Arch:00007:UNDI:003016 SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
    <============ SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
    ProcessMessage: Context:0241DE50  dTime:0 SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: DHCP Discover received. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Initialized CStringStream object with string: c7c22c7d-4f40-49f1-b7ed-871c18a07b05;2015-04-14T19:04:37Z. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Initialized CStringStream object with string: c7c22c7d-4f40-49f1-b7ed-871c18a07b05;2015-04-14T19:04:37Z. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Set enterpirse certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Set enterpirse certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Set media certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443  GET /SMS_MP_AltAuth/.sms_aut?MPKEYINFORMATIONEX SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Set media certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443  GET /SMS_MP_AltAuth/.sms_aut?MPKEYINFORMATIONEX SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Setting message signatures. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Setting the authenticator. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443  CCM_POST /ccm_system_AltAuth/request SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Setting message signatures. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Setting the authenticator. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443  CCM_POST /ccm_system_AltAuth/request SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    ::DecompressBuffer(65536) SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Decompression (zlib) succeeded: original size 148, uncompressed size 298. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
     SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    MP_LookupDevice succeeded: 0 1 0 1 0 SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: device is not in the database. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Getting boot action for unknown machine: item key: 2046820352 SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    ::DecompressBuffer(65536) SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Decompression (zlib) succeeded: original size 148, uncompressed size 298. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
     SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    MP_LookupDevice succeeded: 0 1 0 1 0 SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: device is not in the database. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Getting boot action for unknown machine: item key: 2046820352 SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Initialized CStringStream object with string: c7c22c7d-4f40-49f1-b7ed-871c18a07b05;2015-04-14T19:04:37Z. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Set enterpirse certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Initialized CStringStream object with string: c7c22c7d-4f40-49f1-b7ed-871c18a07b05;2015-04-14T19:04:37Z. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Set enterpirse certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Set media certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443  GET /SMS_MP_AltAuth/.sms_aut?MPKEYINFORMATIONEX SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Set media certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443  GET /SMS_MP_AltAuth/.sms_aut?MPKEYINFORMATIONEX SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Setting message signatures. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Setting the authenticator. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443  CCM_POST /ccm_system_AltAuth/request SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Setting message signatures. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Setting the authenticator. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443  CCM_POST /ccm_system_AltAuth/request SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    ::DecompressBuffer(65536) SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Decompression (zlib) succeeded: original size 409, uncompressed size 950. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName=""><Machine><ClientID>c70485df-9130-4b41-b61b-6c9e11b2f69a</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
    LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="10020125" OfferIDTime="4/2/2015 11:12:00 AM" PkgID="100000D0" PackageVersion="" PackagePath BootImageID="10000087" Mandatory="0"/></ClientIDReply>
     SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Client Identity: c70485df-9130-4b41-b61b-6c9e11b2f69a SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: SMSID=c70485df-9130-4b41-b61b-6c9e11b2f69a OfferID=10020125, PackageID=100000D0, PackageVersion=, BootImageID=10000087, PackagePath=http://JAG-SCCM-01E.jonesapparel.com/SMS_DP_SMSPKG$/10000087, Mandatory=0 SMSPXE 4/14/2015
    3:04:37 PM 7484 (0x1D3C)
    50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: found optional advertisement 10020125 SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    ============> Reply to client (DHCPDISCOVER): SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    DHCP message:
     Operation: BootReply (2)
     Hardware Address type: 1
     Hardware Address Length: 6
     Hop Count: 0
     Transaction ID: 24038353
     Seconds Since Boot: 0
     Client IP Address: 000.000.000.000
     Your IP Address: 000.000.000.000
     Server IP Address: 172.028.000.223
     Relay Agent IP Address: 172.028.011.002
     Hardware Address: 50:1a:c5:fe:d6:e9:
     Magic Cookie: 63538263
     Options:
        Type = 53 DHCP Message Type: 2=DHCPOffer
        Type = 54 Server idenitifier: 172.028.000.223
        Type = 97 UUID: 0068745ee6b94c0e21b76054522b6a7e02
        Type = 60 ClassIdentifier: PXEClient SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    <============ SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    ::DecompressBuffer(65536) SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Decompression (zlib) succeeded: original size 409, uncompressed size 950. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName=""><Machine><ClientID>c70485df-9130-4b41-b61b-6c9e11b2f69a</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
    LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="10020125" OfferIDTime="4/2/2015 11:12:00 AM" PkgID="100000D0" PackageVersion="" PackagePath="xx
    BootImageID="10000087" Mandatory="0"/></ClientIDReply>
     SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Client Identity: c70485df-9130-4b41-b61b-6c9e11b2f69a SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: SMSID=c70485df-9130-4b41-b61b-6c9e11b2f69a OfferID=10020125, PackageID=100000D0, PackageVersion=, BootImageID=10000087, PackagePath=http://JAG-SCCM-01E.jonesapparel.com/SMS_DP_SMSPKG$/10000087, Mandatory=0 SMSPXE 4/14/2015
    3:04:37 PM 7480 (0x1D38)
    50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: found optional advertisement 10020125 SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    ============> Reply to client (DHCPDISCOVER): SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    DHCP message:
     Operation: BootReply (2)
     Hardware Address type: 1
     Hardware Address Length: 6
     Hop Count: 0
     Transaction ID: 24038353
     Seconds Since Boot: 0
     Client IP Address: 000.000.000.000
     Your IP Address: 000.000.000.000
     Server IP Address: 172.028.000.223
     Relay Agent IP Address: 172.028.011.003
     Hardware Address: 50:1a:c5:fe:d6:e9:
     Magic Cookie: 63538263
     Options:
        Type = 53 DHCP Message Type: 2=DHCPOffer
        Type = 54 Server idenitifier: 172.028.000.223
        Type = 97 UUID: 0068745ee6b94c0e21b76054522b6a7e02
        Type = 60 ClassIdentifier: PXEClient SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    <============ SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    [172.028.000.223:67] Recv From:[172.028.011.003:67] Len:359 1acbeb0 SMSPXE 4/14/2015 3:04:40 PM 5928 (0x1728)
    [172.028.000.223:67] Recv From:[172.028.011.002:67] Len:359 15a41f0 SMSPXE 4/14/2015 3:04:40 PM 5972 (0x1754)
    ============> Received from client: SMSPXE 4/14/2015 3:04:40 PM 5928 (0x1728)
    ============> Received from client: SMSPXE 4/14/2015 3:04:40 PM 5972 (0x1754)
    DHCP message:
     Operation: BootRequest (1)
     Hardware Address type: 1
     Hardware Address Length: 6
     Hop Count: 1
     Transaction ID: 24038353
     Seconds Since Boot: 0
     Client IP Address: 000.000.000.000
     Your IP Address: 000.000.000.000
     Server IP Address: 000.000.000.000
     Relay Agent IP Address: 172.028.011.003
     Hardware Address: 50:1a:c5:fe:d6:e9:
     Magic Cookie: 63538263
     Options:
        Type = 53 DHCP Message Type: 3=DHCPRequest
        Type = 54 Server idenitifier: 172.028.000.015
        Type = 50 Requested IP: 172.028.011.052
        Type = 57 Max DHCP Message Size: ff00
        Type = 55 Paramerter Request List: 0102030405060c0d0f111216171c28292a2b3233363a3b3c4243618081828384858687
        Type = 97 UUID: 0068745ee6b94c0e21b76054522b6a7e02
        Type = 94 UNDI: 010310
        Type = 93 Client system Arch: 0007
        Type = 60 ClassIdentifier: PXEClient:Arch:00007:UNDI:003016 SMSPXE 4/14/2015 3:04:40 PM 5928 (0x1728)
    DHCP message:
     Operation: BootRequest (1)
     Hardware Address type: 1
     Hardware Address Length: 6
     Hop Count: 1
     Transaction ID: 24038353
     Seconds Since Boot: 0
     Client IP Address: 000.000.000.000
     Your IP Address: 000.000.000.000
     Server IP Address: 000.000.000.000
     Relay Agent IP Address: 172.028.011.002
     Hardware Address: 50:1a:c5:fe:d6:e9:
     Magic Cookie: 63538263
     Options:
        Type = 53 DHCP Message Type: 3=DHCPRequest
        Type = 54 Server idenitifier: 172.028.000.015
        Type = 50 Requested IP: 172.028.011.052
        Type = 57 Max DHCP Message Size: ff00
        Type = 55 Paramerter Request List: 0102030405060c0d0f111216171c28292a2b3233363a3b3c4243618081828384858687
        Type = 97 UUID: 0068745ee6b94c0e21b76054522b6a7e02
        Type = 94 UNDI: 010310
        Type = 93 Client system Arch: 0007
        Type = 60 ClassIdentifier: PXEClient:Arch:00007:UNDI:003016 SMSPXE 4/14/2015 3:04:40 PM 5972 (0x1754)
    <============ SMSPXE 4/14/2015 3:04:40 PM 5928 (0x1728)
    <============ SMSPXE 4/14/2015 3:04:40 PM 5972 (0x1754)
    Ignoring req from [172.028.011.003:67] Dest Server:[172.028.000.015] SMSPXE 4/14/2015 3:04:40 PM 5928 (0x1728)
    Ignoring req from [172.028.011.002:67] Dest Server:[172.028.000.015] SMSPXE 4/14/2015 3:04:40 PM 5972 (0x1754)

  • Lightroom CC stuttering when no internet connection on Surface pro 3, is there a fix?

    Hello,
    In order to see if the creative cloud for photography is suitable for my need I just downloaded the Lightroom CC (6) free test version.
    I used to work previously on Lightroom 5.7.1 retail version (which is working perfectly) on my Surface pro 3 (i5 8gb ram).
    Problem is, as soon I launch Lightroom CC with the WIFI disabled for battery saving on mobility or just no internet access, Lightroom CC is unusable due to  micro-stuttering every 20-30 sec approx.  Browsing the catalog, adjusting pictures, everything in fact.
    I tried to uncheck the GPU setting as I see in different forums, but no differences.
    After coming back at home, and as soon as I connect the WIFI, relaunch Lightoom CC. Everything runs smoothly...
    I tried again the disable WIFI, restart Lightroom CC, stutters again from start.
    Made 10 attempts of each, and every time I have an internet connection with wifi, everything runs smooth without stuttering, and every time I start the application without internet connection Lightroom do microfreeze (other apps runs fine, it's just LR CC).
    Any ideas, cause for me this is completely a No-GO because I will not do tethering with my phone every time I want to use LR.
    Many thanks.
    Anthony.

    Hi, no clues?
    Ok it seems  when I logout my adobe account id from lightroom CC (help => logout), LR is working smoothly without internet connect.
    Is this normal that the application freeze for few seconds on a multicore device when I am logged, because it's trying to do account sync (none of my collections are sync by the way) or by doing licence checks on a free trial version? 
    Is logout the only solution?
    Many thanks.

  • Microsoft Surface Pro 3 or Surface 2??

    Hello,
    I am looking at the Microsoft Surface Pro 3 and the Surface 2. 
    I currently work off a Sony Vaio laptop and it is working OK.  I am not intending to replace it (right now); but, would like something that I can work on in another room or take with me.
    Would like some feedback on both please.
    Thanks!

    Microsoft actually has a really neat small test to see which one is best suited to you. Surface Pro 3 was a great addition to the line that added more features to the tablet.
    From a personal standpoint I love how they redesigned the rear hinge to do better with keyboards.
    To be quite honest though as far as "major features" go the major differences are that the Pro 3's have some i7's while the Pro 2 only had i5's all the way. You can get some cheaper Pro 3's that have only i3's.
    The new Pro 3 also has a larger resolution supposedly.
    Personally, if you use the keyboard like in your lap or something a lot that would be the only reason as to get the Pro 3 instead of the 2. For most people the Pro 2 was plenty good. I see Pro 3 sort of like Windows 8.1 it was an upgrade to Windows 8 not a real difference.
    I am not affiliated with Best Buy nor have I ever been employed by Best Buy. All of my thoughts and posts are of my own opinion and personal experience.
    I may not always know the right answer, but I will always tell you what I do know. I also do free computer analysis and consultation via private message.

  • When Will Microsoft Fix The Problem With Hosted Networking on a Surface Pro 3?

    Surface Pro 3 512GB
    Windows 8.1 with all patches.
    The following is from this thread:
    http://answers.microsoft.com/en-us/windows/forum/windows8_1-networking/netsh-wlan-start-hostednetwork-not-working-on/f414cea9-c110-483c-a3a2-840a4ce317e2?rtAction=1423330004507
    A Microsoft member said it would be better to raise it in technet.
    netsh wlan set hostednetwork mode=allow ssid=test key=12345678
    The hosted network mode has been set to allow.
    The SSID of the hosted network has been successfully changed.
    The user key passphrase of the hosted network has been successfully changed.
    netsh wlan start hostednetwork
    The hosted network couldn't be started.
    A device attached to the system is not functioning
    One of the comments in the thread said:
    "I have the same issue on a Surface pro 3.
    It is related to the fact that they removed VAP support from the wifi driver."
    Now a new wifi driver was included with the latest firmware update (01/15/2015) but it did not fix the problem.
    I
    Please note this is a Surface Pro 3 problem as it works on a Surface Pro 2 running Windows 8.1.
    This problem has been reported to Microsoft by me and I was told "the developers are working on it."  That was six months ago.  I see posts going back a year saying the problem was reported to Microsoft Support.
    When will this be fixed?

    On Sat, 7 Feb 2015 18:06:38 +0000, saberman_Plus_1 wrote:
    >This problem has been reported to Microsoft by me and I was told "the developers are working on it."  That was six months ago.  I see posts going back a year saying the problem was reported to Microsoft Support.
    Do you have a case number? From
    http://answers.microsoft.com/en-us/surface/forum/surfpro2-surfnetwork/how-do-i-get-the-wireless-hosted-network-feature/03657fe5-b8c1-48c5-940a-ae3e13ffe25f
    you've had a couple of contacts with support.
    If you provide case numbers, it would be helpful in escalating further. And more
    specifically, it might help someone from Microsoft determine IF the issue has
    been escalated. While Microsoft has been doing work on the wifi driver for
    nearly the entire time since the SP3 was released, there is no information
    anywhere as to whether this bug is known or not.
    As you also know, I sent it in to the"right" people inside Microsoft and as you
    also know, I did not get a response. (I'm an end user just like you even though
    I'm a Community Moderator on the Surface Forum in Communities).
    -- Barb Bowman

  • How to adjust line sampling frequency in photoshop CC on surface pro 3

    I just got a Surface Pro 3 so that I could work on my art on the go. I am used to working on a mac with a cintiq, but fell for the hype that photoshop was optimized to work with SP3. However, when I try to use the brush tool, my lines look AWFUL! no matter what I do, the lines are wavy and messy looking. I read that PSCC raised the sampling frequency rate so that the line would look better, but I think THAT is exactly why it looks awful. the Surface pro seems to be picking up EVERY microscopic twitch. I cant work like this ... and I am surely not the only person using PSCC on the SP3, as they're ADVERTISED to work together. How do I adjust the sampling frequency so that my line looks as smooth as it does on a Wacom in photoshop? ...because THAT image below.. looks like crap.

    I'm not an artist so I don't draw using my Surface pro 3.  Many have the same issue with wacom tablets and cintigu from what I read.  They seem to be able to solve their concerns by installing a plugin Lazy Nezumi Pro - Mouse and Pen Smoothing for PhotoShop and other Apps Remember I don't draw and have not installed that plug-in so I can not state that it works well on a surface pro 3.
    Doing a Web search  I found this I quote
    Hi guys,
    I'm the author of Lazy Nezumi Pro!
    Here's the situation with the Surface Pro 3: I'm not 100% sure, but I think the people who got LNP to work with the SP3 the ones who have Photoshop CC 2014, which uses the new Windows 8 native tablet API (instead of Wintab, which is very old tech). If you have this version, make sure you enable Windows Ink for it to work right. It's possible that the N-Trig Wintab implementation is just buggy, or that it's doing something very differently than what LNP is expecting (this is probably the case since I have reports that PS works fine without LNP). Unfortunately I won't know more until I get a SP3 myself and do some testing/debugging.
    I'm sorry I can't help more right now, but I'll keep you updated!  

  • Can we access CM 14.0.2 on the Microsoft Surface Pro 3? It will have Microsoft 8.1 Pro on it.

    My name is Cynthia and I work for Chicago Public Schools. We have approximately 400 users of the Primavera CM system. We've had challenges along the way with compatibility issues, but now here's a question I don't have an answer to.
    Is the Surface Pro 3 any different and what are the Java requirements?

    Hi Cynthia, Unfortunately CM 14.0.x has not been tested/certified against Win 8.1 as a web app server. Also there is no certification for integrating CM with MS Surface Pro. For more further information, please submit a SR within CM tech support. Regards, Matías G. Uribe.

  • AirPort Time Capsule (firmware v7.7.3) has slow wifi connection to new Surface Pro 3

    I got a new Surface Pro 3 i7. I have all the updates for it. I ran into a problem that many others also ran into which was very slow WiFi performance. I utilized many troubleshooting methods and sources and I am currently inclined to believe this... the new Marvell AVASTAR Wireless-AC Network Controller drivers are not compatible with my Airport Time Capsule firmware version 7.7.3.
    Has anyone else experienced this?
    Is there another firmware version that works (older or newer)?
    Details:
    I tried all kinds of things, like changing the network drivers on the SP3 to many different versions. Many of the help forums recommended using the drivers dated 4/24/2014. This did seem to help, but not reliably. What I discovered is... if I connect using the SP3 WiFi to my network extension Airport Express on version 7.6.4, I reliably get 20-22 mbps (which is the best I can expect from my network and works great for my needs). But, when I connect to my primary network Airport Time Capsule, the best I can get is 1.5 mbps, but usually between .15 and .9 mbps. It's completely unusable in today's internet environment. At the same time, I used my iPhone and the Airport Utility to verify the connections.  I used SpeedTest.net on my MacBook, iPad, iPhone and Win8.1 HP laptop to verify that every other device was getting the 20+mbps. And they did.  Only the Surface Pro 3 couldn't perform when using WiFi through the Airport Time Capsule. The SP3 does achieve 20+ mbps like all my other devices, but only when connected to the Airport Express.
    The articles I read said that the network drivers on the SP3 seem to require the routers to be updated to the latest versions. Both the Airport Time Capsule and the Airport Express seem to be updated. When I go into their settings using the Airport Utility, there are no updates available.
    Of course this problem isn't replicated at the Microsoft store since they don't have apple routers.  So, their response is to upgrade the routers.  Extremely unhelpful when the Apple software is saying it is upgraded already. I can't believe this new Airport Time Capsule has to be retired because it isn't playing well with others, and I love the automatic backup it is providing for my MacBook. So, somehow, I need the Airport Time Capsule to work with the new WiFi card & drivers on my SP3, just like the SP3 is working properly with the Airport Express.

    Thanks for your input!
    1. No downgrade. Bummer, but understandable.
    2. Completely agree!!! I did too and then I had to redo it because I couldn't install a driver. I had to start all over and reinstall Win 8 then Win 8.1 over it. It was a colossal waste of time and endless frustration. If I can just get it modestly working, I'll take it. It doesn't have to be perfect right now.
    3.  Great suggestion! And the Microsoft forums are also a buzz. One suggestion I tried (and it seems to be working) is to set a separate wireless network name for the 5ghz band. I haven't thoroughly tested it yet, but I'm hopeful.  I t seems to have worked for some, but not others. The next thing I'll try is fixing the channel, but strangely, I didn't see that option in the AirPort Utility app on my iPhone. Is it only available through Mac/PC laptop/desktop software?
    4. Yup. Sigh. I actually have an old linksys. I retired it when I went 100% apple. I was hoping that things would work smoother. And they did! Until this SP3 came into my life. Arg.
    And and a few more details...
    the AirPort Time Capsule is 802.11ac
    the AirPort Express is 802.11n (2nd gen)
    I'm wondering if it is the AC connection that is the issue. Maybe since the Express always connects with n, it is OK....
    Nope. Just tested the SP3 again and it is maintaining it's connection to the AirPort Time Capsule utiling the 802.11a/n/ac mode and connecting to the 5Ghz special network name. So far so good... Fingers crossed...

  • 8620 prints, but then gives error message on Surface Pro 3

    This error message has been bothering me for some time. From day one when I print from my Surface Pro 3, I get an error message that my document (doesn't matter what it is) did not print. About 95% of the time, it actually DID print but I get the error message. So whenever I print, I don't actually know if the error message is bogus or not.  I've tried uninstalling and reinstalling all of the drivers and apps on my surface, but to no avail. Can anyone help me keep my sanity? Here is an example of the error message from just a little bit ago. Notice the error message in the upper right hand corner. And this "test print" did actually print. 

    Hi!, Egan1: Welcome, to Forum !. Please, download and run, the HP Print and Scan Doctor from ... www.hp.com/go/tools

Maybe you are looking for

  • Does keynote widget work in portrait

    I can insert a keynote into an existing chapter (page) or section when in landscape mode but can't get it to when I am in protrait mode - I just get a beep.  Am I doing something wrong?  One time - not sure how I did it,  but I got it to insert in pr

  • Windows 7 SP1 client shows status of "Not Applicable" for every single update

    Windows 7 SP1 client Every update, including all Critical Updates for Windows 7, show a status of "Not Applicable" when running a "Computer Detailed Status Report" The computer is current in updating its status with the WSUS server. I am hoping that

  • Regex for international character sets like [a-zA-Z] + �, Ł, �, etc.

    Hi all! Is there an internationalized equivalent for the pattern "[a-zA-Z]+" which would accept the French, German, Polish or other local characters like "Ł" or "�" or "�"? It's a bad idea to add all of them to the standard regex like "[a-zA-Z���Ł��]

  • Live stream - buffer and replay

    Hi, i have this issue, which i'm pretty sure isn't feasible, but my boss insists that i give it a try, so here we go: i've developed a video player being used by a commercial TV channel, both for its VOD and live stream.  all the video content - live

  • My iPhone is continually turning itself on and off, how do I solve?

    It's turned itself off and then when I tried to turn it back on it continually turns itself n and off! How do I solve it?