Blog de Aurélien BONNIN [EXAKIS]

Blog sur les technologies Microsoft System Center & le Déploiement

May 2008 - Posts

System Center Configuration Manager 2007 | "Service Pack 1 is available for download"
Une nouvelle très attendue du côté de SCCM 2007 : la mise à disposition du Service Pack 1 en version US du System Center Configuration Manager 2007.  Disponible en téléchargement à partir du lien suivant : http://www.microsoft.com/downloads/details.aspx?FamilyID=5aae62e8-4b7f-4af7-be01-aefaa4bf059a&DisplayLang=en  

Vous trouverez ci-dessous un descriptif de ce Service Pack 1, descriptif mis en ligne par Jeff Wettlaufer, Sr. Technical Product Manager sur System Center Configuration Manager. 


Today we release Configuration Manager 2007 SP1!  It is amazing to see that this was not a release based in bug fix, quite the opposite, there are hardly any hotfixes included in this release.  This is a reflection of changes such as the ship of Windows Server 2008 and Vista SP1.  With some engineering cycles aligning, we have added some additional features that were ready to go at this time, details are as follows:


As a recap SP1 specifically contains:     

1.     
Complete support for management of Windows Vista SP1 and Windows Server 2008. 


2.     
Support for Configuration Manager 2007 Server Site roles on Server 2008. 


3.     
Integration with Intel VPro technologies.


4.     
Asset Intelligence 1.5 

You can find additional details, and information for download on our product homepages, located here.
http://www.microsoft.com/systemcenter/configmgr/default.mspx Also, we will have a full Technical overview at the upcoming Teched USA in Orlando June 10-13th.  We have a full breakout session , and we will be running SP1 (and R2 previews ) at the Microsoft pavilion pod area.  Also, we have a Technet webcast on Configuration Manager 2007 SP1, you can find that here.
Share this post:                                       
System Center Configuration Manager 2007 | "Sizing SCCM Architecture for Deployment Features"

Ci-dessous vous trouverez des informations très complètes afin de « Sizer » une architecture SCCM 2007. Ici ce sizing d’architecture est orienté afin de répondre à des problématiques de déploiement de postes de travail.

Ces informations sont extraites d’un article des Deployment Guys et sont le fruit du travail d’un consultant MS, UK. Article de référence : http://blogs.technet.com/deploymentguys/archive/2008/05/20/sccm-for-deployment-rough-sizing-guidelines.aspx  

 

Site System Maximum recommended number per site
Clients Up to 200,000 per hierarchy
Primary Site Server Up to 100,000 directly assigned clients
Secondary Site Server Up to 500 secondary sites per primary
clip_image001Note
The number of secondary sites recommended per primary site is based on reasonably well connected and reliable WAN network connections. Unreliable server hardware or network connections can dramatically reduce this number.
Management Point Up to 25,000 clients
clip_image001Note
To support more than 25,000 clients in one site, management point site systems can be configured to use Network Load Balancing (NLB).
Distribution Point Up to 4,000 clients
clip_image001Note
The number of clients that one distribution point can support is dependent on network speed, disk performance, and software distribution package size.
Branch distribution point Up to 2,000 per site, each capable of supporting up to 100 clients.
Software update point Up to 25,000 clients
clip_image001Note
To support more than 25,000 clients in one site, software update point site systems can be configured to use Network Load Balancing (NLB).
System Health Validator point Up to 100,000 clients (or one per hierarchy if less than 100,000 clients)
Fallback status point Up to 100,000 clients (or one per site)

 

SCCM Site Server(running site server all roles not specifically listed on other servers)
Component Capacity
CPU Twin Processor with Quad Cores 2.2 Ghz
Disk OS                                80 GB Raid 1 SCCM Application           80 GB RAID 10 or 5 Distribution Point            250 GB RAID 10 or 5 Data drive can be SAN or DAS if external
LAN 100 /1000 MB (sec) production LAN 1000 / MB or Fibre for NLN array Comms
RAM 8 GB
OS Windows Server 2003/8 Standard Edition 64 bit IIS Network Load Balancing
Licences Windows Server 2008 Standard Edition or 2003 R2 with SP2 SCCM site server licence (only 1 required fo this implementation)

 

