Open Beta for Microsoft System Center Service Manager 2010 IPD Guide—Now Available for Download!


The Infrastructure Planning and Design team is working on a new guide: Microsoft System Center Service Manager 2010. Get the beta by visiting the Connect
website at

This IPD guide takes the IT architect through an easy-to-follow process for successfully designing the servers and components for a System Center Service
Manager implementation, resulting in a design that is sized, configured, and appropriately placed to deliver the stated business benefits, while also considering the performance, capacity, and fault tolerance of the system.

The guide covers these key steps in the System Center Service Manager infrastructure design process:

  • Defining the project scope by identifying the necessary System Center Service Manager features, the requirements of the process management packs, and the
    targeted population of the organization.
  • Mapping the selected features and scope to determine the required server roles.
  • Designing the fault tolerance, configuration, and placement of the management servers, portals, and supporting SQL Server databases.

The IPD Guide for System Center Service Manager 2010 can help you reduce planning time and costs, and ensure a successful rollout of System Center
Service Manager—helping your organization to more quickly benefit from this platform for automating and adapting IT Service Management best practices such
as those found in Microsoft Operations Framework (MOF) and the IT Infrastructure Library (ITIL).


Tell us what you think!
Download the beta guide and please provide us with the following:

1. Your honest feedback. No matter what it is or how you phrase it, we can handle it.

2. Your edits and comments in the doc. Please open the doc, add comments, and use track changes to show us what changes you would make.

3. A marked-up doc sent to us by email at by November 9, 2010.


Benefits for participation:

  • You get an early look at the guide.
  • You will be listed on the acknowledgments page for providing useable feedback.

We appreciate your input and will work to make each guide as helpful and useful as possible. Infrastructure Planning and Design streamlines the planning process by:

  • Defining the technical decision flow through the planning process.
  • Listing the decisions to be made and the commonly available options and considerations.
  • Relating the decisions and options to the business in terms of cost, complexity, and other characteristics.
  • Framing decisions in terms of additional questions to the business to ensure a comprehensive alignment with the appropriate business landscape.


Tell your peers about IPD guides!

Please forward this mail to anyone who wants to learn more about Infrastructure Planning and Design guides.

Join the Beta Program

Subscribe to the IPD beta program and we will notify you when new beta guides become available for your review and feedback. These are open beta downloads. If you are not already a member of the IPD Beta Program and would like to join, follow these steps:

1. Go here to join the IPD beta program:

If the link does not work for you, copy and paste it into the Web browser address bar.

2. Sign in using a valid Windows Live ID.

3. Enter your registration information.

4. Continue to the IPD program beta page, scroll down to Infrastructure Planning and Design, and click the link to join the IPD beta program.

Already a member of the IPD beta program? Go here to get the latest IPD beta downloads:

Related Resources

Check out all the Infrastructure Planning and Design team has to offer! Visit the IPD page on TechNet,, for additional information,
including our most recent guides.





SMS WSUS Synchronization failed – SCCM Software Update Point

Using SCCM Software Update Point in combination with a proxy server can lead to WSUS synchronization problems. Synchronization
problems can be identified by the following status messages


SMS WSUS Synchronization failed.
Message: Failed to sync some of the updates.
Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction.SyncUpdates

and by wsyncmgr.log:

Failed to sync update e5077be1-da82-4c15-82d1-e4e8ff0a1264. Error: License agreement not ready. This is a transient state while WSUS is downloading the agreement. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction.ProcessEulas

You may experience this problem if a computer is behind a firewall or behind a proxy server. This problem occurs if one of the following conditions is true:

  • The proxy server environment does not support the HTTP 1.1 range request
  • You are behind a SonicWALL firewall device, and the Enable HTTP Byte-Range request with Gateway AV setting is
    not enabled for the device.

When you copy a file by using BITS in background mode, the file is copied in multiple small parts. To perform this kind of copy operation, BITS uses the HTTP 1.1 Content-Range header. If you are behind a proxy server or behind a firewall that removes this header, the file copy operation is unsuccessful.

Note When BITS copies files in foreground mode, BITS does not use this header.

You may experience this problem if a computer is behind a firewall or behind a proxy server. This problem occurs if one of the following conditions is true:

  • The proxy server environment does not support the HTTP 1.1 range request
  • You are behind a SonicWALL firewall device, and the Enable HTTP Byte-Range request with Gateway AV setting is
    not enabled for the device.

When you copy a file by using BITS in background mode, the file is copied in multiple small parts. To perform this kind of copy operation, BITS uses the HTTP 1.1 Content-Range header. If you are behind a proxy server or behind a firewall that removes this header, the file copy operation is unsuccessful.

Note When BITS copies files in foreground mode, BITS does not use this header.

If you are using WSUS 3.0 with a Windows Internal Database that was created by a default WSUS installation, type the following command:

%programfiles%\Update Services\Setup\ExecuteSQL.exe -S %Computername%\MICROSOFT##SSEE -d “SUSDB” -Q “update tbConfigurationC set BitsDownloadPriorityForeground=1”

