Jump to content


TheHasselhoff

Established Members
  • Content Count

    15
  • Joined

  • Last visited

Community Reputation

0 Neutral

About TheHasselhoff

  • Rank
    Member
  1. Hi! Sorry for the delay in responding. I have tried multiple USB hubs, no effect. It is happening with the Linksys USB3GIG adapters all the time. Every once in a while, it also happens with the Linksys USB300M adapters we have, too. I actually found the chipset (Realtek) drivers from the Realtek website, and this seems to have helped - but with some hardware, the issue still occurs.
  2. Hi everyone! So, I've got a really weird issue, that seems to have just showed up recently in our MDT setup. We image a large variety of Windows tablets, both Windows 7 & 8.1. I've always used a USB hub with a USB NIC (Linksys USB300M, and USB3GIG). It's always worked well - WinPE drivers work great, unit images properly, boots into OS and installs software, joins domain, etc. However, as of last week, we started to notice an issue. During the OSD, it reboots several times during the application installs (as we install several applications during OSD), and also reboots after doma
  3. Hello everyone! Don't know what I'd do with this forum My company is running SCCM 2012 SP1, with MDT integration, for our OSD Task Sequences. Things are working quite well. However, I need to solve a couple of small issues: - As SCCM uses the SYSTEM account to do things, it never logs in as the local Administrator. I'd like it to do this once, at the end of Task Sequence, so that the User folder is created - then log out. (I know I could use a command in the Unattend file, just seeing if something else would be easier.) We need this, as my IT team sometimes copies confidential d
  4. I tried putting a prestart command in, but apparently this happens after initial setup. Not sure where to put a command in, to sleep the initialization part?
  5. I put the x64 and x86 unknown computers in the collection. Beginning to think it has something to do with getting an IP. When I bring up F8, I don't get an IP until after the system wants to reboot (our network administrators have something set on all switches, that now makes computers take 5 seconds or so to get an IP). So, by the time the IP is given out, the script has already errored out. Once I have an IP, I can ping the MP FQDN without issue. Thing is, this wasn't an issue until we rebooted our DP
  6. Hello all - hoping someone can help! We have been getting SCCM2012 (with MDT) set up for a few months now, and all has been well. I have been trying to finish up the OSD portion now. It was working well, except for some driver issues. I ended up having to remove all of the drivers in the system for a clean start, and we also rebooted our DP. I started adding drivers back in, and all seemed well again. However, our USB boot drives no longer work. (We do not use PXE. But our USB drives have always worked well.) When it boots up, it sits at the cmd window for cscript.exe, and never
  7. Hello all, got another question for you! One of the pesky manual steps I currently need to take, after imaging a new computer, is to add it to my proper device collection. Is there any way to have the OSD automatically add the new computer to a specific collection, as part of the OSD? Thank you!
  8. Hello all! Got a question for you. I tried searching everywhere, but to no avail - maybe I'm using the wrong terminology I have been using MDT2012 for a while now, to deploy OSD Task Sequences, and it works great. We have several different images, and variations on each of them. There's about 15 difference sequences. I was able to organize them in MDT2012, into a folder structure - so that the first window that pops up is clean, organized, streamlined, etc. However, I am now trying to migrate to SCCM2012 w/ MDT2012 integrated. Working well so far, except I don't seem to know ho
  9. Hello all! Absolutely love this forum, the information is incredible! I have a question that I haven't found the answer to yet (and I haven't tried to jump into it myself yet). My current setup has SCCM2012 SP1 completely configured and working on the network. We also have MDT2012 SP1 fully operational on its own - this is where we have been (until SCCM was working) imaging all of our computers. Our MDT setup uses an SQL database. Basically, all the database stores is: - MAC address - Computer AD name - OU So, MDT looks at the MAC - and if it's in the database, it knows what
  10. Hi! I will look into the OU script (I am not really using MDT yet, as we have accomplished everything else we need without it so far). Unfortunately, the device number is not related to the serial# (or anything else BIOS-specific). We also do not necessarily use the computers in order. (We also want to be able to use this, in case one of them needs to be reimaged in the future and it cannot boot into Windows.) Thank you!
  11. This will make it easier, but will still require us to type in the names manually. It would be perfect for us, to give SCCM a CSV with the names & MACs, and it do it automatically. (I have to scan the boxes into a spreadsheet with Device#, MAC, and serial# already.) Any ideas? Unfortunately, I am nearly useless in vb scripting
  12. My company currently replaces about 1500 lease-end computers each year. I only have a couple of other people on my team to perform this task. The #1 reason that my team wants to use SCCM is to remove as much of the tedious, "heavy lifting" parts of our requirements as possible. We currently use a thick image, sysprepped and cloned on a HDD duplicator. Each computer boots up, and we have to put a monitor/keyboard/mouse on each one individually - so that we can add to the domain, etc. We then have to manually go into AD and move each one to its proper OU. SCCM seems to have the promise of
  13. Hello all, sorry to bump up an old topic, but this is the exact type of solution we need in my company. We are just getting into SCCM, and I have started testing OSDs. Here's what we do: - each quarter, we go through lease-end replacements of the PCs whose leases are up - the new computer gets a device sticker with a 6-digit number on it; for example, it would look like this: W7-###### - we name the computer W7-###### in AD, and manually put it into the correct OU, right now - the numbers are not necessarily in-sequence (and sometimes one of them gets corrupted and needs to be reimage
×
×
  • Create New...