Run my PC (image) from Surface Pro 3

I would like to run my work pc image from Surface Pro 3 I recently bought. Is it possible to do if so what needs to be done

Hi,
consider setting up Hyper-V and installing the image into a vm.
MCP/MCSA/MCTS/MCITP

Similar Messages

  • Unistall of Window 10 Technical Preview from surface pro 3

    Hi Team,
                   I have surface pro 3 and installed Preview after making my USB Image, after looking into update and finding out Windows essential connector wont work this, as well RSAT
    is not able to install on preview version as I use pro to manage servers using server manager.
    i tried all option but recovery image is from 8.1 so i guess there is no going back, i lost my License for Windows 8.1 ?
    Thanks
    -Sam
    Sr. Software engineer

    Hi,
    We can try to use Factory recovery image to reset your PC to get back your Windows 8.1:
    Note: This action will wipe out your Surface Pro 3 and all of the data on its hard drive. Please backup your important data first.
    First,
    download      the Surface Pro 3 recovery media, you will need to provide your serial      number of your Surface.
    Next, extract the      contents of the downloaded ZIP file onto a USB drive that has been      formatted with the FAT32 file system. You will need at least 16GB of on      the drive.
    With your Surface      powered off, insert the USB drive.
    Press and hold the      Volume Down button, and then press and release the Power button. When the      Surface logo appears, release the Volume Down button.
    Choose your language and      country, and then go to Troubleshoot > Advanced Options > Command      Prompt.
    Type "diskpart"      then press Enter
    Type "select disk      system" then press Enter. This action will select the drive that the      operating system is loaded on.
    There's no turning back after this next      step…
    Type "clean"      then press Enter. Your hard drive is now erased.
    Type "exit"      then press Enter
    Turn off your Surface      and power it on using the method in Step 4
    Choose your language and      country, and then go to Troubleshoot > Reset your PC
    Click Next
    Click "Yes,      repartition the drives."
    Follow the prompts to      begin the recovery process
    After that, if you encounter the activation issue, please contact Surface support for further help.
    Contact Microsoft Answer Desk for Surface
    https://www.microsoft.com/surface/en-us/support/contact-us/
    Kate Li
    TechNet Community Support

  • Unable to run pse 13 dvd on surface pro while connecting through external dvd drive

    Hello, I purchased pse13 DVD and a portable DVD drive to install this software on surface pro having windows 8.1 but this DVD is not detected on surface. Is there a way I can install this software on my surface?

    You'll have to figure out why the surface isn't showing the DVD drive. For that you'll have to contact Microsoft or the DVD manufacturer to see if the drive is compatible with your Surface.

  • Best way to "transfer" Aperture images from MacBook Pro to iMac?

    I recently purchased a MacBook Pro 15" to import and edit images (within Aperture and CS6 as an external editor) when I'm out in the field shooting.
    I prefer to have all my images in one location and thus desire to copy eveything to my home base iMac when I return home.
    What is the best way to "transfer" those images so that my homebase iMac Aperture Library can recognize the new masters and edited versions?  Complicating this is the desire to "stamp" each image with a metadata preset upon import that I can do either at the laptop import or upon transfer to the iMac.
    I know just enough to be dangerous but clearly there is an optimal way to consolidate and manage images when using two computers.
    Welcome any thoughts from fellow photographers!
    Chris

    Thanks Kirby.  I utilize Aperture 3 by reference instead of a compiled library.  So I have individual folder/projects stored on my laptop.  By exporting as a library, does Aperture bring these folders and related images "with it"?
    What I don't want to lose is any post processing I do in the field which creates separate versions and/or .PSD files.
    Thanks for your continued assistance.
    Chris

  • How to copy DNG images from MacBook Pro onto a flashdrive and paste them into my pictures on my iMac

    When I tried to do this, I couldn't get the image on the flashdrive to open in photoshop. Each time I tried I got a message that said photoshop had crashed. When the flashdrive is plugged into the MacBook the image files look like images. When the flashdrive is plugged into my new iMac (Maverick) the image files just show the DNG icon. Both computers have the Creative Cloud.

    iTunes: How to move [or copy] your music to a new computer [or another drive] - http://support.apple.com/kb/HT4527
    Quick answer if you use iTunes default preferences settings:  Copy the entire iTunes folder (and in doing so all its subfolders and files) intact to the other drive.  Start iTunes with the option (shift on Windows) key held down and guide it to the new location of the library.
    So, you can see your whole iTunes folder on the memory stick after copying from the PC?

  • 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)

  • How do I reinstall Windows 8.1 Pro On A Surface Pro 2?

    I just acquired a Surface Pro 2 with a 512 GB SSD.  I need to create another 410 GB partition  and tried to shrink the Windows (C:) partition.  Unfortunately, even through it only currently uses around 20 GB it will not let me shrink
    it below 241 GB.  I need to get it down to 60 GB. 
    Is there anyway to do this without reinstalling?  If not, what do I have to do to reinstall?
    http://www.saberman.com

    I apologize for the duplicate post but I mistakenly posted in the Windows 7 Hardware Compatibility forum by mistake.
    I just acquired a Surface Pro 2 with a 512 GB SSD.  I need to create another 410 GB partition and tried to shrink the Windows (C:) partition.  Unfortunately, even though it only currently uses around 20 GB it will not let me shrink it below 241
    GB.  I need to get it down to 60 GB. 
    I am trying to determine if it is possible to replace Lenovo Thinkpads some running Windows 7 & some running Windows 8.1 with Surface Pro 2s running Windows 8.1.  The Surface Pro 2 has significantly better resolution and a slightly
    larger SSD plus the touch screen.  Unfortunately, the Lenovos are partitioned with a 40 GB C: drive and a 407 GB V: drive and the applications expect that.
    Is there any way to do this without reinstalling?  If not, what do I have to do to reinstall and create a different deployment image?
    http://www.saberman.com

  • Sharepoint 2010 Surface Pro

    How to upload multiple pictures to a picture library.
    Running SharePoint 2010, Client is Surface Pro.
    Installed Picture Manager 2010.
    Using IE "APP" does not allow the link to upload multiple
    Using Desktop IE the upload multiple files link is there touching it then WebDAV connects and picture manager is launched but then there seems to be no way to select multiple images within the picture manager.

    In SharePoint 2010, the multiple upload requires a few ActiveX controls, so the IE Modern UI App will not work. With Desktop IE, make sure you have an Office 2010 32bit or 2013 32bit client installed with SharePoint Support enabled during the install,
    or SharePoint Designer 2010/2013 if you cannot otherwise get Office client.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • MDT 2013 Fails to Format or Partition disk on Surface Pro 3

    I have been trying to image a Surface Pro 3 using MDT 2013 and have been unable to get past the Format and Partition portion of the deployment.  At first I would get an error that it was unable to format or partition the drive and then after that it
    just reboots after trying for so long.  I am able to image any other device with the same task sequence and have no issue just having an issue with the Surface Pro 3.  Any help would be great.
    Thanks in advance.
    I am getting the error FAILURE (5210)
    ZTI Error - Unhandled error returned by ZTIDISKPART: Object required (424)

    I think our problem is also hardware failure although without re-imaging a working surface pro 3 I can't be sure.
    I tried what imfusio suggested in this thread.
    https://social.technet.microsoft.com/Forums/en-US/d31384bc-4e96-4a5b-a400-637bd6006d81/failure-5456-unable-to-determine-destination-disk-partition-and-or-drive-surface-pro-3?forum=mdt
    Unfortunately the deployment failed with the same ZTI Error - Unhandled error returned by ZTIDISKPART:
    Object required (424)
    I then rebooted into WinPE and ran diskpart, I could see the two volumes (EFI and OSDisk). I then tried to format the OS disk volume using diskpart. I got a paramater is incorrect error and the disk was no longer visible with a 'list disk' command. So it's
    like the format is putting the disk offline. I'm going to try restore one of these surfaces, apply all firmware updates then re-image. If that doesn't work I'm out of ideas.

  • Surface Pro 3 with MDT deployed 8.1 Enterprise integrated Update 1 missing power button?

    I am building / deploying an image for Surface Pro 3. Out of the box the Surface Pro 3 has the power button on start screen next to search button. However when I deploy 8.1U1 Ent the button disappears. Reading
    http://winsupersite.com/windows-8/windows-81-update-1-tip-toggle-power-button it appears depending on if the Surface Pro 3 is defined as Slate or Ultrabook it might or might not default to power button being on. Is this expected behavior, anyone else see
    this?

    Luckily I found
    http://blogs.technet.com/b/askcore/archive/2014/07/15/deploy-windows-to-surface-pro-3-using-microsoft-deployment-toolkit.aspx which goes into more detail and has workarounds for deploying Surface 3.

  • Surface Pro 3 Windows 8.1 Question

    I have imaged a surface pro 3 with MDT but when swiping to the left there is no screen setting and I don't see an option for auto-brightness. Also, it doesn't appear that the surface will auto-rotate between landscape and portrait. Has anyone else seen
    this problem? 

    Hi,
    What do you mean by "when swiping to the left there is no screen setting"? what about the right edge? If you swipe to the right edge, can you see the charm bars? Win+C?
    auto-brightness settings can be turned on by  Change PC settings\PC and devices\Power and sleep\Brightness
    https://www.microsoft.com/surface/en-us/support/personalization-and-ease-of-access/troubleshoot-surface-touchscreen-brightness?lc=1033
    and you can check the auto-rotate settings though this guide:
    http://www.microsoft.com/surface/en-us/support/hardware-and-drivers/troubleshoot-surface-touchscreen-rotation
    Yolanda Zhu
    TechNet Community Support

  • I get an error message when running a back-up from my Macbook Pro: The backup disk image Macbook.sparsebundle could not be accessed (error-1) and the backup did not complete? What is the issue?

    I get an error message when running a back-up from my Macbook Pro: The backup disk image Macbook.sparsebundle could not be accessed (error-1) and the backup did not complete? What is the issue?

    Try Here  >  http://pondini.org/TM/C12.html
    More Info here  >  http://pondini.org/TM/Time_Capsule.html

  • Image down to a Surface Pro with Windows 8.1 Enterprise use PXE fails at Driver Pack Install

    I am using SCCM 2012 SP1 running on windows server 2008 R2 deploying to windows Surface Pro, I am deploying Windows 8.1 Enterprise using PXE.
    It gets the pxe response, formats the HD, deploys the image, downloads the driver package, but when it installs the driver package I get a (0xC0000135) error. When it finishes it boots to windows 8.1 but is missing it's drivers. Here is the dism.log
    2014-06-10 15:49:06, Info                  DISM   PID=160 TID=1704 Scratch directory set to 'C:\_SMSTaskSequence\PkgMgrTemp\'. - CDISMManager::put_ScratchDir
    2014-06-10 15:49:06, Info                  DISM   PID=160 TID=1704 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
    2014-06-10 15:49:06, Info                  DISM   PID=160 TID=1704 Successfully loaded the ImageSession at "X:\WINDOWS\Pkgmgr" - CDISMManager::LoadLocalImageSession
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Failed to get and initialize the PE Provider.  Continuing by assuming
    that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Provider has previously been initialized.  Returning the existing instance.
    - CDISMProviderStore::Internal_GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Provider has previously been initialized.  Returning the existing instance.
    - CDISMProviderStore::Internal_GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Manager: PID=160 TID=1704 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Provider has previously been initialized.  Returning the existing instance.
    - CDISMProviderStore::Internal_GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM.EXE:
    2014-06-10 15:49:06, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
    2014-06-10 15:49:06, Info                  DISM   DISM.EXE:
    2014-06-10 15:49:06, Info                  DISM   DISM.EXE: Host machine information: OS Version=6.2.9200, Running architecture=amd64, Number of processors=4
    2014-06-10 15:49:06, Info                  DISM   DISM.EXE: Dism.exe version: 6.2.9200.16384
    2014-06-10 15:49:06, Info                  DISM   DISM.EXE: Executing command line: "X:\WINDOWS\Pkgmgr\dism.exe" /image:"C:" /windir:"Windows"
    /apply-unattend:"C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"C:\_SMSTaskSequence\PkgMgrTemp\dism.log"
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Loading Provider from location X:\WINDOWS\Pkgmgr\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Connecting to the provider located at X:\WINDOWS\Pkgmgr\FolderProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Loading Provider from location X:\WINDOWS\Pkgmgr\WimProvider.dll - CDISMProviderStore::Internal_GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Connecting to the provider located at X:\WINDOWS\Pkgmgr\WimProvider.dll. -
    CDISMProviderStore::Internal_LoadProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Loading Provider from location X:\WINDOWS\Pkgmgr\VHDProvider.dll - CDISMProviderStore::Internal_GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Connecting to the provider located at X:\WINDOWS\Pkgmgr\VHDProvider.dll. -
    CDISMProviderStore::Internal_LoadProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Loading Provider from location X:\WINDOWS\Pkgmgr\ImagingProvider.dll - CDISMProviderStore::Internal_GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Connecting to the provider located at X:\WINDOWS\Pkgmgr\ImagingProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Loading Provider from location X:\WINDOWS\Pkgmgr\CompatProvider.dll - CDISMProviderStore::Internal_GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Connecting to the provider located at X:\WINDOWS\Pkgmgr\CompatProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2014-06-10 15:49:06, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
    2014-06-10 15:49:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
    2014-06-10 15:49:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FolderManager
    2014-06-10 15:49:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: WimManager
    2014-06-10 15:49:06, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: WimManager.
    2014-06-10 15:49:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: VHDManager
    2014-06-10 15:49:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: GenericImagingManager
    2014-06-10 15:49:06, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.
    2014-06-10 15:49:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
    2014-06-10 15:49:06, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
    [160] [0x80070002] FIOReadFileIntoBuffer:(1415): The system cannot find the file specified.
    [160] [0xc142011c] UnmarshallImageHandleFromDirectory:(511)
    [160] [0xc142011c] WIMGetMountedImageHandle:(2568)
    2014-06-10 15:49:06, Info                  DISM   DISM WIM Provider: PID=160 TID=1704 [C:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
    2014-06-10 15:49:06, Info                  DISM   DISM VHD Provider: PID=160 TID=1704 [C:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Getting Provider VHDManager - CDISMProviderStore::GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Provider has previously been initialized.  Returning the existing instance.
    - CDISMProviderStore::Internal_GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM VHD Provider: PID=160 TID=1704 [C:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
    2014-06-10 15:49:06, Info                  DISM   DISM Imaging Provider: PID=160 TID=1704 The provider VHDManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Getting Provider WimManager - CDISMProviderStore::GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Provider has previously been initialized.  Returning the existing instance.
    - CDISMProviderStore::Internal_GetProvider
    [160] [0x80070002] FIOReadFileIntoBuffer:(1415): The system cannot find the file specified.
    [160] [0xc142011c] UnmarshallImageHandleFromDirectory:(511)
    [160] [0xc142011c] WIMGetMountedImageHandle:(2568)
    2014-06-10 15:49:06, Info                  DISM   DISM WIM Provider: PID=160 TID=1704 [C:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
    2014-06-10 15:49:06, Info                  DISM   DISM Imaging Provider: PID=160 TID=1704 The provider WimManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage
    2014-06-10 15:49:06, Info                  DISM   DISM Imaging Provider: PID=160 TID=1704 No imaging provider supported CreateDismImage for this path - CGenericImagingManager::CreateDismImage
    2014-06-10 15:49:06, Info                  DISM   DISM Manager: PID=160 TID=1704 physical location path: C:\ - CDISMManager::CreateImageSession
    2014-06-10 15:49:06, Info                  DISM   DISM Manager: PID=160 TID=1704 Copying DISM from "C:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
    2014-06-10 15:50:07, Error                 DISM   DismHostLib: Failed to create DismHostManager remote object. Checking for dismhost.exe exit code.
    2014-06-10 15:50:07, Info                  DISM   DismHostLib: Found dismhost.exe exit code.
    2014-06-10 15:50:07, Error                 DISM   DISM Manager: PID=160 TID=1704 Failed to create Dism Image Session in host. - CDISMManager::LoadRemoteImageSession(hr:0xc0000135)
    2014-06-10 15:50:07, Warning               DISM   DISM Manager: PID=160 TID=1704 A problem ocurred loading the image session. Retrying...  - CDISMManager::CreateImageSession(hr:0xc0000135)
    2014-06-10 15:50:07, Info                  DISM   DISM Manager: PID=160 TID=1704 Copying DISM from "C:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
    2014-06-10 15:51:08, Error                 DISM   DismHostLib: Failed to create DismHostManager remote object. Checking for dismhost.exe exit code.
    2014-06-10 15:51:08, Info                  DISM   DismHostLib: Found dismhost.exe exit code.
    2014-06-10 15:51:08, Error                 DISM   DISM Manager: PID=160 TID=1704 Failed to create Dism Image Session in host. - CDISMManager::LoadRemoteImageSession(hr:0xc0000135)
    2014-06-10 15:51:08, Error                 DISM   DISM Manager: PID=160 TID=1704 Failed to load the image session from the temporary location: C:\_SMSTaskSequence\PkgMgrTemp\82E1FB72-A2BA-4355-B95D-2AC1A905B6D4
    - CDISMManager::CreateImageSession(hr:0xc0000135)
    2014-06-10 15:51:08, Error                 DISM   DISM.EXE: Could not load the image session. HRESULT=C0000135
    2014-06-10 15:51:08, Error                 DISM   DISM.EXE: Unable to start the servicing process for the image at 'C:\'. HRESULT=C0000135
    2014-06-10 15:51:08, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
    2014-06-10 15:51:08, Info                  DISM   DISM.EXE:
    2014-06-10 15:51:08, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
    2014-06-10 15:51:08, Info                  DISM   DISM.EXE:
    2014-06-10 15:51:08, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Found the OSServices.  Waiting to finalize it until all other providers
    are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2014-06-10 15:51:08, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
    2014-06-10 15:51:08, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
    2014-06-10 15:51:08, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
    2014-06-10 15:51:08, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
    2014-06-10 15:51:08, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
    2014-06-10 15:51:08, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

    Hi,
    This might cause the newer version .wim cannot be modified by the lower version dism.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • SFC and System Restore errors on Surface Pro 3 running Win 8.1

      Yesterday evening, my boss sent me an email complaining about problems mapping network drives (Server 2008r2) and connecting to the office LAN after setting up offline files. He tried troubleshooting to no avail. I suggested SFC.exe and/or a systems
    restore. However neither one worked.
     System restore failed to extract file C:\Users\...\local\Packages\microsoft.windowscommunicationsapps_8v from the restore point.
      Unspecified error (0x8007045b)
     SFC.exe /scannow does report that it found errors, but could not fix them.  I have a CBS.log file that I could post somewhere...
     All this on a Surface Pro 3 running Windows 8.1
    James A. Helfer | COMPUTER SYSTEMS ADMINISTRATOR WTW ARCHITECTS | PITTSBURGH PA

    Stumped here. System restore reports same
    C:\Users\...\local\Packages\microsoft.windowscommunicationsapps_8v from the restore point.
      Unspecified error (0x8007045b)
    SFC 3x squeaky clean
    DISM /Online /Cleanup-Image /RestoreHealth  reported success. Still same issue - unable to do any system restore from any restore point.
    (trying to restore because suddenly Miracast went off to a parallel universe on my SP3..)
    --I've run SFC and DISM multiple times. Neither find any errors. I'm stumped--
    and Volume Shadow Copy Service is running...
    -- Barb Bowman

  • Is it possible to install and run Acrobat Standard or Pro on a Surface Pro 2 tablet?

    Does anyone know if is possible install and run Acrobat Standard or Professional on a Surface Pro 2?
    and, if is possible to use COM automation to fill AcroForms?
    Thanks and regards,
    Adolfo

    Does it run regular Windows 8 (allowing you to install the same apps as older versions of Windows in the desktop) or does it run Windows 8 RT, where only apps from the Windows Store are allowed? It looks like regular Windows 8, in which case you can try out the free trial of Acrobat Pro.
    If it works, the Acrobat SDK (separate download) has all developer information on Acrobat, and you need it (give up any idea you will find code ready for use on Google...)

Maybe you are looking for