Outllok issue in IE7

http://mustech.net/2007/02/20/windows-vista-webmail-owa-fix-for-internet-explorer-7-five-step-fix

 

UPDATE: Some of you are telling me that although the 
MIME upgrade fixes some of the problems but you are still experiencing
difficulty when sending messages.

This is most likely due to your service (company, etc.) not updating their
exchange server with the "hotfix".

"The cause of the problem is due to Internet Explorer 7 in Windows Vista no longer include support for Dynamic HTML Editing ActiveX control, and thus missing a functionality that Microsoft Exchange Outlook Web Access relies on to do HTML editing in Outlook Web Access."

More information about this here:

http://www.mydigitallife.info/2006/12/09…dows-vista/

and here:

http:/…06e8a-08eb-4976-bc68-a03ebe3a2552&DisplayLang=en

It appears that both the MIME download upgrade and the hotfix must be applied in order for everything to work correctly.  If you need access to your email and none of the above is working, the Opera and Firefox browsers are having no difficulty with this problem and are working fine with OWA and Vista (go figure…)
____________________________________________________

You may find yourself unable to compose a new message when trying to access your exchange server via [tag]Microsoft[/tag] [tag]Outlook[/tag] [tag]Web[/tag] [tag]Access[/tag] while using [tag]Internet Explorer[/tag]; however, you can access it with [tag]Firefox[/tag] and the Opera Browsers.  If you are having this problem you will see a [tag]red[/tag] [tag]square[/tag] with an "X" in it when you try to [tag]compose[/tag] a [tag]new[/tag] [tag]message[/tag].

I found this problem to be quite frustrating and found very little information about it on the web.  Thus, I am posting the answer here on http://www.mustech.net

The original conversation I had with about this subject may be found on http://techrepublic.com.com and found here:  Link to thread and the solution was provided by David.

Error Seen with IE7:

The Solution:

1.  Slide down the left Task Pane and Click on "options".

2. Slide down to "E-mail Security" and Click Install or Upgrade the S/MIME Control.  This will download a new add-on.

3. Click "RUN" when asked about the Microsoft Outlook Web Access S/MIME install and security warning.

4. Close and RESTART IE7

5. Go back to your Web Access Site (webmail program) and select "New" to begin composing a new message.  The program should now be functioning normally and the red "X" should be gone.

Good luck!  Your Comments and Suggestions Welcome!

-------------------
Thanks,
http://sccm07.blogspot.com/

Adding registry files silently to the remote systems.

 

 

Adding registry files silently to the remote systems.

 

Save to .cmd file and ejoy

 

================

xcopy /y Add_SUP.reg \\%1\admin$\temp\
psexec \\%1 c:\windows\regedit /s \\%1\admin$\temp\Add_SUP.reg
del \\%1\admin$\temp\Add_SUP.reg

 

================

 

 

-------------------
Thanks,
http://sccm07.blogspot.com/

WINZIP12 Silent Installation Code

WinZip Silent Installtion batch file with License file

 

 

Code:

 

===========

winzip12.msi /qn
xcopy /y /E /I WinZip.wzmul "%AllUsersProfile%/Application Data\WinZip\"

 

===========

 

Yes Life is a batch, and then you FLY

 

-------------------
Enjoy,

Paddy

Microsoft System Center Configuration Manager 2007 Exam Code 70-401

 

Skills measured

This exam measures your ability to accomplish the technical tasks listed in the following table. The percentages indicate the relative weight of each major topic area on the exam.

 

 

