Great overview provided by this fella.
http://www.msexchange.org/tutorials/Exchange-2003-SMTP-Namespace-Sharing.html?printversion
And some comments from M$
http://technet.microsoft.com/en-us/library/465d8acd-a879-4565-abcf-0edb2b09502e.aspx
January 2007 Archives
Windows 2003 R2... Heads Up.
Ok, whew...
Thanks to my favourite wizard, Avi for finding the following article, as recently we built dozens of servers based on a Gold image using R2 media and yet, we were unable to install some R2 Features...
http://support.microsoft.com/kb/912309
Learn something new everyday... I had no idea... :)
Basically, our Gold image was built (from what I can tell) using R2 media but only the first CD. Apparently, Windows 2003 SP1 doesn't 'become' R2 until the second CD is run. In our case, up until today, when we wanted to install the advanced printer management functions that comes with R2 (sexier Enterprise Print Management), we hadn't even noticed/discovered that our systems weren't *totally* R2. Note, we didn't NEED R2 and our systems are fully compliant with R2 but if you need R2 'functionality', you'll need to spin the R2 disc/media, put your valid R2 license code against it and voila, welcome to real R2.
The short version:
If you run Windows 2003 R2 setup on a server and only install using the first CD, you are going to be running Windows 2003 SP1. If you install the 2nd CD (and sometimes you aren't prompted, say in assisted server builds like HP Smart Start, etc.), THEN you will be running Windows 2003 R2.
Powered by www.itgroove.net
Continue reading R2 isn't really R2 until it becomes R2.
To backup WSS 3 stages need to be completed:
Backup IIS Metabase:
cscript iisback.vbs /backup /b
Backup WSS site data:
STSADM.EXE -o backup -directory \\
Backup files folders:
Backup software (Backup Exec/ntbackup)
Got this?
0x80072ee2 "the windows sharepoint services folder could not be found"
Try this...
Microsoft describes the error 0x80072EFF as being related to one of two things ... Either a blocked port (in this example, port 444) or a credentials problem!
The real problem that everyone seems to be having is the credential issue. Here is how we get around that...
When linking to outlook from a SharePoint website Outlook 2003 automatically creates a new PST file to store SharePoint data. Its this root folder that we are going to be working with. Simply right click the root folder that says "SharePoint Folders" and select Properties. Next, click the tab labeled "Home Page". In the Address field enter the full URL to your SharePoint site using the external URL.
Example: https://my.sharepointsite.com:444
Now be sure to click the check box that says "Show home page by default for this folder", then click Apply and OK.
By accessing the SharePoint site from within Outlook, our user credentials will now be cached. Assuming you haven't already, go ahead and "Link to Outlook" any event and/or contact lists. When clicking on the new link (or folder) in Outlook, you should see "Send/Receive Completed" appear on the status bar at the right.
Use of Exmerge is plentiful but just getting it ready to roll takes the following three steps typically:
1. Get ExMerge (for Exchange 2003) http://www.microsoft.com/downloads/details.aspx?FamilyID=429163ec-dcdf-47dc-96da-1c12d67327d5&DisplayLang=en
2. Install Exmerge on a PC that has the Exchange admin tools installed (or on an Exchange server itself)
3. Make sure your account has Send As/Receive As Permissions on the Mailbox store you need to work with http://support.microsoft.com/kb/273642/en-us
4. Copy EXCHMEM.DLL (in your Exchange bin directory) to the same place as EXMerge is copied/extracted or you'll get an error
Powered by www.itgroove.net
Don't mind me, just storing a bookmark for myself...
Don't get too excited, this won't solve your spam. But, applied every time it comes out (every 2 months or so), it will help.
Ok, this was a timely lesson learned.
If you are getting the following error trying to search a Windows Sharepoint Services 3.0 (WSS), you might be experiencing the same problem we did...
No results matching your search were found. Check your spelling. Are the words in your query spelled correctly? Try using synonyms. Maybe what you're looking for uses slightly different words. Make your search more general. Try more general terms in place of specific ones. Try your search in a different scope. Different scopes can have different results.
The gist - if you want to crawl/search WSS content, you will need an NTLM authenticated website (ie. not basic). But you can have both - NTLM for search, basic for UPN (protected by SSL of course)...
To ensure that the index component can crawl content within the Web application:
• Configure at least one zone to use NTLM authentication. Ensure that the search content access account has the Read permission level to content accessed through this zone. You can do so by creating a policy that gives this account the Read permission level.
• Do not configure the default zone to use Anonymous, Basic, Digest, Certificates, or Kerberos authentication (that is, any forms of authentication other than NTLM).
And clarified again in the reference:
• If you want content within the Web application to be included in search results, ensure that at least one zone is configured to use NTLM authentication. NTLM authentication is required by the index component to crawl content. Do not create a dedicated zone for the index component unless necessary.
Base reference if you are interested: http://support.microsoft.com/kb/816042
Debug logging: http://support.microsoft.com/kb/816043/
Enabling the NTP Server on a Windows 2003 Server:
1. Make sure value TYPE is NTP in: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\Type
2. Set Announceflags to 5: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\AnnounceFlags
3. Make sure NTP is enabled (should be 1): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpServer
4. Set the time sources for external time. The value for NTPSERVER in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\NtpServer will be, for our purposes, "time.nist.gov,0x1 clock.isc.org,0x1 usno.pa-x.dec.com,0x1 tock.usno.navy.mil,0x1 timekeeper.isi.edu,0x1"
5. Set the Max Positive and Negative Time Correction. Set decimal values for both (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\MaxPosPhaseCorrection) and (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\MaxNegPhaseCorrection) to be 3600 (1 hour)
6. Do the following to restart Windows Time: net stop w32time && net start w32time
7. You should see successful Event ID 37 (ya, I'm happy with the entered time source) and ID 35 (now synchronizing). Interestingly, I found that it tried the 3rd one first and never bothered synchronizing with the others, at least right away...
Powered by www.itgroove.net
Sponsored by Major Change (.com), the Online Change Register
Configure RPC over HTTP/S on a Single Server
Reference to a nice, simple RPC Port registry update tool in there too...
Problem:
When setting mailbox size limits such as “Issue Warning”, “Prohibit Send”, or “Prohibit Send & Receive”, using Exchange 2003 System Polices or by setting a limit directly on a users account in Active Directory it is not possible to set a size limit greater than 2097151KB due to a restriction in the GUI. If you try to enter a number larger than 2097151 you receive the message
“The value for 'Issue warning at (KB)' is not valid. Specify a value from 0 through 2097151.”
One may argue that it would never be necessary to set a limit great that 2GB for a mailbox, however, the reality is that in today’s email enabled world mailboxes are getting larger and larger, plus it is hard to argue when Google is giving away mailboxes with 2.5GB of space!
As a consultant one of the my problems with not being able to set a limit great than 2097151 has been in situations where I have came into a company to re-architect their Exchange system and half the company has reasonably sized mailboxes and the other half have mailboxes as large as 15GB, yes, you heard me right, 15GB!!!! Sometimes management is unwilling to force these people to cleanup their mailboxes overnight so it is a long process. In these situations I certainly do not want those users mailboxes getting any larger then they are already so I set a limit just above the current size of the mailbox to make it painful for them to keep so much mail and eventually they give in and cleanup their mailbox.
Solution:
Mailbox storage limits cannot be set above 2097151 using the GUI, however, using the tool ADSIEdit a mailbox storage limit larger than 2097151 can be set. ADSIEdit is a very powerful tool and should be used with extreme caution!
Using ADSIEdit to Modify System Policies Mailbox Storage Limits
Add ADSIEdit to the MMC and bind to the domain using the Configuration well known naming context.
Navigate to the Services Container, MicrosoftExchange, ExchangeOrgName, AdministrativeGroups, AdministrativeGroupName, & click on the Policies folder.
In the right hand side of the ADSIEdit window find the name of the policy you want to modify and double click on it.
Scroll through the list of attributes until you see the attribute you want to modify, the attributes in question are:
mDBStorageQuota: Issue warning at (KB)
mDBOverQuotaLimit: Prohibit Send at (KB)
mDBOverHardQuotaLimit: Prohibit Send and Receive at (KB)
Double click the attribute you are going to modify and enter a size limit of your choice, keep in mind that limits are in KB, once you are finished simply close ADSIEdit and you are done.
Using ADSIEdit to Modify Mailbox Storage Limits on a Single User
Add ADSIEdit to the MMC and bind to the domain using the Domain well known naming context.
Navigate to the location of the user account that you want to modify.
In the right hand side of the ADSIEdit window find the name of the policy you want to modify and double click on it.
Scroll through the list of attributes until you see the attribute you want to modify, the attributes in question are:
mDBStorageQuota: Issue warning at (KB)
mDBOverQuotaLimit: Prohibit Send at (KB)
mDBOverHardQuotaLimit: Prohibit Send and Receive at (KB)
Double click the attribute you are going to modify and enter a size limit of your choice, keep in mind that limits are in KB, once you are finished simply close ADSIEdit and you are done.
GB to KB converter you'll need :)
http://www.ibeast.com/content/tools/band-calc.asp
Well, this one was frustrating. To generate an Outlook Public Folder Rule and avoid the "Changes to the rule could not be saved" error (Public Folder Assistant), I had to do more than what Microsoft Exchange knowledgebase suggested (@ http://support.microsoft.com/?kbid=903289). I also had to go to the actual server object in Exchange System Manager, go to the "Security" tab and explicitly change my user account in there to have Send As permissions as well. I figure this is probably because I was the actual administrator who installed Exchange and my account was already in there and although I had full control, the Exchange setup program (educated guess) explicitly denied me send as permissions... dumb but its working for me now.
