Jump to content


matt1234

Established Members
  • Content Count

    13
  • Joined

  • Last visited

Community Reputation

1 Neutral

About matt1234

  • Rank
    Member
  1. This works really great thus far! We have only Win10 here at our site, however we run into instances where either a shared version for office is needed, to a standalone .msi for our warehouses. The drop down menu and variable logic allowed me to have multiple "Install applications" steps re-using the same variables. Works like a champ so far! I do have one question: Can someone maybe direct me to where I can modify/expand the image selection drop down menu?
  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 relate
  3. Hi Thadkew, I will reach out and see if I can get ahold of it - and it happens to want to reboot. I'll have to talk to our IT admin onsite at that location and see if I he has any other information other than what I have been provided. From what I understand, there isn't any indication that the TS is going to reboot or not. One thing, that I will be sure to highlight is, when our admin there presses F12 to note what boot image ID and if there is any difference there.
  4. Hi, Our main site has multiple locations, and a few of them within the US support and deploy our images from the main office via SCCM 2012 R2 SP1 CU3. We have been troubleshooting some network issues recently, that I believe we have cleaned up now. However during some deployment testing, we are experiencing some inconsistent results that I hope someone may have an answer or idea of where to look. -Created 4 VMs setup for OSD (testing/troubleshooting) all of the VMs are set for PXE. -All machines boot up and get to the PXE menu and populate the available task sequences with no iss
  5. I know this is way late, time has gotten the best of me... So it turns out, that the issue according to a MS engineer our rep had referred us to, the intel "iastore.sys" driver for 6th generation (Skylake) CPUs (provided by Lenovo) conflicts with the surface pro NIC driver. We ended up creating a separate boot image for surface pro and book devices, and have called it done until we can re-explore this later. I didn't want to leave this one open ended, so hopefully if anyone runs across this post, it will be of some help/direction.
  6. What SCCM version are you using? Have you updated your adk to Win10? How are you trying to image these? (PXE,USB?)
  7. 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 E
  8. I think I got it... Surface Pro 3 Driver Packages: - Win 8.1 (x64) Queries: - " Select * From Win32_ComputerSystem WHERE Model LIKE "%Surface Pro 3%" " - " Select * from Win32_OperatingSystem WHERE Version like "6.3%" AND ProductType="1" AND OSArchitecture = "64-bit" " With those added, this should allow the TS to identify which package to use depending on the desired deployed OS. Does this look correct?
  9. Hi, Our current Task sequence for the Surface pro devices has been working great for sometime. Now with our entity moving towards Windows 10, I'd like to just add on the driver package step in my task sequence to get the needed driver package at it's desired OS. Currently, I have one driver package for Surface devices with all drivers and firmware as shown in the tutorials provided from here. My current WMI query for identifying the device is the basic " Select * From Win32_ComputerSystem WHERE Model LIKE "%Surface Pro 3% " Which works fine for when you have two different generati
  10. For Win 7 based machines depending how you captured, always make sure you have your image index's set correctly in the "Apply Operating System" and "Apply Data Image" steps. Apply OS Step: 2-2 Apply Data Image: 1-1
  11. Hi, I recently have taken on the challenge of creating and deploying images within my company. Everything seems to be going ok, minus a couple GP objects not applying... Within my TS, I have it set to generate a local admin account with a generic PW to use in case I need to get into the machine. Once domain joined, and I log into my domain/admin account ok, and run a GP update. We have 3 local admin/service accounts that should be populating within the users/groups sections. However, they are not doing so. When I look at the event viewer logs under GP, there are no errors, warn
×
×
  • Create New...