You are browsing the archive for PXE.

HOTFIX is available for the "Operating System Deployment" feature of System Center 2012 R2 Configuration Manager

7:16 am in CM12 R2, OSD, PXE, sccm 2012 R2 by Kenny Buntinx [MVP]

 

All,

KB 2905002 has been posted to the hotfix servers to address two post-R2 issues:

This update resolves the following issues in Microsoft System Center 2012 R2 Configuration Manager.

Issue 1

After you enable the PXE Service Point role

(http://msdn.microsoft.com/en-us/library/jj217832.aspx)

on an instance of a specific distribution point, or you select the Deploy this boot image from the PXE-enabled distribution point property of a boot image, the Windows Deployment Service (WDS) stops running. Additionally, entries that resemble the following are logged in the Windows Application log:

Note This problem affects only distribution points that are installed on site servers.

Issue 2

When operating system image files are downloaded to Configuration Manager 2012 R2 clients, you may find that the download takes longer than it did in previous versions of Configuration Manager 2012 clients. You may see this behavior when the target client is running Windows PE or a full Windows operating system.

 

Please see the KB for details here : http://support.microsoft.com/kb/2905002

Hope it Helps ,

Kenny Buntinx

MVP enterprise Client Management

Configuration Manager 2012: Select a Preferred Deployment when deploying via unknown computer support

1:16 pm in CM12, ConfigMgr 2012, ConfigMgr V.next, OSD, PXE, sccm, SCCM 2012, SCCM v.Next, System Center, Task Sequence, V.next, Windows 7 by Kenny Buntinx [MVP]

Hi there ,

Today a customer requested an interesting scenario about selecting a preferred deployment when deploying multiple TS to a single collection:

Scenario:

You have made a few task sequences available thru PXE boot and enabled unknown computer support . You set all your deployments to available , not required.
When you start your OSD deployment , you will see the few task sequences sitting there and waiting . This is a correct behavior.

The customer likes to see the following behavior:

– one of the task sequences made available will be started automatically after 30 seconds  if none of the other TS are selected.

This will help them to avoid the import computer information part as they stage thousands of machines over one weekend and there process is that the computer name is generated from their CMDB tool after the mac address and serial number is scanned. Then we extract that information and push it into TS variables.

Solution:

You can define a deployment in a prestart command that overrides existing deployments to the destination computer. Use the SMSTSPreferredAdvertID task sequence variable to configure the task sequence to use the specific Offer ID that defines the conditions for the deployment.

More interesting info on John Vintzels blog at http://blogs.technet.com/b/inside_osd/archive/2010/06/07/v-next-beta-1-feature-select-preferred-deployment-from-pre-execution-hook.aspx

Hope it Helps ,

Kenny Buntinx

ConfigMgr 2007 : PXE Cache Behavior

9:02 am in ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, ConfigMgr SP2, configmgr2007, ConfigMgr2007 R3, Deployment, OSD, PXE, R3, sccm, SCCM 2007, SCCM 2007 R2, SCCM 2007 R3, SCCM 2007 SP2, sccm2007 by Kenny Buntinx [MVP]

Config Mgr OS deployments when using PXE boot , you’ve probably had machines that did not want to boot the task sequence as it stated “No task sequence found, booting onto the hard drive”.

This is most likely due to a previous task sequence being advertised to that machine. By default ConfigMgr will cache the PXE advertisement for 60 minutes (Default setting) and then it will expire. Most of the time you can speed up things when restarting the WDS services. Restarting the WDS services ( clearing the cache) isn’t the best solution. In ConfigMgr SP2 the cache expiry can be set in the registry.

  • On an x86 machine the located under:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\PXE
  • On an x64 machine the registry key is under:
    HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\SMS\PXE

Create a new DWORD value CacheExpire, and set the desired value in seconds. For example, if you prefer the cache expired in 2 minutes, set the value to 120. If the value is set to 0, then the default 60 minutes value is used.

Note: Setting the value in CacheExpire is only supported in ConfigMgr 2007 SP2.

Be careful if you have R2 installed and unknown computer support enabled because if you set the cache expire value too low and you are using a mandatory task sequence your machine will continuously start the same task sequence every time it reboots.

 

Hope it Helps ,

Kenny Buntinx