Just some handy blogs =)

Some nice blogs 🙂

The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis

System Center Configuration Manager 2007 client may not install during an OSD Task Sequence in a Refresh scenario

The Task Sequence fails.

Examining the SMSTS.log reveals the following error:

Installing SMS client OSDSetupHook
Clearing existing client configuration. OSDSetupHook
Cleaning existing client certificates from SMS certificate store OSDSetupHook
Restoring SMS client identity. OSDSetupHook
Could not import certificate to temporary store (0x80092024) OSDSetupHook
Failed to restore client certificates. Code 0x80092024. OSDSetupHook
Failed to restore SMS client identity. Code 0x80092024. OSDSetupHook
Failed to install SMS Client (0x80092024) OSDSetupHook
Failed to execute task sequence (0x80092024) OSDSetupHook

Examining the ccmsetup.log and client.msi.log reveals that the logs either do not exist or have not updated since the ConfigMgr 2007 client was originally installed on the reference image.

For all the details as to the cause and how to resolve it see the following Knowledge Base article:

KB2028442 – System Center Configuration Manager 2007 client may not install during an OSD Task Sequence in a Refresh scenario

The System Center Service Manager 2010 Console fails to launch on Windows 7 x86 (32 bit)

On a system that is running Windows 7 x86 (32 bit) the System Center Service Manager 2010 Console fails to launch.  Additionally, The following event is logged in the Application log:

Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Description:
Faulting application Microsoft.EnterpriseManagement.ServiceManager.UI.Console.exe, version version number , faulting module igdumd32.dll, version version number , fault address address.

The system also has one of the following Intel GPU chipsets:

  • Intel Q43 Express Chipset
  • Intel Q45 Express Chipset
  • Mobile Intel 4 Series Express Chipset Family

For the latest status of this issue please see the following Knowledge Base article:

KB2278267 – On a system that is running Windows 7 x86 (32 bit) the System Center Service Manager 2010 Console fails to launch

Microsoft Configuration Manager 2007 setup on Windows Server 2008 failes to proceed

Microsoft Configuration Manager 2007 setup on Windows Server 2008 may fail to proceed with the following error message:

Web-based Distributed Authoring and Versioning (WebDAV) is required for the management point and distribution point site system roles. If you have selected to install a site role requiring WebDAV, and it is not enabled, this rule will fail. Web-based Distributed Authoring and Versioning (WebDAV) is not enabled and/or IIS 6 WMI compatibility component for IIS7 is not installed on the computer specified for management point installation or setup was unable to verify remote IIS settings because IIS common components were not installed on the site server computer. ConfigMgr requires WebDAV to be installed and enabled in Internet Information Services (IIS) for management point site systems. Setup cannot continue.

This occurs even if the steps from How to Configure Windows Server 2008 for Site Systems article has been followed.

To resolve this issue and allow ConfigMgr 2007 setup to complete follow the steps below:

  1. Click on Start, click on All Programs, Click on Administrative Tools and then click on Internet Information Services (IIS) Manager.
  2. Highlight the entry on the left-hand pane for your servername (SERVERNAME (DOMAINuser)).
  3. Double-click on WebDAV Authoring Rules.
  4. Delete any rules that appear.
  5. Highlight your Default Web Site (or ConfigMgr 2007 web site) and edit the WebDAV settings at that level as explained in this article:  http://technet.microsoft.com/en-us/library/cc431377.aspx

For all the details and the latest version of this document please see the following new Knowledge Base article:

KB2378924 –  System Center Configuration Manager 2007 prerequisites checker reports WebDAV settings are incorrect


Import-Mailbox fails occasionally

To import data from a .pst file, you must run the Import-Mailbox cmdlet from a 32-bit computer that has the following installed;

# 32-bit version of the Exchange management tools (download link : http://www.microsoft.com/downloads/details.aspx?FamilyId=6BE38633-7248-4532-929B-76E9C677E802&displaylang=en )
# Microsoft Office Outlook 2003 Service Pack 2 (SP2) or later versions

a few good articles ;
http://msexchangeteam.com/archive/2007/04/13/437745.aspx
http://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/exchange-2007-sp1-mailbox-management-part1.html

Check info:

1.      Please add parameter “-verbose” at the end of the Import-Mailbox and reproduce the issue, which can give us more info to narrow down the cause
2.      Is there any related error or warning event in the application log on the both client and exchange server?
3.    Make sure the mailboxes has been exported on the same version Outlook as you use on your import machine

Troubleshooting:

1. Please make sure that outlook and any MAPI connections are closed prior to running the Import-Mailbox
2. Use outlook 2003 instead of outlook 2007 on the workstation if outlook is to remain open during the process
3. If using outlook 2007, ensure that outlook is logged in using the same credentials as the Import-Mailbox PowerShell window
4. Do not launch PowerShell under the “Run As” method. Instead log into Windows as the desired account with permission to the mailbox and launch PowerShell normally
5. If running Windows XP and getting the error: “PowerShell.EXE has encountered a problem and needs to close.  We are sorry for the inconvenience” – Make sure it dosent get connected to a READ-ONLY domain controller. It will not show up in the log of a XP computer, but trying the same on a Windows 7 and it will show that it connects several times during the import, but if it at one point hits a RODC, Powershell will crash. easy solution just add static entries for the domain to your hosts file.

ConfigMgr 2007 Maintenance Tasks

Common Daily Maintenance Tasks

Some common daily maintenance tasks are listed below:

  • Verify that predefined maintenance tasks scheduled to run daily are running successfully.
  • Check Configuration Manager 2007 site database status.
  • Check site server status.
  • Check Configuration Manager 2007 site system inboxes for backlogs.
  • Check site systems status.
  • Check client status.
  • Check the operating system event logs on site systems.
  • Check the SQL Server error log.
  • Check system performance.

