Thursday, July 15, 2010

TechNet Virtual Labs: System Center

TechNet Virtual Labs: System Center

Application Virtualization
Configuration Manager and Systems Management Server

 

Data Protection Manager

 

Operations Manager

 

SoftGrid
System Center Service Manager
Systems Center Essentials (SCE)

Tuesday, July 13, 2010

DP Pros and Cons

BDP PROS:

· Content on demand

· Uses bits to get content

BDP CONS:

· SCCM client breaks so does the DP

· Requires an unprotected DP to get content

· Less robust reporting than a secondary site.

DP PROS:

· Senders

· Better reporting

· No need for unprotected parent DP

DP CONS:

· No content on demand

· Uses SMB to get content

Monday, July 12, 2010

System Center Family

Below are the Microsoft System Center product alignment

 

image

Tuesday, July 6, 2010

The following WMI namespaces are created by SMS 2003:

The following WMI namespaces are created by SMS 2003:

  • root\ccm

  • root\CCM\VulnerabilityAssessment

  • root\CCM\Events

  • root\CCM\invagt

  • root\CCM\SoftMgmtAgent

  • root\CCM\LocationServices

  • root\CCM\DataTransferService

  • root\CCM\Messaging

  • root\CCM\Policy

  • root\CCM\SoftwareMeteringAgent

  • root\CCM\ContentTransferManager

  • root\CCM\Scheduler

  • root\cimv2\sms

  • root\SmsDm

  • root\sms

  • root\sms\inv_schema

  • root\sms\site_<sitecode>

Monday, July 5, 2010

Troubleshooting WinPE and task sequence issues

You can troubleshoot some common WinPE and task sequence issues.

WinPE never starts the task sequence

Check the SMSTS.LOG file at X:\windows\temp\smstslog\smsts.log. If a package never downloaded, it is likely that you simply do not have the appropriate network drivers installed, which prevents the machine from communicating with Configuration Manager.

Check your driver catalog to ensure you have the right network drivers available and installed into the boot image, and update the boot image to your distribution points.

Additional network or storage drivers might be needed in the boot image to enable the WinPE boot to function correctly. You should add those through Drivers in the Operating System Deployment node.

The right drivers have been added to the boot image, but are not loading

The original boot.wim file (WinPE boot image) created during Configuration Manager installation is copied and modified with IBM-specific drivers and other files. Your task sequences that use the IBM Deployment Pack must use this boot image or the tools might not work properly.

Check to make sure the image into which you loaded the drivers is the same image being used by the task sequence.

This is a common error for administrators who maintain multiple boot images.

Servers will not boot using PXE

PXE is an extension of DHCP, which uses a broadcast type of communication. Broadcast communication uses standard timeout values that are not readily changeable. As a result, a computer waits for a default timeframe to receive a DHCP or PXE response before timing out and causing a failure condition.

Each time a server is rebooted, it must renegotiate the connection to the switch. Some network switches arrive configured with default settings that might incur connectivity delays. That is, the settings on the switch might cause a DHCP or PXE timeout because they fail to negotiate a connection in time.

One of the features that can be affected by this issue is Spanning Tree Protocol (STP). STP is a protocol that prevents loops and provides redundancy within a network. A networking device using this algorithm might experience some latency as it collects information about other network devices. During this period of information collection, servers might boot to PXE and time out while waiting for a response from Windows® Deployment Services. Disable the STP or enable PortFast on end-node ports for the target server to prevent such occurrences. Refer to the manufacturer’s user guide for further information.

Another feature that can be affected by this issue is the EtherChannel or Port Aggregation Protocol (PAgP). EtherChannel allows multiple links between devices to act as one fast link that shares the load between the links. Running the EtherChannel Protocol in automatic mode can cause a connectivity delay of up to 15 seconds. Switch to a manual mode or turn off this feature to eliminate this delay.

Speed and duplex negotiation can also play a role in negotiation timeouts. If auto-negotiation on the switch is set to off, and the server is not configured to that speed and duplex setting, the switch will not negotiate with that server.

For more information, see the Cisco Web site and the following Cisco documents:

Default boot order does not allow PXE to boot when a valid drive exists

When an active partition is created on a hard drive, it automatically becomes a bootable device if a valid operating system has been installed. If your PXE NIC is after the hard drive in the boot order, the hard drive tries to boot before PXE and boots to Windows, or causes an Invalid System Partition error if Windows is not installed.

To resolve this issue, be sure that PXE is placed before the hard drive in the boot order. Keep in mind that even if PXE is first in the boot order, the computer does not actually boot to PXE unless Configuration Manager has a task sequence for it to run.

When using a “Reboot” action after initializing an array controller, the task sequence fails

Configuration Manager 2007 does not allow a task sequence to reboot back to PXE. It can reboot back to WinPE or to an installed operating system, both of which require a disk partition and the appropriate installed software.

Without a disk partition, Configuration Manager will fail when attempting to reboot during a task sequence because it expects to copy WinPE to the disk. Additionally, the management point tracks when a machine has booted to PXE to run a task sequence, and once a machine has booted to PXE for a task sequence, it cannot use PXE as a boot method again for that task sequence unless the advertisement is reset.

To perform a reboot to PXE if you need to within a task sequence, use the custom action called “Reboot To PXE." This custom action, written using C# and VBScript, connects to the Configuration Manager 2007 SDK, and contains custom code to drive actions in the admin console as well as the machine being deployed. This custom action performs all the steps necessary to perform the reboot to PXE and allow for proper program flow when it occurs.

The only other way to accomplish a reboot to PXE is to use more than one task sequence, let the computer “fall off the end” of the first task sequence and manually reset the PXE advertisement for the computer.

Task sequence fails with “Failed to Download Policy” and code 0x80093102 or 0x80004005

This error code typically refers to a certificate validation issue.

The SMSTS.LOG file will show an entry with the following text:

CryptDecryptMessage ( &DecryptParams, pbEncrypted, 
nEncryptedSize, 0, &nPlainSize, 0 ), HRESULT=80093102

or

no cert available for policy decoding

Possible causes are:


  • Misconfiguration of your domain or a site server, such as DNS not pointing to the site server, or the site server not specifying a valid FQDN (which is referred to by the DNS listing).

    If your site server does not specify a FQDN (and only specifies the NETBIOS name), and your DNS server refers to the FQDN, a faulty lookup might cause this error.


  • The certificate being used for PXE and boot media.

    Check the certificates under the Site Settings node and see if any certificates are blocked or missing. Open the certificates and ensure that they are actually installed into the certificate store. If not, install them.


If these actions do not work, try removing the package from the distribution point (via Manage Distribution Points) and adding the package again to regenerate the package hash.


Task sequence fails with “Failed to Download Policy” and code 0x80004005


This error code typically refers to a certificate validation issue.

The SMSTS.LOG file will show an entry with the following text:

failed to download policy

Check the certificates under the Site Settings node to if any certificates are blocked or missing. Open the certificates to ensure that the certificates are installed into the certificate store. If not, install the certificates.

Task sequence fails because the package is not downloading


In WinPE, the default option of “Download content locally when needed by running task sequence” will not work. When in WinPE, the task sequence engine will ignore (and fail) all actions that have packages set for this option.

Set all packages needed for use in WinPE to “Access content directly from a distribution point when needed by the running task sequence.”

