There seem to be an issue with Windows SBS Small Business Server 2011 or Windows Server 2008/ R2 running both Exchange 2010 SP1 Rollup 3 or 4. This has happened many times and gone through the Exchange and router configuration many times with no success. Here is the simple workaround to this teething issue. The issue seems to be a bug from Microsoft where if you have IPV4 along with IPV6 enabled. The IPV6 will be used to resolve the DNS when sending an email. This will fail and the user will either get a delivery report or a delay report.
To solve the issue, simple do the following:
– Open the ‘Exchange Management Console’
– Expand the ‘Server Configuration’ node
– Right Click and select ‘Properties’ on teh server in the content window (This will popup the server’s property window)
– Click on the ‘External DNS Lookups’
– Select ‘Use These DNS Servers’ radio button and add the external DNS IP addresses of your ISP
– Click on the ‘OK’ button to save the configuration
– Expand the ‘Organization Configuration’ node and click on the ‘Send Connectors’ tab
– Right click on your send connector and select ‘Properties’
– Click on the ‘Network’ tab
– Tick the option to ‘Use domain name system (DNS) MX records to route mail automatically’ and make sure to tick the ‘Use the External DNS Lookup settings on the transport server
This should solve the problem and it will process all the mail in the queue of Exchange. Of course depending if you have the right configuration and ports open from the router.
Sometimes when you don’t need a service on your server, especially on SBS it’s a bit tricky since everything is embedded in the installation. One may notice that you might have a repository of more than 10Gb without knowing and here’s how to stop it. For Windows 2003 server, you might do the following to have a clean stop of the WSUS (Windows Server Update Services) service.
Update Service from the
services.msc or from Administrative Tools/Services
Also set the service as disabled.
Also you might look into the Group Policies for your OU (Organizational Unit) so that the PC’s are not pointing to the server for Windows Updates. Open the Group Policy Management from the Administrative tools or just run
gpedit.msc and check if the update service location is set. Remove if specified.
Computer Config -> Administrative Templates -> Windows Components -> Windows Updates -> Specify intranet microsoft update service location
This should stop the WSUS service from running. Also you might either remove or archive the files in the WSUS repository to free up some space.
When coming accross SQL Express editions, you will not be able to set a job in the Agent to execute a stored procedure. I usually do custom stored procedures to run them on Express editions.
There is a way to execute them by using the
sqlcmd -Q "exec myprocedure" -S mysqlserver -d fromthisdatabase -E -o C:\log.txt
This will execute your stored procedure and you can put it in a batch file and schedule it in the Task Scheduler
To setup the Windows Server Backup in Windows 2008 upwards, to support the Hyper-V VSS writer, one must follow the following steps.
After installing the Windows Server Backup and it’s Command-line tools under the Features section in the Server Manager, follow the follwing steps:
Open Command Line or type
VSSADMIN List Writer >C:\vss.txt
Note: This will save a text file with all the VSS information.
VSS.TXT and find the Writer
GUID from the section
Microsoft Hyper-V VSS Writer
GUID to the clipboard
Open Registry Manager by running
Find the following key:
If there isn’t a key
WindowsServerBackup, create it. Then under it, create another key
Application Support. Under that, creat a new key with the GUID of the VSS Writer we copied from the text file.
An example of the GUID is
After you have created this key with the GUID, Create a new value under it calling it
Hyper-V VSS Writer. Make sure it’s of type
REGSV using a String Value.
Some notes when it comes to restore:
When affecting restores make sure you select application based restore.
You will not be able to restore a file from a Virtual Machine, you will have to restore all the machine.
Whe opening the Exhange 2010 management console i.e. EMC once may see the below error:
Connecting to remote server failed with the following error message : The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available.
This seems to be an issue with the IIS port 80 bindings. On my server I managed to fix it by removing any bindings of port 80 and do them again.
Open IIS, and then right-click on tye Default Web Site.
Click Edit Bindings.
Remove the bindings with port 80 and set the value of All Unassigned for the IP address.
In my case this solved the problem. Also I found the below just in case you have multiple sites.
You are running multiple websites.
You try to set up a redirect, for example, to https://mail.contoso.com/owa by requiring Secure Sockets Layer (SSL) on the Default Web Site.
You create another website to do the redirect back to the SSL-enabled website.
Windows Remote PowerShell requires port 80 to be available on the Default Web Site. If you want to set up an automatic redirect to /owa and redirect http requests to https, follow the instructions in the section, “For a Configuration in Which SSL is Required on the Default Web Site or on the OWA Virtual Directory in IIS 7.0” on the following Microsoft website:
When attempting to make a full server backup with Shadow Copy and everything, you may notice the error
0x8004231f whenever you try to affect a backup on your server. This is 99% due to space on one of your hard drives. There is not enough space for the Volume Shadow Copy to create a shadow copy of the files in the drive.
The full error looks like this:
Volume shadow copy creation: Attempt 1.
Error returned while creating the volume shadow copy:0x8004231f.
Error returned while creating the volume shadow copy:8004231f Aborting Backup
To fix this, you may want to either delete or move unecessary folders or files from the drive in question… or look at the Volume Shadow Copies configuration.
Right-Click on the drive and select Properties
Click on the Shadow Copies Tab
Click on the drive you are having problems
Click on Setting button
At this stage you may review the Shadow Copy storage use by increasing or decreasing the limit in MB. Once you have enough disk space for the Shadow Copy on the drive in question, run the NTBackup again and it will not cause any issues.
When deleting or editing a folder or file situated in a folder structure you may encounter an error saying that the “Path too long”. This is due to the fact that the whole path to the folder or file is too long and Windows cannot process it. Yeah I know what you’re saying, why does Windows let you create a path that long in the first place.
Well, a quick fix to this is to rename all folders in the structure to a one letter folder. This way you will be able to remove the folders or files to a normal structured location and the Windows will not argue with the path being too long.
Sometimes you might end up waiting for more than 30 minutes or more to stop the DHCP server on Windows 2008 onwards. Sometimes waiting for much longer. Well to manually kill the process you will need to first find the PID of the process DHCP server and then kill it.
Make sure you run the command line ‘As Administrator’
sc queryex dhcpserver
this will give you the information on the DHCP server process including the PID number. Keep note of this and then run:
Taskskill /F /pid (PID number)
If you try to make a server backup with Microsoft’s SBS 2011, you will surely get an instant error saying:
“A Volume Shadow Copy Service operation error has occurred: (0x800423f0). The shadow-copy set only contains only a subset of the volumes needed to correctly backup the selected components of the writer”
This can be solved by opening a command-line as administrator and going into the folder:
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
After completing, the backup will work like a charm.
Click here to read more on the matter.
Open a command prompt or set this up in a batch file to run when users log in the system and have the following set.
w32tm /config /syncfromflags:domhier /update
net stop w32time
net start w32time
This will synchronize the time of the machine to point to the domain controller which is configured on the machine. If the machine is joined to domain X it will inherit the time setup from domain X, irrelevant if there are multiple domain controllers in domain X. This is the new format which has taken place of the NET TIME which was used by Windows XP downwards.