Showing posts with label Task Sequence. Show all posts
Showing posts with label Task Sequence. 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

Tuesday, January 8, 2013

Service Pack 1 for MS ConfigMgr 2012 Resets the SUP Port to 80

When you apply Service Pack 1 to Microsoft System Center Configuration Manager (ConfigMgr) 2012, ConfigMgr improperly resets the port value in the software update point (SUP) configuration options to port 80. This breaks the update publishing functionality in ConfigMgr if the SUP server was previously configured to use an alternative port. For example, if the SUP is a WSUS v6 server (included with Windows Server 2012) using the default WSUS configuration, the port needs to be 8530.

How to resolve this issue-

You will have to follow following steps:-

  1. In the left pane of the ConfigMgr 2012 console, click the Administration heading.
  2. In the center pane on the Administration page, select the SUP server in the top pane.
  3. In the Site System Rules pane (center-bottom), select Software update point.
  4. In the ribbon, click Properties.
  5. In the Software update point Properties window, configure the Port Numberand SSL Port Number as appropriate.
  6. Click Ok

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.

Tuesday, October 25, 2011

The computer associations are not created by the import computer information wizard in SCCM 2007 Service pack 2

If you are deploying operating system to unknown computer and you are facing a problem and getting some error----

1-No action found for boot device,

means your system is not getting PXE and you WDS service is not running on server, though you have configured all task sequence.
just restart WDS services and reconfigure your PXE,


2-The computer associations are not created by the import computer information wizard in SCCM 2007 Service pack 2

You click the following item in the Configuration Manager console:
Computer Management\Operating System Deployment\Computer Association

-->You run the Import Computer information Wizard to import new computer information.
In this scenario, the computer associations are not created when the new computer information is imported. Therefore, there is no new node in the computer association list.

that mean you server is not updated with
the kb989270 patch, so you must have to install hotfix for more information see http://support.microsoft.com/kb/980270 which should fix the problems with objects in the collections



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 ...