Wednesday, March 31, 2010

How to configure anti-spam agents Exchange 2007

Link HERE!

By default,  only the Journaling and Transport Rule agents are installed on the Hub Transport server role. The Anti-Spam Agent must be installed and enabled for you to use the associated transport feature. Only the agents that provide the messaging features that are designed to be deployed inside the organization are installed by default. Agents that are not installed are designed for use in the boundary network on a computer that has the Edge Transport server role installed. To view the agent configuration, run the Get-TransportAgent command in the Exchange Management Shell.

You can install the anti-spam agents on the Hub Transport server role by using the provided Install-AntiSpamAgents.ps1 script. The script is located in the %programfiles%\Microsoft\Exchange Server\Scripts folder. After you run this script, all of the anti-spam agents are installed and enabled, and the Anti-spam tab is available in the Exchange Management Console.

Open Exchange Management Shell
Set-Location "c:\program files\Microsoft\exchange server\scripts"
./install-AntispamAgents.ps1
Restart-Service MSExchangeTransport

Now, go do a Microsoft Update! This will ensure that you're running with the most recent Anti-Spam Filter Updates.

OK - back to Exchange Management Shell
get-TransportConfig

- if you'vge already configured your Intern SMTP Servers to include all of your SMTP servers that this server is going to talk to, then you're good.
- if not, then do the following:
Set-TransportConfig -InternalSMTPServers 10.0.1.10,10.0.1.11

Of course, use the IPs of your actual SMTP servers. :P

NOTE:
For all anti-spam features to work correctly, you must have at least one IP address of an internal SMTP server set on the InternalSMTPServers parameter on the Set-TransportConfig cmdlet. If the Hub Transport server on which you're running the anti-spam features is the only SMTP server in your organization, enter the IP address of that computer.


Of course, use the IPs of your actual SMTP servers. :P

Done

Tuesday, March 30, 2010

Exchange 2007 - sending out 25 blocked somehow?

Since, I'm using an ISP that blocks incoming ports like 80 and 25, etc., I have to work things a little differently. A friend of mine has a small datacenter and he's allowed me to use his SMTP server as a relay as well as his ISA server for proxying. So, for OWA, my ISA rule is pretty much a default Exchange OWA rule out-of-the-box with the only exception being that it's bridged on the back of the rule to port 81 on my router. Then my router forwards all port 81 traffic to my Exchange server.

Now, for some reason, my ISP also blocks port 25 in and out. Ugh,... I know... a total P.I.T.A.!!!

So, what do I do?

I run all my email through my buddy's SMTP server and Exchange via not just port 25 but also port 26. So, his router forwards all traffic from port 25 to 26 to his SMTP server (just a basic SMTP server and not an Exchange server).