Task sequence does not run again even after clearing the PXE advertisement


You must set the advertisement to “Always rerun” so that any time you reset the PXE advertisement, the advertisement is applied to the computer regardless of whether it ran the task sequence before.

Task sequences fail or act incorrectly after an upgrade


When upgrading from a previous version of this product, existing task sequences using these custom actions are not automatically updated.

To function correctly, open each task sequence action that uses a custom action in an editor. Add a “.” to the description and remove it to enable the Apply button. Click Apply to refresh the properties of the custom action and save any new automatic data or formatting that is required to function with the new version.

Files and logs are not being returned from the client


A number of issues can prevent the task sequence from returning files or logs from the client.

Among the possible issues that might prevent the task sequence from returning files or logs from the client are:


  • Failure of the client-side script prior to the file copy, which is usually evident in the log file.

    Repeat the task and press F8 during the task to get to a command prompt, if you selected the check box for Enable command support on the boot image properties > Windows PE page.

    Then open the SMSTS.LOG file. The location varies. In WinPE via PXE, the location is at X:\Windows\Temp\Smstslog\smsts.log.


  • Malformed XML in the IBM Deployment Packconfiguration file.
  • The command being executed actually has an error but exits with code 0.

    This can occur when a severe error is encountered in the script while the script is set to ignore errors and use programmatic error handling. Then the error handling did not catch the same error.

    Report such issues to the IBM® support site, as described in Getting help and technical assistance.


  • The task sequence cannot access the share or mapped drive that is the target drive for copying the files or logs.

Logs are being returned but not output files


A number of issues can prevent the task sequence from returning output files while allowing the task sequence to return log files.

Among the possible issues that might prevent the task sequence from returning output files from the client are:


  • No return file parameters are specified in the configuration XML.
  • Return file parameters in the configuration XML are incorrect.
  • An error is occurring with the operation of the utility that generates the output file.
  • A null variable is causing an error in the file name of the file to be returned.

Task step execution does not automatically change after a change to the configuration XML file


If you change the configuration XML, previously existing task steps do not automatically change unless you edit them.

To fix the existing task steps, open the task sequence editor and make a minor edit to each custom action step in the sequence. You can simply add a “.” to the description and then delete it to enable the Apply button. Click Apply. The task sequence steps are now saved with the automatically updated information from the new XML file.


Task sequence fails at “Apply Operating System” with “Failed to make volume X:\ bootable”


Several problems can cause this error.

This issue is indicated by log content similar to the following text:

MakeVolumeBootable( pszVolume ), 
HRESULT=80004005
(e:\nts_sms_fre\sms\client\osdeployment\applyos\installcommon.cpp,759)

Failed to make volume E:\ bootable.
Please ensure that you have set an active partition on the boot
disk before installing the operating system.

Unspecified error (Error: 80004005; Source: Windows)

ConfigureBootVolume(targetVolume),
HRESULT=80004005
(e:\nts_sms_fre\sms\client\osdeployment\applyos\applyos.cpp,326)

Process completed with exit code 2147500037

This issue can be related to two different scenarios:


  • If you are using a Format & Partition action in your task sequence to partition the hard drives, make sure that you select the check box for Make this the boot partition on one of the partitions.

    If you do not make a drive bootable and the computer has only the single drive, the task sequence engine automatically makes one of the partitions the boot partition. But if there are multiple drives, the task sequence engine cannot determine which drive should be bootable, and you see this error.


  • If you upgraded from the Configuration Manager RTM to SP1, you might have a problem if both hard drives are completely raw. If you have never partitioned the drives, a known bug in Windows PE prevents Windows PE from determining the drive where it was booted, and you see this error.

    This situation is likely on a server with a RAID controller where you have just formed two or more RAID sets. The new RAID sets are completely raw because they have never existed before.

    The only workaround to the problem of multiple raw drives is to manually boot into Windows PE and run "diskpart" to partition at least one of the drives. Then run the task sequence again. The task sequence should work.

    The known problem with Windows PE is fixed in Windows Vista SP1 and hence in the Windows PE that is derived from Vista SP1.



Install Configuration Manager 2007 SP1
Configuration Manager 2007 SP1 includes the SP1 version of the Windows Automated Installation Kit (WAIK). Download and install Configuration Manager SP1 to get the new version.

Upgrading to Configuration Manager 2007 SP1 automatically updates your default boot images, but does not automatically upgrade the IBM boot images.

Upgrade the IBM boot images by rerunning the IBM Deployment Pack installer and selecting “Modify”. You must also update your distribution points so that the new images are used. You should also update the distribution points for the default boot images as well.

The product installer detects the version of WinPE that is currently in use by the default boot images. If the default boot images are not Vista SP1, the product cannot install.


How to tell if your boot images are upgraded to Vista SP1
Boot image properties contain an identifier for “OS Version.”

Perform this procedure to see the version of WinPE in your boot images:


  1. Click Computer ManagementOperating System DeploymentBoot ImagesIBM Deployment.
  2. Right-click the boot image and select Properties.
  3. Click Images.
  4. Check the OS Version property for a value of 6.0.6001.18000 or greater.


What to do if your boot images are not upgraded to Vista SP1
You can manually recreate your boot images using the Windows AIK and following the steps listed in Technet: How to Add a Boot Image to Configuration Manager.

If your Configuration Manager processes permit, you might find it easier to remove the old boot image packages using the Admin Console, delete the files in the OSD\boot directories, and rerun the SP1 upgrade installation.


How to tell if WAIK was upgraded to Vista SP1


  1. Click Start > Run; then run the Regedit command.
  2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ComponentStudio.
  3. There should be a single key under this key, which is named with the number of the Windows AIK version.

    Note: Only one version of Windows AIK can be installed. However, an uninstall operation might have failed to remove the registry key.

    In such a case, the registry key with the highest version number should be the correct version number.


What to do if Windows AIK was not upgraded to Vista SP1
Configuration Manager is supposed to automatically upgrade the Windows AIK version during an upgrade to Configuration Manager SP1. If that did not occur, try manually uninstalling Windows AIK and rerunning the Configuration Manager SP1 upgrade.

To download Windows AIK, see the Microsoft Download Center: AIK page.


System environment variables are not carried over to the next action in the task sequence


When a task sequence runs, commands run in a command shell. When the task ends, so does the command shell environment, which causes the loss of any system variables that are defined in the task.

To pass variables between tasks, set the variables as “Task Sequence variables,” “Collection variables,” or “Machine variables.”

IBM Link :P

one other link http://publib.boulder.ibm.com/infocenter/toolsctr/v1r0/index.jsp?topic=/dpsccm/dpsccm_t_running_sysprep_w2003.html

SYSPREP for 2k3

When working with Virtual Machines, Sysprep is a real timesaver. You can, on a virtual machine, install several configurations of servers (SMS 2003, SQL or SCCM or vNext, etc), sysprep the images, and then have these pre-configured images ready to deploy to a VPC or any Vcenter  installation when needed, by just copying the appropriate VHD file over and associating it with a new VM.

In order to run Sysprep, you first need to install it. You can get a hold of Sysprep in two ways: it is on the \Support\Tools\Deploy.cab file on the Windows Server installation media, or you can download it from here. Once you get a hold of the Deploy.cab file, you should extract the contents to a directory on your HD, for example c:\Deploy.

