Exchange 2010 Beta is now available!
You can go to https://www.microsoft.com/exchange/2010/en/us/trial-software.aspx and download a 360 day trial. The RTM and public launch will probably coincide with the launch of Office 2010 and SharePoint Server 2010.
T-Mobile G1
I got a new phone today, the Google G1. All I have to say is =]
A lot of people seem to wonder what the best, FREE, way to do a Physical to Virtual (P2V) conversion of their Windows servers is. If your VM host is going to be a Hyper-V server, then there are two good methods (that I know of) to perform the operation.
Method 1:
Use the System Center Virtual Machine Manager’s (SCVMM) integrated P2V conversion utility to perform the operation. This supports doing a live migration, meaning that the target system can remain online and available for user’s requests during the migration period.
SCVMM 180 Day Evaluation: http://technet.microsoft.com/en-us/evalcenter/cc793138.aspx
Method 2:
If you don’t want to use the SCVMM method or it isn’t working properly for you, you can use the free VMWare converter tool. The VMWare converter tool also supports live migrations. After you perform the live P2V conversion with the VMWare converter tool you will end up with a VMDK file (VMWare’s virtual hard disk format), so that will have to be converted to a Hyper-V usable file with the VMDK to VHD converter.
VMWare Converter: http://www.vmware.com/products/converter/
VMDK to VHD Converter: http://vmtoolkit.com/files/folders/converters/entry8.aspx
Good luck!
Here is an article that details how to rebuild IIS in an SBS 2003 installation. Use this article at your own risk, and don’t try to do it remotely… you will lose your connection to the server.
Reinstalling IIS in SBS 2003 (DOC File, 45KB)
IIS 6 Properties
I was having an issue today and thought I would share the solution I found.
I had an IIS 6 server that was hosting some web pages. In a directory beneath the root I had some .exe files that I wanted to like to on the main page to allow downloading. Whenever I would click on the files I would get a 404 error. I knew the files were in the right spot and the naming was correct.
I discovered that in order to allow .exe files to be downloaded from your IIS 6 server you need to remove the “Execute” permissions from the folder that the .exe files are sitting in… not the entire virtual directory, just the particular folder that the .exe files are sitting in.
To do this you have to open the IIS Manager, right click on the directory containing the .exe files, and change the Execute Permissions to “Scripts Only”.
Fallout 3 Headshot
I have been hearing that a lot of people out there have had issues with Bethesda Studio’s Fallout 3. It is always disheartening to hear of an otherwise great game marred with technical flaws.
I was having a problem similar to many, CONSTANT crashing… especially when on indoor levels.
The solution in my situation came to me when I noticed that every time Fallout 3 crashed I had the little FFa icon down in my system tray. I knew that icon was related to a codec pack I had installed on my machine, but I couldn’t remember exactly which one.
Just as a test I downloaded the latest K-Lite codec pack and installed the full version except the media player. As part of the install process it detected and removed all previous codec packs (3 in my case). After the install and a reboot I am now able to play Fallout 3 without the in game crashing! It does however still crash on exit… not a big deal though.
K-Lite Code Pack Download: http://www.free-codecs.com/download/K_lite_codec_pack.htm
I encountered an little nagging issue the other day, so I thought that I would share the solution that I found. I have a server (Windows Server 2008) set up as a Domain Controller (2003 Functional Level). It is the only DC in the forest so it is also the DNS server and the Global Catalog server. I had multiple IP addresses associated with the only NIC installed in the machine, and of course I didn’t want it to register multiple A records with different IPs, but the same hostname. I took the obvious approach and unchecked the “Register this connection’s addresses in DNS”.
What the heck? It kept registering all of the IP addresses in DNS. It seemed pretty straight forward, but the solution lay elsewhere.
By default a DNS server will register all the IPs associated with it in DNS, because it listens on all of those IPs for DNS name resolution requests. The answer in this case was to open up the DNS Management Console, right click on the DNS server in the left pane, choose properties, and click on the “Interfaces” tab. This tab lists all of the IP addresses that the DNS server is listening on. Simply uncheck all except the primary address that clients are making requests on and voila! Just delete the old addresses from DNS (except the primary) and they will stop showing up in DNS.
Exchange 2007
The other day I was installing an instance of Exchange Server 2007 on a Windows Server 2008 machine. During the install process the Hub Transport role install kept failing. The error I received was that the “MSExchangeTransport Service failed to reach the state of Running”.
After banging my head against the wall for a little while I ran across a posting (I can’t remember where) that noted the service in question will not start unless the IPv6 protocol is enabled on the primary NIC. I had indeed disabled it earlier because I did not intend on using IPv6. Enabling the IPv6 protocol and restarting the install process resolved the issue!
SQL Server 2005 Box
I ran into this issue the other day and I thought I would share the simple answer that I found with you.
After installing SQL Reporting Services on a Windows Server 2008 Machine I attempted to verify successful installation by browsing to http://localhost/ReportServer. I was greeted by this message: “Access to the path ‘C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\RSReportServer.config’ is denied”.
After verifying that the SQL instance in question was running under the Network Service account I navigated to the C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer directory, and opened up the security properties of the rsReportServer.config file. I noticed Network Service was not listed. I explicitly granted Network Service access to the rsReportServer.config file, restarted IIS, and it started working!
As a side note, I when reporting services are installed several groups are created locally (or in AD if you are doing it on a DC). If your computer name is longer than 6 characters it cannot create the proper group name (it is too long) and it just shows the SID in AD Users and Computers. Odd huh?
Recent Comments