Configuration Manager Site Supported Configurations

 

 

Primary Site Server

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Enterprise Edition SP 1 x64

Windows Server 2003 Datacenter Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

Secondary Site Server

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

Management Point

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

State Migration Point

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

Distribution Point

Windows Server 2003 Web Edition SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter and Storage Server Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

Distribution Point - Branch DP Role Only

Windows XP Professional Service Pack 2

Windows XP Professional for 64-bit Systems

Windows Vista Business, Enterprise and Ultimate Editions

 

Reporting Point

Windows Server 2003 Standard Edition SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

Server Locator Point

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

Site Database Server

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

Software Update Point

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

Fallback status point

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

PXE service point

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

Configuration Manager Console

Windows XP Professional Service Pack 2

Windows XP Professional x64

Windows Vista Business, Enterprise and Ultimate Editions

Windows Server 2003 Web Edition SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter and Storage Server Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

SCCM 2007 Mobile Device Clients Supported

SCCM 2007 Clients as Mobile Device Client's

 

 

Windows CE 4.2 (ARM processor only)

Windows CE 5.0 (ARM and x86 processors)

Windows Mobile 5.0 Smartphone

Windows Mobile 6 Classic

Windows Mobile 6 Professional

Windows Mobile 6 Standard

Windows Mobile for Pocket PC 2003

Windows Mobile for Pocket PC 2003 Second Edition

Windows Mobile for Pocket PC 5.0

Windows Mobile for Pocket PC Phone Edition 2003

Windows Mobile for Pocket PC Phone Edition 2003 Second Edition

Windows Mobile for Pocket PC Phone Edition 5.0

Windows Mobile Smartphone 2003

Let play a Game with SCCM 2007; Quize on SCCM 2007 ; SCCM 2007 Games

Here is the Microsoft Link...

 

 

http://www.microsoft.com/downloads/details.aspx?familyid=B9FB478A-EC98-47F2-B31E-57443A8AE88F&displaylang=en

 

 

The following quizzes are available:

Configuration Manager 2007 Client Installation Quiz
Configuration Manager 2007 Client Management Quiz
Configuration Manager 2007 Client Site Assignment Quiz
Configuration Manager 2007 Desired Configuration Management Quiz
Configuration Manager 2007 Internet-Based Client Management Quiz
Configuration Manager 2007 Native Mode Quiz
Configuration Manager 2007 Network Access Protection Quiz
Configuration Manager 2007 Wake On LAN Quiz
New! - Configuration Manager 2007 Software Updates Operations Quiz
New! - Configuration Manager 2007 OSDeployment Quiz
New! - Configuration Manager 2007 What's New Quiz
New! - Configuration Manager 2007 Software Updates Configuration Quiz
New! - Configuration Manager 2007 Mobile Device Management Quiz
New! - Configuration Manager 2007 Fundamentals Quiz
New! - Configuration Manager 2007 Client Roaming Quiz
New! - Configuration Manager 2007 Software Updates Interop Quiz
New! - Configuration Manager 2007 Setup Quiz
New! - Configuration Manager 2007 Software Distribution Quiz

 

 

Enjoy,

Paddy

Management Point (MP) Logs

 

 

MP_Ddr	Records the conversion of XML.ddr records from clients, and copies them to the site server.
MP_GetAuth	Records the status of the site management points.
MP_GetPolicy	Records policy information.
MP_Hinv	Converts XML hardware inventory records from clients and copies the files to the site server.
MP_Location	Records location manager tasks.
MP_Policy	Records policy communication.
MP_Relay	Copies files that are collected from the client.
MP_Retry	Records the hardware inventory retry processes.
MP_Sinv	Converts XML hardware inventory records from clients and copies them to the site server.
MP_Status	Converts XML.svf status message files from clients and copies them to the site server.

SCCM 2007 Client To Site Communication Ports

 

 

 

 

Service	Port	Description
Client Request-HTTP (TCP)	80	(default) Client Requests-HTTP (TCP)
Client Request-HTTPS (TCP)	443	(default) Client Requests-HTTPS (TCP)

 

 

By default the HTTP port is set to Port 80 and the HTTPS port is set to Port 443 and as mentioned above can be modified or changed to reflect your infrastructures needs.

 