SYSPREP1

This directory contains several useful tools, and you should definitely read the deploy.chm file for instructions and details on the process. There are two files that are of particular importance to the process: sysprep.exe and setupmgr.exe.

For sysprep to work completely automated, it requires an answer file, called sysprep.inf. This answer file contains the “answers” to all the questions asked by the Windows installer during the setup process. The answer file can be created manually with any text editor, but fortunately there is a nice wizard-like tool that can help you generate this file. This tool is the setupmgr.exe program:

SYSPREP2

This program allows you to generate the sysprep.inf file by presenting you the options and letting you enter the default answer. In order to fully automate an installation, follow these steps on the Setup Manager:

  1. Click Next on the Welcome screen
  2. Select “Create new” and click “Next”
  3. Select “Sysprep setup” and click “Next”:
    SYSPREP2a
  4. Select the type of system you’re going to sysprep, and click “Next”
  5. Select “Yes, fully automate the installation” and click “Next”
  6. Now you need to fill in all the information required to complete the process:
    SYSPREP2b

Once you complete the execution of the Setup Manager, it creates a new directory in the root of the system drive called sysprep. This directory contains all the information necessary for the Sysprep tool to execute.

SYSPREP4

Now you need to execute the Sysprep tool, sysprep.exe:

In this tool:

  1. Click “OK” on the warning dialog that appears when running the tool.
  2. Select “Don’t reset grace period for activation”
  3. Set the “Shutdown mode” to “Shut down”
  4. Click on Reseal. That will leave the image ready for copying.

Once the image is copied, you can just configure a new virtual machine with the new image, and start it up. The last portion of the Windows setup process will execute:
SYSPREP5

After a little while (<10min), the machine will reboot, and the process will be completed. You now have a brand new sysprep’d and cloned server up and running!!

 

for more info http://technet.microsoft.com/en-us/library/cc765993(WS.10).aspx

 

For Windows XP SP3 :-

 

Step #1

The first step is to download the Sysprep App which is included in the CAB file for Windows XP Service Pack 3 Deployment Tools. (Download Sysprep Tool)

Step #2

Next go to the PC you are going to be sysprepping and create a folder on the root of the C: drive called sysprep.

Step #3

Next you will need to extract the contents of the deploy.cab file you downloaded in Step #1 to the sysprep folder on the root of the C: drive.

Step #4

Now we are going to run the sysprep Setup Manager. Double click on setupmgr.exe.

Sysprep Setup Manager

Sysprep Setup Manager

Step #5

Click Next and it is going to ask you whether you want to modify an existing Answer File or create a new one. We are wanting to create a new one, so again click next.

Sysprep - New or Existing Answer File

Sysprep - New or Existing Answer File

Step #6

You now have three options: Unattended Setup, Sysprep Setup, or Remote Installation Services (RIS). In this example we are going to select the Sysprep setup option and then click next. (This creates a sysprep.inf file)

Sysprep - Sysprep.inf File

Sysprep - Sysprep.inf File

Step #7

Select Windows XP Professional and click next. (This will also work on Windows XP Home, Windows Server 2003 Standard, Web, and Enterprise.)

Sysprep - Windows XP Professional

Sysprep - Windows XP Professional

Step #8

In this step it is asking you if you want to fully automate the installation. That is up to you, either way works fine. In this example I will be using the “No, do not fully automate the installation.”

Sysprep - Fully Automate or Not?

Sysprep - Fully Automate or Not?

Step #9

Now we are at the configuration page. There is a lot in here so I am not going to go into detail. In fact, you don’t even need to input anything here for the sysprep to just work. However, everything you input in here will save you time and help shape your image.

Sysprep - Configuration Page

Sysprep - Configuration Page

Step #10

Once you are all done, you should be at the bottom and selected on “Identification String”; click Finish and it is going to prompt you for a location to create and save the sysprep.inf file. The default location is fine, as it will need to be within that sysprep folder on your C: drive. Once you hit ok you will then need to click “Cancel”. There is no close button.

Sysprep - Saving the Sysprep.inf File

Sysprep - Saving the Sysprep.inf File

Step #11

Now you should verify the sysprep.inf file by double clicking on it and opening it up with Notepad.

Sysprep - Verifying the Sysprep.inf File

Sysprep - Verifying the Sysprep.inf File

Step #12

There were a few changes with Windows XP Service Pack 3 and sysprep. The administrator’s profile is no longer copied over to the default profile. You will need to add a line within the sysprep.inf file to regain this important function. Under the InstallFilesPath section add this:

UpdateServerProfileDirectory=1

Once done, hit save.

Sysprep - Adding line to sysprep.inf so the administrator profile will copy over to default profile

Sysprep - Adding line to sysprep.inf so the administrator profile will copy over to default profile

Step #13

Now you are ready to start the sysprep, reboot, and capture your sysprepped image. Double click on the sysprep.exe and then select the following three options in order: Use Mini-Setup, Shutdown Mode: Reboot, and click Reseal. Make sure you have your media ready to capture your image. If you reboot fully without booting to your capturing software it will ruin the sysprep and you will have to redo the sysprep.

Sysprep - Preparation Tool 2.0

