Jump to content


Established Members
  • Posts

  • Joined

  • Last visited

joeman1881's Achievements


Newbie (1/14)



  1. Good Morning, I've been trying to find a solution for this one for a while now. In our environment, we typically use the OSDComputerName TS variable to manually name devices. We have about 15 sites and will be rolling out a large count of devices shortly which will be imaged in a centralized location then spread amongst these sites. My thought is to name each device with <site code><serial>. I've been able to name the device with a simple PS to make the name "DL-<Serial>", but that's because I set the "DL-" portion in the PS script. I'm making about 300 flash drives for imaging and want the TS to prompt for OSDComputerName as usual, but then take that 5-digit entry, append the serial, and make the name those characters combined. I found a few samples online, but non seem to properly prompt during OSD. Has anyone successfully pulled this off with a standard Endpoint TS? Thanks in advance!
  2. Hey guys, In short, I'm trying to figure out if I can streamline automation, and deployment process with our current SCCM (current branch 1802) infrastructure. Long story, we are currently piloting In-Tune. Microsoft pitched it as, "this will cut deployment time down to 10 minutes, or less, and you can pull new devices out of the box and pretty much have them ready to go within that same time frame". After the past month or so of testing, we are finding that's not necessarily the case. Devices need to be in OOBE state and don't always necessarily go through the first pass. When they don't go through, they need to be reset which then adds the lengthy 40-minute time-frame plus the 10 minute provisioning. There also seems to be a lack of information for us to troubleshoot errors (unless this is more of a training issue), which ends up creating many additional calls between Microsoft and our team. We have a functional SCCM environment, with packaged apps, etc. I've seen the MDM option in SCCM, but haven't played with it too much. I believe I should be able to Enroll new OOBE wireless devices similar to the way we would with In-Tune using these tools (but keep the devices on prem). My question is hopefully not too vague, is this process pretty well streamlined in config manager? Is there a way to initiate the same device reset that In-Tune can with newer variants of Windows 10? Each of our techs manages between 1000-2000 devices, so I'm trying to simplify things for them and increase productivity. If you have any insight or experience with testing both of these, please feel free to share. Thanks!
  3. I just saw this reply, but that's actually a good thought, because I do reference those logs fairly often. Thanks for the reply!
  4. Thank you for the reply, I appreciate it! I think these commands will come in handy going forward. We probably should be cleaning things up for all deployments whether space is an issue or not.
  5. Anyone know of the best method for clearing cache on a machine mid-OSD? I have a lab of machines I would like to deploy OS and some large apps (IE: CAD, Adobe CS, etc.), but don't have a ton of disk space, and would rather not clear post deployment. Thanks in advance!
  6. I also recently ran into issues with this on a specific desktop that we support. The "Join Domain or Workgroup" line placed immediately after the "Setup Windows and Configuration Manager" line fixed the 25% of the machines that would fail on me. Hopefully this fixes your issues. Let us know either way.
  7. The domain add after "Setup Windows and Config Manager" did the trick in my test. I will report back after we do a few dozen machines. Thanks for the info on the first Network Settings step. I had no idea that it wasn't adding during that step.
  8. Thanks for the advice, I'm definitely going to try the domain add verify line, as I haven't tried that before. If the machine successfully is added initially, will it realize that it's already been added in previous steps, or will it just attempt a re-add (for curiosities sake)? The only reason I typically add my driver package prior to adding to the domain is because I've had several situations in the past where the machine (previous models) just won't add to the domain until I've added the driver package which in-turn installs the NIC driver. I have tried pulling the driver from the softpaq app that HP offers as well as their support site. The odd part is, all of the drivers are installed correctly once the OSD is complete. This is where I'm thinking your confirm step will come into play. One thing I haven't tried is downloading the latest from intel directly and confirming driver versions so I will do that as well. Thanks again! I will be sure to update this accordingly.
  9. Thanks for the reply! The desktop is an HP Prodesk 600 G1 SFF. I will attach a screen shot of the one driver I have in my driver package and a screen shot of the TS. I usually apply a designated drivers package prior to adding to the domain in case NIC doesn't get installed, then toward the end of the first section prior to reboot I will add auto apply in case anything was missed in the driver package. Let me know if you see something I'm missing. This is so bizarre because in 8,000 devices I've never run into this. I'm wondering if there is something wrong in our process, or if it's just something new that I'm missing with current branch and win 10. Another note: We have deployed 1000 plus of this exact model with windows 8.1 and no driver package. Unfortunately without a driver package, I get the same result with Win 10 deployments. Thanks!
  10. Anyone have thoughts on where I might find an answer to where the problem is other than there not being an available network adapter? In addition these machines are being imaged with PXE. Thanks
  11. Hey all, I have an issue deploying windows 10 only to these HP 600 G1 desktops. The issue is only impacting about 25% of machines, and according to my tech's they just retry a few times and eventually they will go through. We have a pretty mixed environment hardware wise, and I'm not seeing this issue on any other type of desktop/laptop. The issue appears to be that the machines don't add to the domain and instead show "No adapters found in environment". This is an issue because the remainder of my TS involves pulling scripts/software from my server using the fqdn, and of course the machine doesn't end up on the domain. My first though was the driver package must have an issue. So I repackaged with just a NIC driver. It worked for me on my test device (that I was able to duplicate issue on prior), so I asked one of the techs to retry their lab of machines. She had 8 more failures out of about 30 machines with the same symptoms. I'll attach a screen shot of the section where I'm finding what I think is the issue, as well as the full smsts.log. Thank you in advance! smsts1.log
  12. Hey all, I think I may have found a bug, just trying to confirm. We have 20ish device OU's in our domain. We have another OU within that same subset that we dump all freshly images devices so hey can receive a custom tiles layout GPO, then they are moved to their respective site later before handed to staff. This allows them to customize tiles if they'd like, but also provide them with our designated tiles. We've been able to successfully do this with all of our HP desktops/laptops, but for some reason the surfaces (specifically SP2) will only get the tiles if we deploy them in a sites OU or Computer OU and then move them to the OU with the tiles GPO. If I run a gpresult I can see they are actually receiving the GPO correctly, but I'm not seeing the change reflected on the start menu. Oddly, deleting the profile when moved to the another OU does nothing, but reimagine and putting the device in another OU then manually moving to the correct Enforced tiles GPO OU is the only way we can get these SP2s to get our custom tiles. Hopefully that's not too confusing....anyone else experiencing issues like this with Surfaces and Windows 10?
  13. Thanks for the reply as always Peter. Is there any simple way to find which updates are missing and download them in the msp format?
  14. Just following up on this. Any insight is appreciated! Thanks
  15. Anyone have any words of wisdom on an office 2013/16 deployment tactic that doesn't involve manually installing updates from WSUS post install? At one point I want to say I found a powershell script that found the missing updates, and downloaded them to a folder so I could copy them to my "office 2013\updates" folder. I wasn't able to find my script from last time so I thought I'd try finding my updates in SCCM then exporting the cab files to the same updates folder, however it seems office will only install files in the ".msp" format. Anyone else found a way to deploy office with current updates included? Thanks in advance!
  • Create New...