First close your Exchange Management Console (if you have it open) on the Hub Transport server

Exchange Management Shell

Then open up the Exchange Management Shell. It should be in Start – All Programs – Microsoft Exchange Server 2010 – Exchange Management Shell

It should look something like this below.

Now we are going to run the following command.

SetTransportServer -Identity ‘Your Hub Transport Servers Name’ -AntispamAgentsEnabled $true

It should look something like the below, substituting your server name for the mail-server part of course.
SetTransportServer -Identity ‘mail-server’ -AntispamAgentsEnabled $true 

Now when you go back into your Exchange Management Console you will have a couple of new tabs in your Organization Configuration -> Hub Transport and also in your Server Configuration -> Hub Transport both new options are called Anti-Spam and are shown below. Checkout whats in them and I might put up a few additional help blog posts on adding functionality with filtering settings and whatnot at a later stage.

Happy Exchange 2010′ing. Questions in the comments. Cheers

]]> http://www.techhelpblog.com/2012/01/24/enable-built-anti-spam-exchange-2010/feed/ 0 http://www.techhelpblog.com/2011/10/02/wordpress-fatal-error-allowed-memory-size-issue-fix/ http://www.techhelpblog.com/2011/10/02/wordpress-fatal-error-allowed-memory-size-issue-fix/#comments Sat, 01 Oct 2011 14:28:34 +0000 Josh http://www.techhelpblog.com/?p=308 So I have run into this issue with some wordpress sites more often of late, I guess shared hosting servers or similar are tightening their reign on memory allocation? In any case, funnily enough, as I went to post this very post I received the same Fatel error on TechHelp Blog!! So I had to perform my fix to gain access to tell you all how I did it! So this is really only going to work on a LAMP server and even then only on a hosting platform that allows environment variables for php.ini to at least some degree. Basically we are placing a php.ini file in our root directory and referencing it in our .htaccess file. And here’s how.

Edit your .htaccess file in the public_html folder on your website having the issue.

At the very top of the file put in the following
SetEnv PHPRC /home/username/public_html/ <- replace the address with the base address of where you are intending to put the php.ini file we are creating next. Save the file.

Create a new file in the location you assigned in the last step called php.ini ensure it has secure permissions. Please the following text in the php.ini file and save it.

memory_limit = 64M ; Maximum amount of memory a script may consume (64MB)

And that should have your issue resolved!

Questions in the comments, Cheers!

Install the Plugin TinyMCE Advanced from your WP Admin area. Then in it’s main settings page check the box that says “Stop removing the <p> and <br /> tags when saving and show them in the html editor”

Ensure you test this thoroughly as there can be some unwanted side effects, I am yet to see any but be warned .

So the circuit works by using the 10k thermistor as a sensor and creates a reference. The circuit can be calibrated using the 20k trimpot. The PNP transistor is capable of 1A throughput and you can use it to operate a fan, light, or even a relay to then operate a larger fan, pump or whatever you feel like. It can technically run from 10v – 36v however the 1k trimpot may need to be upgraded to prevent damage to the Transistor.

Thermal Switch Circuit using LM741

Here is a board layout I did as a single layer with standard components. Measures 25mm x 39mm. I’ve put up the “overlay” version as twice the size so it can be used as reference and the board itself is looking at the top layer same as the overlay version, so remember if you are doing an iron transfer or similar you will need to mirror it before printing.

Update! – I was playing around with this a few hours ago and wanted to prevent the fan from pulsing when close to the cut-off threshold. IE add in some hysteresis. I simply added a 220K ohm resistor between Pin 3 and 6 which gives it a few degrees of hysteresis. You can have more control over the hysteresis if you would like by putting in something like a 200-500K ohm trimpot between 3 and 6. the 220k ohm resistor gave about 0.5 degree Celsius of hysteresis. IE device triggering on at 45.8 would turn off at 45.3.

Lets start

In the Exchange Management Console click on Server Configuration.  Right-click the server you wish to create a CSR for and choose New Exchange Certificate. see image below

Enter the friendly name for the new cert. Make it relevant to the Server so you will know where the Cert is assigned in the future. the click next.

Next we get the option of selecting a Domain scope or namely if we want a wildcard Certificate. Exchange 2010 does support wildcard certificates however a standard SAN (Subject Alternative Name) Certificate is usually recommended. In this example we will click next and continue with a SAN configuration as this is the most common.

Next you will see the domain/cert configuration for all the different aspects of Exchange that you would like to sign with this digital Certificate. You will be able to configure the names of each service. see image below.

First up we will configure the Client Access server (Outlook Web App) begin this by clicking the little down arrows to the right of the heading and you will see the below.

Enter in your internal exchange server address. here I’ve used internal.domain.com however it would usually be something like servername.domain.local for the internal and the external would be what you call the server from the outside world. IE it’s subdomain name / address.

The next portion is the ActiveSync domain name. I usually always use the same as the external subdomain/address of the server, this simplifies configuration by making it the same as the Outlook Web App address. (external.domain.com). I’ve smudged it out as this screen grab was from a production server.