Common Weekly Maintenance Tasks

Some common weekly maintenance tasks are listed below:

  • Verify that predefined maintenance tasks scheduled to run weekly are running successfully.
  • Delete unnecessary files from site systems.
  • Produce and distribute end-user reports if required.
  • Back up application, security, and system event logs and clear them.
  • Check the site database size and verify that there is enough available disk space on the site database server to allow the site database to grow.
  • Perform SQL Server database maintenance on the site database according to your SQL Server maintenance plan.
  • Check available disk space on all site systems.
  • Run disk defragmentation tools on all site systems.

Common Periodic Maintenance Tasks

Some common periodic maintenance tasks are listed below:

  • Review the security plan for any needed changes.
  • Change accounts and passwords if necessary according to your security plan.
  • Review the maintenance plan to verify that scheduled maintenance tasks are scheduled properly and effectively depending on configured site settings.
  • Review the Configuration Manager 2007 hierarchy design for any needed changes.
  • Check network performance to ensure changes have not been made that affect site operations.
  • Verify Active Directory settings affecting site operations have not changed. For example, you should ensure that subnets assigned to Active Directory sites used as boundaries for a Configuration Manager 2007 site have not changed.
  • Review the disaster recovery plan for any needed changes.
  • Perform a site recovery according to the disaster recovery plan in a test lab using a backup copy of the most recent backup snapshot created by the Backup ConfigMgr Site Server maintenance task.
  • Check hardware for any errors or hardware updates available.
  • Check overall health of site.

Delete all packages from DP

Delete all packages? This should do it.

(replace MyLABServer) with site servername, and LAB with site code (in powershell 2.0):

$pkgs = gwmi sms_package -computer MyLabServer -namespace rootsmssite_LAB

$pkgs | % {$_.Delete()}

This does all classic packages.  If you want to do others, you’ll have to change the class – sms_DriverPackage, sms_ImagePackage, etc…

Disabling Task Sequence Notification Balloons in ConfigMgr 2007

Notification balloons seem to be a frequent topic of feedback from customers. There may pop up too often, or only certain users should get them, or the timing isn’t configurable enough.

Lately we’ve had multiple customers asking for a very specific feature. The AdminUI for SCCM provides the ability to disable notification balloons for normal Software Distribution packages, but not for Task Sequences.

While there are currently no plans to modify the AdminUI to add this ability, all of the necessary logic is already present in the client code; you just have to go out of your way to enable it. If the ability to disable notification balloons for Task Sequences is something that would be beneficial in your environment then you can use the script below to automate the process.

The example below needs to be run on a site server by a user who has sufficient permissions in SCCM to modify the Task Sequences in question. Running the example with no command line arguments will provide usage instructions.

There is no guarantee or warranty associated with this example. Make sure you test any utility before using it in a production environment; and, as always, make sure that you are running frequent backups and that you test the restoration procedure on a regular basis to ensure that the backups are valid.

========

Option Explicit On

If WScript.Arguments.Count < 1 Then
WScript.Echo “Usage:”
WScript.Echo ”    DisableTSNotification.vbs -all”
WScript.Echo ”    DisableTSNotification.vbs PackageID [PackageID]…”
WScript.Quit
End If

Dim strComputer
Dim siteCode
Dim objWMIService
Dim colItems
Dim objItem
Dim packageID
Dim itemFound
Dim numPackages
Dim numUpdated

strComputer = “.”
siteCode=GetSiteCode()
Set objWMIService = GetObject(“winmgmts://” & strComputer & “/root/sms/site_” & siteCode)

If StrComp(UCase(WScript.Arguments.Item(0)), “-ALL”, 1) = 0 Then
numPackages = 0
numUpdated = 0
Set colItems = objWMIService.ExecQuery(“SELECT * FROM SMS_TaskSequencePackage”, “WQL”, 32)
For Each objItem in colItems
If (objItem.ProgramFlags AND 1024) = 0 Then
objItem.ProgramFlags = objItem.ProgramFlags OR 1024
objItem.Put_
numUpdated = numUpdated + 1
WScript.Echo “Modified package ” & objItem.PackageID
End If
numPackages = numPackages + 1
Next
WScript.Echo “Updated ” & numUpdated & ” of ” & numPackages & ” packages”
Else
For Each packageID in WScript.Arguments
Set colItems = objWMIService.ExecQuery(“SELECT * FROM SMS_TaskSequencePackage WHERE PackageID='” & packageID & “‘”, “WQL”, 32)
itemFound = false
For Each objItem in colItems
If (objItem.ProgramFlags AND 1024) = 0 Then
objItem.ProgramFlags = objItem.ProgramFlags OR 1024
objItem.Put_
WScript.Echo “Modified package ” & objItem.PackageID
Else
WScript.Echo “No need to update package ” & objItem.PackageID
End If
itemFound = true
Next
If itemFound = false Then
WScript.Echo “ERROR: Package ” & packageID & ” was not found on this server”
End If
Next
End If

Function GetSiteCode()
Dim objSWbemLocator
Dim objSWbemServices
Dim ProviderLocation
Dim Location
Dim strSiteCode

objSWbemLocator = CreateObject(“WbemScripting.SWbemLocator”)
objSWbemServices = objSWbemLocator.ConnectServer(“.”, “rootsms”)
ProviderLocation = objSWbemServices.InstancesOf(“SMS_ProviderLocation”)

For Each Location In ProviderLocation
If Location.ProviderForLocalSite = True Then
strSiteCode = Location.SiteCode
End If
Next

GetSiteCode = strSiteCode
End Function

========