We recently implemented a new optical storage system using a software package that runs on Windows.  The particular machine that is used to host this application gradually had problems accessing the optical storage (which is essentially a NAS device) and would frequently pop the title message: Insufficient system resources exist to complete the required service. 

I thought this was a bit odd, considering the machine has 16GB of RAM, Dual Quad Core processors, and at fairly large amount of storage.  We kept thinking that there must be a driver issue, or some issue with the software, or even an issue with the optical storage.

I have no way to prove it, because I couldn't ever tell for sure exactly how the system go to the point of not being functional, but the last thing I tried APPEARS to have worked...

I took out the /3GB switch in the boot.ini. 

That was 3 days ago and the system hasn't had the issue since, even though it had gotten to the point where it was happening several times a day.  The thing that tipped me toward this as a possible solution was the fact that everything I read said that this was likely caused by a memory leak, but we didn't seem to have memory issues (at least when we could get into task manager there didn't seem to be much activity) and when I came across this post...  I took a chance and it seems to have fixed the problem for now.

I use DPM to backup a few servers, in a pilot group, and I was trying to add one to a protection group.  I kept getting this error every time I tried to modify the protection group to add another server:

Modify protection group: *Protection Group Name* failed:
Error 360: The operation failed due to a virtual disk service error
Error details: Unknown error (0x80042420)
Recommended action: Retry the operation.

I couldn't figure out the problem until I saw a post on this that mentioned there could be a problem using RDP.  Then I remembered that I can never do disk configuration unless I use a console session.  In order to configure disks it seems you have to be in "Session 0".  If you have to do this remotely, using "mstsc /console" for XP or 2003, or "mstsc /admin" for Vista will put you in "Session 0" just as if you were sitting at the console.

If you are trying to free up space on your system drive you may run across a very large  log file in the system32\wbem\logs folder:

SYMPTOMS

When you use Windows Management Instrumentation (WMI) and you configure it to log all events on your Microsoft Windows Server 2003-based computer or Microsoft Windows XP-based computer for quick analysis and troubleshooting of problems, the file size of both the Framework.log and the Framework.lo_ files may be greater than what you configured for them.

The Framework.log file grows larger than 64 KB when you use WMI on a Windows Server 2003 or Windows XP computer

I am responsible for keeping a number of machines (around 900 or so) up to date with all the latest Windows Updates.  Recently I noticed that a number (around 15 or so that I am sure of) weren't installing particular updates.  I have seen this in the past, but the particular updates that wouldn't apply weren't of real concern to me, so I didn't really investigate.  The latest updates were of concern though so I started looking into it.  Here are the errors that I am getting:

Description:
Installation Failure: Windows failed to install the following update with error 0x80070643: Visual Studio 2005 Service Pack 1.

Description:
The installation of C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ZNWF10\VS80sp1-KB926601-X86-ENU.msp is not permitted due to an error in software restriction policy processing. The object cannot be trusted.

As you can see, this particular update is for Visual Studio Service Pack 1.  After a little digging, I found this:

http://support.installshield.com/kb/view.asp?articleid=Q111207

It basically says that there is a problem with the way the local security policy is configured.  When I looked, it appeared that the local security Software Restrictions Policy wasn't configured.  I "added" a policy and put the dot in the "All users except local administrators".  After that the install ran fine.

 I came across Ben Armstrong's Blog today while doing a little searching.  He has some good stuff about Microsoft Virtual Server on there and one of the things he posted on has to do with a calculator to figure out how to configure your Virtual environment.  It doesn't take much to figure out that Data Center Edition may actually be worth paying for when you use multi-core processors and pack a lot of VMs on one host.

Windows Server Virtualization Calculator

I do not know how I missed this one, but this is a very cool tool.  The Windows Server Virtualization Calculator allows you to specify how many virtual machines you will be running, on a given set of hardware, and it will show you all of your licensing options for buying Windows Server.  This way you can quickly determine what the best option is for your environment.

Virtual PC Guy's WebLog : Windows Server Virtualization Calculator

I have had a few machines that occasionally have strange color combinations and you can't see the logon box to view what you are typing.  I finally put the right words in the search to come up with the answer: 

SYMPTOMS

After you press CTRL+ALT+DELETE to log on to a Microsoft Windows Server 2003-based computer, the logon screen turns black. Although you cannot see what you are typing, you can successfully log on to the Windows Server 2003-based computer. Then, after you successfully log on, the screen becomes visible.
Note This symptom may occur on both the terminal server sessions and the local console. Additionally, this symptom occurs even if you start the computer in Safe mode.

The logon screen turns black after you press CTRL+ALT+DELETE to log on to a Microsoft Windows Server 2003-based computer

Windows cannot access the specified device, path, or file.  You may not have the appropriate permissions to access the item.

OR you may just need to removed Internet Explorer Enhanced Security Configuration.  I haven't ever like it.  This is just one more reason.

So, I was thinking that I would write a script to transfer some DHCP scopes from one machine to another.  Well, wouldn't you know...  there is already a tool to do that, and I didn't even have to install software, just read a little article...

http://www.geekadmin.com/?p=13

I have Windows Server 2003.  So here is the pertinant part for me:

Use this command to export all scopes from the source machine:

netsh dhcp server export C:\dhcp.txt all

Install the dhcp server on the new machine and run this import command:

netsh dhcp server import C:\dhcp.txt all

After that authorize the dhcp server and that´s it!

Quick and easy.

I wasn't familiar with how to get a website to repsond without the “www” in front, and when I went to do searches on it, I wasn't too happy with the results.  So, I am creating this entry just to remind me how to do this simple little task.

To get a website to respond to the “domain.com” and the “www.domain.com”, using Windows 2003 Server for DNS and for IIS, the following are the steps to take:

1.  add a host header for “domain.com” and “www.domain.com” in IIS.

2.  add an “A” record for “domain.com” and “www.domain.com” in DNS.  (Note:  You can use an Alias(CNAME) for the “www” entry instead of a Host(A) record, but you have to enter an A record for “domian.com”.)

If you have a number of DHCP reservations or scopes, 87 specifically, you might have a problem opening the MMC snap-in.  It is ok if you have 86 or 88.  Apparently there is an “error 87” and if you have 87 reservations or 87 scopes the snap-in gets confused.  To fix it, you can call Microsoft for the Hotfix, wait for SP2 for Server 2003, or just use the command line to add a nother reservation or scope.  For more information, see the KB article below:

http://support.microsoft.com/Default.aspx?kbid=902954

PROBLEM: Users unable to logon to W2k3 TS. There are 4 TS in a Citrix farm and once the problem happens the particular users can never logon. This issue is random and happens to only some users.

Error: Winlogon.exe - Instruction “0x75998902” Referenced memory at “0x0151036c”.  The memory could not be “read“.

The issue was fixed by Resetting the browser settings by right-clicking on "User Configuration/Windows Settings/Internet explorer maintenance" in Group Policy.

Can't delete a user profile in Windows?  Try running this utility.  It runs as a service that removes hooks in the registry that fail to close automatically when a user logs off.

Do you really need that license logging service?  Doesn't look that way...

License Logging Service (LLS) is a tool that was originally designed to help customers manage licenses for Microsoft server products that are licensed in the Server Client Access License (CAL) model. LLS was introduced with Windows NT Server 3.51. By default, LLS is disabled in Windows Server 2003. Because of original design constraints and evolving license terms and conditions, LLS cannot provide an accurate view of the total number of CALs that are purchased as compared to the total number of CALs that are used on a single server or across the enterprise. The CALs that are reported by LLS may conflict with the interpretation of the End User License Agreement (EULA) and with Product Usage Rights (PUR). LLS will not be included in future versions of the Windows operating system.