njcomputernetworks.com Blog

Event ID: 7023 - The DNS Server - Not enough storage - Win2003 SBS

We’ve been hearing reports that 951748 and 951746 Microsoft Security Updates are causing some problems with the DNS service on Windows 2003 SBS SP1 (possibly SP2). The event ID seen is:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7023
Date: 7/18/2008
Time: 3:12:11 PM
User: N/A
Computer: Serverxyz
Description:
The DNS Server service terminated with the following error:
Not enough storage is available to complete this operation.

The symptom is that the DNS service will no longer start.

In order to repair this situation, uninstall the two MS security updates (in Add\Remove programs): 951748 and 951746 Then reboot the server and the DNS service will function once again.

How to Integrate Dell Toolkit 2.5 Into SCCM 2007 *.WIM File

Hi.. anyone using *.wim files and building Dell servers might want to add the Dell Toolkit into the WIM file. The WIM file 2.0 is based on Windows Vista PE. Here is how to integrate the Dell Toolkit for building servers (carve out RAID sets, edit DRAC configs, etc.)

Note: Dell is developing a tool that will integrate the Dell Toolkit into SCCM 2007, however, it is not available yet. for more information: http://www.dell.com/downloads/global/power/ps3q08-20080328-Microsoft.pdf

Here is a link to the Dell websites article: http://support.dell.com/support/edocs/software/dtk/2_5/UG/dtkugc5.htm

————– Dell document with some added comments ———————————-

Prep:

a. Copy Winpe.wim to temp directory (from AIK). i.e. c:\temp\winpe

b. edit the C:\Dell\Drivers\winpe2.x\VPE_driverinst.bat to install packages needed by SCCM 2007 into the WIM file.

@echo ————————————
@echo ~~4-Add additional customizations
@echo ————————————
REM Add Windows WMI package
%AIKTOOLS%\PETOOLS\peimg /install=WinPE-WMI-Package %WINPEPATH%\mount\Windows

REM ——Joe Additions ——————————————————————–
@echo ##########################################
@echo ~~JOE-SCCM 2007 additional customizations#
@echo ##########################################
%AIKTOOLS%\PETOOLS\peimg /install=WinPE-Scripting-Package %WINPEPATH%\mount\Windows
%AIKTOOLS%\PETOOLS\peimg /install=WinPE-XML-Package %WINPEPATH%\mount\Windows

and some more edits lower in the file:

@echo ———————————————
@echo ~~12-Commit the customization to base image
@echo ———————————————
::Commit Changes to the Standard Image (winpe.wim)

REM ——Joe Additions ——————————————————————–

@echo ##########################################
@echo ~~JOE-SCCM 2007 additional customizations#
@echo ##########################################

%AIKTOOLS%\x86\imagex.exe /unmount /commit %WINPEPATH%\mount\

%AIKTOOLS%\x86\imagex.exe /export %WINPEPATH%\winpe.wim 1 %WINPEPATH%\boot.wim

d. Save the updated VPE_driverinst.bat

DTK provides a script, VPE_driverinst.bat, to pre-install the Dell drivers into a base Windows PE 2.0 image (winpe.wim)
offline. Use the following steps to execute this script:

Open a command prompt on your system and change the directory to the location of VPE_driverinst.bat. For example:

1) Copy the extracted dell toolkit to c:\Dell

2) cd C:\Dell\Drivers\winpe2.x

3) Execute VPE_driverinst.bat with two required arguments and . For example: (Note you might have to run the bat TWO TIMES before it works)

VPE_driverinst.bat

Where is the destination path to create the directory structure for Windows PE 2.0 (winpe.wim file) and is the path to Dell drivers in the extracted DTK toolkit. For example:

VPE_driverinst.bat c:\temp\winpe C:\DELL\DRIVERS

This will pre-install the Dell drivers into winpe.wim.

NOTE: is passed as the destination to the Windows AIK command copype.cmd. The destination folder C:\vistaPE_x86 is created as part of the process, and should not already exist.

4) Copy the customized winpe.wim image to the folder VistaPE_x86\ISO\sources. For example:

Copy c:\vistaPE_x86\winpe.wim c:\vistaPE_X86\ISO\sources\boot.wim

Active Directory

Active Directory was previewed in 1996, released first with Windows 2000 Server edition, and revised to extend functionality and improve administration in Windows Server 2003. Additional improvements were made in both Windows Server 2003 R2 and Windows Server 2008.

Active Directory was called NTDS (NT Directory Service) in older Microsoft documents. This name can still be seen in some AD binaries.

There is a common misconception that Active Directory provides software distribution. Software distribution is run by a separate service that uses additional proprietary schema attributes that work in conjunction with the LDAP protocol. Active Directory does not automate software distribution, but provides a mechanism by which other services can provide software distribution.