SCCM Site Database Server(running site server all roles not specifically listed on other servers)
Component Capacity
CPU Twin Processor with Quad Cores 2.2 Ghz
Disk OS                    80 GB Raid 1 Data                 300 GB RAID 10 or 5 SQL Logs           300 GB RAID 10 or 5 Data drive can be SAN or DAS if external
LAN 100 /1000 MB (sec) production LAN 1000 / MB or Fibre for NLN array Comms
RAM 8 GB
OS Components Windows Server 2003/8 Enterprise Edition 64 bit IIS Network Load Balancing
Licences Windows Server 2008 Enterprise Edition (if clustering)  or 2003 R2 with SP2 SQL Server 2005 Enterprise (if clustering support is needed otherwise standard will suffice) 20,000 SCCM Client Access Licences

 

 Management Point Servers
Component Capacity
CPU Twin Processor with Dual Cores 2.2 Ghz
Disk OS 80 GB Raid 1 Data 80 GB RAID 10 or 5 Data drive can be SAN or DAS if external
LAN 100 /1000 MB (sec) production LAN 1000 / MB or Fibre for NLN array Comms
RAM 8 GB
OS Components Windows Server 2003/8 Standard Edition 64 bit IIS Network Load Balancing
Licences Windows Server 2008 Standard Edition or 2003 R2 with SP2

 

Software Update Point Server
Component Capacity
CPU Twin Processor with Dual Cores 2.2 Ghz
Disk OS 80 GB Raid 1 Data 80 GB RAID 10 or 5 Data drive can be SAN or DAS if external
LAN 100 /1000 MB (sec) production LAN 1000 / MB or Fibre for NLN array Comms
RAM 8 GB
OS Components Windows Server 2003/8 Standard Edition 64 bit IIS Network Load Balancing Windows Software Update Services
Licences Servers 2008 / 3 OS

 

