Jump to content


lcruisader

Established Members
  • Posts

    10
  • Joined

  • Last visited

lcruisader's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Collaborator Rare
  • Week One Done Rare
  • One Month Later Rare
  • One Year In Rare

Recent Badges

0

Reputation

  1. Brief and to the point, ConfigMGR CB1702 w/MDT 8443 integrated. Deploying Windows 7 x64 w/SP1 virgin WIM with however KMDF, NVME injected. Deploying to Dell hardware (Latitude 7280, 7440,etc.) in UEFI mode using either NVME or SSD hard drives. Nic is Intel I219-LM, driver e1d65x64 versions 12 – 22. After WinPE phase and Windows 7 does OOBE, reboots. Windows does a little more automatic setup and the T.S. continues and starts Setup Windows and ConfigMGR step. Pressing F8 now or 1hr later (yes, literally this takes that long if computer has no IP) ipconfig shows a 169.x.x.x address. I launch device manager from the command prompt here, and the NIC drivers are loaded. Ipconfig/renew does work and gets an IP and then all is well. Any ideas why Windows isn’t pulling an IP at the Setup Windows and ConfigMGR step? I’ve tried configuring the network settings step to pull DHCP, a restart step after drivers which only causes the T.S. to fail, new T.S., different Vlans, net cables, numerous drivers from Intel and Dell and even extracted drivers from a prebuilt system from Dell. No joy. My Windows 10 deployments work just fine and so was this Windows 7 until flash drives showed up. And yes my VM’s build just fine. This definitely points to something to do with the Nic, but what? ‘Really need your help.
  2. team, I have Offices spread about the world with DPs at each of them. I'm cooking with Config Man CB 1702, Single site. 14 internal DPs and 1 internet facing DP. Shiny. Albeit Drivers, Packages or Applications; not every site (office) requires all content I have to offer. I have a single OSD TS I'd like to use, but I cannot afford distributing every package to every DP around the globe. e.g. a site sporting only laptops does not need to have all desktop drivers on their DP. The problem and question is: How do I keep the TS from failing it's dependency check when a laptop only site UEFI PXE boots to run this single OSD TS and cannot find a package on it's DP; for this example the Desktop driver Packages? In advance, thank you kindly
  3. Swampgoose, how did you get passed this issue? I'm having same problem
  4. Read your logs Fella's. Using the red highlighted line as a starting point, as I looked up several lines the answer was in front of me the whole time: Input Error: Can not find script file "C:\_SMSTaskSequence\WDPackage\Scripts\ZTIPatches.wsf". in my T.S. you see I have the MDT toolkit and gather BEFORE the PARTITION & FORMAT step. not smart unless I add those steps again after the Partition & Format step. Now my Language pack installs. All that's left to figure out is why these do NOT get set: Input Method and Display language. The System Locale, Format and Location settings DO get set.
  5. Niall, Good post. I can use help. See my screen shot below, on the step: Install Language Packs Offline my T.S. fails with Incorrect Function 0000001 in the SMSTS.log Any ideas? Thanks
  6. I have a CM 2012 R2 environment. Deploying Windows 7 x64. Via offline servicing in Config man I've patched my win 7 wim image successfully and updated the image on the DPs. I test the image by performing a regular OSD. While the image itself works fine, During OSD I run apply mandatory updates action which finds the same 30 patches I just applied during servicing. I've confirmed the patches are in the image. What is causing this and how can I get around this? Thanks in advance for your help.
  7. I'm having these same problems as the OP. Some computers and servers last week simply started to fail def updates. They where working for several months. On the scep client, it says connection failed. The logs suggest scep is trying MS DIRECTLY opposed to my DP. How do I force scep back to my DP? I have checked my GPO and all is fine there. It points to my DP.
×
×
  • 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.