Belgian Best of MMS Sessions&Recordings online

As of today you can find the full session recordings and presentations available on the Best of MMS TechNet Edge page. If you would like to go through one or more of the presentations again, please find the individual links to the slides and recordings below.  On-demand session recordings We have created a special page on TechNet Edge with all the videos of the event : Best of MMS Belgium 2011. Track 1 – Introduction to Opalis and a Sneak Peek at System Center Orchestrator by David De Backer – System Center Configuration Manager 2012 by Kim Oppalfens – Configuration Manager 2012 – Deployment and Infrastructure Technical Overview by Kenny Buntinx – AVIcode: Overview of Application Monitoring that you can do today by Chris Childers – Operations Manager 2012 : Overview, Setup and Configuration by Alexandre Verkinderen – Technical Overview of System Center Advisor (“Atlanta”) by Arne Peleman Track 2 – SCDPM : DPM 2012 : What goodies are coming? By Mike Resseler – System Center Service Manager 2012 Overview by Kurt Vanhoecke – Virtual Machine Manager 2012 : Technical Overview by Kurt Roggen – Managing your Fabric with System Center Virtual Machine Manager 2012 by Kurt Roggen – Windows Intune : PC Management with Cloud Services by Mike Resseler – Configuration Manager : Hints, Allegations and Things left unsaid by Kim Oppalfens Presentations Please find the download links towards the available presentations below : Track 1 – Introduction to Opalis and a Sneak Peek at System Center Orchestrator by David De Backer – System Center Configuration Manager 2012 by Kim Oppalfens – Configuration Manager 2012 – Deployment and Infrastructure Technical Overview by Kenny Buntinx – AVIcode: Overview of Application Monitoring that you can do today by Chris Childers – Operations Manager 2012 : Overview, Setup and Configuration by Alexandre Verkinderen – Technical Overview of System Center Advisor (“Atlanta”) by Arne Peleman Track 2 – SCDPM : DPM 2012 : What goodies are coming? By Mike Resseler – System Center Service Manager 2012 Overview by Kurt Vanhoecke – Virtual Machine Manager 2012 : Technical Overview by Kurt Roggen – Managing your Fabric with System Center Virtual Machine Manager 2012 by Kurt Roggen – Windows Intune : PC Management with Cloud Services by Mike Resseler – Configuration Manager 2012 : Hints, Allegations and Things left unsaid by Kim Oppalfens This event was sponsored by :

Configuration Manager 2007 SP2, R2 and R3 supports Windows 7 SP1 and Windows Server 2008 R2 SP1

Read the original post here.

---

System Center Configuration Manager 2007 SP2, R2 and R3 now supports the Windows 7 SP1 and Windows Server 2008 R2 SP1 operating systems for client installation.  The Configuration Manager console and branch distribution point are supported on these platforms. Windows Server 2008 R2 SP1 is supported for all core and feature-specific site system roles.

The following software update is required to add Windows 7 SP1 and Windows Server 2008 R2 SP1 to the Supported Platforms list:

• KB 2489044 – Update for System Center Configuration Manager 2007 SP2 to add Windows Server 2008 R2 SP1 and Windows 7 SP1 clients as supported platforms
• KB 977203 – User state migration is unsuccessful on a SCCM 2007 SP1 client or on a SCCM 2007 SP2 client

Configuration Manager 2007  SP2, R2 and R3 supports WinPE 3.1

System Center Configuration Manager SP2, R2 and R3 now supports WinPE 3.1 as the boot image used with operating system deployment. WinPE 3.1 is shipped with Windows 7 SP1 as a Windows Automated Installation Kit (WAIK) supplement.

Steps to upgrade to WinPE 3.1 within the existing Configuration Manager Environment and known limitations with Win PE 3.1 can be found here

An error Occurred while retrieving policy for this computer (0x80072EE7)

 

Today I stumbled against following problem after trying to perform an OSD.

The network drivers in the Boot environment were ok.

But I was not able to resolve the server from within the Boot image.

So I fixed DNS resolving by adding the correct entries to DNS.

When I was able to resolve the configuration manager server, the task sequence went ok.

Hope it Helps.

Kind Regards,

Arne Peleman

Ferranti Computer Systems–Seminar

Ferranti Computer Systems will hold a seminar ‘”Upgrade your IT Service”.

Mostly aimed at potential Benelux-customers.

This seminar will focus on the System Center stack, but will also touch Forefront Endpoint Protection and Hyper-V.

I will be talking about 3 subjects.

• Upgrading to Windows 7 / Office 2010 using System Center Configuration manager 2007
• Co-presenting the SCOM-Opalis solution.
• Offer a preview about System center Configuration manager 2012 and user centric management.