Skills measured by Exam 70-401
Deploying a System Center Configuration Manager 2007 (SCCM) Server (9 percent)
Set up and configure an Active Directory schema.
Migrate from an SMS 2003 hierarchy to SCCM 2007.
Configure an SCCM hierarchy.
Set up and configure security accounts.
Configuring an SCCM Infrastructure (19 percent)
Configure client agents.
Configure site boundaries.
Configure core site system roles.
Configure discovery methods.
Configure client installation.
Configure SCCM infrastructure for Internet-based client management.
Managing Resources (14 percent)
Build an SCCM collection by using queries.
Meter software usage.
Manage assets.
Manage inventory flow.
Manage client agents.
Distributing Applications (17 percent)
Manage packages.
Manage programs.
Manage advertisements.
Schedule distribution.
Track success and failure rates for distribution.
Manage distribution points.
Deploying Operating Systems (13 percent)
Capture a reference computer image.
Manage task sequences.
Configure site system roles related to deploying operating systems.
Deploy operating system packages.
Customize user state migration.
Deliver applications.
Securing a Network Infrastructure (13 percent)
Configure Network Access Protection (NAP).
Maintain NAP.
Migrate from Inventory Tool for Microsoft Update (ITMU) to Windows Software Update Services (WSUS).
Deploy software updates.
Manage vulnerability compliance.
Managing and Maintaining an SCCM Infrastructure (15 percent)
Manage system health.
Configure automatic maintenance tasks.
Create custom reports.
Maintain clients.
Manage systems by using configuration management.
Manage Wake on LAN.

 

 

-------------------
Thanks,
http://paddymaddy.blogspot.com/

DCM How to Remediate Non-Compliant Computers Using Software Distribution

How to Remediate Non-Compliant Computers Using Software Distribution

You can use the compliance results from a Configuration Manager 2007 configuration item or configuration baseline to dynamically populate a collection with computers that report a specific compliance state or a specific non-compliance severity level.

You can then use Configuration Manager 2007 software distribution to assign a package or script to this collection which could, for example, either remediate the non-compliance condition or send a notification to an administrator that this condition requires attention.

For example, an application configuration item that checks for a specific version of Microsoft Office could be configured to report as non-compliant if the version number is not your standard release version. The configuration item could additionally be configured to report a specific non-compliance level such as Error in this case. If you create a collection that dynamically populates with computers that report a non-compliance severity level of Error for this application item, you can then assign to that collection a software distribution package to install the correct version of Office. When the application configuration item is next assessed for compliance, the client computer will report a compliance status and the computer will be dynamically removed from the collection.

The query you use to specify the collection membership defines the non-compliance severity level as a number. These non-compliance severity levels map to the following numbers in the query:

 

Non-Compliance Severity Level	Number Mapping
Information - no Windows event messages	1
Information	2
Warning	3
Error	4

You can build your collection query based on the non-compliance severity level of a configuration item or a configuration baseline.

You will need to specify the unique ID associated with the configuration item or configuration baseline, in addition to the display name. You can find the unique ID values by adding the column CI Unique ID to the display columns on the home pages for the Configuration Baselines node, or the Configuration Items node.For more information, follow the procedure in How to Distinguish Configuration Data with the Same Name in Desired Configuration Management.

You can use the query builder to create your collection query, or you can use the query example in the following procedures.

After using these procedures, perform the following steps:

• Ensure that you have created a Configuration Manager 2007 package containing software or scripts to remediate the non-compliant configuration item or configuration baseline.
  
  
• Create a mandatory advertisement using standard software distribution methods to distribute this package to computers in the collection that you have created.
  
  

To remediate non-compliant computers by compliance state using software distribution

1. Copy the following query and paste it into a text editor, such as Notepad:

   Copy Code

   select SMS_R_System.ResourceId, SMS_R_System.ResourceType, SMS_R_System.Name, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.Client from SMS_R_System inner join SMS_G_System_CI_ComplianceState on SMS_G_System_CI_ComplianceState.ResourceID = SMS_R_System.ResourceId Where SMS_G_System_CI_ComplianceState.ComplianceStateName = "<ComplianceState>" and SMS_G_System_CI_ComplianceState.LocalizedDisplayName = "<BaselineName>" and SMS_G_System_CI_ComplianceState.CI_UniqueID = "<CI Unique ID>"

