Use Existing WSUS to Patch Client during ConfigMgr OSD Task Sequence

Usually when I go onsite to clients for OSD related projects, once in a while come across those that do not want to adapt to using the Software Update Point (SUP). These clients want the capability for integrating the Software Update process in the Build and Capture as well as the Deployment Task Sequences without SUP.

This is easy to do if you have the MDT 2010 Toolkit packaged.

In the Task Sequence for the Build and Capture (of the Deployment TS)

1. Add the MDT Task Use Toolkit Package

Figure 1

2. Add the task Set Task Sequence Variable. Set the WSUSServer variable to the corporate WSUS.

Figure 2

3. Add the task Run Command Line. Enter the command line as shown below (Figure 3).

Figure 3

Installation Prerequisite Check fails on Short File Name (8.3) Support (Site System)

Issue:

When installing System Center Configuration Manager 2007 (full or console), the installation prerequisite check may fail on the Short File Name check and will display the error as below (figure 1)

Figure 1

Description

Setup either could not verify that short file name (8.3) support is enabled on the computer specified for site system installation or the server could not be contacted to determine short file name support information. No further prerequisite checking rules can be evaluated on the specified system. Setup cannot continue.

Cause

This is usually the case when 8.3 name creation has been disabled via GPO or the registry [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\NtfsDisable8dot3NameCreation=1].

Desktop (and Server) administrators do this to help performance when accessing NTFS. Per the MS KB (http://support.microsoft.com/kb/121007), allowing 8.3 file names and directories ‘may’ decrease directory enumeration performance.

Resolution

I am not 100% on why the ConfigMgr setup is checking for this where is requires it (unable to find the answer but have not been aggressively looking either). To get around this, run the following command on Windows XP, Vista or 7 in elevated mode:

fsutil.exe behavior set disable8dot3 0

Run the Prerequisite check again and it should be successful

Figure 2


 

ConfigMgr Report for Dell BIOS Upgrades

Using a Microsoft SCCM Web Report (SQL query), Dell models and corresponding BIOS revisions in your environment can be determined. This report can be helpful for gauging the scope of your targets:

SELECT CompSys.Manufacturer0 as ‘OEM’, CompSys.model0 as ‘Model’,BIOS.SMBIOSBIOSVERSION0 as ‘BIOSVersion’, COUNT(Sys.Resourceid) AS ‘TotalSystems’
FROM V_R_System as Sys
LEFT JOIN V_GS_PC_BIOS as BIOS on Sys.resourceid = BIOS.resourceid
LEFT JOIN V_GS_COMPUTER_SYSTEM as CompSys on Sys.resourceid = CompSys.resourceid
WHERE

CompSys.Manufacturer0 LIKE ‘%dell%’
AND (CompSys.Model0 LIKE ‘%optiplex%’
OR CompSys.Model0 LIKE ‘%latitude%’
OR CompSys.Model0 LIKE ‘%precision%’)

GROUP BY CompSys.Manufacturer0,CompSys.model0, BIOS.SMBIOSBIOSVersion0
ORDER BY CompSys.Model0, BIOS.SMBIOSBIOSVersion0

 

Reference: http://www.delltechcenter.com/page/Dell+BIOS+Upgrades+for+Enterprise+Clients+with+Microsoft+System+Center+Configuration+Manager+2007

Error “The WebDAV server extension is either not installed or not configured properly” in Configuration Manager 2007 – The Configuration Manager Support Team Blog – Site Home – TechNet Blogs

Error “The WebDAV server extension is either not installed or not configured properly” in Configuration Manager 2007 – The Configuration Manager Support Team Blog – Site Home – TechNet Blogs

via Error “The WebDAV server extension is either not installed or not configured properly” in Configuration Manager 2007 – The Configuration Manager Support Team Blog – Site Home – TechNet Blogs.

A “Set Network Location” dialog box appears when you first log on to a domain-joined Windows 7-based client computer

If you get a prompt to Set Network Location (See Figure 1) in Windows 7 on a domain-joined computer, there is a hotfix from MS to resolve this issue.

http://support.microsoft.com/kb/2028749/en-us

Package the hotfix and deploy as a Task in the OSD or MDT Task Sequence as part of the Windows 7 deployment.

Figure 1