Jump to content


allenr74

Established Members
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

0 Neutral

About allenr74

  • Rank
    Newbie

Profile Information

  • Gender
    Male
  1. Is it safe to import drivers for a newly acquired model while an osd task sequence might be running? I say might be running because our company is a global one and imaging of machines can be going on without my knowledge. Should I wait for our change management window to import new drivers for use in the OSD or is it safe to do so during business hours?
  2. Hello, Is there a way to deploy Skype for Business Basic (O365 Click-to-Run) during an Operating System Deployment task sequence? I'm able to deploy O365 Pro Plus with OSD. But if I include Skype in the configuration xml file, the application will not install. I broke Skype out into its own package with its own configuration xml and it still won't install during OSD. Can anyone provide some pointers on how to get this done, please?
  3. I deployed windows 10 ent 1607 to a VM to start creating a reference image. I'm using MDT 2013 Update 2 (8443) as well as ADK 1607. While the deployment succeeded, there was one error regarding IE 11 X86. it is: Error - Internet-Explorer-x86 role processing with DISM.exe failed, rc = -2146498548 I couldn't find much doing a search. Has anyone seen this before?
  4. While I've been working with SCCM for over 6 years I have what's probably a "newbie" question. Is it ok to import drivers while current task sequences are running that deploy operating systems to clients? I won't be editing the task sequences just importing new model drivers (we do use auto apply). When I first started doing os deployments I made the mistake of editing a task sequence that was probably being used and it got corrupted. I don't want that to happen again thus my question now. In the past I've always been careful to import drivers only during change management windows and after I announced to our IT department that imaging was not to take place for a certain amount of time. Is this necessary?
  5. Is it safe to import drivers into SCCM during production hours? We're getting new models in this week and I've always imported drivers on the weekend after business hours for fear of corrupting current production task sequences. Am I correct in importing and creating driver packages only after business hours?
  6. I discovered the resolution to this issue after consulting with MS on a related issue. After upgrading 3 primary site servers to Server 2012 R2, client registration was failing. I found the the inbox share lost requisite permissions on one site server. Once I found that out and reapplied the permissions, the client communications resumed in one site. In another site that was having client registration issues, I discovered that the distribution points (site systems too) were removed from the local admin group on 2 out of 3 of my primary site servers. I discovered this after viewing the mpfdm.log on the distribution points (which are also management points). The errors stated that the source inbox could not be contacted and thus outbox monitoring was skipped. After adding the site systems back to the local admin groups on the 2 site servers, client registration resumed. Adding the site systems back to the local admin groups of the primary site servers also re-established the presence of the pxe advertisement on the sccm machine objects.
  7. We are running CB 1606. We upgraded our test environment over 1 month ago to Server 2012 R2. I upgraded our CAS server to Server 2012 R2 last week and just finished upgrading 2 of our 3 Primary Site Servers. I tested imaging last week at a site and it is fine. Imaging at the 2 sites I upgraded today is good except for a strange issue. I'm using VMWare clients and PXE booting. When I right-click in the console to clear the PXE advertisement, I get the message stating that there is no advertisement or it was cleared already (it wasn't). The client is recorded in the logs and the imaging process goes along fine. Has anyone seen anything like this? The PXE advertisement is not retained on the SCCM Machine object so that ABORTPXE will not display?
  8. I just recently updated our production SCCM environment to SCCM 2012 R2 SP1, CU1. I updated MDT 2013 to Update 1 (8298) and installed the integration on my central site server. I am now having issues deploying Windows 10 to a VMware VM. After it applies drivers and boots into the operating system for the first time, I receive a pop-up message with the following: "Windows could not finish configuring the system. To attempt to resume configuration, restart the computer". Restarting the computer just brings back the same message. This is only happening with MDT integrated task sequences. I created a task sequence without MDT integration and the deployment finishes fine. I created another MDT task sequence for SCCM and it is still failing at the same point. Unfortunately, I cannot get to a CMD line when the error pops up. I try SHIFT+F10 but that doesn't work. I enabled F8 for the boot image but it is past the PE environment. I did get the logs before the OS restart and they all look fine. I updated our lab environment back in August (pre MDT 2013 Update 1 re-release) and didn't run into this issue. Any help would be greatly appreciated.
  9. I had the same issue last year. Lenovo suggested disabling USB 3.0 in the bios. That did the trick.
×
×
  • Create New...