Here’s a short summary about who and what to expect:

Jan Van Meirvenne will be talking about monitoring with system center operations manager in combination with auto remediation by Opalis.
Valerie Siroux will give a tour about DPM and how it can interact with Opalis to create a self-sustained backup solution.
Frederik Baert will provide a session about Service Manager and how you automate your incident management.
Stijn Verhoeven will present the Hyper-V platform and why you should consider virtualization.
Chris Millian will be available to answer your questions about System Center, and if necessary provide a short demo.

Full Program Description

If you’re interested, don’t hesitate to signup!

Kind regards,

Arne

A Configuration Manager 2007 PXE Service Point causes the Windows Deployment Services Server service to crash and hang

 

Following KB Article has been released today as a FAST PUBLISH article.

http://support.microsoft.com/default.aspx?scid=kb;EN-US;2510665

 

Symptoms

When attempting PXE boots via a System Center Configuration Manager 2007 PXE Service Point, PXE boots will initially work and succeed but then all of a sudden stop working. Examining the server where the PXE Service Point and Windows Deployment Services (WDS) are installed reveals that the Windows Deployment Services Server service has crashed and is in a hung state. Attempting to restart the Windows Deployment Services Server service on the WDS server does not resolve the issue. Restarting both the Windows Management Instrumentation and the Windows Deployment Services Server services or restarting the server may temporarily resolve the problem, but the issue will eventually reoccur and WDS will eventually crash again.

Trying to reproduce the issue by continually attempting to PXE boot PCs reveals that although the issue may happen frequently, the issue cannot be reproduced on a consistent basis and that the crashes will happen randomly.

Examining the WDS server where the ConfigMgr 2007 PXE Service Point is installed reveals the following errors in Event Viewer:

System Event Log:
<Date> <Time> Error <WDS_Server> Service Control Manager N/A N/A The Windows Deployment Services Server service terminated unexpectedly. It has done this <x> time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service.

Application Event Log:
<Date> <Time> Information <WDS_Server> WDSServer WDSServer N/A Provider WdsImgSrv was shutdown successfully.
<Date> <Time> Warning <WDS_Server> WDSServer WDSServer N/A An error occurred while trying to initialize provider WdsImgSrv from C:\Windows\system32\WdsImgSrv.dll. Since this provider is not marked as critical, Windows Deployment Services server will continue. Error Information: 0xC1030136
<Date> <Time> Error <WDS_Server> WDSIMGSRV WdsImgSrv N/A An error occurred while trying to initialize the Windows Deployment Services image server. Error Information: 0xC1030136

<Date> <Time> Error <WDS_Server> Application Error {100} N/A Faulting application svchost.exe_WDSServer, version 6 <version>, time stamp <hex_time_stamp>, faulting module ntdll.dll, version <version>, time stamp <hex_time_stamp>, exception code 0xc0000374, fault offset 0x000afaf8, process id <hex_process_id>, application start time <hex_time>

The following error may also be seen:

The Windows Deployment Services (WDS) Server service terminated with service-specific error 16389 (0x4005).

 

Cause

This issue can occur in environments where there are redundant backup routers in place. If IP Helpers for PXE (DHCP relays) are placed on both the primary and backup routers, this may cause a situation where two duplicate PXE request packets are sent to WDS: The original PXE request by the primary router and a duplicate PXE request by the backup redundant router. If the timing is just right, the duplicate second PXE request may overwrite some of the information in WDS from the first original PXE request. This will cause information in WDS for the PXE request to become corrupted and will cause WDS to crash.

 

Workarounds

There are two workarounds to this issue:

1. Disable the PXE IP Helpers in the backup redundant router so that duplicate PXE requests are not sent. For more information on PXE IP Helpers, please see the below TechNet article:
   Configuring Your Router to Forward Broadcasts
   http://technet.microsoft.com/en-us/library/cc732351(WS.10).aspx#Updating
2. Set the ConfigMgr 2007 WDS provider to be single threaded instead of multi-threaded. This will cause only one PXE request to be processed at a time by WDS and will prevent the second duplicate PXE request from conflicting with the first original PXE request. To set the ConfigMgr 2007 WDS provider to be single threaded, create the registry key NumberOfThreads with a DWORD value of 1 in the following location:
   32bit WDS server
   HKLM\Software\Microsoft\SMS\PXE
   
   64bit WDS server
   HKLM\Software\Wow6432Node\Microsoft\SMS\PXE
   This normally should not have a performance impact on the server for PXE requests except in environments where there is a large amount of PXE requests being performed on a constant basis. In environments such as this, it is recommended to use the first workaround.