We are using Microsoft System Center Configuration Manager 2007 Service Pack 2 – Operating System Deployment feature. We create task sequence to deploy Windows 7 and install software updates. In my scenario tasks sequence will install more than 60 software updates.
Deployment start and task sequence hang and stop responding when Downloading 1 of 75 Updates (0% Complete) in Install Software Updates action.
According to Microsoft Support KB2509007 This issue occurs because a deadlock occurs when the task sequence retrieves content locations for the updates.
In other scenario this issue may occur when large numbers of software updates are applied via Install Software Update action in task sequence.
To resolve this issue install hotfix from KB2509007 and follow instructions that explain how to install the KB2509007 hotfix during a ConfigMgr 2007 OSD task sequence.
In other scenario you can solve this issue by reduce number of software updates applied via Install Software Update action.
When I tried to create a stand-alone media – USB drive, the wizard fail because image size is larger than 4095 MB.
When I checked CreateTsMedia.log I found the following:
OS image has a size 7987 Mb exceeding max file size 4095 Mb
Unfortunately System Center 2012 Configuration Manager will not allow create USB stand-alone media if image size is larger than 4095 MB.
As a work around, task sequence media wizard will success when create ISO stand-alone media regardless what is the size of your image, The wizard splits the .WIM files into multiple files smaller than 4095 MB.
You can use the following steps to copy from ISO that you create to USB:
1. Open Command Prompt with administrative privalge and run diskpart tool commands:
select disk 1 (Select disk number according to list disk result, in this example Disk 0 is my HDD, and Disk 1 is USB Flash disk)
create partition primary
select partition 1
format fs=fat32 quick
2. Mount the ISO file that was created to virtual disk (I’m using MagicISO Virtual CD/DVD Manager )
3. Run xcopy command to copy all files including booting files from virtual CD/DVD to USB Flash:
xcopy f:\*.* /s /e /f g:\
F:\ = Source (Virtual Disk)
G:\ Destination (USB FLASH DISK)
You may experience issue when lunch \SMS\BIN\I386\TSMBAutorun.exe task sequence media on Windows 7 or Windows XP x86 and x64 versions, the task sequence didn’t start.
According to my test I found workaround to solve this issue, I copy TSMBAutorun.exe to the root of the USB drive and run it from there.
I configured Operating System Deployment feature in System Center 2012 Configuration Manager to deploy Windows 7 customized master image, and during deploy Task Sequence on specific collection in step to Specify how to run the content for this program I set Deployment options to Access content directly from a distribution point when needed by the running task sequence but when I checked Deployment options of a Distribution Point in the Selected Deployment Properties I found it download content from the distribution point to the destination computer as it is needed by the task sequence, the property change does not appear to have been saved.
This may occur when you have selected Make available to boot media and PXE in the Deployment Settings tab of the Selected Deployment Properties dialog box.
According to KB2713465 This problem is only an issue with the settings that are visible in the user interface. The change is actually saved correctly in the database. You can run a custom report with a SQL query to verify your settings.
The below SQL query is an example which will show all task sequences with the Access content directly from a distribution point when needed by the running task sequence deployment option selected.
SELECT pkg.PackageID, pkg.Name, pkg.SourceSite,
CASE WHEN (adv.RemoteClientFlags & 0x00000008) = 0 THEN 0 ELSE 1 END AS RunFromDPInFastNetwork,
CASE WHEN (adv.RemoteClientFlags & 0x00000080) = 0 THEN 0 ELSE 1 END AS RunFromDPInSlowNetwork
FROM v_Advertisement AS adv
INNER JOIN v_Package AS pkg ON pkg.PackageID = adv.PackageID AND pkg.PackageType = 4
WHERE (adv.RemoteClientFlags & 0x00000008) <> 0 OR (adv.RemoteClientFlags & 0x00000080) <> 0
When configure PXE Service Point in Microsoft System Center Configuration Manager 2007, booting may fail with the following errors:
PXE-T04: Access Violation
PXE-E36: Error Received from TFTP Server
PXE-M-F Exiting PXE Rom
You also may notice missing entries in the SMSPXE.log
This can occur because of wrong DHCP configuration.
You may need to configure IP helper (BOOTP) settings on the routers OR configure DHCP scope options in case you have Cisco DHCP instead of Microsoft DHCP.
To Configure DHCP Scope on Cisco Routers, add the following to DHCP Scope:
next-server ‘IP Address of PXE Service Point’