Exchange error: [0x80004005-0x80004005-0x000501]

When users were sending emails to a contact group, it would bounce immediately with the following error message:

From: System Administrator
Sent: Monday, August 14, 2017 3:14 PM
Subject: Undeliverable: Email subject

Your message did not reach some or all of the intended recipients.

Subject: Email subject
Sent: 8/14/2017 3:14 PM

The following recipient(s) cannot be reached:

'Recipient 1' on 8/14/2017 3:14 PM
This message could not be sent. Try sending the message again later, or contact your network administrator. The client operation failed. Error is [0x80004005-0x80004005-0x000501].

'Recipient 2' on 8/14/2017 3:14 PM
This message could not be sent. Try sending the message again later, or contact your network administrator. The client operation failed. Error is [0x80004005-0x80004005-0x000501].

The issue was the related to throttling settings, and the distribution list was over the 24-hour limit.

To fix the issue, you can create and apply a new throttling policy to the affected mailboxes:

New-ThrottlingPolicy -Name policyname -RecipientRateLimit Unlimited
Set-Mailbox -Identity username -ThrottlingPolicy policyname

Replace ‘username’, ‘policyname’, and ‘Unlimited’ with the desired names and values.

Set permissions on a service using the ‘subinacl’ command

I needed to grant permissions to a non-administrative domain user to be able to start and stop services. The subinacl command can be used to grant these permissions:

subinacl /service \\ComputerName\ServiceName /grant=[Domain\]Username[=Access]

Here are the available ‘Access’ parameters:

F : Full Control
R : Generic Read
W : Generic Write
X : Generic eXecute
L : Read controL
Q : Query Service Configuration
S : Query Service Status
E : Enumerate Dependent Services
C : Service Change Configuration
T : Start Service
O : Stop Service
P : Pause/Continue Service
I : Interrogate Service
U : Service User-Defined Control Comma

Filtering drivers by computer model in MDT or SCCM

If you want to filter by computer model, first you’ll need to get the computer model name by running the ‘wmic‘ command in a DOS prompt, and then typing: ‘CSProduct Get Name‘. That should return something similar to this:

wmic:root\cli>CSProduct Get Name
HP EliteDesk 800 G1 USDT

Then, you’ll want to add a conditional Inject Drivers command, with the condition being a WMI query for:

SELECT * FROM Win32_ComputerSystem WHERE Model LIKE "%EliteDesk 800 G1%"

Replace the “EliteDesk 800 G1” string with whatever model you want to match. The percents on each side are a typical SQL wildcard, which is why I don’t have to include ‘HP’ or ‘USDT’.

Windows Deployment Failure

When deploying a Windows 7 64-bit image from our deployment server (using Microsoft Deployment Toolkit, or MDT), we would run into an error message after the image had been applied to a workstation:

Windows could not parse or process the unattend answer file [C:\windows\Panther\unattend.xml] for pass [specialize]. A component or setting specified in the answer file does not exist

It turned out that Internet Explorer 10 had been installed. To fix the issue, you need to remove the IEWelcomeMsg entry from the answer file (either by editing unattend.xml manually on the server for the task sequence, or using Windows System Image Manager (WSIM).

This post clued me into the issue.

HP Print Driver Crash when printing to networked printers

I ran into an issue recently where any application would crash when printing to a network printer. Our environment is unique in that we are printing to a Windows print server (using Guest privileges), but users on the network are logging in using the Novell client.

The crash would not happen with generic Microsoft drivers that came with Windows XP, but it would happen with any HP-branded drivers. Our first workaround was just to use PCL or PostScript drivers that closely matched the printer, and hope for the best.

In the end, we found out that when printing with the HP drivers, it would write to a file in the Windows directory called hpmnwun.ini. The contents it would write were:


Fixing the issue was a two step process:

1: Erase the contents of the file
2: Change the NTFS Permissions of the file to make it read-only by all users (even Administrators)

I think this forces the HP drivers to print to the printer in the standard Windows printer sharing way. When the HP drivers detect the Novell client installed, it writes the NWUSERNAME info to the file and must try to print in an ‘NDPS friendly’ way, which causes the application to crash when printing to a standard Windows shared printer and not a NDPS printer.

Synchronizing data between different computers and OS’s with Dropbox

About a week ago I installed Dropbox, and I have to recommend it to anybody who needs to sync their files between machines. I have a group of Macs that I use to sync data between, and I used to use iDisk, but Dropbox is so much quicker that I can’t see myself using iDisk anymore. Also, the syncing between Linux and Mac OS X works great – I haven’t got a chance to test the Windows client yet, but I’m sure it works just as good.

If you sign up with this link, you’ll get an extra 256MB, and so will I.

Printing 3×5 cards on Epson LQ-590 or LQ-300 impact printers

With Windows XP, you can define custom paper sizes (such as 3×5 cards) by doing the following:

Start -> Printers and Faxes -> File -> Server Properties

In this dialog, you can define a 3×5 card. The problem is, with the LQ-590 and LQ-300 drivers, these paper sizes do not show up as options when you try and print. Any paper size below 4 inches in height will disappear from your printing options.

To get around this, install the LQ-570 driver (the one that is built into Windows XP). This driver will let you use a 3×5 sized form.

XP Won’t Run on current Intel-based Macs

The new Intel-based Macs will not run Windows XP, because current versions of Windows do not support the new EFI BIOS that the new Macs use.

x64 versions of Windows and Windows Vista do support EFI, unfortunately Vista won’t be out until the end of 2006 (maybe) and current Macs use 32-bit Intel processors, so they are unable to run the x64 version of Windows XP.

XP Won’t Run on Intel MacBook, iMac