Sysprep - Preparation Tool 2.0

  • Sysprep will now get rid of any machine specific identifiers and shutdown the computer.
  • The hard disk is now ready to be imaged.  You can at this stage use tools such as Ghost or boot using your WinPE CD and capture the image to a WIM file.
  • Deploy your image to a computer and restart it.
  • If you start the new computer using the newly deployed image, sysprep will now setup Windows according to the settings in sysprep.inf.
    Image-0273
  •  

    For Windows Vista / 7 / 2008

     

    Type this command with administrative privileges in command prompt

     

    c:\windows\system32\sysprep\sysprep.exe /quiet /generalize /shutdown /oobe

    c:\Windows\System32\sysprep\sysprep.exe

    The experience is also streamlined considerably. Simply run sysprep.exe above and you are presented with:

    image

    Check the “Generalize” checkbox (regenerates system SID), change the Shutdown Options to “Shutdown”, and click OK. The system will go through the sysprep process and shut itself down.

     

    Using Your SysPrep’d Image to Create a New Virtual Machine

    Now, creating a new virtual machine will only take just a couple minutes.

    1. First, you need to copy your SysPrep’d image to a new name and to a new location where you will use this new virtual machine.  Copy your SysPrep’d image files (.vmc & .vhd) to a new location where you want your new virtual machine file to reside.
    2. Rename them to a new, appropriate name.  For example, if you are going to create a SharePoint server you might name them something like:
      1. MySharePoint2007.vmc
      2. MySharePoint2007.vhd
    3. Add this new virtual machine to you Virtual PC or Virtual Server; which ever you are using;
    4. Edit the configuration and make sure the virtual hard drive (VHD) is pointing to your new .vhd file.  In this example, the MySharePoint2007.vhd file.
    5. Configure any other items such as memory allocation and network cards as necessary.
    6. Start the virtual machine.
    7. You will receive a few prompts such as the name for you new machine.
    8. If you wish, you can now join you virtual machine to a domain.

    SysPrep is a must have time-saving tool for anyone who uses Virtual PC and/or Virtual Server.

    Thursday, July 1, 2010

    Microsoft Security Bulletin Minor Revisions

    ********************************************************************
    Title: Microsoft Security Bulletin Minor Revisions
    Issued: June 30, 2010
    ********************************************************************

    Summary
    =======
    The following bulletins have undergone a minor revision increment.
    Please see the appropriate bulletin for more details.

    * MS10-041 - Important
    * MS10-040 - Important
    * MS10-038 - Important
    * MS09-040 - Important

    Bulletin Information:
    =====================

    * MS10-041 - Important

    - http://www.microsoft.com/technet/security/bulletin/ms10-041.mspx
    - Reason for Revision: V1.3 (June 30, 2010): Corrected the registry
       key verification for Microsoft .NET Framework 3.5 and
       Microsoft .NET Framework 2.0 Service Pack 2.
    - Originally posted: June 8, 2010
    - Updated: June 30, 2010
    - Bulletin Severity Rating: Important
    - Version: 1.3

    * MS10-040 - Important

    - http://www.microsoft.com/technet/security/bulletin/ms10-040.mspx
    - Reason for Revision: V1.1 (June 30, 2010): Added a link to
       Microsoft Knowledge Base Article 982666 under Known Issues in
       the Executive Summary to address the issue where specific
       installations of IIS fail on restart after installing this
       security update.
    - Originally posted: June 8, 2010
    - Updated: June 30, 2010
    - Bulletin Severity Rating: Important
    - Version: 1.1

    * MS10-038 - Important

    - http://www.microsoft.com/technet/security/bulletin/ms10-038.mspx
    - Reason for Revision: V1.2 (June 30, 2010): Added a link to
       Microsoft Knowledge Base Article 2027452 under Known Issues
       in the Executive Summary.
    - Originally posted: June 8, 2010
    - Updated: June 30, 2010
    - Bulletin Severity Rating: Important
    - Version: 1.2

    * MS09-040 - Important

    - http://www.microsoft.com/technet/security/bulletin/ms09-040.mspx
    - Reason for Revision: V1.1 (June 30, 2010): Added a link to
       Microsoft Knowledge Base Article 971032 under Known Issues in
       the Executive Summary.
    - Originally posted: August 11, 2009
    - Updated: June 30, 2010
    - Bulletin Severity Rating: Important
    - Version: 1.1

    Tuesday, June 29, 2010

    All Available IMP Links for SCCM destination

    Many times people things about the destination of SCCM Available resources below are some i can suggest

    Books:- Yep there are Three Books available below are the links

    1) System Center Configuration Manager (SCCM) 2007 Unleashed by Kerrie Meyler $37.79 http://www.amazon.com/System-Center-Configuration-Manager-Unleashed/dp/0672330237

    2) Mastering System Center Configuration Manager 2007 R2 by Chris Mosby $37.79

    3) System Center Operations Manager 2007 Unleashed by Kerrie Meyler $40.94

     

    CBT’s,

    Yes there are two best CBT’s offered these are most popular

    cbtnuggets

    http://www.cbtnuggets.com/webapp/product?id=421

    Exam-Pack 70-401: Microsoft Systems Center - Configuration Manager
    $299.00 - Includes 20 Videos

     

    CBT Planet

    http://www.cbtplanet.com/microsoft-it/microsoft-system-center-configuration-manager-training-video.htm

    Microsoft System Center Configuration Manager 2007 (SCCM) CBT Training Course

     

    Topics Based Courses also offered from

    http://blogcastrepository.com/level5/sccm/default.aspx

    for some of them it is free and for most of them you need to pay :D

     

    OK, Now Cools free supported WebPages for SCCM & SMS is below

    and also…..

    Rod Trent's Blog

    Great people Blogs:

    SMS 2003 Client Health : GP Based Script

    Source:-http://www.myitforum.com/absolutenm/templates/Articles.aspx?articleid=17217&zoneid=87

     

    Overview

    Workstation Client Health maintenance is a continuous process that must be maintained. The following document gives an overview on how to fix several common workstation issues.
    CliFix GPO startup script :- Can be downloaded from here http://myitforum.com/cs2/blogs/scassells/Public_SMS_CLIFIX_4.19.vbs.txt
    In an effort to reduce the amount of common workstation issues I have developed a script to check and change the following common issues. This script is to be run via GPO startup scripts. This requires the script to work as the system account and have intranet connectivity. Both are accomplished by running as a GPO. Script Requirements
    1. Script must be in a location where the computers system account has access. Usually on your domain controller ex. \\FQDNDomain\sysvol\ FQDNDomain\
    2. sc.exe must be present for full successful run.
      1. Either in the run path
      2. system32
      3. system32\DLLCache
      4. Note: there are multiple versions floating around in the average environment
    3. regsvr32.exe needs to be present
    4. %systemroot%\system32 needs to be in system path
    Script Settings

    All, unless I missed some, sections of the script can be turned on and off in the top of the script. Please review the script as some features will fail without modification.

    Please Review the following CONFIG SETTINGS Variables:

    • SMSVersion
    • ConfigMgrVersion
    • WKS_ASSIGNSITECODE
    • WKS_CacheSize
    • WKS_LocalAdminGroup
    • WKS_admACCT
    • RegPath
    • strWebAddress
    • StrCCRServer
    • strCCRSiteCode
    • CCMSetUP
    What the Script Does
    1. Checks to make sure the script has not run in X many hours.
      1. Example if X = 12 the script will not run again until at least 12 hours after the last occurrence.
      2. This will prevent a slow down on multiple reboots.
    2. Sets DCOM permissions to be correct for SMS / SCCM configuration
    3. Checks to make sure System Path has the 3 required windows paths enabled. (does NOT use WMI or require a restart to change values)
      1. C:\windows
      2. C:\windows\sysetm32
      3. C:\windows\system32\wbem
      4. Also removes %systemroot% from path replacing it with correct full path value
      5. If one of the 3 paths is missing, it will parse the full path removing duplicates and adding a,b,or c to the beginning of the path statement leaving all else unchanged.
    4. Check to see if sc.exe exists in the run from directory and if not in the system32 directory
    5. Checks to see if this script is run on a workstation or server. If a server kills the script
    6. Checks to make sure the correct local admin group is present (value is set in header of script)
    7. Checks WMI service to see if it is set to auto and running. If not executes sc.exe to start the service.
    8. Attempts to connect to WMI object
    9. If the WMI object connect fails
      1. Attempt to do a repair (if no previous status is present in the registry and approved via script switches)
      2. Attempt to do a rebuild (if ‘repair’ status is present in the registry and approved via script switches)
      3. If both the above have failed then do nothing and report major error
    10. Checks to see if Admin$ is present, if not forces existence via WMI
    11. Checks to see if msxml3.dll is registered, if not forces existence via WSH
    12. Checks to see if Qmgr.dll and qmgrprxy.dll are registered, if not forces existence via WSH
    13. Checks to see if OLEAut32.dll is registered, if not forces existence via WSH
    14. Checks to make sure the following services are set to appropriate Status and Mode
      1. RPC
      2. WMI
      3. Firewall/ICS
      4. Server Service
      5. Remote Registry
      6. BITS
      7. Windows Update Services
      8. Terminal Services
      9. Windows Installer
      10. Note: You may want to review the settings for your environment on each of these services. All of the above services are set to default and either Manual or Automatic.
    15. Check the SMS version
    16. Checks the CCMExec service
    17. If SMS is not correct version can be forced to do an install
      1. Needs Review
    18. If the all of the above test passed without issue you have a healthy workstation. The following two checks are for SMS.
      1. Check log file last update time. If the PolicyEvaluator.log file has not been modified in past 14 days do a repair of the client.
      2. Check client assignment. If no assignment set new site code based on AD boundaries in which the client is present.
        1. Note: Some people may want to disable this as it relies on AD
    19. If any fixes above had to be preformed
      1. Check the advanced client state. Which client policies have enabled.
      2. Check the cache size
      3. Send a Client Configuration Request (CCR) to have client installed
      4. Run CCMSetup from the install share on the server.
    Note during this script several forms of reporting, logging, and information submitting have been preformed. The standard methods of reporting are:
    • Event log
    • Log file in the %temp% directory for the account used to run
      • GPO = C:\windows\temp
    • Reporting to a website that submits client status to a SQL table.
      • Future WebPost on how to do this
    Other verbose methods include:· Two levels of command line reportingo Log to Command lineo Verbose to command line· network share copy

    Future Additions:

    Area's that need improvement

    Below are the port Numbers used in SMS 2003

    • Site Server to child and secondary sites as well as SMS SQL Server.
    445 - Server Message Block (SMB)
    389 - Lightweight Directory Access Protocol (LDAP)
    636 - LDAP (Secure Sockets Layer (SSL) connection)


    • Proxy Management point to parent SQL Server
    1433 - TCP (SMS Site Server to SQL Server)
    389 - LDAP
    636 - LDAP (Secure Sockets Layer (SSL) connection)


    • Advanced Client to Management Point and Distribution Point
    80 - Hypertext Transfer Protocol (HTTP)
    139 - Client sessions (for non BITS-enabled DPs)
    445 - Server Message Block (for non BITS-enabled DPs)
    389 - UDP (User Datagram Protocol) LDAP Ping
    389 - TCP LDAP
    636 - TCP LDAP (Secure Sockets Layer (SSL) connection)
    3268 - TCP (Explicit connection to Global Catalog)


    • Remote Control System service (Wuser32)
    2703 - TCP SMS Remote Chat
    2703 - UDP SMS Remote Chat
    2701 - TCP SMS Remote Control (Control)
    2701 - UDP SMS Remote Control (Control)
    2702 - TCP SMS Remote Control (Data)
    2702 - UDP SMS Remote Control (Data)
    2704 - TCP SMS Remote File Transfer
    2704 - UDP SMS Remote File Transfer


    • Remote Control UDP *
    137 - Name resolution
    138 - Messaging
    139 - Client sessions
    * Only applies if you use NetBIOS over TCP/IP for SMS Remote Control
    • Microsoft SQL Server
    1433 - TCP SQL server
    139 - TCP Named pipes


    • Active Directory Discovery methods
    389 - TCP LDAP
    389 - UDP LDAP
    636 - TCP LDAP (Secure Sockets Layer (SSL) connection)
    135 - TCP RPC Endpoint Mapper
    135 - UDP RPC Endpoint Mapper
    3268 - TCP Global Catalog LDAP
    3269 - TCP Global Catalog LDAP (Secure Sockets Layer (SSL) connection)
    88 - TCP Kerberos
    88 - UDP Kerberos


    • Microsoft Windows NT UDP
    53 – UDP Domain Name System (DNS)
    67 – UDP Dynamic Host Configuration Protocol (DHCP)
    135 – TCP Remote procedure call (RPC)
    138 – UDP Windows Internet Name Service (WINS)
    138 – UDP NetBIOS Datagram Service Computer Browser
    139 – TCP NetBIOS Datagram Service Messenger

    Monday, June 28, 2010

    OSD Log Files Location

    Unfortunately, the smsts.log can be stored in one of 7 locations, depending on the stage of the build and the architecture of the OS:

    • WindowsPE, before HDD format:
            x:\windows\temp\smstslog\smsts.log
    • WindowsPE, after HDD format:
            x:\smstslog\smsts.log and copied to c:\_SMSTaskSequence\Logs\Smstslog\smsts.log
    • Full version windows, before SCCM agent installed:
            c:\_SMSTaskSequence\Logs\Smstslog\smsts.log
    • Full version windows, after SCCM agent installed:
            c:\windows\system32\ccm\logs\Smstslog\smsts.log
    • Full version x64 windows, after SCCM agent installed:
            c:\windows\sysWOW64\ccm\logs\Smstslog\smsts.log
    • After Task Sequence has finished running
            c:\windows\system32\ccm\logs\smsts.log
    • After Task Sequence has finished running(x64)
            c:\windows\sysWOW64\ccm\logs\smsts.log

    Thursday, June 24, 2010

    Windows Update Explained

    Windows Update Explained

    Source  as it is

    http://download.microsoft.com/download/a/9/4/a94af289-a798-4143-a3f8-77004f7c2fd3/Windows%20Update%20Explained.docx

     

    How the Software Update Service Works and Why it Matters to You

    Published: September 2008

    For more information, please see http://www.microsoft.com/windows/downloads/windowsupdate/default.mspx

    Contents

    Introduction. 1

    The Problem with Keeping Computers Up to Date. 1

    Windows Update to the Rescue. 2

    Windows Update for Individual Computers. 2

    Windows Update in Windows Vista. 2

    Windows Update in Windows XP. 4

    Updating Networked Computers. 6

    Windows Server Update Services. 6

    Customizing Windows Server Update Services. 6

    How Updating Works. 7

    Checking for updates. 7

    Downloading updates. 7

    Installing Updates. 8

    Rebooting your computer. 8

    Reporting. 8

    When the Windows Update Client is Updated. 9

    Security Protections in Windows Update. 9

    Additional Resources. 10


    Introduction

    We’ve all heard about or even experienced the havoc that computer viruses and other malicious software can cause to PCs and computer networks. Computer hackers are constantly trying to find ways to attack networks and computers with the intent of committing fraud and other crimes. When they succeed, individuals and enterprises can lose a great deal of time and money. In spite of their high cost and the headaches they cause, many security breaches are easily avoidable. The security fixes are available, but users don’t get them installed quickly enough (or at all).

    Have you ever wondered what Microsoft is doing to help? Or did you know that Microsoft® Windows® Update is an important part of the solution, but weren’t sure exactly what it does or how it works. If so, this paper is for you.

    For individual PC users, this paper will help you understand how to use Windows Update to keep your PC up to date, not only to help protect it from malicious software, but to keep it functioning at its best. If you’re responsible for networked computers, this paper will help you understand how Windows Update and Windows Server® Update Services (WSUS) can help protect groups of computers.

    The Problem with Keeping Computers Up to Date

    With Internet usage increasing, it’s more important than ever to keep your PC protected from malicious code. Understanding this, the people at Microsoft have been hard at work to help ensure that your PC continues to function well and that your personal information is very safe. Special teams at Microsoft proactively search for security vulnerabilities in Microsoft software and provide security updates. One of those teams is the Microsoft Security Response Center (MSRC). The MSRC is on call 24 hours a day, 7 days a week and dedicated to identifying, monitoring, resolving, and responding to Microsoft software security vulnerabilities.

    In addition to security updates, Microsoft provides other software updates that make your computer run better and give you a better Windows experience. For example, an update may fix an issue with a hardware device, improve the performance of your computer, or deliver improved Windows features.

    Downloading and installing the latest software updates, particularly security updates, quickly and consistently on your PC is vital to maintain both its security and its proper functioning. For network administrators, applying updates on computers across your organization—small, medium, or large—is a crucial measure for keeping your systems secure and running properly. Yet doing this manually requires constant time and attention, which many people simply don’t have available for the task. There must be an easier way!

    Windows Update to the Rescue

    Fortunately, there is an easier way, thanks to Windows Update, a free, built-in service included with Windows. This service helps you keep your PC more secure and reliable as well as compatible with devices and applications. It provides a single location for getting updates and scheduling automatic updating.

    Using Windows Update by itself, you get updates for Windows and new or updated hardware drivers. For the other Microsoft software installed on your computer, use Microsoft Update. By turning on Microsoft Update, you get all of the benefits of Windows Update, but you get security and non-security updates for your other Microsoft software, such as Microsoft Office and the Windows Live™ network of internet services. Turning on Microsoft Update is recommended for all Windows PCs. To turn on Microsoft Update, go to http://update.microsoft.com/microsoftupdate.

    Windows Update for Individual Computers

    It is easy to improve the security and reliability of your PC, and take advantage of the continuous improvements Microsoft makes to Windows. Just use this four-step process:

    1. Turn on Windows Update. You probably did this when you set up your new PC by selecting the option to “Help protect Windows automatically.”

    2. Use the recommended settings. Windows Update is designed to work automatically and not interrupt you while you’re working on other things. Using the recommended settings, you get all of the benefits from the service, such as quick delivery of very important security updates, and you get them with fewer interruptions.

    3. Turn on Microsoft Update. Microsoft Update includes updates for both Windows and other Microsoft products. This makes it easy to keep all your Microsoft software updated. To turn on Microsoft Update, go to http://update.microsoft.com/microsoftupdate.

    4. Check Windows Update periodically. You will find a list of lower priority recommended and optional updates that you can choose to download and install. These include driver updates, new product features, and so forth. These updates will keep your PC functioning smoothly.

    Windows Update has slightly different settings in the Windows Vista® and Microsoft Windows XP operating systems, as described in the following sections. For more information about Windows Update and its features, see http://www.microsoft.com/windows/downloads/windowsupdate/default.mspx.

    Windows Update in Windows Vista

    In Windows Vista, you can configure Windows Update settings and view and install updates from Windows Update in your Control Panel. If you go to the Windows Update Web site (http://update.microsoft.com), Windows Update opens automatically.

    Getting Help in Windows Vista

    Windows Update Help provides complete information and procedures for using Windows Update. To open it, click the Help button in the upper-right corner of the Windows Update control panel.

    Figure 1: Windows Update control panel in Windows Vista

    To configure or change settings, click the Change settings link in the left navigation pane. The Change settings screen displays.

    Figure 2: Change settings screen in Vista

    The most secure option is Install updates automatically (recommended). When you choose this option, you don't have to worry that critical fixes for Windows might be missing from your computer if you don’t have time to install them personally. Nor must you worry about Windows Update slowing down your PC’s Internet connection, while it downloads updates, because it operates in the background in a way that won’t interfere with your Internet usage. For more information about how Windows Update behaves during the download and installation process, see “How Updating Works,” later in this paper.

    Updates in Windows Vista

    Important updates offer significant benefits, such as improved security and reliability. Examples include security and critical reliability updates.

    Recommended updates address non-critical problems and help enhance your computing experience. Examples include upgrades to Windows features and less important software updates.

    Optional updates are not downloaded or installed automatically. Examples include less critical driver updates and new Windows or Microsoft software.

    You can choose to have updates downloaded automatically and then install them manually, or you can choose to both download and install updates manually. In either case, Windows Update still continuously checks for updates automatically and notifies you when important or recommended updates are available. Still, the most convenient and secure option is to make both download and installation automatic.

    Even if your PC is configured for automatic updating, you should periodically check that important updates have been installed and also check for Optional updates. To do to this, click the Check for updates link in the left navigation pane of the Windows Update control panel. On the screen that displays, you can review any available updates and install them.

    Windows Update in Windows XP

    In Windows XP, check for updates from the Windows Update Web site http://update.microsoft.com, and configure automatic updating settings from the Automatic Updates program in Control Panel, shown in the following figure.

    Getting Help in Windows XP

    For general Windows Update help and support go to http://update.microsoft.com and click Get help and support in the left-hand navigation pane.

    To get help for the Automatic Updates program in Control Panel, click How does Automatic Updates work?

    Figure 3: Automatic Updates control panel in Windows XP

    The most secure option is Automatic (recommended). When you choose this option, you don't have to worry that critical fixes for Windows might be missing from your computer.

    Updates in Windows XP

    High-priority updates offer significant benefits, such as improved security and reliability. Examples include security and critical reliability updates.

    Optional updates are not downloaded or installed automatically. You need to manually view and install these updates from within Windows Update. Examples include less important software updates, drivers, updates to Windows features, and new Windows or Microsoft software.

    You also don’t need to worry about Windows Update slowing down your PC’s Internet connection and computer. It is designed to operate in the background and minimize interruptions. For more information about how Windows Update behaves during the download and installation process, see “How Updating Works,” later in this paper.

    You can choose to have updates downloaded automatically and then install them manually, or you can choose to both download and install updates manually. In either case, Windows Update still continuously checks for most updates automatically and notifies you when High-Priority updates are available. Still, the most convenient and secure option is to let Windows Update download and install updates automatically.

    With Windows XP, you should check the Windows Update Web site regularly because many of the updates that improve your experience with Windows are not installed automatically. To view all of the available updates, first make sure you upgrade to Microsoft Update, and then click the Custom button, as shown in the following figure.

    Figure 4: Windows Update Web site for Windows XP

    Updating Networked Computers

    Windows Update makes it easy to automatically update a home computer or small group of business computers. However, if you are managing a network of 10 or more computers, you may want to manage the update process for computers on your network. By managing the update process, you have more control over which updates are installed and when they are installed.

    Windows Server Update Services

    Windows Server Update Services (WSUS) is a free add-on for the Windows Server operating system to help network administrators manage updates for computers. By using WSUS with Active Directory® group policy, administrators can fully manage update settings and the distribution of updates for computers on their network. To find out more about using WSUS, go to the Windows Software Update Services (WSUS) Web site http://technet.microsoft.com/en-us/wsus/default.aspx.

    Note: Microsoft also provides the System Center Family of business software for fully managing (including updates) desktop computers and servers in medium to large organizations. For more information, see http://www.microsoft.com/systemcenter/en/us/default.aspx.

    Customizing Windows Server Update Services

    Microsoft provides a complete, programmable, and scriptable API that network administrators and software developers can use to create custom updating behaviors for WSUS. System administrators can use the WSUS API to determine which updates apply to a computer or group of computers, download those updates, and install them with little or no user intervention. Independent software vendors and developers can integrate WSUS features into computer management or update management software to provide a seamless operating environment. For more information, see http://msdn.microsoft.com/en-us/library/bb905331.aspx.

    How Updating Works

    During the updating process, the Windows Update client operates in the background to download and install updates. (The Windows Update client is the Windows Update component running on your PC.) It does this automatically, according to your settings, and in a “silent” manner that doesn’t disrupt your computer usage. This section describes how Windows Update behaves during the update process.

    Checking for updates

    The Windows Update client on your PC checks the Windows Update server at Microsoft for the availability of new updates at random intervals, every 17 to 22 hours. The randomization ensures that the Windows Update server is not overloaded with requests for updates all at the same time. The client is very efficient in checking for new updates and searches only for updates that have been added since the last time updates were searched, allowing it to find updates quickly and efficiently.

    When checking for updates, the Windows Update client evaluates whether the update is appropriate for your computer using guidelines defined by the publisher of the update, for example, Microsoft Office.

    If the computer is not online at the time you specified to check for updates, then the Windows Update client begins checking every five hours until it successfully finds updates. If more than 30 days have gone by without successfully finding updates, the client will notify you. If you should receive such a notification, you should connect your computer to the Internet, go to the Windows Update Web site, and check for updates.

    Downloading updates

    Once the Windows Update client determines which updates apply to your computer, it will begin downloading the updates, if you have selected the option to automatically download updates. It does this in the background without interrupting your normal use of the computer.

    To ensure that your other downloads aren’t affected or slowed down because updates are downloading, Windows Update uses the Background Intelligent Transfer Service (BITS) technology which downloads updates using idle bandwidth. This technology ensures that Windows Update downloads only when no other active download is in progress on the computer. This allows you to smoothly carry on day-to-day activities even while updates are being downloaded in the background.

    Windows Update also supports pausing and restarting downloads. You do not have to worry if you need to shut down your computer, or if you have lost your Internet connection while an update is downloading. Once the connection is reestablished, the download will continue where it left off.

    Installing Updates

    When downloading is complete, depending on your Windows Update settings, the Windows Update client either installs the updates automatically, or else it notifies you of the download without performing the installation. You do not need to be logged in to your computer for Windows Update to automatically install updates.

    When you install Microsoft software

    When you install or reinstall a program, you must reinstall updates that came out after the installation CD or installer was created. For some programs there may be multiple updates available and some updates may require a previously released update to be installed.

    When the option to automatically install updates is configured, the Windows Update client tries to install updates as they become available. For example, if updates are available when you begin shutting down your computer, it gives you the option to install the updates before shutting down the computer. Otherwise, it installs them during the time you have specified for updates to be automatically installed. The default time for updates to be automatically installed is 3:00 AM daily.

    If your computer is not turned on during the scheduled time for installing updates, the Windows Update client will try to wake up the PC (if the PC was asleep), or wait for the PC to be turned on again. As soon as the PC is running again, it will install the updates.

    Rebooting your computer

    When the option to automatically install updates is configured, the Windows Update client, in most cases, automatically restarts the PC for you after installing the updates. This is necessary because your PC may be insecure, or not fully updated, until a restart is completed. To reduce the number of computer restarts required, the client attempts to install as many updates as possible together. If you are using the computer, you may be given the option to postpone the restart.

    Most updates can be installed automatically without any user intervention. Some updates, however, such as service packs require the user to provide explicit consent. These are not automatically installed. When you install updates manually, be sure to restart your PC if prompted to do so. Otherwise, the PC may not be updated until a restart is performed.

    Reporting

    The Windows Update client reports back to Microsoft regarding which updates have installed successfully and which, if any, failed to install. This helps the Windows Update team verify the quality of the updates provided by Windows Update. No personally identifiable information (PII) is sent to Microsoft or stored by Microsoft with the report. For more information, read the Windows Update privacy statement online at http://update.microsoft.com/windowsupdate/v6/vistaprivacy.aspx?ln=en-us.

    The Windows Update client keeps a log of all the different actions it performed on a particular computer at %windir%\windowsupdate.log. On Windows Vista, this log is available from the Windows Update control panel.

    When the Windows Update Client is Updated

    From time to time, Microsoft needs to update and enhance the Windows Update service, and that includes updating the Windows Update client software on your PC. If Windows Update is configured to check for updates, it installs a newer version of the Windows Update client automatically, so that it can continue to check for updates. If Windows Update is completely turned off, the client is not updated. If the client doesn’t update automatically then it may not be able to notify you about new updates. For this reason, Windows Update always updates the client automatically before checking for other updates. Given how important it is to maintain the quality of the update service, Windows Update always updates itself when it is turned on, regardless of whether you've chosen the option to have updates automatically installed or to be notified that they are available so that you can manually install them. If you have automatic updating turned off completely, the next time you manually check for updates, you will be prompted to update the Windows Update client before installing any updates.

    Security Protections in Windows Update

    Windows update implements many security checks and restrictions to ensure that the security of your computer is not compromised. The most critical checks validate the authenticity and quality of the software and updates that are installed on a machine. Some of the ways in which Windows Update maintains the integrity of the updates that get installed are as follows:

    1. Windows Update uses the Secure Socket Layer (SSL) protocol to send and receive information. SSL is used to encrypt the information being transferred, prevents hackers from tampering with information being transferred, and verifies that the Windows Update agent is transferring data from an authorized Microsoft server.

    2. Each update is individually signed using the Secure Hashing Algorithm (SHA-1). This technology allows Windows Update to confirm that the update has been downloaded correctly and hasn’t been changed by anyone. The update signature is also compared to information in the update metadata that was previously downloaded.

    3. Windows Update also checks for the certificate associated with each update. This certificate provides a means for Windows Update to validate the source of each update. Currently Windows Update will only install updates that have certificates issued by Microsoft or other providers that are trusted by Microsoft.

    Windows Update has many more internal security checks and controls. For example, Windows Update ensures that any action that can make your machine less secure (like turning off Windows Update) can only be performed by an authorized administrator.

    To help keep your PC more secure and reliable, it's a good idea to install new updates as soon as they're available. The easiest way to install updates is to use the Windows Update service and make sure automatic updating is turned on. Now that you know how important—and easy—it is, be sure to check your Windows Update settings today.

    Additional Resources

    For additional information about configuring and using Windows Update or to find a discussion group, see the Windows Update Home Page. http://www.microsoft.com/windows/downloads/windowsupdate/default.mspx

    For help and support, including solutions for top issues with using Windows Update and explanations of error messages, see the Microsoft Update Solution Center. http://support.microsoft.com/ph/6527#tab3

    For information about managing Windows Update on an enterprise network, see the Update Management Tech Center.
    http://technet.microsoft.com/en-us/updatemanagement/bb259683.aspx

    To learn how Microsoft monitors and responds to security issues, see the Microsoft Security Response Center Web site. It offers tools such as an alert service, monthly webcast, blog, and Really Simple Syndication (RSS) feeds to help you stay current with security-related updates and information for Windows. http://www.microsoft.com/security/msrc/default.mspx

    To learn about new security updates, find how-to articles and security tips, and get answers to security-related questions, see the Microsoft Security at Home Web site for the free, monthly Security Newsletter for Home Users from Microsoft. http://www.microsoft.com/protect/default.mspx

    For a clearinghouse of information and links about protecting your computer, see http://www.microsoft.com/protect/computer/updates/default.mspx.

    The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.

    This white paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS
    DOCUMENT.

    Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in, or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

    Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

    © 2008 Microsoft Corporation. All rights reserved.

    Microsoft, Active Directory, the Security Shield logo, Windows, Windows Live, Windows Vista, Windows Server, the Windows logo, and the Windows Update Icon are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

    RUN Command Tip’s

    1. Click Start/Run and type APPWIZ.CPL to open "Add/Remove Programs"

    2. Click Start/Run and type SYSDM.CPL to open "System Properties"

    3. Click Start/Run and type HDWWIZ.CPL to open the Add New Hardware Wizard

    4. Click Start/Run and type NCPA.CPL to open "Network Connections"

    5. Click Start/Run and type LOGOFF and press Enter to LOG OFF the current logged user

    List of log files with the description of each to remember easy.

     

    Client Component Installation Manager - Ccim

    Client Configuration Manager - Ccm

    Client Install Data Manager - Cidm

    Collection Evaluator - Colleval

    Component Status Summarizer - Compsumm

    Courier Sender - Coursend

    Courier Sender Confirmation - Cscnfsvc

    Despooler - Despool

    Discovery Data Manager - Ddm

    Distribution Manager - Distmgr

    Hardware Inventory Agent - Hinv

    Hierarchy Manager - Hman

    Hierarchy Manager - Sitecomp

    Inbox Manager - Inboxmgr

    Inbox Manager Assistant - Inboxast

    Inventory Data Loader - Dataldr

    Inventory Processor - Invproc

    LAN Sender - Sender

    License Metering - Licrsvc

    License Server Manager - Licsvcfg

    Network Discovery - Netdisc

    Offer Manager - Offermgr

    Offer Status Summarizer - Offersum

    Replication Manager - Replmgr

    Scheduler - Sched

    Sender - Sender

    Setup - SMSsetup

    Site Component Manager - Sitecomp

    Site Control Manager - Sitectrl

    Site System Status Summarizer - Sitestat

    SMS Administrator Provider - SMSprov

    SMS Executive - SMSexec

    SMS NT Logon Manager - NT_logon

    SMS Provider - SMSprov

    SMS SQL Monitor - SMSdbmon

    SMS_Bootstrap Service - SMS_bootstrap

    Software Inventory Agent - Sinv

    Software Inventory Processor - Sinvproc

    SQL Error Logs – Errorlog  and sqldbmon

    Status Manager - Statmgr

    Windows Networking Logon Discovery - NTlgdscm

    Windows Networking Logon Installation - NTlginst

    Windows NT Logon Discovery Agent - Ntlgdsca

    Windows NT Logon Discovery Manager - Ntlgdscm

    Windows NT Logon Server Manager - NT_logon

    Windows NT Server Discovery Agent – Ntsvrdis

    SCCM Product released Dates

    image

    SMS & ConfigMgr Support

     

    • If you are running SMS 2003, its time to migrate.  That product ended Mainstream support Jan 11, 2010
    • If you are running the RTM version of Configuration Manager 2007, that level of product is now out of mainstream support as of July 2009
    • If you are running Configuration Manager 2007 SP1, that level of product will go out of Mainstream support at the end of calendar 2010.
    • If you are doing a net new deployment, the recommendation is ConfigMgr SP2, on Windows Server 2008 or ‘08 R2.
    • If you are at a current level like SP2 now, its time to check out the very cool new features in the R3 beta – like Power Management.

    What Service Pack level required for Supporting

     

  • Windows 7 as a managed client requires ConfigMgr SP2
  • Windows Server 2008 either as a managed client or a host for a site role required Service Pack 1
  • Windows Server 2008 R2 either as a managed client or a host for a site role requires Service Pack 2
  • Monday, June 21, 2010

    Microsoft Desktop Optimization Pack (MDOP)

    Productivity, manageability and reduced total cost of ownership for enterprise desktops

    Enterprise IT infrastructures are increasingly complex to manage. The Microsoft Desktop Optimization Pack (MDOP) is a dynamic desktop solution that is available as a subscription for Software Assurance customers. The solution suite enhances application deployment and compatibility, increases IT responsiveness and end user uptime, and helps reduce total cost of ownership (TCO) of your desktop software and IT management.

    MDOP employs six innovative technologies to increase desktop manageability, reduce TCO, and improve overall infrastructure satisfaction:

    MDOP 2009 R2 for Windows 7 is now available!

    Learn more about MDOP 2009 R2 features.

    Read more about how customers and partners use MDOP.

    MDOP subscribers can download the software at Microsoft Volume Licensing Site (MVLS).

    MDOP is also available for test and evaluation for MSDN* and TechNet** subscribers in accordance with MSDN and TechNet agreements.

    * Available to levels: TechNet Plus SA Media; TechNet Plus (retail); TechNet Direct (retail); TechNet Plus (VL); TechNet Plus Direct (VL); TechNet Cert Partner; TechNet Gold Cert Partner; T1.

    ** Available to levels: VS Pro with MSDN Premium (Empower); Developer AA; MSDN Universal (retail); VSTS Team Suite (VL); VSTS Architecture (VL); VSTS Development (VL); VSTS Test (VL); VS Pro with MSDN Premium (VL); MSDN Universal (VL); VSTS Database (VL); VS Pro with MSDN Premium (retail); VSTS Test (retail); VSTS Development (retail); VSTS Architecture (retail); VSTS Team Suite (retail); VSTS Database (retail); BizSpark Admin; BizSpark.

    HTTP 500 Internal Server Error when accessing SCCM Reports

    If you are receiving HTTP 500 Internal Server Error when accessing SCCM Reports via web browser, check the following settings:

    1. Make sure that you are not hitting the limit of maximum rows returned by a report query. By default, report viewer in SCCM 2007 is configured to limit the results returned by a report query to 10 000 rows.

    To change the number of rows returned by a report query, create the Rowcount DWORD value under the HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Reporting registry key.

    Set its value to the number of rows that you want returned in the report query. If you want to return all rows, set the value to 0xffffffff, which is the hexadecimal equivalent of –1.

    For more information, refer to the following TechNet article: How to Configure the Maximum Rows Returned by a Report Query, available at the: http://technet.microsoft.com/en-us/library/bb680885.aspx

      2. Increase the ASP response buffer limit size (aspbufferinglimit).

      In IIS 6.0 change has been introduced which limits a default ASP response buffer to 4 MB. Increasing the buffer limit might help you in resolving this problem. To increase the buffer limit, follow these steps:

      • Click Start, click Run, type cmd, and then click OK.
      • Type the following command, and then press ENTER:

      cd /d %systemdrive%\inetpub\adminscripts

      • Type the following command, and then press ENTER:

      cscript.exe adsutil.vbs SET w3svc/aspbufferinglimit LimitSize

      LimitSize represents the buffering limit size in bytes. For example, the number 67108864 sets the buffering limit size to 64 MB.

      To confirm that the buffer limit is set correctly, follow these steps:

      •   Click Start, click Run, type cmd, and then click OK.
      • Type the following command, and then press ENTER:

      cd /d %systemdrive%\inetpub\adminscripts

      • Type the following command, and then press ENTER:

      cscript.exe adsutil.vbs GET w3svc/aspbufferinglimit

      In my case, setting the limit to the value of 12582912 (12 MB) did the trick in the Configuration Manager environment of approximately 10 000 managed devices (SCCM Clients).

      For more information about the ASP response buffer limit, refer to the following article: Error message when a Web browser sends a request for an active server page to a Web server that is running IIS 6.0: “Response buffer limit exceeded”, available at the: http://support.microsoft.com/kb/925764