2. In the query, change <ComplianceState> to the compliance state of the configuration item or configuration baseline. This can be one of:

   • compliant
     
     
   • non-compliant
     
     

3. In the query, change <BaselineName> to the name of the configuration baseline or the configuration item as it appears in the Configuration Manager console.

4. In the query, change <CI Unique ID> to the unique ID associated with the configuration item or configuration baseline.

5. Create the collection by right-clicking the Collections node and then selecting New Collection to launch the New Collection Wizard.

6. On the General page, specify the collection name and, optionally, specify a description.

7. On the Membership Rules page, click the second Membership rules icon to display the Query Rules Properties dialog box.

8. Ensure System Resource is selected as the Resource class, and then click Edit Query Statement.

9. In the Query Statement Properties dialog box, click Show Query Language.

10. In the Query Statement Properties dialog box, paste the modified query into the Query Statement edit box.

11. Click OK to save the query and close the Query Statement Properties dialog box.

12. In the Query Rule Properties dialog box, optionally select Limit to collection, and then click OK.

13. On the Membership Rules page of the New Collection Wizard, optionally click Schedule if you want to define a collection membership update schedule that is shorter than the default of every day.

14. If you are defining an alternative schedule, specify your alternative in the Custom Schedule dialog box, and then click OK.

15. Complete the wizard.

To remediate non-compliant computers by non-compliance severity using software distribution

1. Copy the following query and paste it into a text editor, such as Notepad:

   Copy Code

   select SMS_R_System.ResourceId, SMS_R_System.ResourceType, SMS_R_System.Name, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.Client from SMS_R_System inner join SMS_G_System_CI_ComplianceState on SMS_G_System_CI_ComplianceState.ResourceID = SMS_R_System.ResourceId Where SMS_G_System_CI_ComplianceState.ComplianceStateName = non-compliant And SMS_G_System_CI_ComplianceState.MaxNoncomplianceCriticality = "<Severity>" and SMS_G_System_CI_ComplianceState.LocalizedDisplayName = "<BaselineName>" and SMS_G_System_CI_ComplianceState.CI_UniqueID = "<CI Unique ID>"

2. In the query, change <Severity> to the non-compliance severity level of the configuration item or configuration baseline. This can be one of the following:

   • 1 (Information - no Windows event messages)
     
     
   • 2 (Information)
     
     
   • 3 (Warning)
     
     
   • 4 (Error)
     
     

3. In the query, change <BaselineName> to the name of the configuration baseline or the configuration item as it appears in the Configuration Manager console.

4. In the query, change <CI Unique ID> to the unique ID associated with the configuration item or configuration baseline.

5. Create the collection by right-clicking the Collections node and then selecting New Collection to launch the New Collection Wizard.

6. On the General page, specify the collection name and, optionally, specify a description.

7. On the Membership Rules page, click the second Membership rules icon to display the Query Rules Properties dialog box.

8. Ensure System Resource is selected as the Resource class, and then click Edit Query Statement.

9. In the Query Statement Properties dialog box, click Show Query Language.

10. In the Query Statement Properties dialog box, paste the modified query into the Query Statement edit box.

11. Click OK to save the query and close the Query Statement Properties dialog box.

12. In the Query Rule Properties dialog box, optionally select Limit to collection, and then click OK.

13. On the Membership Rules page of the New Collection Wizard, optionally click Schedule if you want to define a collection membership update schedule that is shorter than the default of every day.

14. If you are defining an alternative schedule, specify your alternative in the Custom Schedule dialog box, and then click OK.

15. Complete the wizard.

Life is a batch, and then you FLY

Life is a batch, and then you FLY
-------------------
Thanks,
http://paddymaddy.blogspot.com/

Happy Marriage Rules

 

 

Rules for a Happy Marriage

 

ü Never both be angry at the same time.

ü Never yell at each other unless the house is on fire.

ü If one of you has to win an argument, let it be your mate.

ü If you have to criticize, do it lovingly.

ü Never bring up Mistakes in the past.

ü Neglect the whole world rather than each other

ü Never go to sleep with an argument unsettled.

ü At least once every day try to say one kind or complimentary word.

ü When you have done something wrong, be ready to admit it.

ü It takes two to make a quarrel and the one in the wrong is the one who does most of the talking

 

 

-------------------
Thanks,
http://paddymaddy.blogspot.com/

Simple Troubleshooting Management Points

 

Just below point when ever you stuck with MP issues

1) Run http://<MP name>/sms_mp/.sms_aut?mplist
This returns a blank screen.
2) Run http://<MP name>/sms_mp/.sms_aut?mpcert
This returns a long list of numbers and letters.
3) Verify that the DTS Service is enabled.
4) Verify that the Task Scheduler is enabled.
5) Verify that the Windows Management Instrumentation service is running.
6) Verify that the SMS Agent Host service is running.
7) Verify that the World Wide Web Publishing Service is running.
8) Verify that the MP machine account has been added to the
SMS_SiteSystemToSQLConnection_<site_code> group.
9) Verify that the SQL Server has named pipes enabled.
10) Update MDAC on the server.
Review Q820910 for details.
http://support.microsoft.com/default.aspx?scid=kb;en-us;820910
11) SQL boxes that are running under a user account, instead of system,
need the SPN updated in AD.
Review Q829868 for additional details.
http://support.microsoft.com/default.aspx?scid=kb;en-us;829868
12) Crossing domain boundaries between MP and SQL may also need the SPN
updated in AD.
Review Q829868 for additional details.
http://support.microsoft.com/default.aspx?scid=kb;en-us;829868
13) IIS Lockdown Tool
If you are using the IIS lockdown tool on your IIS 5 servers be sure to
apply the SMS server template from the SMS 2003 toolkit.
http://www.microsoft.com/smserver/downloads/2003/tools/toolkit.asp
14) Deinstall the MP and IIS, then reinstall IIS and the MP.
a) Remove the MP role on the server.
b) Disable IIS. Remove completely. Reboot the server.
c) Verify that the DTS Service is enabled.
d) Verify that the Task Scheduler is enabled.
e) Verify that the Windows Management Instrumentation service is
running.
f) Enable BITS, enable WEBDEV and install IIS.
g) Verify that the World Wide Web Publishing Service is running.
h) Verify that the MP machine account has been added to the
SMS_SiteSystemToSQLConnection_<site_code> group.
i) Enable MP role on the server.

-------------------
Thanks,
http://paddymaddy.blogspot.com/

SCCM 2007 MP success verification

 

 

http://<ManagementPointComptuerName>/sms_mp/.sms_aut?mplist
http://<ManagementPointComptuerName>/sms_mp/.sms_aut?mpcert

-------------------
Thanks,
http://paddymaddy.blogspot.com/

50 steps to deploye XP Sp2 with OSD

 

 

1. Create a network access account, it only need be a domain user and its password should not expire. Add the account to the Computer Client Agent in the Client node under Site Settings
2. Import XP SP2 as an operating system Install Package (Note most common issue here.
3. Add a Distribution point to your new XP SP2 package created in step 1
4. Create the XP SP2 sysprep package in SCCM
5. The Deploy.cab included on the CD was not updated properly for XP SP2 so you must download a new version here.
6. Create a package that points at the extracted CAB file for its source
7. You do not need to create any programs for the package the build task sequence takes care of this
8. Add the package to a DP that can be used during your build
9. Create a package from definition for the Config Mgr Client (a definition is available called "Configuration Manager Client Upgrade" in the create package from definition wizard)
10. Specify always obtain file from source directory
11. Usually here I create a share at \\SCCMSERVER\SCCMClient pointing to \\SCCMSERVER\SMS_XXX\Client where XXX is the site code in order to make it easier for manual installs in the future. Note I also usually grant domain computers read access to the share and directory to prevent permissions problems in the future (Note this last permissions step may no longer be necessary in SCCM but I haven't tested it yet)
12. Update the ccmsetup command line properties accordingly. Extensive information about command line properties on TechNet here.
13. Add the package to a DP that can be used during your build
14. Create a "Build and capture a reference operating system image" task sequence
15. Name the task sequence something appropriate like "Build Windows XP Gold Image"
16. Select a boot image (I suggest x86 as it will run on all platforms, plus you will be booting from PXE so it really doesn't matter)
17. Select the Operating System Package you created in step 1
18. Enter a product key
19. Set the local admin password to blank
20. Join a workgroup
21. Select the Config Mgr client you created in step 4
22. I generally don't install updates in this phase but this is debatable. You must weigh time to deploy if you have to deploy a bunch of updates during deployment time vs. superseded updates and rebuilding your image more often.
23. Don't add any software to the base image
24. Set your image properties
25. Select a location to save the image and make sure you include the full path including the .wim extension
26. Enter an account with rights to write to the share
27. Finish up
28. Change the task sequence to use "Quick Format"
29. Right Click on the Task Sequence and choose Edit
30. Select the "Partition Disk 0″ step
31. Choose properties on the Default (Primary) partition and check the "Quick Format" option
32. Create a collection to which you will advertise the task sequence; I usually use _OSD\Base Builds
33. Advertise the task sequence to the collection you created in step 7 as optional
34. Right click Task sequence and choose advertise, follow the wizard
35. Make sure you select the check box "Make this task sequence available to boot media and PXE"
36. If you are in test and your boundaries are not defined make sure you select "When no local distribution points are available, use remote distribution point"
37. Make sure you completed step 1
38. Select a client to build your base image
39. I suggest using a virtual platform to keep the drivers in the image at a minimum
40. VMWare ESX is not a good candidate as a platform as it uses SCSI disks only to my knowledge. You do not want SCSI Mass storage drivers in your image, use MS Virtual Server / Virtual PC / Hyper-V or VMWare Server / Workstation
41. Ensure that you have the network and mass storage drivers to boot the device on the boot image and in the driver store (If you have to do this in the future you must update the PXE and standard DPs)
42. Add the appropriate boot images (x86 / x64) to the PXE and standard DPs
    1. If you don't see a PXE DP it means you don't have one :), get WDS installed and your PXE Service point
43. Allow the client to boot from PXE
44. If this client previously had an SCCM agent on it you just need to add the client to the collection you created in step 6
45. If this is a new client and SCCM is pre-R2 add the client manually
    1. Add the client by right clicking the Computer Associations node under OSD and choosing "Import Computer Information"
    2. Enter the Name of the computer; I use XPBase
    3. Enter the MAC and or SMBIOS GUID
    4. Add the computer to the collection you created in step 7
46. If you are using SCCM R2 you can enable unknown computer support on the PXE service point but choose wisely; option 10.2 may still be the best choice given the risk of accidentally formatting your CXOs laptop
47. Boot the device up to PXE and choose your task sequence. In less than an hour you should have the start of a great XP Image
50. 
    -------------------
    Thanks,
    http://paddymaddy.blogspot.com/
    

SCCM 2007 Help full topics from Technet

1. Configuration Manager Single Site Planning and Deployment

ü Configuration Manager Supported Configurations

ü Prerequisites for Installing Configuration Manager

ü Configuration Manager Site Naming

ü SMS Provider Overview

ü Configuration Manager Site Database Overview

ü Planning Configuration Manager Boundaries

ü Configuration Manager in Multiple Active Directory Forests

ü Extending the Active Directory Schema for Configuration Manager

ü Configuration Manager and Name Resolution

ü Configuration Manager and Service Location (Site Information and Management Points)

ü Configuration Manager Site Modes

ü Configuration Manager Custom Web Site Overview

ü Configuration Manager Discovery Planning

ü Configuration Manager Site System Planning

ü Configuration Manager Service Principal Name Requirements

ü Configuration Manager and Network Load Balancing Clusters

ü Configuration Manager Security and Privacy Planning

ü Configuration Manager Setup Overview

ü Configuration Manager Post Setup Considerations

ü Configuration Manager Planning and Deployment Flowcharts

ü Configuration Manager Tasks for Planning a Single Site

ü Configuration Manager Tasks for Deploying a Single Site

2. Configuration Manager Multiple Site Planning and Deployment

ü Administering Multi-Site Hierarchies

ü Roaming Between Sites in Different Modes

ü Configuration Manager Site to Site Communications

ü About Data Priorities

ü Administrator Workflow: Configuration Manager Hierarchy Planning and Deployment

ü Configuration Manager Tasks for Planning Multiple Sites

ü Configuration Manager Tasks for Deploying Multiple Sites

3. Configuring Configuration Manager Sites for Best Performance

ü Performance Considerations When Designing Configuration Manager Sites

ü Best Practices for Central and Primary Site Hardware and Software Configuration

ü Performance Configuration Recommendations

ü Expected Server Resource Usage for Configuration Manager Sites

ü Monitoring Site Performance

ü Troubleshooting Configuration Manager Performance

4. Configuration Manager Upgrade and Interoperability Planning and Deployment

ü Planning to Upgrade to Configuration Manager

ü Configuration Manager 2007 Upgrade Checklist

ü Configuration Manager In-Place Upgrade

ü Configuration Manager Side-By-Side Upgrade

ü Upgrading Secondary Sites

ü Configuration Manager Post-Upgrade Considerations

ü Configuration Manager Tasks for Upgrade and Interoperability

ü Configuration Manager Upgrade Flowcharts

ü Configuration Manager Upgrade Administrator Workflows

5. Deploying Configuration Manager Sites to Support Internet-Based Clients

ü Overview of Internet-Based Client Management

ü Provides an overview of Internet-based client management.

ü Prerequisites for Internet-Based Client Management

ü Lists the external and product dependencies for Internet-based client management.

ü Planning for Internet-Based Client Management

ü Provides planning information for deploying a site for Internet-based client management.

ü Configuring Internet-Based Client Management

ü Provides the configuration checklist and tasks to configure a site for Internet-based client management.

6. Deploying Configuration Manager Sites in International and Multi-Language Environments

ü Planning and Deploying Your Multilingual Site Hierarchy

ü Tasks for International and Multi-Language Configuration Manager Clients

7. Configuration Manager Tasks for Decommissioning Sites and Hierarchies

ü How to Remove a Primary Site from a Hierarchy

ü How to Remove a Secondary Site Using the Configuration Manager Console

ü How to Remove a Secondary Site From a Hierarchy

8. Planning and Deploying Clients for Configuration Manager 2007

ü Overview of Configuration Manager Client Deployment

Provides an overview of client deployment in Configuration Manager 2007.

ü Prerequisites for Configuration Manager Client Deployment

Provides information about the necessary prerequisites for client deployment in Configuration Manager 2007.

ü Planning for Configuration Manager Client Deployment

Provides planning information for the client deployment in Configuration Manager 2007.

ü Configuring Configuration Manager Client Deployment

Provides the configuration checklist and tasks to configure client deployment for the site.

ü Tasks for Configuration Manager Client Deployment

Provides a set of tasks to perform client deployment objectives.

ü Troubleshooting Configuration Manager Client Deployment

Provides troubleshooting information for deploying and managing clients in Configuration Manager 2007.

ü Best Practices for Securing Clients

Provides security and privacy information and best practices for client deployment.

ü Technical Reference for Configuration Manager Client Deployment

Provides technical reference information for client deployment.

Here is the chm file can bedownload from Microsoft.
http://www.microsoft.com/downloads/details.aspx?FamilyID=81997356-7f18-48b2-a53a-d6f995a47f35&DisplayLang=en

-------------------
Thanks,
http://paddymaddy.blogspot.com/

SMS Support Webcasts Archive

SMS Support Webcasts Archive

 

 

2004 Webcasts • TechNet Webcast: Managing a Microsoft Windows Server 2003 Network - (Part 3 of 4) December 15, 2004: This webcast is the third in a four-part series that examines key aspects of proactive Windows Server 2003 network management. In the third part we will focus on using SMS to package and deploy software and updates across your network. • TechNet Webcast: Deploying SMS for Server Management December 14, 2004: Ever wonder what is involved in an effective deployment of an SMS infrastructure? In this webcast, we will explore the specific business and technical requirements needed to analyze and deploy SMS for use in the management of a server environment. • TechNet Webcast: Zero Touch Deployment December 9, 2004: Learn to fully automate your desktop deployment. Get guidance on using the latest versions of SMS and Microsoft BizTalk to automate deployment and provisioning. This webcast introduces the Microsoft Business Desktop Deployment (BDD) Enterprise Edition solution. which offers complete guidance for Zero Touch Provisioning using Microsoft BizTalk Server 2004. • TechNet Webcast: Security Patch Management Tools (Part 3) - SMS with the SUS Feature Pack November 22, 2004: In this webcast, we will discuss using SMS and the SUS Feature Pack as patch management tools in your environment and how they fit into a comprehensive patch management strategy. SMS and SUS offer different advantages and benefits to an organization. This webcast will review their different capabilities and how they contribute to a secure infrastructure. • Executive Circle Webcast: What's New with Microsoft's Enterprise Product Roadmap September 29, 2004: This webcast will bring you up to speed on the enterprise software roadmap, highlighting the significant shifts in delivery dates and support policies for Windows Server™ 2003, SQL Server™, Systems Management Server and Security technologies. • TechNet Webcast: Upgrading to SMS 2003 SP1 September 23, 2004: Now that SMS 2003 SP1 has been released, what is the upgrade process? In this webcast, we'll perform an upgrade of an SMS 2003 site to SMS 2003 SP1. • TechNet Webcast: Security Patch Management Tools (Part 3) - SMS with the SUS Feature Pack September 17, 2004: Do you have an effective, comprehensive patch management strategy? Do you know when to use SMS and when to use Software Update Services (SUS)? In this webcast we will discuss using SMS and the SUS Feature Pack as patch management tools in your environment and how they fit into a comprehensive patch management strategy. • TechNet Webcast: Security Patch Management Tools (Part 3) - SMS with the SUS Feature Pack June 23, 2004: This webcast will discuss using SMS and the SUS Feature Pack as patch management tools in your environment and how they fit into a comprehensive patch management strategy. SMS and SUS offer different advantages and benefits to an organization. This webcast will review their different capabilities and how they contribute to a secure infrastructure. • TechNet Webcast: Combining PatchLink with SMS, SUS, and MBSA for Patch and Security Management May 27, 2004: This webcast demonstrates how PatchLink UPDATE works with Microsoft SMS 2003, SUS, and MBSA to enable patch management from a single console for all Windows operating systems as well as non-Windows OS platforms. • TechNet Webcast: Microsoft System Management Server 2003: A Technical Overview May 21, 2004: Whether you have used SMS before or are just thinking about SMS for the first time, this webcast will give you the information you need to plan for an upgrade or adoption of SMS 2003. The session starts by showing the new features of SMS 2003 and goes on to show how SMS 2003 integrates with Network and operating system technologies, such as Active Directory and Windows Management Instrumentation. • TechNet Webcast: Shop Talk Discussion on Patch Management at Microsoft using SMS 2003 May 5, 2004: This webcast tells you how the Microsoft Information and Technology Group (Microsoft's IT department) patches its desktop and server environment using SMS 2003. • TechNet Webcast: Getting Started with Microsoft Systems Management Server (SMS) 2003 March 25, 2004: This webcast shows how features in the new version of SMS 2003 can help you improve the management and security of your IT infrastructure. Agenda items include an overview of the new capabilities in SMS 2003, recommended best practices for deployment, and how to use the new and improved features. • TechNet Webcast: Using SMS 2003 Software Update Management Features March 3, 2004: This webcast discusses the SMS 2003 software update management process, and demonstrates the entire process from installation of this feature to verification that the distributed patch was deployed successfully. • TechNet Webcast: Upgrading SMS 2.0 to SMS 2003 February 4, 2004: This webcast describes guidelines and procedures you can use when upgrading to SMS 2003. It also discusses the differences in architecture, site systems, client deployment, and capabilities between the two versions of SMS, and includes a walkthrough of an upgrade on an SMS 2.0 site. • TechNet Webcast: Introduction to Automated Deployment Services February 3, 2004: This webcast offers a comprehensive overview of ADS and provides details on its architectural design, features, and benefits, as well as examples of customer deployments.

2003 Webcasts • TechNet Webcast: Securing Your Business Enterprise with Patch Management Using SMS 2003 December 9, 2003: This webcast discusses the Patch Management Solution Accelerators using Systems Management Server 2003 to patch an enterprise and the steps to implement process and automation to increase operational efficiency in the enterprise. • TechNet Webcast: Software and Patch Management with Software Update Service, Windows Update and SMS December 5, 2003: This webcast covers installation and configuration of Software Update Services (SUS) and use of Group Policy to configure clients to use SUS for Automatic Updates. Review SMS features and learn how to install and distribute SUS packages for SMS. • TechNet Webcast: Designing a Secure , Reliable, and Usable Patch Management Infrastructure December 2, 2003: Patch management is one of the core tenants of any security policy. This session provides practical advice on designing and deploying an effective and responsive patch management infrastructure with Microsoft tools and technologies. In addition, the Microsoft Solution for Patch management will be introduced and its core operating architecture discussed in depth. • TechNet Webcast: Asset Management in SMS 2003 September 24, 2003: SMS delivers the tools necessary for managing enterprise Windows environments. This webcast discusses how SMS 2003 works with asset management, covering inventory, software metering, and Web-enabled reporting. • Microsoft Executive Circle Webcast: SMS 2003 Early Adopter Program Feedback September 18, 2003: SMS 2003 has been used by about 60 customers and deployed on more than 100,000 desktops for more than a year now. This session gives you an understanding of results from this rigorous evaluation including scalability and reliability information, as well as lessons learned around deploying and operating SMS 2003 in production enterprises. • Microsoft Executive Circle Webcast: Benefits of a Well-Managed Environment September 10, 2003: There is an assortment of technologies on the market to help enterprises manage their investment in Windows services and devices. However, putting them together to create an optimal experience in managing a Windows enterprise is sometimes difficult. This session explains the processes and technologies that you can use to increase your agility and decrease your operational costs on the Windows platform. • Technical Overview of Systems Management Server 2003 July 29, 2003: Tune in for this in-depth discussion about Systems Management Server 2003. Learn about mobile client support, Active Directory integration, software metering, Web reporting and inventory improvements, infrastructure changes, setup, and upgrades. • Upgrading from Systems Management Server 2.0 to 2003 June 17, 2003: Learn the steps necessary to prepare your Systems Management Server (SMS) 2.0 site for an upgrade to SMS 2003.

2002 Webcasts • An Introduction to Software Update Management Using SMS 2.0 August 14, 2002: Learn about the key problems that customers face when they try to deploy security updates (patches) to their Microsoft Windows NT, Microsoft Windows 2000, and Microsoft Windows XP computers.

-------------------
Thanks,
http://paddymaddy.blogspot.com/