So, as long as your recieving smtp server (in my case, my friend's SMTP server out there on the internet) is configured to recieve from you and it's an smtp server you control outside your network, you can fix this issue.

First - make sure your external smtp server can recieve on both port 25 and 26. And that it will allow relay of your public IP along with the domain name your using.

Then in your exchange server, set your send connector's smart-host to the public ip of that smtp server out there.

There isn't an option in the Exchange MMC to use another port other than 25. So, we will need to use the exchange shell command below:
set-sendconnector -identity "yourwackyconnectorname" -port 26

This will allow your exchange box to send your emails out on port 26 instead of port 25

Tuesday, March 23, 2010

Windows Installer CleanUp Utility (Office 2000, Office XP, or Office 2003)

When you are working on your computer and installing a new program, the installation suddenly fails. Now you are left with a partly installed program. You try to install the program again, but you are unsuccessful. Or, maybe you have problems trying to remove an old program because the installation files are corrupted.

Do not worry. Windows Installer CleanUp Utility might be able to help. You can use the utility to remove installation information for programs that were installed by using Windows Installer. Be aware that Windows Installer CleanUp Utility will not remove the actual program from your computer. However, it will remove the installation files so that you can start the installation, upgrade, or uninstall over.

Tuesday, March 16, 2010

How to make FLV files play in IIS site

how to make FLV files play in IIS site:

  • Open IIS site, Properties

  • HTTP Headers tab

  • Click MIME Types

  • Enter extension: .flv

  • MIME Type: video/x-flv

Friday, March 12, 2010

MS IT 2.0 Recycle Bin Install steps


  1. Run RecycleBinInstaller.msi

  2. Welcome to the SharePoint Portal Server Recycle Bin Setup Wizard – click Next

  3. Recycle Bin Folder location – C:\SPS_RecycleBin

    1. Log File location – C:\SPS_RecycleBin_Logs\LogFile.txt

    2. Action Log File location – C:\SPS_RecycleBin_Logs\ActionLog.txt

    3. Click Next








Note: The RecycleFolder location in which to store deleted Site Collection information must be configured to allow Read/Write permissions to all Authenticated Users.

  1. Select Installation Folder:

    1. Leave the default folder location.

    2. Select Everyone for the installation option.

    3. Click Next



  2. Confirm Installation – click Next

  3. Installation Complete – click Close


Note: SharePoint Portal Server Recycle Bin will create a Registry entry for HKLM\SOFTWARE\Microsoft\IT\SharePoint Portal Extensions\Recycle Bin\.

  1. Open IIS Manager and navigate to the Web Service Extensions

  2. Right-click Web Service Extensions and select Add a new Web service extension…

  3. Extension name – enter RecycleBinISAPI – click Add


10.  Path to file – enter C:\Program Files\Microsoft IT\SharePoint Portal Server Recycle Bin\RecycleBinISAPI.dll

  1. click OK


11.   Click Add – Path to file – enter C:\Program Files\Microsoft IT\SharePoint Portal Server Recycle Bin\RecycleBinISAPIFilter.dll

12.  Click Set extension status to Allowed – click OK

13.  Verify the new Web Service Extension is allowed from IIS Manager.

14.  Expand the Web Sites within IIS Manager.

15.  Right-click the website for YourPortalSite (Default Web Site) and select Properties

16.  Select the ISAPI Filters tab

17.  Click Add

  1. Filter name – enter RecycleBinISAPIFilter

  2. Executable – enter C:\Program Files\Microsoft IT\SharePoint Portal Server Recycle Bin\RecycleBinISAPIFilter.dll

  3. Click OK


18.  Verify ISAPI Filter – right-click the website for your portal site (Default Web Site) and select Properties

  1. Select the ISAPI Filters tab – verify the RecycleBinISAPIFilter Filter Name displays a green arrow in the Status column and the Priority is set to High


19.  Select the RecycleBinISAPIFilter on the Default Web Site (for your portal site) Properties dialog and click the Move up button – click OK

20.  Expand the Default Web Site (where StaffCollaborator is located).

  1. Right-click the _vti_bin virtual folder and select Properties from the context menu.

  2. Under Application Settings, click Configuration, and click Insert

  3. Executable – enter “C:\Program Files\Microsoft IT\SharePoint Portal Server Recycle Bin\RecycleBinISAPI.dll” (don’t forget the quotes!)

  4. Click OK three times.


21.  Expand the Default Web Site (where your portal is located).

  1. Right-click the _layouts virtual folder, then select the Recycle folder and select Properties from the context menu.

  2. Click Create

  3. Application Pool – select MSSharePointPortalAppPool

  4. Click Configuration – click Add

  5. Executable – enter C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll

  6. Extension – enter .spsrec – click OK twice.


22.  Restart IIS

23.  Open Notepad

  1. Enter – Forfiles -p C:\SPS_RecycleBin -s -m *.* -d -15 -c “cmd /c del /q @path”


Note: The 15 in the command will delete all files in the path that are older than 15 days.

  1. Save as RecycleBinCleaner.CMD to C:\SPS_RecycleBin_Logs


24.  Open Control Panel – create a scheduled task to run daily that will execute C:\SPS_RecycleBin_Logs\RecycleBinCleaner.CMD

  1. Start time – 1AM – Run the Scheduled Task as the service account Network\SPSRecycleBinCleaner


Uninstall Process

  1. Open IIS Manager from all of your IIS user web front-end servers for SPS2003

  2. select Default Web Site (for for your portal site), right-mouse click and select Properties

  3. Select the ISAPI Filters tab - remove the RecycleBinISAPIFilter - click OK

  4. expand the Default Web site (staffcollaborator)

    1. select _vit_bin, right-mouse click, select Properties

    2. click Configuration

    3. Under Wildcard... - Remove the RecylceBin entry

    4. click OK - click Yes to approve - click OK twice



  5. From IIS Manager - select the Web Service Extensions - select and Delete the Recycle Bin ISAPI entry

  6. Control Panel > Add/Remove Programs - Select SharePoint Portal Server Recycle Bin - click Remove

  7. restart IIS