Jump to content


Search the Community

Showing results for tags 'Surface'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
    • Windows 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Official Forum Supporters
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Windows Server General
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests

Found 5 results

  1. I am encountering an issue with a Surface Book. The device PXE boots fine, and it pops a message like it's going to start and prompt me for the password. Then, it never pops up, and just reboots. any suggestions? the drivers are distributed, and in my task sequence.
  2. Hi, I have a question regarding surface pro device firmware. We deploy Surface Pro 3s and Pro 4s at our entity. When a new driver/firmware pack is released from MS, we follow the usual instructions in downloading and applying the new driver/firmware pack to the devices. My question however is this- I noticed that if I run a manual windows update on either the surface pro 3 or pro 4, I see another system hardware update within the Windows update menu, when I know we have completed importing the newest drivers/firmware. Does anyone know why this is? I am guessing it is related to the touch panel itself, but I am looking to confirm. thanks.
  3. Hi, We having been deploying Surface devices for sometime now using SCCM R2 SP1 CU3, followed the guides posted here, and have had good luck with these for sometime now. We recently however had to warranty a few surface pro 3 devices for our users, and we are having alot of trouble getting these to format correctly, before failing the task sequence. Note: There have been 0 changes to the Task sequence for sometime, and we are able to image new units. Model: 256GB Surface Pro 3 back from service Prep for imaging: - Disable Secure boot/Clear all keys - Disable TPM - Secure Erase SSD (via surface data eraser tool provided by MS) - Created Offline (USB) Media Imaging: -SP3 starts and loads files to boot into WinPE -Machine name step pops up as normal Next Step, Format and Partition Disk (UEFI) - Hangs and eventually fails out stating that it cannot format the disk (log file attached). This problem remains true if I attempt to image via Offline media, with RMA units only. I left one of the RMA'd devices stock, joined the domain, loaded client, added to a collection and pushed the task sequence for testing/troubleshooting, and I took another Surface we've had on hand for a while, and ran the offline USB image through n through with no issues. The one thing that does stick out, is the internal hard drive vendor. From what we have seen, the majority of the surface units have a Samsung SSD, whereas the RMA units have a Hynix based SSD built in. Being it's a hard drive, the storage drivers should be the same for boot image being the chipset is the same, and vendor should not matter being the same sata protocol. Other than that, I cannot figure out a reason as to why this is happening. trying a new USB stick had no change as well. Has anyone run into or seen anything this before? Update: I found this article, that is basically pointing out the same problem, sadly no solution though- https://social.technet.microsoft.com/Forums/en-US/5a17cf36-d208-4264-ab66-9e483054bcc9/sccm-osd-task-sequence-stuck-at-formatting-c?forum=configmanagerosd - Another kicker, I was able to bring the trouble unit back to the factory image using the recovery USB media created earlier. I went ahead and attempted to image this thing the same way as the other unit- Join domain, add to collection, push TS to unit. Even THAT has failed at the exact same point, where it was no issue for the other one. I'll mess around a little more tomorrow.
  4. Hello, I am trying to PXE boot surface pro 4 and for some reason it does not boot. I get the attached message. It tries to PXE over IP v4, then reaches my correct DP that has PXE and WDS, it finds the correct NBP file SMSBoot\x64\wdsnbp.com (this is specified in DHCP option), it appears to be downloading and NBP file is successfully downloaded. Then without prompting to press Enter key for PXE boot, it moves to IPV6. I have tried below but no luck Upgrade firmware to latest disable secure boot Removed DHCP option - but this time it doesn't even finds my PXE server Verified and made sure MAC address of network adapter is not registered with SCCM DB Tried docking station and no luck I can PXE boot a desktop on same network with no issues. Any suggestions would be helpful Thanks.
  5. I am running into an issue trying to deploy Windows 8.1 to the Surface Pro 3. I followed the directions posted here however since I already have a working MDT/WDS deployment for other machines, I could not run the script. The issue appears to be driver related. I used the link (http://www.microsoft.com/en-us/download/details.aspx?id=38826) and downloaded both the Ethernet and GB Ethernet drivers, added them into my deployment share/OOB Driver section for WinPEx64 and updated my deployment share. The error I receive is as follows "A connection to the deployment share ([path]) could not be made. The Following networking device did not have a driver installed. PCI\VEN_11AB&DEV_2B38&SUBSYS_045E0001&REV00" Photo showing I have the two Microsoft drivers installed under the OOB Driver section. I even change my WinPE settings to include ALL DRIVERS just to make sure it was not somehow picking up the selection profile. http://1drv.ms/1C4sC0P (also attached) Any help would be appreciated. Thank you.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.