Showing posts with label OSD. Show all posts
Showing posts with label OSD. Show all posts

Wednesday, December 31, 2014

OS deployment fails (Failed to download policy )


Recently I have faced an issue with OS deployment. While OSD I got an error

While checking the smsts.log file I found the error in log file that was showing

BOM not found on policy reply

Failed to download policy {172A41CC-19A7-4BE3-91BC-0D979432CA10}/9 (Code 0x80004005).
 
 
 
I checked multiple things but nothing has worked.  Checked the package versions, scope IDs in application but everything was fine.
After that I searched the Policy in the SCCM database in table policyassignment and Policy
select * from policyassignment where policyid = '{172A41CC-19A7-4BE3-91BC-0D979432CA10}/9'
select * from policy where policyid = '{172A41CC-19A7-4BE3-91BC-0D979432CA10}/9'
 
after that I have deleted the policy which was showing as error in smsts.log file.
Delete from policyassignment where policyid = '{172A41CC-19A7-4BE3-91BC-0D979432CA10}/9'

Friday, January 3, 2014

Improve the performance of PXE boot


To improve the PXE boot we have to enable/add a registry value in DP where PXE is enabled,

From the distribution point (where you enabled PXE) complete the following

1.        Open regedit and locate HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\DP

2.        Add a QWORD value and call it RamDiskTFTPBlockSize

3.        Give it a Hexadecimal value of “4000″

Saturday, April 13, 2013

Deploy Windows 8 Enterprise x86 on a UEFI x86 device using SCCM 2012 SP1

New Toys For The Boys
Don’t we all love new toys, especially the ones that require an occasional recharge.

The latest thing I got my hands on is the Lenovo Tablet 2, a very nice 10” tablet thing, with a couple of nice add-ons, like a docking station, Bluetooth keyboard and a pen like stylus. But what I really like about it is that it runs a full version of Windows 8 x86, which means that I can deploy its OS over and over again

So I fired up my SCCM Console to do exactly that …

The Drivers
First off I needed a driver package and Lenovo has been kind enough to supply a ready-made kit for SCCM.

Which can be downloaded from this URL http://support.lenovo.com/en_US/downloads/detail.page?DocID=DS033326

After unpacking the kit, I imported the driver package without any issues





Reading through the readme file for the Lenovo driver kit, I found out that a few extra steps would be required to completely support the Tablet 2 device. The Mobile WAN device need a software package to be installed, and KB2761094 must be installed to remove two “yellow marks” in the device manager. So I added a package for each of these issues.

Mobile WAN device Package
I downloaded the driver for the Ericsson WAN device and got a Lenovo installer and a setup.exe (the only thing actually needed)

I created a package co

full article on
http://blog.coretech.dk/rja/deploy-windows-8-enterprise-x86-on-a-uefi-x86-device-using-sccm-2012-sp1

Friday, January 25, 2013

System Center 2012 SP1 is Generally Available, but contains a lot of bugs. Here's a list of ConfigMgr issues known

We have obseved, after installaing CM12 SP1, we have known lots of error and issues,

I am giving all those errors/bugs and those resolutions..

1-Active Replica Error after the SP1 upgrade for ConfigMgr 2012
2-Server 2012 OSD Issues in ConfigMgr 2012 SP1
3-System Center 2012 Configuration Manager Application Catalog does not refresh on F5 in Windows 8 or Windows Internet Explorer 10
4-ConfigMgr 2012 SP1 client installation error with MicrosoftPolicyPlatformSetup.msi -    Hotfix Available!
5-Changes to built-in collections are overwritten when you upgrade to System Center 2012 Configuration Manager SP1 http://support.microsoft.com/kb/2739984
6-Antimalware Policies issue, a workaround, and a forgotten Beta message with ConfigMgr 2012 SP1 http://myitforum.com/myitforumwp/2013/01/09/antimalware-policies-issue-a-workaround-and-a-forgotten-beta-message-with-configmgr-2012-sp1/
7-Service Pack 1 for MS ConfigMgr 2012 Resets the SUP Port to 80 and Why does WSUS not sync anymore in ConfigMgr 2012 SP1? http://myitforum.com/myitforumwp/2013/01/08/service-pack-1-for-ms-configmgr-2012-resets-the-sup-port-to-80/
8-Application Catalog link breaks if you change the regional settings decimal separator in Software Center in System Center 2012 Configuration Manager http://support.microsoft.com/kb/2801822
10-The 8dot3name settings are disabled on the volumes upon partitioning and formatting of the local disk http://scug.be/sccm/2013/01/15/configmgr-2012-sp1-the-8dot3name-settings-are-disabled-on-the-volumes-upon-partitioning-and-formatting-of-the-local-disk/
11-Antivirus can cause corruption and/or incomplete installations
12-Missing PCM icon even after a successful installation - Workaround available
13-Application evaluation fails in System Center 2012 Configuration Manager running on Windows XP http://support.microsoft.com/kb/2798545
14-Unhandled exception when launching the System Center 2012 Configuration Manager SP1 Console (Microsoft.ConfigurationManagement.exe) http://support.microsoft.com/kb/2800707
17-Virtual Application Fails to Install with Event ID 1008 in the Windows Applications and Services Logs  
18-A Migrated Configuration Manager 2007 Configuration Baseline Fails to Evaluate on Client Computers
19-Error Microsoft.Reporting.WinForms.ReportServerException when you run the Roaming User Profiles Health Report http://myitforum.com/myitforumwp/docs/system-center-2012-sp1-woes-gotchas-and-workarounds/

Wednesday, November 23, 2011

Task Sequence Error 80070070 while deploying OSD

If you are getting Task sequence error 80070070



while deploying OS or capturing image, then that's mean there is no enough space in source directory to install OS, and also same thins there is no space in destination directory where you are storing Captured image.

so for avoid this error you have to provide enough space for Deploying OS and for source file where you are storing WIM Image.

PXE Issue after SCCM CB 1806 upgrade

Recently i had upgraded my SCCM environment 1806 and after upgrade suddenly all PXE servers stopped working. While initiating the PXE ...