If you configured WSUS 3.0 to use an existing installation of SQL Server, type the following command:

%programfiles%\Update Services\Setup\ExecuteSQL.exe -S %Computername% -d “SUSDB” -Q “update tbConfigurationC set BitsDownloadPriorityForeground=1”
Restart the Update Services service and reset wsus by : wsusutil.exe reset
I’m running up against this problem with a McAfee Web Gateway 6.8.7 Build 8378

System Center Configuration Manager 2007 R3 RTM!

Today we are pleased to announce the release and availability of System Center Configuration Manager 2007 R3!  Organizations of all sizes use System Center Configuration Manager for better insight and control of their servers, PCs and devices across physical, virtual and distributed environments.  Now, R3 brings a complete set of power management tools for more Green IT, mobile device management capabilities, as well as other enhancements.

Below is a quick summary of what’s new with R3.  Go here to download the evaluation software – it will be available at around 2 p.m. Pacific time.

Centralized Power Management

Configuration Manager R3 lets IT organizations centrally manage the power settings of Windows 7, Vista and XP computers, helping reduce energy consumption and costs.  You can plan and apply a power management policy for high and low PC usage periods, monitor user activity to avoid any productivity interruptions and correct non-compliance.  Detailed reports of trends and settings help you make smart power management choices, and also validate Green IT projects with summaries of power, money and CO2 savings.  Learn more here.

Mobile Device Management

Configuration Manager R3 includes licenses for the popular System Center Mobile Device Manager, so you can run comprehensive asset inventories, deploy software, manage settings and enforce password policies for Widows phones.

Enhanced Scalability and Performance

Configuration Manager R3 is more scalable than ever, increasing the number of supported clients to 300,000 per site.  R3 is also more efficient in the way it communicates with Active Directory, helping you discover user or machine changes more quickly and allowing custom queries to define user, system or group attributes.

Finally, it is worth noting that, just like Configuration Manager R2, R3 will be the foundation for the upcoming Forefront Endpoint Protection 2010.  By bringingendpoint security into overall endpoint management, you can reduce costs and inefficiencies, and also improve security and compliance.

Configuration Manager 2007 R3 –  Power management mission and design philosophy

We encourage you to take a close look at Configuration Manager R3 today!


System Center Experts Live….

Experts Live is het kennis evenement rondom Microsoft Infra & Security, Unified Communication, Virtualisatie en Management met System Center. Op 4 november organiseren we een ‘Special’ met sprekers van diverse productgroepen van Microsoft uit de USA en specialisten met o.a. een Microsoft MVP status. In de breakout sessies worden o.a. System Center Service Manager, System Center Configuration, Hyper-V en Private Cloud mogelijkheden hands-on gedemonstreerd.

Dit event biedt je de unieke mogelijkheid om direct met de diverse product groepen in contact te komen. Met ondermeer Wally Mead en Travis Wright beschikt dit event over een zeer sterke System Center cast! ‘Prettige’ bijkomstigheid…geen Berlijn, Las Vegas of Barcelona…nee gewoon in Nederland ;-)

MMS 2011 Registration is Open!

Microsoft Management Summit (MMS) 2011 will empower you with the insight, solutions and networking opportunities to succeed in your job today while preparing for the future. MMS is the premier event of the year for deep technical information and training on the latest IT management solutions from Microsoft, Partners, and Industry Experts. Reserve your place at Microsoft Management Summit 2011: Register Today!

Managing Site Boundaries bulk actions SCCM

SiteBound is a tool that allows bulk addition of boundaries to Configuration Manager sites. Adding boundaries through the ConfigMgr console can be tedious if adding more than a handful. Previously for SMS 2003 there was the Siteboun.exe tool which solved this problem, however, to my knowledge ConfigMgr 2007 Toolkit v2 lacks siteboun.exe.

This tool is not as full featured as the Siteboun tool for SMS 2003. It will only add new boundaries to a ConfigMgr site.

SiteBound.exe /s {central site server} /file {excel file} /log {path}

/s Central Site Server name.
/file Path to Excel files.
/log Log file path.

The input for this tool is an Excel 2003 spreadsheet and there are some requirements for the format of this spreadsheet. Review the example spreadsheet, sbexample.xls, attached. Any deviation from this will either produce errors or unexpected resutls.
All output from this tool is written to the log file only. (The Trace utility from the ConfigMgr toolkit can be used to view the log)

The input uses the following syntax:

Boundary SiteCode Description Connection C01 Example IP Range Boundary Fast C02 Example IP Subnet Boundary Slow
Default-First-Site-Name C01 Example AD Site Boundary Fast

Sitebound can be downloaded here.
SMS 2003 Toolkit 2 can be downloaded here.
SCCM 2007 Toolkit v2 can be downloaded here.

I am also curious if vNext with a new toolkit will be released including this feature or that is native in vNext.

Creating SMS/SCCM addresses with VB scripting