Remote / Branch Infrastructure Options
Branch Size (# users) SCCM Remote Architecture Capacity / Licence Requirements
0-3 users No local infrastructure No SCCM specific licence required beyond the SCCM CAL
3-25 users Single Branch Distribution Point No SCCM specific licence required beyond the SCCM CAL
25 – 100 users Dual Branch Distribution Points (fault tolerance and capacity as images and packages will be extensively used) No SCCM specific licence required beyond the SCCM CAL
100 – 1000 users Distribution Point Windows Server 2003 / 2008 NTFS volume with 100 GB of capacity. Can leverage existing file / application server capacity. No SCCM specific licence required
1000 – 2000 users Secondary SCCM site Server No SCCM specific licence required beyond the SCCM CAL. Windows Server 2003 / 2008 server licence
2000 users + Primary site server SCCM site server
  This post was contributed by Richard Smith a Senior Consultant with Microsoft Services, UK.

Share this post:                                       
System Management Server 2003 | "Performing a domain rename/migration"
Petit article intéressant que je me permets de relayer afin que vous puissiez aussi en bénéficier et aussi afin que je puisse toujours l’avoir sous la main J.Qui ne s’est jamais demandé quel impact pouvait avoir une opération de migration ou de re-nommage d’un domaine Active Directory sur une infrastructure SMS 2003 en place ?Et bien voici le discours officiel vis-à-vis de cette opération ; discours officiel porté par J.C. Hornbeck (Manageability Knowledge Engineer) dont l’article est disponible à l’adresse suivante : http://blogs.technet.com/smsandmom/archive/2008/05/15/sms-2003-performing-a-domain-rename-migration.aspx . Merci à lui.

 “A question I get asked every now and then that doesn't seem to be particularly well documented is whether SMS 2003 supports renaming of the domain or domain migration.  While technically two different things, the short answer is no, we do not support changing the domain name that SMS 2003 is installed into.Page 235 of the Scenarios and Procedures for Microsoft Systems Management Server 2003: Planning and Deployment doc says:

Caution:
To change the domain name and the computer name after SMS is installed, you must remove your installation of SMS, change the names, and then reinstall SMS. To avoid this time-consuming task, consider this information carefully before you enter it.
For the long answer, see the notes below:
  • If SMS primary or secondary sites exist in the domain that is being renamed, SMS will have to be uninstalled and then reinstalled with the new domain name. You will not be able to restore the existing SMS database after reinstallation - you will have to start with a clean database.
  • If the domain being renamed is part of an SMS site but has no primary or secondary sites located in it (only logon servers and clients), the domain should be removed from the site prior to the name change and added back into the site after the change.
  • If you are running Internet Information Server, you might need to change the account specified in virtual paths. 
SMS client and SMS sever components pass only NetBIOS names to the operating system for resolution. SMS never uses fully qualified domain names. If a computer’s common name is the same as its NetBIOS name, and DNS is configured appropriately, you can manually resolve the common name to an IP address with the Net Use command. In this case, SMS will operate properly without WINS.”
Share this post:                                       
Systems Management Server 2003 R2 | "Support for Microsoft Update Standalone Package (msu)"
Microsoft vient d’annoncer à travers son site Connect (http://connect.microsoft.com) qu’il cherchait activement des clients disposants d’infrastructures SMS 2003 SP3 R2 afin de réaliser des tests en condition de production (ou du moins proches des conditions de production) d’une mise à jour récemment développée pour SMS 2003 SP3 R2 et destinée à la prise en charge du format MSU (Microsoft Standalone Update)  pour les mises à jour de sécurité destinées aux postes de travail sous environnement VISTA.Actuellement SMS 2003 SP3 supportent seulement la prise en charge de mises à jour aux formats EXE, MSI et MSP. Cet add-on au R2 de SMS 2003 apporterait ainsi le support des mises à jour au format MSU via l’outil Microsoft CUSTOM UPDATE TOOL (faisant partie intégrale du R2 de SMS 2003 SP3), permettant ainsi de scanner les postes VISTA, de remonter un inventaire faisant apparaitre la non-présence de ces MSU sur le/les postes en question, le téléchargement et la distribution de ces mises à jour sur les postes VISTA.  
Share this post:                                       
System Center | "System Center Roadmap"

Ca se passe de commentaire tout est dans le tableau ci-dessous Stick out tongue Encore de quoi faire de beaux projets.


Share this post:                                       
System Center | "New Gadget : System Center Content Search"
Un petit gadget dédié aux produits de la gamme System Center a été présenté au MMS cette semaine. Ce gadget disponible à l'adresse suivante : http://gallery.live.com/LiveItemDetail.aspx?li=49e26ad0-113d-4f3d-a711-57f6530c75d9 a pour but de fournir à vos recherches un ensemble de résultats puisés sur un certain nombre de sites et de pages Internet référencés comme apportant des informations pertinentes sur la suite de produit System Center. « This gadget makes it easier to find help for Microsoft System Center products because it uses Live Search macros to search specific sites instead of the entire web. Search results are only returned from sites that are known to contain helpful information about System Center products. Use the settings in the gadget to pick the System Center product that you want to find information about, and then enter a search term in the gadget to get customized search results. » Ci-dessous un petit aperçu graphique de ce gadget.

Share this post:                                       
System Center Configuration Manager | "SCCM 2007 SP1/R2 & Asset Intelligence feature"
Après l’annonce de Microsoft effectuée au MMS, concernant la sortie de Configuration Manager 2007 Service Pack 1 au mois de Mai (et non Juin comme annoncé à l’origine) et de la disponibilité de SCCM 2007 R2 au mois de juillet (plus d’information ici), Dan Boldo (Program Manager, System Center Asset & License Management Team) vient d’annoncer les nouveautés apportés par SCCM SP1 concernant AI.  May, 2008: AI 1.5 will ship with Configuration Manager 2007 SP1
  • New UI to enable product catalog customizations as well as software license entry.
  • On-demand or scheduled asset catalog updates for SA customers.
  • Ability to import license information (both MS and 3rd party) that shows licenses utilized vs. licenses purchased.
  • New catalog with enhanced schema
 Ci-dessous un historique de l’évolution de Asset Intelligence depuis l’achat de la société Asset Metrix, en 2006, à l’origine de cette fonctionnalité. May, 2006: AssetMetrix acquired
  • Offered comprehensive asset inventory and reporting services.
  • Comprehensive IP around Asset Intelligence (e.g. Taxonomy, Classification)
  • Significant Knowledge Base that had 70,000,000 software instances and over 350,000 software titles.
 April , 2007: AI 1.0 ships with SMS 2003 SP3
  • Extends SMS inventory agent to collect additional artifact data.
  • New SMS reports that simplify asset & license reporting.
  • Semi-annual targeted updates planned with first already released.

November, 2007: AI 1.1 Ships with Configuration Manager 2007
  • Improved performance and reporting accuracy.
  • New reports on CAL utilization (user & device) for Windows Server (2000+) and Exchange (2003+).
  • Enhanced asset mgmt capabilities including hardware change reports and application usage reporting.

 Message d'origine : http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3275994&SiteID=17 

Share this post: