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/