Wednesday, October 26th, 2011
I stumbled across this gem last week and thought I’d share it with you. Using the tables listed here you can figure out what version of Exchange Server you are running.
You can use the Get-ExchangeServer powershell command to find the Exchange 2010 and 2007 versions, but you will need to use the GUI in Exchange 2003.
Friday, October 21st, 2011
Microsoft this week have released an update for the SBS 2011 Migration tool that ships on the SBS 2011 DVDs. This tool takes into account more then a dozen additional checks that need to be done prior to a migration to ensure that the smooth migration form SBS 2003 or SBS 2008 to SBS 2011 Standard. It’s quick and easy to get the update, when you run the Migration Tool on your SBS 2003 or SBS 2008 server before you commence the migration, simply allow it to check for updates and the tool will bring the updates down and then perform the checks on your machine.
The SBS team has a blog post about the tool here
You can also find out more information about the specific checks done by the tool and the corrective actions needed here
This update is a MUST for any migration you are doing as well as reading the SBS Team blog – you can use this link to quickly check the Migration category for migration issues on SBS 2011 migrations.
Monday, October 3rd, 2011
Recently when doing an SBS 2003 to SBS 2011 Standard migration, I had an error of “Object not found” in the Local Move Request screen as you can see below.
I did some digging and found that the permissions on the SBS 2003 / Exchange 2003 mailbox store had been changed for some third party application.
Too fix it do the following,
Thursday, May 19th, 2011
I’ve done a few posts already on migrating to SBS 2011 Standard. I figured I would create this post as a permanent placeholder for all migration whitepapers on how to get to SBS 2011 Standard Edition. Below is the list of whitepapers you need to get to SBS 2011 from the previous versions of SBS.
For migration white papers on moving to SBS 2011 Essentials – check this post.
Thursday, May 19th, 2011
Similar to the post I did on SBS 2011 Standard Migration White Papers, I’m doing this one to create a permanent placeholder for all migration whitepapers on how to get to SBS 2011 Essentials Editions.
For migration white papers on moving to SBS 2011 Standard – check this post.
Wednesday, May 18th, 2011
Microsoft has for some time produced a Best Practice Analyser (Analyzer for the Americans)
This BPA allows you to review your SBS installation and will highlight any of the common misconfiguration issues that the Microsoft SBS Product Support Team has identified over time. The BPA will download the latest updates for it each time it is run and therefore will always ensure your system is reviewed using current standards.
The BPA is a MUST to be run before you do any type of major works on a system and AFTER you’ve done them too. Also ensure you run it prior to a migration to a higher level of SBS to maximise the chances of success.
You can download the SBS Best Practice Analyser for various versions of SBS from the locations below.
Friday, January 14th, 2011
Microsoft have released their white paper on how to migrate to SBS 2011 from SBS 2003. This white paper walks you through all the steps needed to take you from SBS 2003 or SBS 2003 R2 over to SBS 2011 Standard edition. This basically involves installing the new SBS 2011 server in a side by side situation with the existing server, and migrating data over to it using some manual commands on both servers, and some wizards for other things. You will have 21 days to complete the migration after which time the SBS 2003 server will shutdown every few hours. It’s a good process, a little manual, but after the initial installation of the server onsite, you can do the rest remotely.
The whitepaper is available here for download from Microsoft.com
Friday, December 24th, 2010
Microsoft have today released information on TechNet for migration to SBS 2011 Standard Edition from SBS 2003. This is the first and most likely method that many of our clients will be needing to follow to move over to the new platform given many are still on SBS 2003. This document available here .
I’ll be posting more on my migration from SBS 2008 to SBS 2011 over the coming week, so stay tuned.
Friday, April 16th, 2010
I had this error on a client site today when deploying a Windows XP machine that had been in operation for many years into an SBS 2003 R2 network.
I tried to action the suggested fix from the error message, but this did not resolve the issue. I then dug deeper into it by using the SBS Client Setup Log file and as you can see below found it was related to some files on the desktop of the computer.
I deleted those files and ran the connectcomputer wizard again. It still failed, so I reviewed the log file again and found that this time it was related to files in the users temp directory. I deleted them and it worked fine. The secret here is to ensure that you review the Client install log files to know what is causing the problem.
The file is called SBSNetSetup.log and it’s located on the client computers hard drive under C:\Program Files\Microsoft Windows Small Business Server\Clients.
Thursday, April 15th, 2010
Doing some work for a charity organisation today, and had to configure their Telstra supplied Thomson TG782T router to work with SBS 2003 R2. Found it rather confusing though as the routers definition of firewall settings refers to outbound settings only – not inbound settings. Anyway – in order to make it work, I wanted to port forward ports 25, 80, 443, 444, 1723 and 4125 to the SBS 2003 R2 server. This is the procedure I used to do it.
Select the Home Network option from the menu on the left hand section.
Select the device that represents your server – in this case it is the Unknown device which I have identified via it’s MAC address. Click on the link for that device and you will get the screen below.
Select the Configure link in the top right hand side.
Replace the UNKNOWN section in the New Name box with your servers name – this just makes it easier for you to know which device is which. Select the Apply button to record the change to the devices name.
In the connection sharing box, select from the drop down which predefined protocols you want included and then select Add on the right hand side. You will be able to add SMTP, HTTP, HTTPS, and PPTP server using the predefined protocols. You should have a screen like the one below now.
Select the Toolbox menu and then the Game & Application Sharing menu.
You can see the port definitions you’ve already done listed. Scroll down and select the “Create a new game or application” link. Type in a name for the port you wish to define – ie COMPANYWEB and select Manual Entry of Port Maps and Next.
Enter in the port definition as per the screen below and select Add
Once done – select the Add New Game or Application to add definitions for port 4125 which I am calling RWW-RDP.
Once complete – go to Home Network > Devices and select the configure link in the top right hand section. Use the same process as above to add the Companyweb (444) and RWW-RDP (4125) protocols to the list. You should see the screen as below.
Now you are all done. You should now conduct a port scan using your favorite port scanner – I use Shields up from www.grc.com as a basic one as it allows me to confirm the open ports. Below is the result from the first 1024 ports
You should also do a custom port scan for the specific ports you have opened. You can see below how I’ve entered this into the ShieldsUp program for testing.
This is the result from the port scan above. You will note that port 4125 is listed as closed – this is normal as it only opens after you have logged in to the RWW Web Interface and then does an IP check to verify things for security.