i've created this blog as a storage for random tech notes i've found useful and may help others at the same time. i've joked that it's not possible to know everything but i'm google certified and can find just about anything i need using google. it's worked time and time again. anyway i hope you find this info useful if not that's fine too as it's really intended for me anyway :) -- google certified

Tuesday, July 2, 2013

Exchange 2010 upgrade to SP2 fails at hub transport

Exchange 2010 upgrade to SP2 fails at hub transport with error about unable to find source install files for MS Exchange 2007 antispam filter updates.

Worked with MS and resolved by the following:



The following solution has been provided to resolve your issue: Exchange 2010 Sp2 upgrade on server. A summary of the solution is detailed below.

    •    Symptom – Exchange 2010 Sp2 upgrade on server
    •    Cause – Microsoft Exchange 2007 Standard Anti-spam Filter Updates issue
    •    Resolution

1.      Checked Exchange setup log and UninstallASEntIRS.msilog as setup was failing on Hub Role.
2.       Ran windows clean tool found it does not list Microsoft Exchange 2007 Standard Anti-spam Filter Updates.
3.      Checked registry for {14F288C7-C695-40D5-971D-8890605C6040} we still have the key listed.
4.      Downloaded MsiZap.exe tool and Ran MsiZap.exe T {14F288C7-C695-40D5-971D-8890605C6040} it got completed successfully.
5.      Checked registry we still have {14F288C7-C695-40D5-971D-8890605C6040} registry guid listed
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MATS\WindowsInstaller\{14F288C7-C695-40D5-971D-8890605C6040}]  
6.      Took backup of WindowsInstaller key and deleted registry keys which were for Microsoft Exchange 2007 Standard Anti-spam Filter Updates
{14F288C7-C695-40D5-971D-8890605C6040}
{93FCFF43-49E2-4AE5-9AD4-0256878AB886}
{C3F10D8C-BD70-4516-B2B4-BF6901980741}
7.      We were now able to upgrade to E14 SP2 successfully.
8.      Rebooted Exchange server and verified server version it was upgraded successfully in Exchange 2010 Sp2.

Thursday, December 15, 2011

Configure Exchange 2010 to allow relay to external addresses

I always have a hard time finding this command so here you go.

Get-ReceiveConnector "Relay" | Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "ms-Exch-SMTP-Accept-Any-Recipient"

http://exchangepedia.com/2007/01/exchange-server-2007-how-to-allow-relaying.html

Tuesday, October 18, 2011

removing exchange 2003, "One or more users currently use a mailbox store on this server"

Typically working with exchange is no problem for me but I ran into an environment where previously the organization had migrated to exchange 2010 but the old 2003 was not removed properly. Since they still had the old server there I fired it back up and began the process of uninstalling exchange. I verified all mailboxes were moved and so on and went to uninstall. The uninstall popped up a message saying there was still a mailbox on the server. This can happen if a user given an exchange mailbox but one is never created if they never logon to exchange or receive any email. The normal steps are to run some searches and I did but found nothing. I went as far as trying to remove the default mailbox database and still nothing. Finally I found a different query that worked and showed me the mailbox. To do the search, open ADUC, right click the domain, click find, click custom search, click the custom tab. In here type the following and modify for your environment.
The only items you need to change on this query is OrganizationName and ExchangeServerName

(msExchHomeServerName=/o=OrganizationName/ou=First Administrative Group/cn=Configuration/cn=Servers/cn=ExchangeServerName)(objectClass=User)

The above query should be one long line no returns.

Monday, July 11, 2011

Cisco CME fax to email


Recently I’ve been working to test out inbound fax service on a Cisco voice gateway to have the gateway actually receive the fax and then email it to whoever it needs to go to. Go green right? Anyway I followed several articles that made it seem really easy. I followed the steps and it looked like I set it up right but the gateway would never pickup the call. I dug for a while with no help until I finally found a small little pdf on configuring an UC500. It had one little line that said after configuring the application to save the config and reboot the router…… well that didn’t make sense I’ve hardly ever have had to reboot a router for something to take effect. Anyway I was like sure why not so I did and voila! It worked. The article mentioned the reload was necessary to load the application into memory. Ok whatever but it fixed it. Anyway below is a link to the u500.com site that has tons of great articles that also apply to CME. And also is my config I used to setup fax to email on this voice gateway. The hardware is a Cisco 2921, IOS ver 15.1(3)T, cme ver 8.5

voice service voip
 fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none
!
fax interface-type fax-mail
mta send server 10.25.2.5 port 25
mta send subject FAX -
mta send with-subject $s$
mta send filename faxsvr date
mta send postmaster faxes@domain.local
mta send mail-from hostname lib-cme.domain.local
!
application
 service onramp flash:app_faxmail_onramp.2.0.1.3.tcl
 !
dial-peer voice 5001 mmoip
 service fax_on_vfc_onramp_app out-bound
 destination-pattern 1234567890
 information-type fax
 session target mailto:1234567890@domain.com
