posted on July 4th, 2008 by Tracy Sales
To find the product version in Exchange 2007, execute the following command in PowerShell:
Get-ExchangeServer | fl name,edition,admindisplayversion
Refer to the article below to find out how the build number corresponds to a product version:
http://blog.kazmarek.com/2008/07/04/exchange-server-version-and-build-numbers/
Posted in Exchange 2007 | No Comments »
posted on July 4th, 2008 by Tracy Sales
This microsoft article details the various Exchange Server versions, including service packs.
http://support.microsoft.com/kb/158530
Some recent ones:
Microsoft Exchange Server 2003 6.5.6944 October 2003
Microsoft Exchange Server 2003 SP1 6.5.7226 May 2004
Microsoft Exchange Server 2003 SP2 6.5.7638 October 2005
Microsoft Exchange Server 2007 8.0.685.24 or 8.0.685.25 December 2006
Microsoft Exchange Server 2007 SP1 8.1.0240.006 November 2007
Posted in Exchange Server | No Comments »
posted on June 30th, 2008 by Tracy Sales
I came across a situation where an organization had been setup to use RPC/HTTPs “Outlook Anywhere” for some time and all the Outlook 2003 clients seemed to work fine. One user had Outlook 2007 and was unable to connect using this method. In the LAN and through OWA everything worked fine. I tried tons of different solutions online but in the end, the problem was with the configuration in Exchange. I looked over the suggested configuration here:
http://www.petri.co.il/configure_rpc_over_https_on_a_single_server.htm
and I discovered that the RPC ports hadn’t been configured as the article suggests. I used the recommended “RPCnofrontend” tool: http://www.petri.co.il/software/rpcnofrontend.zip and everything worked fine after that.
Posted in Exchange Server, Outlook, SBS 2003 | No Comments »
posted on June 20th, 2008 by cukerdesign
The issue:
Unable to open a file directly on the desktop or in explorer using double-click or right-click->Open.
Quick fix:
For example, to repair Excel’s file extension (.xls) type the following in Start –> Run…
“C:\Program Files\Microsoft Office\Office\Excel.exe” /Regserver
Posted in Uncategorized | No Comments »
posted on June 5th, 2008 by Danny Kazmarek
There is no specific SMTP service like you saw with Exchange 2003 and IIS. However, if you’re just trying to stop the listening port 25 for Inbound/Outbound mail, stop the ‘Microsoft Exchange Transport’ service.
Posted in Exchange 2007, Exchange Server, Microsoft | No Comments »
posted on May 29th, 2008 by Robert Masterson
In Active Directory when you have an Exchange server a user or group, even a public folder can have multiple smtp email addresses associated with the entity (user/group/public folder etc.), but finding the non-default email address can be tedious. A great way to search for it is:
Go to Active Directory Users and Computers –> right click on the domain and click find –> in the find field, change the criteria to ‘custom search’ –> click the advanced tab where you can type in a LDAP query. If you are trying to find out who has sales@yourdomain.com, type proxyAddresses=smtp:sales@yourdomain.com.
Wildcards can be added to the email address portion, and you can also type a wildcard ie. *.yourdomain.com and then change the view to add the proxyaddress column to see all of the entities with their proxyAddresses (email addresses)
Posted in Exchange Server, Microsoft | 3 Comments »
posted on May 22nd, 2008 by Tracy Sales
You have 2 options.
- You can run the following SQL query:
SELECT SERVERPROPERTY(’productversion’), SERVERPROPERTY (’productlevel’), SERVERPROPERTY (’edition’)
- You can check the version of the sqlservr.exe file, below is a list of how the version breaks down:
SQL Server 2005
| SQL Server 2005 RTM |
2005.90.1399 |
| SQL Server 2005 Service Pack 1 |
2005.90.2047 |
| SQL Server 2005 Service Pack 2 |
2005.90.3042 |
SQL Server 2000
| SQL Server 2000 RTM |
2000.80.194.0 |
| SQL Server 2000 SP1 |
2000.80.384.0 |
| SQL Server 2000 SP2 |
2000.80.534.0 |
| SQL Server 2000 SP3 |
2000.80.760.0 |
| SQL Server 2000 SP3a |
2000.80.760.0 |
| SQL Server 2000 SP4 |
2000.8.00.2039 |
Posted in SQL | No Comments »
posted on May 8th, 2008 by Tracy Sales
After an upgrade from CRM 3.0 to CRM 4.0 I noticed that items no longer deleted immediately. It seemed as if they eventually deleted, but I couldnt tell you when. From what I’ve heard from Microsoft and others, the problem is a trigger that is supposed to be disabled or removed during the upgrade. The fix was this:
- In SQL Management Studio, expand the dbo.QueueItemBase table within your CRM database.
- Expand the Triggers folder.
- Right-Click the t_update_queueitembase trigger and disable it. (Select “disable” from the menu).
This may not address items that you have already deleted that are still pending deletion. To correct those, perform the following SQL command:
UPDATE dbo.QueueItemBase
SET DeletionStateCode = 2
WHERE QueueId = ‘YOUR_GUID_HERE’
You’ll have to find the GUID of the Queue you’re trying to delete from, but it’s pretty straightforward after that.
Posted in CRM | No Comments »
posted on April 24th, 2008 by Shayne Comey
In order for printers to be completely autodeleted from both the registry and Print Manager users may need Full Control over the following registry key and subkeys:-
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Print
Users also need Change permissions to the following:
%systemroot%\system32\spool
Posted in Citrix, Printing, Terminal Server | No Comments »
posted on April 24th, 2008 by Robert Masterson
These days many mailservers are requiring reverse DNS (rDNS) and SPF records to validate the sender from this domain.
How does SPF work:
SPF is easy to understand. The “Internet” uses DNS (Domain Name System) to resolve Domain Names (as an example www.msexchange.org) into IP addresses. DNS is also used to direct requests for different services like e-mail and Web Servers. For every Domain around the world an MX (Mail Exchanger) record must exist. An MX record tells the e-mail sender where the target server for receiving mail is located.
SPF is publishing “reverse MX” records in DNS which tells the mail sender which machines send mail from the domain.
The recipient of the e-mail can now check these records to ensure that e-mail is coming from a “trusted” sender from this domain.
These “reverse MX” records can be easily published in DNS. It takes only one line in DNS to fullfil all requirements.
Microsoft has come up with a good and easy wizard (webpage not downloadable tool) that asks a few questions and spits out the correct SPF.
How to add SPF file to Windows Server DNS - link
OpenSPF Website - link or old site
Posted in Exchange 2007, Exchange Server, Microsoft, Networking | No Comments »