The ports can also be modified using the PortSwitch VBS script included on the installation media in the Tools\PortConfiguration directory folder using the following syntax to change the HTTP Port number:

 

 

The following g Registry key holds the information for the HTTP and HTTPS ports:

 

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM

HttpPort=dword:Decimal Value

HttpsPort=dword:Decimal Value

SCCM Ports are configurable & some are not

 

 

Configurable Ports

 

Client to internet (as proxy server settings)

Client to reporting point

Client to site system

Software update point to internet (Proxy server settings)

Software update point to WSUS server

 

UnConfigurable Ports

 

Configuration Manager 2007 console to SMS Provider

Configuration Manager 2007 console to the Internet

Site server to site database server

Site server to site system

Site system to site database server

Site to site (Primary-to-primary or primary-to-secondary)

SQL Query To Find Unhealthy Machines

SQL Query:

 

Select Distinct

Name 'Machine Name',

LastUser 'Last Logged On User',

WasOnline,

LastPingResult State,

Classification Status

From ClientHealthResults

 

Where LastPingResult Is Not Null

And Classification = 'UnHealthy'

RoboCopy VBS Script

VBS script with source and destination folder input dialog boxes as well as hard coding the RoboCopy command line switches opposed to issuing the commands from the command prompt

 

 

 

Set objShell = CreateObject("Wscript.Shell")

 

objSource = InputBox("Enter Source")

objDestination = InputBox("Enter Destination")

 

objCommand = "RoboCopy.Exe " & Chr(34) & objSource & Chr(34) & " " & Chr(34) & objDestination & Chr(34) & " /e /r:1 /w:2"

objShell.Run(objCommand)

 

MsgBox "Done"

What's New in Configuration Manager 2007

Some aspects of Configuration Manager 2007 have changed very little since SMS 2003, while some have changed a lot. Also, several new features have been added and some features have been removed.

The following features are new to Configuration Manager 2007:

• Desired configuration management
  
• Network Access Protection for Configuration Manager
  
• Wake On LAN
  

The following features were previously available only in Feature Packs but are now incorporated into the core product:

• Mobile device management
  
• Operating system deployment
  
• Transfer site settings wizard
  
• Manage site accounts tool (MSAC)
  
• Asset Intelligence
  

The following features have changed significantly from SMS 2003:

• Backup and recovery
  
• Software updates
  

The following features have been improved but still function very much as they did in SMS 2003:

• The administrator console
  
• Collections
  
• Software distribution
  
• Software metering
  
• Remote tools
  

The following features either have not changed or have minor changes:

• Discovery
  
• Inventory
  
• Queries
  
• Reporting
  

The basic site infrastructure has not changed. You still have primary sites and secondary sites, although the new feature for software distribution called the branch distribution point might remove the need to create some child sites in your hierarchy. Site-to-site communication is still configured using senders and addresses; however, in Configuration Manager 2007 senders can be installed only on primary or secondary site server systems. Configuration Manager 2007 now supports hosting the site database on a clustered SQL Server virtual instance as well as SQL Server 2005 named instances. Several new server roles have been added to support new features.

In SMS 2003 you had two types of clients, but in Configuration Manager 2007 you have only one client type, which is similar to the SMS 2003 Advanced Client. Some of the client deployment methods have changed and some methods have been removed. A new method, software update point client installation, allows you to leverage your software update infrastructure to deploy Configuration Manager 2007 clients.

In SMS 2003 you had two security modes, but in Configuration Manager 2007 you have the equivalent of SMS 2003 advanced security. However, you now have two site modes: Configuration Manager 2007 native mode and Configuration Manager 2007 mixed mode. Although site modes are not at all related to the SMS 2003 security modes, they do involve the security of your Configuration Manager 2007 environment. Native mode is a requirement to support Internet-based client management, a new feature that allows you to manage clients that do not have a direct connection to your site.

In SMS 2003, the site server's local subnet is automatically used as the site boundary for the site during setup. In Configuration Manager 2007, there is no default boundary created during setup, and you must manually create the boundary for a site when setup has completed. In SMS 2003, there are site boundaries and roaming boundaries, but in Configuration Manager 2007, there is only one type of boundary and it is equivalent to SMS 2003 roaming boundaries. Computers are assigned as clients to Configuration Manager 2007 sites according to the site boundaries you configure in the Configuration Manager console. Boundaries can now be defined by IP subnets, Active Directory site names, IPv6 Prefix, or IP ranges.

