Have a unique issue I can't seem to find a good answer to. It does require a bit of backstory.
In March, we did a server upgrade for our customer. They were running on a lone SBS2003 box. We installed a new SBS2011 box in its place, but since the old one was in good shape, we also bought a license for Windows Server 2008 32 bit. The goal was to turn the old server into a Antivirus/Print/Apps server and have the SBS be the file server/dc/exchange. The problem was, Microsoft requires you to keep both SBS servers running when doing a migration. So our 32 bit Server 2008 had to be installed regardless, otherwise we could not complete the migration.
So I chose to install the Server 2008 as a virtual machine on my laptop, set it up and configure it, then move it to the SBS2011 server under Hyper V. This was all successful. I created it initially with a 60 GB Virtual Hard Drive. The D drive was set for 20 GB at that time. We then moved it to the hyper-v, and this was also successful. At that time, I had about 70 GB I could spare for the Virtual Server, so I went ahead and extended the drive to bring it close to 90 GB. This was all successful.
Later, I moved it using Acronis to the physical box (the old SBS2003 server.), blowing that server away in the process. The conversion was successful. But here is the problem:
When I extended the Data drive to reach the remainder of this server's storage capacity (It's about 270GB), Disk Management did it successfully and had no issue, and shows a D partition of 270 GB. But When I look in my computer and properties of D: drive, I still have the 90ishGB drive listed. Right now we are at half of that (45) but I would like to know if anyone has had this issue and what they would recommend doing to troubleshoot. I almost want to max the drive out and see if it allows you to go over but I don't want to do that live.