!
dial-peer voice 5000 pots
 service onramp
 incoming called-number 1234567890
 direct-inward-dial

again what fixed it for me was to wri the config and then reload it. also my telco passes all ten digits to me over the PRI. hope this helps!

http://www.googlecertified.me/

Tuesday, June 28, 2011

Cisco CME overlays

Update:
The config below has the overlay DN’s as single line DN’s. This restricts the users ability to transfer calls to cold transfers only. In order to do a warm transfer the DN’s have to be configured as a dual-line DN. And then each DN needs to have the huntstop channel command to keep calls from rolling over to the second line on a phone.



I support different technologies for different clients and recently had an odd request. The client wanted to calls that come in before 9AM to automatically roll to an auto attendant since they do not start servicing patrons until 9AM. Seemed easy enough? Calls flow in to a hunt group so just modify the DN’s that are part of the hunt group and set a night service option and set the night service to be active until 9AM. Problem is that with the night service active those phones don’t ring at all until 9AM. So if internal users called those numbers it went direct to the AA.
The best solution for this case is to create a new set of DN’s that have the same number configured and assign those as overlays on those phones. Then configure those DN’s with a night service that way calls that roll to this new number before 9AM roll directly to the AA but those users can still make/receive calls to their primary direct number.
Below is the portion of the config that is relevant.
This is the night service config:

telephony-service
night-service day Sun 08:00 08:59
 night-service day Mon 21:00 08:59
 night-service day Tue 21:00 08:59
 night-service day Wed 21:00 08:59
 night-service day Thu 21:00 08:59
 night-service day Fri 18:00 08:59
 night-service day Sat 17:00 08:59

This is the first hunt group that calls come into. The * is one wildcard slot for the primary operator. This gives her the option to log on and off of the first hunt group for lunch and breaks. If she’s not logged on calls automatically roll to the next hop which in this case is the DN that is used in the overlay.

ephone-hunt 1 sequential
 pilot 1040
 list *
 final 1043
 timeout 12

This is part of the DN’s for the overlay number. Main thing here is make sure the number is the same on all the DN’s. Also you need to have as many DN’s as active calls you want to handle. Meaning if you only have 3 DN’s configured only three active calls can be active for that number and the fourth will route to the noan call-forward. You’ll also set a different preference for each DN. Each DN will have the no huntstop command the last DN will have huntstop. Since the whole point of this is to config night service we configure each for call-forward night-service and the number to forward them to. In this case it’s the default AA which has time of day rules. The night-service bell command turns this feature on.

ephone-dn  96
 number 1043
 name Backup Operators
 preference 6
 call-forward night-service 1021
 call-forward noan 1021 timeout 20
 no huntstop
 night-service bell
!
!
ephone-dn  97
 number 1043
 name Backup Operators
 preference 7
 call-forward night-service 1021
 call-forward noan 1021 timeout 20
 night-service bell
!

Here is the part of the config on how to apply the overlay to the phones. You have the option to use the different options like : o c and so on between the button and the numbers for that button.  In my case when I attempted to use the o for a standard overlay it kept locking up the phones that missed the call. Not sure why but it was odd so I just went ahead and used the c for overlay with call waiting which is more of what they wanted anyway.  In this case I have an ephone-template with some options configured. The important thing here is to define the button with first their primary number and then all the DN’s that are part of the overlay so the phone can answer a call to anyone of the DN’s for rollover type function.

ephone  11
 mac-address F866.F2F6.A687
 ephone-template 1
 max-calls-per-button 2
 type 6921
 button  1c17,92,93,94,95,96,97

That’s pretty much it. This seems pretty easy but took me a little while to get the theory to work out in real life so here you go.

Tuesday, June 21, 2011

Exchange 2010 auto reply for distribution groups


I had the need come up to configure an auto reply for emails sent to a distribution group. This is easy if you have certain third party applications but it’s not terribly difficult if you don’t. Here’s what you’ll need:

-          Distribution group (Test-Distribution-Group)
-          Dummy mailbox (Dummy-Mailbox)
-          Enable Allow auto replies in Exchange
-          Outlook

First start out by verifying the settings to allow automatic replies happen. In exchange 2010 open up the EMC, Org Config, Remote Domains, Modify the default policy or whatever you have here. On the message format tab, select Allow automatic replies. 

Next open up the properties for the distribution group. EMC, Recipient Config, Distribution Group, Test-Distribution-Group. On the Advanced tab select Send out-of-office messages to originator.

Now we can configure a server side rule in with Outlook to send an email. I used Outlook 2010 here. Open Outlook, File, Rules and Alerts, New Rule, Apply rule on messages I receive, Select sent to people or public group, specify the Test-Distribution-Group, next, Select have server reply using a specific message, click the link and type out the email you want to reply with, here you can also select delete it. I select delete it to keep this mailbox from accumulating a ton of emails. 

Finally we make this mailbox a member of the distribution group.
You can take this a step further and make this dummy mailbox default email address be something like donotreply@domain.com and create a rule that anything sent to this user only is deleted.
Good luck!
google certified