In SMS 2003, roaming boundaries were either local or remote roaming boundaries. When creating Configuration Manager 2007 boundaries, you instead decide whether the boundary will be used for either a slow or unreliable or a fast (LAN) network connection. During upgrade, any existing remote roaming boundaries will become slow boundaries and any local roaming boundaries will become fast (LAN) boundaries.

In SMS 2003, you could not upgrade from the evaluation version of the product to the full version. Configuration Manager 2007 now supports upgrading from the evaluation version. When upgrading an evaluation version, whether it is SMS 2003 or Configuration Manager 2007, an entire setup process must be completed using the new installation source files.

In SMS 2003, the client push installation method properties used when installing clients have the default site code set to Auto. In Configuration Manager 2007, the default site code used when installing clients using the client push installation method is set to the site code of the primary site.

In Configuration Manager 2007, state messages are sent by Configuration Manager 2007 clients using a new messaging system built into the product that allows clients to send "checkpoints" of important changes of state. State messages are not the same as status messages; whereas status messages provide information about component behavior and data flow, state messages provide a snapshot of the state of a process at a specific time.

Configuration Manager 2007 also includes support for fully qualified domain names (FQDNs) and IPv6.

 

can be find more from.....http://technet.microsoft.com/hi-in/library/bb680807(en-us).aspx

Thanks,

Pavan Kumar

Status Check for Wake On Lan

On Error Resume Next

Const wbemFlagReturnImmediately = &h10
Const wbemFlagForwardOnly = &h20

arrComputers = Array("ComputerName")
For Each strComputer In arrComputers
   WScript.Echo
   WScript.Echo "=========================================="
   WScript.Echo "Computer: " & strComputer
   WScript.Echo "=========================================="

   Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\WMI")
   Set colItems = objWMIService.ExecQuery("SELECT * FROM MSNdis_DeviceWakeOnMagicPacketOnly", "WQL", _
                                          wbemFlagReturnImmediately + wbemFlagForwardOnly)

   For Each objItem In colItems
      WScript.Echo "Active: " & objItem.Active
      WScript.Echo "EnableWakeOnMagicPacketOnly: " & objItem.EnableWakeOnMagicPacketOnly
      WScript.Echo "InstanceName: " & objItem.InstanceName
      ''WScript.Echo   " **Computer" & strComputer & "  WOL Settings Failed to Retrive"
     
   Next
Next

Dell recommend using SMS WOL BIOS Settings remote Enable

Dell recommend using SMS and Dell OpenManage Client Instrumentation (OMCI).  However, this requires WMI scripting which may be prevented if security lockdown settings prevent such scripts from running.

Pros: Exposes the Dell BIOS to WMI and therefore enables almost any modification to be made by running VB script.  It also means SMS hardware inventory can then report upon  BIOS settings by extending the SMS_DEF.MOF.

Cons: Requires agent software to be run on the client.

The Dell Client Configuration Utility (DCCU) can be used as an alternative to the OMCI client to create stand-alone executables that can output configuration settings ('Get Values') to an XML file and/or configure BIOS settings ('Set Values'), including enabling WOL.

Pros: Leaves not footprint on the client

Cons: An executable file needs to be created for every action you want to perform against the BIOS; meaning heavier network utilization.

BiosConfigUtility.exe

HP provides a number of tools based on HP Client Management Interface (CMI).  The exception is HP System Software Manager (SSM) which includes a bundled utility called BiosConfigUtility.exe that modifies BIOS settings through a text-based file format, which can be used independently of SSM.   HP says a future version of HP SSM will leverage HP CMI on 32-bit and 64-bit platforms.

Modify the DNS Server Search Order for a Network Adapter

Modify the DNS Server Search Order for a Network Adapter

Configures a TCP/IP-bound network adapter to use two DNS servers: 192.168.1.100 and 192.168.1.200. Note that even if a computer only uses one DNS server, the IP address of that server must still be passed to the SetDNSServerSearchOrder method as an array (in that case, an array with only one element).  and more Scripts can be found here

