Jump to content


Established Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Phylum

  • Rank

Recent Profile Visitors

1,014 profile views
  1. Thanks for the reply Niall! By the way congrats on the book! I did see your post prior to posting but a. I was hoping to avoid having to create new boot media b. The time is already correct before getting the list of Task Sequences c. Although running the following will 'update' the time, the underlying problem still exists net use \\server_name\ipc$ /user:domain\user Passw0rd! net time \\server_name /set /y d. Once he TS starts, its process is to default to the Time Zone already set in WinPE and update the date/time accordingly. Wish there was an option to simply use the BIOS date/
  2. Consider the following: The BIOS date & time are correct Date & time remain correct up until the Task Sequence selection screen Once a Task Sequence is selected, the date & time are updated to the built-in WinPE timezone, thus making it the incorrect time. Is this normal and expected behavior?
  3. Thanks for the reply GarthMJ. I updated the original post but in short Attended: One or more users is logged into it, be it physically or via RDP. The machine may be actively being used (e.g.: user is doing something) OR it may just be locked (e.g.: user locked the workstation before going to lunch) Unattended: Machine is powered up and no users are logged into it; Presumably sitting at the login screen.
  4. Is it possible for ConfigMgr to determine whether or not a machine is attended or unattended? Attended: One or more users is logged into it, be it physically or via RDP. The machine may be actively being used (e.g.: user is doing something) OR it may just be locked (e.g.: user locked the workstation before going to lunch) Unattended: Machine is powered up and no users are logged into it; Presumably sitting at the login screen. If so, what would the query look like? There are several possible scripted solutions online but I was hoping to tap into a built-in SCCM attribute class/attribut
  5. Agreed - nice find and we do appreciate you sharing! I do have some questions if you can recall any details at this point: What was the troubleshooting process that led you there? What update(s) failed? What process is responsible for writing out those keys: The updates themselves? Windows Update Agent? Windows? Do all three keys need to be present for this condition (problem) to exist, or is it any combination of one or more? Thanks!
  6. I encountered this today after upgrading from: SCCM 2012 R2 SP1 MDT 2013 ADK 8.1 To: SCCM 2012 R2 SP1 + CU1 KB3074875 + Hotfix KB3084586 MDT 2013 Update 1 ADK 10 As crazy as this sounds, a reboot solved the issue. You see, after applying the SCCM updates, we bounced the box but didn't bounce it after installing the ADK and MDT. We attempted to build several boot images but it always failed with: Started processing. Creating boot image. Copying WIM file. Mounting WIM file. WIM file mounted. Setting Windows PE system root. Set Windows PE system root. Set Windows PE scratch space. Adding
  7. I went through a number of tests using diskpart, bootrec and mbrwiz. Yesterday I had a troubleshooting session with Microsoft who provided me with two versions of dskprobe (v2 & v3). They were able to witness that every time, the commands 'succeeded' but the MBR was still intact. In DskProbe we can see exactly what's in sector 0, re-write it or copy from another sector to sector 0, and here's where it gets interesting. DskProbe shows the bootguard data in sector 0 (as expected) so we tried leveraging DskProbe's builtin utilities to manipulate sector 0: write zeros to sector 0 save ano
  8. Thanks for the reply. Do you have suggestions on such apps, especially ones that work in a 64-bit PE environment? I used to use mbrwiz back when we were still using Ghost in WinPE 2 & 3, and although it appears to work in WinPE 5 (no errors when executing; claims it completed successfully) it doesn't appear to be doing anything. There wouldn't happen to be a x64 fdisk executable floating around, right?
  9. As the title suggests: I'm looking for guidance on how to wipe the MBR via Task Sequence during an OSD. Any suggestions? We use Symantec Encryption Desktop (aka PGP) and it adds a bootguard to the MBR which needs to be cleared out (we need to wipe the MBR) in order for the machines to boot successfully. If I boot a Win8.1 amd64 ISO, select Repair > Advanced > Command Prompt > Run bootrec.exe /fixmbr, it works fine and corrects the issue so I thought "Why not add bootrec to our amd64 WinPE.wim?" I copied what I thought were the necessary files into our amd64 winpe.wim, based on the
  10. We're fine with backing up themes, wallpapers and other display customizations (DPI, window color & appearance etc.) because it gives us something to go back to or restore if its truly need. However, we do not want to restore the aforementioned on the destination PC by default. I must be doing something wrong and I can't figure out what and need some help. I've read some great write ups on the subject: USMT Custom XML the Free and Easy Way USMT 4.0 Custom Sample - Blocking Wallpaper and Theme Migration from Windows Vista and Windows 7 Blocking Wallpaper Migration with USMT (or: you a
  11. Correct, .NET is an app. Software updates seems to break the installation of any application. If I skip the .NET install and go to IE11 or Office 2010 it fails the same way. What updates am I installing? That's good & somewhat difficult question to answer. I imported a fresh Windows 7 SP1 Enterprise WIM, performed Schedule Updates which installed 93 successfully. I went back to Schedule updates it again, only this time it said 71 were needed. However, whether I do all 71, half or even just 2, all the updates fail with the same errors: Processing image at index 1 SMS_OFFLINE_SER
  12. After dropping the WIM on the workstation I'm running Windows Updates (a few times) and manually rebooting for good measure before moving onto application installations. When the machine comes back up & begins the Application Installation section, it fails on the first application installation which happens to be .NET 4.5.2. The error presented is a not-very-helpful 0x80004005. Selection from smsts.log I opened a bunch of other logs (see attached) and found some alarming errors like: Note: I just selected a handful of errors via cmtrace & copied so there's a bunch of
  13. Thanks for the reply simulacra75! We frequently get requests for custom builds of Windows 7 (some with Office 2007, others 2010 or 2013 or no office suite; completely locked down or with non-standard applications etc.) so I wanted to have a fully OS patched WIM I could use over & over. As the year goes on, I'd like to keep that WIM patched (OS wise) so as not to lengthen the imaging process. (They're sticklers when it comes to 'lengthy' imaging times!) From there I would create another Build & Capture Task Sequence to install our standard apps (office, flash, reader etc.), captu
  14. Crazy old post but, is anonymous access permitted on that DP? Is Anonymous Authentication Enabled in IIS for SMS_DP_SMSPKG$?
  • Create New...