Jump to content


morpheus9394

Established Members
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About morpheus9394

  • Rank
    Newbie
  1. Thanks for that Thadkew. Unfortunately our SCCM, Imaging, Packing and Testing department, aka Me, does not have the time or resources to play and learn a new toy just yet. MDT does look very a very useful took. I will definitely look into it at a later date.
  2. Thanks for the replies and advice. It seems leaving mcafee for the image (for now) did the trick. I was able to build, connect to domain, install software and updates and then sysprep and capture the new image. More testing needed but it seems Mcafee may need to be added to the image last if at all. Not a big deal. Thanks again.
  3. Thanks for the advice. I will try as you suggested. Is it safe to connect to the internet and download all windows updates prior to sysprep, capture and deploy? Is Mcafee the only software you recommended to install before connecting to the domain?
  4. Hi All, I wrongly assumed that creating a windows 10 image and capturing it using SCCM 2102 would be the same as it is with Windows 7. But after a week of banging my head against the wall I am no closer. First Attempt: Installed Windows 10 from USB using latest version downloaded from MS. Connected to Internet, installed all Windows updates Connected to Domain and installed McAfee and a small selection of applications (Adobe Reader, Flash etc) Removed from Domain and ran capture from the SCCM 2012 capture USB I created Capture failed due to "Modern App" twitter Tried several fixes involving powershell but no luck 2nd Attempt: Installed Windows 10 from USB using latest version downloaded from MS. Connected to Internet, installed all Windows updates Removed Modern apps for all users via powershell Captured via SCCM 2012, which worked. Deployed the captured image and that worked fine Using that captured image as a base - Installed McAfee, a base selection of applications as before Captured successfully but on reboot (on captured PC or a new machine built with the deployed image) I got "Windows could not finish configuring the system. To attempt resume configuration, restart the computer" error message Managed to get the machine to boot after much registry playing and removed McAfee as and captured again Got the same "Windows could not finish configuring the system. To attempt resume configuration, restart the computer" error message on reboot Very confused!!! Our build process is very simple but trying to get Windows 10 to work with this process is causing us no end of trouble: 1 - Install OS 2 - Get latest updates 3 - Add to domain 4 - Install McAfee AV software followed by a small selection of applications 5 - Remove from Domain 6 - Capture image as WIM using SCCM 2012 capture USB. 7 - Add image to SCCM, created task sequence and deploy The only ways I've found to get it working is by doing a in place upgrade of an existing Windows 7 build and capturing that. Unfortunately doing a in place upgrade to Windows 10 seems to cause other issues so we wanted to create a new clean image to then roll out. The other way we managed to get it working was by stripping out modern apps before capturing but that then causes issues with the start menu/taskbar and search when in Windows 10. We now have group polices in place to disabled Modern apps and Cortana so there is not need to strip out the modern apps from the build. I'm obviously missing something but after spending nearly two weeks playing, building, Googling....I am no closer to fixing this issue. Any advice would be appreciated. Sorry for the long post.
  5. Hi All, Once a quarter we create a new Win7 build and capture the image WIM. We rename the original WIM from Win7.wim to something like Win7_olddate.wim and the new image will be called Win7.WIM. We then use the following steps to get the new OS content on SCCM: In administration\Distribution Points we removed the content from the site server and from our two DPs Wait for the logs to show the content has been removed In software library\Operating System Images we find the Image, go to properties, images and then reload. This updates the image properties with the newly update WIM image. Finally we distribute the content to the site server and to the DP. Everything seems to work and the logs shows no errors but when we then build a machine it is using the previous version of the image. The only way that seems to work 100% is for us to delete the operation system image under software packages and then add it again. This updates the image ID and then when we distribute the content and build the new image gets applied. I'm wondering why we are going wrong. We used to follow the same process on SCCM 2007 and it worked fine but in 2012 it doesn't seem to like our process. Any tips or advised would be appreciated. Thanks.
×
×
  • Create New...