 [<a href='function.imagecreatefromstring'>function.imagecreatefromstring</a>]: Empty string or invalid image in <b>/var/www/vhosts/tachytelic.net/httpdocs/wp-includes/media.php</b> on line <b>258</b><br />
<!-- Resize Error: File “/var/www/vhosts/tachytelic.net/httpdocs/wp-content/uploads/” is not an image. -->http://www.tachytelic.net/wp-content/uploads/header-11-resized-image-960x164.jpg)
Archive for Exchange
Updating the RecipientContainer of a dynamic distribution group in Exchange 2007
Posted by: | CommentsAfter moving users to a different organisational unit you may find that you are unable to e-mail them using a dynamic distribution group. If the group was created in powershell you wont be able to edit it in the managment console either. It shows a message saying:
This Dynamic Distribution Group was created with the Exchange Management Shell. You can use the Exchange Managment Shell to modify the filter.
And all of the controls are disabled.
To update the recipient container from the Exchange Management Shell run:
Set-DynamicDistributionGroup -Identity DistributionGroupName -RecipientContainer ‘containername/ouname’
New-ExchangeCertificate Cmdlet Syntax Generator
Posted by: | Comments
I am always forgetting the syntax for the New-ExchangeCertificate cmdlet when I need to do a new certificate request so I decided to write a little bit of javascript to build up the command automatically. Its much easier to copy and paste it from here than work with in it the Exchange 2007 Command Shell.
So just fill in the fields below and the command will be built automatically in the box below. Then just copy into command shell. If required, seperate the “Subject Alternative Names” with commas.
|
Common Name: |
|
| Subject Alternative Names: | |
| Organisation: | |
| Organisational Unit: | |
| Town/City: | |
| County/State: | |
| Country: |
CSR Command:
I am thinking of duplicating this code and writing another post which will generate the commands for the import of the newly generated certificate.
Just been trying to install Exchange 2007 SP1 on a freshly installed Windows 2008 R2 and come up against the following error during the installation of the Mailbox Role:
Mailbox Role
FailedError:
An error occurred. The error code was 3221684229. The message was Access is denied..
Simple fix for this is to run setup.exe in compatibilty mode. I chose Vista SP2 and then the installation went through normally.
But before you go rushing to finish your installation it is worth noting that Exchange 2007 SP2 will not be supported on Windows 2008 R2, and therefore you may want to reconsider doing the installation at all! Read here:
http://msexchangeteam.com/archive/2009/09/21/452567.aspx
I flattened the installation and went back to Windows 2008 Standard.
Update: Microsoft have changed the policy to support Exchange 2007 on Windows 2008 r2:
Malware/Virus delivered through fake e-mail from UPS
Posted by: | CommentsI have had several incidents this week of customer systems being infected by executables attached to e-mails appearing to be from UPS.
Looking around the blogs, these e-mails seem to be having a higher than normal infection rate. It is time consuming to get rid of and makes the infected machines unusable and creates a huge number of network connections.
The exact subject line of the email’s that have been received is:
UPS Tracking Number 5440074870
Attached to the e-mail is a zip file containing an executable which when executed installs "XP Security Center".
Much more information about the detail of the actual email can be found on the Trend Malware Blog. The worrying thing about this e-mail is that both of the machines that it infected have their e-mail filtered by very well known external 3rd party mail systems, then have virus scanning on their own Exchange servers and finally on their desktop machines. At the moment this e-mail is still slipping through the net.
This virus does a LOT of clever things to prevent you getting rid of it. I noticed that when trying to run Autoruns from Sysinternals that it just would not work. Renaming the autoruns executable allows it to run. It also stops you being able to install/download Windows Defender, disables system restore, removes the system tools program group amongst other things.
Not a very sophisticated solution but for now I have edited the Exchange IMF custom weighting file on customer systems to ensure that messages with "UPS Tracking" in the subject line are never delivered to the recipients and definitely classed as spam.
I had written a separate post on how to remove the virus manually, but at the moment I am still monitoring the infected machines to ensure they are completely clean.