Using Offline Servicing and Windows 7

By -
Over then next few weeks my company will be rolling out a large number of PC so I am going though the images that we will be using for this process to be sure they are all up to date. While Using Offline Servicing I notices in the log file that not all of the update where being applied. In the long run this isn't really a big issue but it dose make the role out processor more proficient if all the updates I can get are in the image file. So after a little research I came access this post. In the post the author talks about how there is a check on some updates that looks to see if the image the updates are being applied to is Online or Offline, Online meaning an actual running OS and Offline meaning a mounted image file. Since we are using Offline Servicing the image reports back as Offline. Th author then explains how to fix this and it is quite simple.





1. Create a folder where you keep your image files called Mount

2. Run the following command 

dism /mount-wim /wimfile:<PathToWimFile> /index:1 /mountdir:<PathToWimFile>\mount

3. Open Regedit as an administrator

4. Click File and choose Load Hive


5. Navigate to where you mounted the wim file, Then find Widnows\System32\config and load the SOFTWARE hive and name it SoftwareWim.

6.  Take ownership of  HKLM\SoftwareWim\Microsoft\Windows\CurrentVersion\Compnent Based Servicing\SessionsPending

7.  Edit the DWORD Exclusives value and set it to 0

8. Unload the hive by going to file Unload Hive

9. Dismount the wim file and save your changes by running the following command

dism /unmount-wim /mountdir:<PathToWimFile>\mount /commit

10. Delete the Mount folder and try to apply your updates again

Popular posts from this blog

SCCM Task Sequence GUI - How to set up the TS to work with a GUI

By -
Image
Before I have posted how you can create a TS for windows 10 , add a GUI to your TS and run a script to configure your windows 10 install . However all of this has become out dated and so I wanted to update all of that. This how to will walk you through how to create a TS that will allow you to choose a windows 10 or windows 7 image, name the computer, add the computer description to AD, Choose form a list what applications you want to install, Choose to enable BitLocker and set the PIN as well as create a local account. Prerequisites: MDT integrated to SCCM A boot image with the following components added Windows Powershell(WinPE-DismCmdlest) HTML(WinPE-HTA) Microsoft .NET (WinPE-NetFx) Windows Powershell (WinPE-Powershell) A windows 10 and windows 7 image  1. Download the package I have put together containing the scripts you will need https://github.com/sccmtst/SCCM-Management-Scripts/tree/master/TSGUI 2. If you have not already done so download and in...
Read more

SCCM Applications vs. SCCM Packages: Understanding the Key Differences

By -
Microsoft System Center Configuration Manager (SCCM) is a versatile and powerful tool for managing devices, applications, and updates in an organization's IT environment. Among its many features, SCCM allows you to deploy software to your end-users in two primary ways: Applications and Packages. Although both methods have a similar goal, they have some key differences that IT administrators should understand when choosing the appropriate deployment method. In this blog post, we will explore these differences and help you decide which option is best for your organization. Definition and Deployment Scenarios SCCM Applications: An SCCM Application is a high-level, user-centric deployment method that focuses on providing the desired user experience. Applications are designed to be state-based, meaning they can detect if the application is already installed and only perform the necessary actions if the application is not present or if a newer version is available. Applications are suita...
Read more

Faster PXE boot times in SCCM 1606 and later

By -
Image
A new feature introduced with SCCM 1606 was being able to modify the boot times for PXE. This is done by modifying the TFTP block and window size of the boot image RamDisk. This was originally implemented to help a admin over come network requirement. This allows us to make the PXE boot times much faster for my self this meant taking a 10 minute boot time all the way down to 30 second boot time. In order to make this change you need to create 2 registry keys on your PXE enabled DP. Location : HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\DP Name: RamDiskTFTPWindowSize Type : REG_DWORD Value : <customized window size> The default value is 1 (1 data block fills the window)  Location : HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\DP Name: RamDiskTFTPBlockSize Type : REG_DWORD Value : <customized block size> The default value is 4096 (4k).  once you have added the registry keys you will need to restart  the Windows Deployment Service for the ch...
Read more