The next part is the Web Servces, Outlook Anywhere, and Autodiscover. Again here it is best to use the same external address, for ease of configuration and confusion with end users, as the Outlook Web App and server address. For the Autodiscover portion there should be a prefilled area with autodiscover.domain.com, etc.

Lastly I usually configure the Hub Transport server SSL for secure SMTP communication. Use the same external address we have been using all along for ease of configuration. external.domain.com has been my example. here I’ve scrubbed it out as this was from a production server.

Once your happy with the config click next.

The next screen will give you a list to review all of the common names included in the Certificate. Here you can add any additional names. Ensure that the external.domain.com domain name example is selected as the common name, it should be in bold.

Next we configure the Organization details. Substitute your details for those below.

After this process you will be given a Summary of all the information entered to go over. ensure all looks to be in order and click New to create the Certificate Configuration and the exchange CSR to request the actual certificate.

Now you can take your CSR file (called the .req file in this case) and generate a Certificate with a Certificate Signing Authority. The below process will instruct you on the process of installing the Certificate and completing the process. do this by right clicking on the certificate in the Exchange Certificates field and selecting the Complete Pending Request… option.

Next we select the downloaded Signed Certificate. Sometimes your certificate file extension may be .crt as opposed to the Microsoft Default of .cer just worth keeping in mind when using the browse function to navigate to your file.

Once you have selected the file. Choose Complete.

Next we will Assign Services to the Digital Certificate

Now we have a valid Certificate Installed we need to Assign Services to the Digital Certificate before it will be used. do this by right clicking on the installed certificate and selecting Assign Services to Certificate…

Next there will be a list of servers, select the server in question that the cert has been assigned to then click next. After that you will see a list of Services, check the appropriate services and continue by clicking next. see below. You will be prompted to overwrite the existing default certificate and simply click Yes To All to overwrite and install the new cert.

And thats it!

Hope I’ve helped, questions in the comments. Cheers

Basically you just install the 2003 AD support tools. You can download them from here http://go.microsoft.com/fwlink/?LinkId=100114 just download the two files, the msi and cab and then run the msi ignoring the error messages and the replmon tool will be in C:\Program Files (x86)\Support Tools

Hope this helps. Cheers

PS this works with all versions of 2008 including R2, etc.

The server encountered an error while configuring network on ——– Failed to add device ‘Microsoft Synthetic Ethernet Port’.

So the fix, at least for me, was Antivirus exclusions! The box in this case was running AVG enterprise and by adding an exclusion on the virtual machine directory the problem seen above went away, I have since heard of similar issues with other AV apps and also MS Forefront causing the same issues.

Hope this helps

After installing the latest 2010 Exchange server I ran into the usual issue of the OWA (Outlook Web Access) site giving a blank page with a url something like this /owa/auth/logon.aspx?url=https://server.domain.com/owa/&reason=0 .

The cause of this little anoying one is actually a prerequisite of Exchange 2010 and OWA that isn’t picked up as an issue during the install! Never fear there is a simple fix and here it is

• We just need to install the RPC over HTTP Proxy feature by heading to Server Manager – Features – Add Feature then select RPC over HTTP Proxy from the list and continue through the wizard to add the feature!

Presto, problem solved!

You should then be able to reload the OWA URL to your server and get the below!

Questions in the comments

Cheers

<?php
$ip = $_SERVER['REMOTE_ADDR'];
echo “Your IP Address is: ” . $ip;
?>

Here goes. You will notice if you run MMC and try to add the Active Directory Schema Master snap in that it won’t be there! Say what! Microsoft why isn’t it there? in any case here is how to get it back.

1. We need to register the schmmgmt.dll file to get the Active Directory Schema Master snap in to shop up.
open a run window and type “regsvr32 schmmgmt.dll” see below.

2. Once this dll has been registered we need to get a MMC window up and add the snap in.
Open up a Run window again and type “mmc” and click ok. Then click File > Add/Remove Snap-in… as per the below image.

3. Add the now visible Active Directory Schema snap-in. As per the below image. Select the Active Directory Schema snap-in on the left and then click Add followed by Ok.

4. Next we need to Change Active Directory Domain Controller…
Do this by right clicking on Active Directory Schema [server name here] and selecting Change Active Directory Domain Controller… see image below for reference

We then need to ensure that we select the correct “look in this domain” domain in the drop down then click on the server you would like to become the Schema Master and click OK, then confirm the change of selected server.

5. Now we need to right click the Active Directory Schema again and this time select Operations Master…

Then we will see a window like the below one. Here we need to ensure that the bottom greyed out window has the name of the server we just connected to, which is the one that the schema master role will be transferred over to. Once you ensure this is the case you can click Change and approve the change. Once complete close out of this window and the MMC one and job is done

All in all not a painful process at all. But without this snap-in it is a head ache of powershell scripts that I myself haven’t bothered learning. And why would you hey for the rare occasions you might do it and the fact Microsoft included a hidden snap-in that all but does it for you.

Questions in the comments.

Cheers.