Should I create a single VM that runs both SCCM and SQL (maybe 4 CPU with 8 GB RAM) using Windows 2008 R2? OR Break SCCM and SQL apart as VM for SCCM and either use the physical SQL server or create a VM SQL just for SCCM ??
Also where do I want WSUS installed? On the SCCM box or a dedicated box?
Management just handed me the task of getting Configuration Manager up and running. Their initial goal is patch management and software delivery (to patch 3rd party apps). A previous tech had tried to get SCCM up and running but left the company after setup and he did not document anything. He has SCCM running on a single Virtual Server connected to a physical SQL server. My intention is to uninstall his site, format the box and start over. I have read much the last week and had a few questions to help me get started.
Current setup: about 1200 client spread over 45 branches on a fully meshed MPLS network. Each branch has a 1.5 Mbps uplink to the cloud. HQ has a 45 Mbps uplink to the cloud. Each branch has a single Windows 2003 R2 32-bit server acting as a DC and file/print server. Physical SQL server is 8 CPU / 16 GB running about 40 databases for various apps.
I can create as many Virtual Servers at HQ as required. I can install IIS on the branch DCs.
I am thinking of either one or two Virtual Servers at HQ and making the branch server Distribution Points. OK ??
Question:
Should I create a single VM that runs both SCCM and SQL (maybe 4 CPU with 8 GB RAM) using Windows 2008 R2? OR Break SCCM and SQL apart as VM for SCCM and either use the physical SQL server or create a VM SQL just for SCCM ??
Also where do I want WSUS installed? On the SCCM box or a dedicated box?
Thanks,
You can do any of the suggested scenarios. But with a total of 1.200 clients I would say you are more than fine by setting it up on a single box. I have single boxes running with 2.000 computers/clients and the performance is ok. If it turns out the you are not performing as required then you can always move the DB to a remote server without much work. I think you biggest concern is that you have to install IIS and a secondary site on all your remote DC's. I would prefer a VM running as a file/print/SCCM and another VM running as a dedicated DC.
ตอบลบ4 CPU's and 8 GB memory sounds like a very good starting point.
About the Software Update PointUpdated: October 1, 2009
ตอบลบApplies To: System Center Configuration Manager 2007
The software update point in Microsoft System Center Configuration Manager 2007 is a required component of software updates on primary sites, is an optional component of software updates on secondary sites, and is installed as a site system role in the Configuration Manager console. The software update point site system role must be created on a server that has Windows Server Update Services (WSUS) 3.0 installed. The software update point interacts with the WSUS services to configure update settings, to request synchronization to the upstream update source, and on the central site, to synchronize software updates from the WSUS database to the site server database.
Note ::
ตอบลบConfiguration Manager 2007 Service Pack 1 (SP1) requires WSUS 3.0 SP1 or WSUS 3.0 Service Pack 2 (SP2). WSUS 3.0 SP2 is required to support Configuration Manager 2007 SP2 software update management for the Windows 7 and Windows Server 2008 R2 operating systems.
There can be multiple site system servers with the software update point site system role, but only one site system server can be configured as the active software update point. When the site is in native mode, the active software update point can be configured to accept communication from all client computers. Alternatively, an active Internet-based software update point can be assigned to a remote site system server that accepts communication from only Internet-based client computers and the active software update point accepts communication from client computer on the intranet.
ตอบลบRequirements for the Software Update Point
WSUS 3.0 must be installed on each site system server before it is assigned the software update point site system role, and other requirements might be necessary depending on your environment and the Configuration Manager 2007 site server infrastructure. For information about planning for the software update point requirements, see Planning for the Software Update Point Installation.
Software Update Point Settings
The software update point settings are initially specified when creating an active software update point, and they can be modified from the Software Update Point Component properties. The software update point settings configure what site system server is the active software update point; what site system server is the active Internet-based software update point if one is specified at the site; the synchronization source; the synchronization schedule; and the products, classifications, and languages for which software updates will be synchronized. For more information about the settings for the software update point, see Planning for the Software Update Point Settings. After the active software update point is installed at a site, it must be synchronized to retrieve the software updates metadata.
Active Software Update Point
When the software update point site system role is created and configured as the active software update point, the software update point components are installed and enabled. As part of the installation, the WSUS Control Manager component is installed on the software update point computer and is responsible for periodically checking the health of WSUS. The WSUS Configuration Manager component of the SMS Executive service on the site server initially configures the WSUS settings with the settings that were specified while creating the software update point site system role. The WSUS settings are verified every hour, by default, and if any settings have been changed WSUS Configuration Manager will change them to coincide with the software update point settings. This emphasizes the fact that all settings should be made in the Software Update Point Component properties in Configuration Manager and not from within the WSUS console.
Active Internet-based Software Update Point
When the primary site server is configured for native mode, you have the option to install a second software update point to handle connections from Internet-based client computers. A new software update point site system is created but not configured as active. Then, from the Software Update Point Component Properties dialog box, you specify the site system as the Internet-based software update point. The initial configuration is the same as an active software update point except that there are additional requirements when the site is in native mode.
Note::
ตอบลบInternet-based software update points are only supported on site systems for primary site servers. Even though the option to install an Internet-based software update point on secondary sites is available, it will not be accessed by client computers and is not supported.
Installing a Software Update Point at a Secondary Site
ตอบลบAt a secondary site, you have the option of installing an active software update point for the site. Having a software update point at a secondary site provides local access to client computers when scanning for software updates compliance. When the secondary site does not have a configured software update point, client computers will connect to the active software update point on the parent site. You will need to determine whether client computers at the remote site have sufficient connectivity to WSUS running on the parent site or whether WSUS running on a local software update point is required.
Note::
WSUS running on the software update point for the secondary site is configured to be a replica of the active software update point for the parent site.
Important.
ตอบลบInternet-based software update points are not supported on secondary sites.