Wondering how creating SMS/SCCM addresses with VB script ? There are many resources available like SCCM SDK and other VB and PowerShell scripting against SMS/SCCM but not always that clear.

Migrating 150 sites…some automatization would be nice :-) By using VB scripting we will be enabled to fully migrate 150 SMS 2003 sites to SCCM 2007. Including site boundaries, site system roles , properties and addresses. In this post I’d like to share some part of the migration proces,  how to configure addresses with VB scripting.

The SMS_SCI_Address Windows Management Instrumentation (WMI) class is an SMS Provider server class, in Configuration Manager, that represents a sender address, which is a link between the site for which the site control file exists and another site.

The following syntax is simplified from Managed Object Format (MOF) code and includes all inherited properties.

Class SMS_SCI_Address : SMS_SiteControlItem
     String AddressType;
     String DesSiteCode;
     UInt32 FileType;
     String ItemName;
     String ItemType;
     UInt32 Order;
     SMS_EmbeddedPropertyList PropLists[];
     SMS_EmbeddedProperty Props[];
     UInt32 RateLimitingSchedule[24];
     String SiteCode;
     Boolean UnlimitedRateForAll;
     SMS_SiteControlDaySchedule UsageSchedule[7];

Schedule and Rate Limits tab of the Addresses the following will be configured by the SMS_SiteControlDaySchedule WMI class.

The following snapshot of the code sample shows you how to configure the Schedule an Rate Limits of addresses:

Set WbemInst = WbemServices.Get("SMS_SCI_Address").SpawnInstance_()
if (err <> 0) then wscript.quit (err.number)

wbeminst.AddressType = "MS_LAN"
wbeminst.DesSiteCode = SiteCode
wbeminst.ItemName = SiteCode & "|MS_LAN"
wbeminst.ItemType = "Address"
wbeminst.Order = 1
wbeminst.SiteCode = ParentSiteCode 
wbeminst.UnlimitedRateForAll = True

Set newp1 = WbemServices.Get("SMS_EmbeddedProperty").SpawnInstance_()
if (err <> 0) then wscript.quit (err.number)

newp1.PropertyName = "Connection Point"
newp1.Value = 0
newp1.Value1 = SiteServer
newp1.Value2 = "SMS_SITE"

Set newp3 = WbemServices.Get("SMS_EmbeddedProperty").SpawnInstance_()
if (err <> 0) then wscript.quit (err.number)

newp3.PropertyName = "LAN Login"
newp3.Value = 0
newp3.Value1 = "" 
newp3.Value2 = "" 

Set newp7 = WbemServices.Get("SMS_EmbeddedPropertyList").SpawnInstance_()
if (err <> 0) then wscript.quit (err.number)

newp7.PropertyListName = "Pulse Mode"
newp7.Values = pulsemode

WbemInst.Props = Array(newp1,newp3)
WbemInst.Proplists = Array(newp7)
WbemInst.Put_ , WbemContext
WbemInst.RateLimitingSchedule = ParentRates

If (err <> 0) then wscript.quit (err.number)

Set newp6 = WbemServices.Get("SMS_SiteControlDaySchedule").SpawnInstance_()
If (err <> 0) then wscript.quit (err.number)
newp6.Backup = BackupSchedule
newp6.HourUsage = Schedule1
newp6.Update = 1

newp5.Backup = BackupSchedule
newp5.HourUsage = Schedule
newp5.Update = 1
WbemInst.UsageSchedule = Array(newp6,newp5,newp5,newp5,newp5,newp5,newp6)
WbemInst.Put_ , WbemContext

If (err <> 0) then wscript.quit (err.number)

WbemServices.ExecMethod "SMS_SiteControlFile.Filetype=1,Sitecode=""" & ParentSiteCode & """", "Commit", , , WbemContext
if (err <> 0) then wscript.quit (err.number)

WbemServices.Get("SMS_SiteControlFile").ReleaseSessionHandle WbemContext.Item("SessionHandle").Value
if (err <> 0) then wscript.quit (err.number)

Booth arrays PulseMode and Schedule can be configured as follow:

Dim Schedule(24), pulsemode(2)
pulsemode(0) = 0
pulsemode(1) = 3
pulsemode(2) = 5

Schedule(0)= 1
Schedule(1)= 1
Schedule(2)= 1
Schedule(3)= 1
Schedule(4)= 1
Schedule(5)= 1
Schedule(6)= 3
Schedule(7)= 3
Schedule(8)= 3
Schedule(9)= 3
Schedule(10)= 3
Schedule(11)= 3
Schedule(12)= 3
Schedule(13)= 3
Schedule(14)= 3
Schedule(15)= 3
Schedule(16)= 3
Schedule(17)= 3
Schedule(18)= 3
Schedule(19)= 3
Schedule(20)= 1
Schedule(21)= 1
Schedule(22)= 1
Schedule(23)= 1

If you doesn’t configure the pulse mode, the rate limit will be set but the “Unlimited when sending to this address’  checkbox is set instead of ‘Limited to specified maximum transfer rates by hour”.