It appears that the Queue needs at least 4G of free disk space for email to be delivered so: FREE up disk space.

What’s Back Pressure?
In Exchange Server 2007, the Transport service monitors system resources such as disk space and memory on Transport servers (the Hub Transport and the Edge Transport servers), and stops message submission if it is running low on these resources. It continues to deliver existing messages in the queue. When resource utilization returns to normal, it resumes message submission. The feature is called Back Pressure.

Changes to Back Pressure settings in Exchange Server 2007 SP1

The Back Pressure settings in Exchange Server 2007 RTM stop inbound mailflow if free disk space is below 4 Gigs. This static threshold has been lowered in SP1 to a more realistic 500 Mb.

The Resolution
Many configuration options for transport servers are saved in an XML file named EdgeTransport.exe.config (same file name on both Edge and Hub Transport servers) located in \Exchange Server\Bin\. You can edit the file to disable Back Pressure, or modify the parameters to more accurately define what’s high utilization for your deployment or server configurations, as explained in the above docs.

Another resolution, and the one I used in this case, was to move the Queue database to another volume with ample of free space, using the following procedure:
Add the following key in the section in EdgeTransport.exe.config:

Restart the MSExchangeTransport service, and message submission resumes

The Backup Exec System Logon Account (SLA) is created on installation of Backup Exec. When the SLA is created, the username and password match the credentials provided during install for the Backup Exec Services credentials. The owner of the SLA is the Windows user that installed Backup Exec and is a common account by default. Common accounts are shared accounts that can be accessed by all users.

The Backup Exec System Logon Account may have access to most or all of the resources since it contains the Backup Exec Services credentials. In order to make Backup Exec more secure, the SLA can be changed to be a restricted account or can be deleted.

However, if the SLA is deleted, the jobs in which it is used may fail. If the SLA is deleted, it can be recreated by performing the steps given below:

1. Select the Network | Logon Accounts menu option. The Logon Account Management dialog box will appear (Figure 1).

Figure 1

2. Click on the System Account button on the right which will bring up the figure given below (Figure 2)

Figure 2

3. In the Edit Logon Credentials screen, enter the User name in the format <domain name>\<user name>

4. Select the This is my default Logon account check box and click OK

5. This will create the System Logon Account as shown below (Figure 3)

Figure 3

control ncpa.cpl Network Settings
control desk.cpl Display Settings

Then launch “VMWare Tools.msi” through the command prompt.

Thanks as well to http://www.petri.co.il/installing-vmware-additions-on-windows-server-2008-server-core-installations.htm

Found this Microsoft Kb article to fix it it has now been resolved.

http://support.microsoft.com/kb/932513

Found this very useful: http://support.microsoft.com/kb/119493

H-Node is the best as clienst will check with WINS Server database prior to any B-node (broadcast) This means broadcast is a last resort when trying to find resources etc on the network. Remember that we all love DNS though as it is the key to Microsoft Active Directory Functioning

1) This installs printer quietly
rundll32 printui.dll,PrintUIEntry /in /q /n\\servername\printername

2) This deletes the networked printer from the machine being logged onto, and does so quietly.
rundll32 printui.dll,PrintUIEntry /dn /q /n\\servename\printername

3) This Sets the default printer
rundll32 printui.dll,PrintUIEntry /y /n\\servername\printername

No local system state backup but had one AD machine with FSMO’s still online. The AD server that was offline had critical files that needed to be accessed. The server would loop in DSRM and try and repair the database but HAD NO JOY here.
The only solution was http://support.microsoft.com/kb/332199/

After a single registry change the domain controller sees himself as a member server, was able to login to the machine and rejoin the domain successfully. Only cleanup was to rsynch Dfs replication again.

Found this excellent post that resolved this issue straight away.
http://www.shudnow.net/2007/08/10/outlook-2007-certificate-error/