On Error Resume Next  strComputer = "." Set objWMIService = GetObject("winmgmts:" _     & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2")  Set colNetCards = objWMIService.ExecQuery _     ("Select * From Win32_NetworkAdapterConfiguration Where IPEnabled = True")  For Each objNetCard in colNetCards     arrDNSServers = Array("192.168.1.100", "192.168.1.200")     objNetCard.SetDNSServerSearchOrder(arrDNSServers) Next 

SCCM Agent Related Exe file

SCCM Agent Related Exe file

 

 

 

 

ccmdump.exe
CcmExec.exe
ccmrepair.exe
CcmRestart.exe
OSDBitLocker.exe
OSDDiskPart.exe
OSDJoin.exe
OsdMigrateUserState.exe
OSDNetSettings.exe
OSDPrepareOS.exe
OSDPrepareSmsClient.exe
OSDSetupWindows.exe
OSDSmpClient.exe
OSDWinSettings.exe
SCCMNativeModeReadiness.exe
smsboot.exe
SMSCliUI.exe
SmsClrHost.exe
smsnetuse.exe
smsswd.exe
tsenv.exe
TSInstallSWUpdate.exe
TSLauncher.exe
TSManager.exe
TSMBootstrap.exe
TsProgressUI.exe
VAppLauncher.exe
VAppCollector.exe
RCLaunch.exe-Remote Control launch
RCServer.exe-Remote Control Server
clicore.exe

What's new in Windows Vista Service Pack 1 (SP1)

Improvements in reliability

Windows Vista SP1 includes improvements that address many of the most common reasons for which Windows stops responding. Many of the reliability improvements in SP1 are in response to issues that customers reported by using the Windows Error Reporting tool.

Other reliability improvements in Windows Vista SP1 include improvements in wireless computer-to-computer (ad hoc) connections, better peer-to-peer connections, such as using Windows Meeting Space, and many more.

Top of page

Improvements in performance

Windows Vista SP1 includes many changes that can improve your computer's speed and performance. Here are some of the areas that are improved:

•	Faster copying or extracting files from a compressed mode.
•	Better use of network bandwidth when browsing file shares over a network.
•	Improved performance from Windows ReadyBoost in reducing the time it takes for Windows to wake up from Hibernate and Standby power modes.
•	Better power consumption when your computer screen is idle for a long time.
•	Improved logon experience when using a corporate computer, such as a laptop, outside of the corporate network.
•	Faster opening of large image files.

 

Improvements in security

You can now use BitLocker to encrypt multiple partitions on your computer's hard disk, rather than just a single partition. Note that BitLocker is only available in Windows Vista Enterprise and Windows Vista Ultimate.

 

Changes to search

SP1 includes an important change to the way desktop search works in Windows Vista. You can now select a default desktop search service, similar to the way you can select a default search service for web browsers and media players. With SP1, you can now get to your preferred search results from within the Start menu and Windows Explorer.

 

Changes in memory (RAM) reporting

SP1 also changes how the random access memory (RAM) that is installed in your computer is reported. Before SP1, the amount of memory reported was equal to the amount of memory that Windows was able to use. In SP1, the amount of memory reported is the amount of memory that is actually installed on your computer. If you have 4 gigabytes (GB) of memory installed, you'll now see 4 GB of memory reported by features such as System or Performance Information and Tools in Control Panel. This change can only happen if your computer's basic input/output system (BIOS) is capable of displaying that much RAM.

 

Advanced information

If you are an IT professional or an advanced user and want additional detailed information about SP1, you can find the release notes, the SP1 deployment guide, and other information at the Windows Vista Service Pack 1 Resources page on the Microsoft TechNet website.

Query Criterion Values

String Values

You must specify the exact string that the query will use to evaluate the expression — do not use quotation marks unless they are part of the string. For relational operators that perform LIKE comparisons ("is like" or "is not like"), you can use wildcard characters within the string. You can use the following wildcards.

Wildcard	Description
%	Any string of zero or more characters
_ (underscore)	Any single character
[]	Any single character within the range or set (for example [a-f] or [abcdef])
[^]	Any single character not within the specified range (for example [^a-f] or [^abcdef])

Date and Time Values

You must enter a date that the query can use to evaluate the expression. This value must be entered according to the units that are specified by the date and time operator. For example, if you use the "year is after" operator, you would enter the year by using four digits (for example, 2002).

When you write queries by using Configuration Manager 2007 Query Builder, you can express the date and time in any valid SQL format. For more information, see the SQL Server documentation.